Metadata-only protection for YouTube playlists.

TrackRescue monitors playlist availability, preserves missing video context, and keeps users in control of repair actions without storing audio or video content.

What TrackRescue collects

  • Account information such as name, email address, verification status, account settings, and the Google profile photo when the user signs in with Google and has not selected a custom avatar.
  • YouTube account channel id, channel name, and channel country when YouTube provides it after OAuth connection.
  • A two-letter primary playback country and its selection source are stored to evaluate YouTube regional restriction metadata. TrackRescue first uses the country reported by Cloudflare for the current request, then the connected YouTube channel country, then a region-bearing browser language. The raw network address is not stored for this setting, and the user can change the country in Settings.
  • Playlist metadata: playlist id, title, privacy status, thumbnail, item count, and scan timestamps.
  • Playlist item metadata: video id when available, title, channel, owner channel, position, thumbnail, availability status, and first/last seen dates.
  • Repair decisions, undo records, export history, and notification preferences when those features are enabled.
  • Billing status, subscription plan, and Dodo Payments customer/subscription identifiers when paid checkout is enabled.
  • The public Playlist Health Checker temporarily caches public or unlisted playlist metadata and its diagnostic result for six hours. A keyed one-way hash of the requester's network address is retained briefly to enforce the two-check daily abuse limit; the raw address is not stored in the checker tables.

What TrackRescue does not collect

  • No audio files are downloaded, stored, copied, or redistributed.
  • No YouTube video playback content is extracted outside official YouTube APIs.
  • No playlist data is sold or used for advertising profiles.
  • No scraping or non-API YouTube access is used.
  • No full card numbers or payment credentials are stored by TrackRescue.

How Google user data is used

  • Google user data is used only to provide account sign-in, show the user's Google profile photo when no custom avatar is selected, scan selected YouTube playlists, and show playlist repair status.
  • Read-only access is requested first. Write access is requested later only for user-approved repair actions.
  • OAuth tokens are stored only to keep the user connected and to run authorized scans.
  • Users can disconnect a YouTube account or delete all TrackRescue data at any time.

Google user data sharing and disclosure

  • TrackRescue does not sell, rent, trade, or use Google user data for advertising, profiling, or unrelated product analytics.
  • Google user data is not shared with advertisers, data brokers, music distributors, or public users.
  • Google user data is disclosed only to service providers that are necessary to run TrackRescue, such as secure hosting, database, email delivery, logging, and payment/subscription systems.
  • Those service providers may process only the data needed to provide their service to TrackRescue and are not allowed to use Google user data for their own independent purposes.
  • When a user explicitly runs Deep Recovery for an unavailable playlist entry, TrackRescue may send only that public YouTube video id or watch URL to the Internet Archive to look for archived public title and channel metadata. TrackRescue does not send the user's email, OAuth token, private playlist data, or account identity with that request.
  • TrackRescue may disclose limited data if required by law, legal process, security investigation, or to protect the rights and safety of users and the service.

Google user data protection

  • Google OAuth tokens and playlist metadata are stored on protected servers and are not exposed in public pages, client-side code, exports, or emails.
  • Transport security is enforced with HTTPS for the public app and API requests.
  • Access to Google user data is limited to authorized TrackRescue backend processes needed for playlist scanning, repair actions, user-requested exports, support, and account deletion.
  • Secrets, OAuth credentials, and SMTP credentials are stored in server environment configuration, not in frontend source code.
  • TrackRescue keeps operational logs for reliability and abuse prevention, but those logs are not used to reconstruct or redistribute YouTube audio or video content.

Google user data retention and deletion

  • Google user data is retained only while the user keeps a TrackRescue account or a connected YouTube account and the data is needed for playlist monitoring, repair history, exports, billing status, or account support.
  • Users can disconnect YouTube at any time. Disconnecting removes stored OAuth tokens and stops future scans for that YouTube account.
  • Users can request full deletion from the Delete Data page. Deletion removes the local TrackRescue account, profile photos, YouTube connections, OAuth tokens, imported playlist metadata, scan history, repair records, notification settings, and active session data from TrackRescue systems.
  • Backup copies and security logs may remain for a limited period only as required for security, legal, accounting, fraud-prevention, or disaster-recovery purposes, and are then deleted or overwritten according to normal operational cycles.
  • After deletion, TrackRescue does not continue scanning the user's playlists unless the user creates a new account and reconnects YouTube again.
  • Expired public Playlist Health Checker results are removed after the short cache window, and hashed daily abuse-control counters are removed after eight days.

Payments and contact

  • When paid checkout is enabled, Dodo Payments acts as Merchant of Record and processes subscription payments, applicable taxes, and payment method data for TrackRescue.
  • TrackRescue does not receive or store full card numbers. Dodo Payments may process billing details, transaction data, invoices, and receipts under its own privacy terms.
  • TrackRescue receives only the customer, subscription, payment-status, and billing references needed to activate, update, or cancel access.
  • Privacy or account requests can be sent to support@trackrescue.cloud or handled from the account data deletion page.

Website analytics and cookies

  • TrackRescue uses optional Google Analytics 4 only after the visitor allows analytics storage.
  • Analytics may process page URLs, browser and device details, approximate location, referral information, and interaction events to measure website and product usage.
  • Google Analytics does not receive YouTube OAuth tokens, playlist metadata, missing-video records, repair decisions, account email addresses, or payment credentials from TrackRescue.
  • Advertising storage, advertising personalization, and advertising user data remain disabled.
  • The analytics choice is stored in the visitor's browser and can be changed below.

Chrome extension data handling

  • The TrackRescue Chrome extension reads the active tab URL only while its side panel is open and only to identify a supported YouTube playlist or video. It does not read page contents, monitor unrelated tabs, or retain a browsing history.
  • Only the detected YouTube playlist or video identifier needed for the requested protection, scan, candidate, or repair action is sent to the TrackRescue API over HTTPS.
  • The extension stores a separate revocable TrackRescue session token, its expiry, device reference, and the pending-repair count in Chrome local storage. The server stores only a hash of the session token.
  • The extension receives the account display name, plan status, selected playlist metadata, scan state, and repair information needed to render the side panel and complete user-requested actions.
  • Local notifications are used only when the number of pending repairs increases. Extension data is not used for advertising, sold, or transferred for unrelated purposes.
  • The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Last updated

Last updated: July 20, 2026.