Nine pages for the people who sign: IT, privacy, procurement and quality. Each one says what the product does today and what is committed before the first pilot. Documents follow the plain language, not the other way round.
UAE hosting, one database per institution, encrypted backups with tested restore, roles, an audit log that cannot be edited, incident notice within 72 hours.
What is held and for how long, per data class; a privacy-officer seat; export, correction and deletion inside the product; who may open a tutor transcript.
Where the database lives, the three sub-processors and when each is used, and what never leaves the institution's database.
The tutor follows written rules on every turn, cannot give the final answer, and an external AI model is off unless the institution turns it on and each student agrees. Six safeguard areas, answered plainly.
WCAG 2.2 AA as the target, what an automated scan found, the fix plan, what has not been tested yet, and how to report a barrier.
Uptime of 99.5% in term, maintenance outside teaching hours, and the status page.
DPIA starter, record of processing, security overview, data-residency statement and accessibility conformance report, on request.
Terms, the data-processing agreement on request, and acceptable use.
Responsible disclosure: what to report, how we acknowledge, and our commitment to good-faith researchers.
These pages and the documents behind them state what the product does and how a deployment is configured. They do not claim compliance with any law or standard; that judgement belongs to your legal office, and we give it the facts it needs.
Write to us and the person who owns that control replies.