Trust & data

Saucefox lets creators publish downloadable resources associated with their YouTube channels. The current beta can use a read-only subscription verification before making a resource available; this access model is being submitted to YouTube for a compliance determination. This page explains precisely what happens when a viewer starts verification.

What we can see

• Whether the YouTube account you sign in with is subscribed to this creator's channel — a yes/no answer.
• The identifier of your own YouTube channel, which we immediately convert into a salted, non-reversible hash so your unlock can be remembered for 30 days without storing who you are.

What we cannot do

• We cannot see your Google email address, name, or photo — we do not request them, and the consent screen you see asks for a single read-only permission: “View your YouTube account.”
• We cannot post, comment, like, subscribe, upload, edit, or delete anything on your account. The permission is read-only, and Saucefox performs no write operations of any kind.
• We cannot keep access to your account. We request no long-lived access: the temporary token exists only while your subscription is being checked and is discarded immediately. Access and refresh tokens are never stored.

Exactly which API calls we make

With your temporary permission, Saucefox calls exactly two read-only YouTube Data API endpoints, once each:

• channels.list(part=id, mine=true) — to derive the anonymized identifier described above;
• subscriptions.list(mine=true, forChannelId=…) — to check whether you are subscribed to this one creator.

We do not read your subscription list, watch history, playlists, comments, or anything else.

What we store

• The anonymized (salted, hashed) identifier and the verification result.
• Raw verification records are kept for a maximum of 30 days, then deleted automatically. Aggregate funnel counters contain no viewer identity.

What we never store

• Your subscription list.
• Your email address — unless you type it yourself into an optional form.
• Your name or photo.
• OAuth access or refresh tokens.

No trackers on vault pages

Public vault pages use no third-party analytics, no advertising scripts, and no analytics cookies. The only cookie is the strictly necessary unlock cookie that remembers your successful verification for this creator.

Google API Services User Data Policy

Saucefox's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Your control: revoke and delete

Revoke Saucefox at any time from your Google Account permissions. Because Saucefox discards the temporary access token immediately, it cannot use that token later. To delete your pseudonymous verification data, email support@saucefox.com. We complete valid deletion requests as soon as possible and no later than seven calendar days.

YouTube and Google terms

Saucefox uses YouTube API Services. By using the YouTube-connected features, you agree to the YouTube Terms of Service. Read the Google Privacy Policy. Saucefox is not endorsed by or affiliated with YouTube or Google.

Questions

Write to support@saucefox.com. See also our Privacy Policy and Terms of Service.