Privacy Policy

1. About This Policy

Sky Network Pty Ltd (ABN 63 145 355 353) ("we", "us", "our") operates TeacherAI ("the Service"), an educational platform designed to help teachers deliver personalised learning experiences to their students.

This Privacy Policy explains how we collect, use, disclose, and safeguard personal information in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). As we handle data relating to students in Australian schools, we take our privacy obligations extremely seriously.

2. Information We Collect

2.1 Teacher Information

When teachers register and use TeacherAI, we collect:

• Full name and email address
• School or organisation name
• Teaching subjects and year levels
• Account credentials (passwords are securely hashed)
• Billing information for paid subscriptions (processed securely via Stripe)

2.2 Student Information

Student accounts are created by teachers or parents. We collect minimal information:

• Full name
• Email address
• Gender
• Year level
• Class enrollments and course progress
• Lesson responses, assessments, and grades

2.3 Handwriting Data (where Handwriting Mode is used)

Where a teacher or school enables Handwriting Mode for lessons or assessments, we additionally collect:

• Stroke data: pen coordinates (x/y position), timing between strokes, and stylus pressure readings captured during handwriting activities
• Canvas images: PNG snapshots of completed handwriting stored in our secure file store
• Neatness metrics: automatically calculated scores for stroke consistency, baseline alignment, and letter height
• Recognition output: text transcribed from handwriting by on-device recognition (where available)
• Coaching interaction logs: records of AI coaching nudges shown and subsequent writing activity, used to measure coaching effectiveness
• Input device type: whether input was made with a stylus, finger, or mouse

This data is collected as part of completing educational activities. It is used to deliver the handwriting feature (marking, feedback, neatness scoring) and, in de-identified form, to improve our handwriting recognition and coaching systems. See Section 4.3 for full details.

Important: We do not collect sensitive information such as health records, religious beliefs, or government identifiers from students.

2.4 Whiteboard and Annotation Data

Where a teacher uses the Whiteboard or Annotation features during a lesson, the following data may be collected:

• Stroke data: drawing strokes including pen coordinates, colour, width, tool type, and timestamps
• Canvas snapshots: image captures of whiteboard or annotation content, saved as WebP files in our secure file store
• Audio recordings: optional voice recordings made by the teacher during whiteboard sessions
• Video recordings: optional webcam recordings made by the teacher during whiteboard sessions

This data is collected to enable real-time broadcast of teacher annotations to students during live lessons, and to provide post-class access so students can review whiteboard content and replay annotated explanations. Whiteboard data is stored in our Australian servers (see Section 6). Ephemeral stroke data used during live sessions is held temporarily and automatically expires after the lesson ends. Saved snapshots and media are retained per the retention schedule in Section 9.

2.5 Practice Set Data

When students use Practice Sets, we collect:

• Responses: answers to practice questions, including multi-step procedural responses
• Auto-grading results: scores calculated automatically by the platform for supported question types
• Hint usage: which hints were revealed and at which levels
• Mastery scores: per-set mastery levels calculated from session performance over time
• Session metadata: adaptive difficulty level, items attempted, time spent

This data is used to provide adaptive practice experiences, track student progress, and generate feedback for teachers. Where AI feedback is enabled, student responses to open-ended questions may be sent to AI providers for feedback generation (see Section 4.2).

2.6 AI Chat Transcript Data

When students use AI chat features (lesson chat, AI tutor, explanation rating, pre-submission checks, prompt engineering practice), we store:

• Full conversation transcripts: both student messages and AI responses, stored server-side
• Token metrics: input and output token counts per message for usage tracking and cost management
• Session metadata: feature type, lesson/class context, AI model used, timestamps
• Topic summaries: brief topic labels for rate limiting and usage monitoring (separate from full transcripts)

Why we store full transcripts: Server-side transcript storage is maintained to meet Australian child safety standards, school audit obligations, and emerging regulatory requirements under the Privacy and Other Legislation Amendment Act 2024 (automated decision-making transparency) and the anticipated OAIC Children's Online Privacy Code (expected 2026). Transcripts enable schools to audit AI interactions with students, investigate AI-generated feedback on assessed work if concerns arise, and demonstrate compliance with child safe obligations. Message content is capped at 8,000 characters per message. Full transcripts are retained for a minimum of 12 months. Topic summaries are retained for 90 days and then automatically deleted. See Section 9 for full retention details.

2.7 Usage Information

We automatically collect:

• Device type and browser information
• IP address (used for security and anonymised for analytics)
• Pages visited and features used
• Time spent on lessons and activities

2.8 Academic Integrity and Originality Data

Where a school or teacher enables integrity and originality features on an assessment, and while a student completes that work, we may collect:

• Process and editing signals: events such as pasting large blocks of text, switching away from or back to the assessment, exiting full-screen, and unusual timing or single-save insertions
• Writing-style indicators: automated analysis of the style and structure of the submitted text
• Originality signals: comparison of submitted text against online sources and, where your school enables it, a third-party originality/plagiarism-detection service

How this is used: these signals are combined into an advisoryindicator that may prompt a teacher to take a closer look. They are never a verdict, are not proof of misconduct, do not affect grades automatically, and never block a submission. A teacher reviews any indicator and exercises their own professional judgement, consistent with SCSA principles of assessment and the equivalent state and territory frameworks. Where originality checking against external services is enabled, some student work content may be transmitted to providers that process data outside Australia (see Sections 4.6 and 7); schools that require all processing to remain in Australia can leave these features disabled.

2.9 Learner Profile Data (where Personalisation is enabled and consented)

TeacherAI includes an optional Learner Profile feature that builds a private learning picture for each student to help personalise lessons, next-step recommendations, student reflection, teacher insight, and parent reporting. The feature is off by default. No Learner Profile data is captured unless the school or organisation has enabled the feature, the relevant class has enabled it, and the student or their guardian has given the required consent.

Where enabled and consented, Learner Profile data may include:

• Student-provided preferences: interests, learning preferences, survey answers, and voluntary confidence or reflection ratings
• Learning signals: lesson, quiz, practice, activity, and reflection patterns used to identify strengths, support needs, misconceptions, and helpful next steps
• Teacher-provided context: teacher notes or observations explicitly added to support learning
• Recommendation history: suggested next steps, whether a suggestion was shown, dismissed, pinned, or acted on

Learner Profile data is used for educational personalisation only. It is not used for advertising, student ranking, disciplinary decisions, automated grades, or marketing profiles.

2.10 Live Class Games (Arena) Data

When a teacher runs a Live Quiz or an Arena game (a live, multiplayer class game), we collect gameplay data needed to run the session in real time:

• In-game responses: answers to the curriculum questions that power each game, and whether they were correct
• Scores and rankings: points, streaks, placements, and leaderboard position within the session
• Gameplay events: transient game state such as player position, moves, and power-ups exchanged between participants during a live match
• Session metadata: game type, class and lesson context, participants, and timestamps

During a live session, a student's display name, avatar, and score are visible to their classmates and teacher in the same game, as is normal for a shared classroom activity. Real-time gameplay state is transient and is not retained after the session ends. Where a game's results are recorded against a lesson or assessment, the resulting scores are stored as ordinary progress data (see Sections 2.2 and 3). Arena games are not used for advertising or marketing profiles.

3. How We Use Your Information

We use collected information to:

• Provide and improve the TeacherAI educational platform
• Personalise learning experiences for students
• Track student progress and generate reports for teachers
• Process payments and manage subscriptions
• Send essential service communications (password resets, security alerts)
• Respond to support requests
• Comply with legal obligations
• Where Handwriting Mode is used: improve our on-device handwriting recognition model and AI coaching system using de-identified stroke data, so that all students benefit from more accurate recognition and more effective feedback over time (see Section 4.3)
• Where Learner Profile is enabled and consented: personalise learning support, recommend helpful next steps, assist student reflection, and help teachers and parents understand learning strengths, interests, and support needs

We do not use student data for marketing purposes. We do not serve advertisements to students or use their data to build marketing profiles.

4. AI and Machine Learning

TeacherAI can be run in two modes, controlled by school settings.

4.1 AI Disabled (LMS-only mode)

• Schools can disable student-facing AI features at organization and class level, including for all students in the school.
• When disabled, no student prompts or student responses are sent to AI providers from those disabled student AI features.
• In this mode, TeacherAI operates as a standard LMS (lesson delivery, assessment workflows, and progress tracking).

4.2 AI Enabled (where permitted by school policy)

• AI chat is only available within active lessons.
• AI chat is constrained to the current lesson topic, lesson content, and activity context.
• AI chat is designed to guide students toward understanding, rather than provide direct answer-only responses.
• Chat UI history is persisted locally in the browser for user experience.
• TeacherAI stores full AI chat transcripts server-side (both student messages and AI responses) for compliance, safety monitoring, and audit purposes, with a minimum retention period of 12 months. Message content is capped at 8,000 characters per message. A separate minimal topic summary is stored for rate limiting with 90-day automated cleanup. See Section 2.6 for full details.
• AI-assisted features may process lesson and assessment content to generate feedback.
• Processing is real-time and responses are not stored by AI providers for model training.
• Student personal information is not included in AI provider requests.
• Teachers can review and override AI-generated marks or feedback.
• Enterprise AI providers are used under data processing agreements.
• Practice Sets: When AI feedback is enabled, student responses to open-ended practice questions (short-answer, long-answer, coding exercises) may be sent to AI providers for feedback generation, error diagnosis, and learning support. Auto-grading of structured question types (multiple-choice, matching, fill-in-blank, ordering) is performed entirely within TeacherAI systems without external AI processing. Students may also request AI enhancements (alternative explanations, worked examples, visual diagrams) during practice sessions, which are processed via AI providers. All AI-generated practice feedback is stored within TeacherAI systems only.
• Whiteboard and Annotation: Teacher whiteboard drawings and annotations are broadcast to students in real time during live lessons and may be saved as snapshots for post-class review. Whiteboard data (strokes, snapshots, audio, video) is stored within TeacherAI systems in Australia. No whiteboard data is sent to AI providers.

AI-assisted marking is optional and assistive only. TeacherAI does not warrant that AI-assisted outputs are accurate, complete, or error-free. Schools and teachers must not rely on AI-assisted outputs as the sole basis for grading or reporting decisions.

Teachers and schools are responsible for final grading decisions and professional judgement, and should export/download and retain assessment records and submitted work (where available in the Service) in their own reporting systems for safekeeping and audit.

With the exception of handwriting stroke data described in Section 4.3 below, TeacherAI does not use student data to train AI models, and student personal information is not included in AI provider requests.

TeacherAI is an AI-capable platform; however, DOE implementations can be configured to operate in LMS-only mode. For DOE-domain organizations, student AI chat is configured as disabled by default at organization and class level controls. Teacher AI-assisted marking and assessment tools remain available unless the school elects to disable those features in line with local policy.

4.3 Handwriting Mode — Stroke Data and Model Improvement

When students use Handwriting Mode, their handwriting stroke data (pen coordinates, timing, and pressure) is stored as part of their activity completion record. This data serves two purposes:

• Primary purpose (service delivery): Stroke data is used immediately to calculate neatness scores, power the on-device handwriting recognition that transcribes student writing, and generate AI coaching nudges during the session.
• Secondary purpose (model improvement): De-identified stroke data may be used to improve our on-device handwriting recognition model (CRNN) and our AI coaching system, so that recognition accuracy and coaching quality improve for all students over time.

Before any stroke data is used for model improvement:

• Student identifiers (name, email, student ID) are separated from stroke vectors
• Data is aggregated and used only in bulk — individual student handwriting patterns are not singled out
• Canvas images (PNG snapshots) are not used for model training — only the raw stroke coordinate vectors
• Data used for training is handled internally by Sky Network Pty Ltd and is not shared with third-party AI providers for this purpose

Opt-out: Handwriting Mode is not enabled by default. Teachers and schools choose whether to assign activities that use the handwriting widget. If a school does not wish student stroke data to be used for model improvement, they may contact us at [email protected] to request that their students' stroke data be excluded from any training corpus. This does not affect delivery of the handwriting feature itself.

Retention: Stroke data is retained as part of the student's activity completion record, in line with the standard student data retention periods described in Section 9. Upon account deletion or a deletion request, stroke data is removed along with all other student records.

4.4 AI Processing Infrastructure

TeacherAI uses approved AI routing pathways and direct provider APIs to connect to AI models operated by external infrastructure providers. This may include OpenRouter, Anthropic, OpenAI, Google AI, Fireworks AI, Cloudflare Workers AI / AI Gateway, and Pollinations where enabled in product configuration. AI requests are configured to use zero data retention (ZDR) providers where available and supported by provider/account settings. Under this configuration:

• Under ZDR-supported configurations, prompt and response content is not stored by the AI routing provider or inference provider after processing
• Student responses submitted for AI analysis are not used to train or improve external AI models
• AI requests are transmitted solely to generate the requested output (e.g. feedback, marking, explanation) and are not retained after processing, except where minimal technical metadata may be recorded by providers for operational purposes such as billing, rate limiting, or system security

Where possible, TeacherAI:

• Removes or avoids sending personally identifiable information in AI requests
• Limits the information transmitted to only what is necessary to generate the requested response (e.g. student work content, task instructions, rubric criteria)
• Stores AI-generated results only within TeacherAI systems, not with third-party providers

TeacherAI may deploy self-hosted AI models for certain features in order to further minimise external data processing. Where self-hosted models are used, no student data leaves TeacherAI infrastructure.

4.5 Student Data Protection

TeacherAI is designed so that:

• Personally identifiable student information is not required to generate AI responses and is excluded from AI requests wherever possible
• AI prompts are limited to student work content, task context, and curriculum-related instructions
• AI requests use zero data retention infrastructure where available and configured — under those settings, providers do not store or learn from the content of requests
• TeacherAI does not permit third-party AI providers to use submitted student responses to train or improve their models
• Schools retain full control over whether AI features are enabled, and can operate TeacherAI as a standard LMS with all AI features disabled

4.6 Cross-Border Data Processing for AI

AI inference requests are processed by providers whose servers may be located outside Australia, primarily in the United States. This includes the AI routing platform and the language model providers used to generate feedback and explanations.

These cross-border transfers are necessary to provide AI-powered features and are disclosed under Australian Privacy Principle 8 (cross-border disclosure of personal information). To mitigate risk:

• AI requests are configured for zero data retention where available and supported by provider/account settings — under those settings, providers do not store prompt or response content after processing
• Personally identifiable student information (names, emails, student IDs, dates of birth) is not included in AI requests
• Only the minimum content necessary to generate the requested response is transmitted (e.g. student work content, rubric criteria, task instructions)
• Primary data storage (database, files, backups) remains in Australia (Sydney)

Separately, where a school enables originality checking (see Section 2.8), extracted phrases or passages of student work may be sent to web-search services or a third-party originality/plagiarism-detection provider, which may process this content outside Australia. This processing occurs only when the feature is enabled and is likewise disclosed under Australian Privacy Principle 8.

Schools that require all data processing to remain within Australia can disable AI features entirely, in which case TeacherAI operates as a standard LMS with no external AI processing.

4.7 Automated Decision-Making

TeacherAI uses automated processing — both AI models and rule-based logic — to make, or to substantially assist in making, some decisions about students and teachers. This section sets out the kinds of personal information used in that processing and the kinds of decisions made, as required by the automated decision-making transparency provisions of the Privacy and Other Legislation Amendment Act 2024.

Kinds of personal information used

• Work a student submits: typed answers, uploaded files, images of handwritten work and the text transcribed from them, and project and portfolio submissions
• Assessment records: marks, scores, percentages, attempt history, per-question responses, and time taken
• Enrolment information: year level, class membership, and school
• Learning activity signals: lesson and activity completion, practice results, and self-rated confidence
• Messages a student sends to the AI tutor or in-platform chat
• For teacher accounts: name, email address, school, registration details, and sign-in dates

Student names, email addresses and student identifiers are replaced with neutral tokens before any content is sent to an external AI model provider. Because a student may type their own name into free-text work or a chat message, we cannot guarantee a name never appears inside submitted content, but we do not send identity fields to a model provider ourselves.

Kinds of decisions made

• Marks for objective questions (multiple choice, true/false, matching, ordering) — scored automatically by comparing the response against the answer key.
• Marks and written feedback for short and extended written answers — produced by an AI model, then reviewed by a person before the result is published as a grade.
• Suggested grades and feedback on activities, projects and portfolios — produced by an AI model and hidden from the student until a teacher approves them.
• Academic integrity and originality indicators — advisory signals only. They never produce a grade, a penalty, or a blocked submission, and are never a determination of academic misconduct made by automated means. A teacher reviews every flag.
• Safety screening of AI tutor and chat messages — messages are assessed in real time and may be blocked or redacted immediately, and school staff (or, for home learners, a parent) notified.
• Learner Profile inferences — strengths, gaps, confidence and a suggested next activity, inferred from assessment and activity signals. Consent-gated, advisory, and never a determinant of grades. See Section 4.8.
• Teacher account inactivity — an automated schedule warns, then pauses, then retires an inactive teacher account, with advance notice by email at each stage. Signing in at any point cancels it. Retirement removes access and is reversible; permanent erasure is a separate step carried out by our staff. See Section 9.
• New-school registration screening — new-school registrations are automatically classified into a review queue. A person reviews the registration before the school is verified.

Human review of assessment results

Every assessment result is reviewed by a person before it is published as a grade. In a school class that reviewer is the teacher; in home learning it is the parent or guardian, who reviews and finalises the marked attempt. This is enforced in the product rather than left to practice: the review step cannot be switched off for an assessment, and an AI-generated mark or comment is a suggestion until a person accepts it. A teacher or guardian can change any mark, comment or flag before or after it is published.

No decision about a student's grades, enrolment, or discipline is made solely by automated means. Where an automated signal concerns a student's safety or wellbeing, it is escalated to a person rather than acted on as a decision about the student.

Formative quizzes and practice sets work differently: the student sees automated marks and feedback straight away so they can keep working. These are practice activities, not assessments. They do not produce a grade, and they do not feed reporting.

The one place an automated decision takes effect before a person is involved is safety screening: a message assessed as unsafe is blocked or redacted as it is sent, and school staff (or, for a home learner, a parent) are notified immediately afterwards.

If you want an automated mark, item of feedback, or flag reviewed, ask the classroom teacher, who can override it. Home learners, and anyone who would rather raise it with us directly, can contact [email protected].

4.8 Learner Profile Personalisation

The Learner Profile is a consent-gated personalisation layer. It helps TeacherAI adapt learning support to a student's interests, strengths, confidence, misconceptions, support needs, and what has helped them previously. It is designed to assist students, teachers, and parents with clearer learning insight; it does not make final decisions about grades, discipline, wellbeing, enrolment, or assessment outcomes.

• The feature is disabled by default at organisation and class level.
• Capture and profile-based recommendations fail closed unless the student or guardian consent requirement has been met.
• Teachers can use profile insights to adjust support and draft report language, but teachers remain responsible for reviewing and editing any report comment or recommendation.
• Students and guardians may request access, export, reset, deletion, or withdrawal of Learner Profile consent through the school or teacher.

5. Data Security

We implement industry-standard security measures to protect your information:

• Encryption in Transit: Data transmitted between your device and our servers is encrypted using HTTPS/TLS
• Encryption at Rest: Stored production data is encrypted at rest using industry-standard controls
• Access Controls: Strict role-based access controls limit who can access data
• Regular Audits: We conduct regular security assessments and updates
• Secure Authentication: Passwords are hashed using scrypt with random salt

6. Data Storage and Location

Your data is stored on secure servers located in Australia, specifically:

• Primary database: Sydney, Australia (DigitalOcean Sydney region)
• Backups: Australian data centres with geo-redundancy
• Media files: Cloudflare R2 object storage and content delivery

Primary platform data is stored in Australia. Some supporting providers, including AI, payment, email, application hosting, and content delivery providers, may process limited operational data in provider-managed infrastructure as described in this policy and on our subprocessors page.

7. Data Sharing and Disclosure

We may share your information with:

• Teachers: Student data is accessible to their assigned teachers
• Service Providers: Trusted third parties who help us operate the Service, including:
  • Stripe (payment processing)
  • Zoho ZeptoMail (transactional emails)
  • OpenRouter and configured AI model providers, including Anthropic, OpenAI, Google AI, Fireworks AI, Cloudflare Workers AI / AI Gateway, and Pollinations where enabled (AI processing)
  • Cloudflare R2 (file and media storage)
  • Web-search and originality/plagiarism-detection providers (only when your school enables originality checking — see Section 2.8)
• Legal Requirements: When required by law, court order, or government request

We do not sell, rent, or trade personal information to third parties for marketing purposes.

Current provider transparency details are available in our Subprocessors page. Schools may request a Data Processing Addendum (DPA) by contacting [email protected]. Compliance resources are also available at /compliance.

8. Data Breach Notification

In accordance with the Notifiable Data Breaches (NDB) scheme under Part IIIC of the Privacy Act 1988, we will:

• Notify affected users and schools as soon as practicable after becoming aware of an eligible data breach, and no later than 30 days after the breach is identified
• Provide details of the breach including the types of information involved, what happened, and recommended steps individuals should take
• Notify the Office of the Australian Information Commissioner (OAIC) where required
• Cooperate with affected schools so they can meet their own notification obligations to students, parents, and staff

If you suspect a data breach or security incident, please report it immediately to [email protected].

9. Data Retention and Export

Retention works differently for the two kinds of information we hold. Operational and activity data is deleted automatically on the fixed schedules set out below. Student learning records — submitted work, marks, grades, feedback and reports — belong to the school. Australian state and territory records schedules require schools to keep many of these for defined minimum periods, so the school, not TeacherAI, decides when they are destroyed. We do not delete a school's student records on our own initiative.

Deleted automatically

The following are deleted on a fixed schedule, without anyone needing to ask:

• AI Chat Transcripts: full conversation transcripts are retained for a minimum of 12 months to support child safety, school audit, and regulatory compliance obligations. After that period they are automatically deleted
• AI Chat Topic Summaries: brief topic labels used for rate limiting — 90 days
• AI Usage Logs: raw usage logs are retained for 30 days, then aggregated into daily summaries for cost management and billing. Aggregated summaries carry no message content and are retained with the account
• Voice and Video Recordings: student and teacher recordings — 12 months
• Whiteboard Snapshots and associated media: 6 months for active classes and 3 months for archived classes. Ephemeral stroke data from live sessions expires within 4 hours of the session ending
• Live Lesson Working Data: per-slide student responses — 30 days; end-of-lesson reports — 60 days
• Exam Question Responses: 90 days after completion
• Assessment Integrity Records: provenance data and related evidence are purged 90 days after the grade is finalised
• Points and Activity History: 90 days
• Parent–Teacher Messages: a whole thread is deleted 24 months after its most recent message
• Security and Audit Logs: 12 months
• Notifications: 30 days
• Sign-in codes and share links: removed within a day of expiry

Records we hold for the school

• Student Learning Records: submitted work, marks, grades, teacher and AI feedback, and reports are retained while the student's account is active, and are deleted on the school's instruction. We do not apply an automatic deletion window to them, because doing so could destroy records the school is legally required to keep
• Practice Set Data: student practice responses and mastery scores form part of the student's learning record and are treated the same way
• Learner Profile Data: retained while the student's account and class learning record are active. Withdrawing consent stops any further profile data being collected or used. Deleting or resetting an existing profile is arranged through the school or teacher, or by contacting us
• Billing Records: retained for 7 years, as required by Australian tax law

Accounts

• Active Accounts: data is retained while the account is active
• Inactive Teacher Accounts: we email you at around 2 months of inactivity, again when the account is paused for security at around 4 months, and finally a notice stating the exact date at least 30 days beforehand. At 2 years since your last sign-in the account is retired: access is removed and all sessions are ended. Signing in at any point before that cancels the process and resets the clock. Retirement is reversible — contact us and we can restore the account. Permanent erasure of a retired account is carried out as a separate step by our staff. Records your school is required to keep, such as student grades, survive erasure but are no longer linked to you

Data Export and Portability

Teachers can export their data and their students' data at any time using in-platform export tools where available. Exports include student records, assessment results, grades, and course content in standard formats (CSV, JSON). Teachers can delete their own account at any time, without contacting us, from Settings → Security → Delete Account — choose either deactivation (reversible) or permanent deletion. Teachers can also request immediate deletion of their data and their students' data by contacting [email protected]. Export and deletion requests are fulfilled within 30 days.

10. Your Rights

Under the Australian Privacy Principles, you have the right to:

• Access: Request a copy of the personal information we hold about you
• Correction: Request correction of inaccurate or incomplete information
• Deletion: Request deletion of your personal information (subject to legal retention requirements). Teachers can do this themselves from Settings → Security → Delete Account
• Opt out of marketing: Decline non-essential email (such as our "what's new" message to teachers who have been away) using the unsubscribe link in any of those emails. Essential account, security and data-retention notices are not marketing and continue to be sent
• Complaint: Lodge a complaint with us or the Office of the Australian Information Commissioner (OAIC)

11. Children's Privacy

TeacherAI is designed for use in educational settings with students of various ages. We take special care to protect children's privacy:

• Student accounts are created by teachers or with parental/guardian consent
• We collect only the minimum information necessary for educational purposes
• We do not display advertising to students
• We do not enable social features that could connect students with strangers
• Parents/guardians can request access to or deletion of their child's data

Parental Consent

Schools and teachers are responsible for:

• Obtaining informed parental or guardian consent before creating student accounts or entering student personal information into TeacherAI, in accordance with the Privacy Act 1988 and applicable state or territory education privacy frameworks
• Ensuring parents are informed about what data is collected, how it is used, and who can access it before student accounts are created
• Providing parents with the ability to withdraw consent and request deletion of their child's data through the school or teacher

Parents and guardians may contact their child's teacher or school directly to exercise rights relating to their child's data. We will cooperate fully with schools and teachers to fulfil these requests.

Children's Online Privacy Code

We are monitoring the development of the OAIC Children's Online Privacy Code, which is expected to be registered by December 2026. TeacherAI will update its practices to comply with the Code's requirements when it takes effect. As an educational platform used by students, we are committed to meeting the highest standards for children's privacy.

Child Safe Standards

TeacherAI is designed to support schools in meeting their obligations under the National Principles for Child Safe Organisations and applicable state and territory Child Safe Standards. The platform incorporates safeguards including:

• Age-appropriate AI interactions constrained to educational content
• Content filtering to prevent harmful or inappropriate material
• Teacher oversight of all AI-generated content and student interactions
• School-level controls to disable AI features in accordance with local policy
• No advertising, social features, or connections to external users

12. Cookies and Tracking

We use cookies and similar technologies to:

• Keep you signed in to your account
• Remember your preferences (like dark mode)
• Understand how the Service is used (analytics)

We do not use cookies for advertising or cross-site tracking. You can control cookies through your browser settings.

13. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of significant changes by email or through a notice on our website. The "Last updated" date at the top indicates when this policy was last revised.

14. Contact Us

If you have questions about this Privacy Policy, wish to exercise your privacy rights, or want to make a complaint, please contact us:

You may also contact the Office of the Australian Information Commissioner (OAIC) if you have concerns about how we handle your personal information: