Privacy

Version privacy-v3 · Effective

TPS is run by ARATEKNA CORPORATION PTY LTD (ACN 690 338 991), an Australian company. Australian privacy law — the Privacy Act 1988 (Cth) and its Australian Privacy Principles — is the law we’re built around, and this page follows its shape. If you’re in the EU or UK, the annexes at the end add what your law gives you on top. The honest headline hasn’t changed: most of what you give us is public by design.

Who we are, and where to complain

Questions and requests: hello@tokenspersecond.ai. If you think we’ve mishandled your personal information, tell us — we respond within 30 days. If we don’t resolve it, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au). EU and UK users have their own routes, listed in the annexes.

What we collect

Your account: your email address (private — never shown publicly); your handle (public — you can’t rename it yourself, but if it identifies you we can replace it with a pseudonym: see “Your rights”); optionally a bio, website link, and avatar (all public); and your birth year — or, where your sign-in provider can confirm you’re over 18, just that signal instead of the year (private; why we ask is under “If you’re under 18”).

Your submissions: benchmark results and hardware details, any evidence files you attach — including screenshots — and any notes you write on a run. All public.

Your community activity: votes you cast, flags you raise and the notes you attach to them, and anything you write in appeal threads. Flag notes and appeal posts are public; appeal threads and moderation records are kept as a public record — removable where the law requires it or where a complaint we receive is upheld, and marked in place when removed.

Technical: standard server logs (IP address, browser info), kept 30 days for security and abuse prevention. When you accept our terms, we also record the IP address and browser details of that acceptance; these are deleted after one year. Analytics is separate and consent-based — see “Cookies and analytics”.

Email preferences: whether you’ve opted into our digest, and your unsubscribe status.

Reports and moderation: if you report something at /report, or something you posted is reported, we keep the report, our decision and the reasons in a private log.

Things worth knowing before you post

  • Screenshots show more than you think. A desktop capture can include your username, file paths, and other windows. Crop before you upload — evidence files are public.
  • Your account’s internal ID (a UUID) is publicly visible in API responses and some URLs, alongside your handle.
  • Appeal threads are a public record. What you write in an appeal stays public after the appeal ends, even if you later delete your account (it’s shown as from a deleted account).

What we use your information for

Running TPS (accounts, publishing runs, the leaderboard). Keeping the leaderboard trustworthy (moderation, flags, appeals, abuse prevention, handling reports). Licensing the dataset — its own purpose, described next. Email — account messages, moderation notices about your own runs, notices when our terms change, and, only if you opt in, a digest, with a working unsubscribe on everything that isn’t purely account plumbing. Analytics, with your consent — see “Cookies and analytics”.

The dataset

TPS may license its database of runs to third parties (see the Data Terms). What’s in it: public run data with submitter handles, and nothing that isn’t already visible on the public site. What’s never in it: your email address or any private account details; your votes, flag notes, and appeal posts (excluded by construction); runs submitted by under-18s (excluded by construction). And we don’t license the dataset for AI training at all — submitters haven’t granted us that right.

Our licence terms bind licensees to handle the data to the standards of the Australian Privacy Principles, never to try to identify who is behind a handle, never to contact you, and never to pass the data on as an open dataset. Every month we send licensees a list of runs that have been withdrawn or whose owner has deleted their account; licensees must apply it to their copies within 30 days. A licensee that doesn’t need to know who submitted a run can receive the data with handles left out.

If you’d rather your runs weren’t in licensed exports at all: email hello@tokenspersecond.ai and we’ll exclude them from all future exports, no reason needed. They stay on the public leaderboard — this doesn’t withdraw them, it just keeps them out of the product.

Overseas disclosure

Some recipients of TPS data are likely to be outside Australia. Dataset licensees will most plausibly be in the United States, the UK, and the EU. Our hosting provider stores data in Australia, and our analytics provider (Google) processes data in the United States. Australian law generally keeps us accountable for what overseas recipients do with personal information we disclose to them, and our contracts require licensees and providers to handle it to the standards of the Australian Privacy Principles. Current providers: Supabase and Vercel (hosting, Sydney), Resend (email delivery, United States), Google (analytics).

Security, and if something goes wrong

Data is encrypted in transit. Access to your private details (email, birth year) is limited to the people who need it to run the site. Consent and moderation records are append-only. No online service can promise perfect security, and we won’t. If a data breach happens that’s likely to cause you serious harm, we’ll notify you and the OAIC under the Notifiable Data Breaches scheme, promptly.

Your rights

To delete your account, go to Settings → Delete account. We email you a link; opening it takes you to a confirm page, and nothing is deleted until you press ‘Delete my account’ there. To access your data, get a copy of it, or correct it, email hello@tokenspersecond.ai. We handle requests within 30 days.

Withdrawing a run (from the run page) removes it from the site and all future dataset exports, and deletes its evidence files — immediately from live systems, from backups within 35 days. It’s the strongest removal action we have. Licensees who already have the run are told in our next monthly notice and must remove it from their copies within 30 days. Moderation records and appeal threads about a withdrawn run remain — see the Terms.

Deleting your account removes your handle, profile, and email, and deletes your evidence files — immediately from live systems, from backups within 35 days. Your structured results stay on the leaderboard and in the dataset; here is exactly what a row keeps after deletion, so you can judge it for yourself: the run date, hardware details, the numbers, and the rating — no handle, no email, no link to your account, and we don’t try to re-identify rows (our licences forbid licensees trying, too). Licensees who already have your rows with your handle on them are told in our next monthly notice and must strip the handle within 30 days. Where your handle was typed inside appeal threads or moderation notes, we scrub the exact handle and replace it with a neutral pseudonym as best we can — quotes, misspellings, and paraphrases written by others can survive in that free text. Deletion is final once you confirm: there’s no grace period and we can’t restore your profile afterwards. Want a run gone entirely? Withdraw it first.

If we close your account, the same removals happen. If we closed it for repeat infringement, we keep a scrambled (hashed) copy of the email address for 24 months so the same address can’t open a new account; that hash can’t be turned back into your address.

Handles: if your handle itself identifies you, email us — we’ll replace it with a pseudonym across TPS, and the change goes to licensees in the next monthly notice.

If your information is on TPS and you don’t have an account

Your name in someone else’s screenshot, your details in an appeal post — you don’t need an account to do something about it. Use /report: we assess every report within 7 days, and where it’s upheld or the law requires, we remove or redact the content and mark the removal in place. Access, correction, and erasure requests from people without accounts go through the same route or hello@tokenspersecond.ai.

If you’re under 18

TPS accounts are for people 16 and over. We ask your birth year at sign-up (or accept your sign-in provider’s word that you’re over 18) for two reasons: runs submitted by under-18s are excluded from the dataset we license to others, and we owe younger users extra care in how the site treats them — our approach is guided by a children’s data protection impact assessment [reference — to be completed]. If we learn an account holder is under 16, we close the account and delete its personal information (the same backup window applies), and we keep a record that we did.

Cookies and analytics

Signing in sets an essential session cookie — the site doesn’t work without it, and it needs no consent. Analytics is different: we use Google Analytics, and it sets no cookies and collects nothing until you consent. Everyone sees a consent choice before any analytics runs; if you say no, the site works identically. The full list of what’s set and for how long lives in the cookie notice.

Retention

Your account data: until you delete your account, plus the 35-day backup window. Public run data: indefinitely, under the Data Terms. Server logs: 30 days. Analytics data: 14 months. Reports and moderation decisions: while the content they concern remains published or licensed, and then for as long afterwards as a legal claim about them could still be brought. Hashed email addresses of accounts closed for repeat infringement: 24 months. Consent records (which terms versions you accepted, when): we keep these while the runs they cover remain published or licensed, and then for as long afterwards as a legal claim about them could still be brought — nothing is kept longer than it has a job to do. The IP address and browser details attached to each acceptance are deleted after one year.

For EU users (GDPR) — annexe

Our legal bases, per purpose: running the service you signed up for — contract. Keeping the leaderboard trustworthy — legitimate interests. Licensing the dataset — legitimate interests, supported by a balancing assessment, with the objection route above (“The dataset”) available to you at any time, no justification needed; we also tell you about that right, on its own, in the first email we send you. The digest, and analytics cookies — consent, withdrawable as easily as it was given.

You have rights of access, rectification, erasure, restriction, portability, and objection — start any of them at hello@tokenspersecond.ai. Two honest caveats: erasure works forward — we remove, and strip identifying details, going forward, and we tell licensees in our next monthly notice so they can do the same within 30 days, but dataset copies delivered before then will have carried your handle until that notice is applied; and rows stripped of your handle and account link stay in the dataset — “Deleting your account” above describes exactly what they contain. Australia has no EU adequacy decision; where the GDPR requires a transfer mechanism, our contracts use the EU Standard Contractual Clauses. EU representative (Article 27): none appointed — TPS does not currently offer its service in the EU. You can complain to your local supervisory authority.

For UK users (UK GDPR) — annexe

Everything in the EU annexe applies to you under UK law, with these differences: the supervisory authority is the Information Commissioner’s Office (ico.org.uk); transfers from the UK to Australia rest on the UK International Data Transfer Addendum where required; and we have no UK representative appointed — TPS does not currently offer its service in the UK. If you’re under 18, the “If you’re under 18” section above reflects the standards of the ICO’s Age Appropriate Design Code.

Changes

If this policy changes materially, we’ll announce it on the site before it takes effect.

Privacy · tokenspersecond.ai