Scope of this notice
This notice covers the public Tanya marketing site and its waitlist. It does not describe an active managed assistant: public account creation, public chat, checkout, payments, transactional email, and external channel effects are source-disabled during WAVE-F0.
The repository also contains alpha components for self-hosting. If you run them, you or the operator you choose controls that deployment and must document its own storage, providers, retention, security, and legal basis.
Data the public site currently handles
- Waitlist request: the email address you submit, a random confirmation token, verification state, and timestamps. The request remains unverified while confirmation email is disabled and does not create an account or grant access.
- Abuse prevention: the waitlist route reads the request IP supplied by the hosting layer for an in-memory hourly rate limit. The application does not write that IP into the waitlist record; hosting infrastructure may maintain its own request logs.
- Analytics preference: the site can remember a consent choice locally, but external analytics dispatch is source-disabled during WAVE-F0. A PostHog key, a granted choice, or a test override cannot reactivate transmission.
Data the public site does not currently collect
- No public hosted account, password, workspace, or API key.
- No managed conversation or cross-surface memory record.
- No card data, Stripe customer id, subscription, or paid usage.
- No public-chat prompt sent to an LLM provider through the disabled marketing endpoint.
Third parties and self-hosted providers
A configured hosting or database provider may process the waitlist data needed to serve and store your request. PostHog, Stripe, and Resend modules exist in the repository but are not active public analytics, payment, or email processors during WAVE-F0.
A self-hosted Tanya deployment can be configured to call model or tool providers chosen by its operator. Those providers may receive the data that operator sends to them. Review that deployment's configuration and each provider's terms before using it with personal or sensitive information.
The repository's processor inventory is available at docs/legal/PROCESSORS.md. Inclusion there documents a possible integration; it is not a claim that every listed service is currently active.
Retention and your rights
Waitlist entries are still handled by email. Ask what waitlist data is held, request correction or deletion, withdraw a request, or exercise other applicable data-protection rights by emailing legal@usetanya.com. There is no self-service control on this public site.
Existing accounts have a self-service panel in the dashboard, under Settings: it exports the data held for the account and requests its erasure. Erasure spans the SaaS surfaces and the Brain service, and it is fail-closed — see the Terms of Service, section 7, for what happens when a boundary is not configured.
Retention periods
The table of retention periods is published in the repository at docs/legal/RETENTION.md. It is read from the code — migrations, auto-migrated tables, and the purge jobs actually scheduled — not from an intention, and a repository check fails if a table is missing from it.
We publish its shape here rather than a copy of its 88 rows, because a copy would drift from the file the check guards. Of those 88 tables: 15 are bounded by a scheduled purge that runs without anyone asking; 44 are cleared only when an erasure is requested, which is not a duration; 27 carry no written duration at all; and 2 are unbounded for a reason written next to them. We would rather publish that count than describe a schedule the code does not yet enforce.
Those periods are operating parameters. Whether they are the right ones in law — legal basis, enforceable duration, how people are informed — is a separate review, and nothing on this page is legal advice.
Browser storage
The marketing site stores the analytics consent decision locally in your browser. Analytics remains off when consent is unset or denied. No public managed-account session is created while account creation is disabled.
Contact
Privacy questions and rights requests: legal@usetanya.com. For a public code issue that does not contain personal data, use the project repository. Do not post personal data in a public issue.