Privacy policy
Sample version: sample-2026-10-23 · 23 October 2026
This sample describes how information may be used when a school, its staff and its families use ZaraLearn. It is provided for product testing and must be tailored to the actual service before launch.
1. Information provided to the service
Registration may include a school’s name, location, chosen web address and an administrator’s name and email address. School workspaces may contain student and guardian details, class enrolments, attendance, assignments, results, communications and school-fee records. Use fictional records while testing.
2. Purpose of processing
The intended purposes are to create school workspaces, authenticate users, manage school records, deliver communications and support school-fee payment workflows. Information entered in a test workspace should only be used for those test activities.
3. School and account responsibilities
Schools should ensure they are authorised to enter and manage personal information, especially information about children. Users should provide only information relevant to their school activities and keep account credentials private.
4. Access and sharing
Access is intended to follow school membership and assigned roles. Guardians should access only records for linked children. Service providers may process information needed to host the application, deliver messages or handle payments. The production policy must identify actual providers and any international processing arrangements.
5. Payments
School-fee checkout is handled through the payment provider. The application may receive payment references, amounts and confirmation states to update school records. Enter payment details only on the provider’s checkout page and use provider test details during testing.
6. Cookies and browser storage
The application uses session cookies for authentication and browser storage to retain selected preferences, registration progress and payment-attempt references. Clearing browser storage may remove saved progress. A production policy should describe any additional analytics or advertising technologies actually used.
7. Retention and deletion
Test records should be removed when no longer needed for testing. Production retention periods, backup handling and any school recordkeeping requirements must be defined before launch. Contact the school administrator to request review, correction or removal of a school-managed record.
8. Security and individual requests
Users should sign out on shared devices and report unexpected access or suspected account misuse. Requests to access or correct information should be directed to the school or service contact as appropriate. This sample does not promise a particular response period or describe an audited security programme.
9. Updates to this sample
This document may change as the product and its operational arrangements are defined. A new policy version should be recorded when revised policies are made available for registration acceptance.
Questions and contact
For questions about this sample, use the contact page. For a school record or account request, contact your school administrator.