YTSubSearcher privacy policy

Access to data

When you select “Sign in with Google”, Google opens its own sign-in and consent window. After consent, the extension receives an OAuth access token, a refresh token and the Google account’s technical identifier (sub). The identifier separates data belonging to different accounts; tokens authorize the requested API calls. Your Google password is entered on Google’s pages and is not provided to the extension. The extension does not separately request your profile name, email address or profile photo.

YouTube permission is used only for reading data. The extension does not subscribe to channels, publish videos or modify YouTube data. The search date and filter settings are processed locally.

Through the YouTube Data API, the extension reads the selected account’s subscriptions: channel identifiers and names, information about the account’s YouTube channel and upload playlists, and public metadata for videos from those channels: video identifier, title, channel, publication time, duration and thumbnail URL. This data is used to find videos specifically from your subscriptions, filter them by date and duration, and display links to matching results. Cached metadata reduces repeated API requests.

The day, month and year you enter, the selected duration groups and your time zone are used for local filtering. Your search date is not sent to the developer or used for advertising or profiling.

Data sharing

The extension sends authorization and token-refresh requests to Google, subscription and metadata requests to the YouTube Data API, and thumbnail requests to i.ytimg.com. OAuth tokens are sent to Google to authorize API requests; Google and YouTube also receive ordinary network information such as your IP address. Opening a result takes you to the selected video on YouTube, where Google’s and YouTube’s policies apply.

The extension has no developer-operated server that receives user data. The developer does not receive or inspect your tokens, account identifier, subscriptions, search filters or results. They are not sold, rented or shared with advertisers, data brokers or artificial intelligence services. The extension contains no advertising or analytics.

Local storage

OAuth tokens and the technical account identifier are saved in the extension’s local storage within your Firefox profile, so you do not have to sign in again for every search. The extension does not synchronize them between devices. Do not publish or share a backup of your browser profile.

Cached channel metadata, search settings and results are stored locally. The cache remains current for 6 hours after a channel scan finishes; current search results are retained for up to 6 hours after the search finishes or the last results are received. Expired records are deleted when the extension starts, before a search and approximately once a minute while Firefox is running. If Firefox is closed or the device is asleep, deletion takes place when operation resumes. Changing the filter does not extend the retention of earlier results.

Authorization data is retained while your account is connected. Google sets the access token’s lifetime; a refresh token allows continued use without signing in again. Signing out or uninstalling the extension removes locally stored authorization data. Google may independently revoke tokens or limit their lifetime.

Deleting data and revoking access

“Clear” clears the date and results. “Clear cache” deletes the local cache and results without signing out of Google. “Sign out” deletes local tokens, the account identifier, the cache, settings and results. These actions do not delete subscriptions or videos on YouTube.

To revoke access granted through Google, remove the app’s permissions in your Google account’s connection settings. You may need to sign in again afterwards. Uninstalling the extension deletes its local storage.

To disconnect fully, select “Sign out” and then revoke access in your Google account settings. Clearing the cache does not revoke Google permission, and revoking permission alone does not guarantee deletion of already cached local data. The developer cannot remotely clear your Firefox profile because no copy of the extension’s user data is kept on a developer server.

Use of Google data

YTSubSearcher’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data access is limited to finding videos from subscriptions and displaying results to the user. Data is not used for advertising, credit assessment, artificial intelligence model training, or image or video generation.

Google API Services User Data Policy and Limited Use

Google APIs Terms of Service

YouTube and short videos

YouTube is the source of videos and metadata. The “Possible Shorts” group means videos lasting no more than 3 minutes; it does not confirm that they are Shorts. The extension does not fetch YouTube pages to determine the format automatically and does not embed a video player.

By using YouTube features in the extension, you also agree to the YouTube Terms of Service. Information about how Google handles data is available in the Google Privacy Policy.

Google permissions and their purpose

openid: provides the selected Google account’s technical identifier so that locally stored data can be associated with that account. It does not give the extension access to all Google services.

https://www.googleapis.com/auth/youtube.readonly: permits reading subscriptions and channel and video information for the search. Access is read-only; it is not used to publish, change or delete videos, subscriptions, comments or other account data.

Data protection

Remote authorization and Google API requests use HTTPS. Sign-in uses PKCE and a state parameter to check the authorization response. Tokens are kept in the extension’s local storage; cached data is kept in the Firefox profile’s IndexedDB. Protection on the device depends on Firefox, your operating system and access to your browser profile. Do not share tokens or your browser profile backup with other people.

Public website and support

The homepage and this policy are publicly accessible without signing in to Google or GitHub. The site is hosted on GitHub Pages. The hosting provider may process network information about visits under GitHub’s policies. The website itself does not request access to a Google account and does not contain the extension’s Google OAuth tokens.

The site stores only your selected language in your browser’s localStorage under the key ytss-homepage-language. This preference is not sent to the developer; you can remove it by clearing this site’s browser data. The website contains no developer-added analytics or advertising trackers.

If you choose to email dd.nikolaenko@gmail.com, the developer receives your sender address and message content to respond to your request; the email service processes the message. Do not include passwords or OAuth tokens. Use the same address for privacy questions or requests to delete information you voluntarily supplied.

GitHub Privacy Statement

Policy changes

The current policy is published on this page with its update date. If the use of Google user data changes, this policy and the extension’s corresponding disclosures must be updated before that use begins; renewed Google consent will be requested when required.

Contact the developer

Suprastin0311. Questions and data deletion requests: dd.nikolaenko@gmail.com