Privacy Policy — Spark Break

Spark Break is built so that the sensitive part — which apps you chose and how long you spent in them — never leaves your iPhone. There is no account and no server of ours holding your plan at all: everything the app knows about you lives on the phone. This page explains that in plain language, then lists the little that does leave it.

1. Who we are

Spark Break is the controller of the personal data described here. It is built and run by one person, not a company — there is no office to write to, so questions, requests and complaints all go to [email protected], and they reach a person rather than a queue.

2. What stays on your device

Apple seals Screen Time data inside the app on your phone. It is not something we choose not to upload — we are not able to. The following never reaches us:

The apps you protect: Stored as opaque Apple tokens. Even we cannot read which apps they are.
Per-app usage time: Rendered by Apple's own view inside the app. Never transmitted.
Camera frames during a rep: Read on the device to count the movement, frame by frame, and dropped immediately. Nothing is recorded, nothing is saved, nothing is sent.
Whether your plan is paid for: Asked of the App Store each time the app opens, and decided on the phone from Apple's own answer. A record of each purchase goes to RevenueCat (section 3), but nothing there decides whether your apps are protected.

There is no sign-in and no account: your plan, your history and your settings are stored only on this phone. Delete the app and they are gone with it.

3. What leaves your phone

Four things, none of them to a server of ours — we run none, and this website is a folder of static files on Google's hosting. They go to Apple and Google, and to two services that work on our behalf: PostHog for product analytics and RevenueCat for subscription records. Nothing below is tied to an account, because there isn't one.

Crash and diagnostic reports When the app fails: the device model, iOS version, and where in the code it broke. Purpose: fixing the crash. No usage data, nothing about which apps you protect.

Product analytics Counts of events like "a break was completed" or "onboarding finished", along with your plan settings — goal, target, mode, and which week you are in — and when the app is opened and closed. The same events go to Google and to PostHog. Each gives the install an anonymous id so one phone is not counted twice; it points at an install, not at a name, an email or an account. Both use the connection's IP address to tell roughly which country it came from. Purpose: knowing which parts of the app actually work. Never a per-app figure, never which apps you protect.

Subscription records When you start a subscription or a free trial, the store's record of it — which plan, the price and currency, the dates, and an anonymous id — goes to RevenueCat, which keeps our subscription records. Apple tells RevenueCat directly when a subscription renews, is cancelled or is refunded. RevenueCat also passes these events, with the anonymous analytics id, to PostHog, so a purchase can be counted alongside the steps before it. Purpose: knowing how many people subscribe, stay and leave. No card details: neither we nor RevenueCat ever see them.

Push token Only if you allow notifications: the anonymous device token Apple issues, so a reminder can reach this phone. Purpose: delivering the reminders you turned on. It says nothing about you or your usage.

Payment itself is Apple's business, not ours: Apple takes the money and we never see your card. Whether your plan is active is decided on the phone, from the App Store's own answer each time the app opens.

4. How long it is kept

We hold no personal record of you, so there is nothing on our side with a retention period. Your own data lives on your phone for as long as the app does — delete the app and it goes with it. Crash reports and analytics are held by Apple and Google under their own policies, up to 14 months in Google's case. PostHog and RevenueCat keep analytics events and subscription records for as long as we use them, and delete them when we ask. The push token stops working as soon as you turn notifications off.

5. Your rights

You can ask for a copy of what we hold, correct it, export it, delete it, or object to a particular use — though in practice we hold nothing that identifies you, so the honest answer to most requests is "there is nothing on file". Removing your data is entirely in your hands, as described on the deletion page. We answer requests within 30 days, and you can complain to your local data protection authority if we get it wrong.

6. Children

Spark Break is not made for children under 13, or under 16 where local law sets that age. We do not knowingly collect their data. If you believe a child's data reached us, write to us and we will remove it.

7. Where data is stored

Your data stays on your iPhone. We run no servers, so nothing is stored with us. The four exceptions in section 3 are handled by Apple (crash reports, push delivery), Google (crash reports, analytics), PostHog (analytics) and RevenueCat (subscription records), who may process them in the United States and other countries under the safeguards those providers offer, including standard contractual clauses.

8. Changes to this policy

If we change something material, we update the date at the top and tell you in the app before the change takes effect. Older versions are available on request.

9. Contact

Questions, requests and complaints: [email protected]. We reply within two business days.