Retention

Data retention and deletion readiness

Pilot-facing retention overview for candidate, recruiter, and workspace data. Final retention periods must be aligned with the client, founder, and counsel before launch.

Retention schedule pending

[PLACEHOLDER: approved retention periods for CVs, applications, recruiter notes, audit logs, backups, support tickets, and analytics].

Deletion path

Candidates and client administrators can request deletion through the contact path. Some records may need to be retained where legally required or needed for auditability.

Candidate and CV data

HanteR may store CV/resume files, parsed resume text, extracted contact details, job applications, recruiter notes, shortlisting explanations, and workflow status for the duration agreed with the recruiting client.

AI-assisted outputs

AI-assisted summaries, fit explanations, and shortlist support may be stored so recruiters can review, challenge, and audit the basis for workflow decisions. These outputs remain support material, not final autonomous decisions.

Deletion and correction requests

Candidates may request deletion or correction through the contact path or through the recruiting organization.
Client administrators may request deletion for pilot workspaces, jobs, candidates, and files subject to agreed legal and operational constraints.
Deletion from backups, logs, and audit records may follow a separate approved schedule that must be documented in the client onboarding pack.

Pilot defaults

Until the approved retention schedule is finalized, HanteR should use conservative, client-agreed retention settings and avoid retaining candidate data longer than needed for the pilot purpose.