Clarity School
One school. One shared overview.
Clarity School connects teachers, classes and agreed school-wide insights, with clear roles, limited data routes and an introduction that begins before any import.
From classroom to school
What belongs together, without mixing everything.
Teachers work in their classes. School leadership receives only agreed school-wide insights. Learners' personal areas do not become a general school profile.
Introduction
Do not simply switch it on. Approve it together.
Goals and roles
The school, teachers, administration and privacy leads agree which workflows genuinely belong in Clarity and who may see each area.
Data and safeguards
Purposes, data categories, roles, deletion routes, providers and safeguards for minors are documented before any production import. A School DPA has not yet been released publicly.
Start small
A limited pilot tests real workflows, roles, support needs, accessibility and rollback routes before more classes are added.
Approval and operation
The School agreement, DPA, responsibilities and expansion become binding only after technical and legal approval.
Current status
The features are defined. School operation still requires approval.
School is not presented as a finished rollout. The individual Teacher core, an institutional data route and a legally approved school are three different pieces of evidence.
Plan, role and boundaries
The catalogue defines the frame. Approval makes it operational.
School is listed as a separate B2B offering with teachers, classes, school-wide insights and 500 GB of Clarity Space. These details do not replace an offer, role design or privacy approval for a specific school.
- Offering
- School by enquiryNo public purchase. Scope, price, pilot and introduction are confirmed for the specific school.
- Catalogue frame
- Teachers and classesThe plan lists unlimited teachers and classes. The people and data that actually participate are limited before the pilot.
- Clarity Space
- 500 GB plan allocationStorage scope and technical write limits are confirmed in the School offer and before any production import.
Four conditions before production school data
- A working individual Teacher area is not an approved School operation. Institutional roles and access need their own evidence.
- The School agreement and school-specific DPA have not yet been released publicly. There is no production rollout or production data import without both.
- School-wide insights are limited by purpose, roles and data scope in the pilot. Learners' personal areas do not become a general school profile.
- Price, support route, storage operation and expansion are confirmed during the School enquiry; this website does not claim an existing partnership or a school already in operation.
More time for teaching begins before the first sign-in.
Tell us about the school, roles, number of classes and desired pilot. We will identify the next verifiable step without pretending that a finished rollout exists.