Where the data lives

One database per institution, in a UAE cloud region, before any real student data is held. The product keeps no other copy of personal data. What leaves that database is short enough to list in full.

Sub-processors

Each is named in your agreement. Two of the three are used only if the institution turns them on.

Sub-processorWhen it is usedWhat it receives
Hosting providerAlways; named per agreementRuns the product and holds the institution's database and its backups, in the UAE region
E-mail relayOnly if the institution enables e-mail notificationsThe recipient's e-mail address and the text of the notice
External model providerOnly if the institution enables it and the student consentsThe tutor turn, for consenting students only, with no training on institution data recorded as a setting with the provider's terms

What leaves the database, in full

  • Checkpoint scores and totals go to the institution's own LMS gradebook through LTI 1.3 Advantage, at release.
  • E-mail addresses and notices go to the e-mail relay, only when e-mail is enabled.
  • Tutor turns go to the external model provider, only for students who consented, only when the institution enabled it.
  • Nothing else. Attempts, working lines, requests, accommodations, audit entries and consent records never leave the institution's database.

The statement

The data-residency and sub-processor statement in the compliance pack is generated from the institution's own settings, so it says which of the three are in use for your deployment. The lines only the hosting operator can fill in are marked as such.

Request the residency statement