Human Ink helps you prove that content you write is human-authored by analyzing your own typing behavior, only on Google Docs. Your raw keystrokes and your own typed text never leave your device — your writing is stored only as a one-way hash. We save two things off-device: anonymized writing metrics per document, and the text you paste in, so a reviewer can tell legitimate quotes from AI-generated text pasted and lightly reworded.
While tracking is enabled (you control this with the on/off switch), the
extension reads, locally and in memory, on docs.google.com documents only:
To give each document a memory across sessions and days, the extension saves a small metrics-only record per document to our database (Supabase). It contains: counts and timing (keystroke count, typed/pasted character counts, paste count, backspaces, session duration, dates), the typed-vs-pasted ratio, the document id/title, and the one-way proof hashes. If you are signed in, your Google email is attached for attribution.
Pasted content. When you paste text into the document, we save that pasted text (capped per paste) so quotes can be distinguished from reworded AI output. This is content you brought in from elsewhere — not your own typing. Pasted content can be sensitive (personal, copyrighted, or third-party material); we store only what was pasted into the doc, attribute it to your account if you are signed in, and it should be treated accordingly (consent, retention limits, restricted access — and FERPA if used with student work).
It does not contain your keystrokes or your own typed text — those never leave your browser (your writing is stored only as a one-way hash).
Human Ink's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We request access to your Google Docs content and revision history solely to compute the proof described above; we do not use it for advertising, do not sell or transfer it, and do not allow humans to read it except as required for security or to comply with the law.
Your on/off preference, a summary of your most recent session, and a per-document rollup are
kept in the browser's local extension storage (chrome.storage.local) on your
device. The per-document metrics record is also stored in our Supabase database (see above).
You can clear local data any time by removing the extension.
You can request access to, or deletion of, the data we hold about you at any time — no account required. We identify your records by the Google email attached to them (if you were signed in) and/or by a specific Google Doc's document id, and remove the matching rows from both our metrics table and our stored pasted content. Records captured while you were signed out carry no email, so to delete those we need the document id of the Doc in question.
To make a request, email ydevarshi@gmail.com with your Google email and/or the document link, and we will delete the data promptly. Removing the extension additionally clears all data held locally on your device.
The extension computes SHA-256 hashes locally. Any future on-chain publishing is user-initiated and only ever submits a hash (a fingerprint), never your raw text or raw behavioral data.
storage — save your on/off preference, last-session summary, and per-document rollup locally.activeTab — let the popup read the live session from the tab you're viewing.identity — optional Google sign-in, to read your doc's revision history and attribute metrics to your account.*.supabase.co — to save the anonymized per-document metrics described above.Questions about this policy or your data: ydevarshi@gmail.com.