Developer Docs Request Demo
Request Demo

Subprocessors & Compliance

The regulatory frameworks Traffelo AI is architected against, the edge processing guarantees behind them, and how to obtain the current subprocessor register.

Version: 2.0 (Enterprise) Effective: September 1, 2026

Key highlights

Sub-5ms WASM Edge PII Scrubbing

Quantized WASM/ONNX models detect, mask and tokenize PII at your sovereign edge node before any payload leaves it.

Privacy 2.1
Zero Public Model Training

Client datasets, prompts and output payloads are never stored, monetized, or used to train public foundation models.

Privacy 2.2
4 regions Sovereign Residency

EU/UK, Türkiye, GCC and S.E. Asia — SCCs, the UK IDTA, KVKK Article 9, and in-region storage options.

Privacy 5.1
18+ Enterprise B2B Only

Web properties and evaluation tools are for commercial entities. No data is knowingly collected from anyone under eighteen.

Privacy 1.2 · Terms 1.3
This page summarises the document in plain language. The full binding text is linked below, and the English text governs.

1Frameworks we operate under

The binding obligations are set out in Privacy 1.1. The platform and its corporate interfaces are architected against the GDPR and UK Data Protection Act 2018, KVKK, the UAE and Qatar PDPLs, and the Singapore and Malaysia PDPAs, each with its own transfer mechanism.

Clause: Compliance 1

2What the edge architecture guarantees

Reproduced from Privacy 2.1 and 2.2: quantized WASM/ONNX models detect, mask and tokenize PII locally before transmission; in-flight buffers are cleared post-execution; and client data is never used to train public foundation models. Published performance figures, sub-5ms included, are modeled projections rather than an SLA.

Clause: Compliance 2

3Subprocessor register

Vetted third-party providers support website hosting, security logging and transactional communications, all contractually bound to equivalent standards and barred from independent processing. The current register is available on request and is deliberately not reproduced on this page.

Clause: Compliance 3

4Certifications and disclosure

Enquiries about SOC 2 Type II controls and ISO/IEC frameworks, and reports of a technical vulnerability, go to the security contact. Security research outside the Coordinated Vulnerability Disclosure policy is not authorized.

Clause: Compliance 4

Read or download the full document

The complete, binding text — free, with no form to fill in. Open it in the browser, or save it as a PDF from your print dialog.