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.
Each is named in your agreement. Two of the three are used only if the institution turns them on.
| Sub-processor | When it is used | What it receives |
|---|---|---|
| Hosting provider | Always; named per agreement | Runs the product and holds the institution's database and its backups, in the UAE region |
| E-mail relay | Only if the institution enables e-mail notifications | The recipient's e-mail address and the text of the notice |
| External model provider | Only if the institution enables it and the student consents | The tutor turn, for consenting students only, with no training on institution data recorded as a setting with the provider's terms |
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.