Privacy Policy

Last updated: 26 October 2026

The short version

• The app asks for no account, no password and no email address. You buy inside the app, from Apple, and we never see your payment details.
• Your focus sessions are stored on your device, not on our servers.
• We use three analytics tools — one to count how the product is used, one to count visits to our website, and one to measure how fast the website loaded — and first-party cookies to tell which advertising brought you to our waitlist or to the App Store, so we know what our advertising costs.
• We do not sell your personal data, and we do not share it with advertisers.

1. Who is responsible

Bohdan Kolesnik, an individual entrepreneur registered in Ukraine, of Vinnytsia, vul. Skaletskoho 36A, apt. 21, Ukraine, is the controller of the personal data described here.

Contact: terceapp.support@gmail.com

2. What the app stores, and where

Your intervals are written to a database on your iPhone, and your record — its days, weeks and months — is worked out from them there. Our analytics hears of each interval as it happens — that it started, its length, how long it ran (§3) — but never the record built from them. If you have iCloud backup switched on, the database is included in your device backup, which is Apple's service and not ours.

A few totals do leave the device, and only when you look at them: opening your record sends how many sessions you have finished and how many hours you have focused in all, and how many days in a row you have finished one; when the share screen draws a card, it sends the hours and sessions on that card. They go with our analytics, under the random identifier described in §3. Those are totals; the record's days, weeks and months are never sent.

If you signed in on an earlier version of the app, the address you signed in with is kept on your iPhone too, so Settings can show who is signed in. Signing out removes it. This version of the app does not offer sign-in.

Deleting the app deletes this data.

3. What we collect when you use the app

We collect product analytics so we can tell whether terce is worth continuing to build. These are events about what happened in the app, and this is the whole list:

• that the app was opened — including how long it had been since the last time — and that a session started, finished or was stopped;
• that you held the clock and let it go again, that you extended a session and by how much, and that a break started and ended;
• the length of an interval and the clock face in use;
• on the first launch: which of its screens you saw; your answer to "What did you come here for?", picked from a fixed list of five, which stays with your install's later events; how many of its hour windows you picked; whether you made its promise by holding it down; the interval lengths you picked there and the clock face it ends on; and how long it took. Never anything you type;
• whether you allowed notifications when the app asked, at your first start;
• that the paywall was shown or closed, which locked face or part of the record opened it, whether your install has a free part or is sold wholly by subscription, and whether a purchase or a restore followed;
• if you signed in on an earlier version of the app: that you signed out, or deleted that account. Never its address or the code;
• the totals described in §2, when you open your record or the share screen draws a card, and whether that card covers a week or a month; that you saved a card to your photo library; and, each time the share sheet closes, whether a card was handed to another app — never which app;
• which settings you change, and what you changed them to: the theme, whether the weekly recap is on, which sound plays when an interval ends, or none, whether the screen is kept awake, and whether the progress bar is on;
• that you used Siri, a Shortcut or Spotlight to start, stop or extend a session, skip a break, show the clock, or ask for today's total;
• that you paused, resumed or stopped a session with the buttons on its Live Activity;
• that a weekly recap notification arrived, and whether you opened it;
• a random identifier for your install, the app version, and your device model and iOS version;
• while you are signed in to an account from an earlier version of the app, the random id of that account's purchase, so the app and that account count as one person. Signing out stops it being sent;
• the identifier for vendors — a random id that iOS gives our apps for your device, and that only our apps ever see. It is how we can tell that two sessions were the same install before you have bought anything. It is not the advertising identifier, we cannot use it to recognise you in anybody else's app, and you can clear it yourself by deleting every app of ours from the device;
• your device's language and mobile network operator, which the analytics tool attaches to events by default;
• if Amplitude switches it on for its analytics tool: after the app crashes, a report of where in the code it stopped, and counts of how that tool itself is working, with your device model and iOS version. These are never linked to you or to the events above.

Each time it opens, the app also asks terce.app for its current settings. That request carries no identifier and nothing about how you use terce; like any request, it reaches our host (§7) from your IP address.

We do not collect the contents of anything, your location, your contacts, your photos, or any identifier Apple uses for advertising.

On location specifically: analytics tools normally record the IP address a request arrives from and turn it into a country, a region and a city. We switch all of that off — no IP address, no country, no region, no city — so there is no geography attached to any of these events.

terce does not ask for the App Tracking Transparency permission because it does not track you across other companies' apps and websites.

4. What we collect on this website

This covers both of our websites — terce.app, where you are reading this, and get.terce.app, where our advertising sends people. Neither sells anything. Each writes whichever of the cookies below it needs, and both run the same two measurement tools. Nothing is collected on either that is not described on this page.

• terce_anon_id — a random identifier written to a first-party cookie the first time you visit. It lets us count one visitor as one visitor across our pages. It is linked to nothing about you unless you join the waitlist, which keeps it beside your address (below).
• terce_app_user_id — a random identifier written only when a checkout begins on this website. We do not sell anything on this website, so it is not written today.
• terce_attribution — the campaign parameters in the link you followed, and the address of the page that linked to us, written to a first-party cookie so that they are still known if you join the waitlist, or follow our link to the App Store, later in your visit. When you follow that link they go with the event that records it, and the campaign's name goes to Apple in the link itself, so that Apple can count the installs each of our campaigns brings. It holds no identifier of any kind and nothing you typed. We only write it when there is something to record, and we never overwrite it: if you first arrived from an advertisement, that advertisement stays credited. We do not record it when the page that linked to us is one of our own.
• A page view — which page you opened, the page you came from, your browser, your device type and the country, region and city your request came from. This is Vercel Web Analytics, and it counts visits. It sets no cookie, it stores no identifier that could follow you to another website, and the hash it uses to tell one visit from another is discarded after 24 hours. It runs from our own domain — no request for it leaves terce.app or get.terce.app.
• How fast the page was for you — which page you opened, how long its largest element took to appear, how quickly it answered your first tap, how much it moved while loading, and your connection speed and country. This is Vercel Speed Insights, and it exists so we can tell whether the site is slow for real people rather than only on our own machines. It measures timings, not what you did. It sets no cookie, it stores no identifier that could follow you to another website, and like the page view above it runs from our own domain — no request for it leaves terce.app or get.terce.app.

All three cookies are first-party, set with HttpOnly and Secure, scoped to terce.app and its subdomains, and expire after one year. HttpOnly means no script on the page can read them. We run no third-party advertising or tracking cookies on this site.

If you join the waitlist, we store the email address you type and nothing else about you. Alongside it we keep the cookie id from above and the campaign parameters, so we can tell which advertising brought you, and the date you joined. The row also records the page that linked to us, which version of the page you were shown, which of our sites you joined from, and whether the launch email has gone out to you yet — so that a second send cannot reach you twice.

• We write to you twice at most — an email with a TestFlight link when the first build is ready to hand over, and one with the App Store link on the day terce is released. Every message carries an unsubscribe link.
• We do not sell, rent, share or publish the list, and nobody outside the people named in §7 is given it.
• Ask us to remove you at any time and we delete the row, not just flag it. Email terceapp.support@gmail.com; you do not have to give a reason.
• The address is never sent to our analytics. The event that records a signup carries only the part after the @ — gmail.com, or a company domain — which tells us nothing about who you are.

5. What we collect when you buy

You buy terce inside the app, from Apple, and we never see your card details, your name or your Apple Account. Apple takes the payment, and tells the app through RevenueCat (§7) which plan your install holds and whether it is current. From that we see the plan, its price and the App Store country it was bought in, and when it started, renews, ends or is refunded — under a random id, never your name or your email address. We do not sell anything on this website.

Accounts from earlier versions. Earlier versions of the app let you sign in with an email address, to bring in a subscription bought on our website. This version does not, and nobody can create an account. If you signed in before, we keep that account — its address, the random id of its purchase and that payment's transaction id, and whether it is current — until you delete it (§8). To delete it, use Settings → Account → Delete account in the app, which emails a six-digit code to its address to confirm it is you, or email us. A code is stored only as a keyed hash, stops working after ten minutes or five wrong tries, and is deleted once it is used.

6. Why we are allowed to do this

Where the GDPR or UK GDPR applies:

You can object to anything based on legitimate interests — see §9.

7. Who we share it with

Every one of them acts on our instructions or as an independent controller for its own legally required purposes — except Apple, which sells terce in the App Store as a controller in its own right, under its own privacy policy. None of them is given your data to advertise to you, and none of them buys it from us.

8. Where your data goes, and for how long

We are in Ukraine, and the services above are in the EU, the UK and the United States. Transfers out of the EEA and the UK rely on the European Commission's Standard Contractual Clauses or on an adequacy decision.

Waitlist addresses, and the accounts from earlier versions, are stored in the United States, in Supabase's us-west-2 region (Oregon). If you are in the EEA or the UK, that is a transfer out, and it relies on the Standard Contractual Clauses in the sentence above.

One thing is cleared out automatically, on no fixed date: a code we email, a day after it stops working — removed the next time our account service runs after that. Nothing else is deleted on a schedule, so rather than quote a period we do not keep to, this is what actually happens to each thing:

• Analytics events: held by our analytics provider until we delete them. We have not set an expiry, and there is no date on which they go.
• Purchase records: Apple and RevenueCat hold the record of an App Store purchase, under their own policies. We keep the records tax law requires, currently for at least three years.
• Cookies: one year from the day each is written, or until you clear them. This is the one item on this list that does expire by itself — the expiry is set on the cookie.
• Waitlist addresses: kept until you ask us to remove you. Sending the launch email does not remove anybody. The unsubscribe link in that email deletes your row outright — the row, not a flag on it — and emailing terceapp.support@gmail.com does the same. Those two are the only things that delete an address.

• An account from an earlier version — its address, the random id of its purchase and that payment's transaction id: kept until you delete it, in the app under Settings → Account, or by emailing us. Either removes it from terce's records outright, and keeps one thing: a one-way hash of that random id — never the id, never your address — so that a subscription you did not cancel cannot write the account back when it renews. The hash cannot be turned back into either, and it has no expiry. RevenueCat keeps the record of that account's purchase under its own policy. A subscription ending does not delete the account. A code we email goes when it is used, when the account is deleted, or a day after it expires, and is useless after ten minutes either way.

If you want any of this gone sooner, ask. §9 is the route, it costs you nothing, and we answer within one month.

9. Your rights

You can ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, or to receive it in a portable form. Email terceapp.support@gmail.com and we will answer within one month. We will not charge you and we will not treat you differently for asking.

Deleting the app removes everything stored on your device. Clearing your browser's cookies removes the three cookies in §4. If you signed in on an earlier version of the app, you can delete that account yourself, in the app under Settings → Account → Delete account, with a code sent to its address.

If you are in the EEA or the UK, you can complain to your national data protection authority. If you are in California, you have the rights described above under the CCPA; we do not sell or share personal information as those terms are defined there, and we do not offer financial incentives for data.

10. Children

terce is not directed at children, and we do not knowingly collect data from them. If you believe a child has given us data, email us and we will delete it.

The waitlist needs consent, and consent has an age. In the EU and the UK a child cannot give valid consent for an online service on their own below an age each country sets between 13 and 16. So do not join the waitlist if you are under 16 unless a parent or guardian is doing it with you. If you have, email us and we will remove the address — you do not have to give a reason.

11. Changes

If we change this policy we will update the date at the top and, where the change materially affects you, tell you by email before it takes effect.

12. Contact

Bohdan Kolesnik Ukraine, Vinnytsia, vul. Skaletskoho 36A, apt. 21 terceapp.support@gmail.com