Privacy Policy

Updated September 17, 2026

This policy describes how FeedFit handles data to organize your YouTube feed, provide Google sign-in, manage PRO access, and offer optional manual account backup and restore. Contact the FeedFit operator at os1739@gmail.com.

YouTube content and local preferences

FeedFit reads the current YouTube page and information about displayed videos, including video identifiers, titles, channel names, channel identifiers or handles, and links. It processes button selections and page navigation or scrolling as needed to hide content, prioritize channels, skip hidden Shorts, and display controls. Preference lists, exceptions, settings, and supporting video or channel metadata may be stored locally in your browser. This is not a service for collecting your complete browsing or viewing history, keystroke logs, or chat messages. Selecting “Not interested” sends feedback through YouTube's own interface.

Google sign-in and authentication

Free local features do not require Google sign-in. When you sign in, Google and Firebase Authentication process your identity information. FeedFit uses your account identifier and email to identify your account, display your email, and associate your subscription and cloud preferences with you. The sign-in flow requests Google identity, email, and profile scopes. FeedFit does not ask for or store your Google password. Firebase session and refresh tokens are stored in the extension's local IndexedDB to maintain sign-in. Signing out clears the stored session but does not delete your Firebase account.

Optional PRO backup and restore

When an eligible PRO user selects Back up, FeedFit sends supported lists and filter settings to its authenticated API and stores them in one Firestore document associated with the account. These include preferred and hidden channels, hidden Shorts channels, hidden video identifiers, exceptions, and supported filtering or display settings. Restore downloads that backup to the current device. Each operation requires confirmation before replacing the existing account backup or local settings. Not every local preference or cache is included. Version 0.7.73 and later do not automatically upload or download lists. Earlier versions may continue automatic synchronization until updated or synchronization is disabled. Free accounts cannot use this backup service. Authentication and subscription checks remain separate. Firestore is in the United States (nam5), and the API runs in us-central1.

Live payments and subscription records

Paddle processes live PRO payments as Merchant of Record under its Privacy Notice. The separate checkout page loads Paddle's checkout software. Payment and billing details you enter are processed by Paddle and its payment providers. FeedFit does not store full card numbers or card security codes.

FeedFit links checkout, transaction, subscription, and payment-event identifiers to your authenticated account. It stores subscription and entitlement status, access-expiry dates, and processing timestamps to provide paid access, manage cancellations or refunds, and prevent duplicate checkout requests. Signed payment notifications update these records. Sandbox testing uses separate records and does not represent a real payment.

Technical information and security

Website and API requests include technical information such as IP addresses and browser headers. FeedFit uses request IP addresses and account identifiers in temporary server-memory rate limits to reduce abuse; it does not request GPS location. Google hosting and cloud services may retain operational request and error logs under their own retention settings. Data sent to our authentication, backup, and payment services uses HTTPS. Access to cloud preferences is checked against the signed-in account and PRO entitlement.

Use, sharing, and Limited Use

We use data to provide and maintain FeedFit's stated features, authenticate users, back up and restore preferences, manage subscriptions, respond to support requests, and secure the service. Necessary data is processed by Google/Firebase for authentication and hosting and by Paddle and its payment providers for billing. We do not add advertising or analytics trackers to the information website. The website stores your selected language locally.

FeedFit's use and transfer of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We do not sell user data, use or transfer it for purposes unrelated to FeedFit's stated functionality, use it for personalized advertising, or use it to determine creditworthiness or for lending. Transfers are limited to permitted purposes such as providing the service, security, or legal obligations. Human access to user data is limited to permitted circumstances, such as support with your consent, security investigations, or legal requirements.

Control, retention, and deletion

You can remove or reset preference lists in the extension. Local changes do not update an existing account backup until you select Back up. Signing out does not delete local lists or existing cloud records. Uninstalling the extension does not delete your cloud account or cancel a subscription. Subscription cancellation is available through subscription management.

Account, backup, and billing records currently remain until deletion is requested or performed; there is no automatic inactivity-deletion schedule. To request access, correction, or deletion of account or cloud data, contact us from your account email. We may verify ownership. Records necessary for legal, accounting, security, or dispute-resolution purposes may need to be retained. Provider backups, operational logs, and Paddle's records follow their respective retention practices. Support messages are used to handle your request.

Provider information: Firebase privacy information · Google Privacy Policy · Paddle Privacy Notice.