nAble Academy · Legal information
Privacy Policy
This draft describes the personal information the nAble Academy platform is designed to handle and the integrations visible in the application source. It must be completed by the service operator before publication.
Draft prepared 12 November 2026 · Requires operator/legal review
1. Who operates nAble Academy
nAble Academy is the name of an education and school-management platform. The legal organisation responsible for this website and service must be identified before this policy is published:
- Full registered legal name: [INSERT VERIFIED LEGAL ENTITY]
- Registered / principal address: [INSERT VERIFIED ADDRESS]
- Privacy contact: [INSERT MONITORED PRIVACY EMAIL]
- Data protection officer / representative: [INSERT IF APPLICABLE, OR CONFIRM NOT REQUIRED]
Do not replace these fields with a brand or assumed company name. Identify the entity that actually operates the service and determines the relevant processing purposes.
2. Scope and roles
This policy is intended to cover the public website and the nAble Academy school platform, including accounts for platform administrators, school administrators, teachers, students and parents. Some functions are enabled only for particular schools or roles.
A school may decide which educational information is entered, who receives accounts and which staff, students or parents can see a record. Depending on the service agreement and applicable law, the school may act as controller for some school records and the Operator may act as its processor; the Operator may have separate responsibilities for its own account, security and service operations. The actual allocation must be confirmed in the school agreement and any data processing agreement. This draft does not decide those roles.
3. Information the platform may handle
The reviewed application source contains features and data structures that may handle:
- Account information: names, email addresses, account identifiers, role, account status, school association and parent/student links used for account access and role-based experiences.
- School and academic information: school, class and section records, timetables, attendance, curriculum and syllabus details, learning materials, assignments, exams, submitted answers, grading, results, question-bank content, announcements and notifications.
- User-generated content and files: information entered, created or uploaded by a school or an authorised user through enabled features, including school branding assets and educational materials.
- Live-class information: class/session identifiers and participant information; real-time audio, video, chat or screen-sharing streams when a LiveKit-powered live class is used. This draft does not state that live classes are recorded.
- AI feature inputs and outputs: prompts, selected school resources, question content and generated text when an authorised user uses an AI-assisted feature. Production AI provider names and their processing terms must be verified and listed before publication.
- Technical and security information: session and browser state, diagnostic or security logs, and signals processed by tools such as Cloudflare Turnstile during authentication-related verification.
- Browser storage: authentication/session values, consent choices, optional appearance preferences and feature-specific local data may be stored in local storage or session storage. The source includes a user-scoped Question Bank cache and pending sync queue, notification read markers, offline-runner state and interactive-diagram state. A legacy/mock-data storage path is also present in source and must be checked for production reachability. These technologies are not all cookies.
The exact fields and purposes depend on the production configuration and features enabled by the relevant school. The Operator must validate this list against deployed systems before publication.
4. How information is obtained
Information may be entered by a user, supplied by a school or its authorised staff, generated by use of platform features, or received from service providers supporting authentication, security verification, hosting, live classes and other enabled functions. Add any additional production sources here after verification.
5. Purposes of use
Based on the current feature set, information may be used to:
- create accounts, verify sign-in and maintain authorised sessions;
- provide school, classroom, curriculum, attendance, assignment and examination workflows;
- show records to the appropriate users according to role, school and configured permissions;
- support notifications, live classes and authorised AI-assisted features;
- protect the service and authentication endpoints from automated or abusive activity;
- remember optional appearance and on-screen guide preferences when the user permits it; and
- meet applicable legal, security and service-management obligations.
Analytics tracking was not found in the application source reviewed for this draft. If analytics is introduced, the Operator must update the privacy and cookie disclosures, define its purpose and legal basis, and obtain any consent required before optional analytics technology is loaded.
6. Legal grounds and notices
Completion required: the Operator must map each purpose and data category to its actual legal ground in each relevant jurisdiction and relationship. Depending on the circumstances, grounds may include performance of a contract, legal obligation, legitimate interests, consent or processing on a school's documented instructions. This draft does not select a legal ground on the Operator's behalf.
The final notice must explain the legal ground for account administration, school records, security, live classes, AI features, optional preferences and any future analytics, together with the consequences where information is not provided.
7. Service providers and recipients
The source identifies integrations with the following providers; their involvement depends on the feature used and production configuration:
- Supabase: used for application authentication and backend data services.
- Cloudflare Turnstile: its browser script is loaded on authentication-related screens for security verification. See Cloudflare Turnstile documentation.
- LiveKit: used by the LiveKit live-class implementation for real-time communications when that provider is selected.
- AI provider(s): the AI gateway supports configurable provider protocols. The actual enabled vendor names, data submitted, retention terms and processing locations must be verified from production configuration and listed here.
- Schools and authorised users: school and learning information is made available within the school workspace according to the user's role, school association and permissions.
Before publication, add the complete current subprocessor list, each provider's role, the relevant contract and the categories of data each provider receives. Information may also be disclosed when required by law or a valid legal request.
8. International processing
[VERIFY THE PRODUCTION REGIONS FOR SUPABASE, CLOUDFLARE, LIVEKIT AND EVERY ENABLED AI PROVIDER. IDENTIFY ANY INTERNATIONAL TRANSFERS AND THE ACTUAL LEGAL SAFEGUARDS USED. DO NOT PUBLISH A COUNTRY OR TRANSFER MECHANISM UNTIL VERIFIED.]
9. Retention and deletion
[INSERT THE APPROVED RETENTION SCHEDULE OR OBJECTIVE RETENTION CRITERIA FOR ACCOUNT INFORMATION, SCHOOL/LEARNING RECORDS, UPLOADS, LIVE-CLASS METADATA, AI REQUESTS AND LOGS, SECURITY LOGS, BACKUPS AND CLOSED ACCOUNTS.]
Browser storage remains on a device until the relevant value is removed, the browser data is cleared, or the application replaces it. This is separate from retention of records in hosted systems and does not replace a server-side retention schedule.
10. Children and student information
Student accounts may relate to children. Before launch, the Operator and each school must confirm the lawful basis, school/parent/guardian authorisations, age-related requirements and process for handling requests about student information in each jurisdiction where the platform is offered. Behavioural analytics and targeted advertising should not be introduced for student accounts without a separate documented legal and safeguarding review.
11. Security
The platform uses authentication, role-aware access and service-level security controls. No system can be described as completely secure. The Operator should maintain an accurate record of its technical and organisational measures and its incident response process. Report a security or privacy concern to [INSERT VERIFIED CONTACT].
12. Your rights and requests
Depending on the law that applies and the Operator's role for the relevant data, a person may have rights to request access, correction, deletion, restriction, objection, portability or withdrawal of consent, and to complain to a competent supervisory authority. Some student-record requests may need to be made through the school that manages the account.
Send a request to [INSERT PRIVACY EMAIL]. Add the verified identity-check process, response timeframes, school escalation process and competent authority details before publication.
13. Changes and contact
Material changes should be reflected here with a revised date. If a new purpose or optional tracking technology is introduced, the Operator must provide the required notice and obtain any required consent before that processing begins.
Legal entity: [INSERT FULL LEGAL NAME]. Privacy contact: [INSERT VERIFIED PRIVACY EMAIL]. Cookie choices can be changed using the Cookie settings link on the Cookie Policy page. See the Cookie Policy and Terms & Conditions.