CoreShieldCoreShield AI

Last updated:

Draft — pilot phase · under legal review

The Arabic version of this document is the authoritative legal text. This English translation is provided for convenience; in case of any discrepancy, the Arabic version prevails.

Data Processing Agreement (DPA)

Controller: [Customer legal entity], [Customer registered address] Processor: MainCore Technologies, Kingdom of Saudi Arabia Effective: 16 July 2026 Applicable: GDPR Article 28, Saudi PDPL

1. Scope

This DPA applies to Personal Data that Controller uploads to the Service and Processor processes on Controller's behalf. It supplements the Terms of Service.

2. Subject matter & duration

Subject matter: processing of Personal Data via CoreShield's Detect → Cloak → Send → Restore pipeline. Duration: the term of the underlying subscription plus any period during which residual Personal Data is retained per Section 8.

3. Nature & purpose

Processing enables Controller to use external LLMs on documents containing Personal Data while reducing that Personal Data's exposure to those LLMs. Detected sensitive values are sealed in an AES-256-GCM vault and replaced with tokens before sending; values the detection does not recognise — notably some personal names — can reach the provider as written. Cloaking reduces risk; it is not a guarantee.

4. Types of data & categories of data subjects

Types: as determined by Controller's uploads — typically names, national IDs, IBANs, medical record numbers, addresses, phone numbers, email addresses.

Data subjects: as determined by Controller — typically Controller's employees, customers, patients, counterparties, or the subjects of documents Controller processes.

5. Processor obligations

Processor will:

6. Sub-processors

Processor's sub-processor list is at Annex A. Controller consents to the current list. Processor will notify Controller of additions with 30 days' notice; Controller may object during that period.

7. Data residency & international transfers

The current pilot is hosted on Microsoft Azure (UAE North region) and processes synthetic data only — no real customer Personal Data. Real customer data will be hosted on infrastructure inside the Kingdom of Saudi Arabia. Licensed in-Kingdom cloud providers are currently under evaluation, including STC Cloud, and the final provider will be determined before any real data is processed. The migration to in-Kingdom infrastructure will be completed upon the first real customer contract, before any real customer Personal Data is processed. Where any transfer outside the in-Kingdom region occurs, it relies on EU Standard Contractual Clauses or an equivalent PDPL-approved mechanism. Under the Send verb, cloaked text is transmitted to the external LLM provider; it may include values the detection did not recognise, notably some personal names.

8. Return & deletion

On termination, Processor will delete Personal Data within 30 days unless Controller instructs return in a machine-readable format. Backups are retained for 7 days on a rolling basis and are then purged automatically. These are two separate processes: deletion removes Personal Data from the live service within 30 days of termination, while backups expire on their own rolling 7-day cycle, so a deleted value is gone from every backup no more than 7 days after it was deleted from the live service. Audit-chain records are retained for 7 years as required by NCA-ECC.

9. Audits

Once per year (or after a Personal Data Breach), Controller may audit Processor's controls, on 30 days' notice, at Controller's cost, subject to Processor's reasonable confidentiality and security requirements. Processor's SOC-2 Type II report (once obtained) satisfies routine audit needs.

10. Liability

Liability under this DPA is subject to the limitation of liability in the Terms of Service. Sub-processor breaches are Processor's responsibility as if committed by Processor.

Annex A — Approved sub-processors

Microsoft Azure and OpenAI were verified against the deployed pilot configuration on 2026-08-08; Resend was added on 2026-10-11 after verification against the deployed configuration (transactional email and alert delivery). Only sub-processors genuinely in use are listed.

Sub-processorPurposeData category receivedHosting region
Microsoft AzureCloud hosting: compute (AKS), block/object storage, managed PostgreSQL, and Key Vault (encryption-key custody). All platform infrastructure runs here.All platform data. Detected sensitive values are AES-256-GCM encrypted at rest in the vault; values the detection does not recognise — notably some personal names — can remain in the cloaked text as written.UAE North (uaenorth) — current pilot (synthetic data only). Real customer data will be hosted inside the Kingdom of Saudi Arabia; the in-Kingdom provider is under evaluation (see Section 7).
OpenAIExternal LLM inference (model gpt-4o-mini) for the Send verb.Cloaked text: detected sensitive values are replaced with tokens before sending; values the detection does not recognise — notably some personal names — can reach the provider as written.Per the provider's API terms; OpenAI's default API processing region is the United States. Transfers are subject to Section 7.
ResendTransactional email delivery: account invitations, password reset, and alert emails.Recipient email address and message content.Per the provider's terms.

Not currently engaged (configured-capable but not wired in the deployed pilot as of 2026-08-08; must not be presented as active sub-processors until enabled): Anthropic, Google (Gemini), and Azure OpenAI (alternative LLM providers — no API keys deployed, not in AI_FALLBACK_CHAIN); AWS and STC Cloud (STC Cloud is a planned migration target only); Sentry and PostHog (no error-tracking or analytics tooling is deployed).

Annex B — Technical & organizational measures

Signatures

Controller: ______________________________ Date: ____________

Processor: ______________________________ Date: ____________