A trust boundary you can see.

Dakia is a client, not a mailbox. Run it on your own infrastructure, or join the hosted beta where we run it for you. Either way it connects directly to the email providers you choose, and your mail never moves to a Dakia mailbox.

Connections
Direct to your providers
Credentials
Encrypted at rest
Telemetry
None

Encrypted credential storage

Account credentials are encrypted at rest, stored separately from Dakia’s databases. Self-hosting? Dakia creates a 32-byte credential key on first startup and keeps it server-side; protect both persistent volumes and their backups. The host administrator can access these files; this is not end-to-end encryption. Mailbox passwords and Gmail refresh tokens use this encrypted credential store. Keep the Google client secret private in your server configuration.

Your identity, your sign-in

Self-hosting? New installations use a built-in username and password. The first person claims the installation with a private setup code from the host. The owner can then create single-use invitations that expire after 24 hours. Your Dakia password is separate from your mailbox password. Follow the sign-in guide. OpenID Connect remains an optional mode for installations configured with an external identity provider; it is not required for setup. Gmail authorization is separate from your Dakia login.

Careful with received mail

Received HTML is sanitized and rendered in isolation. External images load through Dakia’s bounded image proxy. You can block external images and tracking pixels in Workspace; both options are off by default.

Responsible disclosure

Security reports can be sent to support@dakiamail.com. Do not include passwords, live authorization codes, or sensitive mailbox contents.