Privacy Policy

FeeBuddy handles account identity, organization information, participant/student/member records, guardian or emergency contacts, financial ledger records, staff memberships, support/contact requests, security and audit records. Organizations choose the participant information they record across tuition/coaching, arts, sports, fitness, wellness, martial arts and other training workflows.

Information supports organization setup, role-based access, participant and program management, payment records, receipts, reminders, support and security. Organization access is tenant scoped. Demo workspaces contain fictional data. Do not include passwords, cookies, security links, API keys, database credentials or payment credentials in support messages.

When paid subscription billing is enabled, payment information is processed through the configured payment provider. FeeBuddy may retain provider subscription/payment identifiers, billing status and verified billing-period information to manage access. Participant receipts are not FeeBuddy SaaS invoices. External payment-provider verification is NOT VERIFIED; this policy does not assert live payment processing or provider certification.

An active organization Owner can request organization data, an export or account closure in Settings support requests. Some existing screens export particular CSV records; a complete organization export and account closure are reviewed support requests, not automatic self-service completion. For personal account questions or access difficulties use the contact form.

Submission does not immediately delete data. Financial history, receipts, security/audit records, staff relationships and subscriptions require operational and legal retention review. No fixed retention period or automatic deletion completion is promised by this implementation. Support ownership and retention policy require launch review.

Role and membership safeguards restrict access. Operational logs use bounded event categories and request references rather than support message bodies. Local email delivery mechanisms exist, but external email delivery remains unverified. General account-email ownership verification remains a launch dependency. No legal or regulatory certification is claimed.