Privacy policy
Effective date: October 5, 2026
This policy explains what HumDocs ("we", "our", "us") collects when you use the HumDocs Typer extension, this website and your account (together, the "Service"), why, who helps us run it, and what you can do about it.
The short version
- The extension never sends us the text you give it. It types that text into the Google Doc you choose, from your own browser.
- The extension talks to our server about licensing: to start your free trial when you press Start, and to check a license key you enter. Your text is never part of that.
- The extension also sends anonymous counts of events like installs and runs, with no identifiers: no install number, no text, nothing about your documents or you.
- This website sets no cookies. If you sign in, your browser keeps a sign-in token so you stay signed in.
- We do not sell or share your personal information, and we do not use advertising trackers.
1. The browser extension
What stays on your computer. The extension keeps these in your browser's extension storage, on your computer only: the text in the popup (so it is still there next time, until you clear it or uninstall); your settings; your license key and when it was last checked; the random number made when it was installed, and when your trial started and ends; how far the last run in a Doc got, so it can be continued after a reload; runs you queued or scheduled, and your last 30 runs (with their text, so you can use one again); you can clear the history in the extension; and small notes such as whether you have seen the keep-awake notice or updated from a version that had the Pro features free. Files you import (.txt or .docx) are read on your computer and never uploaded. Uninstalling the extension deletes all of it.
What goes to Google. The extension types into the Google Doc or Google Slides presentation you pick, the same as if you typed it yourself. Google saves it in your Google account under Google's own privacy policy. The extension runs only on docs.google.com (Google Docs and Slides).
What comes to us for licensing. Only what licensing needs. If you enter a license key, the extension sends the key to our license server to check it, together with a random number it made when it was installed (it names no person and no computer; it lets us count, and limit, how many installs use a key). This happens when you press Activate, then about once every 30 days (or daily while a key is not active). The free trial starts only when you press Start on the extension's first screen (or in its Settings); until then nothing is sent. Starting it sends only the random number it made when it was installed (the same one described above), and we keep a scrambled form of it with the trial's start and end dates, so asking again from the same copy of the extension gets the same dates back. If the extension was updated from a version before 2.3.0, starting the trial also sends the version it was updated from, which makes the trial 7 days instead of 3; that version is not kept. Free runs are not counted and send nothing to our server. Like any web request these also carry your IP address and basic browser details. When you start the trial, we record a scrambled form of your network's IP address (a one-way keyed hash from which the address cannot be read back) and keep it for up to 90 days, so a trial cannot be restarted endlessly from one network. Otherwise the address is used only briefly, to slow down repeated guessing. Nothing else is sent for licensing: not your text, not your documents, not your browsing.
Anonymous usage counts. The extension also sends anonymous counts of events like installs and runs, with no identifiers, so we can see basic numbers such as how many installs go on to a first run, a trial or a purchase. Each count says only which event happened (installed, updated, first run, a run started, finished or stopped, a Get Pro or Get a License click, a trial started), which plan the extension is on (free, trial, Pro, or what an earlier version kept) and the extension's version number. It carries no install number, no text, nothing about your documents and nothing about you, and it is sent in the background without holding anything up. We add it to that day's total and keep only the daily totals. We do not store or log your IP address with them; like any web request, a count reaches our server provider (Supabase) with your IP address, which its own logs may keep for a short time.
Chrome Web Store. The HumDocs extension's use of the data it handles complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. It is used only to provide the extension's features, never sold, never used for advertising, and never used to decide anyone's creditworthiness.
2. The website and your account
- Account: your email address, and your name and profile picture if you sign in with Google. Our sign-in provider records when you signed in and the IP address and browser used, for security.
- Purchases: Stripe takes payment on its own pages and tells us your email address, the date, the amount and a payment reference. We never see your card number. We keep your license key with the purchase email, the Stripe reference, and whether the license is active, refunded or disputed.
- Emails: we send sign-in links and codes, and an email with your license key after you buy. We do not send newsletters or marketing emails.
- Account settings: the name you enter on your account page.
- Support: if you email us, we keep your messages and anything you attach. If you use the bug report form, it sends us an email with what you write, your email address if you give one, any screenshot you add, your HumDocs version, and your browser and operating system. We also keep a private structured copy for bug tracking and human review. It contains screened report text, steps, product area, HumDocs version, and browser/operating system, plus internal triage status and tracking data. It has no separate reporter-email, screenshot, IP address, account, payment, or authentication field. If screening detects sensitive content or untrusted instructions, the affected text is withheld from the structured copy and the report is held for manual review. Screening may miss sensitive details in ordinary text, so please do not submit passwords, API keys, payment information, or other secrets. Your email address and screenshot remain in the support email, which we keep separately while handling the issue. We do not send bug reports to AI in this mode. To ask about or request deletion of a report, email [email protected].
- Visits: our host keeps standard server logs (IP address, browser, pages requested) for security. We count page views with Cloudflare Web Analytics, which does not use cookies and does not identify you.
3. Cookies and similar storage
This website sets no cookies. If you sign in, your browser stores a sign-in token in local storage so you stay signed in, until you sign out or delete your account, and a one-time value while a sign-in is being completed. Both are needed for sign-in to work, so we do not ask for consent for them. Stripe sets its own cookies on its checkout pages; see Stripe's privacy policy. Our pages load fonts from Google Fonts and the sign-in code library from esm.sh, so your browser contacts those services, which receive your IP address.
4. Why we use your information
- To run your account, sell and deliver licenses, check license keys and answer support requests (performing our contract with you).
- To keep sign-in secure, prevent fraud and abuse, and enforce our Terms (our legitimate interests).
- To keep purchase records for tax and accounting (legal obligation).
We do not use your information for advertising, and we make no automated decisions about you.
5. Who we share it with
Only these providers, and only to run the Service:
- Supabase: stores accounts and licenses, answers license checks, keeps anonymous daily usage counts, passes original bug reports to our inbox, and stores private screened bug-report copies and tracking status;
- Stripe: processes payments;
- Google: "Continue with Google" sign-in, and Google Fonts;
- Resend: delivers sign-in emails, license key emails, and bug reports to our inbox;
- Cloudflare: hosts this website and counts page views;
- esm.sh: serves the code library our sign-in uses;
- legal or regulatory authorities, when the law requires it.
We do not sell or share personal information, as California law uses those words.
6. How long we keep it
- Your account: until you delete it.
- License and purchase records: for as long as the license exists, and for as long as tax and accounting law requires. This is what keeps your key working and lets us handle refunds.
- Private structured bug-report rows: approximately 90 days after receipt, then deleted by a scheduled retention job. An active processing lease or job interruption can delay deletion; we monitor overdue rows. Provider backups can have a separate retention period.
- Support bug-report emails and screenshots: while we handle the issue, then deleted within 90 days after resolution where operationally practical. We handle appropriate deletion requests sooner when practical. Other support messages are kept only as long as needed.
- Scrambled network addresses (from starting the trial): 90 days, then deleted.
- Anonymous daily usage counts: kept as long as they are useful. They identify no one.
- Server and sign-in logs: kept by our providers for a short time.
7. Deleting your account
"Delete my account" on your account page removes your account and sign-in details straight away. Your license records stay, detached from the deleted account, so the key keeps working and can be added to a new account. If you want those records erased too, email us: we will delete everything the law does not require us to keep, and the key will stop working.
8. Your rights
Wherever you live, you can ask us for a copy of your data, or ask us to correct, delete or export it. Email [email protected]. We answer within 30 days and will not treat you differently for asking. In the EU, the UK and similar places you can also object to or restrict some processing, and complain to your local data protection authority. In California you have the right to know, delete and correct your personal information.
Do Not Track and Global Privacy Control. We do not track you across other websites, so there is no tracking for these signals to turn off. We treat them as a request not to sell or share, which we never do anyway.
9. Children
The Service is not directed to children under 13 (or a higher age where local law requires), and we do not knowingly collect personal information from children. If you believe a child has an account, email us and we will delete it.
10. International transfers
Our providers may process data in countries other than your own, mainly the United States. Where the law requires it, transfers are protected by our providers' standard contractual clauses or equivalent safeguards.
11. Security
We use access controls, encryption in transit and the security features of our providers. No system is perfectly secure, so we cannot promise that nothing will ever go wrong. If a breach affects your data, we will tell you as the law requires.
12. Chrome Web Store and Google data
The use of information by the HumDocs Typer extension follows the Chrome Web Store User Data Policy, including the Limited Use requirements. Our use of information received from Google sign-in follows the Google API Services User Data Policy, including the Limited Use requirements: we use your Google name, email address and picture only to create and show your account, never for advertising.
13. Responsible use
HumDocs is not for academic dishonesty, plagiarism, exam misconduct or getting around a school, employer or platform policy. If we see signs of that, we may review the account and purchase records we hold (we never have your text or your documents) and act under our Terms.
14. Changes
If we change this policy we will update the date at the top. For important changes we will tell account holders by email before they take effect.
15. Contact
HumDocs is run by Nihit Kaul, California, United States, who is responsible for the information described in this policy. Privacy questions and requests: [email protected].