Privacy Policy for ezy Youtube Video Control

Last updated: August 12, 2026

1. Scope

This policy explains how ezy Youtube Video Control ("the extension") handles information while providing YouTube viewing, player-control, navigation, and page-layout features. The extension is independently developed and is not affiliated with, endorsed by, or sponsored by YouTube or Google.

2. Information the Extension Handles

• Saved preferences: player, layout, list-filter, caption, playlist, Shorts, chapter-dot, video-summary, and keyboard-shortcut settings, including channel names, handles, or title keywords entered into exclusion fields.
• Current YouTube page and website content: the current URL and video identifier; page and player state; visible title, channel, view-count, duration, upload-time, watched, live, and upcoming indicators; caption/player information; chapter titles and times; and, when Video Summary is enabled, the answer returned in YouTube's native Ask panel.
• Limited YouTube Ask conversation text: when Video Summary is enabled and the native Ask panel already contains a conversation, the extension checks existing user turns for the fixed localized summary wording and finds the latest completed summary answer. This is used only to avoid a duplicate request and reuse an existing summary. Non-summary turns are not copied or retained.
• Feature interactions: relevant keyboard, mouse-wheel, click, scroll, and playback events are processed in real time to perform selected actions. They are not logged as an activity history.
• Optional Google account authorization: only when the user selects Connect Google account, the browser's Identity web-auth flow opens Google's account chooser for the Google Drive appDataFolder scope. This login is independent of the browser profile. After connection, the extension reads the current Drive user's display name and email address through the Drive about resource so the popup can identify the connected account. It does not request separate email/profile OAuth scopes, contacts, or general Drive files. It may also read limited file metadata already present in its hidden app-only folder to confirm access.
• Optional settings synchronization and backups: when enabled or manually requested, the extension stores synchronized preference values, per-setting modification timestamps, a random device identifier, schema/revision metadata, and up to five backup snapshots in its hidden Google Drive appDataFolder.
• Optional channel-folder management: when enabled, the extension stores user-created folder names and order, channel IDs, titles, page and thumbnail URLs, folder assignments, ordering, modification metadata, and deletion markers locally. If channel sync is enabled, the same channel-library.json document is stored in the hidden Google Drive appDataFolder. After explicit subscription-list connection, the YouTube Data API supplies current subscription IDs, limited subscribed-channel metadata, latest public-video publication times, and public topic-category URLs. Topic categories are requested only while the manager is maximized and are displayed as classification aids.
• Optional YouTube subscription removal: only after the user selects subscribed channels, presses the separate unsubscribe control, and confirms its warning, the extension sends those subscription IDs to the YouTube Data API for removal. Folder deletion and moving a channel between extension folders never unsubscribe the user.

The extension does not create or retain a history of videos or pages the user visits.

3. How Information Is Used and Stored

• Preferences are stored locally on the current browser profile with Chrome's chrome.storage.local API. New preference changes are not transmitted through Chrome Sync. On the first run after upgrading, existing preference keys are copied once from legacy chrome.storage.sync storage into local storage. Google Drive synchronization remains off by default and exchanges non-device-local settings only after the user enables it.
• Current page content, page state, chapter data, and interaction events are processed temporarily in the current tab only to provide selected features. They are not sent to the developer or stored as browsing history.
• Google account connection is optional. An interactive chooser opens only after an explicit button click; a previously authorized connection may be checked or renewed silently. OAuth access tokens remain only in the background service worker and chrome.storage.session. The display name is not stored. While connected, the email address is stored locally as an OAuth login_hint so renewal remains bound to the selected account, and is removed on Disconnect.
• Settings synchronization is local-first and optional. When enabled, settings.json is merged using per-setting timestamps and a random device identifier. The extension checks shortly after local changes and approximately every two minutes. Only the five newest manual or automatic safety backups are retained. Turning sync off stops Drive exchange without deleting cloud files.
• Channel-folder management is off by default and local-first. It replaces YouTube's native subscription section only after its own section mounts successfully and restores the native section when disabled or unavailable. Folder selection and expansion are device-local UI state. Separately enabled channel sync exchanges channel-library.json with appDataFolder approximately every two minutes.
• YouTube subscription access is requested incrementally only after the user explicitly connects the list in the channel manager. The subscription list is held in a short in-memory cache and normalized into the local channel library. To show “today” or “N days ago” without repeatedly consuming API quota, latest public-video publication and check times are cached only on the current device for approximately 12 hours and are not uploaded to Drive. Public topic categories are fetched in batches only while the manager is maximized, kept in memory for approximately 12 hours, and are not uploaded to Drive. Unsubscribe requests are never scheduled and never result from folder editing.
• The developer operates no data-collection server and receives no preferences, page content, prompts, summary responses, analytics, or telemetry from the extension.

4. Video Summary: YouTube Ask Processing

• The request is handled in the current YouTube page by Google/YouTube. Google/YouTube may process the prompt, current video, account, and page context according to the user's settings and Google's policies.
• The extension reads the returned answer and keeps a cloned copy only in the current tab's memory. It discards that copy when the feature is disabled, the page navigates, or the tab reloads.
• The developer does not receive the prompt, video context, or answer. YouTube may retain its native Ask conversation under its own service behavior and policies; the extension does not control or delete YouTube's copy.
• If the native Ask panel already contains a conversation, the extension reads existing turn text only to determine whether the same summary was previously requested. It reuses the latest completed answer or stops without adding a new question. Unrelated conversation turns are not stored.
• If YouTube Ask is unavailable, the extension does not send the request through an alternate service.

5. Sharing and Service Providers

The developer does not sell, rent, share, or transfer user information. External processing connected to user-selected features is limited to:

• Legacy Google Chrome Sync storage: an earlier version may have synchronized saved preferences. The current version reads those existing extension preference keys once for local migration, leaves the legacy copy unchanged, and does not send new preference changes through Chrome Sync.
• Google/YouTube Ask: processes the fixed summary request and relevant current-video context only when Video Summary is enabled and YouTube Ask is available.
• Google OAuth web authorization and Google Drive API: the browser Identity API opens Google's web account chooser independently of the browser profile. The Drive API accesses this extension's hidden appDataFolder, returns the current user's display name and email address, and—only for enabled sync or requested backup/restore—stores and retrieves settings JSON documents.
• YouTube Data API: after explicit subscription-list connection, reads current subscriptions, limited channel metadata, latest public-video publication times, and public channel topic categories for Channel Folders. It removes subscriptions only after a separate selection and confirmation flow. The developer does not receive these requests or results.

The extension shares no data with advertising networks, analytics providers, data brokers, or developer-operated services.

6. Permissions

• storage: saves preferences, synchronization metadata, a random device identifier, the connected-account renewal hint, and the short-lived latest-video check cache locally and reads legacy synchronized preference keys during one-time migration.
• identity: opens the browser's OAuth web-auth flow after an explicit action. Initial Drive connection requests https://www.googleapis.com/auth/drive.appdata. If the user later chooses to connect subscriptions in Channel Folders, the extension incrementally requests https://www.googleapis.com/auth/youtube to view and manage current subscriptions and perform user-confirmed unsubscription. No separate email/profile OAuth scope is requested.
• alarms: schedules optional settings synchronization approximately every two minutes and provides a fallback for deferred uploads while the service worker is suspended.
• https://www.youtube.com/*: runs packaged scripts and styles on YouTube pages to apply selected player, layout, list-filter, chapter, summary, caption, playlist, recommendation, and Shorts features.
• https://www.googleapis.com/*: calls the Drive API for app-only settings/channel data and, after explicit subscription connection, calls the YouTube Data API to read subscriptions or perform user-confirmed unsubscription.
• https://oauth2.googleapis.com/*: requests revocation of the current OAuth access token when the user disconnects the account.

The extension does not request identity.email, tabs, activeTab, scripting, browsing-history, cookies, or web-request permissions.

7. Advertising, Analytics, and Remote Code

• No advertising, analytics, tracking, or telemetry is included.
• The extension does not download or execute remote code. All executable logic is included in the extension package.
• Interacting with YouTube's existing page and native Ask service does not download executable logic into the extension.

8. Retention and User Control

• Local preferences remain in Chrome storage until the user resets or removes the extension or clears its storage. A legacy synchronized copy from an earlier version may remain temporarily for rollback compatibility until the user removes synchronized data or a later migration explicitly cleans it up. The developer cannot access or delete either copy.
• Current page state, chapter data, interaction events, and the extension's temporary summary copy are discarded when no longer needed, including on navigation, reload, tab closure, or feature disablement as applicable.
• Google OAuth access tokens remain only in service-worker memory and chrome.storage.session and are silently renewed when Google permits it. Disconnecting disables sync, clears the locally stored email renewal hint and session token, and requests token revocation, but does not delete existing appDataFolder data.
• Cloud settings.json and the five newest backups remain when sync is turned off or the account is disconnected. Restoring creates a safety backup first. Sync OFF and Disconnect do not imply cloud-data deletion.
• Users can remove the extension's cloud files from Google Drive by opening Google Drive storage settings, selecting Manage apps, opening this app's Options, and choosing Delete hidden app data. This deletion is controlled by Google Drive and cannot be undone by the extension.
• Local channel folders and assignments remain until edited/reset, extension removal, or storage clearing. If channel sync is enabled, channel-library.json remains in appDataFolder after sync is turned off or the account is disconnected. The subscription-list memory cache expires after approximately five minutes. Latest public-video publication/check timestamps remain only on the current device and refresh after approximately 12 hours. Public topic categories remain in service-worker memory for approximately 12 hours. Disconnecting clears these caches. Confirmed YouTube unsubscription is not restored by extension folder data.
• Legacy data retained by Chrome Sync and data retained by YouTube are controlled by Google and the user's Google/Chrome settings and are subject to Google's policies.

9. Security

• Google OAuth and API requests use HTTPS/TLS connections to Google's authorization, Drive, YouTube Data API, and token-revocation endpoints.
• OAuth access tokens are handled only in the extension's background service worker and chrome.storage.session; they are not sent to or stored on a developer-operated server.
• Drive access is restricted to the hidden appDataFolder. The extension does not request access to the user's general Drive files.
• The extension requests YouTube subscription access only after a separate explicit connection action and performs removal only after the user selects targets and confirms the warning.

10. Limited Use

Information is handled only to provide or improve the extension's disclosed single purpose and user-facing features. It is not used for advertising, creditworthiness, unrelated analytics, or sale to third parties, and the developer does not permit humans to read it.

The use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

11. Policy Changes

If information-handling practices change, this policy, the Chrome Web Store disclosures, and any required in-product disclosure will be updated before the changed practice takes effect.

12. Contact

Questions about this policy may be sent to ohnagi@gmail.com.