Privacy
Last updated 27 August 2026
TICK has no accounts, no sign-up, no cookies and no trackers. It does not know who you are, and it is not built to find out.
What is stored on your device
One thing: a browser localStorage entry called
tick.ar, holding your last twenty Aim Ratings so the
results screen can show you a trend. It is a list of numbers. It
never leaves your browser and is never sent anywhere. Clearing site
data for this domain deletes it.
No cookies are set. No analytics, advertising, fingerprinting or third-party scripts are loaded — the page ships its own code and nothing else.
What the server sees while you play
A match runs over a WebSocket. For the life of that connection the server holds, in memory only:
- your network connection, including the IP address that any internet connection necessarily carries;
- a callsign the server generates for you — two dictionary words and four digits. You do not supply it, and it is not tied to you across sessions;
- the inputs you send during the match, and the score derived from them.
The application writes nothing to disk. There is no database, no profile and no match history: when the connection closes, everything above is dropped. Whatever infrastructure the server happens to run on may keep its own connection logs, as any web host does; that sits below this application and outside its control.
Other players
Other people in your match see your generated callsign and your in-game score. That is the whole of it — there is nothing else about you for them to see.
Children
TICK collects no personal information from anyone, of any age, and nothing in it is directed at children as a marketing audience.
Changes
If this policy changes, the date at the top changes with it. TICK is open source, so the change is visible in the repository's history too.
Contact
Questions about any of this: dev [at] playtick.lol.