Data processing

Candidate data handling should be explicit before the pilot starts.

CVault data-processing content separates candidate files, parser output, retention expectations, deletion paths, and customer-controlled deployment terms.

What candidate data is processed, retained, deleted, or controlled by the customer?

Data lifecycle
1Upload

permitted files

2Process

scoped workflow

3Retain

scoped workflow

4Delete/export

customer request

Processing areas

Access scope

Candidate data is handled inside workspace-scoped review workflows.

Retention expectations

Pilot retention and deletion should be agreed before files are shared.

Customer controls

Deployment terms, DPA support, and subprocessors depend on reviewed customer setup.

Decision areaCVaultGeneric parsing
Pilot dataScoped to one reviewed pilot workflow.Broad upload without lifecycle clarity.
DeletionDiscussed as part of the pilot terms.Hidden in vague privacy copy.
Compliance languageNo unsupported badges or blanket guarantees.Overbroad trust claims.

Reviewed rollout

Set data expectations before sharing files.

Use one controlled room to confirm access, retention, and deletion terms.

Review access options