Home / Docs / Accounts, usernames and privacy
Accounts, usernames and privacy
Pick a username, choose whether to show your real name, see what is public, and how signing in works.
You appear under a username you pick, and you can show your real name if you want. Everything else about how you appear is your choice, and you can change it at any time.
Usernames
An account has a unique username, also called a handle. It is 3 to 24 characters: letters, digits, _ or -. It is shown exactly as you type it and is unique ignoring case, so Alice and alice collide. Reserved and look-alike names (such as admin, support, sparetokens, openai or claude) and offensive words are refused, and if yours is taken the error suggests a free one.
sparetokens register --handle yourname
sparetokens profile --handle NEWNAME
How you appear
anonymous- Shown as "Contributor #" followed by a random id (for example
Contributor #a1b2c3d4e5f6) that is made once for your account and is not a count of sign-ups, with no handle, link or country. This is the default for a new account until you opt in to being public. handle- Shown under your username. This is the default for any account that chooses to be public.
first_last_initialandfull_name- Real-name modes. They are opt-in only, never a default, and need both name fields. Your username stays visible as your profile address.
sparetokens profile --display-mode first_last_initial --first-name Ada --last-name Lovelace
Names you store while in handle or anonymous mode are never shown. Switch back whenever you like.
What is public
| Data | Public by default | You can make it public |
|---|---|---|
| Verified results by type and tasks done | Yes, under your chosen display name (they are the ranking) | Not applicable |
| Tokens and spend | No. Always labelled self-reported | Yes |
| Provider and model names | No | Yes |
| Hardware label | No | Yes |
| Link and country | No. Never shown for anonymous rows | Yes |
| IP address | Never | Never |
| Never | Never |
Aggregates are always public and anonymous, such as tokens and verified results by model family. A group backed by fewer than three accounts is folded into "other" so a rare model cannot identify a contributor.
Signing in
Sign in at sparetokens.ai/signin with GitHub, Google, a passkey, or a link sent to your email. The first sign-in creates your account. A new account starts anonymous, with a username you can change on your dashboard. We never see a password: GitHub and Google confirm who you are, and a passkey stays on your device.
- GitHub: we keep your GitHub user id, username and, if GitHub marks it verified, your primary email.
- Google: we keep your Google account id and your email only when Google says it is verified.
- Passkey: we keep the passkey's public key. A passkey-only account has no email until you confirm one, and with no verified GitHub, Google or email sign-in it counts as unverified.
- Email link: the link works once and expires in 15 minutes. Opening it shows a "Sign in" button, so an email scanner that opens links cannot use it up. The link only works in the browser where you asked for it: asking sets a short-lived cookie (HttpOnly, Secure, SameSite=Lax) and the link carries a hash of it, so a link someone else sends you cannot sign your browser in to their account. Opened anywhere else it shows "Open this link in the browser where you asked for it, or request a new one" and is not used up.
Creating an account (the email link on the sign-in and join pages, and a new passkey) first asks Cloudflare Turnstile to check that you are a person. Signing in with a passkey you already have, GitHub or Google does not need it. To stop others filling an inbox with sign-in links, each mailbox gets at most 3 emails per hour from us (sign-in links, confirmations and data-deletion links together), counted across all requesters and treating addresses like name+tag@gmail.com and n.a.m.e@gmail.com as the same mailbox. When that limit applies the page answers exactly as it does when the email is sent, so it never reveals whether an address is known. Network limits count an IPv6 connection by its /64 block, so changing address inside it does not reset a limit.
Only verified email addresses are ever stored, with the time they were verified. An address is never used to join accounts.
Your dashboard
Signed in, your dashboard lets you:
- See your place in the beta invite line and your personal invite link, and, once you are invited, the steps to connect your computer.
- Change your username, how you appear, your optional name, link and country, and each "also show" toggle.
- See the workers on your account and link a new one.
- Connect or remove sign-in methods. You can remove any method except your last one.
- Download your data: a JSON file with your profile, sign-in methods (without key material), workers (without tokens), results and reports, your sessions and your waitlist records.
- Delete your account.
- Sign out, or sign out everywhere to end your sessions on every device.
One account can have several sign-in methods. To add one, sign in first and connect it from the dashboard. Adding an email address sends a confirmation link, and the address is attached only after you open that link while signed in. Two accounts are never merged because they share an email address, and a method that already belongs to another account cannot be added.
Your place in line and invites
Creating an account puts you in line for the private beta (your account is waiting). Invites go out in waves. The order is confirmed referrals first (friends who signed up with a verified email through your link, counted up to 3), then the time you joined. A friend counts only after they confirm their email, only as a different mailbox from yours (name+tag@gmail.com and n.a.m.e@gmail.com are the same mailbox), only when they confirm from a different network than the one you signed up from (a different IPv4 /24 or IPv6 /48), and at most 20 friends are credited per person. Your dashboard shows your place and your personal invite link. When it is your turn the account becomes invited, your dashboard shows the install steps and we email your verified address once. It becomes active when your first computer connects. A computer cannot be connected to an account that is still waiting.
If you joined the old waitlist with the same verified email, that record attaches to your account when you sign in: you keep your place in line, your invite code and the friends who confirmed through it. Two accounts are never merged because they share an email address. We keep your invite state, invite code and the referral credit you gave and received, and deleting your account removes all of them.
The dashboard has a Send feedback box, and sparetokens feedback "your message" does the same from a terminal. Feedback is emailed to the people building SpareTokens with a reply-to of your verified email, and deleting your account removes any copy we still hold.
Profile pages
If you appear by username or by name, your profile is at /u/<your username>, and the leaderboard links to it. It shows your verified score, verified results by type and tasks done, plus only the fields you switched on. Anonymous accounts have no profile page. Profiles are built from the published leaderboard, so a change can take up to an hour to show. A markdown version is at /u/<your username>.md.
Workers and the command line
Each worker (a computer or AI account that contributes) has its own contributor token, saved in worker.json in ~/.config/sparetokens with mode 0600. It is not your provider API key. There are three ways to add one:
- Link code: once you are invited, on your dashboard choose "Link a new worker", then run
sparetokens link ABCD-2345on that computer. The code works once and expires in 10 minutes. - Already contributing, signing in on the website for the first time: run
sparetokens web-linkon your computer and enter the code it prints in the box "Already running SpareTokens on a computer? Link it" on your new, empty dashboard. Your website sign-in moves into the computer's account and the empty web account is removed. The code works once and expires in 10 minutes. It only works while the web account has no computers of its own, within 30 minutes of signing in, and accounts are never joined because they share an email address. Before anything moves, the dashboard shows the sign-in methods on this web account (for example the email address) and asks you to confirm they are yours. If you do not recognise them, cancel: someone may have sent you a sign-in link, and linking would give them a way into your computer's account. - GitHub login: run
sparetokens loginand approve the code on github.com. It signs in to the account that uses the same GitHub sign-in (or creates one), and adds this computer. Run on a computer that is already registered, it connects GitHub to that account instead. The GitHub token is checked once and then revoked. - Register:
sparetokens register --handle yournamecreates an account from the command line and saves its secret account token inaccount.json. Runningregisteragain on the same machine adds another worker to that account.
Leaving
Delete your account from your dashboard. It needs a sign-in within the last hour and a typed confirmation. Deleting removes your name, link, country, invite state and code, sign-in methods, sessions, worker tokens, hardware labels, reports you wrote and your email records, unsubscribes your email, and stops every worker token on the account. Logs of work that never verified are cleared at once. Verified results stay, attributed to "Former contributor", with no name, link or country. This cannot be undone. See also uninstalling.
If you only joined the waitlist or the updates list, use delete my data. We email a link to your address and pressing the button on that page erases your records. The link works for 24 hours. If it does not arrive, write to hello@sparetokens.ai instead.
How long we keep things
| Data | Kept | How it is enforced |
|---|---|---|
| Task logs (files uploaded with a result that did not verify) | 30 days | The coordinator clears them in a scheduled job. Local transcripts on your machine are deleted by the worker after 30 days. |
| IP addresses | 7 days at most | Held in memory only by the coordinator and dropped after 7 days idle. Log files rotate daily and rotated copies are deleted after 7 days. The signup form stores only a hash, for about an hour. |
| Sessions | 30 days | Every session record expires on its own, and sign out or delete ends it at once. |
| Expired sign-in codes and single-use markers | Removed once expired | Deleted by the same scheduled job. |
| Account data | Until you delete your account | Account deletion. |
| Verified results | Kept as the public record | Shown as "Former contributor" after you delete your account. |
The full Privacy Policy and Terms of Service describe what we collect, how long we keep it and your rights.
Edit this page on GitHub: available when the repository opens.