AttnomSolutions
Loading page
Bringing in the next surface without the heavy transition shell.
Loading page
Bringing in the next surface without the heavy transition shell.
Privacy
This page now shows what Attnom stores, why it exists, where it lives, how long it stays, and what a privacy request should look like as a real product flow.
Retention rules
Keep only what is needed for delivery, support, billing integrity, and platform security.
Storage model
Account, project, payment, and consent data live in separate operational lanes rather than one vague bucket.
Contact route
Privacy requests route through direct contact with enough account, project, or payment context to review safely.
Data-handling map
Each card below explains one data lane so a person can see the operational reason for collection before they scroll through detailed terms.
Data lane
Purpose
Sign-in, recovery, workspace continuity, 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 route
Use /contact with the account email and the route where the issue happened.
Data lane
Purpose
Scope work, price delivery, coordinate approvals, and track project continuity.
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 route
Use /contact or the workspace route with a project reference.
Data lane
Purpose
Verify deposits, reconcile orders, and preserve financial continuity around 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 route
Use /contact with the payment reference, route, and wallet or order context.
Data lane
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 route
Use /contact and specify whether the change is export, deletion, or consent-related.
Console preview
The preview below explains what a self-serve privacy console should show even when a human still reviews the request before final release.
Export request
Preview mode
Export request
A self-serve export flow should let 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 route 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
Send the request through direct contact with enough account, project, or payment context for Attnom to verify the right records before anything is released or removed.