Workspace security you can understand.

Learn how YoMaily controls workspace access, protects provider credentials, and checks sending eligibility. Read the limits of those controls before connecting your services.

No impersonationNo browser-stored provider secretsServer-gated Stripe billingNo autonomous-send claim

How access and sending are controlled.

Workspace access and roles

The server checks workspace membership and roles against the application database before allowing access.

Separate client workspaces

Server authorization and PostgreSQL row-level security are separate checks against access to another workspace’s records.

Protected provider credentials

Client provider credentials use encrypted storage scoped to the workspace. Diagnostic results redact secrets.

Approval before dispatch

Human approval, suppressions, rate limits, quiet hours, and provider restrictions are checked before an eligible message is dispatched.

Audited administration

Service administration uses aggregate records and audited operational actions. It does not expose client campaign content or provider secrets.

Workspace capacity limits

Workspace plan limits apply to client capacity. Checks run on the server before additional capacity or sending is allowed.

Account setup and billing happen in your workspace.

Verified visitors can create an isolated workspace and select a plan through authenticated Stripe Checkout. Provider connections and campaign sending remain deliberate, workspace-specific actions: customers supply their own provider credentials, and sending requires setup, review, approval, and the applicable safety checks.

No public statement on this page is a certification, penetration-test report, availability SLA, or guarantee that an incident cannot occur.

Ask us about workspace security.