Privacy & Terms
Schools trust us with information about children. That deserves a page you can actually read, so this one avoids legal language wherever plain words will do.
Musdom is software that schools use to run themselves — admissions, attendance, classes, grades, tuition, staff hours and communication with families.
Almost everything in Musdom belongs to a school, not to us. When a school puts student records into Musdom, we hold that information on the school's behalf and act on its instructions. We do not decide what to do with a school's records; the school does.
US education privacy law lets a school share its records with a company acting as a school official under the school's direct control. Our student data privacy agreement is written to meet those conditions, and we sign it with the schools we work with. Ask us for a copy before you commit to anything.
There is a narrower set of information we hold in our own right: the account you create, the email address you sign in with, and basic records of how the site is used. This policy covers both.
About students: name, date of birth, gender, grade or level, preferred name, languages spoken at home, profile photo, attendance, grades and report cards, Qur'an memorization progress, and records a school keeps about injuries, illness and behavior. Health and safety details a school asks families for — allergies, medications, dietary needs, emergency contacts, and who is allowed to collect a child. Documents a family uploads, which commonly include birth certificates and immunization records. Free-text notes staff write about a child.
About parents and guardians: name, email address, phone number, relationship to the child, home address, notification preferences, profile photo, and a record of tuition invoices, payments, discounts and donations.
About staff: name, email, phone, job title, employee number, start date, biography, profile photo, clock-in and clock-out times, pay rate and allowances, and the hashed PIN used at a front-desk screen.
About applicants: the same student and parent details as above, gathered before a child enrolls, plus anything the school's own application form asks, and whether the family has asked about financial assistance.
Musdom has no built-in field for social security numbers or other government ID numbers, and we never ask for one. A school can still build its own question asking for one, and a family can attach a document containing one. If you would rather that did not happen at your school, do not ask for it.
To provide the service the school is paying for, and nothing else. That means showing the right information to the right person, sending the emails and messages a school asks us to send, producing its reports, and taking tuition payments on the school's behalf.
We also use a small amount of usage information to keep the product working and to understand which parts of it people struggle with.
We do not sell personal information, and we never will.
We do not use student information for advertising, and we do not target advertising at students or families. Musdom carries no advertising at all.
We do not build profiles of students for any purpose other than the school's own educational use.
We do not use school data to train artificial intelligence models. No AI service receives student information from Musdom.
One school's staff cannot open another school's records. There is one deliberate exception, and it is worth reading carefully. A family is a single record shared by every school its children attend — so where a family attends more than one school using Musdom, each of those schools sees the whole household: every child by name, photograph, grade and date of birth, including a child it does not itself enroll, along with the household address and the other parent's contact details. Shared household details — the family surname, the address, a parent's name and phone number — can be corrected by any of those schools, and the correction is shared. A child's own details can only be changed by a school that child actually attends or has applied to; a school where only their sibling attends can see them but cannot edit them.
What does not cross over is that other school's own work: its attendance, grades, fees, forms, documents and notes stay with the school that recorded them.
This only ever reaches a school your family actually joined, or has been part of before. A school you have only applied to does not get it — applying is not joining — and a school your family has no connection with cannot see your household at all.
Running Musdom means relying on a small number of other companies. Each one is listed below with what it does and what reaches it. We do not add a new one that handles personal information without updating this list.
| Company | What it does | What reaches it |
|---|---|---|
| Supabase | Stores the database, the uploaded files, and the sign-in system | Everything in Musdom |
| Vercel | Runs the website, and measures how quickly pages load | Web traffic, anything passing through a page as you use it, and timing measurements from each visit |
| Stripe | Takes tuition and fee payments into the school's own account | Payer name and email, the amount, and the invoice description, which can include a child's name. Card and bank numbers go straight to Stripe and never reach Musdom |
| Resend | Delivers the emails Musdom sends | The recipient's email address and the contents of the email, which can include a child's name |
| Cloudflare | Checks that a person, not a bot, is signing in | Your IP address at sign-in, sign-up and password reset |
| PostHog | Tells us which parts of Musdom get used and where people get stuck | Your email address, the pages you visit, recordings of your sessions (what was on the screen, including any student details shown, and where you clicked and scrolled — not what you type), and your IP address, browser and device. Only Musdom's two founders can see these, and only to understand where Musdom is hard to use |
| Mapbox | Draws maps, and completes an address as it is typed — on events and on a school's own address | The address being typed, event and school locations, and the IP address of whoever loads a map |
| Calendly | Books demonstration calls from our public site | The name, email address and school of anyone who books a call with us |
| Google Fonts | Serves the icon font the pages are drawn with | Your IP address and browser, when a page loads |
Profile photographs of children, parents and staff are stored privately. They are loaded through a link created when a signed-in person views the page, which then works for up to an hour. Anyone that link is forwarded to could open the photograph during that hour without signing in, so treat a copied image link as something worth not forwarding.
Five things are different: photographs attached to a school event, event banners, school logos, and the cover and about photographs on a school's public page. Those are published at a plain web address that anyone holding the link can open, without signing in, and they stay reachable. This is true even when the event itself is visible only to your own families — the page is protected, the photograph is not. A school posting event photographs should treat them as public. If your school needs photographs kept behind a sign-in, do not post them to an event gallery, and tell us — Musdom does not do that today.
Musdom sets a cookie to keep you signed in, a ten-minute cookie when a school connects its payment account, a year-long cookie on a front-desk screen so it stays paired, and a cookie lasting up to eight hours when a Musdom administrator is viewing the system as another user in order to support them.
Our analytics tool sets its own cookie to recognize a returning browser, and the bot check on our sign-in, sign-up and password-reset pages may set one too.
We carry no advertising cookies, no tracking pixels, and no third-party marketing tags of any kind.
While a school is using Musdom, its records are kept for as long as the school wants them. Schools need history: last year's attendance, a leaver's report card, a paid invoice from three years ago.
When something is deleted in Musdom it is normally hidden rather than erased, so that a mistaken deletion can be undone and so that history stays intact. Audit trails are kept and are not deleted.
When a school leaves Musdom, we prepare its data and hand it over, then delete it from the live system within sixty days of the end of the agreement — unless the school asks us in writing to keep it for longer, or the law requires us to. Copies sitting inside routine backups go when those backups roll over on their ordinary cycle.
Information travels to and from Musdom over an encrypted connection, and the platforms we store it on encrypt it where it sits. Uploaded files — documents families send, immunization records, curriculum files, attachments on an announcement — are held privately and reached through links that expire, with the exception of the five public images described above.
Who can see what is decided by that person's role. A parent sees their own children and nobody else's. Teaching and office staff can see every student at their own school, including the health and safety details a school needs staff to know, and can see their colleagues' staff records. Money, admissions, pay and the office side of an incident record are narrower, and are limited to the roles that need them.
A small number of Musdom staff can access school data when they need to in order to support you or fix a fault. We tell you plainly that this is possible rather than implying it is not.
No system is perfectly secure, and we would rather say so than promise otherwise. If personal information held in Musdom is exposed, we will tell the affected school without undue delay and no later than seventy-two hours after we become aware, with what we know and what we are doing about it.
If you are a parent or an eligible student and you want to see, correct or delete a student record, ask your school. The records belong to the school, education law gives you those rights against the school, and we are not allowed to change a school's records on your say-so. Tell your school, and we will help them do it.
For anything else — your own account, an email you do not want, a question about this policy — write to hello@musdom.com and a person will answer you.
Children do not put their own records into Musdom. Student information reaches us only because a school put it there to run its classroom, and the school provides the consent the law allows it to give on a parent's behalf for that educational purpose. We use it for nothing else. Musdom is not designed or marketed for children to use directly, and we do not knowingly keep an account created by one.
If we change this policy in a way that matters, we will tell the schools using Musdom rather than quietly changing this page.
Musdom is provided by Musdom LLC, a Washington limited liability company ("Musdom", "we", "us"). These terms cover use of Musdom. A school also signs a separate agreement with us covering price and term, and we offer a student data privacy agreement covering how student records are handled. Where a signed agreement and these terms disagree, the signed agreement wins.
You need an account to use Musdom, the details you give us should be true, and you are responsible for what happens under your sign-in. Tell us promptly if you think someone else has got into your account.
Staff accounts are created by the school. A school can remove them, and we act on the school's instruction when it does.
Use Musdom for running your school. Do not try to reach another school's information, do not attempt to break or overload the service, do not upload anything unlawful, and do not use it to harass anyone.
A school is responsible for what its staff and families put into Musdom, and for having the right to put it there.
A school's records belong to the school. We hold them to provide the service, we act on the school's instructions, and we do not sell them or use them for our own purposes.
We do use general, non-identifying information about how the product is used to make it better. That never involves handing a school's records to anyone else.
A school pays what its agreement with us says, on the schedule it sets out. Prices are agreed in writing, not set unilaterally on a web page.
Payments that families make to a school through Musdom go directly into that school's own payment account. Musdom does not hold that money and takes no cut of it. What a family owes a school, and any refund of it, is between the family and the school.
We work hard to keep Musdom available, fast and correct, and we fix things quickly when they break. We do not guarantee that it will never be unavailable or never contain a fault.
Musdom is a record of what a school puts into it. It is not a substitute for a school's own judgment, and it is not legal, financial or medical advice.
Except where the law does not allow us to limit it, our liability to a school is limited to what that school paid us in the twelve months before the problem arose.
A school can stop using Musdom as its agreement provides. We can end an account that is being used to break these terms, and we will say why.
When a school leaves, we prepare its data and hand it over, then delete it from the live system within sixty days, unless it asks us in writing to hold it longer. Copies inside routine backups go as those backups roll over.
We may update these terms. If a change matters, we will tell the schools using Musdom before it takes effect.
These terms are governed by the laws of the State of Washington, and its courts are where any dispute about them is decided.
Questions about any of this, or a request about your own information, go to hello@musdom.com. Schools evaluating Musdom can ask us for our student data privacy agreement and our answers to your security questions — we will send both without making you chase us.
Still deciding? The questions schools ask us covers the practical ones.