Access Control, Confidentiality and Training Policy

Who can access our systems and client data, how we grant and remove access, how we keep information confidential, how we train staff and how we secure devices.

1. Purpose and scope

This policy explains how Carefully Coded Ltd controls access to information and systems, protects confidentiality, trains the people who handle client data, and secures the devices they use. It applies to:

  • everyone who works for us, including the director, employees and contractors;
  • all company and client systems, accounts, cloud services, code repositories and data;
  • equipment and software we install on client sites;
  • every device used to access client data.

It forms part of our Information Security Policy. Where a client contract sets stricter requirements, the contract takes precedence.

2. Principles

  • Least privilege: people only get the access they need for their current work, and no more.
  • Individual accounts: everyone has their own account. Shared logins are not used for systems holding client data.
  • Separation of admin rights: administrator access uses separate accounts or elevated sessions, not day-to-day accounts.
  • Need to know: client data is only accessed for the purpose of the client's work.

3. Authentication

  • Multi-factor authentication (MFA) is required on all systems holding client data, including cloud hosting, databases, code repositories, email and password managers. We also use MFA everywhere else it is available.
  • Passwords must be unique for each service and at least 12 characters, or generated by a password manager.
  • Passwords are stored only in an approved password manager, never in documents, code or chat messages.
  • Default passwords on any device or service, including hardware we install, are changed before use.
  • Accounts are locked or rate-limited after repeated failed sign-in attempts where the system allows.

4. Joiners, movers and leavers

4.1 Joiners

Before anyone is given access to client data, they must:

  • sign a confidentiality agreement;
  • complete the training in section 6;
  • have their access approved by the director and recorded in the access register.

Where a client requires security vetting or site clearance, for example for work at airports, we complete it before the person starts that work.

4.2 Movers

When someone's role or projects change, the director reviews their access within 5 working days and removes anything no longer needed.

4.3 Leavers

When someone leaves:

  • all access to company and client systems is removed on their last working day, or immediately if they leave without notice;
  • shared secrets they knew, such as API keys and service credentials, are rotated within 5 working days;
  • company devices and any client equipment are returned and securely wiped;
  • the access register is updated and the removal recorded.

5. Access reviews

The director reviews all access to systems holding client data at least every 6 months, and checks that:

  • every account belongs to a current person or a documented service;
  • each person's access still matches their role;
  • MFA is enabled where required.

We record the date, findings and actions. Unneeded access is removed within 5 working days of the review. Client-site access, such as building passes or site credentials, is reviewed with the client as their rules require.

6. Training

Everyone who handles client data must complete data protection and security training:

  • before they first access client data;
  • at least every 12 months after that;
  • after a significant incident or policy change, where relevant.

Training covers, as a minimum:

  • the UK General Data Protection Regulation (UK GDPR) and our Data Protection Policy;
  • recognising and reporting phishing and other social engineering;
  • password, MFA and device security;
  • how to report incidents under our Incident and Data Breach Response Procedure;
  • secure development practices, for those who write code;
  • safe use of AI tools under our AI Use Policy;
  • site security rules, for those working on client premises.

We keep a training record for each person showing the course or material, the date completed and the next due date. The director checks the records at each access review. We use recognised free material as a baseline, such as the NCSC's staff cyber security training and the ICO's data protection guidance, supplemented by client-specific training where a contract requires it.

7. Confidentiality

  • Everyone who works for us signs a confidentiality agreement before accessing client information. The obligation continues after they leave.
  • Contractors and suppliers who access client data must be bound by written confidentiality terms. See our Sub-processors page.
  • Client information is only shared with people who need it for the client's work, and never with other clients.
  • Client data is not used for testing except as allowed by our Test Data Policy.
  • Signed agreements are kept for at least the period of employment or engagement plus 6 years.

8. Device security

Every device used to access client data, whether company-owned or personal, must:

  • have full-disk encryption switched on;
  • lock automatically after no more than 5 minutes of inactivity and require a password, PIN or biometric to unlock;
  • run an operating system that is still supported by its vendor and receives security updates;
  • have automatic security updates switched on, with updates applied within the timescales in our Vulnerability Management, Patching and Secure Development Policy;
  • have its firewall and anti-malware protection switched on;
  • be capable of being remotely locked or wiped if lost or stolen;
  • be recorded in our asset register.

Devices that cannot meet these requirements must not be used to access client data. Lost or stolen devices must be reported straight away as an incident.

Client data must not be copied to removable media, such as USB drives, unless the client has agreed and the media is encrypted. Data is kept and deleted under our Data Retention Policy, and stored in the locations set out in our Data Location Policy.

9. Physical security

  • Devices are not left unattended and unlocked in public places.
  • Screens are positioned or shielded so that client data cannot be overlooked.
  • Hardware held for clients is stored securely before installation.
  • On client sites, staff follow the client's security rules, wear any required identification and only enter authorised areas.

10. Records

We keep the following records and make them available to clients on request:

  • the access register;
  • access review results;
  • signed confidentiality agreements (confirmation of signature, not personal details, unless the contract requires more);
  • training records;
  • joiner and leaver checklists.
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.