Session-protected access
The service uses random server-side session records and HTTP-only cookies. The backend checks session validity and account status when protected requests are made.
This page describes protections confirmed in the current application code. It is not a certification or a promise that covers every deployment, provider or operational practice.
The service uses random server-side session records and HTTP-only cookies. The backend checks session validity and account status when protected requests are made.
Mailbox ownership is resolved from the authenticated session. Message, conversation, contact, label, rule, blocked-sender and attachment operations are scoped to the signed-in mailbox.
Temporary mailbox expiry and quota are enforced by the server. Mail may be purged after the configured retention period; actual timing depends on deployment configuration.
Inbound mail depends on the configured routing and backend services. Outbound delivery depends on the configured provider and account status. No end-to-end encryption, independent security audit or compliance certification is claimed here.
An approved Privacy Policy and Terms of Service have not been supplied in this application. Ask the service administrator for the applicable policy before relying on deployment-specific data handling details.