1. Purpose and scope
This policy sets out how long Carefully Coded Ltd ("we", "us") keeps information, and how we delete it securely when it is no longer needed. It supports the storage limitation principle in the UK General Data Protection Regulation (UK GDPR).
It applies to all information we hold, in any format, including:
- our own business records, where we are the controller;
- client data we hold as a processor, including data in systems we host, on devices we install and in project files.
It applies to everyone who works for us, including staff and contractors.
2. Responsibilities
The data protection lead, Tom Emmerson, Director, owns this policy and the retention schedule, approves legal holds and signs deletion certificates. Staff and contractors must not keep information longer than this policy allows, and must not delete information under a legal hold.
3. Client data
Where we act as a processor, the client decides how long its data is kept. We follow the retention periods in the client contract and the client's written instructions.
At the end of a contract, we will return or delete client data, as the client chooses. Unless the contract says otherwise, we will complete this within 30 days of the contract ending, and confirm it in writing. Copies held in backups are removed as those backups age out (see section 6).
Where a client contract sets stricter terms or shorter timescales than this policy, the contract takes precedence.
4. Retention schedule
Retention periods start from the trigger shown. At the end of the period we delete the information, or anonymise it so that no one can be identified.
| Information | Retention period | Trigger | Reason |
|---|---|---|---|
| Client data held as a processor | As set by the client contract; returned or deleted within 30 days unless the contract says otherwise | End of contract or client instruction | Client is the controller |
| Production data copied for testing (with approval) | Deleted as soon as the approved task is complete | End of task | Test data policy |
| Contracts, proposals and project records | 6 years | End of contract | Limitation period for contract claims |
| Financial and accounting records | 6 years | End of the financial year they relate to | Companies Act 2006 and HMRC requirements |
| Complaint records | 6 years | Closure of the complaint | Evidence and service improvement |
| Security incident and data breach records | 6 years | Closure of the incident | Accountability and lessons learned |
| Data subject request log and responses | 6 years | Closure of the request | Accountability |
| Staff and contractor records | 6 years | End of employment or engagement | Legal claims and statutory requirements |
| Payroll and tax records | 6 years | End of the tax year they relate to | HMRC requirements |
| Unsuccessful job applications | 6 months | Applicant told of the outcome | Defending recruitment decisions |
| Website and business enquiries that do not lead to work | 2 years | Last contact | Follow-up on genuine interest |
| Client and supplier contact details | 6 years | End of the business relationship | Contract management |
| Training records | 6 years | End of employment or engagement | Evidence of compliance |
| Deletion certificates | 6 years | Date of issue | Evidence of deletion |
| Backups | Overwritten within 35 days | Date of backup | See section 6 |
If information is not listed, the data protection lead will decide a retention period, record it and add it to this schedule.
5. Legal holds
If we become aware of actual or likely legal proceedings, a regulatory investigation, an audit or a formal request for information that relates to information we hold, the data protection lead will place a legal hold on it.
While a legal hold is in place:
- we suspend deletion of the affected information, including scheduled and automated deletion where it can be paused;
- we record the hold, what it covers, why it was applied and the date;
- where the information is client data, we tell the client unless the law prevents us.
When the hold is lifted, we record the date and resume normal deletion.
6. Secure deletion methods
We use deletion methods that make information unrecoverable in practice.
6.1 Cloud systems and databases
We delete records using the application or platform's own deletion functions, then remove any related files, exports and logs that contain the data. Where a whole environment is no longer needed, we delete the storage, databases and keys. Where data is encrypted, we also destroy the encryption keys where the platform allows this.
6.2 Backups
We do not edit individual records out of backups. Instead, backups follow a fixed rotation, and every backup is deleted or overwritten within 35 days of being created. Deleted data therefore leaves all backups within that cycle. If data is restored from a backup, we reapply any deletions made since the backup was taken before the system goes back into use.
6.3 Laptops, phones and storage media
All our devices use full-disk encryption. Before a device is reused, returned, sold or recycled, we perform a factory reset that erases the encryption keys, or use the manufacturer's secure erase function. Storage that cannot be securely erased, or that has failed, is physically destroyed. We record the device, the method and the date.
6.4 Installed equipment
For equipment we install on client sites, such as displays, sensor stations or airport equipment, we securely erase any client data stored on the device before it is removed, replaced or returned, using the methods in 6.3. If the client wants to keep and destroy the storage itself, we record this.
6.5 Paper
We keep as little on paper as possible. Paper containing personal or confidential information is shredded with a cross-cut shredder, or destroyed by a professional confidential waste service that issues a certificate of destruction.
7. Deletion certificates
On request, we will give a client a written deletion certificate confirming:
- what data was deleted or returned;
- the systems and devices it was deleted from;
- the deletion method used;
- the date deletion was completed, and the date by which any backup copies will have aged out;
- the name and signature of the person confirming it.
We provide the certificate within 10 working days of the request, or of completing deletion if later, unless the contract sets a shorter period. We keep a copy for 6 years.
8. Reviews
The data protection lead reviews the information we hold against this schedule at least once a year and arranges deletion of anything past its retention period. We keep a short record of each review.
We review this policy at least once a year. Related policies: Data protection policy, Information security policy and Business continuity policy.