ClassM8 Privacy Policy

ClassM8 by Mueble Group / Personal Data Protection Notice

ClassM8 Privacy Policy

Information about studio accounts, students, teachers, bookings, attendance and enabled payment or notification services.

Draft for review / 9 October 2026 / Effective date pending approval

01 / Scope and responsibilities

ClassM8 is Mueble Group's studio-management platform. This notice covers studio owners, administrators, teachers, students, parents or guardians, and people contacting the platform team. Available functions depend on the studio's plan, settings and deployment.

A studio generally determines why and how its student, teacher, booking and attendance records are used and acts as data controller for those activities. Mueble Group may process those records on the studio's instructions as a service provider, while acting as controller for its own customer administration, support and relevant platform-security purposes. The precise allocation must be confirmed in the studio agreement; this notice does not replace the studio's own privacy notice. The platform operator's full legal identity and address are pending confirmation.

02 / Accounts and studio records

Depending on the fields and functions enabled, records may include name, email, phone number, login/account identifiers, user role, studio membership, teacher assignments, student profiles and parent/guardian details supplied by you or the studio. Studio records can include schedules, classes, bookings, class-credit balances, plans, subscriptions and purchase history.

We may receive support messages and relevant attachments from users and authorised studio staff. Device/browser details, IP addresses, timestamps and application or security logs may be generated through use. Sensitive information, such as health notes, should only be collected if needed, with the required notice, explicit consent or other lawful basis and appropriate safeguards. This draft does not assert that such fields are enabled.

03 / Uses and required information

We process personal data for the purposes described here, with consent where required or under an applicable PDPA exception, such as processing necessary for a contract or legal obligation. Optional marketing requires the appropriate consent and can be declined without stopping essential service messages. Providing data for an enquiry, account, booking or payment is necessary to handle that request; optional fields should be identified when collected. Missing required information may prevent the relevant service.

Relevant functions include setting up studio accounts, assigning teacher access, booking sessions, administering class credits and purchases, recording attendance, providing reminders or announcements, handling support and protecting the service. A studio is responsible for the notices and choices associated with its own marketing and collection of student information.

04 / QR attendance

For supported sessions, a teacher or administrator can display a temporary, class-specific attendance QR code. A signed-in student scans it, and ClassM8 checks the account, studio, class and code validity before recording attendance.

The attendance record may include the student and studio/class identifiers, check-in time and result, with related troubleshooting or security logs where configured. QR attendance should not be described as collecting continuous location, facial biometrics or storing camera images without evidence that those functions are actually enabled. Camera permission may be needed by the scanning method used. Ask your studio about another check-in method if scanning is unavailable.

05 / Payments: Stripe and HitPay

ClassM8 supports Stripe and HitPay integrations. The payment service used depends on your studio and checkout configuration; supporting an integration does not mean every studio uses both providers.

Where enabled, payment-related information may be sent to the chosen processor, including customer/contact details, order amount, currency and transaction references. ClassM8 and the studio may receive payment status, receipt, refund or subscription references and limited payment-method metadata. In a provider-hosted checkout flow, full card credentials are entered with the payment provider; the exact integration and whether any credentials reach platform systems must be verified.

Payment providers also process data for their own legal, security and financial-service purposes. Their privacy notices apply. Refunds, recurring payments and account deletion do not automatically cancel each other; contact your studio about both the subscription and related records.

06 / Notifications and Firebase

Where Firebase Cloud Messaging or other Firebase services are enabled, the relevant Google service may process device/app identifiers, push registration tokens and delivery or diagnostic information as applicable. Firebase Authentication, Analytics and Crashlytics should only be treated as used if separately confirmed.

Enabled notifications may include booking updates, reminders, attendance or payment updates and studio announcements. Channels such as push, email, SMS or WhatsApp depend on the actual configuration. Push permissions and preferences can be managed in the app/device where supported; disabling them may mean missing reminders. Service notices and optional promotional messages should be treated separately.

07 / Multi-tenancy and recipients

Records are associated with the relevant studio tenant. Studio administrators may access records within their permitted scope; teachers and students receive access according to their roles and enabled permissions. Joining more than one studio can create separate studio relationships and records.

Multi-tenancy should not be taken as a guarantee of a physically separate database. Tenant isolation, cross-studio access rules, support access and export permissions require technical confirmation. Authorised platform staff, hosting/database/backup providers, configured payment and messaging providers, professional advisers and authorities may receive information where necessary and lawful. The studio's own access and exports are subject to its policies and responsibilities.

08 / Hosting, cookies and transfers

Account sessions, authentication, security and preferences may use cookies, local storage or similar technologies. Optional analytics should be disclosed and choices provided where required. Blocking essential storage may interrupt sign-in, checkout or attendance functions.

Hosting and third-party services may process personal data outside Malaysia. A transfer must have an applicable basis under section 129 of the PDPA, such as qualifying protection in the destination or an applicable statutory exception, with consent where required. The actual providers, countries, transfer assessment and safeguards must be confirmed before publication.

Confirm the application host, database/storage provider, backup locations and enabled Firebase and payment-service regions; no Malaysia-only hosting claim is made.

09 / Retention, children and security

Personal data should be kept only for as long as needed for the stated purposes, applicable legal obligations and the resolution of disputes. Data no longer required should be deleted, anonymised or securely disposed of. Backup copies may remain until the relevant backup cycle expires; access and restoration must remain controlled. Specific retention and backup-expiry periods need operational confirmation.

Studio instructions, account closure, legal/accounting records, attendance history, payment references and logs may require different periods. A request to one studio may not affect records held by another studio or an independent payment provider.

Where minors attend classes, the studio should provide age-appropriate information and obtain parent/guardian authority or consent where required. Confirm actual age limits and safeguarding arrangements before publishing. Security and incident-response measures must be verified, including role access, tenant isolation and backup handling; statutory breach notifications apply where required.

10 / Requests and contact

Where Malaysia's Personal Data Protection Act 2010 (PDPA), as amended, applies, you may request access or correction, withdraw consent, stop direct marketing, or object to processing likely to cause damage or distress, subject to statutory conditions. You may also request data portability in writing electronically, subject to technical feasibility and compatible formats. These rights are subject to applicable exceptions; deletion is not an unrestricted PDPA right.

For studio-controlled records, contact your studio first. For platform-account, support or security records controlled by the operator, contact Mueble Group. Requests may require identity verification and be subject to legal retention or other restrictions. You may complain through the JPDP website.

For privacy questions or requests, use the Mueble Group contact form or the existing WhatsApp contact: +60 3-5030 7412. State which service and, if relevant, which studio or social account your request concerns. Please do not send passwords, payment-card details or identity documents in an initial message. A dedicated privacy email, postal address and any required DPO contact must be confirmed before publication.

Draft reviewed on 9 October 2026. Effective date: pending approval. Updates should be dated and communicated where appropriate.