Privacy policy
Last updated 30 August 2026
A book manuscript is about as personal as data gets, so this policy tries to be specific rather than reassuring. It sets out exactly what leaves our servers, who it goes to, how long we keep it, and what you can do about it.
1. What this covers
This policy explains what InkWrit ("we", "us", "our"), operated by ModernTyrTech, a Buxton Holdings company, collects when you use inkwrit.ai, why, and what we do and do not do with it. It covers your account, the books you write, and the technical data generated by using the product. By using InkWrit you agree to this policy.
The short version: your manuscript is yours, we do not train AI models on it, we do not sell data to anyone, and you can export everything and leave at any time.
2. What we collect
We do not collect payment card details. Card data goes directly to our payment processor and never reaches our servers.
- Account information — your email address, display name and authentication details. If you sign in with Google, we receive your name and email address from Google; we never see your Google password.
- Content you create — manuscripts, chapters, outlines, story bible entries, style profiles, uploaded writing samples, uploaded and generated images, and the publishing details you set for a book, such as author and publisher credits.
- Your API key, if you use the bring-your-own-key plan — stored encrypted, used only to run your own requests, never displayed again after you save it, and deleted with your account.
- Usage and billing records — your plan and any token purchases, the AI jobs you run, the model used and the tokens charged. This is what makes your ledger itemised.
- Technical data — the standard information a web application receives, such as browser type, approximate location derived from IP address, and error diagnostics.
3. How we use it
- To run the product — storing your work, assembling context for your AI requests, generating exports.
- To meter and bill token usage accurately, and to show you where every token went.
- To fulfil add-on purchases, including issuing commercial licence certificates and processing ISBN orders.
- To keep the service secure and to diagnose faults.
- To contact you about your account, a purchase, or a material change to the service.
4. AI providers and what gets sent to them
Generating text and images requires sending content to third-party AI providers. When you run a job, the assembled context — which may include your style profile, exemplar passages, relevant story bible entries, chapter summaries and the text you are working on — is transmitted to the provider so they can return a result.
Text generation uses Anthropic. Image generation uses Flux models run on Replicate. We do not use your manuscripts to train models, and we access these providers on API terms that do not permit training on submitted content. Providers may retain content briefly for abuse monitoring under their own policies.
If you use the bring-your-own-key plan, your writing requests are sent to Anthropic using your own key, under your own agreement with Anthropic.
AI calls are made from our servers. Provider API keys are never exposed to your browser.
5. Who else handles your data
We do not sell personal data, and we do not "sell" or "share" personal information as those terms are defined in California privacy law. We do not share your manuscripts with anyone except as needed to run the service for you.
- Stripe, our payment processor, for plan subscriptions, token purchases, add-ons and marketplace payments to editors. Stripe handles card details; we receive only a confirmation and a transaction reference.
- Anthropic and Replicate, the AI providers described above.
- Google Cloud, which hosts the service and stores your account and your work in the United States.
- Google, for sign-in when you choose to continue with Google.
- Cloudflare, which provides DNS for our domains.
- Bowker, if you order an ISBN: we file your book's registration details, such as title, author and publisher, to register it on your behalf.
- Error monitoring and operational tooling, used to diagnose faults.
6. Storage and retention
Your account and content are stored on Google Cloud infrastructure in the United States and retained while your account is open, because a story bible you set up three years ago should still be there when you come back to it.
If you use InkWrit from outside the United States, your data is transferred to and processed in the United States. Our processors handle it under contractual terms that require them to protect it, and this policy applies wherever the data is processed.
When you delete a book, it is removed from your workspace and purged from our systems within a reasonable operational window, including from backups on their normal rotation.
Billing and purchase records are kept for as long as tax and accounting law requires, even after an account closes.
7. Your rights
Where a legal basis for processing is required, ours are straightforward: we process your account and content because the contract with you requires it, billing records because the law requires them, and diagnostics under our legitimate interest in running a working, secure service. Anything optional, such as the bring-your-own-key plan, happens only because you chose it.
Depending on where you live, you may have rights to access, correct, export or delete your personal data, to object to certain processing, or to complain to a data protection authority. We honour these requests regardless of where you are.
Export is not a request you need to make: PDF, EPUB and DOCX export is built into the product, free and unlimited, at any time, and Settings includes a one-click download of your data as a single file.
Deletion is also self-serve: closing your account from Settings cancels any active subscription, deletes your content and stored files, removes your stored API key, and deletes your login. Billing records we must keep for tax and accounting law are retained; operational audit records are kept in anonymised form.
- Access — ask for a copy of the personal data we hold about you.
- Correction — fix anything inaccurate in your account.
- Deletion — close your account and have your content removed.
- Portability — export your books in standard formats whenever you like.
8. Security and breach notification
Data is encrypted in transit, stored API keys are encrypted at rest, and access to production systems is restricted. No online service can promise perfect security, so we do not.
If a breach of our systems affects your personal data, we will notify you without undue delay, consistent with the notification laws that apply, and tell you what happened, what data was involved and what we are doing about it.
10. Children
InkWrit is not directed to children and may not be used by anyone under 13. We do not knowingly collect personal data from children under 13; if we learn that we have, we delete it. Writing books for children is very much encouraged; writing them from a child's account is not supported.
11. Changes to this policy
We will update this policy as the product develops. Material changes will be notified to account holders, and the date at the top of this page always reflects the current version.
12. Contact
Privacy questions and data requests go to privacy@inkwrit.ai. General support is at support@inkwrit.ai.
Questions about this document? Write to privacy@inkwrit.ai.