Test Data Policy

We use synthetic or anonymised data to develop and test systems. Real production data is used only with the client's written approval, kept to a minimum and deleted afterwards.

1. Purpose and scope

This policy sets out what data Carefully Coded Ltd ("we", "us") may use when developing, testing, demonstrating and training on the systems we build. It reduces the risk of real personal data being exposed in environments that are less tightly controlled than production.

It applies to all development, test, staging, demonstration and training environments, including local copies on laptops, and to software for installed hardware. It applies to everyone who works for us, including staff and contractors.

Where a client contract sets stricter terms than this policy, the contract takes precedence.

2. Responsibilities

The data protection lead, Tom Emmerson, Director, approves any request to use production data outside production and keeps the records described below. Every engineer is responsible for using the right data in the right environment.

3. Definitions

  • Production data: real data from a live system, or supplied by a client, that relates to real people or real operations.
  • Synthetic data: data we create that looks realistic but does not relate to any real person.
  • Anonymised data: data derived from production data that has been processed so that no individual can be identified, by us or anyone else, using means reasonably likely to be used. Pseudonymised data, where people can still be re-identified, is not anonymised and is treated as production data.

4. Default: synthetic or anonymised data

By default, all non-production environments use synthetic data or anonymised data only. We will:

  • create synthetic data sets and fixtures as part of each project;
  • use clearly fictional names, addresses and contact details, and reserved test values such as example domains and test card numbers;
  • not use real email addresses or phone numbers that could cause messages to reach real people;
  • where we anonymise production data, do so within the production environment before anything is copied out, and check the result before use.

5. Using production data

Sometimes a problem can only be investigated with real data. In that case, production data may be used outside production only when all of the following apply.

5.1 Written client approval

The client has given written approval in advance. The request will state:

  • the purpose, such as diagnosing a specific fault;
  • exactly which data is needed;
  • where it will be held and who will access it;
  • how long it will be kept, and how it will be deleted.

5.2 Minimised

We copy only the records and fields needed for the task. Where possible, we investigate within the production environment instead of copying data out.

5.3 Protected to production standard

The data is stored in the UK only, on encrypted systems and devices that meet our access control policy, and protected to the same standard as production, in line with our Data location and remote access policy and Access control policy. It must not be shared with anyone outside the approved list, put into artificial intelligence tools (see our AI use policy), or used for any other purpose.

5.4 Deleted afterwards

The data is securely deleted as soon as the task is complete, or by the end of the approved period if sooner. Deletion covers every copy, including local copies, exports and logs. We confirm deletion to the client in writing, and provide a deletion certificate on request under our Data retention and secure deletion policy.

6. Records

The data protection lead keeps a record of each use of production data outside production, including the client approval, the data used, who accessed it, and the date of deletion. We keep these records for 6 years.

7. Breaches of this policy

If production data is found in a non-production environment without approval, it must be reported to the data protection lead immediately. We will delete it, investigate how it got there, and treat it as a security incident under our Incident response procedure, telling the client where their data is involved.

8. Review

We review this policy at least once a year. Related policies: Data protection policy and Information security policy.

Organisation
Carefully Coded Ltd
Version
1.0
Owner
Tom Emmerson, Director
Effective from
19 November 2026
Next review
19 November 2027

Questions about this policy? Email info@carefully.codes.