Give out an USPO alias. Shield your real address.
Every sign-up, download and marketplace gets its own address on your proxy. Mail arrives at USPO Shield first, gets checked against your rules, and is relayed to the inbox you actually read — or stopped before it ever gets there.
- 1
- inbox per person
- 0
- real addresses exposed
- ∞
- aliases to burn
Every verdict is recorded in your delivery log
Three steps between a stranger and your inbox.
- 01
Mint an address
Name the alias after whatever you are signing up for. USPO Shield generates the local part so two aliases never collide, and mints a private relay token with it.
- 02
Decide what gets through
Allow only the senders you expect, block specific addresses, or stop anything whose subject contains a keyword. No rules means everything on the alias flows through.
- 03
Read it in your own inbox
Approved mail is relayed to your destination address with the alias kept in the reply path. Stopped mail never reaches you, but you still see why it was stopped.
A proxy that behaves like a bouncer.
Rules are evaluated server-side, before any message is handed on. Nothing is forwarded on the hope that it is fine.
Sender allowlists
Only the addresses you name can reach the destination. Everything else is turned away at the proxy.
Blocklists & keywords
Ban a sender outright, or catch a subject keyword before the message is relayed anywhere.
Pause without deleting
Switch an alias off the moment it starts leaking. Mail stops arriving; the address stays reserved.
Full delivery log
Sender, subject, verdict and the rule that fired — recorded for every message the relay sees.
Multiple destinations
Send receipts to one inbox and newsletters to another. Set a primary default and override per alias.
One real address
Your destination is never handed to a sender. The alias is the only thing that ever travels outward.
The relay is a real endpoint, not a mock-up.
Each alias carries its own private relay token. Point your mail provider's inbound webhook at that URL and USPO Shield evaluates the message against the alias rules, records the verdict, and relays it to your destination — nothing is stored beyond a short preview of the subject and body.
You can also fire a test message from any alias page to see exactly how your own rules respond before you hand the address to anyone.
Open your relay/api/inbound/<alias-token>{ "from": "…", "subject": "…", "text": "…" }status → allowlist → blocklist → keywords{ "verdict": "forwarded" | "blocked" }Your inbox should not be public property.
Create an account, add the inbox you actually read, and start handing out addresses that can be switched off.