Student sign in

Privacy policy

Recess Pty Ltd (ABN 46 674 209 100, ACN 674 209 100) operates Recess and is responsible for the personal information described in this policy.

Updated 2 November 2026

Who this policy covers

This policy explains how we handle information about school staff, experts and students who use Recess classroom units and sessions, including pilot participation and separately arranged live delivery. The public short-course library and existing family accounts have their own notices in the library; their account and device work remain separate from school classroom records.

Adult accounts and communications

Adult records may include a name, email address, school or professional affiliation, role, location, verification status, invitations, bookings and communications. We receive this information from the adult, their school and authorised staff completing checks. School staff have individual accounts. For classroom units, Recess records the school-role review, work email, approving staff member and invitation acceptance or revocation; class co-teacher assignments are recorded separately. Presenters use invitation-based access. Experts can arrange their contributions with us by email without a school account.

Sign-in uses a short-lived, single-use email code and a secure browser cookie. Presenter records may also include identity checks, training, rehearsal and child-safety clearance information. Browser preferences can remember choices such as whether the presenter tutorial has been completed.

Website enquiries and activity

Teachers, parents and learning-group organisers can send an enquiry without an account. We store the adult's name, email, optional school or group and year levels, message, and limited referral information, such as whether they arrived through a newsletter or course completion link. Authorised Recess staff can record the conversation stage, notes and a follow-up date to respond and organise a possible unit or pilot. Please do not include students' names, contact details or sensitive information. Sending an enquiry does not subscribe anyone to marketing emails.

The public short-course library records limited activity counts, such as visits, course starts, lesson and course completions, completion-card downloads and sharing actions. These use a short-lived browser-tab identifier, course and lesson identifiers, a time and a recognised referral category. They do not include names, email addresses, answers, projects or completion-card text, and are not linked to family accounts or school learner records. These counts describe recorded browser activity, not verified individual learners or assessed learning. The library privacy notice explains browser choices and retention.

Enquiries and follow-up notes are kept while needed to handle the request and any resulting relationship, or to meet operational and legal requirements. Email hello@recess.education to request access, correction or deletion. A short-lived hashed technical identifier is used to limit repeated submissions and activity requests.

Saved classroom units

Recess can prepare a school class and record its assigned teacher contact before the teacher accepts an invitation. Recording a contact does not create a signed-in teacher or activate their access. Recess administrators can use the student lesson interface through their own adult account. Their responses are saved separately from learner records and are excluded from student progress and submissions.

For a classroom unit, the teacher creates a class and issues each learner a nickname and a private learning code. A learner enters the shared class code and their own private code; no student email address or independent adult account is required. Teachers should use short nicknames rather than full names, keep any roster linking nicknames to students within the school, and distribute private codes individually. A nickname and its work can still relate to an identifiable student and are not treated as anonymous.

A learner has a school profile with a nickname and private code, and a separate membership for each assigned class. An authorised teacher can reuse that profile from a class they already have access to in the same school. Recess does not merge learners based on matching nicknames. Recess stores the school and responsible teacher, class settings and access expiry, learner nickname, lesson progress, activity answers, code notes supplied in Recess, written evidence, reflections, submission times and teacher feedback. The assigned teachers and authorised Recess administrators can review records for that class. School approval alone does not give a teacher access to every class. Learners can access their own saved work and feedback, not another learner's work. These records support teaching and progress across the unit; they are not a student messaging channel or a feed to an external presenter.

We store hashes of private learning codes and browser session tokens rather than their readable values. The shared class code is retained so the teacher can display it. A learner browser session uses an HttpOnly cookie. Shared-device access is the default: it uses a non-persistent browser cookie and expires on the server after eight hours. A learner may choose to remember access on a personal device for up to 30 days. Browser restoration may retain a session cookie, so learners must sign out on shared devices. Both modes end earlier if class access expires or credentials are revoked. Resetting a private learning code ends access through the previous code and sessions without deleting the learner's saved work. Students should sign out on shared devices.

While a learner edits, this browser tab can hold an unsaved recovery draft in session storage. It is removed after a successful save or when the learner completes sign-out for that class; closing the tab normally ends this tab storage, although browser session restoration can restore a tab. This recovery copy is separate from work saved to Recess, is not a backup across devices, and can be unavailable when browser storage is blocked. Save or download unsaved work before leaving a shared device.

Games Design & Coding uses Microsoft MakeCode Arcade as an external editor, which can open alongside the lesson in the Recess browser. Recess does not automatically send lesson responses to MakeCode or back up an Arcade project. Opening the editor connects to Microsoft's service under its own terms and privacy practices. Students should export editable game projects to the school-approved location and verify that they reopen; an optional code note saved in Recess does not replace that project file.

Optional school browser assistants

Schools can choose whether to permit the teacher and student assistants. Both school permissions default to off, and each class's student assistant also defaults to off. Additional service, privacy and safety approvals are required before a permission becomes available. Student assistance is limited to school-confirmed users aged 13 and over, is unavailable during independent work or a paused or locked session, and selects from reviewed learning-support cards. The staff assistant can generate lesson explanations, planning suggestions and activities for a teacher to review. These features do not grade students, submit work, operate other tools or make changes to school records.

When an enabled assistant is used, the question, any attempt deliberately entered into that assistant, recent conversation history, requested type of help and reviewed lesson context are sent through Recess to OpenAI for processing and safety checks. Recess does not automatically attach learner records, saved lesson responses, grades, browsing history, page contents or opened files. Do not enter student names, contact details, assessment records or other sensitive information. Automated checks can reject some inappropriate or identifying input, but cannot identify every instance.

Teachers can save a class-specific lesson plan with teaching time, assistance mode and staff notes. Learners cannot read those staff notes. In Review mode, a learner deliberately saves an initial attempt and explanation of their reasoning as classroom work. That version is kept unchanged, linked to the lesson and its settings, and can be reviewed by the assigned teachers. It is sent to OpenAI only if the learner subsequently chooses Request feedback on saved attempt and the school's AI permissions and service approvals allow it. Later ordinary lesson responses remain separately editable. An administrator using Student view records their own attempt separately from pupil records.

Conversation text is held in memory in the native browser or current web lesson view and cleared when that view or session ends. The native browser also clears it when the user, class or lesson scope changes. Recess processes requests on its server but does not save assistant questions or replies in its database. Deliberately saved initial attempts are classroom records, rather than conversation history. We retain request identifiers, school and class identifiers, the requesting account or learner identifier, type of assistance, times and completion outcome to enforce limits and investigate faults. Bounded routine cleanup removes request metadata older than 30 days; removal can take longer while a backlog is processed or the routine is not running. Saved classroom responses remain subject to the separate retention arrangements above.

OpenAI states that API data is not used to train its models by default. Recess requests responses with storage disabled; this does not mean zero data retention. OpenAI may retain abuse-monitoring logs, which can include request content, for up to 30 days by default, with exceptions such as longer retention required by law. Its API data controls describe processing and retention. The school must consider these provider arrangements before enabling assistance.

The assistant is not a messaging channel to a teacher, presenter or Recess staff member. Conversations are not monitored live by a person and are not an emergency-reporting service. Students should speak directly to their teacher or another trusted adult if they need help or want to report a concern.

Files opened in the Recess browser

A file deliberately opened from the device, or downloaded into the browser's document workspace, is held in memory for viewing. The browser does not automatically upload that file to Recess storage or an AI provider. Selecting Save a copy writes a file to the location the user chooses. Closing the document or ending the browser session clears its in-memory copy; the original file and any saved copies remain on the device or school storage until removed there. The school remains responsible for shared-device use, approved storage and access to those files.

One-off session participation

In one-off expert sessions, students join with a classroom code, without creating an account or entering a name. Recess assigns a participant label that does not use their name. We process the classroom connection, admission and participation events, fixed-choice reactions, structured poll and activity answers, and safety or security signals. Join security uses a short-lived cookie and a hashed technical identifier to limit misuse. Labels and technical records are not treated as anonymous simply because a student has not entered a name.

Student participation does not include chat, questions or messages to the presenter, cameras or microphones. Learning activities use prepared choices and structured responses. Where a reflection includes optional written feedback or a suggested future topic, students are asked not to include names or personal details.

Live reactions are quick signals, such as applause or interest. Recent reaction totals are visible to everyone in the session, without student names or classroom identifiers, and are not treated as evidence of learning. Contributors do not receive student-level reaction data. “I'm confused” is a fixed reaction, not a written question or a private support channel.

Restricted records from earlier session formats may contain a first name, classroom alias, message or written reflection. These remain subject to the access and retention controls below; they are not republished as part of the current student experience. Adults should include only necessary student information when reporting a safety concern.

Expert videos and live delivery

The on-demand format uses prerecorded expert content. Recording an expert's approved presentation is separate from recording a classroom: student cameras and microphones remain unavailable, and student participation is not recorded as video or audio. The content and access available during the pilot are confirmed with each school.

For separately arranged live sessions, the presenter's audio and video are delivered through our live-video provider. Schools choose whether students watch on a classroom screen or individual screens. Recess does not record live sessions by default.

Private rehearsal rooms are available only to authorised adults. We store the room owner, prepared materials, access and control records, and technical connection identifiers. Practice activity answers stay on the test screen and do not enter student or contributor learning reports. Connecting rehearsal audio or video uses the same video provider as a live event.

Why we use it

  • to authenticate adults, manage school teams and confirm access or bookings;
  • to provide session access, connect students and operate learning activities;
  • to manage participation, respond to safety concerns and maintain an accountable audit trail;
  • to send service emails and produce privacy-protected class and programme outcomes; and
  • to secure, troubleshoot and improve the service.

Safety and human review

Authorised teachers open or pause their own classroom and supervise participation. Students with a valid code enter an open classroom without individual admission. Students should tell their supervising adult if they need help or want to raise a concern. Recess restricts safety reports and historical disclosures to staff with the appropriate safeguarding role.

Restricted review tools may use automated rules and an AI moderation service to assist authorised staff with existing written records. They do not create a student messaging channel. Adults can request review of a safety decision through Help and complaints.

Who receives information

Authorised school staff can access information needed to manage their school and assigned classrooms. In one-off expert sessions, teachers receive class summaries covering their own class's participation and activity results, without student names. Schools may share these summaries with families; they do not receive another school's class-level results. In saved classroom units, the responsible teacher instead reviews individual work and feedback under the teacher-issued nickname, as described above.

Presenters see the session material and combined activity results needed to deliver the learning, not a student conversation feed. Reports shared with experts describe overall participation and learning feedback without student-level records, contact details or private safety information. These protections also apply to reports shared under existing delivery agreements. We limit or omit results from small groups where reporting could identify a student. We do not sell personal information or use student contributions for advertising profiles, sales leads or unrelated customer research.

Service providers and security

Cloudflare supports hosting, storage and security; Agora delivers live audio and video; Resend sends service emails; and OpenAI services support the optional school assistants and restricted review of historical written records. Providers may process technical connection information needed to deliver and protect these services. Microsoft operates MakeCode Arcade, whose privacy statement applies when its editor is used. Earlier service records may also remain in restricted OpenAI Sites storage while they are retained or removed under this policy.

These providers operate internationally, so information may be processed outside Australia. Contact us for the provider and processing-location details relevant to your school's proposed delivery. Location-specific requirements are checked before a school participates.

We use role-based access, time-limited credentials and audit records to restrict access. Presenters and teachers cannot use a classroom code to access another school's dashboard or reports. No online service is completely risk-free; tell us promptly if you suspect unauthorised access.

How long we keep it

  • Sign-in and access. Adult email sign-in remains separate from learner codes: adult codes expire after about 15 minutes and adult browser sessions after about seven days. For scheduled live events, student event access ends 30 minutes after the scheduled finish; other one-off session cookies expire within about six hours. Saved classroom unit access defaults to a shared-device session of up to eight hours; choosing to remember a personal device extends access to up to 30 days. Class access expires one year after creation, unless it ends earlier. Expiry ends access and does not, by itself, delete stored records.
  • Saved classroom work. The one-year class access period is not an automatic deletion schedule. Saved unit responses, code notes, reflections and teacher feedback remain stored after access expires unless separately removed. We retain these records for agreed teaching, recovery, support or required recordkeeping needs; contact us to arrange access, correction or deletion and explain your school's retention requirements. They are not included in the one-off participation cleanup below.
  • One-off student participation. Routine cleanup removes one-off participation records and activity answers after about 30 days. The same routine period applies to names, aliases, messages and reflections from earlier formats, except where needed for an unresolved safety case.
  • Technical records. Anti-abuse join checks are normally removed within 24 hours and room audit events after about 90 days. Live event reactions disappear from the view after seconds and are removed during cleanup after the event ends or within about one day. Reactions do not form part of contributor learning reports.
  • Rehearsals. A private practice room closes after two hours or when ended earlier. Its adult preparation and technical records may remain after it closes, for operational and security needs. These records are separate from student participation and learning reports.

Cleanup runs periodically, so deletion may follow the relevant expiry time. Privacy-protected aggregate outcomes and learning guides can remain available after the underlying student-level records are removed.

Safeguarding case metadata may be retained longer where it is needed to protect a child, investigate a concern or meet legal obligations. An unresolved case is excluded from routine deletion so authorised safeguarding staff can complete the review. Once resolved, its source disclosure and student reference return to the routine deletion schedule. Private disclosures are never copied into learning or contributor reports. Adult account, contract, booking and compliance records are retained only for operational, legal and security needs.

Your choices and contact

Adults may ask to access or correct their personal information, close an account, or make a privacy complaint. Students and families may contact us directly or ask their school to help. Include the school, session and date where possible; do not send sensitive student information unless we ask for it through an appropriate process. Some records may need to be retained for safety or legal reasons.

Email hello@recess.education and address the request to the Privacy Contact at Recess Pty Ltd (ABN 46 674 209 100, ACN 674 209 100). We will verify the request, investigate the concern and explain the outcome and any next steps. If a privacy complaint is not resolved, you may review the Office of the Australian Information Commissioner complaint process.