Security & Compliance — GDPR, DPDP, SOC 2-Ready | ArexisSkip to content

Security & compliance

Built for the day someone asks “why?”

Isolation, fairness and accountability as properties of the system — not promises in a policy.

Compliance posture

In the product

Properties of the system, not promises in a policy.

  1. 01

    Tenant isolation

    Every row carries your organisation’s id; every query is scoped to it. One workspace can never read another’s candidates.

  2. 02

    Encryption

    TLS end to end. Settings and tokens encrypted at rest.

  3. 03

    Sign-in

    Google and Microsoft SSO, or email and password with policy controls. Neither path can lock the other out.

  4. 04

    The operator console

    TOTP multi-factor, backup codes, IP allowlist, password expiry, session limits. Every action audited.

  5. 05

    Fair AI by construction

    Anonymised before scoring. No inference on protected traits or emotion. Provenance on every score.

  6. 06

    Candidate-side safety

    Single-purpose expiring links. Proctoring in the browser; no audio transcript is kept beyond a few words at a flagged moment.

Data handling

Where your data lives, and doesn’t.

Where video happens
In your own Microsoft 365 or Google Workspace. Recordings are fetched only with admin consent.
What we store
Parsed résumé data, scores with provenance, transcripts you keep, pipeline history — all scoped to you.
What we don’t
Card details, raw proctoring video, or any inference about a candidate’s emotional state.

Procurement asking questions?

The current security questionnaire and data-processing terms, by return mail.