Privacy Policy
Suta is a training app that keeps your workouts on your device and in your own iCloud. It has no user accounts and no advertising, and it does not track you across other companies' apps or websites. This policy explains what leaves your phone, where it goes, and why.
The short version. Every session, set and record you create is stored on your device and synced to your own private iCloud account, so a new phone or a reinstall does not cost you your history. That record goes to Apple, not to us: we have no server and no way to read it. What else leaves your phone is what the App Store and our purchase provider need in order to sell you the Founding Member unlock and remember that you own it, a crash report if the app crashes, and usage analytics — which screens you use, and a summary of each run — unless you switch it off in the app's Settings. None of that identifies you by name.
Contents
1. Who is responsible
Suta is developed and published by Andrei Vataselu, an independent developer ("we", "us"). For the purposes of the UK and EU General Data Protection Regulation, we are the data controller for the limited personal data described in this policy.
You can reach us at contact@suta-app.com.
2. Data stored on your device
Everything you record in the app is written to a private database inside the app's own storage area on your device:
- Sessions — the exercise, when the session started and ended, its outcome, and total elapsed time.
- Sets and rep entries — the numbers you logged and when you logged them.
- Derived state used for display, such as your current and longest streak.
- Small preferences held in the app's own settings storage, such as the exercise you last selected, whether you have seen onboarding, and whether usage analytics is switched on.
Your training record is not transmitted to us. There is no server component to Suta and no way for us to read your history. It is synced to your own iCloud account, described next. The one exception is the summary of each run that usage analytics includes (section 5) — the exercise, the reps, the time and how the run ended, never the record itself — and you can switch that off in the app's Settings.
If you have iCloud Backup or an encrypted device backup enabled, your app data may also be included in that backup. That backup belongs to you and is governed by Apple's Privacy Policy, not by this one.
3. iCloud sync
The training data listed above is synced to your own private iCloud account, using the iCloud storage Apple provides to apps (CloudKit). This is what lets your history appear on your other devices and come back when you reinstall the app.
- It is stored in your iCloud account, not ours. We are not a party to it, we hold no key to it, and we cannot read, export or delete it.
- It syncs only between devices signed in to the same Apple Account.
- It requires no account of ours and no sign-up — it uses the Apple Account already on the device.
- If you are not signed in to iCloud, or you turn Suta off under iCloud in the Settings app, the app keeps working and simply stays on that device.
Apple is the processor for this storage, and its handling of it is covered by Apple's Privacy Policy. Section 12 explains how to delete the synced copy.
4. Purchases
Suta offers an in-app purchase that unlocks the paid features. Two parties are involved, and neither of them gives us your identity.
Apple
The purchase itself is made through the App Store. Apple handles payment end to end. We never see and never receive your name, email address, card details or billing address. Apple's handling of that transaction is covered by Apple's Privacy Policy.
RevenueCat
To validate your purchase receipt and remember that you own the unlock — including after you reinstall the app or set up a new device — the app uses RevenueCat, a purchase infrastructure provider acting as our data processor. When you open the app, RevenueCat may receive and store:
| Data | Why |
|---|---|
| A randomly generated anonymous app user ID | To attach an entitlement to an install without an account. It is not linked to your name, email or Apple ID. |
| Purchase receipt and transaction history | To verify the purchase is genuine and still valid. |
| Device and app information — platform, OS version, app version, country, locale, time zone | To deliver the correct offer and to make purchases work across a user's devices. |
While usage analytics is switched on (section 5), RevenueCat also receives Apple's ad attribution for the install: whether it followed a tap on one of our App Store ads, and which campaign and search keyword. It tells us which ads lead to purchases.
RevenueCat processes this on our behalf under a data processing agreement. Their handling is described in the RevenueCat Privacy Policy.
RevenueCat also reports purchase events — a purchase, a renewal, a cancellation, a refund — to our analytics provider, PostHog (section 5). While usage analytics is switched on, the RevenueCat ID is linked to the random analytics identifier, so those events can be seen alongside how the app is used. That tells us which parts of the app lead people to buy; it does not tell us who you are.
Your training data is never sent to RevenueCat.
5. Crash reports and usage analytics
The app uses PostHog, an error tracking and product analytics provider acting as our data processor, for two things: reports of crashes, and usage analytics.
Crash reports
If the app crashes, or hits an error it cannot recover from, it sends a report to PostHog so we can find and fix the fault. A crash cannot be reported while it is happening, so the report is sent the next time you open the app. It contains:
| Data | Why |
|---|---|
| What went wrong — the kind of error, and the parts of the app's code that were running when it happened | To find the fault in the code. |
| Device and app information — device model, OS version, app version, locale, time zone | To reproduce the fault on the same kind of device. |
| A randomly generated identifier for the install, and one for the app session | To tell one crash affecting many people apart from many crashes affecting one person. It is not linked to your name, email or Apple ID. |
Your training data is never included in a crash report.
Usage analytics
Unless you switch it off, the app also tells PostHog how it is used, so we can see what works, what does not, and what to build next. It sends:
| Data | Why |
|---|---|
| The screens you open and the actions you take — for example starting a run, choosing an exercise, opening the upgrade screen or sharing a card | To see which parts of the app are used, where people get stuck, and what leads to a purchase. |
| Your answers in the introduction — how long you expect 100 pushups to take, and the exercises you pick | To understand who the app is for. |
| A summary of each run — the exercise, the reps, the time, the number of sets, the time you were chasing and whether you beat it, and how the run ended | To see whether people improve, and how easy the app is to use mid-set. |
| Your plan, and choices such as which exercises you list and whether reminders are on | To understand which features people rely on. |
| Whether you installed the app after tapping one of our ads on the App Store, and if so, the identifiers of that ad's campaign, ad group and search keyword. Apple provides this without the advertising identifier (IDFA) and without tracking you | To see which ads bring people who keep training, and stop paying for the ones that don't. |
| Device and app information, and the random identifiers described above | As for crash reports. |
It never includes your name, email address, contacts, location, the name you put on a share card, or your training history as a whole.
Your choice. Usage analytics is on by default. To switch it off, open Settings in the app and turn off Share usage data. It stops immediately, and the link to your purchase record described in section 4 is removed. Crash reports continue, because they are used only to fix faults.
PostHog necessarily sees your device's IP address when a report or an event arrives, as any server does; we have configured it not to store it. PostHog's handling is described in the PostHog Privacy Policy.
6. What we do not do
To be explicit, Suta contains:
- No advertising inside the app, and no advertising identifier (IDFA). The app does not ask for permission to track, because it does not track you across other companies' apps or websites — the usage analytics in section 5, including whether you came from one of our App Store ads, stays with us and our processors.
- No user accounts, sign-in, or email collection. There is nothing to register for, and the only time we ever have your email address is if you choose to write to us (section 7).
- No social features, sharing to third parties, or contact-list access.
- No location, camera, microphone, photo library, health or motion data access.
- No selling or sharing of personal information, as those terms are defined under the California Consumer Privacy Act. We have never done so and have no plans to.
7. If you email support
If you write to us, we receive your email address and whatever you choose to put in the message. We use it only to answer you, and we keep the correspondence no longer than we need to for support and record-keeping purposes.
8. Legal bases
Where the UK or EU GDPR applies, we rely on:
- Performance of a contract — processing purchase and entitlement data so that the features you paid for are unlocked on your devices.
- Legitimate interests — verifying receipts to prevent fraudulent unlocks, finding and fixing the faults behind crash reports, understanding how the app is used so we can improve it, and responding to support requests you send us.
We do not rely on consent for anything described here. Purchase processing is needed to deliver what you paid for. Crash reports and usage analytics are limited to what it takes to fix and improve the app and carry nothing that identifies you by name, and you can object to usage analytics at any time by switching off Share usage data in the app's Settings.
9. How long data is kept
- Training data — kept until you delete it. Because it syncs to your iCloud account, deleting the app no longer erases it: Reset progress in the app's Settings does, everywhere at once. See section 12.
- Purchase and entitlement records — retained by RevenueCat and by Apple for as long as needed to honour the purchase and to meet tax and accounting obligations, which in most jurisdictions is several years.
- Crash reports — kept for as long as they help us fix the fault, and no longer than 12 months.
- Usage analytics — kept for as long as it helps us understand how the app is used, and no longer than 12 months.
- Support email — typically up to 24 months.
10. International transfers
RevenueCat is based in the United States, so purchase-related data described in section 4 is processed there. Where such transfers are subject to UK or EU data protection law, they are made under the European Commission's Standard Contractual Clauses, incorporated into our agreement with RevenueCat.
PostHog is also based in the United States, and the crash reports and usage analytics described in section 5 are stored there, under the Standard Contractual Clauses in our data processing agreement with PostHog.
11. Your rights
Depending on where you live, you may have the right to request access to your personal data, correction, deletion, restriction of processing, portability, or to object to processing; and under the CCPA, to know what is collected and to opt out of sale or sharing (we do neither). Exercising any of these rights will never make the app worse for you.
Because there are no accounts, we usually hold nothing that identifies you, and the honest answer to an access request is often "we have nothing under your name". Where a request concerns your purchase record, write to us and we will pass it to RevenueCat and confirm the outcome.
Usage analytics is stored against a random identifier rather than against you. You can stop it at any time in the app's Settings; to ask for what has already been collected to be deleted, write to us and we will delete what we can attribute to your install.
To make a request, email contact@suta-app.com. We aim to respond within 30 days. If you are in the EEA or the UK and are not satisfied with our response, you may lodge a complaint with your national data protection authority.
12. Deleting your data
Deleting the app is no longer enough. It removes the copy on that device, but your training data is synced to your iCloud account and will come back when you reinstall — which is the point of syncing it, and worth knowing before you rely on a delete.
To erase it for good, open Settings in the app and choose Reset progress. That deletes every session, set and record from the device, from iCloud and from your other devices. It cannot be undone, and we cannot restore it for you, because we never had a copy. It does not reach the usage analytics described in section 5; section 11 explains how to have that deleted.
You can also remove the data from iCloud without the app, in the Settings app under your name → iCloud → Manage Account Storage, and you can stop the sync there at any time.
A purchase is separate from your data: it stays attached to your Apple ID, and reinstalling the app and using Restore Purchases brings the unlock back — but not your training history.
13. Children
Suta is not directed to children under 13 (or the minimum age of digital consent where you live, if higher), and we do not knowingly collect personal data from them. If you believe a child has provided us with personal data, contact us and we will delete it.
14. Security
Your training data is protected by iOS itself: app storage is sandboxed and encrypted at rest when your device has a passcode set. The synced copy sits in your own iCloud account, encrypted in transit and at rest by Apple. Communication with RevenueCat, PostHog and the App Store uses encrypted connections. No system is perfect, but there is no database of ours to breach — which is the strongest security property this app has.
15. Changes to this policy
If we change what the app does with data, we will update this page and change the effective date at the top. Material changes will also be noted in the app's release notes. Continuing to use the app after a change means you accept the updated policy.
16. Contact
Andrei Vataselu
contact@suta-app.com