Security & Trust

MVPLedger is built as a multi-tenant youth-sports Club OS. Security controls are designed around tenant isolation, least-privilege access, auditable changes, private storage, provider separation, and recoverability.

Tenant and role isolation

Supabase PostgreSQL is the authoritative application database. Organization, team, household, finance, registration, document, and communication access is constrained through application authorization and Row Level Security policies. MVPLedger treats an unknown authorization state as unavailable rather than assuming access or silently presenting an empty result.

Authentication and privileged access

Authentication is provided through Supabase Auth and application-side role checks. Organization permissions are scoped by membership and role, with narrower team and household authority where appropriate. Service-role credentials and provider secrets are server-side configuration and are not returned in normal client reads.

Payments and banking

MVPLedger is designed not to custody organization funds. Stripe Connect payment flows use the organization’s connected payment relationship, and bank-linking through Plaid is used for authorized reconciliation workflows. Raw card data and bank-login credentials are handled by the respective providers rather than stored as ordinary MVPLedger application data.

Data in transit and storage

Production connections use HTTPS/TLS through the application and infrastructure providers. Sensitive documents and financial artifacts are designed for private storage and authorized access, including signed or scoped retrieval where applicable. Public surfaces expose only data intentionally prepared for those surfaces.

Auditability and change control

MVPLedger records audit information for security-sensitive and operational workflows where the product requires traceability. Database changes are maintained as source-controlled migrations, and Edge Function source is maintained in the Git repository so deployed behavior can be compared against the reproducible source of truth.

Recovery and availability

The project maintains a recovery workflow that can replay the migration chain from zero and lint the resulting database. Backup and provider recovery controls are treated as release gates and are validated separately from application feature work. No public uptime guarantee is made on this page.

AI and consequential actions

AI-assisted features are used for explanation, summarization, drafting, forecasting, and suggestions. Consequential actions such as approving expenses, changing dues, granting aid, closing reconciliation, refunding payments, changing permissions, or publishing private financial information remain governed by deterministic application authority and human action.

SOC 2 posture

MVPLedger is building operational and technical controls with SOC 2 readiness in mind. This does not mean MVPLedger has completed an independent SOC 2 examination or holds a SOC 2 report. Any future attestation will be described only after it is independently completed.

Responsible reporting

If you believe you found a security issue, contact support@mvpledger.com with enough detail for us to investigate. Do not access, alter, or retain data that does not belong to you.