Built on infrastructure clubs can trust.
You’re trusting us with member contact info, payment history, and the day-to-day operations of your club. Here’s exactly how we protect it — the isolation between clubs, how payments work, and where AI is and isn’t allowed to touch your data.
Your club’s data stays yours
Every table in the database carries a tenant_id, and Postgres row-level security enforces it on every single query — not just in application code. A club’s bookings, members, and revenue are never queryable from another club’s session, even though every club runs on the same shared Supabase database underneath.
Payments never touch our servers
Card numbers are tokenized directly by Stripe. Courtlines never stores raw card numbers — we only keep the last 4 digits and card brand, purely for display on a receipt. Refunds, disputes, and payouts all run through Stripe’s infrastructure, not ours.
Encrypted, always
Data is encrypted in transit (TLS) between your browser, our servers, and every vendor we use, and encrypted at rest in the database. We don’t run third-party ad-tracking pixels on any club’s booking pages — your members’ activity isn’t for sale.
What our AI features can and can’t see.
Courtlines has an AI advisor and an MCP connector that lets AI tools like Claude answer questions about a club’s own data. Both are opt-in, and if your club never turns them on, nothing about how your data is stored or accessed changes — you’re completely unaffected.
For clubs that do opt in, the MCP connector uses a scoped API key issued per tenant, not a master key that spans every club on the platform. That key only opens onto read-only "safe views" — pre-built summaries of bookings, revenue, and customers — plus exactly one narrow write action: creating a booking inquiry. It does not hand an AI agent raw database access, the ability to run arbitrary queries, or any path to another club’s data.
In practice, that means an AI agent connected through MCP can tell you how last week’s bookings looked or draft a follow-up to a lead — the same things a staff member could pull from a report — but it can’t reach into the database directly, and it can’t do anything to your account you haven’t explicitly allowed.
Who we work with
A small, well-known set of vendors handle payments, messaging, and monitoring. Each operates under its own privacy policy and an industry-standard data processing agreement.
Your data, on request
Any club (or club member) can request a full export or deletion of their data. We respond within 30 days, except for records we’re legally required to keep, like signed waivers.
Questions before you sign up
Want more detail on how a specific piece works — RLS policies, our MCP scopes, vendor DPAs — before you commit? Ask us directly, we’ll walk you through it.
For the full legal detail, see our Privacy Policy and Terms.
Have a security question we didn’t answer?
Talk to the people who built it — not a support queue.