Your provider handles sign-in
Mailbox connections use the provider’s own OAuth flow. The password stays between you and the provider.
Your mailbox and CRM are sensitive systems. Ervona uses scoped access, encrypted credentials, account-level isolation, and records that show exactly what the Desk did.
Connecting Ervona does not mean handing over passwords or opening your entire stack. Access is scoped, revocable, encrypted, and separated by account.
Your provider grants a scoped token. Ervona never receives your email password.
Stored tokens are encrypted before they touch disk, with the key held separately.
The database refuses to return records that do not belong to your account.
Disconnecting invalidates access immediately. There is no cached copy left active.
Every connection is designed around the minimum access needed to do the job—and a clean way to take that access back.
Mailbox connections use the provider’s own OAuth flow. The password stays between you and the provider.
Tokens and credentials are encrypted with AES-256-GCM using a key stored separately from the protected data.
Revoking a mailbox or CRM connection invalidates its token immediately instead of keeping a dormant copy of access.
Row-level security prevents a query from returning another account’s records, even if application code makes a mistake.
Salesforce and HubSpot are mutually exclusive per account, enforced by a database trigger so records cannot be cross-mapped between two CRMs.
What Ervona stores, how long it stays, and why it exists.
Kept so a quiet day is explainable instead of becoming a mystery.
Enough time to investigate a recent issue without keeping the conversation indefinitely.
Deleted—not merely deactivated—when you revoke the connection.
Ervona is working toward formal SOC 2 attestation. That audit will cover the same areas described on this page: encryption, access control, isolation, and logging.
Found a security issue? Read our vulnerability disclosure policy or contact us directly.
security@ervona.ai →