Data retention

Draft: not legal advice, pending review by counsel. This page is a working draft, not a published retention schedule. Placeholders in square brackets must be replaced and the whole document reviewed by qualified counsel before launch.

1. Purpose

This schedule describes how long boson intends to keep each category of data. The periods below are placeholders. They must be agreed with the business, confirmed against customer contracts and reviewed by counsel before launch.

2. Retention schedule

Data category	Intended retention period	Notes
Company and user account records	[retention period]	Kept while the account is active and for a short period after closure for security and legal reasons.
Jobs, pipelines, forms and rubrics	[retention period]	Recruiter-owned content. Deleted or returned according to the customer agreement.
Candidate applications and answers	[retention period]	Includes questionnaire and assessment responses.
Interview recordings	[retention period]	Deleted by the recording-retention workflow after the configured period.
Grading records, evidence and audit events	[retention period]	Kept to explain decisions and support audits and disputes.
Code submissions and sandbox output	[retention period]	Held in the isolated sandbox and its database.
Service and security logs	[retention period]	Capped at the infrastructure level.
Backups	[retention period]	Rotated on the backup schedule.
Billing and tax records	[retention period]	Kept as required by tax and accounting law.

[Confirm every period with the owner and counsel. Do not publish this table with placeholder values.]

3. Recording retention

The repository includes a scheduled recording-retention workflow. It is designed to identify recordings past their retention date and delete them. The workflow exists, but the final retention periods and the production schedule are still to be confirmed.

[Confirm the production schedule, the default period, any per-company override, and how deletion failures are retried.]

4. Deletion requests

Candidates and customers can ask for data to be deleted. Requests are handled under the privacy policy and the candidate data notice. Some records may be kept where the law, a contract or a security investigation requires it.

[Confirm the deletion process, response period and any legal-hold exceptions.]

5. Backups and residual copies

Deleted data may remain in backups until the backup rotation completes. Backups are not used to restore individual records except during a recovery operation.

[Confirm backup rotation and whether a restore could reintroduce deleted data.]

6. Changes

We will update this schedule when retention periods change or when a new data category is added. The effective date will be added before launch.

7. Contact

Questions about retention: [privacy contact email].

This draft is not legal advice.