tokenstat
homepricingstatshelpsign in
tokenstat
Sync and profiles

Publish a profile, or stay private

György
Reviewed by
György
Updated Jul 30, 2026 3 min

Syncing and publishing are two separate decisions. You can sync several machines into one dashboard and never show anyone, and that is the default: an account is private until you claim a handle and turn publishing on.

Claiming a handle

A handle is the address your profile would live at, tokenstat.ai/yourname. Claiming one does not publish anything by itself, it reserves the name.

The rules, so a rejection is not a mystery:

  • 4 to 32 characters, letters, numbers and dashes
  • No leading or trailing dash, and no double dash
  • Not purely numeric, so a handle can never be confused with an internal id
  • Not on the reserved list, which holds product words, infrastructure names, and anything impersonation-prone
  • Look-alikes of reserved words are refused too: separators are stripped and digit homoglyphs folded, so t0kenstat and token-stat are blocked next to tokenstat

Once set, a handle is fixed for 30 days. That stops churn and name-squatting, and it means a link to a profile keeps working.

Turning publishing on

Publishing needs a handle, and it is a separate switch in your settings. Until you flip it, the profile URL does not resolve for anyone, including you when signed out.

What a published profile shows: your display name, your handle, an optional bio, optional links, and your usage in aggregate, which means totals, model and tool breakdowns, a heatmap, and the cost picture.

What it never shows: project names, file paths, prompts, repository names, or machine names. Those either never left your machine or left as salted hashes whose salt stays local. The detail is in what leaves your machine when you sync.

Going back to private

Flip publishing off. The page stops resolving immediately.

You keep the handle. Going private is not the same as giving up your name, so nothing is released for someone else to take, and turning publishing back on later restores the same URL.

The same principle runs through everything gated by tier: a downgrade stops publishing the things a higher tier allowed, it never deletes them. Your links, layout and theme stay stored and reappear if you upgrade again. Nobody should lose what they typed because a subscription lapsed.

Search engines

A profile is only listed in the sitemap once it has a claimed handle and real data. An empty or unpublished profile carries noindex and is not offered to search engines at all. There is also a separate switch if you want a published profile that people can visit but search engines should not list.

Getting rid of it entirely

From /settings/data:

  • Export everything as JSON, including the data behind the profile
  • Delete the account, which is a real cascade and not a flag on a row

Deleting the hosted account does not touch your local archive. That stays on your disk, where it always was.