Privacy Policy

• Google profile basics: the name and email associated with the Google account you sign in with.
• YouTube channel info: the channel ID, handle, and title for the channel you authorize. We request the youtube.readonly scope only — we do not read your videos, comments, analytics, or any other Google service.
• Badge data you submit: the YouTube video URL, the SHA-256 hash and file size of the video file you select, your attestation text, and the disclosure form fields (public + private halves).
• Reports against badges:if someone files a report on one of your badges, we store the report reason and (optionally) the reporter's email. Reports are visible to you, the badge owner.
• Authentication cookies: a session cookie issued by Supabase to keep you signed in. No third-party tracking cookies.

• The video file itself. The SHA-256 hash is computed locally in your browser via the Web Crypto API. The bytes of the file never reach our servers.
• Anything outside YouTube. The Google scope we request is read-only YouTube. We cannot see Gmail, Drive, Calendar, Photos, or any other Google service.
• Browsing or analytics. No Google Analytics, no Mixpanel, no third-party trackers. We have no idea what other tabs you have open.
• Payment information. Silver is free. Gold (when it ships) will use Stripe; we will never see your card data.

• Verify that the YouTube channel you claim is actually yours.
• Mint a badge tied to your channel and serve a public proof page at getbyhuman.com/v/<slug>.
• Submit your video's hash to OpenTimestamps calendar servers for Bitcoin-anchored timestamping. This is intentionally public — anchoring to Bitcoin means anyone can verify the timestamp without trusting us.
• Store the public half of your disclosure on the proof page. The private half is recorded for audit only and never published.
• Email you about the service if needed (account issues, badge revocations, major policy changes). No marketing.

To run the service, we rely on a small number of third-party providers that process limited data on our behalf. They're each bound by their own privacy and security commitments, and we use them only for the purposes described.

• Google — Google OAuth + the YouTube Data API, used to verify channel ownership and fetch video metadata (title, duration).
• Supabase — database and authentication infrastructure where creator profiles, badges, disclosures, and reports are stored.
• Vercel — application hosting and scheduled jobs (the OpenTimestamps upgrade cron).
• Cloudflare — hosts the public landing site (Cloudflare Pages), proxies proof pages from the apex domain, and stores desktop installer downloads (Cloudflare R2).
• OpenTimestamps — public calendar servers (operated by independent contributors) that batch-anchor your file hash into a Bitcoin block. Once anchored, the proof is verifiable without ByHuman or OpenTimestamps in the trust path.

• Public proof pages at getbyhuman.com/v/<slug>. These are intentionally public and indexable. By minting a badge, you're publishing a claim under your channel's name.
• Bitcoin blockchain anchoring. Your file hash is committed inside a Bitcoin block via OpenTimestamps. This is permanent and public by design.
• Nothing else with anyone. No data brokers, no advertisers, no analytics vendors.

While your account is active, we retain your creator profile, badges, and disclosures indefinitely — public proof pages and Bitcoin-anchored timestamps are by design permanent and verifiable long-term. Reports against badges are retained for 24 months for audit purposes, after which they're deleted unless they led to a revocation (revocation records persist on the affected proof page). If you delete your account, see the next section.

You can request any of the following at any time:

• Access. A copy of the personal data we hold about you in a machine-readable format.
• Correction. Updates to inaccurate data — e.g., your email or channel handle if it changed.
• Deletion. Removal of your creator profile, badges, disclosures, and reports from our database.
• Restriction or objection.If you believe we shouldn't process certain data, tell us and we'll review the request.

Email support@getbyhuman.com to make any of these requests. We respond within 30 days.

Two things we can't delete:

• Your file hash anchored to Bitcoin. The blockchain is immutable; the hash itself doesn't identify you (it's opaque bytes), but we can't un-anchor it.
• Web archive caches of your proof page if anyone's archived it (archive.org, etc.). Those are out of our control.

ByHuman Creators is operated from the United States, and your data is processed and stored there (and at our subprocessors' US-based facilities). By using the service from outside the US, you consent to the transfer of your data to the United States, which may have different data-protection rules than your home country. EU/UK users retain the rights described in the previous section.

ByHuman Creators is not directed at children under 13. If you're under 13, please don't use the service. If we learn we've collected data from a child under 13, we'll delete it.

We'll update this page when we change how the service handles data. The “Last updated” date at the top will change. For material changes (new data we collect, new third parties), we'll email signed-in creators before the change takes effect.

Questions about this policy or your data: support@getbyhuman.com.