You hold the keys. We can't pool your data. We never sell it.
Most health apps get your data through a contract you never read and can't undo. Wubs is built the opposite way — you connect each source yourself, you can see and delete everything, and your records are encrypted under a key that's yours alone. There's no master switch that reads everyone, because there's no master key.
Two ways an app can get your health data.
| The usual way | The Wubs way | |
|---|---|---|
| How it reaches the app | A vendor signs an agreement with your health system — often a BAA — and your data flows to them. | You connect your own records, one source at a time. |
| Did you actually choose? | Often not. Consent is buried in paperwork you never directly signed. | Yes — you approve each connection, every time. |
| Can you see what was taken? | Rarely. | Always. Every source is listed, with where it came from. |
| Can you delete it? | Almost never. | Anytime, in a tap. |
| Can it write to your chart? | Sometimes. | Never. Read-only, always. |
| Could staff — or a breach — read across everyone? | Usually one database, one key. | No. Encrypted per person; there is no master key. |
| Do they sell it or train on it? | Check the fine print. | No. Not sold, not used to train AI. |
If you can't answer those questions about a health app, that's your answer.
Each one is a claim we'll stand behind — and the design choice that makes it true.
No master key. No bulk access.
Your health data is encrypted at rest under a key unique to you. There is no single key that unlocks everyone — so no employee, and no one who breached a database, can read across users or mine the population. Your record isn't a row in a pool; it's a locked box only your session opens.
You connect it. You can disconnect it.
Every record and device is connected by you, through your own secure portal login — we never see your password. You can see a log of what was synced, disconnect any source, and stop sharing whenever you want.
You see — and approve — every source.
Wubs shows you where each piece of information came from. When something's ambiguous, it asks instead of assuming — and anything unconfirmed is never quietly saved as fact. You're the one who decides what's true about you.
Read-only to your medical record.
Wubs can read the copy you choose to share. It can never write to, change, or send anything into your hospital's chart. When you want your care team to see a summary, you review it, edit it, and send it — on your terms.
Never sold. Never used to train AI.
We don't sell your data, and we don't train models on your records or your conversations. Your information is here to help you — not to become a product.
The lower-risk way to extend care between visits.
You don't have to underwrite another vendor holding your patients' data under an agreement your patients never really saw. Wubs is patient-mediated by design — which removes the questions that keep your privacy and security teams up at night:
- No new data-sharing surface. Data is connected by the patient, not piped to us under your BAA. There's nothing new for you to expose.
- Consent that isn't ambiguous. Each patient connects and approves their own sources.
- Read-only by construction. Nothing Wubs does can alter your record.
- No pooled-PHI honeypot. Per-person encryption means there's no central trove to lose.
- Aligned to care, not extracting from it. Wubs coaches toward the plan you already set — it never invents one.
Trusting an ecosystem of vendors to hold your patients' data responsibly is a bet you have to keep making. Choosing the one built so that bet never comes up is a decision you make once.
In the app, anytime.
Built for health data
We treat your health information with the protections it deserves, and we'll publish formal attestations here as they're completed. Until then, the guarantees above are architectural — true by construction, not by promise.