Card numbers, families' details and children's records, and who gets to see each. Here is what the product does about it.
Card details are typed into Stripe's own payment form and go straight to Stripe. OrgFrame never sees a card number or stores one, and payouts go from Stripe to your bank.
The database checks which organization every row belongs to before it hands one over, so one club's staff can never read another club's families, whichever screen asks.
Every staff member holds a role with its own permissions. A coach's role covers their team, not the whole organization, and a treasurer's needn't include rosters.
Children under 13 never have a login, parents control their child's information, and coaches see an age rather than a birth date.
Birth certificates and other documents sit in private storage, opened only through short-lived private links.
Sign in with a passkey, Google or Apple, or with an email and password if you'd rather.
Every page, form and payment is served over HTTPS, on your organization's own domain too.
Session recording never runs on an organization's public website, where team pages, rosters and photos live. Inside the app, it hides every word on screen.
When an organization closes its account, its data is deleted or de-identified, apart from what tax and accounting law requires us to keep.
Found something that looks like a security issue? Email support@orgframe.app with what you found and how to see it. Please don't test against an organization that isn't yours.
The Privacy Policy says what is collected, how long it is kept and who handles it for us.
A board's, a treasurer's or a parent's. Each gets a straight answer.