BypassWriter
We do not store your drafts
In shortDrafts and rewrites have nowhere to live in our database. The limit: the rewriting provider receives your text to do the rewrite.
Your draft passes through our server, is sent to our rewriting provider, and is let go. On our side it is not written to a database, not written to a log, and not kept in a cache to warm up later.
This is not a retention period set to zero — it is the absence of anywhere to put it. There is no column in our database that can hold a draft or a rewrite, which is a stronger guarantee than a policy, because a policy can be changed by editing a sentence and this would take a schema change.
It also means we cannot train on your writing, hand it to anyone, or sell it as an asset later. Not as a promise about our intentions — we simply do not have it.
The limit of that claim is worth stating plainly, because it is the part a promise like this usually leaves out: it covers what BypassWriter holds. Performing the rewrite means sending your text to the provider named in the next section but one, and what they do with it in transit is governed by their terms, not by our schema.
What we do store
In shortAn account record, one row per rewrite with word counts, model, tone and timing, and a daily counter. Never the writing itself.
An account record: the user id our authentication provider gives us, which plan you are on, and where that plan came from.
A row for each rewrite: how many words went in, how many came out, which model and tone were used, whether it succeeded, how long it took, and when. That is what a daily limit has to count in order to be enforced rather than merely stated.
A daily counter: how many requests you have used today, so the limit resets at the same moment for everyone.
Note what is not in that list. No draft, no rewrite, no titles, no subject matter. A row says that a rewrite of 400 words happened at a certain time. It says nothing about what it was about.
Who else touches your data
In shortOnly the rewriting provider sees your text. Clerk, Dodo Payments, Supabase and Vercel see your account, billing or requests, never the writing.
The rewriting provider is the only one of these that sees what you write. Performing a rewrite means sending your text to them, and the result is sent back to be scored so the workspace can show you a reading. This happens on our server, over the wire, for the length of the request. We do not choose what they retain, so we do not state it on their behalf: their own terms govern that, and if you need a guarantee about it in writing, ask us before you paste anything sensitive.
Clerk handles sign-in and holds your email address and login details. We read your account id from them; we do not hold your password.
Dodo Payments handles payments and subscriptions. They hold billing details, including card details. We never receive card numbers; we receive signed billing events tied to the account selected before checkout.
Supabase hosts the database described above, and Vercel hosts and serves the site.
Each of these has their own privacy policy covering the part they hold. Only the rewriting provider receives the text itself; the others see your account, your billing or the request, never the writing.
Your choices
In shortSign out any time, cancel from the billing portal, or email support to delete your account and usage rows.
You can sign out of any session from your account screen, and you can cancel a paid plan at any time from the billing portal.
If you want your account and its usage rows deleted, write to support@bypasswriter.com and we will delete them. There is no drafts archive to also delete, which is the point of the first section on this page.
How to reach us
In shortQuestions, access requests and deletion requests all go to support.
Questions about this policy, requests to see or delete what we hold, and anything else on this page go to support@bypasswriter.com.
Changes to this policy
In shortThe date changes when the policy does. If we ever start storing your writing, it will be said plainly and in advance.
If this policy changes, the date at the top changes with it. If a future version of BypassWriter ever starts storing what you write, that will be said here plainly and in advance, not softened into a sentence that could be read either way.