Permissions at every boundary
Organization membership and mailbox access are checked on the server. Shared mail separates read, write, management and send permissions. Platform administration does not automatically grant access to mailbox contents.
Trust starts with the details.
Understand how RelyPost controls account access, protects service credentials and handles email content.
Protect each way into your account
Account passwords use Argon2id hashing. Multi-factor authentication supports authenticator codes and recovery codes. Native mail clients use separate app passwords, and API keys can be scoped and revoked.
Safer handling of messages and files
Remote email images are blocked by default. Message HTML is sanitized for display, and attachments require authorized access. The upload pipeline integrates malware scanning. These controls reduce risk; they do not make every incoming message trustworthy.
Encryption with a clear scope
Native IMAP and SMTP connections require TLS. Stored service credentials are encrypted. RelyPost processes message content to provide mail features, so this is not an end-to-end encrypted email service. Your own domain configuration and device security also matter.
GOOD TO KNOW
A few useful answers.
How do I report a security issue?
Contact security@relypost.com. Describe the issue and provide the minimum details needed to reproduce it. Do not include passwords, recovery codes or private mailbox contents.
Does RelyPost guarantee inbox placement?
No. Receiving providers apply their own filtering and sender-reputation rules. Correct authentication and careful sending help, but neither SMTP acceptance nor a security feature guarantees inbox placement.
YOUR NEXT CHAPTER
Create your workspaceMake your business feel at home.
Start with your domain. Build a workspace around your team.