Privacy policy

Gorilla Gainz is a calisthenics tracker for iOS and Android. This policy explains what data we process, why, on what legal basis, and for how long. It describes only what the app actually does.

1. Controller

Cloo GmbH
Reumtengrüner Str. 32B, 08209 Auerbach, Germany
Represented by the managing directors Yannick Seeger and Paul Otto
Amtsgericht Chemnitz, HRB 38181
Contact: [email protected]

No data protection officer has been appointed so far. Whether one is required will be assessed before release.

2. Principles

• Your sessions are private until you explicitly share them.
• Every new post starts at Private, even if your last post was public.
• Health data, body weight and location stay private and never appear in the feed.
• No ad tracking, no advertising identifiers, no ad networks, no data sales.
• Declining any permission never blocks normal training.

3. What we process

Account and profile

Email address, password hash or the identifier of your sign-in provider (Sign in with Apple, Google Sign-in), username, optional avatar image, language, units, and your confirmation that you are at least 16. Purpose: providing the account, sign-in, email verification, password reset. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).

Training data

Workouts, weekly plan, weekly goal, sessions, individual sets with reps, holds and added weights, detected personal records, and your streak. Purpose: the core function of the app. Legal basis: performance of a contract (Art. 6(1)(b) GDPR).

Body weight and health data

You can always enter your body weight manually. Optionally, and only after you grant access in Apple Health or Health Connect, the app reads your most recent weight entry and stores it together with its source and timestamp. Also optionally, the app writes a completed session back to your health profile as a strength-training workout.

We store no raw health records. All that remains of an export is an outcome code (succeeded, failed, cancelled) plus one opaque identifier per platform, so a retry cannot create a duplicate entry. That ledger is visible only to you, is included in your data export, and is deleted with the session or the account.

Health data is never used for advertising, never shared with third parties, and never copied into analytics or crash reports. Legal basis: your explicit consent (Art. 9(2)(a) together with Art. 6(1)(a) GDPR). You can withdraw access at any time in your device settings.

Location

Location is strictly opt-in. If you grant it, a session stores exactly one point , preferably at the start and otherwise at completion. The fix is requested at low accuracy, so the point is coarse. There is no continuous tracking, no route, no place name and no map.

The point lives only in your private session document. It is never copied into posts, feeds, crew data or analytics. Legal basis: consent (Art. 6(1)(a) GDPR), withdrawable at any time in your device settings.

Content you publish

A post always belongs to a completed session and may carry text, exactly one photo, a summary of the exercises, and tagged crew members. Alongside that we process comments, reactions, reposts, friendships and reports. Photos are compressed before upload, which strips embedded metadata such as photo GPS. Legal basis: performance of a contract (Art. 6(1)(b) GDPR); for reports, blocks and moderation additionally our legitimate interest in a safe platform (Art. 6(1)(f) GDPR).

Subscription

If you buy Gorilla Gainz Pro, the transaction runs entirely through the App Store or Google Play. We never see payment details. Through RevenueCat we receive your subscription status, purchase history, renewals, cancellations and trials, plus a pseudonymous purchase identifier. Legal basis: performance of a contract (Art. 6(1)(b) GDPR); for keeping records, legal obligations (Art. 6(1)(c) GDPR).

Product analytics

We measure how the app is used with PostHog: sign-up and verification, onboarding completion, first workout, weekly goal, feed interactions, live sessions, paywall and subscription flow, and permission grant or error states at an abstract level. This comes with a pseudonymous identifier, app version, platform and coarse region.

We explicitly do not send raw text, photos, comment content, passwords, health values, body weights, precise coordinates or individual set values. Session replay is used only masked and sampled, and never on health, location, authentication or content screens. Legal basis: our legitimate interest in a working, improvable product (Art. 6(1)(f) GDPR); where store rules or national ePrivacy law require consent, we ask for it in the app.

Error and stability data

Sentry captures crashes, handled and unhandled errors, app hangs and performance data from both the app and the API: error type, stack trace, device model, OS version, app version and a pseudonymous identifier. Personal data is scrubbed before transmission; auth tokens, health data, coordinates, post content and set values do not belong in breadcrumbs or context. Legal basis: our legitimate interest in a stable and secure app (Art. 6(1)(f) GDPR).

Server logs

Requests to our API produce technical logs: IP address, timestamp, endpoint, status code and user agent. They serve operations, debugging, rate limiting and abuse prevention. Legal basis: legitimate interest (Art. 6(1)(f) GDPR).

Push notifications

If you allow notifications, we store a device token so we can send reminders and social alerts. Delivery itself runs through Apple's (APNs) and Google's (FCM) push services. Legal basis: consent (Art. 6(1)(a) GDPR), withdrawable at any time in your device settings.

4. Recipients and processors

We do not sell data. We use the following service providers, each under a data processing agreement where they process on our behalf:

How PostHog and Sentry are operated, meaning our own instance or the vendor's cloud, and which hosting provider and location we use will be named here before this text is approved. Beyond that, we disclose data only where we are legally required to.

5. International transfers

We run our services inside the EU wherever possible. Where a transfer to a third country does take place, in particular with Apple, Google and RevenueCat, we rely on an adequacy decision or on the European Commission's Standard Contractual Clauses. The specific regions will be added here before approval.

6. Retention

• Account, training and content data: until you delete it or delete your account.
• Free accounts can see 30 days of their own training history; the data remains stored and becomes fully visible again with Pro.
• Location point and health export ledger: until the session or the account is deleted.
• Server logs and crash reports: short term, at most 90 days.
• Analytics data: pseudonymous, at most 12 months.
• Purchase and accounting records: for as long as statutory retention periods require, typically up to 10 years.
• Moderation decisions and bans: for as long as platform safety requires.

Workouts that other users saved as their own copy remain as their copy; after a deletion, your name and profile are no longer part of it.

7. Your rights

Under the GDPR you have the right to:

• Access the data we hold about you (Art. 15).
• Rectification of inaccurate data (Art. 16).
• Erasure (Art. 17).
• Restriction of processing (Art. 18).
• Data portability (Art. 20).
• Object to processing based on legitimate interests (Art. 21).
• Withdraw consent at any time, with effect for the future (Art. 7(3)).

Two of these you can exercise directly in the app: data export and delete account live under Settings › Account. Both are available without a Pro subscription. The steps are on the support page.

For anything else, write to [email protected]. You also have the right to lodge a complaint with a data protection supervisory authority.

8. Minimum age

Gorilla Gainz is for people aged 16 and over. You confirm your age when creating an account. We do not target children and do not knowingly collect data from anyone under 16. If we learn of such an account, we delete it. Please report concerns to [email protected].

9. Security

All traffic is encrypted over HTTPS. Passwords are stored hashed. Media lives in private object storage and is reachable only through short-lived signed links. Administrative access is checked against roles on the server and logged with actor, timestamp and action.

10. Changes

We update this policy when the app changes. We announce significant changes in the app. The version published on this page, with the date shown above, is the one that applies.