Sovereign Mail
PricingSourceOpen app

SUPPORT

Start with a safe diagnostic, not a secret.

Use the channel that matches the issue. Never post credentials, provider passwords, Cloudflare tokens, private keys, raw mail, or message content.

Community support
Managed-service priority

Product questions and bugs

Search or open a public issue in the GitHub issue tracker. Include the application version, browser, safe steps to reproduce, expected result, and actual result. Remove domains, addresses, request bodies, and identifiers that are not needed.

Workspace diagnostics

Owners and administrators can open Settings → Debug to view schema, provider health, last successful synchronization, failed-operation count, recovery-point state, and safe next actions. Review the report before sharing it and redact any customer-specific domain you do not want in a ticket.

Managed-service support

Subscribers receive the priority contact path in their service confirmation and billing receipt. Include the workspace installation identifier and a short impact summary. Billing requests should include the Stripe receipt identifier, never full card details.

Security reports

Do not publish an exploitable security issue. Use GitHub’s private vulnerability reporting when it is available for the repository. If that path is unavailable, open a non-sensitive issue asking for a private contact channel without disclosing the vulnerability.

Account deletion and refunds

See Account deletion for self-service removal and owner limitations. See Refunds for eligibility and timing.

Mail-provider outages and Cloudflare incidents remain controlled by those providers. Sovereign Mail support can help diagnose and recover, but cannot override a third party’s service.
© Sovereign Mail
PrivacyTermsRefundsSource