Data Protection Policy

How we handle personal data lawfully and securely, both as a controller for our own business and as a processor acting on our clients' instructions.

1. Purpose and scope

This policy sets out how Carefully Coded Ltd ("we", "us") complies with the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018 (DPA 2018).

It applies to all personal data we handle, in any format, and to everyone who works for us, including staff and contractors. It covers the systems we build, host, install and support for clients, including software for custom hardware and equipment installed on client sites.

2. Responsibilities

Role Responsibility
Data protection lead: Tom Emmerson, Director Owns this policy, keeps the records described here, handles data protection queries, leads on breaches and is the contact point for clients and the Information Commissioner's Office (ICO).
Staff and contractors Follow this policy and related policies, complete training, and report suspected breaches immediately.

Contact the data protection lead at tom@carefully.codes.

We are registered with the ICO as a data controller. Our registration number is ZB512909. We renew the registration each year.

3. Our roles: controller and processor

As a controller, we decide why and how personal data is used. This covers our own business data: staff and contractor records, client and supplier contacts, website enquiries and job applications. Our Privacy notice explains this processing.

As a processor, we handle personal data on behalf of a client, such as a council or other public authority ("the Authority"). The client is the controller. This covers data in platforms, apps and devices we build, host or support for them.

Where we act as a processor we will:

  • process personal data only on the client's documented instructions, as set out in the contract and any written instructions issued under it;
  • tell the client promptly if we believe an instruction breaks data protection law;
  • not use client data for our own purposes;
  • make sure everyone with access is bound by confidentiality;
  • assist the client with security, breach notification, data protection impact assessments and data subject requests;
  • delete or return all personal data at the end of the contract, as the client chooses, and confirm this in writing;
  • make available the information the client needs to show compliance, and allow and contribute to audits.

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

4. Data protection principles

We will make sure personal data is:

  1. processed lawfully, fairly and transparently;
  2. collected for specified, explicit and legitimate purposes, and not used in ways incompatible with them;
  3. adequate, relevant and limited to what is necessary (data minimisation);
  4. accurate and, where necessary, kept up to date;
  5. kept no longer than necessary (see our Data retention and secure deletion policy);
  6. kept secure, using appropriate technical and organisational measures.

We are responsible for, and must be able to show, compliance with these principles (accountability).

5. Lawful basis

As a controller, we identify and record a lawful basis under Article 6 UK GDPR before we process personal data. The bases we usually rely on are contract, legal obligation, legitimate interests and, for website analytics and marketing cookies, consent.

We do not normally process special category or criminal offence data as a controller. If we need to, for example for staff health information, we will identify an Article 9 condition and any DPA 2018 Schedule 1 condition, and record it before processing starts.

As a processor, the lawful basis is the client's responsibility. We process only as instructed.

6. Privacy by design and data protection impact assessments

We build data protection into the systems we design from the start. By default we collect the minimum data needed, restrict access, encrypt data in transit and at rest, and use synthetic data for testing (see our Test data policy).

We will carry out a data protection impact assessment (DPIA) before any of our own processing that is likely to result in a high risk to individuals. For client projects, we will provide the information the client needs to complete its own DPIA, including a description of the system, data flows, security measures and sub-processors. We will review a DPIA when the system or processing changes significantly.

7. Records of processing

The data protection lead keeps a record of processing activities, as required by Article 30 UK GDPR:

  • as a controller: purposes, categories of data and data subjects, recipients, retention periods and security measures;
  • as a processor: each client we act for, the categories of processing, any sub-processors, and security measures.

We review the record at least once a year and whenever we start a new client project or a new type of processing.

8. Security

We protect personal data in line with our Information security policy and Access control policy. Access is granted on a least-privilege basis and removed promptly when no longer needed. We manage vulnerabilities under our Vulnerability management policy and plan for disruption under our Business continuity policy.

9. Data location and international transfers

We store and process client data in the UK only, including backups, and we do not transfer it outside the UK. Administrative access from outside the UK needs the client's prior written approval. See our Data location and remote access policy.

For our own business data, if a service provider processes personal data outside the UK, we will only use it where the transfer is covered by UK adequacy regulations or an appropriate safeguard, such as the International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses.

10. Sub-processors

We only use sub-processors with the client's authorisation, under a written contract that flows down the Article 28 terms, and after due diligence. We give clients 30 days' notice of any change. See our Sub-processor management policy.

11. Personal data breaches

Anyone who suspects a personal data breach must report it to the data protection lead immediately. We follow our Incident response procedure.

  • As a processor, we will notify the client without undue delay after becoming aware of a breach affecting its data, or within any shorter period set in the contract, and give them the information they need to meet their own obligations.
  • As a controller, we will report a notifiable breach to the ICO within 72 hours of becoming aware of it, and tell affected individuals without undue delay where the breach is likely to result in a high risk to them.

We record every breach and suspected breach, including the facts, effects and action taken, whether or not it is reported.

12. Data subject rights

We respect the rights of individuals to be informed, and to access, rectify, erase, restrict, port and object to the processing of their data. We follow our Data subject rights procedure. As a processor, we pass requests to the client and help them respond.

13. Retention and deletion

We keep personal data only as long as our retention schedule or the client contract allows, then delete it securely. See our Data retention and secure deletion policy.

14. Artificial intelligence

We never use client data to train artificial intelligence (AI) models. See our AI use policy.

15. Training and awareness

Everyone who works for us completes data protection training before they are given access to personal data, and refresher training at least once a year. We keep a record of who completed what training, and when. Staff working on a client contract also follow any client-specific training or vetting requirements.

16. Raising concerns

Anyone can raise a data protection concern with the data protection lead. Staff can also use our Whistleblowing policy.

17. Review

We review this policy at least once a year, and sooner if the law, our services or our client contracts change.

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.