What Brick keeps.

What gets stored

When Brick reads a paste, he keeps the writing patterns: the verdict with its confidence, each tell he found with the short fragment he quoted as evidence, the full text of the paste after redaction, and the reply he wrote back. He also keeps a fingerprint hash of the paste so the same email circulating through many inboxes shows up as one email, the character count, which prompt version and model did the reading, how long it took, the tone you picked on a regenerate, and any feedback you left.

He keeps the reply so he can tell whether his replies are getting better over time. The saved copy goes through the same stripping as everything else, so where your copy has a name, his has [name]. The reply you copy is untouched.

What gets stripped first

Before anything is saved, email addresses become [email], phone numbers become [phone], and links become [link]. That pass runs on the full text and on every quoted fragment. Contact details in a paste never reach the database.

Brick also covers names, companies, and signature lines where he can identify them, both on the marked-up email he shows you and in what gets saved. That one is best effort rather than a promise: finding a name takes judgment, and he can miss one. The three above are pattern matching and do not miss.

What is never stored

The email as you pasted it. Only the redacted version is kept.

Who you are. There is no account, no signup, and no email gate, so Brick has nothing that names you and wants nothing that does.

Your IP address. Brick counts requests per IP so the rate limit holds. Those counters live in a separate store and expire on their own within a couple of hours. The database never gets the IP.

What you did on the page. Brick runs no analytics and records no visits or clicks, so he cannot tell you how many people came by or what they pressed. He knows an email arrived because he read it.

The tip jar

The tip jar in the corner is Ko-fi's, and their widget loads on every page here. That means Ko-fi's servers see your IP address and which page you were on, the way any embedded button does, whether or not you ever click it. Opening the panel loads more of their page, and paying happens entirely on their side.

Brick never sees your card details and never learns who tipped. A content blocker stops the widget and nothing else on the page breaks.

Why

The patterns are how Brick gets better at spotting AI-written email. The catalog of tells gets revised against what actually shows up in the wild, and the next version reads sharper than the last. Aggregate numbers, like how many emails Brick read last week, sometimes appear in Outblox content. Pasted content never does.

Questions

Send them to bryce@outblox.com. A human reads that inbox.