Privacy Policy

AI Summarizer · Chrome extension · Last updated 2026-06-02

This document explains what data the AI Summarizer Chrome extension collects, how we use it, and your rights.

TL;DR

1. What the extension does

When you click Summarize on a video, web page, or PDF, AI Summarizer:

  1. Reads the URL of the page you're currently viewing, or the file you uploaded.
  2. Fetches the underlying content:
    • YouTube / Vimeo videos — the public caption track.
    • Web pages — the HTML rendered to plain text in your browser.
    • PDFs — the bytes of the file you chose.
  3. Sends that content with your prompt to the AI provider you selected (Gemini / OpenAI / Anthropic).
  4. Displays the response.

The entire pipeline runs in your browser. We don't have a server in the middle of this flow in the free version.

2. Data we collect, process, store, and transmit

2.1 What we collect

The extension collects the following categories of data only when explicitly triggered by you (clicking "Summarize" or similar):

We do not collect: name, email (in v1.0.x free build), IP address, geolocation, browsing history beyond pages you summarize, personal communications, financial information, or any data for advertising purposes.

2.2 How we process the data

Processing happens in two places:

We, the extension developer, do not have a server in this pipeline. We never see your content or your API keys.

2.3 How we store the data

2.4 How we transmit the data

2.5 Account features (disabled in v1.0.x free build)

This version of the extension does not require, offer, or expose any sign-in or account creation. There is no Pro tier active. The codebase contains optional account scaffolding for future versions, but it is not reachable through the user interface in this build.

3. Legacy storage details

On your device (chrome.storage.local — never leaves your computer)

On your device (chrome.storage.session — cleared when you quit the browser)

On our infrastructure (Supabase) — only if you sign in

We do not store: your IP address (Supabase logs are kept under their infrastructure, subject to Supabase's policy); browsing history other than what you actively summarise; content of any page you didn't trigger a summary on.

3. Third parties

When you ask for a summary, page content goes directly from your browser to the AI provider you selected. We don't proxy it in the free version.

ProviderWhat we sendTheir policy
Google GeminiPage content + your promptlink
OpenAIPage content + your promptlink
AnthropicPage content + your promptlink
Supabase (optional)Email + subscription state + historylink
Stripe / Paddle / Lemon Squeezy (optional)Email + customer idSee respective sites

If you use browser-session mode instead of an API key, the prompt is typed into your already-logged-in tab on gemini.google.com / chatgpt.com / claude.ai. In that case the prompt goes to the provider under your own account, exactly as if you had typed it manually — we never see it, and no API key is used.

4. Permissions justification

PermissionWhy
storageSave your preferences and locally-stored API key.
scriptingInject the in-page "Summarize" button/card and read the current page's content — only after you ask for a summary.
tabsDetect the active tab's URL so the panel pre-fills, and read the open video tab's transcript.
activeTabAccess the page you're on when you click the action.
sidePanelOpen the summarizer in Chrome's docked side panel.
host: youtube.com, vimeo.com, twitch.tv, tiktok.com, instagram.com, x.com / twitter.comAdd the summarize UI and read video transcripts/captions on these sites.
host: gemini.google.com, chatgpt.com, claude.aiOptional "browser-session" mode: drive your already-signed-in AI tab instead of using an API key. Only used if you pick that mode.
host: generativelanguage.googleapis.com, api.openai.com, api.anthropic.comSend the content + your prompt directly to the AI provider you selected.

5. Your rights

For EU users: data is processed under GDPR Article 6(1)(b) — performance of a contract — for account/subscription data, and Article 6(1)(a) — consent — for optional history sync.

6. Cookies and tracking technologies

The extension does not set, read, or use cookies of any kind. It does not use:

The only browser-storage APIs used are chrome.storage.local (preferences, history) and chrome.storage.session (transient chat state). Both are scoped to the extension and not accessible to any website.

7. Analytics and advertising

The extension contains zero analytics. No Google Analytics, no Mixpanel, no Amplitude, no Hotjar, no Segment, no custom telemetry. We do not measure clicks, impressions, sessions, or any behavioral metric. There is no remote logging endpoint.

The extension contains zero advertising. No ad networks, no sponsored content, no affiliate tracking, no retargeting tags.

8. Children's privacy (COPPA)

The extension is not directed at children under 13 years of age, and we do not knowingly collect personal information from children. If a parent or guardian believes that a child has provided us with information, please contact m.nazar77@gmail.com and we will promptly take steps to delete such information from our systems (although, as documented above, no personal data is collected in this version).

9. Data categories — full disclosure table

CategoryCollected?HowStored whereRetention
Personally identifiable info (name, email, phone)No
Authentication data (passwords, credentials)No
Financial and payment dataNo
Health and medical informationNo
Personal communications (emails, SMS, chats)No
GeolocationNo
Web browsing historyNo
User activity (clicks, mouse, keystrokes)No
Website content (pages user chooses to summarize)Yes, per explicit user actionContent script extracts text via DOMParserTransmitted to user-selected AI provider; not stored by usNot retained — only kept in chrome.storage.session for the duration of the summary chat
User preferences (language, model, theme)YesUser enters in settingschrome.storage.local on user's deviceUntil user removes the extension or resets settings
API keys (provided by user)YesUser pastes in settingschrome.storage.local on user's deviceUntil user removes the extension or clears the key
Summary historyYesSaved after each summarychrome.storage.local on user's device, last 50 entriesLast 50 entries kept (oldest dropped automatically); user can wipe at any time

7. Changes to this policy

Material changes will be announced in the extension's release notes and updated here. The Last updated date at the top reflects the most recent revision.

8. Contact

Privacy questions, deletion requests, or data export: m.nazar77@gmail.com