> For the complete documentation index, see [llms.txt](https://docs.labs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labs.ai/security-and-compliance/privacy.md).

# Privacy & Data Processing

> **EDDI is a data processor.** Organizations deploying EDDI act as the data controller and are responsible for obtaining user consent, maintaining data processing agreements (DPAs), and ensuring lawful basis for processing.

## What Data EDDI Stores

| Data Category             | Storage              | Contains PII?                                | Retention                                                                |
| ------------------------- | -------------------- | -------------------------------------------- | ------------------------------------------------------------------------ |
| **Conversation Memory**   | MongoDB / PostgreSQL | Yes (userId, chat content)                   | 365 days default (configurable)                                          |
| **User Memory**           | MongoDB / PostgreSQL | Yes (userId, structured facts)               | Until deleted, or `eddi.usermemories.deleteOlderThanDays` (default: off) |
| **Audit Ledger**          | MongoDB / PostgreSQL | Yes (userId, prompts, responses, tool calls) | Indefinite (EU AI Act record-keeping); content redacted on erasure       |
| **Database Logs**         | MongoDB / PostgreSQL | Yes (userId, log messages)                   | `eddi.logs.db-retention-days` (default: kept until deleted)              |
| **Managed Conversations** | MongoDB / PostgreSQL | Yes (userId, intent)                         | Until explicitly deleted                                                 |

## Data Subject Rights

### Right to Erasure (Art. 17)

EDDI provides a unified erasure endpoint:

```
DELETE /admin/gdpr/{userId}
```

This cascades across all stores:

1. **User memories** — permanently deleted
2. **Conversation snapshots** — permanently deleted
3. **Managed conversation mappings** — permanently deleted
4. **Database logs** — userId pseudonymized with a keyed (`gdpr-erased:k1:`) or per-deployment-salted (`gdpr-erased:s1:`) value; the log message text is kept
5. **Audit ledger** — rows kept; recorded content (prompt, response, LLM detail, tool calls) redacted and userId pseudonymized. `eddi.audit.erasure-mode=pseudonymize` (default `redact`) keeps the content and pseudonymizes the userId only

This is the short list; the full cascade is in [gdpr-compliance.md](https://docs.labs.ai/security-and-compliance/gdpr-compliance.md#1-right-to-erasure-gdpr-art-17--ccpa-1798105).

**Why keep the audit rows?** Record-keeping obligations for AI systems (EU AI Act Arts. 12/19) cover the record that processing happened, so the rows and their chain stay — but not with the erased person's data in them. The pseudonym is **not** anonymisation: the database-log pseudonym is keyed or salted, so it cannot be recomputed from a list of candidate identifiers without the key or salt (rows from older releases, and a fallback when the salt cannot be read, keep an unsalted SHA-256 value that can), and pseudonymised data remains personal data (GDPR Art. 4(5)).

### Right of Access / Portability (Art. 15/20)

```
GET /admin/gdpr/{userId}/export
```

Returns user data as JSON: memories, conversations (with chat history), managed conversation mappings, audit processing records, attachment metadata, linked (OAuth) accounts, and the group discussions the user started with their shared artifacts. Schedules and HITL tool-journal entries are not exported yet (the erasure does delete them); they are named in `omittedCategories`, so the response is currently always `207 Multi-Status` with `complete: false` — see [gdpr-compliance.md](https://docs.labs.ai/security-and-compliance/gdpr-compliance.md#2-right-of-access-gdpr-art-15--data-portability-art-20--right-to-know-ccpa-1798100).

### Right to Restriction (Art. 18)

```
POST   /admin/gdpr/{userId}/restrict
GET    /admin/gdpr/{userId}/restrict
DELETE /admin/gdpr/{userId}/restrict
```

Restricts, checks (`true`/`false`) and lifts a restriction. While restricted, new conversations and new turns for the user are refused with `403`; stored data is kept. See [gdpr-compliance.md](https://docs.labs.ai/security-and-compliance/gdpr-compliance.md#3-right-to-restriction-of-processing-gdpr-art-18--lgpd-art-18).

### MCP Tools

For AI-orchestrated compliance workflows:

* `delete_user_data` — full cascade erasure (requires `confirmation="CONFIRM"`)
* `export_user_data` — the same bundle as the export endpoint; check `complete` and `omittedCategories` before treating it as a full Art. 15 response

## Security Measures

* **Encryption at rest**: AES-256-GCM via Secrets Vault for API keys and credentials
* **Audit trail**: append-only ledger with HMAC-signed entries for tamper detection — signed only when `EDDI_VAULT_MASTER_KEY` or `EDDI_AUDIT_HMAC_KEY` is set
* **Secret redaction**: `SecretRedactionFilter` scrubs API keys, tokens, and vault references from audit entries before persistence
* **RBAC**: All GDPR endpoints require `eddi-admin` role
* **Input validation**: URL validation, regex injection prevention, path traversal protection
* **PII-safe logging**: GDPR operations log pseudonyms, never raw user IDs

## Third-Party Data Transfers (GDPR Art. 44-49)

EDDI sends conversation content to configured LLM providers during AI processing. **Every conversation turn constitutes a data transfer to the selected provider.** The specific provider is configured per agent by the deployer.

### Supported LLM Providers and Data Locations

| Provider                                                                               | Data Location                                                                                     | Self-Hosted? | DPA Available                                                   |
| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | ------------ | --------------------------------------------------------------- |
| **Ollama**                                                                             | Your infrastructure                                                                               | ✅ Yes        | N/A (local)                                                     |
| **jlama**                                                                              | Your infrastructure                                                                               | ✅ Yes        | N/A (local)                                                     |
| **Self-hosted OpenAI-compatible** (`openai-compatible`: vLLM, llama-server, TGI, …)    | Wherever you run the server                                                                       | ✅ Yes        | N/A (your server)                                               |
| **Anthropic**                                                                          | US/EU (varies)                                                                                    | ❌ No         | [anthropic.com/policies](https://www.anthropic.com/policies)    |
| **OpenAI**                                                                             | US                                                                                                | ❌ No         | [openai.com/policies](https://openai.com/policies)              |
| **Google Gemini**                                                                      | US/EU (varies)                                                                                    | ❌ No         | [cloud.google.com/terms](https://cloud.google.com/terms)        |
| **Mistral**                                                                            | EU (France)                                                                                       | ❌ No         | [mistral.ai/terms](https://mistral.ai/terms/)                   |
| **Azure OpenAI**                                                                       | Your Azure region                                                                                 | Partially    | Via Azure Enterprise Agreement                                  |
| **AWS Bedrock**                                                                        | Your AWS region                                                                                   | Partially    | Via AWS Enterprise Agreement                                    |
| **Oracle GenAI**                                                                       | Your OCI region                                                                                   | Partially    | Via Oracle Cloud Agreement                                      |
| **Hugging Face**                                                                       | Varies by model host                                                                              | Partially    | [huggingface.co/terms](https://huggingface.co/terms-of-service) |
| **Vertex AI**                                                                          | Your Google Cloud region                                                                          | Partially    | Via Google Cloud terms                                          |
| **xAI, DeepSeek, Moonshot, Qwen, Z.ai, MiniMax, OpenRouter, Groq** (OpenAI-compatible) | Provider-operated; several are hosted outside the EU/US, including in China (check each provider) | ❌ No         | Check each provider's own terms                                 |

### Deployer Responsibilities for LLM Data Transfers

As the data controller, you **must**:

1. **Select providers**: Choose LLM providers that meet your data residency and compliance requirements
2. **Establish DPAs**: Sign Data Processing Agreements with each cloud LLM provider you configure in EDDI
3. **Document transfers**: Record all LLM providers in your Article 30 processing register
4. **Inform users**: Disclose in your privacy policy that conversations are processed by third-party AI providers
5. **Assess adequacy**: For non-EU providers, ensure adequate safeguards (Standard Contractual Clauses, adequacy decisions, or binding corporate rules) per GDPR Art. 46
6. **Consider self-hosting**: For maximum data sovereignty, use Ollama or jlama with self-hosted models — zero external data transfers

### What Data is Sent to LLM Providers

The current message, the conversation history window and the agent's templated system prompt — and, depending on the agent's configuration, the user's persistent memories (including `global` memories other agents wrote about the same user), retrieved documents, tool results and group discussion content. EDDI adds no user identifier to a provider request by itself; one reaches the provider only if a prompt template or a tool result contains it. The full inventory is in [What reaches the LLM provider](https://docs.labs.ai/security-and-compliance/compliance-data-flow.md#what-reaches-the-llm-provider).

## Consent (GDPR Art. 6/7)

EDDI does **not** manage user consent. As a data processor, consent is the controller's responsibility.

### Legal Basis

EDDI's data processing activities and their typical legal bases:

| Processing Activity     | Suggested Legal Basis                         | Notes                    |
| ----------------------- | --------------------------------------------- | ------------------------ |
| Conversation processing | Art. 6(1)(a) Consent or Art. 6(1)(b) Contract | Controller determines    |
| Persistent user memory  | Art. 6(1)(a) Consent                          | Users should be informed |
| Audit ledger retention  | Art. 6(1)(c) Legal obligation                 | EU AI Act Arts. 12/19    |
| System logging          | Art. 6(1)(f) Legitimate interest              | Operational necessity    |

### Controller Obligations

Deployers should:

1. Obtain appropriate consent before enabling conversational AI
2. Inform users about data processing via their privacy policy
3. Provide clear opt-out mechanisms in their application
4. Leave `enableMemoryTools` off (the default) unless users are explicitly informed that their interactions are remembered across sessions — and note that `longTerm` properties set by a property setter persist across sessions whatever that flag says
5. Document the legal basis for each processing activity in your Article 30 register

## CCPA Compliance

### Do Not Sell (§1798.120)

EDDI does **not sell personal information** and has no mechanism to do so. EDDI is middleware infrastructure — it processes data on behalf of the deployer (controller) and does not share, sell, or monetize user data with any third party for commercial purposes.

If your deployment scenario involves sharing user data with third parties (e.g., analytics providers), this is the controller's responsibility to manage and disclose.

### Right to Know (§1798.100) and Right to Delete (§1798.105)

The GDPR export and erasure endpoints serve both, with the same results and the same limits: the export does not yet cover every category, and the erasure keeps the audit ledger (redacted) and database logs (pseudonymized). See [gdpr-compliance.md](https://docs.labs.ai/security-and-compliance/gdpr-compliance.md#ccpa-specific-requirements).

## Data Retention

| Category            | Default                                | Configuration                                                                                                                                                               |
| ------------------- | -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Ended conversations | Deleted after 365 days                 | `eddi.conversations.deleteEndedConversationsOnceOlderThanDays` (a database migrated from EDDI 5 holds this sweep until `eddi.migration.v6-rename.retention-confirmed=true`) |
| Idle conversations  | Ended (not deleted) after 90 days idle | `eddi.conversations.maximumLifeTimeOfIdleConversationsInDays`                                                                                                               |
| User memories       | No auto-delete                         | `eddi.usermemories.deleteOlderThanDays`, or the GDPR API / MCP tools                                                                                                        |
| Audit ledger        | No auto-delete                         | Retained for EU AI Act record-keeping; content redacted on erasure                                                                                                          |
| Database logs       | No auto-delete                         | `eddi.logs.db-retention-days`                                                                                                                                               |

Set retention to `-1` to disable automatic cleanup.

## International Privacy Regulations

EDDI is open-source middleware deployed by organizations worldwide in regulated environments. This section maps each major privacy framework to EDDI's technical capabilities and identifies the organizational measures deployers add on top.

> **How to read this section**: Privacy regulations have two layers — **technical safeguards** (encryption, access control, audit, erasure) and **organizational measures** (consent processes, officer appointments, breach notification procedures). EDDI implements the technical layer. Your organization implements the organizational layer. Together, they form a complete compliance posture.
>
> * ✅ **Built-in** — EDDI handles this out of the box
> * 🏢 **Your org** — Organizational measure, outside the scope of middleware
> * ✅ + 🏢 — EDDI provides the technical foundation; your org completes it

***

### PIPEDA — Canada

Canada's **Personal Information Protection and Electronic Documents Act** (2000, amended 2023) governs the collection, use, and disclosure of personal information in the course of commercial activity. It follows the 10 Fair Information Principles.

| PIPEDA Principle            | EDDI Technical Capability                                                                                                                                                                                              | Status      |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
| **Accountability**          | Audit ledger (HMAC-signed when a key is configured) records conversation processing and administrative actions (reads are not recorded)                                                                                | ✅ + 🏢      |
| **Identifying Purposes**    | Agent configuration documents AI processing purpose                                                                                                                                                                    | ✅ + 🏢      |
| **Consent**                 | Deployer integrates consent capture in their application layer                                                                                                                                                         | 🏢 Your org |
| **Limiting Collection**     | Token-aware windowing limits data sent to LLMs; configurable retention auto-deletes old conversations                                                                                                                  | ✅ Built-in  |
| **Limiting Use/Disclosure** | Data used only for configured agent interactions; audit trail logs every LLM invocation (model name, prompt, response)                                                                                                 | ✅ Built-in  |
| **Accuracy**                | Conversation state is timestamped and versioned; user memories updatable via `PUT /usermemorystore/memories`                                                                                                           | ✅ Built-in  |
| **Safeguards**              | AES-256-GCM envelope encryption (Secrets Vault), HMAC-SHA256 audit integrity, Keycloak OIDC, role-based access control                                                                                                 | ✅ Built-in  |
| **Openness**                | Full source code is open (Apache 2.0); PRIVACY.md and documentation are public                                                                                                                                         | ✅ Built-in  |
| **Individual Access**       | `GET /admin/gdpr/{userId}/export` — returns memories, conversation outputs, managed conversation mappings and other categories as JSON; it is always reported incomplete and names what it omits (`omittedCategories`) | ✅ Built-in  |
| **Challenging Compliance**  | `DELETE /admin/gdpr/{userId}` — cascade deletion; audit trail kept with its content redacted and the user id pseudonymized                                                                                             | ✅ Built-in  |

**Deployer checklist**:

| Responsibility    | Details                                                                                                                                                                                                                                   |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Consent capture   | Integrate consent flow in your frontend before enabling EDDI chat. PIPEDA: implied consent for non-sensitive data, express consent for sensitive data (health, financial)                                                                 |
| Bilingual notices | Provide English/French privacy notices for Canadian consumers                                                                                                                                                                             |
| Breach reporting  | Report breaches with "real risk of significant harm" to the **Office of the Privacy Commissioner** (OPC) and affected individuals. Maintain breach records for 24 months. Use EDDI's `docs/incident-response.md` as your runbook template |

***

### LGPD — Brazil

Brazil's **Lei Geral de Proteção de Dados** (2018, effective 2020) closely mirrors GDPR and grants data subjects (titulares) extensive rights over their personal data.

| LGPD Right                                    | EDDI Technical Capability                                                                                                                                         | Status     |
| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
| Confirmation of processing (Art. 18, I)       | Documented in PRIVACY.md; audit trail records conversation processing and administrative actions                                                                  | ✅ Built-in |
| Access to data (Art. 18, II)                  | `GET /admin/gdpr/{userId}/export` — full JSON bundle                                                                                                              | ✅ Built-in |
| Correction of inaccurate data (Art. 18, III)  | `PUT /usermemorystore/memories` — upserts individual memory entries                                                                                               | ✅ Built-in |
| Anonymization/blocking/deletion (Art. 18, IV) | `DELETE /admin/gdpr/{userId}` — cascade deletion; audit trail redacted and pseudonymized                                                                          | ✅ Built-in |
| Data portability (Art. 18, V)                 | JSON export, machine-readable; partial (it names the categories it omits)                                                                                         | ✅ Built-in |
| Deletion of unnecessary data (Art. 18, VI)    | Configurable retention (`eddi.conversations.deleteEndedConversationsOnceOlderThanDays`) + idle conversation auto-end                                              | ✅ Built-in |
| Information about sharing (Art. 18, VII)      | LLM provider data flows documented; audit trail records model name per invocation                                                                                 | ✅ Built-in |
| Consent revocation (Art. 18, IX)              | `POST /agents/{conversationId}/endConversation` + `DELETE /admin/gdpr/{userId}` provide the technical mechanism; consent state tracking is your application layer | ✅ + 🏢     |

**Deployer checklist**:

| Responsibility         | Details                                                                                                                               |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Legal basis            | Establish a legal basis for processing (consent, legitimate interest, contract performance) before deploying EDDI agents              |
| DPO appointment        | Appoint a **Data Protection Officer** (Encarregado) — mandatory for all controllers                                                   |
| DPIA                   | Conduct and document Data Protection Impact Assessments for AI processing. EDDI's audit ledger provides the data inputs for your DPIA |
| Breach reporting       | Report security incidents to the **ANPD** within a "reasonable time" (ANPD recommends 2 business days)                                |
| Cross-border transfers | Ensure LLM providers meet LGPD transfer requirements (adequacy decisions, standard contractual clauses, or binding corporate rules)   |
| Portuguese notices     | Provide privacy notices in **Portuguese**                                                                                             |

***

### APPI — Japan

Japan's **Act on the Protection of Personal Information** (2003, significantly amended 2022) is one of Asia's most mature data protection laws. Japan holds an EU adequacy decision, facilitating cross-border data flows between the two regions.

| APPI Obligation                            | EDDI Technical Capability                                                                                                                                                                                                                  | Status     |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- |
| Purpose of use specification (Art. 17)     | Agent configuration documents processing purpose via system prompts and behavior rules                                                                                                                                                     | ✅ + 🏢     |
| Accurate and up-to-date data (Art. 19)     | Conversation state is timestamped and versioned; user memories are updatable via REST API                                                                                                                                                  | ✅ Built-in |
| Security control measures (Art. 23)        | AES-256-GCM vault encryption, HMAC-SHA256 audit integrity, Keycloak OIDC, RBAC, SSRF protection, sandboxed evaluation                                                                                                                      | ✅ Built-in |
| Supervision of employees (Art. 24)         | Keycloak OIDC + role-based access (eddi-admin, eddi-editor, eddi-user, eddi-approver, eddi-viewer)                                                                                                                                         | ✅ Built-in |
| Supervision of contractors (Art. 25)       | LLM provider data flows documented in PRIVACY.md; audit trail records which model/provider processed each turn                                                                                                                             | ✅ Built-in |
| Disclosure to data subjects (Art. 33)      | `GET /admin/gdpr/{userId}/export` — full data bundle                                                                                                                                                                                       | ✅ Built-in |
| Correction and deletion (Art. 34-35)       | `PUT /usermemorystore/memories` for correction; `DELETE /admin/gdpr/{userId}` for deletion                                                                                                                                                 | ✅ Built-in |
| Breach notification (Art. 26)              | Incident response runbook (`docs/incident-response.md`)                                                                                                                                                                                    | ✅ Built-in |
| Cross-border transfer (Art. 28)            | EDDI documents provider data flows; deployer verifies recipient country protections and obtains consent where required                                                                                                                     | ✅ + 🏢     |
| Pseudonymized information (2022 amendment) | GDPR erasure pseudonymizes the identifiers it keeps (a keyed HMAC in the audit ledger when it signs, an unkeyed SHA-256 otherwise; a keyed or salted pseudonym in the database logs) — satisfies APPI's pseudonymized information category | ✅ Built-in |

**Deployer checklist**:

| Responsibility            | Details                                                                                                                                                                   |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Purpose documentation     | Document AI processing purposes in your privacy notice; EDDI's agent config captures intent, but your privacy policy communicates it to users                             |
| Cross-border verification | Verify LLM provider countries meet APPI equivalence or obtain individual consent. Japan→EU: covered by adequacy decision. Other countries: require contractual safeguards |
| PPC registration          | Register with the **Personal Information Protection Commission** (PPC) if processing data at scale                                                                        |
| Breach reporting          | Notify PPC and affected individuals **promptly** (report within 3-5 days in practice, full report within 30 days)                                                         |

***

### POPIA — South Africa

South Africa's **Protection of Personal Information Act** (2013, effective 2021) establishes 8 data processing conditions closely aligned with EU standards. Enforced by the Information Regulator.

| POPIA Condition                             | EDDI Technical Capability                                                                    | Status     |
| ------------------------------------------- | -------------------------------------------------------------------------------------------- | ---------- |
| Accountability (Condition 1)                | Audit ledger (HMAC-signed when a key is configured), documented data flows, open-source code | ✅ Built-in |
| Processing limitation (Condition 2)         | Token-aware windowing, configurable retention, idle conversation auto-end                    | ✅ Built-in |
| Purpose specification (Condition 3)         | Agent configuration documents purpose; deployer communicates to users                        | ✅ + 🏢     |
| Further processing limitation (Condition 4) | Data used only for configured agent interactions; audit trail provides accountability        | ✅ Built-in |
| Information quality (Condition 5)           | Timestamped, versioned state; user memories updatable                                        | ✅ Built-in |
| Openness (Condition 6)                      | Public PRIVACY.md + Apache 2.0 open source                                                   | ✅ Built-in |
| Security safeguards (Condition 7)           | AES-256-GCM, HMAC, Keycloak OIDC, RBAC, SSRF protection                                      | ✅ Built-in |
| Data subject participation (Condition 8)    | Export endpoint + cascade deletion endpoint                                                  | ✅ Built-in |

**Deployer checklist**:

| Responsibility                     | Details                                                                                                                                                                                               |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Information Regulator registration | Register with the **Information Regulator** before processing personal information                                                                                                                    |
| Information Officer                | Appoint an **Information Officer** — mandatory for all responsible parties                                                                                                                            |
| Special personal information       | POPIA requires prior authorization from the Information Regulator for processing special personal information (health, biometric, children's data). Assess whether your EDDI agents process such data |
| Breach notification                | Notify the Information Regulator and data subjects "as soon as reasonably possible"                                                                                                                   |
| Language requirements              | Provide privacy notices in at least one of South Africa's **11 official languages** relevant to your user base                                                                                        |
| Cross-border transfers             | Only to countries with adequate protection or with appropriate safeguards (binding corporate rules, consent)                                                                                          |

***

### PDPA — Southeast Asia

The **Personal Data Protection Act** applies in multiple Southeast Asian jurisdictions. Singapore's PDPA (2012, major amendments 2021), Thailand's PDPA (2019, effective 2022), and Malaysia's PDPA (2010, amended 2024) are the most mature.

#### Singapore PDPA

| Singapore PDPA Obligation          | EDDI Technical Capability                                             | Status      |
| ---------------------------------- | --------------------------------------------------------------------- | ----------- |
| Consent (Part 4)                   | Deployer integrates consent capture in their application layer        | 🏢 Your org |
| Purpose limitation (Part 4)        | Agent configuration documents purpose; deployer communicates to users | ✅ + 🏢      |
| Access obligation (Part 5)         | `GET /admin/gdpr/{userId}/export` — full data bundle                  | ✅ Built-in  |
| Correction obligation (Part 5)     | `PUT /usermemorystore/memories` — upserts individual entries          | ✅ Built-in  |
| Accuracy obligation (Part 4)       | Timestamped, versioned conversation state                             | ✅ Built-in  |
| Protection obligation (Part 5)     | AES-256-GCM, HMAC, Keycloak OIDC, RBAC                                | ✅ Built-in  |
| Retention limitation (Part 5)      | Configurable auto-cleanup + configurable idle conversation timeout    | ✅ Built-in  |
| Transfer limitation (Part 5)       | Provider data flows documented; deployer verifies transfer safeguards | ✅ + 🏢      |
| Data breach notification (Part 6A) | Incident response runbook template                                    | ✅ Built-in  |

**Deployer checklist (Singapore)**:

| Responsibility         | Details                                                                                                                                    |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Consent capture        | Singapore PDPA has a deemed consent framework for business improvement, but explicit consent is required for most AI processing            |
| DPO appointment        | Appoint a **Data Protection Officer** (DPO) — mandatory                                                                                    |
| Breach notification    | Notify the **PDPC** within **3 calendar days** of assessing a notifiable breach; notify affected individuals as soon as practicable        |
| DPIA for AI processing | Mandatory Data Protection Impact Assessment for high-risk AI processing. EDDI's audit ledger provides the technical evidence for your DPIA |

#### Thailand PDPA

Thailand's PDPA is structurally modeled on GDPR. EDDI's GDPR infrastructure covers all technical requirements. Key deployer responsibilities:

**Deployer checklist (Thailand)**:

| Responsibility             | Details                                                                                   |
| -------------------------- | ----------------------------------------------------------------------------------------- |
| DPO appointment            | Appoint a DPO if processing sensitive data or performing large-scale monitoring           |
| Breach notification        | Notify the **PDPC** (Personal Data Protection Committee) within **72 hours** of discovery |
| Cross-border transfers     | Require adequacy, appropriate safeguards, or consent                                      |
| Thai-language notices      | Provide privacy notices in **Thai**                                                       |
| Consent for sensitive data | Explicit consent required for sensitive personal data (health, biometrics, etc.)          |

#### Malaysia PDPA

Malaysia's **Personal Data Protection Act** (2010, significant amendments 2024) regulates the processing of personal data in commercial transactions. The 2024 amendments introduced mandatory breach notification, appointment of data protection officers, and cross-border data transfer mechanisms — aligning Malaysia more closely with GDPR.

| Malaysia PDPA Principle                   | EDDI Technical Capability                                                                                                         | Status      |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ----------- |
| General Principle (lawful processing)     | Agent configuration documents processing purpose; deployer establishes lawful basis                                               | ✅ + 🏢      |
| Notice and Choice Principle               | Deployer provides notice and obtains consent in their application layer                                                           | 🏢 Your org |
| Disclosure Principle                      | LLM provider data flows documented in PRIVACY.md; audit trail records which provider processed each turn                          | ✅ Built-in  |
| Security Principle                        | AES-256-GCM vault encryption, HMAC-SHA256 audit integrity, Keycloak OIDC, RBAC, SSRF protection                                   | ✅ Built-in  |
| Retention Principle                       | Configurable auto-cleanup (`deleteEndedConversationsOnceOlderThanDays`) + idle conversation timeout                               | ✅ Built-in  |
| Data Integrity Principle                  | Timestamped, versioned conversation state; user memories updatable via REST API                                                   | ✅ Built-in  |
| Access Principle                          | `GET /admin/gdpr/{userId}/export` — full data bundle in machine-readable JSON                                                     | ✅ Built-in  |
| Correction (2024 amendment)               | `PUT /usermemorystore/memories` — upserts individual entries                                                                      | ✅ Built-in  |
| Deletion (2024 amendment)                 | `DELETE /admin/gdpr/{userId}` — cascade deletion across the stores listed in the GDPR guide; audit rows and log text are retained | ✅ Built-in  |
| Data breach notification (2024 amendment) | Incident response runbook template (`docs/incident-response.md`)                                                                  | ✅ Built-in  |
| Cross-border transfer (2024 amendment)    | Provider data flows documented; deployer applies for approval or uses whitelisted countries                                       | ✅ + 🏢      |

**Deployer checklist (Malaysia)**:

| Responsibility          | Details                                                                                                                                                              |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Registration            | Register with the **Department of Personal Data Protection** (JPDP) if processing personal data                                                                      |
| DPO appointment         | Appoint a **Data Protection Officer** — mandatory under the 2024 amendments                                                                                          |
| Consent capture         | Obtain consent before processing; separate consent required for each purpose; consent must be in both **Bahasa Malaysia and English**                                |
| Breach notification     | Notify the **JPDP Commissioner** as soon as practicable (within **72 hours** under 2024 amendments); notify affected data subjects without undue delay               |
| Cross-border transfers  | The 2024 amendments introduced a whitelist model — data may only be transferred to countries specified by the Minister, or with explicit consent of the data subject |
| Sensitive personal data | Processing of sensitive data (health, political opinions, religion, criminal offences) requires **explicit consent** and additional safeguards                       |

***

### PIPL — China

China's **Personal Information Protection Law** (2021) is one of the world's strictest data privacy frameworks. It has strong extraterritorial reach, strict data localization requirements, and heavy penalties (up to 5% of annual revenue). PIPL is particularly relevant for EDDI deployments serving users in mainland China, as it imposes specific requirements on cross-border data transfers and AI-powered automated decision-making.

| PIPL Obligation                                     | EDDI Technical Capability                                                                                                                                         | Status      |
| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- |
| Lawful basis for processing (Art. 13)               | Agent configuration documents purpose; deployer establishes legal basis (consent, contract, public interest, etc.)                                                | ✅ + 🏢      |
| Informed consent / separate consent (Art. 14, 29)   | Deployer integrates consent capture and separate consent UI for sensitive data, cross-border transfer, and public disclosure                                      | 🏢 Your org |
| Right to know (Art. 44)                             | Documented data processing in PRIVACY.md; agent configs describe purpose                                                                                          | ✅ + 🏢      |
| Right to access and copy (Art. 45)                  | `GET /admin/gdpr/{userId}/export` — full data bundle in structured JSON                                                                                           | ✅ Built-in  |
| Right to correction (Art. 46)                       | `PUT /usermemorystore/memories` — upserts individual entries                                                                                                      | ✅ Built-in  |
| Right to deletion (Art. 47)                         | `DELETE /admin/gdpr/{userId}` — cascade deletion across the stores listed in the GDPR guide; audit trail kept with content redacted and the user id pseudonymized | ✅ Built-in  |
| Right to refuse automated decision-making (Art. 24) | Deployer provides opt-out mechanism; EDDI's audit ledger records all AI decisions for transparency                                                                | ✅ + 🏢      |
| Data minimization (Art. 6)                          | Token-aware windowing limits data sent to LLMs; configurable retention auto-deletes old conversations                                                             | ✅ Built-in  |
| Security measures (Art. 51)                         | AES-256-GCM vault encryption, HMAC-SHA256 audit integrity, Keycloak OIDC, RBAC, SSRF protection, sandboxed evaluation                                             | ✅ Built-in  |
| Data breach notification (Art. 57)                  | Incident response runbook template (`docs/incident-response.md`)                                                                                                  | ✅ Built-in  |
| Impact assessment for sensitive data (Art. 55)      | EDDI's audit ledger and data flow documentation provide evidence for Personal Information Protection Impact Assessments (PIIAs)                                   | ✅ + 🏢      |
| Audit and record-keeping (Art. 54)                  | Append-only audit ledger of pipeline task executions, HMAC-signed when a signing key is configured                                                                | ✅ Built-in  |

**Deployer checklist (China)**:

| Responsibility                                    | Details                                                                                                                                                                                                                                                                                            |
| ------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Data localization                                 | PIPL Art. 40 requires **Critical Information Infrastructure Operators** (CIIOs) and processors exceeding volume thresholds to store personal information **within mainland China**. Use self-hosted LLM providers (Ollama, jlama) or Chinese cloud providers to avoid cross-border transfer issues |
| Cross-border data transfer                        | If personal information must leave China, complete one of: (1) **CAC security assessment** (mandatory for CIIOs or large volumes), (2) **PIPL standard contract** filed with provincial CAC, or (3) **Personal information protection certification** from an accredited body (Art. 38)            |
| Separate consent                                  | Obtain **separate, informed consent** for: cross-border transfers (Art. 39), sensitive personal information processing (Art. 29), public disclosure of personal information, and image/identity processing in public spaces                                                                        |
| Personal Information Protection Impact Assessment | Conduct PIIAs before: processing sensitive data, using personal data for automated decision-making, cross-border transfers, or any processing that significantly impacts individuals (Art. 55). EDDI's audit ledger and data flow docs provide the technical input                                 |
| DPO / representative appointment                  | Appoint a **Personal Information Protection Officer** if processing volume exceeds CAC thresholds. Foreign organizations processing Chinese residents' data must designate a **domestic representative** (Art. 53)                                                                                 |
| Breach notification                               | Notify the **Cyberspace Administration of China** (CAC) and affected individuals **immediately** upon discovering a breach. Notification must include: categories of data, cause, potential harm, and remediation measures (Art. 57)                                                               |
| Automated decision-making transparency            | PIPL Art. 24 requires transparency and fairness in automated decision-making. Provide users with an explanation of decision logic and an opt-out mechanism. Do **not** use automated decisions to impose unreasonable differential treatment on individuals                                        |
| LLM provider selection                            | Prefer providers with data centers in mainland China (e.g., Azure China, Alibaba Cloud, Baidu, local Ollama deployment) to avoid triggering cross-border transfer obligations                                                                                                                      |

> **⚠️ Important**: PIPL's cross-border data transfer regime is significantly stricter than GDPR's. Using cloud-hosted LLM providers (OpenAI, Anthropic, Google, etc.) with Chinese user data likely triggers cross-border transfer obligations. For China-targeted deployments, **self-hosted models via Ollama or jlama are strongly recommended** to keep all data within Chinese jurisdiction.

***

### Other Jurisdictions

For jurisdictions not listed above, EDDI's data protection infrastructure generally meets international standards. Key regions and their primary regulations:

| Region          | Regulation                                         | Key Notes                                                                                                           |
| --------------- | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Australia**   | Privacy Act 1988 + APPs                            | 13 Australian Privacy Principles; notifiable data breach scheme; OAIC oversight                                     |
| **South Korea** | PIPA (Personal Information Protection Act)         | Strict consent requirements; mandatory DPO; 72-hour breach notification                                             |
| **India**       | DPDPA (Digital Personal Data Protection Act, 2023) | Consent-based framework; "significant data fiduciary" category; cross-border restrictions to blocked countries only |
| **EU/EEA**      | GDPR                                               | See [gdpr-compliance.md](https://docs.labs.ai/security-and-compliance/gdpr-compliance.md)                           |
| **USA (state)** | CCPA/CPRA (CA), VCDPA (VA), CPA (CO), etc.         | See CCPA section above                                                                                              |
| **UK**          | UK GDPR + Data Protection Act 2018                 | Substantially mirrors EU GDPR; ICO oversight                                                                        |

For all jurisdictions: deployers should consult local counsel to confirm organizational obligations specific to their region.

## Contact

For privacy-related inquiries about the EDDI platform, contact the project maintainers at [github.com/labsai/EDDI](https://github.com/labsai/EDDI).
