Security

In transit. The app and splitclubapp.com talk to our servers only over HTTPS (TLS 1.2 or 1.3). Our website hosting, Vercel, redirects every plain HTTP request to HTTPS, and our pages tell browsers to use HTTPS only (HSTS).

At rest. Your account, bookings and messages are stored with Supabase, which encrypts all customer data at rest with AES-256. Vercel encrypts the data it stores with AES-256 too. Stripe encrypts card numbers at rest with AES-256 and keeps the keys on separate machines.

You enter card details only in Stripe's own forms: Stripe's payment sheet in the app, and Stripe Elements or Stripe Checkout on the web. The card number goes from your device straight to Stripe. Our servers never receive or store it. Stripe gives us the card brand, the last four digits and the payment status.

Stripe is certified as a PCI Service Provider Level 1, the highest level in the payments industry. More on how payments are handled is on our Compliance page.

Row-level security. Our database checks, row by row, who is asking before it returns anything. Every table that holds member data has row-level security turned on, so a signed-in member can read only what they're allowed to see (their own account, the splits they're in, the conversations they belong to), and someone who isn't signed in can read almost nothing. We test these rules, and new tables are closed to people who aren't signed in unless we open them on purpose.

Least privilege. Each automated job that works on our data has its own database login, limited to the few things that job needs (for example, read-only access to error reports, or adding listings without access to anyone's profile). It can't read or change anything else, and we can switch off one job's access without touching the rest.

Private files. Identity documents, operator licences, introduction videos, support attachments and photos sent in chats are kept in private storage that isn't publicly reachable.

Staff access. SplitClub staff can see an account only when they need to, to run the service, keep it safe and answer you.

API keys, database passwords and other secrets are kept out of our source code. They live in our hosting providers' settings for secrets and are read only where they're used. Where a provider lets us, each job gets its own key, limited to what it needs where the provider allows, so one key can be revoked without affecting the others.

When you upload a photo or video in the app, your phone removes its location and other hidden metadata (GPS, EXIF and similar) before it is uploaded. People who see your photos can't tell where or when they were taken from the file.

splitclubapp.com detects automated scraping and bursts of requests and blocks them, by network address and by a random security cookie. Search engines and AI assistants are confirmed by their published network ranges, not by what they say they are. Our partner API, MCP server and sign-in forms have their own rate limits.

Our pages send security headers that stop other sites from framing them, limit which outside scripts can load, and stop browsers guessing file types. What the security cookie and our scraping protection record is in our Privacy Policy.

When the app crashes or hits an error, a report goes to Sentry and Google Firebase Crashlytics so we can fix it. Reports include your device model, operating system, app version, the last few screens you opened and your SplitClub account id. They don't include your name, email or phone number: the app turns off Sentry's collection of personal details, and doesn't record network requests in reports, since those can carry ids and search terms. Error reports from our servers never include request contents, and email addresses, phone numbers, keys and tokens are removed from error messages before they're sent.

Our database is backed up automatically every day by Supabase, and the last seven days of backups are kept, so we can recover from a mistake or a failure.

You can delete your account in the app (Profile, then Delete account), or by emailing privacy@s7vc.com from the email on your account. When you do, we remove your profile details, and your login is retired so it can't be used again. Your photos, videos and documents are put on a deletion queue in the same step and removed from storage; anything that fails stays on the queue and is retried every day until it's gone.

If you have money in your SplitClub wallet, we ask you to withdraw it first, so it isn't lost. Some records, such as payment records without your name or contact details, are kept for as long as the law requires; our Privacy Policy lists them.

Before anyone can be paid out (a business, or a member withdrawing from their wallet), Stripe verifies who they are and their bank details through Stripe Connect. Businesses claiming a page may also be asked to verify with Stripe Identity, which checks a government ID. SplitClub doesn't receive copies of the ID documents Stripe checks; Stripe tells us the result and the verified name.

SplitClub is for people 18 and over, and nightlife is 21+. We ask for your date of birth and ask you to confirm you're 18 or older; an account with a date of birth under 18 can't use channels or post. Venues check ID at the door.

If you think you've found a security problem in SplitClub, email privacy@s7vc.com with the subject “Security”. Tell us what you found and how to reproduce it. Please don't access other people's data, change or delete anything, or disrupt the service while testing, and give us reasonable time to fix the problem before you share it.

If a breach affects your personal information, we'll tell you, and the authorities where required, as the law requires. No system is completely secure, and we keep working on ours.