Privacy Policy — VoxRox Mail

Version 2026-06-01 (draft, pre-first-release). This version is preliminary and has not yet been reviewed by a lawyer — see "Open items" at the bottom.

VoxRox Mail is a desktop e-mail client for Windows. The application runs locally on your computer. Your e-mails, contacts, account credentials and logs stay on your device and are never sent to any VoxRox server or other third party — except those you choose yourself by adding an e-mail account (your e-mail provider, and optionally Google or Microsoft for OAuth login).

VoxRox does not operate a backend server for this application, does not store your data in the cloud, and does not collect telemetry, analytics or crash reports against an external endpoint.

Who is the data controller

Under the GDPR you are the data controller for everything stored by the application — all data lives locally on your device under your operating system account. VoxRox only supplies software that processes data according to your instructions and has no access to your data.

What data the application stores locally

All persistent data lives in the standard Windows data directory:

%LOCALAPPDATA%\VoxRox\Mail\

Contents:

What is encrypted

• IMAP/SMTP passwords and OAuth tokens (Google, Microsoft) are encrypted with AES-GCM using a key derived from crypto.bin. Without the crypto.bin stored in your profile they cannot be decrypted.
• crypto.bin itself is protected only by Windows file system permissions on your user profile. Recommendation: do not back it up to public cloud storage without additional encryption.

What is not encrypted

• E-mail headers and bodies, contacts, message subjects, senders, attachments, log files and synchronization metadata sit in the SQLite database and on disk in plain form. If you need protection against physical disk access, use full-disk encryption (BitLocker etc.).

What data leaves the device

The application initiates network traffic only in these cases:

1. Connection to your e-mail server (IMAP and SMTP) — fetching mail, sending, folder synchronization. Where exactly the application connects depends on the account you add (Gmail, Outlook, Seznam, custom server).
2. OAuth login (Google, Microsoft) — if you choose this login method instead of an app password. The application opens your default browser on the provider's login page, receives an access token + refresh token, and stores them locally (encrypted, see above). It periodically obtains a new access token from the provider using the refresh token.
3. Application updates (Tauri updater) — checking for a newer release against the release endpoint and downloading the signed installer. The exact URL will be confirmed before the first public release.

The application does not send your e-mails, contacts or activity to any VoxRox server or third-party analytics platform.

Diagnostic reports from the client

The frontend sends technical errors (JavaScript exceptions, failed API calls) to the local backend endpoint POST /api/internal/client-errors, which runs on 127.0.0.1 on your computer. These reports are not transmitted anywhere — they are written to your local logs only.

If you contact support and provide a manually exported diagnostic bundle (GET /api/internal/diagnostic-dump), that bundle contains only masked e-mail addresses, account configuration (host, port, SSL), synchronization status and runtime metrics. It does not contain credentials, OAuth tokens, message bodies or subjects.

Third parties

When you add an account, the following providers come into play:

• Your e-mail provider (Gmail, Outlook, Seznam, your own server, …) — governed by their own data processing terms.
• Google — if you use Gmail with OAuth (policies.google.com/privacy).
• Microsoft — if you use Outlook / Hotmail / Live with OAuth (privacy.microsoft.com).
• GitHub — if we decide to distribute updates via GitHub Releases in the future, the application will periodically check for a new version against the GitHub API (GitHub Privacy Statement).

VoxRox has no data-sharing agreement with any of these providers regarding your data. Communication happens directly between your computer and the respective server.

Your rights and controls

• Remove an account from the application — delete the account in Settings. This cascade-deletes the account record, credentials, sync state, messages and contacts from the local database.
• Revoke OAuth access at the provider:
  • Google: myaccount.google.com/permissions → find "VoxRox Mail" → Remove access.
  • Microsoft: account.microsoft.com/privacy/app-access (personal accounts) or myapps.microsoft.com (work / school accounts) → find the app by Client ID → "Remove permission". Microsoft does not implement the standard revoke endpoint (RFC 7009), so the revocation has to happen on their side.
• Complete data removal — uninstall the application and then manually delete the %LOCALAPPDATA%\VoxRox\Mail\ directory. The installer deliberately does not delete the data directory (so reinstall does not lose your mail).
• Data export — contacts can be exported to vCard via Settings > Contacts. Full database export is not available from the UI in the 0.x releases; advanced users may copy db/mail.db directly and open it in any SQLite browser (e.g. DB Browser for SQLite).
• Access to logs — files under logs/ are plain text readable in any editor.

Children

The application is not specifically aimed at children under 16, but does not restrict their use either — features depend entirely on the accounts you add yourself. Recommendation for parents: confirm that your chosen e-mail provider permits use by a child.

Security disclosure

If you discover a vulnerability or security issue in the application, please do not report it publicly in the issue tracker. Email info@voxrox.org. See the Support page for responsible-disclosure details.

Changes to this policy

This version is preliminary. Before the first public release and on every material change (e.g. introducing telemetry, changing the list of third parties) this document is updated. The current version is always included in the installation and in the project repository.

Open items before the first release

These items will be filled in before this document is finalized:

• Specific Tauri updater endpoint URL.
• Legal review (especially the GDPR phrasing of "data controller" for the case where the user deploys the application inside an organization).