Built for the person reading this at 2am, wondering if they're imagining it.
Receipts started as a private tool for one person who knew something was wrong in their messages, but couldn't name it. They built it. Now we're a small team in Brisbane making it available to anyone else who needs it.
We built this because naming something is the first step to loosening its grip. And because memory is a poor witness. Especially of conversations that are designed to make you doubt yourself.
Four commitments we've written down, and then written into the product.
Safety before growth.
If a growth decision puts a user at risk, we don't make it. Every feature ships through a safety review first.
Language, never labels.
Receipts names what the language is doing. Not who anyone is. We will never call someone an abuser. Or a victim.
Useful without being sure.
Most people who need Receipts don't know they need it yet. The product must be useful the moment someone opens it, without commitment.
Quiet by default.
No notifications, no nudges, no streaks. Safety tools cannot look like engagement tools.
The list matters as much as the product.
We think about these lines often. Naming them publicly is how we stay on the right side of them.
We don't run ads.
No banners, no sponsored content, no affiliate links. The product is paid for by the people who use it.
We don't use engagement metrics.
No DAU dashboards, no streaks, no notifications designed to pull you back. A week where no one opens Receipts is a good week.
We don't dark-pattern cancellation.
One button, one click, no exit survey, no retention offer. Your data exports in the same flow.
We don't call anyone an abuser.
Or a victim. Receipts describes language, never people. That's a line we don't cross even when users ask us to.
If you ever see us doing one of these, write to us. contact@receipts.love
Questions, feedback, or partnership inquiries. We'd love to hear from you.
We're a small team. We read everything.