Privacy
Your manuscript stays yours.
Kaizen R/W keeps your manuscript in your browser. We don't keep a server-side copy of your draft, your marks, or your local dictionary. When you click an AI action, that passage goes through our proxy to the provider you picked, and the response comes back. Hosted plans run on paid commercial API tiers that don't train on inputs.
Passage goes out. Response comes back. Nothing sticks to the proxy.
- Draft text, marks, dictionary entries, scan state, and local settings stay in your browser unless you trigger an AI action.
- If you request access or use account features, KRW may store your email address and account identifiers needed to operate that flow.
- Text only leaves your browser when you ask for a reading, interpretation, or rewrite. The relevant passage and context are sent through KRW's proxy to the provider you chose.
- Hosted free and Pro run on KRW's provider accounts. Bring-your-own-key works on every tier and keeps billing on your side.
Request path
How the request travels.
Your browser
Your draft and revision memory live here first. Nothing leaves until you click an AI action.
KRW proxy
KRW passes the request to the model provider and hands the response back. It's a proxy, not a manuscript vault.
Model provider
Hosted routes run on paid APIs that don't train on inputs by default. Google's paid Gemini API and Anthropic's commercial API both exclude API traffic from training. Their current docs are the source of truth, linked below.
Provider docs
The provider's current documentation is the source of truth.
Policies and models change. If the work is sensitive, read the provider docs before you send it through hosted AI.
- Hosted free uses Google Gemini on Google's paid API. Model docs | API terms
- Pro uses Claude via Anthropic's commercial API. Model docs | Privacy docs
- Bring your own key works on every tier. Your provider bills you directly. Your key stays in your browser and doesn't burn hosted usage. What the provider does with the text is governed by the account and terms on your key.
No manuscript vault.
The data path is short enough to explain.
Your editing stays local-first. If you'd rather pay your provider directly, BYOK works on every tier.