Privacy policy
Last updated
This describes what tokaido. stores, where it lives, and how to get rid of it. It is written to be read rather than to be defensible.
1.What we store
The documents you create and save: their text, configuration, brand settings and version history. Your account details — name, email address, and the organisation you belong to. Usage records: which documents were generated and exported, and when.
A document you generate but never save is not written to disk. It exists in the render pipeline for as long as the request takes and is then gone.
2.Where it lives, and who can reach it
Every record belongs to exactly one tenant, and isolation is enforced by the database itself through row-level security rather than by application code remembering to filter. A query that omits the tenant filter returns nothing; it does not return someone else’s document.
Uploaded assets and exported files are held in object storage under the same tenant boundary.
3.What the model sees
Generating a document sends your brief, and any source material you supply, to a large language model provider for processing. That material is used to produce your document and for nothing else. We do not use your content to train models.
If a document must never leave your infrastructure, do not generate it here — use the ingestion path instead, which parses files locally without a model call.
5.Deleting your data
You can delete any document at any time. Deleting a tenant erases its documents, versions, assets, brands, presets, API keys, sessions and users, and removes its stored files. The erasure is recorded — what was deleted and when — because a deletion nobody can evidence is not much use to you in an audit.
Write to hello@tokaido.online to request erasure, a copy of your data, or a correction.
6.Changes
If this policy changes materially we will say so before the change takes effect rather than moving the date at the top and hoping. The date at the top is when this version was published.