This Wirepass belongs to whoever set it up: the first account made on it takes it, and after that the sign-up box is gone. Anyone who finds the address sees a sign-in form and nothing else.
Wirepass is somewhere to put all the things that would otherwise fill up your email: bank alerts, parcel tracking, newsletters, a message from a script when the backup finishes. You read them when you want to, in a list, instead of them landing among the messages from actual people.
A pass is one sender's way in. You make one per sender and give out nothing else — never your real email address, never your phone number.
An email pass is an address like newsletter-4f8a2c9e1b3d7f02@yourdomain.com that you paste into a newsletter sign-up form. It starts with the name you gave the pass, so a bounce or a stray message tells you which sender it belongs to without looking anything up. A webhook pass is a web address that a script or a service can send a message to.
If a sender starts spamming you, or gets breached, or sells your address on, you delete that one pass. The sender is stopped that second and nothing else you have is affected. That's the whole point of giving each one its own.
A feed is a list of messages. Every pass delivers into one, and you decide which — one feed for money, one for newsletters, one for everything else. You can read a feed here in the browser, or add its link to an RSS reader on your phone or computer.
Each feed has three settings. It can arrive once a day as one summary instead of message by message, which is the right setting for anything chatty. It can be kept for a number of days and then thrown away, or kept forever. And it can be made public, which turns it into a page anyone can read — useful for a status feed, wrong for anything else.
Rules belong to a pass, and they read like sentences: if the sender contains "bank.com", then send it to feed money. You build them from two dropdowns; there is nothing to learn.
A rule can send a message to a different feed, add a tag, mark it important, or ignore it entirely. Rules are read top to bottom and the first one that matches is the one that happens, so put the important ones at the top — there are arrows to move them.
Feeds wait for you: nothing arrives until you open one. That's the point for a newsletter and no use at all for a fraud alert. So a pass can send a copy of what it accepts out to something that can reach you — a phone notification service, a chat room, a home dashboard. You give the pass a web address, that service gives you a buzz in your pocket.
Each pass chooses between a copy of everything it accepts, or only the ones a rule marked important. Anything a rule ignores is never copied, and a copy that fails to send doesn't cost you the message: it is already in your feed.
An email pass can also send the mail itself on to your own email address — useful while you're still getting used to this, or for the one sender you want in your inbox. It has to be an address you have verified with Cloudflare, and it is the one and only case where anything leaves here as email.
You can't write messages here. There's no compose box and no reply button — this is somewhere things arrive, not somewhere you send from. It won't show pictures, attachments or formatting either: messages are kept as plain text, which is also why nothing in them can track you or run code. There are no apps to install and nothing to pay for.
A feed link is a password. Anyone who has it can read that feed, so treat it like one. If you put it in someone else's RSS reader app, that company can read your messages too; for anything sensitive, read it here instead. You can change a feed's link at any time, which locks out anyone who had the old one.
Write down your owner secret. It is shown once, when you make your account. It is the only way to reset a forgotten password, and the only way to export your messages. Lose both it and your password and there is no way back in — there's no email address on file for us to send a reset link to, by design.
On your own Cloudflare account, in your own database. Nobody is running this for you and nobody else can see it. You can export everything as a file at any time, and you should, now and again.
Up to 500 passes, 100 feeds, 50 rules per pass, and 10,000 messages a day — more than a person is likely to want on the free side of a Cloudflare account. Messages can be up to 10,000 characters (5,000 for email, or 60,000 when a pass shows pictures). Feeds show 100 messages at a time, with a link to older ones.
Sending messages from your own scripts, the exact rule format, and what is stored where: see the developer notes.