Security & TOMs
The technical and organisational measures Helu applies to protect personal data.
Overview
Helu applies technical and organisational measures pursuant to Article 32 GDPR designed to protect personal data and ensure the confidentiality, integrity, availability and resilience of the systems used to provide our services. Our security controls are reviewed and further developed in line with the state of the art, the nature and scope of processing, and the risks to the rights and freedoms of data subjects.
Last updated: 17 November 2026
Measures in Detail
1. Physical Access Control
Measures designed to prevent unauthorised persons from gaining physical access to systems and infrastructure used to process personal data.
- Hosting infrastructure is operated in professional data centres with controlled physical access.
- Physical access is limited to authorised personnel and managed by the relevant hosting provider.
- Access to facilities is protected through appropriate authentication and access-control mechanisms, such as access cards, security keys or equivalent controls.
- Authorised-person lists and access permissions are subject to approval and review procedures.
- Visitors and third-party access are subject to appropriate controls where applicable.
2. System Access Control
Measures designed to prevent unauthorised use of systems that process personal data.
- Access to systems is granted through individual user accounts and is limited according to role and business need.
- Authentication mechanisms and password requirements are applied in accordance with internal security policies.
- Access sessions are protected through appropriate timeout, lockout or equivalent safeguards where technically applicable.
- Administrative and privileged access is restricted to authorised personnel.
- Access rights are reviewed periodically and adjusted or revoked when no longer required.
3. Data Access Control
Measures designed to ensure that authorised users can access only the data required for their role and that personal data cannot be read, copied, modified or deleted without authorisation.
- Role-based and need-to-know access principles are applied.
- Access rights are subject to approval processes and periodic review.
- Production access is restricted and granted only where operationally necessary.
- Personnel with access to personal data are subject to confidentiality obligations.
- Access to customer data is limited to the extent necessary for service delivery, support, maintenance and security.
4. Transmission and Encryption Control
Measures designed to protect personal data during electronic transmission and to provide traceability of relevant data transfers.
- Personal data is transmitted using encrypted transport protocols such as HTTPS/TLS and secure administrative channels.
- Encryption mechanisms are selected based on the state of the art and the relevant risk profile.
- Sensitive administrative access is restricted to secure channels.
- Relevant transmission and system events are logged where appropriate.
- External data transfers are limited to authorised recipients and approved processing purposes.
5. Input and Change Control
Measures designed to make it possible to determine whether and by whom personal data has been entered, changed or removed from processing systems.
- User actions and system events are logged where technically and operationally appropriate.
- Access rights are assigned based on role and need-to-know principles.
- Changes to systems and access permissions follow approval and change-management procedures.
- Administrative actions can be reviewed through available audit and application logs.
- Development, deployment and production changes are subject to controlled release processes.
6. Processor and Vendor Control
Measures designed to ensure that personal data is processed only in accordance with documented instructions and that service providers are selected and monitored appropriately.
- Sub-processors and other relevant service providers are subject to due-diligence and approval procedures.
- Privacy, security, contractual terms, certifications and other relevant assurances are considered during vendor selection.
- Sub-processors processing personal data are contractually bound to appropriate data-protection and confidentiality obligations.
- Helu maintains a current list of relevant sub-processors and applies the contractual notification process defined in the DPA.
- Responsibilities and documented instructions are defined and maintained through standardised internal procedures.
7. Availability and Resilience Control
Measures designed to protect personal data against accidental destruction or loss and to support the availability and resilience of processing systems.
- Regular backup procedures are implemented for relevant production data.
- Recovery procedures are tested on a recurring basis.
- Infrastructure is monitored for availability, performance and operational incidents.
- Business continuity and incident-response procedures are maintained for relevant systems.
- System architecture and hosting controls are designed to support appropriate redundancy and resilience.
8. Separation Control
Measures designed to ensure that data collected for different purposes or customers can be processed separately.
- Customer and tenant data is logically separated within the application architecture.
- Production and test environments are separated.
- Access rights are managed in a granular manner based on tenant, role and operational responsibility.
- Testing and development processes are designed to avoid unnecessary use of production personal data.
- Where production data is required for troubleshooting, access is limited and controlled.
9. Confidentiality and Personnel Security
Organisational measures designed to ensure that personnel handling personal data understand and comply with their confidentiality and security obligations.
- Relevant personnel are subject to contractual confidentiality obligations.
- Access to personal data is granted only where required for the individual's responsibilities.
- Security and data-protection responsibilities are communicated internally.
- Access rights are removed or adjusted when personnel change roles or leave the organisation.
- Security awareness and internal guidance are maintained as appropriate to the role and risk.
10. Security Monitoring and Incident Management
Measures designed to detect, investigate and respond to security events and personal-data breaches.
- Relevant system and application logs are maintained for security and operational monitoring.
- Security incidents are assessed and handled through defined incident-response processes.
- Potential personal-data breaches are escalated internally without undue delay.
- Customers are notified of relevant personal-data breaches in accordance with the DPA and applicable law.
- Corrective and preventive actions are documented where appropriate following material incidents.
11. Secure Development and Change Management
Measures designed to integrate security into software development and technical changes.
- Source-code changes are subject to controlled development and review workflows.
- Development and production environments are separated.
- Technical changes are tested before production deployment where appropriate.
- Dependencies and infrastructure are maintained and updated in line with security requirements.
- Access to development and deployment systems is restricted to authorised personnel.
12. Data Minimisation, Retention and Deletion
Measures designed to limit personal-data processing to what is necessary and to support appropriate retention and deletion.
- Helu processes customer personal data only for documented service purposes and customer instructions.
- Access and processing are limited to the data necessary for the relevant service or task.
- Customer data can be deleted or returned in accordance with the contractual terms and applicable retention requirements.
- Deletion processes cover relevant production data and are complemented by backup lifecycle procedures.
- Retention periods and technical deletion processes are reviewed as systems and services evolve.
Control Summary
| Control area | Helu approach |
|---|---|
| Physical access | Professional hosting facilities with controlled access and approved authorised-person procedures. |
| System access | Individual accounts, role-based access, authentication controls and periodic access reviews. |
| Data access | Need-to-know access, restricted production access and confidentiality obligations. |
| Transmission | Encrypted transport and secure administrative channels. |
| Logging | Application/system logging and review of relevant administrative actions. |
| Vendor control | Due diligence, contractual safeguards and maintained sub-processor documentation. |
| Availability | Backups, recovery testing, monitoring and incident-response procedures. |
| Separation | Logical tenant separation and separation of production/test environments. |
| Personnel | Confidentiality commitments and role-based security responsibilities. |
| Secure development | Controlled source-code, review, testing and deployment workflows. |
| Retention/deletion | Contractual deletion/return processes and ongoing retention governance. |
Further Development of Measures
The measures published on this page form part of Helu's Data Processing Agreement where referenced therein. Helu may further develop or adapt individual controls as technology and security standards evolve, provided that the overall level of protection is not materially reduced.
For questions regarding Helu's security measures or data protection, please contact us via our contact page.




