Connection boundary
OAuth connections avoid shared mailbox passwords and can be revoked from the provider or emlOPS.
SECURITY
Control is not
a setting.
It is the architecture: narrow provider access, minimized data, visible AI actions, and a human authorization boundary.
Approval boundary
Prepared drafts and sending remain distinct actions. Nothing sends without an authorized human decision: you approve the message, or you switch on automatic replies or a sending policy, which you can turn off at any time.
Data minimization
Attachments remain at the provider and load on demand; operational metadata is kept only as needed.
Tenant isolation
Workspace and provider records are tenant scoped, with privileged operations enforced on the server.
Credential protection
Provider credentials are encrypted at rest and accessed only inside the operation that needs them.
AI controls
Managed and bring-your-own requests share bounded context, visible model selection, and reviewable output.
Auditability
Sensitive actions are logged so account connections, drafts, approvals, and changes can be investigated.
SECURITY CONTACT
Report a concern directly.
Send responsible security disclosures to info@emlops.com. Include affected URLs, reproduction steps, and potential impact.