Privacy Policy

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 Checked4AI beyond your browser session.

Google Doc revision history

When you open the Checked4AI 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 Checked4AI 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 DeepSeek's API for analysis. The screenshot is not stored by Checked4AI after the API call completes.

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 sent to DeepSeek is 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.

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

DeepSeek API

Document text is sent to DeepSeek only when you explicitly trigger the AI Authorship Check. DeepSeek's privacy policy governs their handling of that data: deepseek.com/privacy

Checked4AI backend (checked4.ai)

AI authorship checks are proxied through Checked4AI's own backend at checked4.ai. Your Firebase authentication token is used to verify your identity; the document text or screenshot is forwarded to DeepSeek server-side and the result is returned to you. Checked4AI does not store the content of these requests.

Stored locally only

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

How to clear your data

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

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.