Draft — pending legal review
Privacy Policy
Last updated: October 2, 2026
This page explains, in plain language, what HumanizerKit stores when you use our writing tools, why we store it and what you can do about it. We try to collect as little as we need to run the service.
What we store
- Your text and results. When you run a tool, we store the text you submitted and the result so it can appear in your history and so we can investigate problems.
- Your account. If you sign in, we store your email address and, if you use Google sign-in, your name and profile picture from Google.
- Usage counts. We count how many times you use each tool so we can apply the limits shown on the Pricing page.
- Saved references. If you save a source in the Reference Finder, we store its bibliographic record together with the claim you saved it for, until you remove it from your library.
- Feedback. If you rate a result, we store that rating with the run it belongs to.
- Abuse prevention data. We store a one-way hash of your IP address (not the address itself) to stop one person from creating unlimited guest sessions. When you sign in, your session also records your browser's user agent (for example, the browser and operating system name); we do not store your IP address with it. Your IP address is briefly held in server memory to rate-limit sign-in attempts.
How long we keep it
Your history stays until you delete it. When you delete a run, it is hidden from your history right away. Deleted runs are then permanently erased from our database by a scheduled cleanup, which we will switch on before our public launch; until then they remain stored but hidden. Usage counts are kept for billing and abuse prevention.
If you delete your account, your profile, sign-in sessions, history, feedback and saved references are deleted immediately and cannot be recovered. What we keep is limited to anonymous usage counts. If you had a subscription, Stripe keeps the payment records it is required to keep, such as invoices.
Cookies
We use a small number of cookies that are needed for the site to work. We do not use advertising cookies.
- Session cookie keeps you signed in after you enter your email code or sign in with Google.
- Guest ID cookie (
aw_anon) is a random, signed identifier that lets us keep your guest history and daily limit together before you sign in. Its contents are not linked to your identity unless you sign in, at which point your guest runs move into your account.
Services that process your data
- AI model provider. When you use a tool that relies on an AI model, the text you submit is sent to the company that runs the model so it can produce your result. The Plagiarism Checker's check does not use an AI model; only its Pro "Rewrite this passage" option does (see below).
- Research databases. When you use the Reference Finder, search terms based on your claim are sent to public research databases and book catalogues (OpenAlex, Crossref, Semantic Scholar, Open Library and Google Books) to find sources. Identifiers of the sources that were found, such as a DOI, may be sent to Unpaywall to look for an open-access copy. Your account details are not sent with either. Citations are formatted in your browser.
- Plagiarism Checker sources. To find matching sources, the Plagiarism Checker sends short phrases from the text you check (up to 40, each 8 to 12 words long) as search queries to the Wikipedia API, run by the Wikimedia Foundation, and to OpenAlex. Your full text and your account details are not sent with them. The check itself uses no AI model. Like the other tools, the text you checked and the result are stored in your history. If you use "Rewrite this passage" on the Pro plan, that passage is sent to the AI model provider to suggest a new wording.
- Cloudflare Turnstile. For guests, Cloudflare checks that requests come from a real browser. Cloudflare may process your IP address and browser details for this check.
- Email delivery. When you sign in with email, a delivery provider sends your one-time code.
- Google. If you choose Google sign-in, Google handles that sign-in. Our pages also load the Inter font from Google Fonts.
- Payments (later). When paid plans launch, payments will be handled by Stripe. We will never see or store your full card number.
Improving our tools
We do not sell your text. We may review stored runs and ratings to fix bugs and improve our prompts and quality checks. If you would rather we did not use your runs for this, you can opt out by contacting us. We will add a self-serve setting for this before paid plans launch. You can also delete runs from your history at any time.
Your choices
- Use the tools as a guest without giving us your email.
- Delete any run from your history.
- Delete your account yourself at any time from your account page. It is deleted immediately, together with your history and saved library; if you have a subscription, cancel it first.
- Ask us for a copy of your data.
Children
The service is not intended for children under 13, and we do not knowingly collect their information.
Changes
If we change this policy, we will update the date at the top of this page. For significant changes we will also let signed-in users know.
Contact
A contact address for privacy requests will be published here before launch.