Privacy

The short version

We keep as little as we can. If you're signed in, the text you check or rewrite on the website stays in your history for 30 days so you can reopen it, and you can delete it any time. Saved documents keep a record of how they were written, as counts and occasional snapshots, never keystrokes, which you can pause or delete. API calls keep only numbers. Like most sites, we log each request with your IP address, an approximate location and your browser; the IP is dropped after 30 days and the rest after 90. We don't sell your data or show ads.

Who we are

ZeroLLM is made by Rad Soft, Inc. You can reach us at hello@radsoftinc.com.

What we keep

• Your Google account basics. When you sign in with Google we store your name, email address and profile picture. Sign-in sessions also record the IP address and browser they were started from.
• Website history, for 30 days. When you're signed in, text you explicitly check or rewrite on the website is saved with its score, and which rewrite model wrote it, so you can reopen it. Items older than 30 days are deleted automatically, and you can delete one item or your whole history from your account page at any time. The checks that run in the background while you type aren't saved.
• Documents. Documents you save, and each pass you make on them, stay until you delete them.
• Writing records for saved documents. While you edit a saved document, we record how it's being written so its writing receipt can show it: every few seconds, how many characters were typed, pasted, deleted or rewritten by ZeroLLM, how long you were active, the size of each paste, and which parts of the current text came from where. We also keep occasional snapshots of the text, thinned out over time, for the receipt's replay; they can include text you later deleted. We never record individual keystrokes. A record stays with its document until you delete it or the document, and you can pause recording for any document from its receipt.
• Shared receipts. A writing receipt is private until you share it. A share link lets anyone who has it see the receipt, and the replay if you include it, without signing in. It stops working as soon as you turn it off. To show the detector's verdict, a shared receipt checks the current text when it has changed, which counts toward your checking allowance.
• Your writing sample. If you save a sample of your own writing for My voice, we keep that one sample until you replace or delete it in your account. It's used only as a style reference for your own rewrites when you pick My voice.
• API requests, numbers only. For calls made with an API key we keep the word count, score, label and rewrite model, never the text.
• Usage counts. We count the words you use each month to apply your plan's limits. For visitors who aren't signed in, we keep a daily count per IP address for up to two days.
• A short-lived cache. Detection results are cached for about an hour, keyed by a fingerprint of the text, so identical text isn't scored twice.
• A request log, for 90 days. Every request to ZeroLLM, from the website, the API, the Chrome extension or the Docs add-on, signed in or not, is logged with: when it happened, which kind of request it was (the route, never the text you sent, and never the ids or share links in it), whether it worked and how long it took, your IP address, the approximate location the IP points to (country, region and city, looked up on our own servers), your browser, operating system and kind of device as your browser reports them, the website that sent you if it says, and which app made the request. If you're signed in or using an API key, the log also notes your account, which key (never the key itself), your plan and how many words the request covered. We use it to see where people come from, to keep the service working and to look into abuse.
• Your IP address goes after 30 days. After 30 days the IP address is removed from the request log for good; the approximate location stays with the rest of the entry until it's deleted at 90 days. Only Rad Soft can see the log.

Page analytics

On zerollm.app we use PostHog, a product analytics service, to count which pages are viewed, how long people stay, and a short list of named actions: starting and finishing a sign-in, running a check or a rewrite, picking a rewrite option, creating a batch, an API key or a share link, saving a writing sample, and opening the API docs. Each action carries only counts and settings, such as the number of words or the style you picked, never the text itself. We don't record clicks, sessions or the screen, and share links are removed from page addresses before anything is sent.

PostHog keeps a random identifier in your browser's local storage to tell visits apart, and sees your IP address when your browser sends it events, which it can use for an approximate location. When you sign in we link your visits to your account id and plan; your email address isn't sent, except for Rad Soft's own staff accounts. The events go through zerollm.app on their way to PostHog's servers in the US.

Who processes your text

• Rewriting goes first to ZeroLLM's own rewrite model, which runs on our servers. Anthropic's API then reads each rewrite beside the passage it came from, to catch sentences that don't make sense or change what you said. My voice is written by Anthropic's API, which also gets your writing sample. In an emergency we can turn on Anthropic's API as a stand-in when our model is busy or its drafts don't pass our checks.
• Detection runs on our own servers.

We don't sell, rent or share your data for advertising, and we don't train models on your history, documents, writing records or samples.

The Chrome extension and Google Docs add-on

• What they send. Only the text you choose to check: a selection, the main text of the page you're on, or your Google Doc or a selection in it. It goes to zerollm.app for detection and nowhere else. They don't read your browsing history, run analytics or load code from anywhere else. Each request says which of them sent it and its version, which goes into the request log above.
• Chrome extension. With an API key saved in its options, checks use that key, and API rules apply: history keeps only numbers. Without a key, checks use your zerollm.app sign-in, or run as a guest. The key stays in Chrome's storage on your computer, and the last result is kept only until Chrome closes.
• Google Docs add-on. It reads only the document it's opened in, and checks need an API key, which is stored with your Google account for the add-on alone. It highlights flagged sentences in your document only when you ask it to, and can clear those highlights again.

Cookies

We use a cookie to keep you signed in. Page analytics use your browser's local storage rather than a cookie. We don't use advertising or cross-site tracking cookies.

Your choices

Delete history items or clear everything on your history page, and revoke API keys on the API keys page. Pause or delete a document's writing record, and turn off its share link, from the document's writing receipt. Replace or delete your writing sample on your account page. To delete your account and everything tied to it, email hello@radsoftinc.com from the address you sign in with.

Changes

ZeroLLM is in beta and this page will change as it does. We'll update the date above when it does, and tell signed-in users about anything significant.