Privacy

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, and the full text of the paste after redaction. 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.

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.

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. There are no analytics and no tracking scripts of any kind here, so Brick cannot tell you how many people visited or what they clicked. He knows an email arrived because he read it.

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.

Back to Brick