Security and privacy
From Muzeqo Wiki
Security and privacy in Muzeqo rest on keeping each school’s records apart in the database itself. Every school is its own tenant, separated by row-level security in a PostgreSQL database, so the rule holds for every page, export and calendar feed and not only for what the menus show. Within a school, each person sees what their role allows: teachers see only their own students and families only their own children.[4][5]
People sign in with a password, a passkey or a Google account; children can have a login of their own with no e-mail address. Sensitive changes are written to an audit log. When a school’s trial lapses or its plan is cancelled, nothing is deleted. Muzeqo Pty Ltd publishes a privacy policy and terms of service on its website.[1][4]
Keeping schools apart
Each request runs as an unprivileged database role chosen from the person’s membership, inside a transaction that records the person and the school. Row-level security policies limit the rows they can read to that school; column permissions keep staff-only fields, such as internal notes, from other roles; and composite foreign keys make it impossible to save a record that points at another school’s data.[1]
The About page states that the tests check this separation against a real database. A person who works at several schools uses one login and switches between them, but each school remains a separate tenant and no data is merged.[4][5] The public FAQ describes the database as PostgreSQL and invites schools to ask for the current hosting provider and region before signing up; the privacy policy says data is encrypted in transit and at rest and backed up daily.[5][6]
Who sees what
Each role inside a school — owner, admin, manager, billing, teacher, parent and student — holds a fixed set of permissions, which the office can adjust per member:[1][3]
- Owners and admins see everything, including settings, payments, policies, team access and the audit log (Office portal).
- Managers run day-to-day operations, and see finances only if the school allows it; billing staff see invoices, payments, teacher pay and financial reports.
- A teacher sees a student only with an active assignment or a recent or upcoming lesson, and sees a guardian’s contact details only if the school allows it (Teacher portal).
- Families see their own children; from a group lesson, each family sees only its own child’s copy of the lesson note, and other people appear by name and avatar only, never with their contact details (Family portal).
Signing in
There are three ways in.[1]
- Password: stored only as a hash. Sign-in and password recovery are throttled per address. “Forgot your password?” sends a single-use, expiring link to the account’s own address and signs the account out everywhere else. A security e-mail confirms every password change.[1][3]
- Passkeys: up to 10 per person, using Face ID, Touch ID, Windows Hello or a phone’s fingerprint or face unlock. A passkey is added under My account and always needs the device’s biometric or PIN; on the login page the browser offers saved passkeys from the e-mail box. Losing every passkey does not lock out anyone who still has a password.[1][2]
- Google: “Sign in with Google” links only to a confirmed account, so nobody can claim another person’s address in advance.[1]
Nobody joins a school because their e-mail address matches: staff and families join through a single-use invitation link that expires. There is no separate one-time-code step at sign-in; the feature page presents a passkey as the stronger alternative.[1][3]
Children
Students under 18 are guardian-centred: invoices, reminders and messages go to the guardian, and private messaging between a teacher and a child is off unless the school turns it on. Schools, not children, create student records.[6]
A guardian or the office can give a child a Child login with a username and password and no e-mail address. It shows the child’s own lessons, notes and a Questions thread that the parent can read and the teacher answers, but never the family’s money; the child cannot buy, change or cancel a subscription. Wherever children appear on a board or ranking, only first names are shown.[3][6]
Practice and the microphone
The Practice player, the tuner and the singing features listen in the browser and send nothing: the sound is analysed on the device, and takes are saved as measurements, never audio.[3][6] The Muzeqo AI Examiner receives note data only. A song recorded in Jam is published only where the student chooses.[3]
Muzeqo AI and personal information
The writing features of Muzeqo AI run only when the school has switched on “Drafts with Muzeqo AI”; otherwise nothing is sent for them. Translation for families runs while the school’s “Translate for families” setting is on, as it is unless the school turns it off, and the text a family reads in another language can include names, amounts, dates and e-mail addresses. A lesson note is drafted from the teacher’s rough lines with only the student’s first name and instrument, and reply suggestions mask names, e-mail addresses, phone numbers and links. The privacy policy sets out what each feature sends to the outside service that runs it, and states that card and bank details, teacher checks, and recordings and videos are never sent.[3][6]
Payments, audit and the website
Card and bank details are entered on Stripe’s forms and never reach Muzeqo; it stores only a card’s brand, last four digits and expiry (Billing and invoices).[6]
An append-only audit log records sensitive changes — settings, access, payouts, invoices, imports, sign-ins and exports — with who made each change and when. Owners and admins can filter it and export it as a spreadsheet, and every export is itself logged.[3]
Every response from the site carries security headers, including HTTP Strict Transport Security and a rule that only the site itself may frame its pages, apart from the enrolment form schools embed. Every upload is capped in size, documents and message attachments at 10 MB a file, and executable file types are refused. The privacy policy says a single session cookie keeps a person signed in, that the marketing pages set no tracking cookies, and that no analytics service is used.[3][6]
The site’s robots.txt lets the crawlers that gather text for training AI models read only Muzeqo’s own marketing pages and its llms.txt summary, and the server turns them away from every other page, including schools’ enrolment pages, teachers’ public profiles and job advertisements; search engines can still list those public pages.[7]
When a school leaves
Under the published principle “Nothing is deleted when you leave”, a lapsed trial or a cancelled plan only caps new additions; the school’s records stay, and the company provides an export on request.[4] Owners and admins can also download everything the school keeps as spreadsheet files in one zip, from Settings, under “Your data” (Data import and export).
The terms say school records belong to the school and are kept after a plan is cancelled or a trial ends, so that the school can return or export them, and are deleted within 30 days of the school’s written request.[8] As of 19 November 2026 the website offers no self-service way for a person to delete their own account; questions about Muzeqo’s own records go to help@muzeqo.com.[6]
Privacy policy and terms
The privacy policy and terms of service are published on the website and dated 5 November 2026. The privacy policy is written around the Australian Privacy Principles: it lists the service providers that process data, says what is collected, why and for how long, states that personal information is not sold and school records are not used for advertising, describes how notifiable data breaches are reported, and explains how to complain to the Office of the Australian Information Commissioner.[6] The terms are between Muzeqo Pty Ltd and each school, say that teachers see only their assigned students, and are governed by the law of Victoria.[8]
As of November 2026 the company’s own feature list describes both documents as awaiting legal review and kept out of search engines until then.[3]
See also
References
- abcdefghi“Security and sign-in”. Muzeqo Pty Ltd. Retrieved . Primary source.
- ab“How it works”. Muzeqo Pty Ltd. Retrieved . The section “One app, built like a school”.
- abcdefghijkl“Everything in Muzeqo”. Muzeqo Pty Ltd. Retrieved . The group “Security and privacy”.
- abcde“About Muzeqo”. Muzeqo Pty Ltd. Retrieved . The sections “Five things you can hold us to” and “How it is built”.
- abc“Frequently asked questions”. Muzeqo Pty Ltd. Retrieved . On the home page: “Where is my data stored and who can see it?” and “Can my teachers see every student?”.
- abcdefghi“Privacy policy”. Muzeqo Pty Ltd. . Retrieved .
- ^“robots.txt”. Muzeqo Pty Ltd. Retrieved . The rules for AI training crawlers.
- ab“Terms of service”. Muzeqo Pty Ltd. . Retrieved .
Facts last checked on .
