Health answers stay out of your ad tools.
Signed BAAs, health answers kept away from analytics and pixels, access scoped per role, on every telehealth build.
The pixel on the intake page is the leak.
Weight
Medications
Condition
Pixel on the intake
A patient types her weight and medications into an intake at 11pm; the page carries the same Meta pixel as the landing page, so her answers go to Meta with the page view.
Weight
Medications
Condition
What we ship
The intake pixel fires 'step 3 completed' and nothing else; the answers go to the chart, and the ad platform never sees them.
Cerebral and BetterHelp both settled with the FTC over pixels like this; Improvado's 2026 telehealth guide puts the reported settlements at roughly $7 million and $7.8 million.
We are not your lawyer. This is how we build, so your lawyer has less to worry about.
Five rules, on every telehealth build.
Signed BAA before the first commit
Your template or ours, signed before any code moves.
Health answers never reach ad tools
Marketing reads a step number; the care team reads the chart.
Access scoped per role
A designer on the landing page cannot open a patient record.
Intake sends only what the flow needs
The answers your providers decide on, not the whole form to every system.
Flagged while scoping
A request that would put patient data in the wrong place is raised on the scope call.
Three things we ask of you.
- Your brand is already live: provider network, pharmacy and LegitScript in place.
- You sign the BAA with us, the same way you did with your platform and your pharmacy.
- You share the list of every tool that currently receives data from the funnel.
Asked before every telehealth build.
Can our own developers take it over later?+
Yes. It is a plain Next.js repo on your GitHub, running on your domains and your Stripe keys, with no framework of ours sitting in the middle. Anyone you hire reads it the way they read any other codebase, and ending the retainer changes nothing about what is live.
Is this HIPAA-compliant?+
We sign a BAA on every telehealth engagement. Health answers never reach analytics or ad tools, and access is scoped per role, so the care team reads the chart and marketing reads a step number. The tracking settlements this industry has already paid came out of the same account the ad budget comes from, so if a request would put patient data somewhere it should not go we flag it while scoping, before it is built.
What does the patient see?+
Your brand on your domain, start to finish. Nothing looks borrowed from another clinic, which is half of why a page converts: someone about to hand over a card and a medical history can tell a template when they see one. Firstfill never appears to a patient.
