MailboxWarm
How MailboxWarm protects account and mailbox access.
App sign-in, mailbox authorization, stored credentials, and provider actions are separated so one kind of access does not silently grant another.
Separate identities
App login and mailbox authorization are different credentials. The backend verifies app identity and enforces workspace ownership on reads and changes.
Protected credentials
Mailbox credentials are encrypted before storage. App sign-in uses a separate email code; it does not grant access to your mailbox. Only connect mailboxes you control when your provider is available.
Controls before launch
TLS, encryption, destination restrictions, permission review, restore testing, and verified sending limits are release requirements—not claims that an unfinished implementation already satisfies.