Skip to content
RelayKeys

Last updated 7 October 2026

Privacy

What personal data RelayKeys keeps, why, for how long and who else sees it: about the businesses that run stores on it and their teams, and the resellers in those stores.

Who looks after it

RelayKeys, in the United Kingdom, decides how data about the businesses that use it, their teams and visitors to this site is used (the data controller, under UK data protection law). Each store's resellers are that store's: the business that runs it is the controller, and RelayKeys handles their data for them, as our terms set out. Contact us on our Discord.

Businesses and their teams

  • Your account: name or username, email, password (one-way hash), two-factor secret (encrypted) and recovery codes (hashed), for you and everyone on your team, and what each can access.
  • Your store: its name, address and settings, and the payment account and Discord bot details you connect (keys and secrets encrypted).
  • Security: the IP address and browser of each sign-in and signed-in device, failed attempts, and a log of changes made in your console and by whom.
  • Contacting us: what you send us, and your details to reply.

Resellers in stores

For each store, the panel keeps this about its resellers, for the business that runs it:

  • Applying: name, email, company and website if given, the message, and the IP address and browser used.
  • The account: username and email, the password (only as a one-way hash, never readable), the two-factor secret (encrypted), recovery codes (hashed) and the link to the reseller's shop.
  • Using it: orders, the keys bought (encrypted), the balance and every change to it, API keys, API links and webhooks, and any custom prices or discounts.
  • Payments: the amount, status and the payment provider's reference. Card and PayPal details stay with Stripe and PayPal. Crypto payments are made on a public blockchain.
  • Security: the IP address and browser of each sign-in and signed-in device, failed sign-in attempts, a log of API requests (what was asked for and the answer), and a log of changes to the account.
  • Discord, if linked: the Discord ID, username and avatar, and the messages the store's bot sends.

Resellers with a question about their data should ask the store they resell in first.

Why it's used

  • To provide the service (our contract): running your store, signing people in, delivering keys and sending what's been asked for, like webhooks and Discord messages.
  • To keep stores and the service safe (our legitimate interests): spotting fraud, stopping abuse, locking out repeated wrong passwords and investigating problems.
  • To keep financial records (a legal obligation), for accounting and tax.

We don't sell personal data, use it for advertising, or track anyone across other sites.

Who else sees it

  • Vercel and Neon, which host the service and its database for us.
  • Resend, which sends the sign-up and password emails.
  • Stripe, for a business's subscription to a paid plan (stores' own payment accounts are theirs).
  • Discord, when a store connects the bot or someone links their account.
  • The payment providers a store connects, which work for that store.
  • Authorities, when the law requires it.

Some of these providers handle data outside the United Kingdom. Where they do, it's protected as UK law requires: in a country the UK recognises as adequate, or under the UK's approved contract terms.

How long it's kept

  • API request logs: 90 days. Webhook delivery records: 30 days.
  • Signed-in sessions: until they expire or you sign out. A remembered device: 30 days.
  • Account details: while the account is open. When it's deleted, its username, email, password, two-factor and Discord link are erased.
  • Orders, payments and balance changes: while the account exists, and afterwards as long as accounting and tax law needs them (normally 6 years).
  • The log of sign-ins and account changes: as long as needed to protect accounts and look into misuse.
  • Applications and requests for a panel: a year after they're answered.

When a store closes it's archived straight away, so nothing in it can be reached. Its owner can ask us to delete its data or send them a copy, and we do within 30 days of being asked, except what the law requires us to keep.

Cookies

Only cookies the panel needs to work, so no consent is asked. There are no analytics or advertising cookies.

  • __Host-session: keeps you signed in.
  • __Host-device: when you choose to remember a device, skips two-factor on it for 30 days.
  • __Secure-handoff: for a minute after you sign in on RelayKeys's own site, lets your store's address finish signing you in, and only in this browser.
  • vendora_links_ok: remembers, for this sign-in, that you confirmed it's you before using API links.
  • vendora_store and vendora_view_as: in a store's console, which store it shows and whose dashboard you're viewing.
  • vendora_discord_oauth and vendora_discord_install: while Discord is being linked or the bot added, to finish safely.

Keeping it safe

Connections are encrypted. Keys, two-factor secrets, payment account keys and API links are encrypted when stored, and passwords are hashed. Two-factor sign-in is available on every account, and sign-ins are rate limited.

Your rights

You can ask for a copy of your data, to correct it, to delete it, to limit or object to how it's used, or to have it in a form you can take elsewhere. Contact us on our Discord and we'll reply within a month. Some data, like financial records, may have to be kept by law. You can complain to the Information Commissioner's Office at ico.org.uk, though we'd like the chance to put it right first.

Changes

We'll update this page when what we do with data changes, and show the date at the top.