ARCHIVE
Your information.
Clearly explained.
Guest use, username accounts, saved collections and community credit each work differently. Here is what the archive saves and what you control.
You can explore the archive and keep a collection in your browser without an account. A username account adds saves across devices and lets you submit references for review. It uses a passkey, without asking for an email address or password.
Use your skate handle.
Creating a username account does not require an email address.
The app saves your username, an internal account identifier, passkey public credentials, passkey labels and dates needed to manage the account. It saves one-way hashes for account sessions and recovery codes.
Your device or passkey provider keeps the private key and handles its unlock check. The archive does not receive your device PIN or biometric unlock data.
Treat your username as an identifier, not a secret. A username by itself cannot sign someone in.
Browse without an account.
Guest measurements, hunt lists, collections and personal additions save in this browser. Guest collection data is not synchronized to an account until you explicitly choose to import it after signing in.
Browser data can be cleared or accessed by someone else who uses the same browser. Device saves are not a separately encrypted account vault.
Export a backup before clearing browser data or changing devices. Keep exported files private; they contain the information you entered.
Your records stay separate.
When signed in, the app saves your measurements, hunt list, collection notes, planned liners and personal skate additions under your account identifier. These records are not published to other visitors.
The app also keeps a browser copy for interrupted connections. Signing out ends server access; it does not erase browser copies or backups you downloaded.
Account data is stored for the app to read and synchronize. This is not end-to-end encrypted storage. Avoid putting passwords, recovery codes or unrelated sensitive information in collection notes.
Choose what is public.
Community references go to the owner for review. Pending submissions are visible to the submitting account and the owner, rather than the public board.
You can enter a skate handle and opt in to public contributor credit. The archive does not automatically publish your sign-in email or real name.
A reviewed reference can publish its title, text, source link and approved credit. Check what you type or link before submitting; free-text fields can contain information you choose to share.
Keep another way in.
Recovery codes appear once when issued. The server keeps their hashes, so it cannot show the original codes again. Add another passkey and keep recovery codes somewhere private, separate from your main device.
Account recovery replaces all old passkeys, ends old sessions and issues new recovery codes. The saved collection remains with the account.
There is no email-reset link for username accounts. Losing every passkey and recovery code can mean losing access. Signing out all sessions revokes server sessions, but cannot erase files or browser copies on other devices.
Earlier accounts still exist.
Existing ChatGPT sign-in is a separate option for earlier collections and owner tools. That identity service supplies account information, including an email address, to the archive server. This sign-in is not required to create a username account.
The application does not automatically save the authenticated email in its collection or contribution records or use it as a public contributor name. The owner’s access is checked separately.
Copying an earlier collection to a username account is an explicit action. Existing username-account entries take priority. The earlier account and its contribution history remain separate; copying does not permanently link the accounts.
Usage without collection details.
The archive counts page loads, approximate visits, broad referral categories and public skate-record opens. A random tab-session code groups visits separately from account and collection data.
The app’s visitor statistics do not include sign-in emails, saved measurements, notes, search text or personal skate additions. Those counts are visible to the site owner.
The app respects Do Not Track and Global Privacy Control signals for its visitor statistics.
Limits on repeated attempts.
To limit repeated account requests, the app keeps short-lived abuse counters derived from network information. Those app-level counters store hashed values instead of raw IP addresses.
Hosting, identity and passkey providers may process technical information under their own policies. The descriptions here explain this application’s behavior, not every provider’s logging or device storage.
Passkeys reduce password-related risks, but no sign-in method removes every risk. Keep your browser, devices and recovery information protected.
Use the level you need.
Stay a guest for browsing and device saves. Create a username account for account synchronization and reference submissions. Choose public credit separately when sharing a contribution.