Strongs Privacy Policy

Last updated: November 9, 2026

Strongs is a workout logging app made by Aleksandar Mudrić. This policy explains what data the app handles and why. Short version: your data is used only to run the app for you. It is not sold, not shared for advertising, and not used for tracking.

What we store

We do not use analytics, advertising or tracking SDKs, and we do not collect your location, contacts or advertising identifiers. The app uses Firebase App Check, which lets Google check that requests to our servers come from the genuine app; it is not used for tracking and does not use an advertising ID.

Emails we send

Verification and password reset emails are sent from strongs.application@gmail.com through Google's Gmail.

To stop abuse, our servers keep short-lived records of recent requests: when a verification or password reset email was sent to an address (identified only by a one-way hash of the address), and how often an account sent feedback, connected a trainer or used Create from text (identified by your account ID or a one-way hash of it). These records expire 24 hours after the last request and are then deleted automatically, at the latest within another day.

Where it is stored

Data is stored with Google Firebase (Firebase Authentication with Identity Platform, Cloud Firestore, Cloud Functions and Crashlytics). Your training data, trainer connection and feedback are kept in Firestore in the European Union (multi-region eur3), and our server functions run in europe-west1 (Belgium). Google runs Firebase Authentication, which holds your account, from data centers in the United States, and processes crash reports on its global infrastructure. Google processes this data on our behalf under the Firebase data processing terms, which also cover transfers outside the European Union.

For security, Google logs sign-in requests, which can include your email address and IP address. These logs are kept for Google Cloud Logging's standard retention period (30 days by default) and are used only to investigate problems and abuse.

Your training data is readable only by your own signed-in account, and by a trainer you choose to connect (see below). The workout in progress is also saved on your device, so it survives the app being closed. On Android the app opts out of device backups and transfers.

Training with a trainer

Every account has a trainer code on its Profile. If you give your code to someone and they enter it in Strongs, they become your trainer, right away and until one of you ends it. Your trainer can then:

To make this work, we store who your trainer is, with the name on each account, or its email address if it has no name (accounts made with an email and password usually have none), so each of you can see the other. While you have a trainer, a copy of your workout in progress is kept on our servers so your trainer can see it, and your trainer's changes reach your phone as short instructions that your phone applies and then deletes. A note your trainer wrote is marked as theirs.

You have one trainer at a time. Profile → Remove next to your trainer's name ends their access at once; your trainer can also remove you. New Code stops your old code from connecting anyone new. Deleting your account also ends the connection and deletes your code. A trainer only gets access through a code you share, and never sees your feedback, account details or password.

Apple Health and Health Connect

If you turn on the Health option in Settings, Strongs writes each finished workout (type "strength training", with its start and end time and, when it can, estimated calories) to Apple Health or Health Connect. To estimate the calories, Strongs reads your latest body weight from there, if you allow it; this is the only health data the phone app reads, and the estimate is made on your device.

With Health on, Strongs on Apple Watch reads your heart rate and active energy during a workout it records, to show your heart rate and to save both with that workout in Apple Health; it reads nothing else.

Health data stays on your devices: it is never sent to our servers or stored there, never used for advertising and never shared with third parties. You can turn this off in Settings and revoke the permission in your phone's settings at any time. Workouts you import from a file are not written to Health.

Create from text

Some versions of Strongs include an optional feature, Create from text, that turns a workout you describe in your own words into a template or workout. It is off unless you turn it on, and it may not be available in your version of the app. When you use it, the text you typed, the names of your custom exercises (so the result can use them) and your weight unit are sent to Google's Gemini model on Vertex AI, processed in the European Union. Google does not use this data to train its models, may keep it in a cache for up to 24 hours, and may log requests to detect abuse under its terms. We do not store your text or the model's answer on our servers: our logs record only a shortened one-way hash of your account ID, the size of the request, its cost and whether it worked. Nothing is saved to your account until you save the result.

How long we keep it

Export and deletion

Children

Strongs is not directed at children under 13 and does not knowingly collect their data.

Changes

If this policy changes, the new version will be posted on this page with a new date. See also the Terms of Use.

Contact

Questions or requests: mudricaleks@gmail.com, or the feedback button in the app.