Privacy
Where your manuscript actually lives
Last updated 23 August 2026.
Your writing stays in your browser
Today, your books and chapters never leave the device you wrote them on. They are stored in your browser’s local storage. We cannot read them, we do not have a copy, and we could not produce one if asked.
The consequences are yours to weigh, and both directions matter:
- Nobody else can see your manuscript, including us.
- Clearing your browser data deletes your work, permanently. There is no backup on our side to restore from.
- Your work does not follow you to another device or another browser.
- Export regularly. Markdown export exists for exactly this reason.
What we do collect
- Feedback you deliberately send. When you rate a page or write a note, that text and the page you were on are recorded. Nothing is sent unless you submit it.
- An account, only if you sign in. Signing in with Google gives us your email address, name and profile picture. If you do not sign in, no account and no identifier are created — you are not tracked anonymously either.
- Standard web server logs held by our hosting provider — IP address, time, page requested — used to keep the site running and detect abuse.
What we do not do
- No advertising, and no sale of anything to anyone.
- No third-party analytics or tracking pixels.
- Your writing is never used to train a model — ours or anyone else’s.
- Writing you provide to teach the product your voice judges your output and never primes it. That is enforced by which service is permitted to read it, not by policy alone.
If you sign in
Signing in with Google shares your email address and name with us, so an account can exist and your work can follow you between devices. We do not receive your Google password and have no access to your Google account beyond that basic profile.
We do not receive your Google password and have no access to your account beyond that basic profile. Signing in does not back up or sync your work. Your manuscript stays in this browser, on this device, and clearing your browser data still deletes it permanently — an account does not change that.
Who is responsible
riter app is owned and operated by AlphaHive Limited, a company registered in the United Kingdom, which is the data controller. Contact us through the support page.
| Data | Basis | Kept |
|---|---|---|
| Your manuscript | Not processed by us — it stays in your browser | Until you delete it |
| Account — name, email, picture | Contract — you asked us to create an account | Until you ask us to delete it |
| Feedback you send | Legitimate interest — improving the product | 24 months |
| Server logs | Legitimate interest — running the site, detecting abuse | As held by Firebase Hosting |
Data is processed in the UK, the EU and the US, because Firebase Hosting is a Google service with a global network.
Your rights
Under UK and EU data protection law you can ask for a copy of your data, ask for it to be corrected or deleted, and object to how it is used. For your manuscript, you do not need to ask us — it is in your browser, you can export it, and clearing site data deletes it.
For feedback you have submitted, or an account once accounts exist, contact us through the support page.
If you are unhappy with how we handle your data, you can complain to a supervisory authority. In the UK that is the Information Commissioner’s Office at ico.org.uk; in the EU it is the authority in your country of residence. You do not have to raise it with us first, though it is usually faster.
Changes
This page changes when the product does — particularly when accounts and server-side storage arrive, which will materially change where your work lives. The date at the top is the version.