Where your members' data lives, and who can see it.

The database is in the EU, in Ireland. The app runs on servers in Dublin. The full list of providers, what each one does and where, is in the privacy policy.

Every connection is encrypted (HTTPS only). Data is encrypted at rest by our providers, and keys and tokens we have to store are encrypted on top of that.

Every row in the database belongs to one gym, and the database itself refuses to show it to anyone else (row-level security). Automated tests check that one gym's account can't read another gym's data.

You sign in with a code sent to your email, or with Google. Add an authenticator app as a second step and it's asked every time after that. The owner can make it required for everyone at the gym.

Card payments go through your own Stripe account. Lapelio never sees full card numbers, never holds your money, and can't refund, charge or move funds.

• You, and the coaches you add
• Each member sees only their own link: what they owe and their receipts
• A phone that isn't linked sees your gym's name at the door QR, never member data
• Lapelio acts only on your instructions as your processor; access is limited to the people who need it, bound to secrecy

• Our database provider keeps backups in the same EU region; they age out within days
• Export everything any time, free
• Close your account and you have 30 days to export, then it's erased

If a breach affects your gym's data, we tell you without delay and within 48 hours at the latest, so you can notify your authority in time.

Email hello@lapelio.com with "Security" in the subject: what you found, and how to see it again. Please don't open other people's data or slow the service down while you look. We read every report, reply quickly and tell you when it's fixed.

The same address is in lapelio.com/.well-known/security.txt.