Data isolation and residency
Every organisation sits in a fully isolated tenant workspace, enforced at the database with row-level security. Data residency inside the Kingdom lands with general availability.
Procurement and security teams ask about these four first. Here are the answers, explained in full on the intro call.
Every organisation sits in a fully isolated tenant workspace, enforced at the database with row-level security. Data residency inside the Kingdom lands with general availability.
Explicit consent, export of your data whenever you ask, and full erasure. Built into the platform as functions you use, not a promise on a page.
Subscription invoices are issued from the platform, and ZATCA e-invoicing activates with our accredited provider.
Any CMA-regulated investment activity runs through a licensed partner, never through ilaf directly.

The four documents, as they stand today, with the date each was last reviewed.
The same answers published on the FAQ page, kept current by the ilaf team from HQ.
You do. Every partner has an isolated instance holding its own data, with consent, export and erasure tools built into the platform.
Your ecosystem data stays inside the Kingdom. The platform is built around Personal Data Protection Law requirements, subscription invoices are shaped for e-invoicing, and any regulated investment activity runs through a CMA-licensed partner.
Every person can download their data as a JSON file and erase their account from their own account page at any time. A whole-workspace export and deletion is run by the ilaf team on your written instruction, and the workspace is erased after the agreed retention period.
A 45-minute session on a live environment carrying your brand, and a reply within one business day.