Security

Overview

Rovela runs its own mail transport and storage rather than relaying through a third party, which keeps the surface area small and the trust boundary explicit. This page describes the measures in place and how to reach us about a security concern.

Hosting and isolation

The service is self-hosted on dedicated infrastructure, with no multi-tenant cloud sharing of the mail stack:

• Mail transport, storage, and the API run on servers the operator controls, in a single region.
• Each organization's data is separated by row-level scoping enforced in the application, not by physical isolation alone.
• The operating system and mail server packages are kept current, and security patches are applied promptly when issued.

Encryption

• Transport between clients, the API, and the mail servers uses TLS. Inbound and outbound mail are delivered over encrypted connections where the peer supports it.
• Mailbox contents and metadata are stored on encrypted volumes.
• DKIM signing keys are generated in place and rotated; credentials are hashed and never returned in plain text.

Access control

• Administrative access to the infrastructure uses individual keys with no shared accounts. Keys are rotated and revoked when a person leaves.
• Within an organization, members see only what their role permits. An organization owner can audit and revoke access at any time.
• Administrative actions are logged, and a member's actions in the dashboard are attributable to that member.

Reporting a vulnerability

If you believe you have found a security issue, write to security@rovela.dev with the details. We acknowledge responsible disclosure and will work with you to fix confirmed issues. Please avoid public disclosure until a fix is available.