Security
Built to clear your risk team.
What the platform does, where the data lives, and how one organization can't see another. No adjectives.
Where data lives
Our own infrastructure in Brazil
This isn't an architecture preference. It's the difference between notifying the regulator of a contract and asking it for permission.
Service in Brazil · art. 15
10 days
to notify, after signing
You sign, go live, and notify the Central Bank of Brazil (BACEN) within ten days. The project timeline is yours.
Service abroad · art. 16
60 days
of prior authorization, before signing
Without an agreement between supervisors, the contract depends on an authorization requested sixty days in advance — and the project waits for the answer.
Isolation
Each organization in its own space
Isolation is checked on the path of every request, not by naming convention.
- Organization
- Policies, pipelines, sources and decisions belong to an organization, and a request only sees its own.
- Files and queues
- File and queue sources only read inside your organization's space.
- HTTP calls
- HTTP sources are protected against internal addresses: the pipeline can't reach the platform's network.
- In transit
- TLS on every call, and the site answers with HSTS.
Access
Test and production don't mix
- A key per environment
- Test and production use different credentials, each with an expiry. The test key can't see real data, not even by mistake.
- Idempotency
- The same call repeated with the same key within 24 hours doesn't create a second decision.
- Purpose
- Every bureau lookup of personal data carries its declared purpose, recorded with the lookup.
Keep going