EDGY
PTENES
← Landing
Sovereignty & LGPD

Sovereignty is not a promise — it is architecture

Every request goes through the sovereign gateway before going anywhere. What stays, stays. What leaves, leaves clean — and is logged.

95.6%
of the flow is sovereign
0
PII fields crossing the border
1:1
audit record per inference

The path of a request

01

Entry at the gateway

Identity and department resolved inside EDGY. Nothing is forwarded before that.

02

PII and secrets filter

Sensitive fields are removed or replaced by internal references.

03

Context and compression

Company context comes in from the sovereign index; the prompt leaves compressed.

04

Anonymous egress and logging

The provider receives an anonymous prompt. EDGY records who asked, what left and what it cost.

Blocked at the border

Fields identified and removed before the request leaves the country. The policy is set per department.

CPF CNPJ CEP email phone biometrics keys and secrets

LGPD Art. 11, operationalized

Sensitive data has an inviolable policy per department: the rule cannot be bypassed by the user or by the team admin. Every attempt is logged.

  • ✓Data orchestrated in Brazil
  • ✓Behavioral audit without storing content
  • ✓Conversations not used to train third-party models
  • ✓On-prem or own-hardware option

Need the technical detail for legal?

We send the architecture diagram, the list of filtered fields and the audit record model.