Privacy policy
Last updated 26 October 2026.
Humanize Autotyper types text you already have into a document on your screen. The short version: the text you type out never leaves your computer, and the only thing we receive automatically is a random ID used to check whether your subscription is active. Anything else reaches us only if you write it in the feedback box and press Send.
What stays on your device, always
| Data | Where it lives | Why |
|---|---|---|
| The text you paste in | chrome.storage.session, in memory, wiped when Chrome closes |
So the popup can be closed and reopened mid-run |
| Your settings (speed, pauses, typos, …) | chrome.storage.local |
To remember your preferences |
| Free-plan word count | chrome.storage.sync, a running total plus a window start date |
To meter the free allowance |
| Feedback you have started but not sent | chrome.storage.session, in memory, wiped when Chrome closes |
So it survives the popup closing |
None of this is transmitted to us, to any analytics service, or to anyone else. The word count is a number; the words themselves are never counted anywhere but on your own machine and are never uploaded.
What is sent to our server
Only if subscriptions are enabled in your build, and only these fields:
- Install ID, a random UUID generated on your device the first time you open the extension. It is not derived from your name, email, hardware, browser fingerprint, or IP, and it identifies nothing about you except “this install”.
- Reference code, if support asks you to quote the one shown after checkout.
- Plan choice (monthly or yearly) when you start checkout.
- Feedback, only if you write some and press Send. See below.
Our server replies with your subscription status and nothing else. It never receives your documents, your settings, your word counts, or the pages you visit.
Feedback
The extension and the website both have a feedback box. Nothing is sent until you press Send. What goes is the message you wrote, labelled with where you wrote it and, from the extension, its version number. No install ID goes with it, and we never ask for your name or email.
Our server does not store the message. It passes it to a Google Apps Script that emails it to our Gmail inbox, where it is kept like any other email under Google’s privacy policy. To stop the box being flooded, the server holds your IP address in memory for up to 10 minutes; it is never written down or sent on. Because the message arrives with no name or address, we cannot reply to it or link it to you.
Payments
Checkout runs on Stripe’s own hosted page, in a normal browser tab. Your card number, billing address, and email are entered on Stripe’s site and handled by Stripe under Stripe’s privacy policy. This extension never sees, receives, or stores payment details.
Our licensing database stores, per subscriber: the Stripe customer and subscription IDs, the plan, the subscription status and renewal date, the license key, and the install IDs bound to it. We do not keep a copy of your email address; the Manage or cancel button opens Stripe’s Customer Portal for anything billing related.
The website
This policy covers the extension. The website that hosts it, humanizeautotyper.com and humanize-autotyper.web.app, uses Google Analytics through Firebase to count visits and to see which pages people read before they install. That is ordinary website measurement: pages viewed, rough location by country, browser and device type, and whether the visit arrived from a search or a link. Any tracker blocker stops it, and Google’s handling of what it collects falls under Google’s privacy policy.
The extension itself sends none of this. The two are separate, and nothing on the website can see the text you paste into the extension.
What we do not do
- No analytics, telemetry, crash reporting, or usage tracking in the extension.
- No advertising, and no selling or sharing of data with third parties.
- No reading, collecting, or transmitting of the content of web pages you visit.
- No account, no password, no email list.
About the debugger permission
Google Docs and other rich editors ignore keystrokes that scripts fake, so this
extension uses Chrome’s debugger API to dispatch real keyboard
events into the tab you choose. It uses Input.dispatchKeyEvent and
Input.insertText for that input. At Start it also runs a fixed local
location check that returns only yes or no: is this tab a Google Doc? The tab’s URL
is not returned, stored, or transmitted.
The extension does not use the DevTools Protocol to read the DOM, read cookies, intercept network traffic, or capture page content. It attaches only to the tab that is active when you press Start and releases the connection during idle pauses as well as when the run finishes, errors, or you press Stop. Chrome displays its “debugging this browser” banner whenever a key burst is attached.
At startup the extension also enumerates existing debugger targets once, purely to detach any session left behind by a crash. It does not record what it finds.
Data retention and deletion
- Device-side data is deleted when you uninstall the extension, or immediately if you clear the extension’s storage.
- Licensing records are kept while your subscription is active and afterwards only as long as needed for billing and tax records.
- To delete your licensing record, cancel in Stripe’s Customer Portal and email us from the address you paid with, which is how we find the right record. We hold no other way to identify you, which is rather the point.
- Feedback emails are kept in our inbox for as long as they are useful. To have one deleted, email us its text and roughly when you sent it.
Children
This extension is not directed at children under 13 and we do not knowingly collect data from them.
Changes
If this policy changes materially, the version shipped with the extension is updated and the date at the top changes with it.