Loading…
Legal
Last updated: 5 November 2026.
Muzeqo is music school management software operated by Muzeqo Pty Ltd from Victoria, Australia. This policy covers the Muzeqo website and the application. Each school that uses Muzeqo is responsible for the personal information it enters about its own students, families and staff; Muzeqo processes that information on the school’s behalf.
Our address is Level 15, 28 Freshwater Place, Southbank VIC 3006, Australia.
Account details (name, e-mail address, phone number where given, password hash, passkey public keys, linked Google account identifier). School records entered by the school: students, guardians, teachers, lessons, attendance, notes, invoices and payments, messages. Enquiries sent through the contact form (name, e-mail, phone, school or organisation, message and, if given, roughly how many teachers, schools or campuses and students). Technical data: sign-in events, IP addresses used for throttling, audit-log entries.
Card details are never collected by us: Stripe hosts the card form and we store only the card brand, last four digits and expiry.
Practice memberships: when a parent subscribes to the practice tools, we record who subscribed, which students the membership covers, its status and dates, the amount paid and Muzeqo’s share, and the Stripe identifiers for the customer and subscription. Card and bank details are entered on Stripe’s pages and never reach Muzeqo. Practice activity (the pieces played, tempo, accuracy results from “Check my playing”) is stored for the student and visible to the family and, where the school has turned sharing on, the teacher. Nothing from the microphone is recorded or sent anywhere.
Learn at home: when a parent or an adult learner with no school joins, we record their name, e-mail address and password hash, the names of the learners, the plan chosen, the status and dates of the subscription (free days, period end, cancellation, a failed payment) and the Stripe identifiers for the customer and subscription. Because no school is involved, Muzeqo itself is responsible for this information. Practice activity is handled as described above.
Teacher CVs and teacher checks, which a teacher chooses to add, are described in their own sections below.
To provide the service a school has signed up for: scheduling, invoicing, payments, messaging, teacher pay and reporting. To send transactional e-mails and texts (invoices, reminders, invitations, statements, confirmations). To keep accounts secure and investigate misuse. To answer enquiries. We do not sell personal information and do not use school records for advertising.
Service providers who process data for us under contract: Stripe (payments and subscriptions), Resend (e-mail delivery), Twilio (text messages), Anthropic (Muzeqo AI, only while a school has it turned on: it receives the text a staff member is drafting, with a student’s first name at most, and the notes of pieces — never surnames, contact details, payments or health notes), our database and hosting providers. Each receives only what its function needs. The application runs on Fly.io in Sydney and its database is hosted by Supabase in Sydney, so school records are stored in Australia. Stripe, Resend, Twilio and Anthropic are United States companies and process what they receive there, so the e-mail addresses and phone numbers that messages are sent to, the payment records Stripe holds, and the text sent to Muzeqo AI are disclosed overseas (Australian Privacy Principle 8). The player’s sound recordings are served by a content delivery network, Bunny.net, which receives no personal information.
YouTube (Google LLC, United States), only when a family chooses Sing with YouTube in the practice tools: the search words typed go to YouTube, and the chosen video plays in YouTube’s own embedded player under Google’s privacy policy. No account or student details are sent.
A family buys the practice tools from Muzeqo itself, never through its school, so its payment record is in Muzeqo’s own Stripe account; the school sees only that the family has them. Nobody at Muzeqo or the school sees card or bank details. Stripe stores payment records in the United States.
For Learn at home, Muzeqo is the seller, so the customer record is in Muzeqo’s own Stripe account and not in any school’s.
Students under 18 are guardian-centred: invoices, reminders and messages go to the guardian, and private teacher-to-child messaging is off unless the school turns it on. Schools, not children, create student records. In Learn at home the parent or adult learner creates the learner records.
A practice membership or a Learn at home membership is always bought by an adult (a parent or an adult learner). A child’s own login can use the tools the membership covers but cannot buy, change or cancel it.
Each school’s data is separated by database row-level security; access is by role; sensitive actions are written to an audit log; tokens are stored hashed; sign-in and recovery are throttled. Data is encrypted in transit and at rest by our hosting providers. The database is backed up daily and the backups are kept in Australia for a short rolling period. If a data breach is likely to cause serious harm, we notify the people affected and the Office of the Australian Information Commissioner as the Notifiable Data Breaches scheme requires, and we tell the school whose records are involved as soon as we can.
School members can see and correct their own details under My account. Schools manage their own records. For access or correction requests about information a school holds, contact the school first; for anything about Muzeqo’s own records, contact us at help@muzeqo.com. A school’s records are kept while its account exists, including after a plan is cancelled, so the school can return or export them; we delete them within 30 days of the school’s written request.
Membership and payment records (practice memberships and Learn at home) are kept for seven years as tax records; practice activity is kept while the student’s record exists and deleted with it.
A teacher may keep a CV in Muzeqo. It belongs to the teacher, not to a school, and the teacher keeps it if they leave every school. It holds what the teacher writes (a headline, an About me, other teaching experience, education and training, repertoire, styles, skills and languages), their e-mail address and mobile number if they choose to show them, and a teaching record. We collect it so the teacher can show their experience to the schools and employers they choose, and print or save it.
The teaching record is worked out from each school’s records of the lessons the teacher taught there, and is stored as counts only: a rounded number of lessons, a band for the number of students (for example 20–49), the instruments, and whether lessons were in groups, online or at other schools. It never includes a student’s name, and the CV warns the teacher if a student’s full name appears in text they write. The counts are a snapshot, refreshed when the CV is opened if it is more than a day old, and kept as it was if the teacher’s membership at a school is suspended. A school appears by name only if its office chooses, and a school can switch the counts off for its teachers.
Only the teacher sees their CV unless they share it. A teacher can make a private link, open for 7, 30 or 90 days, with their contact details off unless they switch them on for that link, and can turn it off at any time. Anyone who has the link can read the CV while it is active, and the page asks search engines not to index it. We count how many times each link is opened and record each link being made, opened or turned off in a log the teacher can read. We do not store the reader’s address or name: a code that changes daily and cannot be turned back into an address is used only to limit repeated opens. Only a one-way hash of the link’s token is kept, so a link is shown once.
A link is deleted 90 days after it expires or is turned off. The log of who opened a link or looked at a CV or check is kept for two years. A CV and its teaching record are kept while the teacher’s account exists.
When a teacher closes their account the CV and its teaching record are deleted with it, and they leave backups in the normal backup cycle.
A teacher can read, correct or hide anything on their CV in the app, can see who has opened it, and can ask us to delete the whole CV. A count that is wrong comes from a school’s records, so the school corrects it; if the school cannot, contact us at help@muzeqo.com. For complaints, see Complaints and contact below.
A teacher may ask Muzeqo to check a qualification or registration: a Working with Children Check, a teacher registration, a degree, first aid or CPR training, or an ABN. For each we record the kind of check, the number on the card or register entry, the name shown on the register, the result (current, not current, due for a recheck, expired or not found), the date we checked and the expiry the register shows. We keep the last four digits of the number and a keyed fingerprint of it, so we can spot the same card on two accounts and confirm a number entered again at a recheck, and a log of who has looked and when. For a degree or first aid training the teacher gives us a share link from the issuer; it is opened once and deleted. We do not take uploads of documents.
We use checks only to show a “Checked by Muzeqo” badge on the teacher’s CV and to the schools the teacher chooses, to ask for a recheck when one falls due, and to spot the same card on two accounts. A check records only what a register showed on the day we looked, so we say “checked”, never “verified”. A check can reveal criminal-history information, for example whether a Working with Children Check is current, so we collect it only with the teacher’s consent, given in the app before the first check. Adding a check is optional, and a teacher can withdraw one at any time.
The teacher sees every check and who has looked at it. A small number of Muzeqo staff do the checking: each signs in with a passkey and a recent re-sign-in, sees a check only while it is open, and cannot decide their own. Every time staff reveal a number it is logged for the teacher to see.
A school sees a check only if the teacher has chosen to share it with that school. It then sees the status, the date last checked, the expiry and the last four digits, never the full number, the document or the history. If a check is confirmed as not current, we ask each school where the teacher has lessons in the next 60 days, and each school the teacher shares with, to check the teacher’s card itself; the notice is neutral and does not say what the result was. A first “not found” result goes only to the teacher. Anyone with a live CV link the teacher has made sees the badge, or that a check is due for a recheck or has expired.
Numbers are encrypted when entered and are never put on a CV, a link, an e-mail, a text message or a log. Notices about checks are sent in the app, by e-mail through Resend and, if texts are used, by text message through Twilio. Both are overseas providers, and a notice carries no check details, only that there is an update to sign in and see. No AI service or other outside service receives any check.
The full number and any share link are deleted as soon as the check is decided; if nobody has looked at one within 30 days it is deleted and the teacher is told. The result, without the number, is kept for 12 months after the teacher withdraws the check or closes their account, and the log of who looked is kept for two years. Backups are cleared in the normal backup cycle.
Check records are stored in the same Sydney database as everything else, encrypted at rest by the hosting provider, and the numbers themselves are encrypted again by Muzeqo under a key only Muzeqo holds. Notices go out through Resend and Twilio, which process them in the United States; a notice never carries check details. A check notice is sent by text only if the teacher has given a mobile number for texts. Checks are done by a small number of named Muzeqo staff.
A teacher can see all their checks, and who has seen them, in the app, and can correct or withdraw a check. If the register shows a different name from the teacher’s, we ask the teacher about it rather than guess. To ask for a copy of a record, a correction or a deletion, or to complain, contact us at help@muzeqo.com. If you are not satisfied with our response you may complain to the Office of the Australian Information Commissioner (see Complaints and contact below).
A teacher may upload sheet music for their own teaching: a MusicXML or MIDI file, or a PDF or photo of a printed page. We keep the file’s name, size and fingerprint (SHA-256), the notation our own software read from it, the teacher’s confirmation that they hold the rights to it and when they gave it, and, if it is taken down, who did so and why. A PDF or photo is read on our own server and deleted as soon as it has been read; the original is never kept.
An uploaded piece is private to the school that uploaded it: its staff can see it, and a family only while it is assigned to their child. It is never published, offered to other schools or added to Muzeqo’s library, and it is removed if a rights holder asks.
When a school has Muzeqo AI turned on, the notes of an uploaded piece — its title, level and notation, never a student’s or teacher’s name — are sent to Anthropic, the AI provider behind Muzeqo AI, so that it can plan how the piece is played: phrasing, dynamics, pedal, fingering and tips a teacher can read to a child. Anthropic processes this for Muzeqo under commercial terms that do not allow it to train its models on what we send, and Muzeqo does not train any model on uploaded music either. Anthropic processes it in the United States.
Some changes happen automatically on a date or when a payment status changes, without a person deciding each time. A person can ask us to review any of them: contact us at help@muzeqo.com.
Trials and plans: a school’s free trial ends on its date, and new additions are capped until a plan is chosen. A school plan paid by e-mailed invoice moves to “on hold” if the invoice is unpaid after its due date, and comes off hold when it is paid. A family’s free days end on the date shown and payment then starts; we send a reminder before.
Subscriptions: if a payment for a family’s own subscription fails, access continues for 14 days while payment details are updated, and then the subscription ends. Receipts and reminders are sent by e-mail.
Teacher checks: reminders go out before a check expires (for a Working with Children Check, 90, 30 and 7 days before). When the register’s expiry passes, the check turns “expired” and leaves the CV. When a recheck falls due, or the teacher’s name on Muzeqo has changed, the teacher is asked to enter the number again. A number nobody has looked at in 30 days is deleted. A CV link stops working on its expiry date.
A single session cookie keeps you signed in. The marketing pages set no tracking cookies, and we use no analytics service.
Write to help@muzeqo.com. If you are not satisfied with our response you may complain to the Office of the Australian Information Commissioner (oaic.gov.au).