Privacy Policy for ezy Youtube Video Control

Last updated: October 24, 2026 (v3.4.5)

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 and popup state: player, layout, list-filter, caption, playlist, Shorts, chapter-dot, video-summary, keyboard-shortcut, per-channel/per-folder tuning-profile, and sleep-timer settings; popup navigation state; favorite and recently changed setting keys/timestamps; and 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.
• Bilingual captions: only when the user enables caption optimization and selects original + translated captions, the extension loads the selected video's original caption text and translation from youtube.com using the current player's same-origin caption requests. Caption text is held only in the current tab's memory for synchronized display and is discarded on navigation, feature disablement, or tab closure. It is not uploaded to Drive or sent to the developer or another translation service.
• Local video feature records: when the related feature is used, the extension stores a YouTube video ID with its selected playback speed, resume position, duration, and update timestamps. A user-created bookmark stores a video ID, playback position, optional note, and creation time. The playback queue stores up to 200 video IDs plus ordering, played-state, item, claim, owner-tab, lease, and acknowledgement metadata needed to prevent multiple YouTube tabs from consuming the same item, preserve the user's chosen order and played-item preference, and recover across service-worker restarts.
• 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.
• Promotional banner in the popup: when the popup is opened in a layout large enough to include it, the extension requests a small banner-configuration JSON file (image URL, destination link, label, and display schedule) from the developer's static server at app.ezy.kr. The JSON request uses credentials: "omit". Successful, disabled, invalid, and failed attempts are cached in the current browser profile for a limited period when extension storage is available, so another configuration request is not normally made while that cached result is still valid. When a validated banner is displayed, the browser loads its image from an ezy.kr host as a normal cross-origin image with a no-referrer policy; this image request follows the browser's normal credential policy and therefore may include cookies already associated with that host. The extension code does not add an extension-generated identifier, preference, Google account value, current URL, video identifier, or page content to either request. As with ordinary resource delivery, the hosting infrastructure receives the requesting IP address and standard request headers and may temporarily retain standard access logs for operation and security. The extension sends no separate impression beacon, click beacon, tracking pixel, or analytics identifier. The banner promotes the developer's own ezy apps, and destination links are restricted to ezy.kr and apps.microsoft.com.
• 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, general Drive files, or any YouTube OAuth scope. The account connection is used only for the optional synchronization and backup features; no subscription feature requires it. 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. When the user opens the channel manager while signed in to YouTube in the current tab, the extension reads the subscription list — subscription IDs and the subscribed channels' IDs, titles, page URLs, and thumbnail URLs — directly from youtube.com through the same internal web endpoints the YouTube page itself uses, under the current tab's existing YouTube login session. No Google sign-in, OAuth scope, or YouTube Data API access is used for any subscription feature. Each channel's latest public-video publication time comes from YouTube's public RSS feed, requested without any credentials.
• YouTube session signing values: to authenticate those same-origin subscription requests the way the YouTube page does, the extension reads the current tab's YouTube session values — the SAPISID (or __Secure-3PAPISID) cookie and the page's account-identification values (SESSION_INDEX for multi-login accounts and DELEGATED_SESSION_ID for brand accounts). The cookie value is used transiently in memory only to compute the SAPISIDHASH request signature; it is never stored, never logged, and never sent anywhere except youtube.com itself. If the user is signed out of YouTube, the extension only shows guidance and sends no request.
• Optional YouTube subscription removal: only after the user opens a subscribed channel's row action in the channel manager, presses the separate unsubscribe control for that one channel, and confirms an inline warning that names the channel, the extension sends one unsubscribe request for that channel to youtube.com through the same session-based endpoint the YouTube page itself uses. Before sending, it re-checks that the channel is still in the current subscription list and sends nothing if it is not. Folder deletion, moving a channel between extension folders, and the "clean up unsubscribed channels" action never unsubscribe the user; the clean-up only removes library records for channels YouTube already reports as unsubscribed.

The extension does not read Chrome's general browser-history database or build a general list of pages visited. It does retain the feature-specific video IDs, resume/speed records, bookmarks, and queue entries described above on the current browser profile.

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. Only the specific video-state, bookmark, and queue fields disclosed in section 2 are retained locally; the extension does not store a general page-content or visit log.
• 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.
• The YouTube subscription list is read only in the current tab, under the tab's existing YouTube login session, when the user opens or refreshes the channel manager. No Google account connection is required for any subscription feature, and the session cookie used to sign these requests is used in memory at the moment of signing and sent only to youtube.com. 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 repeated network requests, latest public-video publication and check times from the public RSS feed are cached only on the current device for approximately 12 hours and are not uploaded to Drive. Unsubscribe requests are never scheduled and never result from folder editing.
• The developer receives no preferences, page content, prompts, summary responses, analytics, or telemetry from the extension. The only developer-operated resources contacted by the extension are the static promotional-banner configuration and image described in section 2; those resource requests carry only the standard network metadata described there, not extension feature data.

4. Video Summary: YouTube Ask Processing

• Navigating to another video discards any pending confirmation or in-progress request, so a confirmation given for one video is never sent in the context of another.
• 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 (youtube.com): while Channel Folders is enabled, the extension sends the same-origin subscription-list requests and user-confirmed unsubscribe requests described above to youtube.com under the user's existing YouTube login session, and fetches public, credential-free RSS feeds for latest-upload times. These requests go only to youtube.com and are processed by YouTube under the user's account and Google's policies; the developer does not receive them. The YouTube Data API is not used.
• Developer's static promotional server (app.ezy.kr): serves the credential-free JSON configuration and the banner image described in section 2. The image is loaded under the browser's normal image credential policy and may include cookies already associated with its host. The extension code does not directly attach an extension identifier, Google account value, setting, current URL, video identifier, or page content; the hosting infrastructure still receives standard network metadata such as the IP address and request headers.

The extension shares no extension preferences, account values, browsing content, or extension-generated identifiers with advertising networks, analytics providers, or data brokers. Standard network metadata involved in delivering the first-party promotional resources is handled as described above.

6. Permissions

• storage: saves preferences and device-local UI state; synchronization metadata and a random device identifier; the connected-account renewal hint; channel-folder/library data; per-video speed/resume records; user-created bookmarks; the playback queue and its coordination metadata; sleep-timer and tuning-profile state; short-lived latest-video metadata; and the short-lived promotion configuration/attempt cache. It also reads legacy synchronized preference keys during one-time migration.
• identity: opens the browser's OAuth web-auth flow after an explicit action. The only OAuth scope requested is https://www.googleapis.com/auth/drive.appdata, used for the optional settings and channel-library synchronization and backups. No YouTube OAuth scope and 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, and, while Channel Folders is enabled, sends the same-origin subscription-list, user-confirmed unsubscribe, and public RSS requests described above.
• https://www.googleapis.com/*: calls the Drive API for app-only settings/channel data. It is not used for the YouTube Data API.
• 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

• The popup may show one clearly labeled promotional banner for the developer's own ezy apps, configured by the static JSON file described in section 2. No third-party advertising network, ad SDK, ad auction, or personalized ad targeting is involved.
• No analytics, tracking, or telemetry SDK is included. The extension sends no dedicated impression, view, or click beacon and no extension-generated identifier. Ordinary JSON/image delivery can still appear in the hosting infrastructure's standard access logs, and opening a destination necessarily sends a normal navigation request to that destination.
• The extension does not download or execute remote code. All executable logic is included in the extension package; the banner configuration is plain JSON data that packaged code validates before use and is never executed.
• 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.
• A sleep-timer end time is removed when the timer finishes or is cancelled. Favorite setting keys remain until unstarred; the recent-changes list keeps at most 20 setting keys with timestamps as newer changes replace older ones. Per-channel/per-folder tuning profiles remain until individually removed or extension storage is cleared. These device-local UI records are not uploaded to Drive.
• 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.
• Per-video speed, resume position, duration, and timestamps are stored only on the current browser profile. The store is capped at 500 video records. Records older than about 180 days and least-recently-updated overflow records are removed during a later video-state write, so an expired record can remain if no later write occurs. The user can remove all indexed video-state records with Settings → Local data → Delete all. Finishing at least 90% of a video removes its resume position while preserving its saved speed.
• User-created bookmarks are stored only on the current browser profile, up to 1,000 entries. Each remains until removed individually, extension storage is cleared, or the extension is removed. The Local data → Delete all control intentionally does not delete bookmarks.
• The playback queue is stored only on the current browser profile, up to 200 unique video IDs. Entries remain until playback is acknowledged, removed, or cleared. A queue claim includes opaque claim/item/owner tokens and the consuming tab ID under an approximately two-minute lease; expired claims are cleaned during a later queue operation. The last acknowledgement receipt can remain until replaced or extension storage is cleared.
• 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.
• 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 and disappears when the page unloads. Latest public-video publication/check timestamps remain only on the current device and refresh after approximately 12 hours. The session cookie value used for request signing is never retained. Confirmed YouTube unsubscription is not restored by extension folder data.
• The promotional-banner configuration, or a null result recording a disabled, invalid, or failed attempt, is cached locally in chrome.storage.local for a limited period. It is replaced once that period elapses, or removed when the user clears extension storage.
• 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. Limited Use

YouTube page information, Google API information, and locally stored extension-feature data are handled only to provide or improve the disclosed user-facing features. They are not used to select or personalize promotions, determine creditworthiness, run unrelated analytics, or sell data, and the developer does not receive their contents. Standard network metadata created when the first-party promotional resources are requested is used only to deliver those resources, operate and secure the host, and meet legal obligations; authorized operators may access server logs only when reasonably necessary for those limited purposes.

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

10. 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.

11. Contact

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