Privacy.

02

1. Roles under PDPL

---

In a typical deployment, the customer acts as the data controller and DataSitr acts as a processor for the service workflow. Requests are handled on Saudi-hosted infrastructure. The live pilot stores limited operational state, including encrypted token mappings and compliance metadata, on Saudi-hosted operational systems.

03

2. The Three-Lane Data Geometry

---

Your data flow is automatically segmented:

• Green Lane (Tokenized External): For eligible requests, detected direct identifiers are replaced before sanitized text is sent to approved external providers.
• Amber Lane (Pseudonymized): Pseudonymized requests are handled on in-Kingdom infrastructure when external routing is not appropriate.
• Red Lane (In-Kingdom): Higher-risk or sensitive requests stay on in-Kingdom processing paths rather than being sent externally.

04

3. Cryptographic Vault and Retention

---

Identified PII is stored as AES-256-GCM encrypted token mappings for rehydration during the request workflow. On the live pilot, shared operational state runs on Saudi-hosted operational systems. Token mappings are time-limited, and compliance metadata may be retained to support audit and customer operations.

05

4. Data Subject Rights

---

We provide APIs that help the Data Controller carry out supported data-subject workflows, including export, deletion, and rectification of vaulted subject data and related records. Availability of any specific workflow depends on the deployed configuration and the customer's own legal process.

06

5. Last updated

---

This page was last updated on 2026-05-14.