YTProof
Privacy Policy.
Last updated
YTProof gives creators a public profile for sharing selected YouTube statistics and cards. This policy explains how YTProof, available at www.ytproof.com, handles your information. For privacy questions or deletion requests, contact hello@ytproof.com.
You control which statistics you select. Every successful card export publishes the video and its statistics record on your public profile. Revenue calendars stay private unless you enable public visibility. We do not sell personal information or use Google data for advertising.
1. Account and profile information
When you create an account, we use your email address, username, account identifier and authentication information to provide sign-in, confirmation, recovery and account support. Passwords are hashed by our authentication service. Google sign-in supplies your Google account identifier, email address and, when provided, your name and profile photo. It does not by itself connect your YouTube channel.
We store the profile details you choose, including your handle, display name, photo, bio, links, appearance settings and visible badges. These chosen profile details are public. Your email address, authentication tokens and private channel-access records are not displayed on your profile or cards. We also store account creation information, your UID, badge awards and paid-feature access so those features work.
2. Google and YouTube information
YTProof uses YouTube API Services. Connecting YouTube is a separate Google consent flow, where you choose the Google account or channel and approve read-only permissions. We never ask for or receive your Google password. We do not upload to, edit or delete content on your YouTube channel.
The youtube.readonly permission lets us identify authorised channels and retrieve their names, channel identifiers, thumbnails and current reported view and subscriber totals. The yt-analytics-monetary.readonly permission allows read-only analytics, including estimated revenue. We use it to retrieve views, subscriber gains and losses, and estimated revenue for the reporting periods and revenue-calendar months you request. YouTube rounds current subscriber totals; estimated revenue can be delayed or revised.
We use these responses to show your private statistics preview, generate the card you request, maintain its original statistics record and provide your revenue calendar. The permissions cover broader reports than the fields we currently retrieve. Selecting a statistic for a card does not make all of your channel analytics public. Non-monetised channels can use available view and subscriber statistics without publishing revenue.
Google explains its own practices in the Google Privacy Policy. You can remove YTProof’s access through Google account security permissions. The YTProof Terms also link to the YouTube Terms of Service.
3. Google API data and Limited Use
We comply with the Google API Services User Data Policy, including its Limited Use requirements, for information received from Google APIs.
We use Google user data only to provide or improve the user-facing features described in this policy. We do not sell it, use it for targeted advertising, transfer it to data brokers, use it for lending or credit decisions, or train general-purpose AI or machine-learning models with it.
We transfer Google user data only as needed for the features you request and consent to, security and abuse prevention, legal obligations, or a business transfer with your prior explicit consent. Human access is limited to your specific affirmative permission, necessary security investigations, legal obligations, or internally aggregated information permitted by the Limited Use rules. Paying for Premium does not grant additional access to your Google data.
4. What is public and who receives information
Public profiles and cards: when you export, we publish the original video, its poster and the selected statistics record. Visitors can view and download them. The record includes selected values and periods, revenue currency where relevant, publication time, availability information and a file fingerprint. Connected records also show the fetch time and channel count. Channel names are hidden unless you enable disclosure. Anonymous video styling hides identity on the video; it does not make the linked profile or record private.
Revenue calendars: these are private by default. Enabling “Show on public profile” shares saved daily estimated amounts for the months you sync. Turning it off blocks public calendar access. These amounts can include financial information, so enable sharing only when you want visitors to see them. Playground figures are supplied by the creator and are distinguished from API-retrieved statistics on their original record pages.
Service providers: Supabase processes authentication, account and profile records, private reports, encrypted connection records and media storage. Vercel provides website hosting and temporary rendering of the card’s selected statistics and uploaded media. Google processes authentication, consent and API requests. These providers receive information needed to perform those functions on our behalf, under their service arrangements. We do not send Google passwords or expose access tokens to profile visitors.
Payments: Whop handles optional Premium checkout. If offered, separate Stripe Checkout purchases handle custom badges or other paid features. We send our internal account identifier and purchase type to associate checkout with your account, and store payment or membership references, status and access dates. We do not send YouTube earnings or analytics to payment providers, and YTProof does not store payment card numbers. Payment providers process the details you give them under their own policies.
Other disclosures: we may disclose information when legally required or necessary to address fraud, abuse or security incidents, subject to the Google-data restrictions above. Public profile links take you to independently operated services. Loading externally hosted profile images can send ordinary connection information, such as an IP address, to that image host. Downloaded or independently copied public content remains outside our control.
5. Media and file comparison
Media previews run in your browser. Export uploads the background and audio you select to private temporary storage so our renderer can create the original card. Inputs are removed after successful rendering or cancellation; scheduled cleanup removes expired or abandoned uploads. The resulting video and poster are served publicly with the card. Do not upload material you do not have permission to use.
Comparing a file with an original card uses its SHA-256 fingerprint locally in your browser. The file selected for comparison is not uploaded to YTProof. An edited or re-encoded video can have a different fingerprint.
6. Cookies and profile visitor analytics
We use HTTP-only session cookies to maintain sign-in and short-lived OAuth state to validate connection requests. Supabase session refresh tokens maintain your YTProof account session; they do not grant YouTube API access. We do not store YouTube access tokens or earnings in browser local storage. A chosen editor display name may be saved locally.
Visitor counting uses a random HTTP-only visitor cookie, lasting up to one year, and keyed hashes of the cookie identifier and connection IP address to reduce repeat counts. This feature does not store raw IP addresses or use browser fingerprinting. It stores a first-visit date and broad device category. Shared networks can count as one visitor. Profile owners see aggregate counts, not visitor identities; their own visits and recognised bots are excluded. Visitor records remain until the profile owner deletes the account. Hosting providers may process IP addresses and request information in operational or security logs.
7. How long we keep information
Account and profile information remains while your account exists. Creator-entered Playground cards remain until you delete the card or account. Badge and purchase-access records are kept to provide those features. Payment providers may retain transaction records separately for their legal and accounting obligations.
YouTube access and refresh tokens are encrypted on the server. When you connect a channel, we request renewable read-only access so normal access-token expiry can be handled automatically while you remain signed in. Google may revoke or expire that renewal permission. Channel credentials expire after thirty days without a successful renewal, or earlier when Google supplies a renewal expiry; renewed access extends that thirty-day window. Signing out or disconnecting removes the relevant session's channel access. Tokens never go to the browser extension. Private statistics snapshots can be used for up to fifteen minutes and require an active owned channel connection. Expired credentials and snapshots are rejected and removed by scheduled cleanup.
New connected historical cards remain available only while access to every original channel is reconfirmed within each 28-day window. Reconnecting renews the access check without rewriting the historical statistics. Without reconfirmation, connected records and media expire. Older connected records without renewal information expire on their recorded date. Calendar reports expire 28 days after sync. Private channel identifiers and access-check dates support renewal and are not shown to profile visitors.
Expired cards and calendars stop being served by YTProof before physical cleanup. Daily scheduled cleanup removes expired records, associated media, connection tokens, temporary consent state and abandoned rendering data. Successfully deleting a card or account removes its associated media from active storage. A copy already downloaded by another person cannot be recalled.
8. Disconnecting, deleting and accessing your data
Use your account dashboard to edit profile details, remove individual cards, change calendar visibility, disconnect YouTube or delete your account. Signing out clears that session’s private channel connections and temporary statistics snapshots. Published cards and saved calendar months can remain until their stated expiry or until you remove them.
Disconnecting YouTube removes stored connections, reports and published connected cards, and requests token revocation from Google. If Google is temporarily unavailable, an encrypted token may be held for a revocation retry until it expires. Account deletion removes your account, profile, sessions, cards, associated media, visitor records and stored API data. Neither action deletes your YouTube channel or information held independently by Google.
You can also revoke consent directly in Google account security permissions. When revocation is detected, we remove affected connected records. In-app disconnection removes associated authorised data promptly; externally revoked data is removed on detection or expiry and cleanup, within 30 days of revocation. If you cannot access the dashboard, contact hello@ytproof.com to request deletion.
Contact us to request access to, a copy of, correction of, or deletion of information we hold about you, or to raise a privacy complaint. Depending on your location, you may also have rights to restrict or object to processing, withdraw consent, request portability or complain to a data-protection authority. We may ask for enough information to verify account ownership; never send us your password or access tokens. Withdrawing YouTube consent does not require deleting your YTProof account.
Browser extension for YouTube
The optional YTProof extension adds a card editor to studio.youtube.com. It does not read Studio statistics, Google passwords or Google cookies. Channel selection and figures come from the channels you authorise through YTProof and the existing read-only YouTube API integration.
When you explicitly allow the extension on the YTProof connection page, a temporary approval lets the extension request your public account identity, authorised channel names and identifiers, selected statistics and card publication results through that signed-in YTProof tab. Each approval lasts up to 15 minutes and renews after rechecking the same signed-in account while the tab stays open. Your account and Google access tokens remain on the website and backend. The extension holds the connection tab identifier, temporary approval identifier and expiry in browser session storage; channel selections, preview data and card links are held in memory while the editor is open. This information is used only for the card workflow, without extension analytics or advertising tracking.
Close the connection tab, use Disconnect on the connection page or in the editor, or sign out to stop extension access. The website stores your approved YTProof account identifier in that tab's session storage so refreshing it can restore approval after checking the current account; this identifier is not an access token. Browser restart clears the extension's active approval; a restored, previously approved website tab can reconnect after the account is rechecked. Disconnecting the extension does not revoke YouTube access or delete already published cards; use your account dashboard for those actions. Publishing from the extension makes the same video and original statistics record public as publishing from the website.
On www.youtube.com, the extension identifies the video or channel you open and the video identifiers on visible video cards. While your temporary approval is active, it sends those identifiers to YTProof to request API statistics and display badges, charts and reports. Visible public graphs refresh about once a minute; private daily reports refresh about every five minutes. Refresh pauses when the report is hidden or after a request fails. It does not send search terms, unrelated browsing activity, Google cookies or passwords. Reports are fetched using server-side API access; the extension does not scrape statistics from the page. Public statistics can cover any public video or channel, regardless of which YouTube account you browse with. YTProof uses its own server-side API key for public statistics; if that key is not configured, it can use an active channel grant belonging to your signed-in YTProof account, including a grant authorised in another session. Private daily views and estimated earnings require an active connection owned by your YTProof account to the matching channel.
YTProof retains timestamped public API view counts for up to 30 days to display recorded observation history. These shared public observations contain a video or channel identifier, count and timestamp; they do not contain your account identity, private analytics or notes. Derived analytics and third-party earnings projections remain disabled unless the operator has the required approval. Projections are identified as models rather than actual earnings or verified proof. Your notes are saved only in this browser’s extension storage, are never transmitted to YTProof or YouTube, and remain until you delete them or remove the extension.
Video thumbnails and channel pictures: the extension adds thumbnail download buttons to video cards and video reports, and a download icon over channel profile pictures when you hover or focus them. Clicking a control requests that public image from YouTube’s image servers and starts a browser download. We try the highest available thumbnail resolution, with lower-resolution fallbacks, and request the original available channel picture. These downloads do not require a YTProof account connection or linked YouTube channel.
Download permissions and network access: the extension requests the browser’s downloads permission to start these image downloads. It also requests access to i.ytimg.com, yt3.googleusercontent.com and yt3.ggpht.com to check thumbnail availability and image format and retrieve public images. The extension’s image availability and format checks omit account credentials. YTProof does not attach its account credentials or Google API access tokens to image downloads. Google’s image servers receive the requested image address and ordinary connection information, such as your IP address. Image downloads are handled by the extension and your browser; the images and download requests are not sent to or stored by the YTProof backend. We do not use this permission to read your download history or inspect files on your device.
Where images are saved: your browser saves images to its configured download folder, usually Downloads, or shows its usual save prompt if you enabled that setting. Existing files are preserved by using unique filenames. Downloaded images remain on your device until you remove them; disconnecting YTProof or uninstalling the extension does not delete them. These controls download public images, not video or audio files. Downloading an image does not grant ownership or permission to reuse it.
9. Security
We use HTTPS, HTTP-only session cookies, encrypted YouTube access tokens, OAuth state and PKCE, server-side ownership checks and request validation. Private database and media access is restricted to the service. Connected exports use server-retrieved reports rather than arbitrary finished videos supplied by the browser. No online service can guarantee absolute security; contact us if you believe your account or information has been compromised.
10. Changes to this policy
We update the date on this page when the policy changes. If we introduce a materially different use of your Google data or request additional permissions, we will explain it and obtain the required consent before that use begins. This policy remains publicly accessible from the website and the Google consent screen.
11. Contact YTProof
For privacy questions, data-access requests, deletion requests or complaints, email the YTProof operator at hello@ytproof.com. Include your YTProof handle and the nature of your request, without passwords, payment card details or Google credentials.