⏮ Checked4Privacy Policy
Privacy Policy
Last updated: May 2025

Checked4 helps you understand how any Google Doc was written — by replaying its revision history and checking content for AI authorship. This policy explains exactly what data the extension accesses, how it is used, and what is shared with third parties.

Data we access
📂
Google account identity

When you sign in, the extension authenticates your Google account via OAuth and Firebase Authentication. Your display name, email address, and profile photo are used to show who is signed in. This information is not stored by Checked4 beyond your browser session.

📂
Google Doc revision history

When you open the Checked4 viewer, the extension calls the Google Drive API to fetch the revision history of the current document. This includes the text content of each revision so the playback animation can be reconstructed. Revision data is stored only in your browser's local storage (chrome.storage.local).

📂
Document text — AI authorship check

If you use the AI Authorship Check feature, the extension sends the text content of the document to Anthropic's API to estimate whether it was written by a human or an AI. This only happens when you explicitly click "Scan" or "Check this page for AI." The text is not stored by Checked4 after the API call completes.

📂
Screenshots of the active tab

When you trigger the AI check from the extension popup, the extension captures a screenshot of the currently visible tab and sends it to Anthropic's API for analysis. The screenshot is not stored by Checked4 after the API call completes.

📂
Anthropic API key

If you enter an Anthropic API key to enable the AI Authorship Check, the key is stored locally in your browser (chrome.storage.local). It is never transmitted to any server other than Anthropic's own API endpoints.

How data is used
🔍
Revision playback only

Revision history is used solely to render the character-by-character playback animation in the viewer.

🔍
AI authorship results only

Document text and screenshots sent to Anthropic are used solely to return an AI likelihood score and brief reasoning displayed to you inside the extension.

🔍
No secondary use

No data is used for advertising, analytics, profiling, or any purpose beyond the features described above.

Third-party services
🔗
Google (Drive API + Firebase Auth)

Revision history is fetched from Google's servers using your OAuth token. Sign-in is handled through Firebase Authentication with Google as the identity provider. Google's privacy policy governs their handling of that data: policies.google.com/privacy policies.google.com/privacy

🔗
Anthropic API

Document text or screenshots are sent to Anthropic only when you explicitly trigger the AI Authorship Check. Anthropic's privacy policy governs their handling of that data: anthropic.com/privacy

🔗
No Checked4 backend

Checked4 itself does not operate any backend server. No data passes through our own infrastructure.

Data storage & retention
💾
Stored locally only

All data stored by Checked4 — cached revision entries and your Anthropic API key — lives exclusively in your browser's local storage. It is never uploaded to any server operated by Checked4.

💾
How to clear your data

You can remove all stored data at any time by going to chrome://extensions → Checked4 → Clear data, or by uninstalling the extension.

Data we do not collect
🚫
No browsing history

The extension only checks if the current tab is a Google Doc. It never reads your browsing history.

🚫
No location data

No GPS coordinates, IP-based location, or region data are collected.

🚫
No analytics or telemetry

There is no usage tracking, crash reporting, or analytics of any kind.

🚫
No data from other sites

The extension only activates on docs.google.com. It does not read content from any other website.

Questions?

If you have questions about this privacy policy or how your data is handled, please contact us at the email listed on the Chrome Web Store listing.

Checked4 · Data stays in your browser · No backend servers