Privacy notice
What we collect when you use Oat or write to us, what it is for, who else touches it, and how long it stays.
Last updated 23 September 2026
Who is responsible
The company that operates Oat is the controller for the personal data described here. Its name and address will be stated here once confirmed by counsel. Until then, questions go through the contact page.
What we collect and why
| Data | Where it comes from | What it is for |
|---|---|---|
| Account: name, email address, sign-in method, session | Clerk, when you sign in | Knowing who you are and which workspaces you belong to |
| Workspace content: imported writing, drafts, comments, revision requests, approvals | You and your team, through the desk or a linked chat | Preparing, reviewing and publishing your work; the audit trail |
| Connection data: account name and ID, granted scopes, encrypted tokens, sync times | The provider, when you connect an account | Reading your reporting and publishing to accounts you authorised |
| Messages you send to Oat on WhatsApp or Apple Messages, and your linked number | You, through the provider | Review and approval in a conversation; replies to your questions |
| Access and contact requests: name, email, what you make, site URL, role, message, the page you sent it from | The forms on this site | Deciding whether Oat fits, and replying to you |
| Usage and audit records: who did what, when, to which revision; job states; model usage and cost | Generated by the service | Operating the service, keeping approvals accountable, staying within budget |
| Technical logs: IP address, browser, request path, error details | Vercel and Railway, as requests are served | Security, debugging and keeping the service up |
We do not collect payment details; there is no public billing. We do not buy data about you from anyone. We do not run advertising or analytics tags on this site.
How your writing is used
Your archive and your drafts are used as context for the work Oat prepares for your workspace and for nothing else. They are sent to the configured writer model through the Vercel AI Gateway when a draft is prepared or assessed, and to no one otherwise. We do not use your writing to train models, and the voice rules Oat learns from your corrections are stored in your workspace, shown to you, and reversible.
Messages from WhatsApp and Apple Messages are used for review and replies only and are never fed into lasting model improvement.
Who receives data
The vendors that run parts of Oat are listed on the subprocessors page, with what each one receives. Providers you connect (your site host, Google, Meta, LinkedIn, HeyGen, Kapso for WhatsApp, Apple) receive what their connection needs and are governed by their own terms. We do not sell personal data and we do not share it with advertisers.
Some vendors operate outside the United Kingdom and the European Economic Area. The transfer mechanism for each will be recorded on the subprocessors page once confirmed by counsel.
How long we keep it
| Data | Kept for |
|---|---|
| Workspace content and audit records | Until you delete the piece, the source or the workspace. Deleted data leaves active systems within 7 days and backups within 30. A tombstone without any content remains until the affected backups expire. |
| Audit events | 90 days after the event, or until the workspace is deleted, whichever is first |
| Redacted diagnostics | 30 days |
| Raw transport payloads (webhook bodies, provider responses) | 7 days |
| Connection tokens | Until you disconnect, when the ciphertext is deleted at once |
| Access and contact requests | Until we have replied and the matter is closed, and at most 12 months after our last reply; sooner if you ask |
| Account records in Clerk | Until you delete your account or ask us to |
| Concierge support access | Expires after 7 days unless renewed explicitly |
Your rights
You can ask for a copy of the personal data we hold about you, ask us to correct it, ask us to delete it, or object to a use of it. Owners can export a workspace as Markdown or HTML from the desk and delete it outright. For anything else, write through the contact page; we answer within a month. If you are in the UK or the EEA you can also complain to your data protection authority.
Cookies
Oat sets session cookies from Clerk to keep you signed in and a short-lived cookie during an account connection. Nothing else. The cookies page lists them.
Security
The security page describes the controls in plain words: workspace isolation enforced in the database, encrypted connections, approvals bound to exact revisions, and models that never hold credentials.
Changes
When this notice changes, the date at the top changes with it and the difference is described here. Material changes are also sent to workspace Owners by email.