Policies and school information
Development prototype - draft policy pack. Use fictional details. These documents explain the present demo and technical pilot, and what still needs school/provider approval before real pupil use. They are not a claim of legal compliance.
Updated 13 November 2026. Read the short explanation for children and families, or choose a topic below.
For children and families
My School Day helps you see your lessons, choose a reward and tell an adult how you feel or what you need. Ask a trusted adult to help you read a screen or explain a change.
Your information belongs to you. You can ask what is written about you, say if something is wrong and ask who can see it. An adult should explain the answer in a way you understand. Do not share your school code or someone else's photo. If something worries you, tell a trusted adult.
Use pretend names and sample photos in this prototype. A parent code is linked to one child; the school must check who the parent or carer is before giving access. A code is not permission to view other children's records.
Privacy notice
The demo feedback form collects adult reviewers’ role, ratings and comments about the website. School, name and reply email are optional. Feedback is stored in this site’s database and is visible only to the authorised Bright Futures owner, who can use it to improve the demo and reply if contact details were supplied. Do not include pupil information. Owner-record backups can include these submissions.
Two separate areas: the public visual demo stores sample records in the browser. The signed-in school accounts area at School accounts stores its records in the database attached to this site. Demo records are not automatically copied into school accounts or another device. Both areas are for fictional records while the pilot is under review.
Information entered can include a child's name, year, class, sex selection, photo, school passport, timetable, assigned staff, interventions, targets and responses, feelings, achievements, parent details, access codes and messages. Staff records can contain a name, job, photo and assignments. School accounts also receive the sign-in account identifier, email and display name and can record access requests, school contacts, support requests, review decisions and activity history.
The intended purposes are organising the school day, providing individual support, communicating with families and administering access. Staff and families supply information; children create check-ins, choices and lesson ticks. Only enter information needed for those purposes. Do not enter real health, safeguarding or pupil records during this prototype stage.
The service provider's legal identity, contact address, school responsibilities, processing grounds, service-provider register and retention schedule are not yet finalised. This draft does not replace the completed privacy notice needed for real pupil use.
Lawful basis and sensitive information
Before real records are entered, the school and provider must record who decides the purposes and means of processing. Their actual activities determine whether each is a controller, joint controller or processor; the label in a contract alone does not decide this.
Record an appropriate Article 6 lawful basis for each purpose. Information revealing a disability, diagnosis or health need may also require an Article 9 special-category condition and relevant UK safeguards, including an appropriate policy document where required. Do not treat a registration tick, a parent code or use of the site as blanket consent.
Where consent is the chosen basis, explain the genuine choice, record it and provide a way to withdraw it. A school must assess its own grounds rather than assuming that every use relies on consent. Review the Children's code where applicable to the provider's activities and carry out a data protection impact assessment where processing is likely to be high risk.
Your rights, corrections and complaints
Children have data protection rights. Depending on the purpose and legal grounds, these may include access, correction, deletion, restriction, objection and portability. Where processing relies on consent, it can be withdrawn. Rights and any limits should be explained clearly; deletion is not automatic where records must lawfully be kept.
Ask the school data protection contact about a real school record. The school should check identity and authority proportionately, consider the child's own rights and understanding, protect other people's information, record the request and respond within the applicable statutory time limit. A parent's access to the portal does not automatically entitle them to every confidential record.
For non-urgent prototype questions, use the enquiry form in School accounts. Do not include real pupil information. Raise a privacy concern with the responsible organisation, and you can also complain to the Information Commissioner's Office (ICO). The provider's published privacy contact is still to be completed.
Cookies and browser storage
Staff registration in the browser demo saves a name, year group, school email and a one-way fingerprint of the permanent demo access code in browser storage. The readable code is shown once on registration and is not emailed. Personal email providers are blocked, but a permitted email domain does not verify school employment or ownership of that address. These demo codes do not grant access to the separate verified school-account area.
The visual demo uses local storage with names beginning bright-futures- for sample profiles, codes, timetables, interventions, photos, staff assignments, messages, targets, feelings, achievements, certificates, completed lessons, game progress and acknowledged alerts. These records generally remain until replaced or removed, or until this site's data is cleared in the browser. Some in-memory choices and demonstration registration requests reset when the page reloads.
Browser storage is specific to the browser profile and website origin. People sharing that browser may be able to view saved demo records. Private browsing, device settings or storage limits can prevent saving. Clearing browser storage does not erase school-account database records, printouts or downloaded copies.
Hosting and sign-in services may use additional storage or cookies. Their names, providers, purposes and lifetimes still need a browser and hosting audit. Before adding optional technologies, document whether consent or a current statutory exception applies and provide any required controls. This draft is not a completed cookie audit.
Terms of use and school licensing
Bright Futures is a development prototype for exploring school-day support with fictional information. Demo sign-in screens do not create verified staff or parent accounts. Features, sample content and availability may change. Keep access details private and use the site respectfully.
A live school licence needs a separately agreed contract covering the legal parties, authorised users and school, fees, taxes, renewal, cancellation, support, availability, suspension, responsibilities, data return or deletion, liability and applicable law. No price, service guarantee or school contract is created by this draft page.
Upload only content the school is authorised to use. School and family records are not transferred into the provider's ownership merely by being entered. Any permission needed to host that content, ownership of the software and logo, and permitted copying of teaching materials must be addressed in the final agreement. Do not claim another person's work as your own.
Acceptable use
Use the portal for agreed school-day activities and routine communication. Do not impersonate another user, guess or share access codes, access another child's information, bully anyone, upload harmful files or use messages for advertising. Use only approved sample images in the demo.
Adults should use school-approved devices and accounts, check the selected child before saving or printing, and sign out of school accounts on shared devices. Demo records can remain in a shared browser after leaving a portal. Report accidental access to the school administrator rather than copying the information.
Staff should explain features in an accessible way and respect the child's choices and communication preferences. A feeling, target response or reward choice is a starting point for support, not a diagnosis or a complete assessment of the child.
Safeguarding and alerts
I Need is not an emergency service. In the visual demo, a request flashes on the child's own screen and records elapsed time until an adult acknowledges it with the demonstration teacher code. It does not send a live alert to a teacher's separate device. A completed timer does not establish that the child's need was resolved.
For immediate help, tell a nearby trusted adult and use the school's established emergency and safeguarding arrangements. Do not place urgent concerns in Message Home, a support form or a change notice and assume someone is monitoring it.
Before school use, name the designated safeguarding lead and deputies, agree who monitors each feature, response and escalation arrangements, what to do if a request is missed and what happens during absence or service failure. Follow the school's safeguarding policy and the child's agreed support plan. The school's own safeguarding policy remains authoritative.
Messages, feelings and support requests
Message Home is for routine updates about the linked child. In the visual demo, messages are saved in that browser; in school accounts, messages are held in the site's shared database. The current message and support forms do not send email, text messages or emergency notifications. Parent access codes are generated on registration but are not emailed automatically.
Keep messages relevant, factual and respectful. Schools should define who reads them, their normal monitoring hours, how replies are covered during staff absence and what should be raised through another channel. Do not promise a response time until the school has agreed and published it.
Feelings and zone suggestions support a conversation. Ask the child what helps and follow their individual plan. Do not use automated zone labels, game levels or a single target response on their own to make significant decisions about a child.
Photos, school passports and printouts
Use photographs only for an agreed purpose and with an appropriate lawful basis and any school permissions required. Explain who will see them. For this prototype, use sample photos that you are authorised to use, without other children's details or identifying information in the background.
Check the selected child or staff member before uploading, replacing or printing. A school passport should describe relevant strengths, communication preferences and support needs; avoid unnecessary private family information. Confirm accuracy with the child and relevant adults.
Printed passports, exported PDFs, screenshots, certificates and backups are separate copies. Collect printouts promptly, use approved storage and sharing methods and dispose of them under the school's arrangements. Removing a photo or clearing the browser does not remove copies already downloaded or printed. The school should record who handles correction and removal requests.
Accounts, parent codes and permissions
The visual demo's portals and example codes are demonstrations, not verified identity or production access controls. Do not enter real passwords or pupil records. A child's initials and three numbers and the two-digit teacher acknowledgement code must not be presented as secure authentication for a live school service.
In school accounts, users sign in and the school administrator approves roles and links to pupils. Staff can be restricted to selected children; parents and pupil displays should only be linked to the intended child. The current school-account design serves one school per site. Separate schools need separate sites or a separately tested isolation design.
Verify a parent's identity and relationship before issuing an access code. Codes remain valid until replaced; a code is not proof of parental responsibility. Agree replacement, access removal, leaver checks and account recovery. Restrict access promptly when someone leaves or a code may be exposed, and review assignments regularly.
Accessibility statement
Bright Futures uses text labels alongside visual cues, plain language and a reduced-motion option for the on-screen request. A full independent accessibility audit has not been completed. Compliance with WCAG 2.2 AA has not been established.
Testing still needs to cover keyboard navigation and focus, screen readers and form labels, zoom and reflow, contrast, touch targets, error messages, photographs and alternatives, timing, flashing requests and all portal flows. Website walkthrough videos and downloaded documents also need accessible alternatives.
If a feature is difficult to use, ask an adult for help or an alternative way to communicate. Send a non-urgent accessibility request through School accounts, describing the page and the format or adjustment needed without disclosing real pupil details. The final statement needs named contact details, test findings, known barriers, a remediation plan and the applicable complaint or enforcement route.
Retention, archiving and deletion
Demo profiles, photos and records remain in this browser until removed or site data is cleared. Archiving hides a pupil from active selection and blocks their demo code, but keeps associated records. Some session-only information resets on reload. Deleting browser data does not delete school-account database records or separate copies.
School accounts provide administrator tools to archive and restore profiles, export records and permanently delete an archived pupil's records following confirmation. These tools do not decide how long a school must keep information. Automatic retention-based deletion is not configured by the policy page.
The school and provider must approve a schedule for each record category, including messages, photos, learning and support records, access requests, codes, audit logs and backups. Record the reason, retention trigger, period, responsible person, exceptions such as a lawful hold and the secure deletion or return process. No universal retention period is claimed here. Include printed and exported copies and explain backup expiry.
Security and personal data incidents
Report a suspected disclosure, lost device, wrong-child access, exposed code or unauthorised change promptly to the school administrator and agreed provider contact. For a non-urgent prototype report, use School accounts without including real pupil data or secrets. Named incident contacts and out-of-hours arrangements remain to be published.
The responsible team should contain the incident, protect evidence, restrict affected access, assess the information and people involved, record decisions, coordinate recovery and review what needs changing. Keep a record even when regulator notification is not required. A processor must inform the controller without undue delay after becoming aware of a personal data breach.
The controller must assess whether notification is required. A notifiable breach must be reported to the ICO without undue delay and within 72 hours of awareness where feasible; high-risk effects on people can also require informing them without undue delay. This process must be agreed in the school/provider contract. This draft does not claim security certification or independent penetration testing.
Backups, outages and school-day continuity
The school accounts area offers administrator-controlled manual backup downloads and a restore of missing records to the same school site. This does not configure automated off-site backups. Restores keep existing records and do not restore account approvals or audit history; encrypted parent codes depend on the site's existing encryption key.
Assign a backup owner, approved encrypted storage, a backup schedule, access limits, retention and a tested recovery process. Confirm recovery expectations in the school agreement rather than promising an untested recovery time.
During an outage, use the school's agreed alternative timetable and communication arrangements. Keep a suitable accessible fallback available. The app is not guaranteed to work offline and should not be the only way a child can request support.
School agreement and DPIA review
Before real pupil use, the school and provider must agree their roles, authorised purposes, necessary records, access arrangements, support and safeguarding responsibilities. Assess the need for a data protection impact assessment, particularly because children and potentially sensitive support information are involved. Record and address identified risks before a pilot.
Where the provider is a processor, the written data processing agreement should cover instructions, confidentiality, security, subprocessors, transfers, assistance with rights and incidents, return or deletion of data and audit arrangements. A licence and a data processing agreement serve different purposes; both may be needed.
The editable documents in School Back Office are draft prompts. A saved school approval records a decision; it is not an independent compliance check and does not automatically publish the approved wording to this public page.
Contacts and information still required
Still required before real pupil use: the provider's legal business name, postal address and published privacy/support email; the responsible school's details and data protection contact; safeguarding and incident contacts; the approved retention schedule; contractual service providers and processing locations; accessibility findings; and the agreed school licence and data processing documents.
Administrators can enter school contacts in School Back Office - School details and maintain review documents in Policies and review. Signing in and appropriate permissions are required. School settings do not automatically fill this public page.
For routine prototype questions, open School accounts and use the enquiry facility. It is not an urgent contact service and does not send email automatically. For urgent concerns, contact the school through its established arrangements.
Policy ownership and review
This policy pack is a draft updated on . No completed school or legal approval is asserted. The provider and school must name the owner and reviewer of each document, record the approved version and next review date, and make final information accessible to children and families.
Review policies when purposes, features, access, providers or legal requirements change, and after an incident or audit. Keep public notices and school documents consistent and explain material changes before new uses begin. A new feature does not itself authorise collecting more information.