Privacy Policy

The short version

• You can run a free preview without creating an account. Signing in is optional — it exists so your records can be reached from another device — and there is never a password, only Google or a one-time code emailed to you. See section 8.
• Your text is sent to AI model services to be scored and rewritten. One of them, Alibaba Cloud DashScope, is a third party.
• We keep the text you submit and the rewrites we produce. Some of it is used to measure and improve rewrite quality.
• We use Microsoft Clarity (which includes session recording) and Bing UET. There is no consent banner on this site today.
• Clearing your browser data does not delete what is already on our servers. Email us and we will delete it.

1. What we collect

• An anonymous browser ID: a random UUID generated in your browser and stored in local storage. It is how we recognize you between visits and how your free allowance is tracked. It works with no account and no password; if you do sign in, this ID is what tells us which existing records belong to you.
• Account information, if you sign in: your email address and an account identifier issued by Supabase, our sign-in provider. There is no password — neither sign-in method creates one — so we hold none. Signing in is optional and section 8 covers it in full.
• Your IP address: stored on your user record and used to recognize a returning visitor when the browser ID is missing — for example after you clear site data. Under GDPR an IP address counts as personal data, so we name it here rather than filing it under “technical data.”
• The text you submit and the text we return: your input, the humanized output, and the AI-detection scores calculated for both.
• Your rewrite choices: when the humanizer offers several versions of a paragraph, we store the original paragraph, each candidate version, and which one you selected.
• Payment information: order ID, amount, status, and the customer ID and email address our payment processor (Creem) returns after a successful payment. Card numbers never reach our servers — the checkout is handled entirely by Creem.
• How you found us: the referring page, any UTM or ad-click parameters in the URL, and the search keyword if the referrer contains one. These are recorded once, on your first visit, and again with each order.
• Analytics events: page views, clicks, and session recordings collected by Microsoft Clarity, plus conversion events sent to Bing UET. See section 4.

2. Where your text goes

Humanizing text means sending it to a language model. Ours run in two places:

• Model servers we operate ourselves, which handle the main rewriting pass.
• Alibaba Cloud DashScope, a third-party model service. Every AI-detection score is produced there, and depending on how the rewriting pipeline is configured, the rewrite itself may run there too. Requests go to DashScope's endpoint at dashscope.aliyuncs.com, which is operated from mainland China, so your text is processed on infrastructure located there. Alibaba Cloud handles that text under its own terms as our processor.

No other third party receives the content of your text from our servers. Specifically:

• Creem, our payment processor, receives order amounts and identifiers — never your text.
• Bing UET, our advertising measurement tag, receives event names such as a purchase and the amount paid — never your text.

Session recording is a separate question, and section 4 answers it. We do not sell your data.

3. How we use your text to improve the service

When the humanizer generates several candidate rewrites and you pick one, we store your original paragraph, all of the candidates, and your choice. We use those records to measure rewrite quality and to improve the models behind the service. Your submissions and our outputs are also written to an internal processing log we use to diagnose failures and investigate abuse.

We do not sell this material, publish it, or show it to other users. If you would rather none of it be kept, email us after your run and we will delete the records tied to your anonymous ID — see section 7.

4. Analytics, session replay, and advertising

• Microsoft Clarity (loaded from clarity.ms) records page views, clicks, scrolling, and session replays — a reconstruction of what happened in your browser window. We also pass your anonymous browser ID to Clarity so that sessions from the same browser can be linked over time. A replay can include content that was displayed on the page, so please assume a recording may contain whatever was on screen during your visit.
• Bing UET (loaded from bat.bing.com) measures whether our advertising works. It receives event names and purchase amounts only.

Both are Microsoft products. Microsoft holds this data under its own retention rules and its own privacy statement, and we do not control what happens to it there.

There is no consent banner on this site today, so there is no in-page switch that turns analytics off. If you would rather not be measured, blocking clarity.ms and bat.bing.com — with a content blocker, your browser's tracking protection, or your own DNS — stops both, and the humanizer keeps working normally without them. You can also email us to have the identifiers we hold on our side deleted, though we cannot delete records inside Microsoft's products on your behalf.

5. Cookies and browser storage

• We set no cookies of our own. Nothing on our side depends on one.
• Local storage holds your anonymous browser ID and the traffic-source values described in section 1. If you sign in, it also holds your sign-in session — that is where it lives instead of in a cookie. Signing out removes it.
• Session storage holds a draft of a run in progress so a reloaded tab can pick up where you left off. It does not survive closing the tab.
• Clarity and Bing UET set their own cookies from their own domains, under Microsoft's terms.

Clearing your browser data gives you a fresh anonymous ID, but it does not delete anything already stored on our servers. To remove that, see section 7.

6. How long we keep things

• Preview and result documents: if you never paid for a run, its document is deleted automatically 48 hours after it was created. If you paid, it is kept for 30 days so you can come back and download it, then deleted automatically.
• Submitted text, outputs, rewrite records, and processing logs: we keep these until you ask us to delete them. We are not going to quote an expiry date we do not currently enforce.
• Payment records: kept for as long as accounting and tax rules require us to keep them.
• Analytics: held by Microsoft under Microsoft's retention rules, not ours.

One thing that is easy to confuse: the re-run window in your order history closes 7 days after payment. That is a product rule about what you can still do with an order, not a statement about when data is deleted.

7. Your rights, and how to use them

Under GDPR and the CCPA you can ask what we hold about you and ask us to delete it. We handle those requests for anyone who asks, not only for residents of the EU or California.

How to ask: email [email protected] with your anonymous browser ID. To find it, open your browser's developer tools on this site, look under Local Storage for the key uuid, and copy the value. If you have paid for a run, the order ID on your Creem receipt works too.

What happens next: we process these requests by hand — there is no self-serve delete button in the product — and we aim to complete them within 30 days. We will delete the text, rewrites, and processing logs tied to your ID. We will keep payment records where tax and accounting rules require it, and we cannot reach into Microsoft's analytics products on your behalf.

If we cannot reasonably tell that a request comes from the holder of an ID, we may decline it. An anonymous ID is not proof of identity, and honoring an unverified request would let anyone delete someone else's work.

8. Accounts and signing in

Signing in is optional. The free preview needs no account, and the anonymous browser ID from section 1 is all we need to give you a result. An account does one job: it attaches the records we hold for you to something more durable than a single browser, so you can reach them from another device.

What we receive when you sign in: your email address, and an account identifier issued by our sign-in provider. That is the whole list. Neither sign-in method produces a password — one is Google, the other is a six-digit code emailed to you — so there is no password for us to store, leak, or ask you to reset.

• Supabase verifies your sign-in and stores the account record on our behalf. Their hosting region for this project is us-west-1, in the western United States. Your submitted text is never sent to Supabase.
• Resend delivers the email containing your sign-in code, sent from mail.aigcleaner.app. Resend handles your email address and that message. It receives none of your text.

What happens to work you did before signing in: signing in links the records already tied to this browser's anonymous ID to your account. If you sign in again on a different device, the records tied to that device are brought under the same account, so one account ends up holding both. Paid orders are matched to your account by the verified email address on the order; where the same address has been used by two accounts, the first to claim an order keeps it and we do not move an order from one account to another.

The history list stored inside your browser is a separate thing, and signing in does not upload it or delete it. It stays on the machine and stays visible to you here. Signing out clears it from that browser, so the next person to use the machine cannot read it.

Deleting your account: email [email protected] from the address you signed in with. We will delete the account record we hold — the email address and account identifier included — along with the text, rewrites, and processing logs stored under it. As in section 7, this is handled by hand rather than by a self-serve button in the product, we aim to complete it within 30 days, and the same limits apply: payment records are kept where tax and accounting rules require it. You can also simply stop signing in; the free preview keeps working without an account.

9. Changes to this policy

If we change how we handle your data, we will update this page and the date at the top. The version you are reading is the one that applies.

10. Contact

Questions, access requests, and deletion requests all go to [email protected].