Privacy

TypeGroove is a reading game. It keeps the little it needs to give you your progress back, and nothing else. There is no advertising here, no tracking across other sites, no profile of you built anywhere, and nothing is sold or shared with anyone.

There are two measurements, named below and both worth being plain about: a count of page views, and a report when something breaks. Neither stores anything in your browser to recognise you by, and neither follows you anywhere else.

What is kept

Your account. An email address, and — if you sign in with Google — the account identifier Google returns along with the name and picture on your Google profile. This is held by Supabase, which runs the database and the sign-in.

Your display name. Taken from your Google profile, or from the part of your email before the @. You can change it. It is public: it is what the daily board shows.

Your runs. For each passage you finish: a score, words per minute, accuracy, timing consistency, how long it took, and the date. Your best for each passage and your daily streak are kept alongside.

Texts you upload. Title, author and the text itself. These are private to your account and are not shown to anyone else.

What is not kept

Your keystrokes. While you read, the app records what you typed and when, because a score has to be checked rather than trusted. That record is sent once, replayed against the passage on the server to confirm the run was really typed, and then dropped. Only the resulting numbers are written down. The sequence of keys you pressed is never stored.

There is no password to keep, either. Signing in is a link sent to your email, or Google — neither leaves a password here to lose.

What other people can see

Two things, and only these: your display name, and the runs you post to the daily board. That board is public and readable without an account, which is the point of it. Practice runs, everything you upload, your streak and your email are private to your account.

What is measured

Page views. Vercel Analytics counts visits, which page, which country, roughly what kind of device, and which site you arrived from. It does this without cookies and without storing an identifier in your browser, so it cannot tell today’s visitor from tomorrow’s. Nothing else is sent to it — no record of what you did on the page, only that the page was opened.

Whether people come back. This is the only thing worth knowing about a daily, and it is worked out from the runs already described above rather than by watching anyone: the dates on your own runs, counted. It never leaves this site.

Crashes. When something goes wrong, Sentry is sent the error and the line of code it happened on. It is deliberately not sent the contents of the request, your cookies, the address you were on, or any of the variables in scope — which is to say not the keylog described above, not your session, and not the page you were reading.

Who else is involved

Supabase stores the database and handles sign-in. Vercel hosts the site and, like any web host, sees the requests your browser makes. Google is involved only if you choose to sign in with it. Resend delivers sign-in emails if you use the email link instead. Vercel Analytics counts page views and Sentry receives crashes, both as described above.

One more worth naming because it happens whether or not you have an account: the site loads its typefaces from Google Fonts, so your browser requests them from Google, and Google sees your IP address when it does. Nothing else on the page reaches a third party.

Deleting it

Ask and the account goes, along with the runs, the streak and anything uploaded. It is a real delete, not a flag — the database removes everything attached to the account.

Asking about any of this

Write to hello@typegroove.com.