Security & trust
What is and is not certified, how content is handled, and what you can verify yourself.
Request and response content is not retained by default. An organization sets a retention ceiling that its projects can only tighten, and can require zero-retention endpoints outright. Metadata (route, usage, charge) is kept as billing and route evidence.
BYOK provider keys are encrypted at rest, scoped to the org, never logged, and their use is recorded as the credential source on every attempt.
Every route is authorized server-side against the organization on the request. Staff elevation into a tenant is just-in-time: at most four hours, approved by a second person, revocable, expired by a job the moment its clock runs out, and recorded in the platform audit log with the reason given.
[email protected] for coordinated disclosure. Reports are acknowledged and tracked as incidents with per-component communication; no bounty programme is claimed.
No audit report, certification or BAA is claimed today. What can be obtained is listed here as the registry records it.
The processing region is a hard routing constraint enforced per request — a control, not a residency certification; no residency claim is made.