Privacy Policy

Effective date: April 26, 2026 · Last updated: October 11, 2026

1. Who we are

Kerge is built and operated by an individual developer based in Estonia (European Union). For the purposes of the EU General Data Protection Regulation (GDPR), that developer is the data controller for any personal data this Privacy Policy refers to.

You can reach us at privacy@kerge.app.

2. What this policy covers

This policy describes how the Kerge mobile app for iOS and Android handles your information. It also covers the marketing website at kerge.app on which this policy is hosted. In the app, you can open it from Settings → About → Privacy Policy.

It does not cover third-party services we link to (such as the App Store, Google Play, or external websites), or the Kergekava web planner, which is a separate product.

3. Data the app stores on your device

The app keeps everything you create — workouts, sets, plans, exercises, settings — in a local SQLite database stored in the app's private storage on your phone. The database itself is never uploaded by Kerge. It is included in your device backups (iCloud Backup or Google's device backup) only because the operating system backs up app data; we do not control or access those backups. If you turn on Google Sheets sync, workout records are also sent to your Google Drive as described in section 6.

This local data may include:

• Workouts you log (exercises, sets, reps, weights, RPE, notes, timestamps)
• Plans and templates you build or import
• App settings and preferences (units, language, theme)
• Optional body-weight or measurement entries you choose to record

You can delete the local app data by uninstalling the app. This does not delete your Google spreadsheet, exported backups, or Apple Health records.

4. Apple Health (HealthKit)

On iOS, Kerge can integrate with Apple Health if you grant permission. When you do:

• Writing: When you finish a workout, Kerge writes the completed workout and its active energy to Apple Health so it appears in the Health app.
• Reading: Kerge does not request read access to Apple Health and does not read any of your Health records. If a future version needs to, we will update this section first to say what it reads and why, and iOS will ask for your permission separately.

HealthKit data stays in Apple's on-device Health store. Kerge never transmits HealthKit data to its own servers or to any third party, and never includes it in the Google Sheets upload. Health data is not used for advertising, shared with data brokers, or used for any purpose other than providing the app's training features.

You can review or revoke Health permissions at any time in iOS Settings → Privacy & Security → Health → Kerge. There is no equivalent system on Android — Kerge does not currently integrate with Google Fit or Health Connect.

5. Other device permissions

Camera

The app can use your camera to scan QR codes when you import a shared training plan. The camera feed is processed only on your device, only while the QR scanner is open, and never recorded or transmitted.

Photo library

To measure bar speed, you pick a video from your photo library. Kerge reads only the video you pick and analyses it on your device. Videos, measurements and the GIFs you make from them are never uploaded; they leave the app only if you share them yourself.

Notifications

If you enable notifications, the app schedules local notifications on your device (for example, rest-timer alerts), and on iOS can show your workout as a Live Activity on the Lock Screen. Neither involves a Kerge server or a push-notification service.

6. Optional Google Sheets sync

Kerge works offline without a Kerge account or backend. Google Sheets sync lets you keep a copy of your workout history in a spreadsheet in your own Google Drive. It is a one-way export, not a full backup or a way to sync changes between devices.

Your consent

Sync is off by default. Nothing is sent to Google until you tap Connect Google Sheets in Settings → Google Sheets and approve Kerge on Google's own consent screen. That approval is your consent to the upload. Once connected, Kerge creates the spreadsheet, uploads the workouts already in the app, and from then on updates it when you finish, import or delete a workout. You can withdraw consent at any time by disconnecting (see below).

The upload goes directly from your phone to Google, under your Google account. Kerge has no server in between and never receives a copy; Google stores the spreadsheet for you under its Privacy Policy.

What is uploaded

• Workouts tab: date and time, title, duration, number of sets, total volume, and your workout notes.
• Sets tab: for each set, the workout date and title, exercise, set number and type (for example, warm-up), reps, weight, RPE, whether it was completed, and its volume.
• Exercises tab: name, type, muscles worked, and equipment for each exercise you have logged.
• Random identifiers for workouts, sets and exercises, so Kerge can update existing rows instead of adding duplicates. Kerge generates these; they do not identify you.

When it first creates the spreadsheet, Kerge also adds a Dashboard tab of formulas that summarise the other tabs. Kerge never writes to the Dashboard again, nor to any tab you add.

Not uploaded: Apple Health data, body-weight entries, bar-speed videos and GIFs, plans and templates, and app settings.

What Kerge can access in your Google account

Kerge asks only for Google's drive.file permission, which covers files the app itself created. It cannot see or change anything else in your Drive, and it does not ask for your name, email address or profile. The sign-in credential Google issues is stored in your phone's secure storage (the iOS Keychain or Android Keystore) and is never sent to Kerge.

Kerge's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Kerge uses this access only to create and update your spreadsheet. It does not use it for advertising, does not sell it, and no person at Kerge reads it.

Disconnecting

Settings → Google Sheets → Disconnect stops all future uploads and deletes the Google credential from your phone. It does not delete the spreadsheet; it stays in your Drive, and reconnecting later resumes in the same file. Uninstalling Kerge also leaves the spreadsheet in place.

Disconnecting does not remove Kerge from your Google Account's list of connected apps. To revoke Kerge's access completely, open myaccount.google.com/connections and remove Kerge. This also matters if you uninstall without disconnecting first, because iOS can keep Keychain items after an app is deleted.

Deleting the uploaded copy

Because Kerge never holds a copy, the spreadsheet can only be deleted from your Google account. Disconnect sync in Kerge first, so it stops writing to that spreadsheet. Then delete the spreadsheet in Google Drive and empty Drive's trash (Google otherwise removes trashed files after 30 days). Copies you have downloaded or shared with other people must be deleted separately.

7. Crash and error reports

To find and fix bugs, the app uses Sentry (operated by Functional Software, Inc.) to report crashes and errors. When the app crashes or hits an unexpected error, Sentry transmits diagnostic information so we can investigate. This typically includes:

• The error message and stack trace
• Device model, operating system version, and app version
• The approximate time the error occurred
• Anonymous identifiers Sentry uses to group related events

We have configured Sentry not to attach your workout content, your Apple Health data, or any data you have entered into the app. We do not knowingly send personally identifying information to Sentry. Sentry processes this data on our behalf as a processor under GDPR; you can read Sentry's own privacy notice at sentry.io/privacy.

Our legal basis for this processing is our legitimate interest in keeping the app stable and secure (Article 6(1)(f) GDPR).

8. App updates

Kerge can receive bug-fix updates between App Store and Google Play releases through EAS Update, a service of Expo (650 Industries, Inc.). When the app starts, it asks Expo's servers whether an update is available. That request includes your platform, the app version and release channel, the update you currently have, and a random identifier generated for this installation; like any server, Expo also sees your IP address. It includes no workouts, health data, or anything you have entered. Expo processes this on our behalf as a processor under GDPR; see expo.dev/privacy. Our legal basis is our legitimate interest in delivering fixes quickly (Article 6(1)(f) GDPR).

9. App stores

The app is distributed through the Apple App Store and Google Play. When you install or update the app, those stores may collect data about you under their own privacy policies. Kerge does not receive identifying information about individual installs from those stores.

10. The kerge.app website

The marketing site at kerge.app is a static page. It does not set tracking cookies, does not run analytics, and does not have a comments or contact form.

For typography it loads web fonts from Google Fonts; doing so causes your browser to make a request to Google's servers, which can see your IP address and user-agent. See Google's privacy policy at policies.google.com/privacy.

11. Children

Kerge is not directed at children under 16. We do not knowingly process the personal data of anyone under 16. If you believe a child has used the app in a way that has caused us to process their data, please contact us at privacy@kerge.app and we will help you delete it (typically by uninstalling the app, which removes all locally stored data).

12. Your rights under GDPR

You can access, correct, or delete your local data directly inside the app, and remove local app data by uninstalling. If you enabled Google Sheets sync, manage or delete that copy in Google Drive as described in section 6.

For the limited data we do process — namely Sentry crash reports and EAS Update requests — you have the right to:

• Request access to data we hold about you
• Request that we correct or delete it
• Object to processing or request that we restrict it
• Lodge a complaint with your local data protection authority (in Estonia, the Andmekaitse Inspektsioon, aki.ee)

To exercise any of these rights, email privacy@kerge.app. Note that because crash reports and update requests are not tied to a real-world identity, we may need additional information (such as the approximate time of a crash and your device model) to find data relating to you.

13. International transfers

Sentry stores data in regions selected by us, and Expo is based in the United States, so processing may take place outside the European Economic Area. Where it does, we rely on the safeguards Sentry and Expo provide (including the European Commission's Standard Contractual Clauses) under GDPR Article 46. Your Google spreadsheet is stored by Google under your own account and Google's terms.

14. Data retention

Local app data is retained until you delete it or uninstall the app. Your Google spreadsheet remains in your Drive until you delete it; disconnecting or uninstalling Kerge does not delete that copy. Sentry crash events are retained for up to 90 days, after which they are deleted automatically. Expo keeps update-request logs under its own retention policy.

15. Changes to this policy

If we change how the app handles your data we will update this page and bump the "Last updated" date above. Material changes will also be flagged in the app's release notes.

16. Contact

Questions, requests, or concerns about privacy: privacy@kerge.app.