1. Purpose and scope
This policy sets out where Carefully Coded Ltd ("we", "us") stores and processes client data, and the rules for accessing it remotely.
"Client data" means any data we hold or can access on behalf of a client, including personal data, in:
- systems and platforms we host or manage;
- databases, backups, logs and file storage;
- devices and equipment we install or support, such as displays, sensor stations or airport equipment;
- copies on our own laptops, phones and project storage.
It applies to everyone who works for us, including staff and contractors, and to our sub-processors.
Where a client contract sets stricter terms than this policy, the contract takes precedence.
2. Responsibilities
The data protection lead, Tom Emmerson, Director, is responsible for this policy, for approving system designs against it, and for keeping the records it requires. Every member of staff and every contractor is responsible for following it.
3. UK-only storage and processing
All client data is stored and processed in the UK only. This includes:
- primary storage and databases;
- backups and replicas, including disaster recovery copies;
- logs, monitoring data and error reports that contain client data;
- temporary copies, exports and test copies.
Our primary hosting is a UK region of a major cloud provider, agreed with each client in the contract. When we design or configure a system for a client, we:
- choose UK regions for every service that stores or processes client data;
- check that backup, replication and failover settings keep data in the UK;
- check that monitoring, logging and error-reporting tools do not send client data outside the UK;
- record the location of each component in the project documentation.
We only use sub-processors that can keep client data in the UK (see our Sub-processor management policy).
We do not transfer client data outside the UK. If a client asks us to, we will only do so with their prior written instruction, and with a lawful transfer mechanism in place.
4. Remote access from outside the UK
Nobody may access client systems or client data from outside the UK unless the client has given prior written approval. This includes:
- administrative access to servers, cloud consoles, databases and installed devices;
- remote support sessions;
- access to client data on laptops or phones;
- staff and contractors who are travelling or working abroad, even briefly.
4.1 Requesting approval
If someone needs access while outside the UK, the data protection lead will ask the client in writing before travel or before access, stating who needs access, why, from which country, for what dates, and what security measures will be used. Access may only go ahead once written approval is received, and only within its terms.
4.2 When travelling without approval
Staff and contractors travelling outside the UK without approval must:
- tell the data protection lead before they travel;
- not access client systems or data while abroad;
- where practical, have their client access suspended for the period of travel and restored on return.
If urgent support is needed while a team member is abroad, another team member in the UK will provide it. If no one in the UK is available, we will tell the client and agree a way forward with them. Our Business continuity policy covers cover arrangements.
5. Remote access within the UK
Remote access within the UK must follow our Access control policy and Information security policy. In particular, it must use:
- devices that meet the device rules in our access control policy, including full-disk encryption and up-to-date software;
- individual accounts with multi-factor authentication;
- encrypted connections;
- the minimum access needed for the task.
Staff must not access client data over untrusted public networks without an encrypted connection, or from personal or shared devices.
6. Records
The data protection lead keeps:
- the location of each client system and its components, in the project documentation;
- every request for, and approval of, access from outside the UK;
- a record of travel notifications and any access suspended and restored.
We keep these records for 6 years, in line with our Data retention and secure deletion policy.
7. Breaches of this policy
Any access from outside the UK without approval, or any client data found stored outside the UK, must be reported to the data protection lead immediately. We treat it as a security incident under our Incident response procedure and tell the affected client.
8. Review
We review this policy at least once a year, and whenever we change hosting provider or region.