Privacy
A data-handling map, not a legal wall.
This page now shows what Attnom stores, why it exists, where it lives, how long it stays, and what a privacy request looks like as a real product flow.
Last updated
Retention rules
Keep only what is needed for delivery, support, billing integrity, and platform security.
Storage model
Account, project, payment, and consent data are grouped by purpose instead of pushed into one vague bucket.
Contact path
Privacy requests go through direct contact with enough account, project, or payment context to review safely.
Data-handling map
Purpose, retention, storage, and contact path at a glance.
Each card below explains one data type so a person can see the operational reason for collection before they scroll through detailed terms.
Data type
Account and identity
Purpose
Sign-in, account recovery, saved work, and support verification.
Retention
Held while the account is active, then retained only as long as needed for security, recovery, or record integrity.
Storage
Primary application records and transactional email logs.
Contact path
Use /contact with the account email and the page or product where the issue happened.
Data type
Project and delivery data
Purpose
Scope work, prepare quotes, coordinate approvals, and track active projects.
Retention
Kept for the life of the engagement and for follow-through where delivery, support, or dispute review requires it.
Storage
Workspace, project, and delivery records inside the Attnom application stack.
Contact path
Use /contact or workspace with a project reference.
Data type
Payments and receipts
Purpose
Verify deposits, reconcile orders, and keep financial records with live work.
Retention
Retained for billing integrity, reconciliation, and fraud or charge review where applicable.
Storage
Payment records, receipt references, wallet addresses, and blockchain confirmation details.
Contact path
Use /contact with the payment reference, wallet, and order context.
Data type
Messaging and consent
Purpose
Respond to inquiries, manage newsletter preferences, and preserve necessary operational notices.
Retention
Preference state is retained until changed; support communications are kept while the thread remains operationally relevant.
Storage
Consent logs, support messages, and notification preferences.
Contact path
Use /contact and specify whether the change is export, deletion, or consent-related.
Cookies and local storage
What this site keeps on your device
No tracking and no analytics, so there is no cookie banner. This is the full list, by the name your browser shows. Clearing site data in your browser removes all of it.
- Session cookieCookie
- Keeps you signed in. Set only when you sign in, and scripts on the page cannot read it.
attnom-auth-token- Google sign-inCookie
- Only while you sign in with Google. They tie the answer from Google to this browser and remember where to send you after. Gone within ten minutes, and scripts on the page cannot read them.
attnom-google-stateattnom-google-nonceattnom-google-verifierattnom-google-nextattnom-google-mfa- Signed-in nameLocal storage
- Lets the menu show your account before the server answers. Cleared when you sign out.
attnom-auth-session- Prism device idCookie
- A random id, so a Prism watchlist saved without an account comes back. Kept for a year.
attnom-prism-device- AppearanceLocal storage
- Your light or dark choice.
attnom-appearance- Install promptLocal storage
- When you closed the install card or started a download, so it does not ask again too soon.
attnom-app-install-dismissed-atattnom-app-installedattnom-native-download-started-at- Prism case listLocal storage
- The assets you kept on the board. It never leaves this device unless you export it. The second name is an older copy, read only when the first is missing.
attnom-prism-case-assets:v2attnom-prism-case-assets:v1- Prism board densityLocal storage
- How tightly the board lists rows, per scope.
attnom.prism.board.density.- Tool settingsLocal storage
- The options you last used in a tool, so it opens the way you left it.
attnom-tool-preferences:v1attnom-tool-platform:- Unsent draftsLocal storage
- A build request you have not sent yet, and where to return after you sign in.
attnom-labs-request-draft-v2attnom-account-intent- Academy reading progressLocal storage
- Which Academy chapters you read to the end, and the one you opened last, so the books can show your place. No account, and it never leaves this device.
attnom-academy-progress:v1- Saved Academy chaptersOffline cache
- Academy pages you opened, so they read without a connection.
attnom-academy-v1- Offline pagesOffline cache
- The offline page, the apps page, privacy, terms, the app manifest and the logo, so they open without a connection. The name ends in the release it came with, and an older one is removed when the site updates.
attnom-shell-- Site scripts and stylesOffline cache
- The files that draw the pages, so saved pages still look right offline. It keeps a limited number.
attnom-static-v2- ImagesOffline cache
- Logos and pictures the site showed you, checked again each time they are used. It keeps a limited number.
attnom-images-v1
Console preview
Preview export, deletion, and consent changes like product flows.
The preview below explains what a self-serve privacy console shows even when a human still reviews the request before final release.
Export request
Preview the account-data export before a human review completes it.
Preview mode
Export request
A self-serve export flow lets someone choose the scope, submit the request, and understand what comes back before Attnom releases any bundle.
Flow steps
Choose the scope: account profile, workspace activity, project history, payment references, or preference state.
Submit the request with the account email and enough product context to match the right records.
Attnom reviews identity and packages the export before release.
What the user sees
Guardrails
Passwords, secrets, and internal security notes are not exported.
Records tied to third-party privacy or fraud review can be redacted where necessary.
Privacy model
Need a privacy, export, deletion, or consent request?
Use the dedicated deletion request path with enough account, project, or payment context for Attnom to verify the right records before anything is released or removed.