Skip to content

Pre-launch legal draft

Privacy review requirements

This route reserves the production location for an approved privacy notice. It currently documents required subjects and must not be treated as final legal terms.

Not a final privacy policy. Publication requires qualified legal review, named controller/contact details, jurisdictional scope, and verified operational procedures.

Account and billing data

The final notice must describe authentication identifiers, account profile information, Stripe customer/subscription projections, credit and export history, support requests, security logs, purposes, retention, and processors.

Business dataset

The notice must describe source business records, enrichment evidence, correction and opt-out handling, rights and lawful-basis analysis, data recipients, and international considerations where applicable.

Security and rights

The launch version must provide a verified privacy contact, request process, applicable rights, retention/deletion rules, safeguards, subprocessors, incident approach, and effective/change dates.