Privacy Policy
Last updated: 9 September 2026
The short version
- terce has no account and no password.
- 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 three first-party cookies to connect an ad click to a purchase 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, your daily totals and the calendar heatmap are written to a database on your iPhone. They are not uploaded to us. If you have iCloud backup switched on, they are included in your device backup, which is Apple's service and not ours.
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*, not about *what you were doing*:
- that the app was opened, and that a session started, finished or was stopped;
- the length of an interval and the clock face in use;
- that the paywall was shown, and whether a purchase or a restore followed;
- a random identifier for your install, the app version, and your device model and iOS version.
We do not collect the contents of anything, your location, your contacts, your photos, or any identifier Apple uses for advertising. 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. Each writes whichever of the cookies below it needs — the funnel has no checkout yet, so it writes fewer — 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 not linked to your name or your email.
- `terce_app_user_id` — a random identifier written when you begin checkout. It is the id your purchase is filed under, and it is what lets your purchase reach the app on your phone.
- `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 later in your visit. 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.apporget.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.apporget.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.
- We write to you once — a single email with a TestFlight link when the first build is ready to hand over. 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
We never see your card details. Web purchases are processed by Paddle as merchant of record; app purchases are processed by Apple. Your card number goes to them, not to us.
From Paddle we receive your email address, the country used for tax, the plan you bought, the amount, and a transaction id. We use these to give you access, to send you receipts and service emails, and to keep the records tax law requires.
6. Why we are allowed to do this
Where the GDPR or UK GDPR applies:
| What | Basis |
|---|---|
| Running the app and giving you access to what you bought | Performance of a contract |
| Receipts, renewal notices, cancellation confirmations | Performance of a contract |
| The three first-party cookies in §4 | Legitimate interests — measuring our own advertising, with no third-party sharing |
| The anonymous page views in §4 | Legitimate interests — counting visits to our own website, with no cookie and no cross-site identifier |
| The performance timings in §4 | Legitimate interests — keeping our own website fast, with no cookie and no cross-site identifier |
| Holding your address on the waitlist and sending the launch email | Consent — you gave us the address for exactly that, and you can withdraw it at any time |
| Product analytics in §3 | Legitimate interests — understanding and improving the product |
| Keeping invoices and tax records | Legal obligation |
You can object to anything based on legitimate interests — see §9.
7. Who we share it with
| Who | What they get | Why |
|---|---|---|
| Paddle.com Market Ltd | Your email, billing country, purchase details | Merchant of record — they take the payment and issue the invoice |
| Apple | Purchase and subscription status for app purchases | Apple sells and manages App Store purchases |
| RevenueCat, Inc. | Your random purchase id and subscription status | Tells the app whether you have access, across your devices |
| Amplitude, Inc. | The events in §3 and §4, under random identifiers | Product analytics |
| Vercel Inc. | Your IP address and request logs, briefly; the anonymous page views and performance timings in §4 | Hosting our websites, counting visits to them, and measuring how fast they loaded |
| Supabase, Inc. | Your waitlist email address, if you joined | Stores the waitlist |
Every one of them acts on our instructions or as an independent controller for its own legally required purposes. 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 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.
- Analytics events: kept for 24 months, then deleted.
- Purchase and invoice records: kept as long as tax law requires, currently at least three years.
- Cookies: one year, or until you clear them.
- Waitlist addresses: kept until the launch email has been sent and then for six months, so we can answer a question about it, after which the row is deleted. Ask us sooner and we delete it sooner.
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 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 under 13, 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.
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