Stay connected, keep addresses separate

Separate website relationships with different receiving addresses

Shopping sites, communities, newsletters, and projects don't need to know the same address. Trace where an address was exposed and cut off only the affected connection when it turns sour.

Understand the four steps of address separation

A separate address isn't a second public inbox. It's a relationship boundary between a website and your private email.

1

The website only sees the separate address

Use a dedicated address when signing up instead of submitting your real email directly.

2

The system receives and checks it

Incoming mail passes basic security rules while essential status and timing details are recorded.

3

It reaches your verified destination

Messages are sent to a private email address you have confirmed, so you don't need to keep reopening the website.

4

Control each source separately

When unwanted mail appears, pause the relevant identity while other connections continue normally.

Use-case matrix

Use different entry points for short-term, ongoing, and important relationships

Choose based on the task's risk and how long you expect to stay in touch—not one address for everything.

TaskTemporary addressSeparate forwarding addressLong-term email
One-time download or trialRecommendedUsableUsually unnecessary
Shopping and newslettersNot convenient for ongoing useRecommendedUsable, but the source is harder to identify
Communities and long-term projectsNot suitableRecommendedSuitable for important relationships
Banking, healthcare, and governmentNot suitableUse with cautionRecommended
Testing email templatesRecommended for short testsSuitable for ongoing regression testsNo need to expose your primary address

How it works

Verify the destination first, then assign a public identity

One receiving destination can manage multiple identities, each with its own status, creation time, and delivery count.

Verify your receiving email

Enter an email address you control and enter the six-digit verification code; no separate password is required.

Create a prefix without sensitive information

Name it by purpose, but leave out your name, birthday, and account number; leave it blank to generate one at random.

Check the delivery trail

Filter records from the past 30 days by status, retry failed deliveries, and restore false positives.

Disable precisely

Pause a single identity instead of changing your real email, then delete it when you no longer need it.

Limitations

Separating public addresses doesn't eliminate every email risk.

Your details may still identify you

If payment details or message content reveal your real identity, separating addresses cannot anonymize the entire relationship.

Keep recovery access for important accounts

Use a long-term email address first for financial, healthcare, government, and core work accounts.

Delivery depends on multiple parties

The sender's server, the network, and the recipient's mailbox can all cause delays or rejection.

Records are not permanent archives

Delivery history is kept for only the past 30 days; save important content in your own systems.