Trulyp.
Encryption and Backups

Encryption at rest

Persistent application data, including database data, is encrypted at rest using LUKS-based block storage encryption with AES-256 key management.

Database backups are created from the underlying database storage rather than as readable SQL exports. Backup data is also encrypted at rest.

Application secrets are not stored directly in the Kubernetes cluster. They are managed through an external secrets store and kept in a separate secure vault.

Encryption in transit

All external traffic to our SaaS platform is HTTPS-only and uses TLS 1.2 or newer.

For customers connecting directly to a database, the customer controls the database connection and is responsible for configuring TLS where required.

SaaS backup policy

Customer data is backed up using multiple schedules, providing both recent recovery points and longer-term retention. For trial environments no backups are maintained.

RPO — Recovery Point Objective describes the maximum amount of data that could be lost when restoring from a backup. An RPO of 24 hours means that, in the worst case, up to approximately 24 hours of changes may need to be recovered or recreated.

RTO — Recovery Time Objective describes our target time for restoring data or services after a recovery process has started. An RTO of 2 hours, for example, means the target is to complete that recovery within approximately two hours.

Information security

Our backup and security processes are managed as part of our broader information security practices and ISO 27001-certified management system.