Public profiles are optional proof pages for selected typing runs. They are not required to play Typearchy and they are not a social network.
Each profile has one durable URL:
https://typearchy.com/u/handle
It shows a handle, useful aggregates from published runs, and at most three pinned runs. The primary pin includes a replayable pace ghost and every pin can launch its reproducible challenge. There are no followers, feeds, comments, reactions, private messages, or public contact details.
Profiles are device-owned. Typearchy does not require email, a password, GitHub, or another identity provider.
- The app creates a random device token and requests a connection code.
- The app opens
typearchy.com/connectwith that short-lived code. - The player claims an available handle.
- The website stores only a hash of the device token.
- The app detects the completed connection automatically. A same-origin claim from the setup page also signs in that browser with its own device token; an existing browser session is left unchanged.
The connection expires after 15 minutes. The raw device token stays in a user-only local file and is never included in a command-line argument. A one-time recovery code is shown after claiming the handle. Recovery works like connecting: the app requests a short-lived recovery session, opens typearchy.com/recover with it, and the player confirms with their handle and recovery code. Recovery rotates the code, revokes previous device access, and connects the new device. No token material ever appears in a URL.
A second device connects without the recovery code. When a browser is already signed in, it can approve an app's connection code on typearchy.com/connect. When the app is connected, choosing Account in browser in History asks the service for a one-time code that lasts ten minutes and opens typearchy.com/connect?browser=CODE; the player confirms there and the browser receives its own device token. Neither path revokes other devices or changes the recovery code.
A connected device can replace a lost recovery code from Account on the website. The old code stops working, every device stays connected, and the account page shows when the code was last replaced.
Profiles can be made private from the app. A private profile and its runs stop appearing publicly immediately, and publishing to it stays available locally.
Disconnecting in the app revokes that device. It does not remove other devices, the profile, or published runs.
Deleting the profile requires a second confirmation in the app. It removes the profile and every public run while preserving all local history.
Nothing uploads automatically. A player must publish each finished run from the result screen or local history. Custom passages cannot be published.
The service accepts only:
- schema and content version
- mode, duration, target label, and reproducible challenge key
- WPM, raw WPM, accuracy, consistency, and error count
- a decimated WPM pace series
- completion time
It never accepts the prompt, typed text, individual keystrokes, correction timing, local mistake history, machine identity, or IP-derived location.
Publishing creates an immutable result URL. The app can pin or unpin that run, copy its URL, or remove the public copy. Removing it keeps the local result.
Profiles allow three pins. The newest pin is the primary run. Its pace ghost is reconstructed from aggregate WPM samples and can be played, paused, or scrubbed. It is not a screen recording and contains no typed text or key events.
Desktop scores are self-reported by an unsandboxed client. Typearchy does not call them verified or cheat-proof. Every receipt identifies the mode, target, duration, accuracy, and challenge so visitors can compare it fairly.
Cloudflare D1 stores profiles, hashed recovery secrets, hashed device tokens, short-lived connections, published runs, pins, and rate-limit counters. Public aggregates are derived from published runs. There is no global player directory.
Handles are case-insensitive, limited to safe ASCII characters, and checked against reserved product and system names. Connection, recovery, and publishing endpoints are rate-limited.