How it works

You hand out a disposable address instead of your real one. Mail sent to it reaches your inbox, but the sender never learns who you are — and neither does most of this system.

Creating an alias

Your address goes straight into a Skyflow vault, which hands back a token — an opaque reference with no relationship to the original text. Only the token is kept outside the vault.

When someone emails you

The relay looks up the token for that alias, asks the vault to resolve it, and forwards the message. Your address exists in memory for the length of one request and is never written down.

What each part can see

This is the part that matters. A token is a reference, not an encoding — there is no key and no algorithm that turns it back into an address. Without a vault credential it is a meaningless string.

Why the sender’s name looks different

Forwarded mail arrives from an address on this domain rather than the original sender:

From: "Dana Reed (via skyflowmail.com)" <r-7gf031gg@skyflowmail.com>

Two reasons. Re-sending under someone else’s address fails modern authentication checks, and the message would land in spam or vanish. And it means that when you hit reply, your response routes back through the relay instead of going out from your real address — which would undo the whole point.

What this does not do

• It is not encryption. Mail is forwarded in the clear, exactly as ordinary email works. Anyone who could read your mail before still can.
• It hides you from the sender, not from the relay. This service resolves your address to deliver each message. The guarantee is that it is stored in a vault with an audit trail rather than sitting in a database.
• An alias is only as private as where you put it. Post one publicly and it will attract spam like any address.