Security & Trust

How RANQD protects your club’s data

Clubs trust RANQD with their members’ details and their event payments. This page explains, in plain language, how that data is stored, protected, and handled - and what to do if you ever spot a problem.

Where your data lives

All club and player data is stored in the United Kingdom (AWS London region) on Neon, and the application runs on Vercel. Both providers hold SOC 2 attestations and industry-standard certifications for their infrastructure. Data is encrypted in transit (TLS) and at rest (AES-256).

Payments

  • Card details never touch RANQD’s servers. All card entry happens on the payment provider’s own hosted, PCI-DSS-certified pages (Stripe is PCI Level 1).
  • Money paid to a club settles directly to that club’s own payment account - RANQD never holds club funds.
  • Every payment notification is verified before it is trusted. Stripe and PayPal messages are cryptographically signature-checked; Mollie sends only a payment reference, which we confirm by fetching that payment directly from Mollie over an authenticated connection. Anything that fails to verify is rejected.

Access control & accounts

  • Sign-in credentials are stored only as strong one-way hashes (bcrypt) - nobody at RANQD can read your PIN.
  • Optional two-factor authentication for club owners, with one-time recovery codes.
  • Repeated failed sign-ins are rate-limited and temporarily locked, with an alert email to the account owner.
  • Role-based access: club owners, admins, and players each see only what their role allows.

One club can never see another’s data

RANQD is multi-tenant: every read and write is scoped to your club on the server, on every request. Tenant isolation is re-verified whenever new features ship, and it is a standing focus of our internal security reviews.

Monitoring, audit & recovery

  • Every club has its own audit trail of admin actions; security-relevant events are retained indefinitely.
  • The database supports point-in-time recovery, so data can be restored to a moment before an incident.
  • We run regular internal security reviews with documented findings and verified fixes.

Data protection (UK GDPR)

  • For player data, your club is the data controller and RANQD is the processor - we process member data only to run your club’s leagues, sessions, and events. A data processing agreement is available on request.
  • We never sell personal data, and marketing emails (club follower updates) are strictly double opt-in with one-click unsubscribe.
  • When a club leaves, its data is retained for 90 days (in case you return) and then deleted, except where the law requires longer retention of financial records.
  • Subprocessors we rely on: Vercel (hosting), Neon (database), Resend (transactional email), Upstash (rate limiting), Stripe / Mollie / PayPal (payments). Each is bound by a data processing agreement.

Found a vulnerability?

We welcome responsible disclosure. Email hello [at] ranqd.app with the details and we’ll respond promptly. Please don’t access data that isn’t yours or disrupt the service while investigating. A machine-readable policy lives at /.well-known/security.txt.

Questions from your committee? Write to hello [at] ranqd.app - we’re happy to complete security questionnaires for clubs and venues.