Privacy Policy
Last updated: September 11, 2026
Checked4AI 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 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 OpenAI's API (ChatGPT) to estimate whether it was written by a human or an AI. This happens when you explicitly click "Scan" or "Check this page for AI," or automatically when you open the replay viewer as a Pro subscriber (the AI Content Check). 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 OpenAI's API (ChatGPT) for analysis. The screenshot is not stored by Checked4AI after the API call completes.
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 sent to OpenAI is used solely to return an AI likelihood score and brief reasoning displayed to you inside the extension.
No secondary use of document data
Document content, revision history, and AI check results are never used for advertising, analytics, profiling, model training, 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
OpenAI API (ChatGPT)
Document text is sent to OpenAI only when you explicitly trigger the AI Authorship Check. OpenAI's privacy policy governs their handling of that data: openai.com/policies/privacy-policy
Stripe (payments)
Pro subscriptions are billed through Stripe. Checked4AI never sees or stores your card details; Stripe's privacy policy governs their handling of payment data: stripe.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 OpenAI server-side and the result is returned to you. Checked4AI does not store the content of these requests.
Data storage & retention
Document data stays in your browser
Cached revision entries and document text live exclusively in your browser's local storage. Document content is never stored on any server operated by Checked4AI.
Account and usage records
To enforce free-tier limits and Pro access, Checked4AI's backend stores a small account record keyed to your Google account ID: how many free replay views and AI checks you have used, and your subscription status (including your Stripe customer ID if you subscribe). This record contains no document content. It is deleted on request โ email support@checked4.ai.
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.
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 in the extension
The extension contains no usage tracking, crash reporting, or analytics SDKs. The checked4.ai website uses standard web analytics and advertising tags, described in the next section.
No data from other sites
The extension only activates on docs.google.com. It does not read content from any other website.
Website analytics & advertising (checked4.ai only)
Google Analytics and Google Ads
The checked4.ai website (not the extension) uses Google Analytics to measure page visits and Google Ads conversion tracking to measure whether an ad click led to an install or subscription. These set Google cookies (such as _ga and _gcl_au) and may read a gclid parameter from the URL. Google's privacy policy governs their handling of that data: policies.google.com/technologies/partner-sites
Reddit Pixel and Conversions API
If you arrive from a Reddit ad, the website stores the rdt_cid click ID in a first-party cookie and loads the Reddit Pixel, which sets a _rdt_uuid cookie. Page visits and subscription conversions may be reported to Reddit, including a hashed form of your email address if you subscribe, so Reddit can attribute the conversion to the ad. Reddit's privacy policy governs their handling of that data: reddit.com/policies/privacy-policy
What these tags never receive
Analytics and advertising tags run only on checked4.ai pages. They never receive Google Doc content, revision history, AI check results, or anything from inside the extension. You can block them with a content blocker or your browser's tracking protection without affecting the extension.
Questions?
If you have questions about this privacy policy or how your data is handled, please contact us at support@checked4.ai.