1. Who we are
Keyed is an independent tool for distributing game review keys between two kinds of user: developers, who upload keys and review requests, and content creators, who verify a channel and request keys. This policy covers both.
Keyed is operated by a sole trader based in the United Kingdom, who is the controller of the personal data described below. You can contact us at any time about anything in this policy: support@keyed.id.
2. The short version
- We store as little as we can get away with. No analytics, no tracking pixels, no advertising, no profiling.
- Creators: when you verify a channel, a dedicated Google or Twitch consent (separate from sign-in) confirms you own it. We read your public channel stats (handle and subscriber/follower count) at the moment you request a key — and nothing more.
- Developers: the game keys you upload are stored encrypted, never in plaintext, and we never resell, resurface, or share them.
- Payments are handled entirely by Polar as merchant of record; we never see your card details.
- You can delete your account (and everything in it) yourself from your dashboard at any time.
3. What we collect and why
Different data is stored depending on which side of the product you use.
Everyone (sign-in)
- Email address — your account identifier and how we contact you about your requests, deliveries, or billing. Comes from the sign-in method you choose (email, Google, or Twitch).
- Public profile pieces from your OAuth provider (e.g. display name, channel handle) — only if you sign in that way.
Content creators
- Channel verification data — the platform (YouTube or Twitch), your channel ID/handle, URL, and a snapshot of your subscriber/follower count taken at the time of each request. This exists so developers can see you are a real, verified creator, and is shown only to the developer you request from.
- Request details — your display name, the email you want the key delivered to, the platform you request for, and any message you write.
- What we never receive or store: when you verify a channel, the one-time OAuth access token is used in the moment to read your public channel stats and is then revoked/discarded. We do not keep it, we do not read private messages, videos, drafts, contacts, or anything else from your Google or Twitch account. We read your public subscriber or follower count and nothing else.
Google user data. Keyed's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use YouTube API Services, so by connecting a YouTube channel you are also bound by the YouTube Terms of Service and the Google Privacy Policy. We use Google user data only to confirm that you own the channel you are connecting; we do not use it for advertising, sell it, transfer it to anyone else, or allow humans to read it. You can review or revoke any access you have granted to Keyed at any time in your Google Account permissions. See section 7 for how this data is protected.
Developers
- Project details — title, description, banner, supported platforms, subscriber threshold.
- Game keys you upload — stored encrypted at rest; the plaintext exists only long enough to email the key to an approved creator. We cannot read them casually, and they are never visible to other users.
- Billing linkage — when you top up credits, our payment provider gives us a customer reference and the number of credits purchased. That is all; card details never reach us.
Small technical data (everyone)
- A keyed, one-way hash of your IP address (HMAC-SHA256 with a secret that is held only on our servers) — used only to rate-limit request submissions and prevent abuse. We never store the address itself and make no attempt to recover it from the hash.
- Essential cookies only — a session cookie so you stay signed in, plus a short-lived token from our bot-check provider. There are no advertising or analytics cookies of any kind.
- Error and performance reports — when something breaks or runs slowly, our error tracker (Sentry, hosted in the EU) receives a technical report: the error message, stack trace, the page or route involved, browser/OS type and timings. We configure it not to collect user identity details (including IP address), request bodies, cookies, headers, URL query strings, database query data, or the values of variables in memory, so emails, game keys and tokens are not sent. Reports are used only to find and fix bugs.
4. What we deliberately do NOT collect
- No analytics or product-tracking scripts (as of the date above).
- No advertising pixels or cross-site tracking of any kind.
- No behavioural profiles, ad targeting, or audience selling — and never any.
- No precise location, contacts, or device fingerprinting.
- Your game keys in plaintext (stored encrypted, and only revealed to fulfil an approved delivery).
5. Who else processes your data
Keyed could not run everything itself; we use a small, fixed set of specialist providers. We do not share your data with anyone else, and we never sell it.
| Provider | What they do | What they don't get |
|---|---|---|
| Supabase | Databases, accounts, and sign-ins (hosting our backend). Game keys are additionally encrypted inside the database with a separate secret held in Supabase Vault. | — |
| Vercel | Runs this website and API. | — |
| Cloudflare | Turnstile bot-check on public request forms. Receives enough to verify humans only. | — |
| Resend | Delivers emails (key deliveries, decisions). Receives your email address and the email content only. | — |
| Polar | Merchant of record for paid credits. Handles checkout, payment, VAT/sales tax, and receipts. We receive only a customer reference — your card details never touch Keyed. | — |
| Sentry | Error and performance reports (EU region), limited as described above. | — |
| Google / Twitch (OAuth) | Verify your channel ownership when you connect one; we receive your public channel identity and stats only. | Private account data, videos, or messages. |
Some of these providers may process data outside the UK. Where that happens, they are responsible for providing an equivalent level of protection (e.g. standard contractual clauses).
6. Who sees what
- Creators: the developer you submit a request to sees your channel handle, its public subscriber/follower count, your display name, and your request text. That is the entire point of the product. Developers you never request from see nothing about you.
- Developers: your project details are visible on your public request page. The keys you upload are never shown to creators until an approved request is fulfilled, and never shown to other developers at all.
- Nobody — including us — sees your payment card details.
7. How we protect your data
Google and YouTube user data
- Minimum scope. We request a single read-only YouTube permission (
youtube.readonly), solely to confirm that you own the channel you are connecting. - No stored credentials. The access token Google issues is single-use. We do not request a refresh token, so we never hold standing access to your account. The token is used once to read your channel's public identity and subscriber count and is then revoked with Google. It is never written to our database, cookies, or logs.
- Protected sign-in flow. The connection uses PKCE and a signed, single-use state value held in a short-lived (10 minute), httpOnly cookie, so a connection can only complete for the signed-in user who started it.
- Minimal retention. The only Google-derived data we keep is your channel ID, name, URL and subscriber count. It is deleted when you disconnect the channel or delete your account.
Across the service
- Encryption in transit. All traffic between your browser, our servers, our database, and the third-party services listed above uses TLS (HTTPS).
- Encryption at rest. Our database is hosted by Supabase and is encrypted at rest. Game keys are additionally encrypted inside the database with a separate secret held in Supabase Vault; they are decrypted only at the moment an approved key is delivered. Stored keys are not accessible to the browser, other users, or other developers.
- Access controls. Row-level security restricts every user to their own records. Server credentials and API secrets are held as server-side environment secrets and are never sent to the browser. Our sign-in session uses httpOnly cookies, and the site sets protections against clickjacking and content sniffing.
- Limited telemetry. Our error tracker is configured to exclude request bodies, cookies, headers, query strings, user identity details and variable values (see section 3), so sensitive data does not leave our systems through error reports.
- Breach response. If we discover a personal data breach that puts your rights at risk, we will notify you and the UK Information Commissioner's Office as UK GDPR requires.
8. How long we keep things
- Account data: until you delete your account.
- Requests and channel snapshots: kept so you and the developer have a record of the request; delete your account and they go too. There are no standing OAuth permissions to revoke — we never retained access tokens in the first place.
- Rate-limit IP hashes: short-term (hours, at most days) and pruned automatically. A copy of the hash is also kept on each request record, so it is deleted along with that request when you delete your account.
- Error and performance reports: kept by Sentry for a limited period under its standard retention settings, then deleted.
- Emails we send you: held in your mailbox, which is outside our control; we keep delivery records only for as long as your account exists.
- Payment records: Polar, as merchant of record, retains transaction receipts for its own legal/tax obligations regardless of account deletion. We hold only the credited amounts, which go when your account does.
- Delivered keys: we cannot unsend an email, so an emailed key is outside our control the moment it is delivered. Deleting your account will not retract emails already sent.
9. Your choices
- Delete your account any time from the "Deactivate account" section of your Settings page. This permanently removes your account, requests, channel verifications, notification settings, projects and their remaining keys (for developers), and any unused paid credits are forfeited. Already-sent emails cannot be retracted.
- Disconnect a channel to remove a verification.
- You can also contact us at support@keyed.id to exercise data rights (access, correction, deletion, complaint) — under UK GDPR, we respond within one month.
- You have the right to complain to the UK Information Commissioner's Office (ico.org.uk) if you believe we have mishandled your data.
10. Changes to this policy
If we ever add or change what we collect (for example, if we introduce optional product analytics in future), we will update this page and the date above, and — for anything material — tell signed-in users by email before the change takes effect. We will never quietly widen what we collect.