[Legal](https://vatan.one/legal)

# Privacy notice

Every table that holds anything, what is in it, how long it stays, and that the invoice record holds no prompt text.

VATAN AI LIMITED · company number 15519518 · in effect from 6 October 2026

1. Who is responsible for your data2. What we hold, and for how long3. Why we are allowed to hold it4. Who else sees it5. Data that leaves the UK6. How it is protected7. What you can ask us to do8. The newsletter9. Cookies and browser storage10. Children

### 1. Who is responsible for your data

VATAN AI LIMITED, company number 15519518, registered office 1202 Conington Road, London, England, SE13 7GX, is the data controller for the information described here. Write to privacy@vatan.one about anything on this page.

For your account, your billing and your support messages we are the controller and this notice applies. For the content you send through the API we are a processor acting on your instructions, you are the controller, and the data processing agreement governs it.

### 2. What we hold, and for how long

The table below is the whole of it, each row named by where it is stored.

The metering line matters most. The record that produces your invoice holds token counts and costs. It does not hold the text of your prompt or the answer.

### 3. Why we are allowed to hold it

Account, key, metering and billing data is processed to perform the contract you entered into when you opened an account. Without it we cannot authenticate you, serve a request or invoice for one.

Audit records and abuse controls rest on our legitimate interest. That interest is running a service that is not being attacked, and showing a customer what changed on their account and who changed it.

Billing records are kept for six years to meet a legal obligation under UK company law.

Website analytics and crash reporting rest on our legitimate interest in knowing whether the site works and whether it is being read. Both run on our own servers in Germany, not on a third party’s.

Analytics is OpenPanel, which we run ourselves; the retention table says what it records. It sets no cookie; only a browser that opted out stores a flag.

A crash report holds the type, message and stack of an error, never a form value or an account identifier.

A message sent through the contact form, a demo request or a safety report rests on our legitimate interest in answering the person who wrote. It is used only to reply.

### 4. Who else sees it

The sub-processor register lists every company that can receive data, what each receives and where each is located. Adding a model provider without updating it fails our build.

Model providers receive the content of requests routed to them. Which provider receives a given request is determined by the model you named.

Our infrastructure supplier hosts the database in Germany. Payment details go to Stripe and never reach us. Email we send is transmitted through Amazon Web Services.

Analytics and crash reporting are not on that list, because both run on our own servers.

We do not sell data, and we do not share it for advertising.

### 5. Data that leaves the UK

Some of it does, and here is exactly which. Model inference to providers in the United States and in France. Payment processing to Stripe in the United States and Ireland. DNS, inbound email routing and storage of media generated in the chat to Cloudflare in the United States. Outbound email through Amazon Web Services in Sydney, Australia. Hosting is in Germany.

For transfers to countries the UK has found adequate, which includes the European Economic Area, adequacy is the basis. For the United States and Australia we rely on the data protection terms in each supplier’s own contract, which incorporate the standard clauses those suppliers publish.

We have not signed a bespoke transfer agreement with any of them and we have not carried out a documented transfer risk assessment. If your own compliance process requires one, say so before you start and we will tell you honestly where we are.

### 6. How it is protected

Traffic is encrypted in transit. Passwords are stored as scrypt hashes, and session tokens and API key secrets as SHA-256 hashes, so a copy of our database is not a set of working credentials.

Every tenant-scoped table has row-level security enabled in the database, so a query that does not name a tenant returns nothing rather than everything. The database has no route to the internet.

What we do not have, because a security review asks first: no ISO/IEC 27001, no SOC 2, no commissioned penetration test, no hardware security module, no cyber insurance. Backups are encrypted and copied offsite every hour and every day, and a restore from them was rehearsed on 4 October 2026.

### 7. What you can ask us to do

You can ask us for a copy of your data, or for it in a portable form. You can ask us to correct it, to delete it, or to restrict or stop a particular use.

The console does the two most common ones without asking us: you can export your usage and your ledger, and deleting your account deletes it.

We will answer a request within one month. If you are not satisfied you can complain to the Information Commissioner’s Office at ico.org.uk, which is the UK supervisory authority.

### 8. The newsletter

If you subscribe on the blog, we hold your email address and any name you give. We also record when you asked, when you confirmed, the wording you agreed to, the page you used and your status.

We keep a log of every email we send you, including the confirmation email.

The lawful basis is your consent. We send nothing but the confirmation email until you press the link in it.

The confirmation link stops working after 7 days. An address nobody confirms is deleted 30 days after it was last requested.

Every email has a link to unsubscribe, which takes effect at once. We then delete your name and keep the address, the consent record and the log, so we never write to you again.

### 9. Cookies and browser storage

Two cookies, both strictly necessary. vatan_session keeps you signed in for 30 days or until you sign out. vatan_connection_oauth lasts ten minutes, only while a connection signs in.

Local storage in your browser is kept until you clear it. vatan-storage-notice records that you dismissed the storage notice, and vatan.theme your light or dark choice.

vatan.chat.v2 holds a copy of your Assistant conversations, so the screen reads them without waiting for the network. The conversations themselves are kept in your workspace; the retention table above says who can read them and for how long.

Pictures and recordings you attach to a turn are the exception: they are held in this browser only and are never uploaded with the conversation.

Also in local storage: vatan.jobs.seen-failures, failed jobs you have seen; vatan.knowledge.availableBytes, a memory estimate for a quality run; vatan.drawer names, panel sizes; and which sections you left open.

Session storage, cleared when the tab closes: vatan.widgets.new, an unsaved widget draft; vatan_chunk_reload, so the page reloads once after we release an update.

### 10. Children

The service is not for people under 18 and we do not knowingly hold data about a child. Tell us at privacy@vatan.one if you believe we do.

### What is held, table by table

Named by the database table it lives in, so a reviewer can check every claim.

| Data | What it holds | How long |
| Account and workspace identity.people, identity.tenants | Email address, workspace name, the time the account was created and whether the address has been confirmed. A password is stored only as a scrypt hash; accounts created through Google or GitHub have no password at all. | Until the account is deleted. |
| Sessions and API keys identity.sessions, routing.keys | A SHA-256 hash of each session token and of each API key secret, never the value itself. A key secret is shown once at creation and cannot be recovered from us. | Sessions until they expire or are revoked. Keys until revoked or the account is deleted. |
| Request metering routing.usage | The request id, the model, token counts, latency, cost, status and time. Any labels you sent with the request, and your own id for an end user if you sent one. When the gateway refuses a request, its own one-sentence reason. It does NOT hold the prompt, the completion or a provider’s error text. | For as long as the account exists, unless you set 30, 90 or 365 days on the account screen. |
| Route attempts routing.attempts | For a request that walked a route: each model tried, in order, with the status, latency and the error sentence the provider returned. A provider error sentence can quote part of a request, so this is treated as content. | Indefinitely at present. |
| Cached completions routing.response_cache | The full text of a completion. It is off unless a request opts in with the x-vatan-cache header, and the entry then expires after the caller’s chosen time. An image generated in the chat is also a completion and is stored; it has its own row below. | 300 seconds by default, capped at 24 hours, then expired. |
| Media generated in the chat routing.media, and a private Cloudflare R2 bucket | An image a model generated for you, and a record of which model made it, how large it is and when. The bucket is private and has no public address. The bytes are reached only through the control plane, behind your session. A picture belonging to another workspace is not readable with its address. The prompt that produced it is NOT stored. | Until you delete it, or until the account is deleted. There is no expiry. Deleting it removes the bytes too. |
| Assistant conversations, projects and saved prompts assistant.conversations, assistant.projects, assistant.prompts | What you and the model said in the Assistant, in order, with the model that answered and what each tool was asked. This includes what you ask a bot as a linked member. Readable by you alone, or your workspace while shared, with no copy made. A project holds a name and the standing instructions every conversation in it follows. A saved prompt holds its text. Pictures and recordings you attach are NOT stored here; they stay in the browser you attached them in. | Until you delete it, or until the account is deleted. There is no expiry. Deleting a conversation removes it from this store and from every browser it was open in, and deletes the pictures it drew. |
| Batches routing.batches, routing.batch_items, routing.batch_blobs, R2 | Each request in a batch, its answer, its cost and whether it failed. Files that answers produce are kept as bytes; answers to Google file batches, in R2. | Until the account is deleted; answers in R2, 30 days. Answer files, 7 days after the batch. |
| Uploaded batch files routing.batch_files, and a private Cloudflare R2 bucket in the EU | A file of requests you uploaded to run as a batch. It holds your prompt text. The database keeps only its name, size, line count and a digest. A file can be 2,000 MB, one line 5 MB, and a workspace 25 GB. | 30 days by default, and you can choose 1 hour to 30 days at upload. An hourly job then takes the bytes out of the bucket. Deleting a file, or deleting the account, removes the bytes after any unsent batch is sent. |
| Saved prompts routing.prompts | Whatever the customer chose to save as a reusable template, which may include personal data if they put it there. | Until deleted by the customer. |
| Agent runs automation.runs, automation.steps | Its question and answer. The first 4,000 characters of each model answer and tool result, and the exact model turns so an interrupted run can continue. | The exact model turns are cleared 90 days after the run ends. The rest stays until the account is deleted. |
| Workflow runs started from the console or with an API key automation.runs, automation.steps | Its question, any earlier turns, its answer, and what each step was given and gave. For a file sent with it, only the file's name, type and size. A run started with record set to false holds none of that text: only its steps, timings, model and cost. A queued run that named an end user holds your id for them. | Deleted 90 days after the run ends, with its question, answer and step text. |
| Files sent with a workflow run A private Cloudflare R2 bucket, with only each file's name, type and size in automation.runs | A file sent with a run through the API or a console test, kept only for the run to read. A channel's file is read in memory, or on the server's disk if over 8 MB, unless its bot saves files for the group (below). | Deleted when the run ends, and within about an hour if that delete fails. A run waiting for somebody to approve a step keeps its files until it continues. |
| Workflow runs through a published widget automation.runs, automation.steps | Which steps ran, how long each took, the model, the cost, and any error with the visitor's words removed. No visitor text and no IP address. | Deleted 30 days after the run ends. It never held visitor text. |
| Workflow runs through a messaging channel automation.runs, automation.steps | A linked member's run keeps what a console run keeps; a public bot's keeps no sender text. | Deleted 30 days after the run ends. |
| Kept conversations assistant.conversation_turns | Only when switched on for a widget, bot or console and API runs, which say so. Messages, replies (a member's typed reply too) and the sender's id, name and handle, encrypted per workspace and masked first where set to. Any thumbs or mark on a reply. | Deleted after the 7, 30, 90 or 365 days chosen for that widget or channel, or kept until deleted. A visitor can delete their own at any time. Backups hold a deleted row for up to 100 days. |
| Group recordings assistant.conversation_turns | Only on a bot set to record, in a group where a linked member has used it. Every message there, said to the bot or not: who sent it, when, the group and the words. A file only as a label, such as "(photo)", with a document's file name, unless the bot keeps files too. Encrypted per workspace. Unless set not to, the bot posts a notice once, after it starts recording there. Members who can read conversations see them. A linked member can ask the bot about them in that group, and the model answering reads them. Nobody else can get them through the bot. | Until deleted, unless whoever manages the bot chooses 7, 30, 90 or 365 days. They are the workspace's record of its client conversations. Disconnecting the bot keeps them. Delete this person or deleting the account removes them. Backups hold a deleted row for up to 100 days. |
| Files saved in a group A private Cloudflare R2 bucket, and assistant.chat_files | Only on a bot set to save files: a file a linked member sends it, or any file sent in a group it records with files kept. Its name, type, size and who saved or sent it. Never put in Knowledge. | For the days set when it was saved, 90 unless changed. Deleted sooner on disconnect, account deletion, or Delete this person for whoever saved or sent it. Retried if it fails. |
| Group notes, promises, reminders and contacts assistant.chat_facts, chat_todos, chat_reminders, chat_contacts | What a linked member asks the bot to keep about a chat. Notes, promises with dates, reminders and who gets them. A contact's name, company, email and time zone. Encrypted per workspace, but not dates or zones. A drafted follow-up is emailed to the member who asked, not kept. Reminders and a weekly digest of contacts and promises are emailed, also to listed addresses outside the workspace. | Notes and contacts 365 days, and promises and reminders 30 days after they close, unless the bot sets otherwise. All go when the bot is disconnected or the account deleted. Delete this person removes reminders to them, promises recorded against them as a member on that bot, and cards or reminders with an address of theirs we hold. Otherwise only their recorded messages go. Notes stay. Backups hold a deleted row for up to 100 days. |
| Groups a bot is in, and alerts assistant.channel_chats, governance.audit | Each group a linked member used the bot in: its name, when, and when it was told about recording. An alert to members names a topic, the group and the sender, never their words. | Groups until the bot is disconnected. An alert's audit line as the audit row says. |
| Widget visitor details assistant.widget_visitors, assistant.visitor_links, assistant.visitor_codes | Only when a widget asks: the name, email, company and phone a visitor gave, encrypted. Whether they confirmed the email, and any consent to updates with its time and wording. An emailed code, hashed. | Deleted with their conversation, or by Delete this person or Forget me. A code goes within a day. |
| Tables tables.tables, tables.rows, tables.access | The rows of a table you made or imported, and who it is shared with. Table cells are stored as plain text, not encrypted, so they can be searched, counted and summed. Workspace isolation and an encrypted offsite backup protect them. | A table keeps its rows until you delete them, the table or the account. A table set to keep rows for some days deletes older ones. A row that belongs to a person goes with Delete this person. |
| Staff lists assistant.staff, assistant.staff_settings | People your workflows message who do not sign in: name, phone, email, team, manager, language and time zone. Once they connect, their Telegram id and name. Plain text, so it can be searched. The notice they are shown. | Until the person or the account is deleted. Unlinking forgets their Telegram account. Backups hold a deleted row for up to 100 days. |
| Files kept with a table row A private Cloudflare R2 bucket, and tables.row_files | Only when a workflow saving a row is set to keep files: the voice note, photo or video the run came with, its name, type and size. | For the days the workflow or the table sets, else as long as the row. Deleted with the row, Delete this person or the account. |
| Questions waiting for a reply automation.run_waits, automation.approval_asks | Who a workflow asked, how and when; any yes or no; the reminder and thank-you it sends; an emailed request and its link's hash. Replies stay with the run. | Deleted 7 days after the reply comes or the wait ends. |
| Messages to a bot being answered assistant.channel_inbox | Each message to a bot, encrypted, until it is answered, whether or not the bot keeps conversations. | Deleted once answered, within a day. A backup taken meanwhile may hold it for up to 100 days. |
| Requests for a person assistant.handovers, assistant.conversation_pauses, assistant.conversation_threads | Which widget or bot a person was asked for on, when, and who answered; a pause on that bot; when a bot conversation began. Hashes and dates, no message text. | Deleted 30 days after it was asked. A pause and a start date go within a day. |
| Questions copied from conversations assistant.knowledge_todos, automation.scenarios | A question a member copied from a kept conversation into Knowledge or a test, as plain text. | Deleted 90 days after it was added. A saved test stays until removed. Delete this person removes both. |
| Conversation results assistant.conversation_results, assistant.outcome_tags | For each widget or bot conversation: its turns, any handover, any 1 to 5 rating and its outcome tag. No message text, and the person only as a hash. | Erased with the workspace. Delete this person removes theirs. |
| Text messages sent platform.sms_messages | Each text a workflow or identity check sent through your own SMS provider: when, its status and cost, and the number masked. Not the words. | Deleted after 90 days. |
| Payment links a workflow made automation.payment_waits | The amount, the payment provider’s reference for it, whether it was paid, and the name of the secret holding your merchant id. No card and no payer. | Deleted 7 days after it is paid or the link lapses. |
| Emails a workflow sent platform.workflow_emails | Each email a Send an email block sent: when, its status, and how many people and files. Not the addresses or the words. | Deleted after 90 days. |
| One-time codes assistant.identity_challenges | A keyed hash of the code, never the digits, and the paused run, encrypted. Once confirmed, only that and a hash of where it went. | A code lasts up to 30 minutes and a confirmation up to 24 hours, as the workflow sets. Deleted within an hour after. |
| Campaign contact lists automation.campaigns, automation.campaign_contacts, automation.campaign_suppressions | The list you uploaded and each person's send status. The opt-out list keeps a hash and the last four characters, never the address. | Erased 7, 30 or 90 days after the campaign ends, as you chose, or sooner. The opt-out list stays while the workspace does. |
| Writes to your systems systems.write_backs, systems.sync_runs, systems.hook_receipts | Each record a workflow writes to your systems, encrypted until it lands or is given up on; then only the method, path and status. When each sync ran, and incoming webhook keys. | A body for about four hours at most. Write and sync records, 30 days. Webhook keys, 7 days. |
| Scheduler log platform.job_runs | The job's name, its times, whether it succeeded and a one-line summary. No request content. | Deleted 30 days after the job ran. |
| Webhooks platform.webhooks, platform.webhook_deliveries, platform.webhook_inbox_requests | Your endpoint address and signing secret, each delivery attempt with what your endpoint answered, and the body we sent so it can be retried. It holds message text only where a webhook is set to carry it. A Vatan test receiver keeps what reached it. | A sent body for 7 days. A test receiver keeps its last 100 requests. The rest until you delete the webhook or the account. |
| Billing commerce.ledger, commerce.balances | Amounts, dates and a Stripe reference. Card details are never received by us and are held by Stripe. | Six years, which is the period UK company law expects accounting records to be retained for. |
| Support and enquiries governance.support_requests, governance.enquiries | What the sender wrote, their name, email address and company if given, and the reason they chose. This includes demo requests and safety reports. A confirmation goes to the sender and a notification to us, by email. | Until deleted on request. |
| Newsletter subscribers commerce.contacts, commerce.messages | Email address, any name given, when consent was asked for and confirmed, the wording agreed to, the page used, the status, and a log of each email sent. | Until you unsubscribe, when the name is deleted and the rest is kept so we never write again. An unconfirmed address is deleted after 30 days. |
| Website analytics OpenPanel, self-hosted | A page path and title, the referring site, browser and device details, an approximate location from the IP address, and a device and session identifier derived on our server. Whether the IP address belongs to a hosting or cloud company. Campaign tags (utm_, src, ref) are kept; no other query string or account identifier. | On our own infrastructure. No deletion schedule is set, so it is kept until we delete it. |
| Knowledge collections knowledge.documents, knowledge.chunks_1536, in its own database | Documents you add: the text taken from a file, a page or a paste, its search chunks and their embeddings, and a page’s address. From a connected source, also who wrote or last edited it. The original file is not kept. | Until you delete the document or its collection, or until the workspace is erased when the account is deleted. |
| Questions asked of Knowledge knowledge.asks, knowledge.answers, in its own database | A question, who asked it and which documents answered. For the Assistant, also its answer, the passages it cited, and a vote and note if the asker gave one. A search sent with record set to false keeps no question. | Deleted after 13 months, or when the account is deleted. |
| Crash reports GlitchTip, self-hosted | The type, message and stack of an error. Never a request body, a header, a query string, a prompt or a completion, and a test enforces that. | On our own infrastructure, for as long as the issue is open. |
| Audit governance.audit | Who did what to an account and when, including actions taken by an operator, so a customer can see a change that was not theirs. | Indefinitely. It exists to be looked back at. |

Source: https://vatan.one/legal/privacy
