Last updated: May 16, 2026
Note: In case of any discrepancy between the English and translated versions, the English version shall prevail.
Tatsulok is built for professional teams whose work is confidential by default. Each request you send is processed by a model provider and forgotten the moment the response returns — no retention, no training, no human review. Your workspace itself — threads, files, memory — stays with you across every surface. The sections below explain exactly what is sent, what is kept, and what is never sent.
Account information you provide: name, email, and OAuth identifiers from your sign-in provider. Workspace content you choose to keep: files, threads, memory, settings, and citations — needed to make the same Tatsu available on every surface. Operational data: request IDs, latency, and error codes — no prompt or workspace content. Anonymous product analytics: only when you allow it. We do not sell your data.
We share your data only with the processors that operate the service: OpenRouter for model routing under a zero-retention contract — OpenRouter dispatches each request to an upstream model provider (currently Groq for Groq-served routes) and is contractually required to use only upstream providers that also do not retain content; one request, then dropped — operational metadata such as token counts and latency may be retained by OpenRouter for billing and abuse prevention, but prompts and completions are not; Cloudflare for file storage, embeddings, request handling, and bot protection (AES-256 at rest for R2; Cloudflare-managed encryption for Vectorize; Workers invocation metadata retained up to 7 days for operational logs); Convex for application state (AES-256 at rest); WorkOS for authentication (industry-standard encryption per WorkOS documentation); Resend for transactional email such as invitations and security notices; and PostHog for anonymous analytics — only when you allow it, with workspace content never sent and on-screen content masked in any session recording. We do not sell or rent your data, and we share it with law enforcement only when legally required.
Every AI request runs through providers under contracts that do not retain your prompts, attachments, or responses after processing; do not use your inputs to train, fine-tune, or improve any model; do not allow human review of your content by the provider; and do not publish your prompts or completions to public datasets. We enforce this at the routing layer, not by trust. We disable every non-compliant endpoint at the organization level — paid endpoints that may train, free endpoints that may train, free endpoints that may publish prompts, and any provider-side product-improvement program based on user inputs. The current provider path is OpenRouter, which dispatches to upstream model providers (currently Groq for Groq-served routes); we update this list when it changes.
TLS in transit on every connection. AES-256 at rest for files in Cloudflare R2 and application data in Convex; processors whose encryption algorithm is not publicly documented (Cloudflare Vectorize, WorkOS, OpenRouter, Groq, PostHog) use their own provider-managed encryption-at-rest. Authentication via WorkOS, with OAuth and SAML support for enterprise. Engineer access to production data is least-privilege, audit-logged, and limited to operational tasks — incident response, and investigation of feedback you have submitted, with only the context you chose to attach. Data residency: today our application database (Convex) and authentication (WorkOS) are US-region only; customers in Japan, the EU, and other jurisdictions should know that data is processed outside their local region. Cloudflare and OpenRouter route through the closest edge point of presence. No system is perfectly secure; we work to keep yours close.
We use a small number of essential cookies for sign-in sessions and to remember your preferences (language, theme, sidebar state). Anonymous product analytics — pageviews and product events through PostHog (US Cloud) — run only when you explicitly allow them on the cookie banner; no content from your workspace is ever included. PostHog session recording, when enabled, masks all input fields and on-screen text on the client before any data is sent (see https://posthog.com/docs/session-replay/privacy). You can change your analytics decision at any time from Settings, and you can manage all cookies through your browser's standard controls.
You can export your full workspace from Settings → Data, delete specific items or your entire workspace at any time, change the model and provider for your requests, and revoke analytics consent. If you are in a jurisdiction with statutory privacy rights (GDPR, CCPA, PIPEDA, APPI, and others), you can exercise them by contacting legal@tatsulok.com. We respond within applicable statutory windows.
Tatsulok is not directed at children under 13 and does not knowingly collect personal information from them. If you believe a child has provided us with personal information, contact us and we will delete it.
We update this policy as the platform evolves. Material changes are announced in-product before they take effect. The current version is always at https://www.tatsulok.com/legal/privacy and mirrored at docs/privacy.md in our repository.
For privacy questions, contact legal@tatsulok.com.