Privacy
Last updated September 26, 2026
Count.do is a countdown tracker made by Orkestra Studios. This page says what we keep, why, where it lives and for how long. We keep as little as we can: no ads, no trackers, no third-party cookies.
Who we are
Orkestra Studios runs Count.do and is responsible for the data described here. Write to berkcan@orkestra.co about anything on this page.
What we keep
- Without an account, your countdowns stay in your browser, not on our servers. A random id kept with them lets us count steps such as "made a first countdown" without knowing who you are.
- With an account, we keep your email address, the countdowns you save, and your sign-in sessions with the IP address and browser they came from.
- When a shared countdown is opened, we note the view once per browser tab, with the random id or your account.
- When you make, share, import or finish a countdown, we note that event too, with the random id or your account.
- We note a few first steps through Count.do, such as a first countdown or a first share, once each, with the random id or your account.
- To stop abuse, we keep short-lived counters, keyed by IP address, account or email address, that limit how often something can be done.
- When something breaks, we keep the error, the kind of page it happened on and the app version. We never keep a countdown's link there, and we mask email addresses.
- When an admin acts on an account or a countdown, we keep a record of which one, what changed and, for a suspension, why.
Why we keep it
To run Count.do for you (your account and countdowns), to keep it safe (limits, sessions, error records), and to see how it is used as a whole (views and steps). We do not sell data, show ads or build profiles. The legal grounds are providing the service you asked for and our legitimate interest in keeping it safe and understanding its use.
Cookies and storage
One cookie for everyone who signs in, and a second only for an admin viewing the site as someone else. Everything else stays in your own browser.
| Name | Kept in | What for | How long |
|---|---|---|---|
| __Secure-better-auth.session_token | Cookie | Keeps you signed in | About 7 days, renewed as you use it |
| __Secure-better-auth.admin_session | Cookie | Lets an admin return to their own account after viewing the site as someone else; admins only | Until they return |
| count-do.guest.v1 | Local storage | Your countdowns and random id before you sign in | Until you clear it |
| count-do.guest-import-reported | Local storage | Remembers countdowns that could not be moved into your account, so we tell you about them once | Until you clear it |
| count-do.viewed.* | Session storage | Counts a view once per tab | Until the tab closes |
| count-do.step.* | Session storage | Counts a step once per tab | Until the tab closes |
| count-do.completed.* | Session storage | Counts a finished countdown once per tab | Until the tab closes |
| count-do.guest-import-tried | Session storage | Moves your countdowns into your account once per visit | Until the tab closes |
- __Secure-better-auth.session_tokenKeeps you signed inCookie · About 7 days, renewed as you use it
- __Secure-better-auth.admin_sessionLets an admin return to their own account after viewing the site as someone else; admins onlyCookie · Until they return
- count-do.guest.v1Your countdowns and random id before you sign inLocal storage · Until you clear it
- count-do.guest-import-reportedRemembers countdowns that could not be moved into your account, so we tell you about them onceLocal storage · Until you clear it
- count-do.viewed.*Counts a view once per tabSession storage · Until the tab closes
- count-do.step.*Counts a step once per tabSession storage · Until the tab closes
- count-do.completed.*Counts a finished countdown once per tabSession storage · Until the tab closes
- count-do.guest-import-triedMoves your countdowns into your account once per visitSession storage · Until the tab closes
Where it lives
Vercel hosts the site and keeps request logs for about an hour. Neon keeps the database in Frankfurt, Germany. Resend delivers sign-in emails. Each handles data only to run Count.do for us; some of them process data in the European Union and the United States.
How long we keep it
We clean up once a day, so each limit below can run over by about a day.
- Your account and countdowns: until you delete them or ask us to delete your account.
- Sign-in sessions: a session ends about 7 days after its last use. We delete its record, with its IP address and browser, 30 days after that.
- Sign-in codes: they expire after 5 minutes; the next cleanup deletes them.
- Abuse counters (keyed by IP address, account or email address): deleted once unused for 24 hours.
- Views of shared countdowns: 90 days.
- First steps, countdown events other than views, and admin records: kept while Count.do runs.
- Error records: capped in number; the oldest go first.
- Internal event records: 30 days after they are handled.
Your rights
Under Türkiye's Personal Data Protection Law (KVKK) and the EU's GDPR, you can ask to see, correct, export or delete your data, and object to how we use it. Write to berkcan@orkestra.co; we answer within 30 days. You can also complain to Türkiye's Personal Data Protection Authority or to the data protection authority where you live.
Children
Count.do is not for anyone under 16.
Changes
When this page changes, we update the date above. See also the Terms of use.