Your school’s data deserves clear answers.
What Konjo stores, how access is controlled, and where the limits are. No certification claims or uptime promises.
Access follows the person’s role.
Konjo uses database row-level security and staff permissions to control access to school records. Sensitive account fields are excluded from broad queries. Public booking and signing links use scoped access.
Owners assign staff roles. The Studio assistant uses that staff member’s existing access; changes require confirmation, and sensitive actions are restricted.
Payments go through Stripe.
Card entry happens in Stripe’s payment forms. Konjo stores payment references and the details needed for records and reconciliation, not full card numbers or security codes. Your school connects its own Stripe account during Guided Launch.
Each dojo is the seller (merchant of record) on its own Stripe account, and Stripe processes the payments. Stripe’s fees come straight out of each payment: 2.9% + 30¢ per card payment, plus Stripe Billing’s fee on memberships. 2.9% + 30¢ is the published US card rate; Stripe’s own fee on international cards, American Express or a currency conversion can be higher. Konjo adds no fee.
Who processes data.
- Supabase
- Database, sign-in, file storage and server functions. Everything the app and Studio store, on US infrastructure.
- Vercel
- Hosting for the web app, Konjo Studio and this site. Request logs, Studio performance data and AI Gateway requests.
- Stripe
- Payments and payouts under Stripe Connect. Card details typed into Stripe’s own form, payer name and email, amounts, and your Connect account details.
- Mux
- Video transcoding and playback. Video that members upload, the playback files made from it, and playback metadata.
- Brevo
- Email sent on your dojo’s behalf. Recipient address, subject and message body.
- Google Gemini, through Vercel AI Gateway
- The language model behind the Studio assistant. The conversation, and the records that staff member was already allowed to read. Prompt training is disabled.
- Expo Push and Apple Push Notification service
- Delivering push notifications. A device push token and the text of the notification.
- Sentry
- Crash and error reporting in enabled app builds. Error and device details, sampled mobile replay with default masking, logs and submitted feedback. Errors, URLs or feedback may still contain personal information.
Some services are used only when you choose the relevant feature:
- Address autocomplete, on the event form.
- An embedded reference video, inside the curriculum.
- Apple or Google sign-in, if that is how you sign in.
- Apple TestFlight, while the iOS app is in beta.
- Printify, if a dojo turns on merchandise.
- Anthropic Claude is an Agent model default. Agent is currently disabled for general use; its separate terms and privacy disclosures apply before activation.
See the Privacy Policy for the full categories, purposes and retention details.
Export, deletion and retention.
Available Studio screens provide CSV exports. Galen helps arrange other records and media during service and for 30 days afterward. Members can request account deletion from Account & settings. The current deletion process can remove some school records or fail because of linked business records. Contact Galen and your school first if records need to be preserved, or if deletion fails.
Supabase provides the database backup infrastructure. There is no separate Konjo backup service or guaranteed recovery time. Konjo does not offer an uptime SLA or claim SOC 2 or ISO certification.
This site keeps things simple.
No analytics trackers, advertising scripts or embedded third-party media are loaded here. Hosting providers still receive ordinary web request logs. The demo form sends the details you choose to give us so Galen can reply.
A concern needs a person.
Contact support@getkonjo.com for security questions or to report a vulnerability. Include what you observed and enough detail to reproduce it, without sending another person’s private records.