Humanize AutotyperChrome extension

Privacy policy

Last updated 2 August 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 ever receive is a random ID used to check whether your subscription is active.

What stays on your device, always

DataWhere it livesWhy
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

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:

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.

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

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. That is the only thing it is used for: Input.dispatchKeyEvent and Input.insertText, outbound only.

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, only while typing is running, and detaches the moment the run finishes, errors, or you press Stop. Chrome displays its “debugging this browser” banner the whole time, so you always know when it 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

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.

Contact

robhatt2007@gmail.com