Privacy policy

When you create an account: your email and a hashed password (we never store the password itself), your display name, and your role.

When you create a student profile: name, year level, optional state, learning preferences (session length, scaffold level), interests, and any context you provide about how they learn best. If you choose to, you can also tell us about learning differences (ADHD, dyslexia, dysgraphia, dyscalculia). These count as health information, so we only keep them after you tick a box to agree (see section 5).

Schoolwork you add: photos, PDFs, documents and report cards. These often show more than the questions, for example your student's name, their school or a teacher's name. Please crop or cover anything you would rather we did not see.

As your student uses Masterly: every session, answer, grade, and the records we build from them (mastery, weekly insights, work items). We store enough to make the product work, and not more.

Technical data: IP address, browser type and timestamps for security and abuse prevention, and error reports when something breaks.

Running the product: building daily sessions, grading attempts, computing mastery, generating insights, sending notifications you've opted into.

Operating the business: billing through Stripe, sending account emails (email verification, password resets, account deletion confirmation), customer support.

Improving the product: error reports and aggregated usage patterns to find bugs and improve features. We don't use your or your student's data to train AI models, and OpenAI does not use data sent through its API to train its models.

We don't sell your data. We don't have advertisers. The only other companies that handle your data are the service providers we use to run Masterly:

• BinaryLane (Sydney, Australia). Hosting. Our server, database and uploaded files live on a BinaryLane virtual server in Sydney.
• Cloudflare. Sits in front of the site: domain names, encryption, protection against attacks, and the secure tunnel to our server. Everything you send to Masterly passes through Cloudflare's worldwide network on the way. Cloudflare also stores our off-site backups (Cloudflare R2) in a private, access-controlled bucket, and forwards email sent to our support and privacy addresses to our inbox.
• OpenAI (United States). AI grading, content generation and safety checks. Sees the questions, the answers sent for AI grading, the worksheets and report cards you upload, and the learning details that shape content: year level, the general themes we match from interests (like "gaming" or "animals and pets", never the words you typed), the learning context you write, learning differences you have added, and in some requests your student's first name. OpenAI does not use API data to train its models. It may keep API data for up to 30 days to detect abuse, then deletes it. Some lessons include pictures that OpenAI draws for us. Those are made from the lesson's own text only - a short description of the picture - and no student information is sent with them. The same pictures are reused for every student who gets that lesson.
• Stripe. Payment processing. Sees your billing details, not student learning data.
• Resend. Sends account email (verification, password resets, deletion confirmation). Sees your email address and the message.
• Sentry. Error monitoring for the website, the app and our server. When something breaks it receives a technical report: what failed, the page address and the browser type. It is set up not to collect personal information by default, and never records sessions or screens.
• Google Analytics. Counts visits to our public pages (home, pricing, help and pages like this one) using cookies. It never runs inside the signed-in parent or student app.
• Your web browser's speech service. If your student uses the microphone button to dictate an answer, the browser turns speech into text, not Masterly. Some browsers, including Chrome, send the audio to the browser maker's speech service to do this. Masterly never receives or keeps the audio, only the typed result. The "Read aloud" button works the other way and stays on the device: it only uses voices built into the device, never an online voice, so the text it reads is not sent anywhere. If the device has no built-in voice, the button doesn't appear.

We'll only ever share data with law enforcement if legally compelled - and we'll tell you unless legally prohibited.

Our database and your uploaded files are stored in Sydney, Australia. Off-site backups are kept in private, access-controlled storage with Cloudflare.

Some of the providers above handle data outside Australia, mostly in the United States: OpenAI, Stripe, Resend, Sentry and Google. Cloudflare's network runs in many countries. We send each provider only what it needs for its job, and choose providers that publish their privacy and security commitments. By using Masterly you agree to this data going overseas for these purposes.

Masterly is operated by the parent or guardian. Student profiles are created by the account holder, who is responsible for obtaining any necessary consent.

Learning differences are optional. We only keep them after you tick the consent box, we use them only to adapt lessons and grading, and we share them with no one except OpenAI to shape the content it writes. Untick them in Settings at any time to remove them, which also withdraws your consent.

We design the student-facing experience to minimise data collection: no advertising and no analytics or tracking inside the app. Error monitoring (Sentry) runs there so we can fix problems. Student responses and grades are only ever shown to the student and the adults on your account who have access to that student.

If you're subject to COPPA (United States), GDPR (European Union), or similar frameworks, the rights below apply with no extra steps. Contact us if you'd like the legal bases documented in detail for your jurisdiction.

You can, at any time:

• Access. See everything we store about you and your students. Settings → Privacy → Download my data.
• Correct. Edit your profile, your students' profiles, and the learning context we use, including removing learning differences.
• Export. Download a JSON archive of your account and history.
• Delete. Permanently delete your account and every record we associate with it. This includes student profiles, work items, sessions, attempts, and the insights we've generated. Deletion is immediate and irreversible.
• Object. Tell us if you'd rather we didn't process your data for a specific purpose. We'll either accommodate or explain why we can't.
• Complain. If you are not happy with how we handle a privacy concern, you can contact the Office of the Australian Information Commissioner at oaic.gov.au.

Data in transit is protected by TLS. Passwords are stored only as slow, salted hashes (PBKDF2). Sign-ins use short-lived tokens with rotating refresh tokens, kept in a sign-in cookie that only our server can read. It is needed to keep you signed in and is never used for tracking. Our server accepts no direct connections from the internet; traffic reaches it only through Cloudflare's tunnel. Off-site backups are kept in private, access-controlled storage.

No system is unbreakable. If we ever experience a security incident affecting your data, we'll notify you without undue delay and tell you what we know, what we don't, and what we're doing about it.

Active accounts: we keep your data for as long as your account exists. Behind-the-scenes records are cleared out automatically: background task records after 30 days, notifications you have read after 90 days, AI usage records (counts and costs, never content) after 13 months, and activity logs after 2 years. Records of your consent, and of deletions, are kept for as long as the account exists.

Cancelled subscriptions: your data stays on a Free-plan account; you can come back any time.

Deleted accounts: removed from our database straight away. Copies in backups expire on their own: backups on our server after 14 days, off-site backups within 90 days. OpenAI may keep request data for up to 30 days, and error reports expire in Sentry. Deletion logs and legal records may persist longer where required by law.

We'll update the “last updated” date above whenever this policy changes. Material changes (anything affecting your rights or how we share data) will also be emailed to active account holders with at least 30 days' notice.