InkWho

InkWho privacy policy

Last edited: October 25, 2026.

This policy describes local analysis and optional Google Docs snapshot import. Features vary by release. Google Docs import is being prepared for a future release; the Google Docs section applies to versions that offer Import from Google Docs. Older releases do not offer that feature.

Local text analysis

InkWho reads visible webpage text to estimate AI-writing characteristics. Text analysis runs entirely on your device. InkWho DOES NOT send webpage text, browsing history, or analysis results to a server. No InkWho account is required for local analysis. Optional Google Docs import requires Google sign-in and consent, as described below. The extension does not include a remote analytics service for text analysis.

The Check text page also accepts pasted English or a TXT, DOCX or text-layer PDF file you select. Batch checking accepts up to ten TXT files. Compare two texts keeps each input separate. Importing a file does not automatically start analysis. InkWho does not save this input in extension storage. Use Clear to remove it from the open Check text page. Chrome may restore form text when reopening a tab or browser session; this is managed by the browser. InkWho DOES NOT upload the text or file.

Optional local result history

History is off by default. Inside Recent results, choose Keep my results on this device to save completed text, webpage and selection results. Records contain a score, section scores, coverage, mode, app version, source category, time and random record identifier. They never contain original text, page titles, URLs, website identities or filenames.

Up to 20 records are retained. Records older than 30 days are removed when history is next accessed. Delete individual entries, choose Clear history, or turn history off to clear all records. No history is sent automatically. History cannot restore or rerun original text.

Copying and saving results

Copy result, Save result and Print/PDF create a report containing score metadata, coverage, mode, time and app version. Original source text, webpage addresses, filenames and random record identifiers are omitted. Reports include the InkWho attribution link; a current historical-wording match can also include its published source link. These actions do not upload a report. Your clipboard and downloaded or printed files are controlled by your device and remain separate from extension storage.

Copy text & result includes the selected passage, its displayed judgment and score, any website-context adjustment, any matched historical source, and an InkWho attribution link. Share includes the checked text and its result. Sharing opens your device’s sharing options when supported; otherwise it copies that content to your clipboard. InkWho does not choose a recipient or send a message for you. These actions happen only when you choose them; shared text is not added to local history or uploaded for analysis.

Settings

Your settings are saved in Chrome extension local storage, including sites you pause or explicitly enable. Private and sensitive sites identified by the extension, and pages containing password fields, pause by default. These safeguards cannot identify every sensitive page. You control Chrome site access and can switch automatic analysis off.

Optional feedback

Thumb buttons save only votes you deliberately submit. Stored fields include the displayed score, agree/disagree vote, result scope (overall, section, or selection), optional section number, detection sensitivity, analysis and app versions, timestamp, and random identifiers used to group results and replace votes. New score votes do not include webpage text, page titles, URLs or hostnames.

In Your feedback, turn Enable feedback off to hide voting controls and prevent new feedback from being saved. Existing records remain until you choose Clear feedback. Up to 500 current score votes are kept locally. InkWho does not automatically transmit votes.

Export feedback downloads a file to your device. Random identifiers and timestamps are excluded, with temporary grouping numbers used within that export. Exporting does not send the file to the developer. If you choose to share it later, review the file and the destination before sending.

Earlier feedback records and compatibility feedback handlers can retain a website hostname or a free-text comment locally. The current passage-score thumb controls do not store website identities or source text. Clear feedback deletes both compatibility records and current score votes. Current exports exclude compatibility free-text comments and website identities.

Retention and control

You can clear feedback, disable analysis, change site permissions, or uninstall the extension. Exported files are separate downloads; delete them through your device's file manager if no longer needed.

Contact

For privacy questions, contact [email protected].

Website context scoring

Website context is evaluated locally on supported AI chat sites and may adjust the writing score. It is an experimental heuristic, not a calibrated authorship probability. It is applied automatically; there is no separate website-context switch. Earlier saved website-context opt-outs no longer apply. Other reading preferences are preserved. A model can quote or reproduce human writing, so an AI-site result does not establish who originally wrote the words. Adjusted results may retain the original model score and scoring-method identifier in optional local history; website addresses and message roles are not saved.

Historical wording and page dates

A small bundled index can identify exact wording from four reviewed 2016 public-domain source excerpts. Matches show source evidence and coverage; they do not lower the writing score or prove who placed the text on the current page. Unmatched text is not evidence of recent authorship. Declared webpage dates are unverified and do not change scores. Matching and date checks run locally. Source identities and matching spans are not saved in result history.

Optional Google Docs snapshot import

Google Docs import requires a Google account and an explicit Google authorization, even though InkWho itself requires no account. The requested scope is https://www.googleapis.com/auth/documents.readonly, which allows viewing all Google Docs documents accessible to the authorized account. It is not restricted by Google to the one pasted link. InkWho uses this access only to retrieve the document you request; it does not list your documents, edit them, or write results back to Google Docs.

When you choose Connect and load preview, Chrome handles Google authentication. InkWho sends the requested document ID and access token to Google's Docs API. Google returns the requested document's title and tab contents. All tabs of that document are retrieved, including tab structure and content that the text extractor excludes; only the selected tab's body paragraphs and lists are used for analysis. Pending suggested changes are excluded, using original wording. Comments are not retrieved. Tables, images, headers, footers, footnotes and other unsupported elements are excluded from analyzed text and reported in the preview. This is a snapshot, not continuous document monitoring. Refresh retrieves that document again only when requested.

InkWho keeps the document link, document and tab titles, retrieved content, preview and snapshot binding in the open page's memory. It does not persist these in extension storage or transmit them to InkWho. Tokens are held in page memory, never written by InkWho to extension storage or logs. Chrome manages its own token cache and Google can retain the account grant. Closing or reloading the page clears InkWho's in-page access state but does not prove Google access was revoked. Disconnect attempts Google revocation and Chrome cache cleanup, drops the snapshot binding and clears the displayed result; existing imported draft text remains ordinary text until you clear it. If remote revocation cannot be confirmed, the interface directs you to remove access from your Google Account connections. Clear imported text separately if you no longer want it in the open page. Browser session restoration can retain form text. Disconnect does not delete previously saved local result history, clipboard contents, downloaded reports or your source Google document. Clear local result history separately using Recent results, and delete exported files through your device. Closing a page is not a secure-erasure guarantee.

Imported document text and analysis are not sent to InkWho servers, analytics providers or model-training services. API import and revocation requests use HTTPS. InkWho does not provide its developers or staff with access to imported document content through this feature. If you contact support or deliberately share a report, you choose what to disclose and to whom; avoid including private document text or credentials. Google receives the API requests needed for the import and disconnection. InkWho does not transmit imported Docs data to third parties; user-directed copy/share/export is under your control. Optional snapshot result history remains subject to the 20-record, 30-day limits described above; stored summaries remain until cleared or expired on access. Snapshot result history/report metadata can include import time, selected-tab analysis scope, retrieved-tab scope and detected exclusions; document title, document ID, URL, tab title and source text are excluded from metadata-only reports/history. Actions explicitly named Copy text & result or Share include text, as described above.

InkWho's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google Docs data is used only to provide the requested snapshot import and local analysis, not for advertising, sale, credit decisions or general-purpose AI model training.

Visiting the InkWho website

The public InkWho website is hosted by Cloudflare. Some pages load Cloudflare Web Analytics. Visiting the website makes requests to its hosting and analytics services; this is separate from the extension’s local analysis. The extension does not send checked webpage text or imported document content to these website services. For Cloudflare’s handling of website request information, see its privacy policy.