Security, described by the implementation.

A closer look at specific TalentVault mechanisms for organisation boundaries, AI actions, files, sign-in, and infrastructure.

Organisation data isolation

What it is

Candidate and other business records are scoped to an organisation at the database layer.

How it is done

PostgreSQL row-level security is enabled on the business tables. Their policies use the row’s organisation ID and the signed-in user’s organisation membership to govern reads and writes.

Consultant control over Hisi changes

What it is

Hisi presents proposed data changes and external actions for consultant review before execution by default.

How it is done

The runtime creates a pending action with a preview and payload hash. A confirmed action is checked again before execution. Explicit direct-authorization rules and consultant-configured standing rules can permit defined actions without a new confirmation each time.

Records of AI activity

What it is

Hisi tool calls have step records, and data-changing actions have a separate action history and execution audit event.

How it is done

The runtime records each tool step. Proposed and completed changes are stored as action records; execution adds an audit event identifying the actor, run, tool, and affected object references.

Private documents and expiring downloads

What it is

Candidate documents are stored in a private bucket rather than at permanent public URLs.

How it is done

Storage policies restrict access by organisation membership. Downloads use a signed URL generated through the signed-in user’s storage access, with a 60-second expiry.

Email code sign-in

What it is

The standard sign-in flow verifies control of the user’s email address with a one-time code.

How it is done

TalentVault sends a six-digit code and verifies it before establishing the signed-in session. Codes expire after 10 minutes, and attempts are rate-limited.

Storage locations

What it is

TalentVault’s application runtime, primary database, authentication, and primary document storage are in Singapore.

How it is done

The database, authentication, and storage use Singapore (AWS ap-southeast-1). Resume originals also have a second copy in Western North America. Subprocessors may process data in other locations.

Subprocessors

What it is

TalentVault uses external providers for infrastructure, email delivery, and AI processing.

How it is done

The product privacy notice lists infrastructure categories and AI providers, their purposes, and processing regions.

View the TalentVault subprocessor list