Mail Service PRIVATE MAIL
View plans
Help center

Straight answers.
No fine-print fog.

Privacy, account access, mail protocols, database-backed plans, and launch behavior explained in plain language with technical context.

Browse questions

Find the right boundary.

Filter by topic. Every answer describes current behavior or an explicit implementation boundary.

Security overview
Plain languageTechnical contextNo inflated claims
Do you scan inboxes for advertising?Business model

No. Subscription revenue funds the service, so advertising profiles are not part of the business model.

Can I use a regular mail client?IMAP, SMTP, POP3, JMAP

Supported accounts can use the protocol settings shown in their mailbox area. Each capability displays whether its state is applied, pending, failed, or unsupported.

Where do plan prices come from?MariaDB price history

Pricing joins each active public plan to its single current price record. Amounts are stored as integer minor currency units, never floating-point prices; older Stripe Price mappings remain in history when an administrator changes pricing.

Why does checkout say setup pending?Billing lifecycle

Test Products and current Prices are mapped, but registration, billing-customer creation, subscriptions, and verified webhook processing are not connected yet. Checkout stays disabled until that complete lifecycle is available.

Is every message end-to-end encrypted?Encryption boundary

No blanket claim is made. Transport security, storage protection, encrypted application secrets, and end-to-end message encryption are separate capabilities.

What happens before launch?Reservation lifecycle

The home page shows a username reservation form. Accepted reservations are stored server-side for 30 days, while the browser keeps the one-time reservation token in localStorage.

How are recovery methods handled?Verified recovery

A backup method must be verified before it can be trusted for recovery. Reset and verification tokens are stored as cryptographic hashes and expire.

Technical glossary

The terms behind the interface.

Short definitions for the security and mail concepts used throughout the site.

TLS

Transport Layer Security

Authenticates and encrypts a supported network connection. It does not by itself make message content end-to-end encrypted.

CSRF

Request forgery protection

Binds state-changing browser requests to the active application session.

IMAP

Mailbox synchronization

Keeps folders and messages synchronized with a compatible mail client.

JMAP

Structured mail API

A modern API capability used only when supported by the configured mail service.

Explore the product system

See how the pieces fit together.

Move from questions to the mailbox, protocol, and billing capability map.

View features