Login

You log in at /login with your access key — a 32-character string of letters and digits issued when your account was created. There is no email address, no password, and no one-time code sent to your inbox.

The login form

Go to statelessid.com/login. The page shows a single input field. Paste your access key into that field exactly as it was issued: 32 lowercase hexadecimal characters, no spaces, no hyphens, no line breaks. Then submit the form.

The system checks whether the key matches an account. If it does, you are forwarded to your dashboard and a session cookie is set in your browser. The session lasts for the duration of your browser session and expires after a period of inactivity. When it expires, you are shown the login form again. Logging in again with the same access key resumes your dashboard without any data loss.

Do not bookmark a dashboard URL and expect to return to it while logged in indefinitely. The session is time-limited by design. Bookmark /login instead and keep your access key in a password manager so you can log in quickly when the session expires.

What your access key looks like

Your access key is exactly 32 characters long. It contains only the digits 0 through 9 and the lowercase letters a through f — hexadecimal notation. It has no hyphens, no spaces, no uppercase letters, and no special characters. An example of the format (not a real key) would be: 3b8e0f1c7a429d65e0f1c7a429d65e3b. Count 32 characters and you have the right length.

The key was issued once, on the page you landed on immediately after a successful checkout. If you saved it correctly, it is in your password manager. If you stored it elsewhere — a text file, a notes app, an email you sent yourself — it should be there too. The key does not change unless you explicitly regenerate it.

Why wrong keys fail silently

When you submit an incorrect access key, the form clears and nothing else happens. There is no error message. The system does not say "wrong key," "account not found," or "try again." This is intentional. Telling a visitor whether a particular key string matches any account on the server is information that can be used for enumeration — systematically testing keys to find valid ones. Silence removes that signal.

The same principle applies to slightly malformed keys. A key with 31 characters, a key with an uppercase letter, a key with a trailing space — all of these produce the same silent form-clear as a completely random string. The absence of a message is not a hint about what went wrong; it is simply the system declining to confirm or deny anything about the submitted string.

If you are certain you are pasting the correct key but login is still failing silently, the issue is almost always a paste artifact: a leading or trailing space, a line break, a smart quote if the key passed through a rich-text editor, or a character that was silently corrupted by a notes app. Paste the key directly from your password manager into the login field, not through any intermediate application.

After a successful login

A successful login takes you directly to your dashboard. If you have one site registered, you land on that site's view. If you have multiple sites, you land on the site list or the most recently viewed site depending on your browser's session state. No email is sent when you log in. No notification appears anywhere else.

Your session cookie holds your dashboard state for this browser on this device. Logging in on a second device or browser does not invalidate the first session. You can have multiple active sessions simultaneously — one on your laptop, one on a desktop — and both will show the same account data.

Troubleshooting

If the login form clears immediately every time you submit, confirm that you are pasting your access key and not your site key. The access key is exactly 32 characters of [0-9a-f]. Your site key is a different string visible in the dashboard settings. The login form accepts only the access key. If the wrong type of key is being submitted, the form will always clear silently.

If you are copying from a terminal or a text editor and the paste includes a trailing newline or space, the submitted string will be longer than 32 characters and will never match any account key. Paste into a plain-text editor first to inspect the raw characters, confirm the length is 32, then copy from there into the login field.

If you cannot remember where you stored your access key and do not have it in a password manager, the recovery path is to regenerate it from the admin panel. See the regenerate article for how that works. There is no email-based password reset — see the email-is-not-login article for why.