Security

The controls below describe the security measures currently implemented by the platform. No certification is claimed unless DijiPeople states one separately in writing.

What is implemented

Tenant isolation. Every query against tenant-owned data is scoped by the tenant on the authenticated session. The tenant is never taken from a request body, query string or header. Cross-tenant access is exercised by a dedicated database-backed test suite that attempts to reach one tenant's records with another tenant's session.

Authentication. Per-client JWTs — the tenant product, the platform admin and the desktop agent each have their own signing secret and audience. A token issued for one cannot be used against another. Sessions are verified against a live session record on every request, so revocation takes effect immediately.

Authorization. Two permission systems are enforced together, and a route requires both. Row-level scope is applied separately, so holding a permission does not grant access to every record of that type.

Encryption in transit. HTTPS.

Integration credentials at rest. Third-party credentials are encrypted with a dedicated key. In production the platform refuses to start without that key rather than storing them in plaintext.

Audit. State-changing operations record before and after snapshots.

Erasure. Tenant erasure is executed as an explicit, ordered sequence rather than a cascade, and the order is re-derived from the schema by an automated check so it cannot drift.

What is NOT claimed

• No SOC 2, ISO 27001, HIPAA, PCI or GDPR certification. None has been obtained.
• No uptime or availability SLA.
• No 24/7 support commitment.
• No data-residency guarantee. A hosting region can be recorded per workspace,

but no promise is made about where data is stored until the infrastructure supports one.

• No claim about encryption at rest beyond what the hosting and database

providers offer by default; see the Subprocessors page for who they are.

Reporting a vulnerability

Report suspected vulnerabilities to the security contact on the website. Please do not test against another customer's workspace.