PrivateDropBox.com
Private communications

Choose an inbox by its complete message lifecycle—not by one encryption badge.

Email crosses providers, devices, spam systems, notifications, and backups. A private service should explain which content is protected, which metadata is necessary, who can recover access, and how you can leave.

Use the decision map Read the journal
Decision map

Four signals to inspect first

Use these boundaries to compare claims without turning the process into a feature contest.

Content

Separate transport encryption, encrypted storage, and end-to-end encryption. Ask which fields and recipient types are covered.

Metadata

Review routing, IP, device, delivery, alias, calendar, contact, and notification records.

Recovery

Decide whether provider-assisted recovery or user-controlled keys match the consequence of loss.

Portability

Use custom domains and standard exports when lock-in would be costly.

01

The right privacy boundary

A service can protect stored mail while still processing subject lines, recipients, timestamps, spam signals, and device sessions. That is not automatically a failure, but the boundary should be clear.

Protected-message modes for outside recipients may use portals or encrypted attachments. Follow the message beyond the sender’s interface and understand what the recipient must trust.

02

Endpoints and notifications

Web, mobile, and desktop clients can expose content through lock-screen previews, remote images, local caches, crash diagnostics, and ordinary cloud backups. Configure the endpoint as carefully as the server account.

Aliases reduce correlation only when replies preserve the alias and the underlying mailbox is not revealed. Test inbound and outbound behavior before using an alias for separation.

03

A migration that preserves access

Document mail-related DNS records, keep the previous service active during testing, verify important senders and password-reset flows, and export historical mail in a standard format.

Keep domain registration and email recovery independent. A domain takeover can redirect mail, while an email compromise can reset the registrar unless recovery loops are broken.

Field checklist

Make the next review testable

  • Map encryption states
  • Review retained metadata
  • Harden recovery
  • Control notifications
  • Test aliases
  • Export and restore mail
Frequently asked

Common decision points

Can ordinary email be fully private?

Email can be protected in meaningful ways, but universal end-to-end encryption is difficult because correspondents, routing, spam controls, and metadata cross systems.

Should I use a custom domain?

A custom domain improves address portability and compartmentalization, but it adds registrar and DNS accounts that must be secured.

What matters more: encryption or recovery?

Both. Strong encryption with an unusable recovery plan can cause permanent loss; easy recovery can create an access path. Choose the balance explicitly.

Go deeper

Related field guides

Long-form articles with procedures, limitations, and recovery questions.