Trust, by design.
Club software holds kids' names and families' money. That's not a footnote — it's the design brief. Plain-English version below.
Every club is a sealed room
Isolation between clubs is enforced by the database itself (row-level security keyed to your club), not by application code promising to behave. One club can never query another's data.
We don't hold card numbers
Payments run through Stripe, a certified payment processor. Card details go to Stripe directly — they never touch our servers.
Families can leave, completely
Account deletion is self-serve and real: profile and linked swimmer data are removed, not flagged hidden. Built for GDPR, applied to everyone.
Kids' photos are consent-first
Swimmer photos and public leaderboard listings are gated behind explicit parental consent. No consent, no publication — the default is private.
Receipts a tax office would nod at
Every receipt carries the club's own legal name, address and tax ID — built for VAT compliance in the EU and good bookkeeping everywhere.
Changes happen in the open
Every release is documented on the public changelog. Security fixes ship first and get written up like everything else.
Where we are honest about maturity
SwimSync is young software. We publish what we ship, we fix what we find, and we don't claim certifications we don't hold. If your committee has security questions, ask — you'll get a straight answer from the person who wrote the code.
Ask us anything