Role-based access
Five roles (administrator, risk manager, analyst, requester and viewer) decide who can see and change what. API keys are scoped by role in the same way.
Trust and security
This page lists only what is true of the product now. Items in square brackets are still being finalised and will be published here; we will not describe them until they are.
Five roles (administrator, risk manager, analyst, requester and viewer) decide who can see and change what. API keys are scoped by role in the same way.
Decisions and changes are logged with who made them and when. The audit trail exports to CSV or JSON with the other registers.
When you connect your own AI provider, its key is encrypted with AES-256-GCM.
Personal data is removed before any request goes to an AI model. AI outputs are labelled and kept in a usage log, and a person makes the decision.
See how the AI is governedNexaPair can be deployed in a cloud region inside the UAE, so your records can stay in the country.
Each webhook carries an HMAC-SHA256 signature with a timestamp, so your systems can reject anything that was not sent by NexaPair.
See the verification codeWe will publish these here. Until then, ask us and we will answer in writing.
| Item | Status |
|---|---|
| Certifications | [CERTIFICATION STATUS] |
| Hosting provider and region | [HOSTING PROVIDER] |
| Encryption at rest and in transit | [ENCRYPTION AT REST AND IN TRANSIT DETAILS] |
| Latest independent penetration test | [PEN-TEST DATE] · [PEN-TEST FIRM] |
| Sub-processors | [SUB-PROCESSOR LIST] |
| Data processing agreement | [DPA TEMPLATE] |
| Data retention and deletion | [DATA RETENTION POLICY] |
We will complete your security questionnaire. Write to us at
[SECURITY CONTACT]