Data Protection Policy
Last updated: 16 October 2026
Version 1.0, approved by Suleman Siddiqui, Advisor to the CEO, on 16 October 2026.
This policy explains how Sthenos identifies the information we are responsible for, the rules that protect it, how we prevent it from being lost or exposed, and the tools we use. It applies to our own business information and to everything our clients entrust to us. It sits under our Information Security Policy. How we handle personal information collected through this website is covered separately in our Privacy Policy.
1. Identifying the information we hold
This policy requires an inventory of the types of information we hold, where each is stored and who is responsible for it, kept by the Security Officer. For every client engagement it requires a record of what client information we will receive, where it will be kept and when it will be returned or destroyed.
Every piece of information falls into one of four classes:
| Class | What it covers | Examples |
|---|---|---|
| Restricted | Information whose exposure would cause serious harm | Client credentials and keys, security test findings, personal data covered by special rules |
| Confidential | Client information and sensitive company information | Client source code and documents, contracts, pricing, employee records |
| Internal | Everyday business information not meant for the public | Internal procedures, project plans |
| Public | Information approved for release | This website, published capability statements |
If in doubt, we treat information as Confidential. A client’s own classification overrides ours for that client’s information.
2. Rules for handling information
- Need to know. Access to Confidential and Restricted information is limited to the people working on that engagement.
- Approved places only. Client information is kept only in systems the company has approved, or in the client’s own systems when the client asks for that. It is never kept on personal accounts or personal storage.
- Encryption. Confidential and Restricted information is encrypted when stored and when sent over a network. Restricted information is sent only through channels agreed with the client, never as a plain email attachment.
- Minimum necessary. We collect and keep only the information an engagement needs. We do not copy client production data into test environments unless the client agrees in writing, and then only after masking it where possible.
- Subcontractors. A subcontractor may handle client information only under a written agreement with confidentiality and security terms at least as strong as ours, and only with the client’s approval where the contract requires it.
- Retention and destruction. We keep information only as long as the engagement, the contract or the law requires. At the end of an engagement we return or securely destroy client information, as the client chooses, and confirm in writing when asked.
3. Preventing loss and exposure
This policy requires:
- Multi-factor authentication on every system that holds client information, wherever the service supports it.
- Full-disk encryption, screen locks, current updates and malware protection on every device used for Sthenos work.
- Access to be reviewed every quarter and removed on the day it is no longer needed.
- Regular backups of the information we need to operate, with restores tested at least twice a year.
- Security awareness training for everyone when they join and every year, covering phishing and safe handling of client information.
- Secure deletion of data, and wiping of devices before they are reused or disposed of.
4. Tools
We use a company password manager for credentials, encrypted private networking for administrative access, version control with review for code, vulnerability scanning for our systems, and central logging to detect misuse. We choose providers that encrypt data and support multi-factor authentication, and we review the tools we rely on at least once a year.
If something goes wrong
A suspected loss or exposure of information is a security incident and is handled under our Security Incident Response and Reporting policy, including notifying affected clients.
Responsibility and review
The Security Officer owns this policy and reviews it at least once a year. Everyone who works for Sthenos must follow it; breaking it can lead to disciplinary action.
Questions
Email contact@sthenostechnologies.com with “Data protection” in the subject line.