Powerful email tools need boringly serious security.

Inspect the controls behind your mailbox connections, shared documents, signing links, team permissions, and AI access. Elite Mail Suite gives you clear ways to authorize, review, and revoke access.

Personal workspace Allowed
Shared team content Allowed
Manage members Restricted
Organization controls Restricted
Choose a role to inspect its permissions.

Security across the account, workspace, and service

Account access

Verified accounts, hashed passwords, optional authenticator MFA, device management, rotating credentials, and session invalidation protect account access.

Tenant and team boundaries

Tenant-scoped APIs, exact-email invitations, and role-based team permissions keep workspace access tied to an authenticated account and approved role.

Transport and service hardening

TLS in transit, rate limits, hardened non-root services, least-privilege service accounts, and security-focused response headers.

Recovery

Database integrity monitoring, backup procedures, and recovery checks support dependable operation.

Auditability

Security, administrative, and signature actions produce audit history so teams can review sensitive changes, access events, and completed signing records.

Data minimization

Standard tracking sends message metadata rather than message bodies. Provider refresh credentials are encrypted at rest; stored content and files enter through deliberate product workflows.

Scoped AI access

Reading, drafting, sending, and administration use distinct permissions. AI connections respect account and team policies, with review and confirmation for protected actions.

Document and signing access

Opaque public tokens are hashed or encrypted according to the access workflow. Quarantined and revoked assets are denied before storage access.

Completed signing records

Completed signature documents carry file hashes and completion records. Recipient-specific access and audit history preserve the context of the finished request.

A clear purpose for the data you share.

  1. Standard tracking records normalized message, recipient, delivery, and event metadata. Message bodies are not part of the standard tracking payload.
  2. Explicit workflows store the templates, campaign content, recordings, documents, and signature material a user chooses to create or upload.
  3. Signal classification keeps likely-human, privacy-protected, automated scanner, sender, and unknown activity distinct with clear labels for each activity type.
  4. Retention and deletion are described in the privacy policy and DPA, including separate treatment for network and approximate-location fields.

Your connections, your choices.

What can a connected inbox access?

Provider authorization shows the requested access. The connection supports the mailbox features you enable; standard tracking and stored campaign or document content have different data needs.

Can an assistant send for me?

AI reading, drafting, and sending use separate permissions. Tracked AI messages and campaign launches require review of the prepared send. Configured workflows follow their authorization rules.

Who controls team AI access?

Owners and admins set role limits. A connection cannot grant more access than the user and team allow.

Can I see what happened?

Review recent connection activity and workflow history. Check the action and its result before deciding what to do next.

How do I stop access?

Disconnect the provider or AI connection, pause the workflow, or revoke a document link. Revocation does not recall an already sent email or downloaded file.

What can I delete?

The privacy policy and DPA explain retention and deletion, including different treatment of tracking metadata, uploaded content, and operational records.

Security information for your review

These controls are not a claim of SOC 2, ISO 27001, or another independent certification. Enterprise evaluators may request current architecture, access-control, recovery, and vulnerability-management information under appropriate confidentiality terms.

Report a suspected vulnerability privately

Use the support contact and include enough detail to reproduce the issue. Do not access other users’ data, disrupt the service, or perform destructive testing. Credible reports are acknowledged and coordinated through remediation and disclosure.

Contact security

Get the information your review needs.

Talk through workspace access, data handling, and deployment with us.