한국어 · English
View Digest Privacy Policy
Last updated: September 30, 2026
View Digest (“the extension”) does not run a backend server, and the developer does not collect, store, or receive your API key, your analyses, or your viewing history in any form. All data either stays in your browser or is sent directly to Google (the Gemini API) using your own API key.
1. Information stored and where
| Information | Stored in | Details |
|---|---|---|
| Gemini API key | chrome.storage.sync |
Entered by you. It is never sent to the developer. If you use Chrome sync, it is synced to your own Google account. |
| Analysis reports, video titles/URLs, creation time, estimated cost | chrome.storage.local |
Your analysis history, up to 50 entries, kept only in this browser. |
| Subscribed channels | chrome.storage.local |
The channel URLs/IDs you added and when each was last checked. |
| Usage log (number of analyses, token counts, estimated cost) | chrome.storage.local |
Used only to enforce the daily limit and estimate costs. |
| Review-prompt state (number of successful analyses, when to ask next, whether you answered) | chrome.storage.local |
Used only to decide when to show the Chrome Web Store review card. It is never sent anywhere. |
The extension contains no analytics, advertising SDKs, or tracking pixels, and does not send your activity to the developer.
2. Information sent to a third party (Google Gemini API)
When you run an analysis, your browser sends the following to Google’s Generative Language API
(generativelanguage.googleapis.com) directly, using your own API
key:
- The URL of the YouTube video you are analyzing
- The prompt used to generate the report (fixed instruction text)
This request goes straight from your browser to Google and never passes through a server run by the developer, so the developer cannot know which videos you analyze. For how Google handles this data, see the Google Privacy Policy and the Gemini API Terms of Service.
3. What the extension does on YouTube pages
The extension runs only on youtube.com and reads only:
- The current page URL (to get the video ID)
- The tab title (used as the default report title)
It does not read or collect any other page content, such as comments, watch history, or sign-in information.
When you click a ▶ time button in a report, the extension moves the playback position of the YouTube tab showing that video to that time. It does not read or send any page information in doing so.
To show the channel name in your analysis history, the extension looks up the analyzed video’s URL at
YouTube’s public oEmbed endpoint (youtube.com/oembed) without sign-in information (cookies).
The channel name is stored with your history, only in this browser.
Likewise, to show when a video was posted, the extension loads the analyzed video’s public watch page
(youtube.com/watch) without sign-in information (cookies) and reads only the publish date. The date is
stored with your history, only in this browser; nothing else from the page is stored or sent anywhere.
4. Channel subscriptions (automatic analysis)
When you subscribe to a channel, the extension periodically fetches YouTube’s public RSS feed
(youtube.com/feeds/videos.xml) only to check for new videos. When the RSS feed is unavailable, it
fetches the channel’s public videos page (youtube.com/channel/…/videos) for the same purpose,
without sign-in information (cookies). No personal information is sent in the process.
5. Retention and deletion
- You can delete your analysis history, subscribed channels, and usage log individually or all at once from the popup or the options page at any time.
- Removing the extension or clearing your browser profile data deletes everything stored locally.
- Because the API key is stored in
chrome.storage.sync, if you use Chrome sync you can also delete synced data separately in your Google account settings.
6. Children’s privacy
The extension is not directed at children under 14 and does not knowingly collect personal information from children.
7. Changes
If this policy changes, the “Last updated” date on this page will be updated.
8. Contact
Please send questions through GitHub issues.