Security & access
The public website is open. Operational data is not.
Captrixa is built so that partner data stays behind authenticated, role-checked and tenant-scoped access — and so that no forecast can act on its own.
Architecture
Four boundaries between the internet and your data.
Partner operational data remains tenant-scoped and does not become public network data. Public research data is stored apart from it and never enters a partner tenant.
- Open
Public website
captrixa.com
- Static pages, open to everyone
- No calls to the pilot API
- No partner or pilot data
- Authenticate
Microsoft Entra ID
Your organisation’s account
- Authorization code flow with PKCE
- No shared passwords or links
- Role and tenant assigned by admins
- Authorise
Pilot workspace
captrixa.com/eu/workspace
- Signed-in users only
- Access token checked on every API call
- ANALYST · PLANNER · ADMIN roles
- Isolate
Tenant data
EU cloud region
- Every query scoped to one tenant
- Pseudonymised identifiers
- Append-only, hash-chained audit
Controls
How access and data are protected.
Microsoft Entra ID sign-in
Workspace users sign in with their organisation’s Microsoft account using the authorization code flow with PKCE. There are no shared passwords, public links or client secrets in the browser.
Role-based access
Each user holds exactly one Captrixa role — ANALYST, PLANNER or ADMIN — assigned in Entra ID. Accounts without a role, or without a mapped tenant, are refused.
Tenant isolation
Every query is scoped to the signed-in user’s tenant. Another tenant’s records are not addressable, and pseudonyms differ between tenants for the same identifier.
Protected operational API
The pilot API validates the access token on every request. The public website does not call it and cannot reach partner or pilot data.
Data handling
Shipment, vehicle and release identifiers are replaced by tenant-scoped pseudonyms on intake. Hosted storage is private, encrypted at rest and reachable only by the service’s managed identity. Partner data is transferred only after the agreed data-sharing and data-processing arrangements are in place, where applicable.
Append-only audit trail
Recommendations, decisions and administrative actions are written to an append-only, hash-chained audit log per tenant. Logs never contain tokens or raw identifiers.
Evidence separation
Public research data, modelled output, partner observations and live outcomes are stored and labelled separately. Public data never enters a partner tenant.
Hardened web delivery
The site is served over HTTPS with HSTS, a restrictive Content Security Policy and framing protection. Partner files are never committed to source control.
Human control
No autonomous dispatch.
In pilot scope, Captrixa cannot move a vehicle, book capacity or send an instruction by itself. Forecasts create options; only an authorised planner can approve an action, and that approval is recorded.
Posture
Honest about where we are.
Captrixa is an early-stage company. We do not currently hold ISO 27001 or SOC 2 certification, and we do not claim them. The platform is designed around GDPR principles — data minimisation, pseudonymisation, purpose limitation and tenant isolation — and pilot data processing is agreed with each partner before any data is shared.
Pilot infrastructure runs in a Microsoft Azure region in the EU.
To report a vulnerability or ask a security question, email contact@captrixa.com.
Questions about data handling before a pilot?
We will walk your security and data-protection team through the architecture, access model and data handling before any data is shared.