Last updated: 6 September 2026
Security approach
Repulion uses organisation separation, server-side permissions and traceable operational actions as part of the platform architecture.
Access control
- Role-based permissions are checked on the server.
- Organisation data is scoped to the active organisation.
- Repulion Control is separated from normal organisation access and uses stronger authentication controls, including 2FA.
- Support access should be permissioned, scoped and auditable.
Data protection
- Sensitive documents are kept outside normal public access and served only after authorization.
- Stored secrets are encrypted where required and passwords are hashed.
- Security-sensitive operations are designed to leave audit records.
Backups and resilience
Repulion maintains protected backup and recovery processes for production data. Backup status and operational diagnostics are kept out of the public website and available only to authorised platform operators.
Incident handling
Security events and material service incidents are investigated and handled through controlled platform processes. Public status information is limited to the detail needed to communicate service impact while protecting sensitive infrastructure information.
Responsible disclosure
If you believe you have found a security issue, do not publish sensitive details or access data that is not yours. Send the issue privately to info@repulion.com with “Responsible disclosure” in the subject.
Certifications and claims
Repulion does not describe itself as “hacker-proof” and does not claim certifications it has not earned. Formal compliance commitments, subprocessors and contractual security requirements should be documented separately when applicable.