How can we help?

Every Pro feature. A card is required at sign-up but the first charge is at the end of the trial — cancel any time before then and nothing is taken. The trial mirrors production: real Stripe Connect flow, real custom-domain provisioning, real lifecycle emails. Nothing is mocked.

No — you can export everything from the dashboard at any time, in JSON. After cancellation we keep operational data for 60 days (so a change of heart can be reversed with one email) and then anonymise it. Billing records — booking prices, payment intents, refund records — are retained for 7 years to satisfy HMRC. Your members' names, emails and phone numbers are scrubbed from those rows; the totals reconcile but the personal data is gone.

No. Each club has its own subdomain and its own data, partitioned at the database layer — not just in app code. Every server-side query carries the tenant id derived from the URL, and a misconfigured request can't reach another tenant's rows. Members signing in with the same email at two clubs maintain two separate accounts; we don't cross-link.

Member payments and tournament fees go through Stripe Connect — funds settle directly to the club's bank account, usually 2–7 days after the charge per Stripe's standard schedule. Freyaa never holds member funds. We don't take a cut of member transactions on Pro and below; Stripe's standard processing fee (1.5% + 20p UK domestic) applies.

Yes. The migration guide covers the self-serve path; for the most common case — a Google Sheet of members — see how to import members. Concierge migration is free during the trial on Pro and Enterprise; email us with what you're using today and we'll quote a date.

Yes — Pro and Enterprise let you map a custom domain like book.yourclub.com. Add a CNAME in your DNS provider, we provision SSL automatically. Usually live within an hour. Full walk-through: Connecting a custom domain.

EU. Postgres lives at Neon in Frankfurt, transactional email through Resend EU, error telemetry on Axiom EU. Backups are encrypted at rest and retained for 30 days. The full sub-processor list is on the privacy page.

It can't happen. A unique database constraint rejects overlapping bookings on the same court before the row is written. The UI translates the rejection into a friendly "that slot was taken just now" message and refreshes the grid. More detail: double-bookings.