Legal
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
This policy applies to Trulyp SaaS. Customer data is backed up daily and weekly. Trial environments are not backed up.
| Backup | Frequency | Retention |
|---|---|---|
| Daily | Daily at 02:00 | 30 days |
| Weekly | Sunday at 03:00 | 60 days |
Recovery objectives (SaaS)
RPO (Recovery Point Objective): 24 hours. The maximum period of data that may be lost when restoring from a backup.
RTO (Recovery Time Objective): 24 hours. The target time to restore data or services after recovery has started.
Stricter recovery objectives can be agreed for enterprise customers in a customer-specific Service Level Agreement.
Private cloud and on-premises
For private cloud and on-premises deployments, the customer is responsible for backups, recovery and the related recovery objectives.
Information security
Our backup and security processes are managed as part of our broader information security practices and ISO 27001-certified management system.