Skip to content
Made to Teach

Legal

Privacy Policy

Effective date: 2 April 2026
Applies to Made to Teach websites, the Made to Teach mobile app, import.madetoteach.com.au, and related services.

Made to Teach respects the privacy of teachers and school staff who use our websites, mobile app, timetable import tools, and related services. This Privacy Policy explains how we collect, use, store, and disclose personal information when you use Made to Teach.

We handle personal information in line with the Privacy Act 1988 (Cth) and the Australian Privacy Principles where they apply.

1. Who this policy covers

This policy applies to:

  • Made to Teach websites and support channels,
  • the Made to Teach mobile app on iOS and Android,
  • the timetable import site at import.madetoteach.com.au, including the one-time code flow that connects the site to the app,
  • teacher accounts, timetable drafts, synced app data, and related support or operational activity.

2. What information we collect

We collect information that is reasonably necessary to operate the service, keep it secure, and support the app.

2.1 Account and profile information

  • name or display name, email address, and sign-in provider details,
  • timezone, school country or state, teaching focus, and onboarding preferences,
  • account status, product entitlement, or subscription status connected to your Made to Teach account.

2.2 App content and service data

  • classes, timetable entries, reminders, assessments, notes, and other planning content you create in the app,
  • the one-time import code generated inside the app,
  • timetable files you upload, such as recurring grid .pdf files or .ics exports,
  • calendar event details needed to build a timetable draft, including titles, times, recurrence details, and locations,
  • draft timetable rows and review outcomes created through the import flow,
  • support messages or emails you send to us.

2.3 Images and attachments

  • photos or images you take or attach inside the app,
  • image metadata and storage references needed to display those attachments across your devices where cloud sync is enabled.

2.4 Technical and device information

  • IP address, browser type, app or device metadata, and request timestamps,
  • error logs, session activity, and technical diagnostics used for security, support, and operational debugging,
  • cookies required to keep a claimed import session attached to the current browser, plus analytics cookies or similar browser storage if we enable website measurement tools such as Google Analytics,
  • aggregated website usage and search performance information from tools such as Google Analytics and Google Search Console,
  • device identifiers, local storage entries, and secure device tokens needed to keep sign-in, import access, sync, settings, or similar app features working.

2.5 Notifications and widgets

  • notification preferences and locally scheduled reminder data if you enable reminders,
  • limited upcoming schedule or planning information written to device widget storage if you enable home screen widgets.

3. How app data is stored and synced

Some parts of Made to Teach can be used in a local-only mode. In that mode, core app data is stored on your device rather than in our cloud backend, unless you separately use a cloud-connected feature such as timetable import.

If you sign in to a cloud account, we may sync profile and planning data through our backend so that it is available across supported devices and sessions.

Authentication tokens and temporary import access tokens may be stored using secure device storage where available. Depending on your account mode, images may remain on-device or be uploaded to our cloud storage so they can be retrieved later.

4. How we use information

  • to operate the website, mobile app, timetable import flow, and related support services,
  • to authenticate users, keep sessions secure, and connect a browser upload to the correct teacher account,
  • to parse calendar files and create timetable drafts for review in the app,
  • to save, sync, restore, and display the planning data you choose to keep with Made to Teach,
  • to schedule reminders or support widget features on your device where you enable those features,
  • to process or restore subscription entitlements and account status,
  • to secure the service, prevent misuse, investigate errors, and improve the product,
  • to understand website traffic, landing pages, and search visibility so we can improve the website and import flow,
  • to comply with legal obligations and respond to lawful requests.

5. Device permissions

The app may request access to certain device features so that optional functionality can work.

  • Notifications: to schedule local reminder alerts if you turn them on.
  • Camera or photo library: to let you take or attach images to reminders, notes, or other app content.
  • File picker access: to let you select timetable files or image files from your device.

You can usually decline these permissions, but the related feature may not work properly until access is granted.

6. Calendar content, student privacy, and sensitive information

Calendar exports can sometimes include more than timetable structure. Depending on the system used by a school or teacher, an uploaded file may contain class names, room names, teacher-entered notes, or in some cases student names embedded in event titles or descriptions.

Made to Teach does not want or require formal student records for timetable import. We ask users to upload the narrowest timetable file available and to avoid uploading unnecessary student-identifying or sensitive information.

We do not create a student record system from imported files. The import flow is intended only to turn timetable structure into a draft recurring timetable inside the app.

7. When we may disclose information

We may disclose information to trusted service providers that help us operate Made to Teach, such as:

  • Supabase for database, authentication, storage, and backend services,
  • Vercel for web hosting and deployment infrastructure,
  • Google for website analytics, search performance reporting, and related web infrastructure tooling,
  • Apple or Google when you use their sign-in, app distribution, device, or purchase services,
  • RevenueCat for subscription entitlement and purchase support,
  • professional advisers, security providers, or regulators where reasonably necessary.

We do not sell personal information.

8. Cross-border processing

Some of our service providers may process or store information outside Australia, including in the United States or other jurisdictions where their infrastructure operates. Where that happens, we take reasonable steps to work with providers that offer appropriate security and privacy protections.

9. Retention

Local-only app data generally stays on your device until you delete it, clear app storage, or uninstall the app.

Account-linked data is retained while your account remains active and for as long as reasonably necessary to support the service, security, backups, support, legal compliance, or operational needs.

One-time import sessions are temporary. Pending or unused sessions may expire automatically. Parsed timetable draft rows are retained only as long as reasonably necessary to support the import and associated support, security, or operational needs.

We aim not to keep raw uploaded files longer than necessary for processing. Where feasible, we parse the file to the required timetable draft data and avoid treating the raw file as a long-term store of record. If you tell us that a PDF timetable did not extract correctly, we may keep that PDF for a short period so we can improve the parser, then delete it once it is no longer needed for that work.

10. Data security

We use reasonable technical and organisational measures to protect information against unauthorised access, misuse, loss, or disclosure.

  • restricted backend access,
  • secure account and token storage where supported on the device,
  • short-lived import codes and session expiry,
  • signed session cookies,
  • role-based database access and infrastructure controls.

No online system can be guaranteed perfectly secure, but we aim to keep the risk proportionate and well managed.

11. Access, correction, deletion, and complaints

If you want to request access to, correction of, or deletion of personal information we hold about you, contact us at privacy@madetoteach.com.au.

If you believe we have mishandled your information, contact us first so we can investigate. If you are not satisfied with the outcome, you may contact the Office of the Australian Information Commissioner at oaic.gov.au.

12. Changes to this policy

We may update this Privacy Policy from time to time as the product evolves. The latest version will be published on this site with a revised effective date.

Copyright 2026 Made to Teach

PrivacyTerms