Data Retention Policy

Retention schedule and criteria

The following reflects the current product design; the production operator must configure and verify deletion jobs before launch.

• Candidate assessment records: 365 days where the disclosed candidate-consent version applies, unless the inviting organization lawfully configures a shorter period or a documented legal hold applies.
• Public and consumer results and certificates: while needed to deliver verification, account history, disputes, or the contract; reviewed at least annually and deleted or anonymized when no longer necessary.
• Incomplete sessions and expired invitations: until operational cleanup confirms expiry and releases reserved resources.
• Payment, invoice, refund, and tax records: for the period required by applicable accounting, tax, anti-fraud, and legal-claims law.
• Consent, security, support, and audit records: only as long as needed to demonstrate compliance, protect the service, resolve disputes, or meet law.

Deletion, anonymization, and legal holds

A deletion request removes linked external identities and direct identifiers where possible. Referentially necessary assessment or financial records may be pseudonymized instead of erased when retention has a valid legal basis.

A documented legal hold can pause deletion for a specific dispute or obligation. Holds require restricted authorization, a reason, audit recording, review, and release when no longer necessary.

Backups and processors

Deleted data may remain temporarily in protected backups until normal rotation, without being restored except for disaster recovery. Any restored data must be re-subjected to deletion controls.

Processors must delete or return data at the end of service subject to lawful retention and contract terms. Contact privacy@iqlabtest.com for an access, deletion, or retention question.