Privacy Policy

How Koaryu handles account, studio, student, and payment-adjacent data.

Updated May 19, 2026

Information Koaryu handles

Koaryu handles account information, studio settings, staff roles, students, guardians, leads, schedules, attendance, rank progress, reports, audit records, billing plans, payer records, invoices, payments, refunds, disputes, and related metadata needed to operate the product.

Authentication and access

Koaryu uses Supabase Auth for authentication and uses studio membership, role checks, backend authorization, and database policies to scope records to the correct studio. Users should protect their login credentials and studio admins should promptly remove staff who no longer need access.

Payments

Stripe processes card and bank/payment method details. Koaryu stores Stripe IDs, invoice status, payment status, fee amounts, reconciliation state, and other payment metadata so studios can understand and repair billing activity without storing raw card numbers.

How information is used

Koaryu uses information to provide studio management features, enforce permissions, support billing workflows, troubleshoot errors, protect accounts, generate exports and reports, improve reliability, and respond to support requests.

Exports and deletion

Studio admins can export many operational records from Reports. Admin-only cleanup tools can delete or replace working studio data after confirmation while preserving platform access records needed to keep Koaryu Core subscription access intact.

Third-party services

Koaryu depends on service providers such as Supabase, Stripe, Render, and Vercel to authenticate users, store data, process payments, host the backend, and serve the frontend. Those providers may process information as needed to deliver their services.

Contact

For privacy, access, export, or deletion questions, contact support@koaryu.app and include the relevant studio name and account email.

Koaryu may update this privacy policy as the product, business details, data retention decisions, support process, and payment configuration evolve. Material changes should be reflected here before relying on the updated behavior in production.