For ERP practitioners
The exposure log that doesn’t get filled in the waiting room.
Bronwin is a two-tap tracker shared between you and one patient. They tap a color, rate it 1–10, and go. You read the week before the session. What the colors stand for is agreed in the room and stored on your two phones — never on ours.
Free for three patients, permanently. Every plan gets every security feature.
How intense was it?
This is the board. Tap it — what you see is exactly what someone glancing over a shoulder sees, and exactly what we see.
The current state
SUDS ratings are already required. They’re just not arriving.
Between-session logging isn’t an enhancement to exposure work — it is the protocol. The homework sheet is the part that fails, and it fails the same three ways in every practice.
Reconstructed from memory
A week of ratings filled in five minutes before the session, in the waiting room, is not a week of ratings. It’s a recollection of one, shaped by how the week ended.
Lost, or left at home
Paper goes through the wash. Notebooks get forgotten. The week that mattered most is reliably the one that’s missing.
Too expensive in the moment
A form takes a minute and announces itself to the room. During an actual exposure, on a bus or at a family dinner, that minute doesn’t get spent.
How it works
Three moves, and only one of them is yours.
You agree on the colors
Together you decide what each button stands for: an intrusive thought, a compulsion resisted, a physical surge, whatever the two of you are working on. That agreement is written into the legend, and the legend never leaves your two phones.
They tap it
Something happens; they open the app, tap the shape, and pick a number from 1 to 10. Under five seconds. A note is optional and most people skip it. It works with no signal — a basement, a plane, a parking garage — and catches up later.
You read the week
You open their board and see the days laid out: every mark, every rating, with your legend beside it once you enter your PIN. Export any date range to PDF, legend included, for your own records.
Boundaries
What Bronwin is not.
Every one of these is a decision, not a missing feature.
It is not monitored
No notifications, no alerts, to anyone, and no setting that changes it. You find out what was logged when you open the app. Please don’t tell a patient otherwise — someone who believes you’re watching may rely on that in a bad moment. It’s the one thing to get right when you introduce it.
It is not a crisis service
A crisis button sits at the bottom of every screen, works with no signal and before setup, and tells nobody when pressed.
It is not the clinical record
Transcribe what matters into your own system, the way you always have. The PDF export exists so the record that counts lives where it belongs.
It does not interpret anything
No scores, no risk levels, no predictions. It records and displays; the conclusions are yours, reached in the room. That’s also what keeps it from being a regulated device.
Pricing
You pay. Your patients never do.
Priced against the EHR you already have, at roughly a quarter of it, because this is an adjunct and not a system of record.
- 3 active patient connections
- Every security feature
- Full history, no retention limit
- BAA required, same as every plan
Not a trial. Enough to evaluate properly, or to run a few pro-bono cases indefinitely.
- Unlimited patient connections
- PDF export for any date range
- Priority support
- Everything in Free
For a solo private practice. One subscription, however many patients come and go.
- Seat management and provisioning
- Central billing and invoicing
- Metadata audit logs — which device read which connection, and when
- Negotiated BAA
Audit logs cover access, never content. Nobody at your organization can read patient data, including your administrators.
Two rules we’ve written down so we can’t quietly drop them later. Security is never a paid tier — the PIN, the encryption, the recovery, the verification check are identical on every plan, including free. Connections are never metered above the floor — charging per patient would create an incentive not to connect one, which is backwards clinically and commercially.
Early access
We’re opening with one cohort of ERP practitioners.
The server is built. The app is in development, and we would rather hand it to twenty clinicians who will tell us the truth about it than launch it at everyone. If between-session SUDS tracking is already part of your protocol, three questions and we’ll be in touch.
Status: backend complete and tested, client in development, independent security assessment not yet done. We’ll say so plainly when each of those changes.