Privacy & security
A front desk, not a chart.
Living Link is built so that protected health information never needs to travel through it. That isn’t a limitation we’re apologising for — it’s the design, and it’s why an office can adopt this in an afternoon.
The short version
Four answers, before you ask your office manager.
Where do patient messages go?
Into your practice’s own storage on Cloudflare, reachable only with your sign-in code or the link’s own key. They travel over HTTPS — nothing moves in the clear. They are not sold, not used to train anything, and not shared with anyone.
What if a patient types a symptom anyway?
The page asks them not to, in plain words, on the screen where they type — not in a policy nobody reads. Practice pages carry a visible notice: scheduling and general questions only, save health details for the visit.
If someone does share something clinical, treat it the way you’d treat a voicemail that went too far: move the conversation into the system you already use for that, and close the thread here. One tap closes it — it stays readable, but accepts nothing further.
Who can read a conversation?
Whoever holds your sign-in code, and nobody else. There is no public wall, no comment section, and no way for one visitor to see another’s messages. Visitors are anonymous by design: we never ask their name, email, or phone number. A conversation is identified by a random code stored in that visitor’s own browser.
What happens if we stop paying, or leave?
Your links keep working on the free plan — they don’t go dark and your window decal doesn’t become a broken address. Ask us to delete the account and the pages and their conversations go with it.
The boundary
We don’t claim HIPAA compliance. Here’s why that’s the point.
A system that handles protected health information needs a business associate agreement, audit trails, and a compliance programme behind it. Living Link deliberately sits outside that: it is the part of your practice that faces the street, answering the questions a stranger asks before they are a patient at all.
So we designed the product to keep clinical information out rather than to secure it once it’s in. Practice pages say so. The message box says so. If your workflow needs to carry PHI, use the system you already have — and let this handle everything the phone used to interrupt.
How it’s built
The parts that matter to whoever signs off.
No password database
Your account is a code you hold. We store only a one-way hash of it, so there is no password file to breach and nothing of yours to leak from ours.
Encrypted in transit
Every page, message and reply travels over HTTPS.
You can close any line
One tap ends a conversation. It stays readable and accepts nothing new until you reopen it.
We never touch money
If a page sells something, the button goes to your own payment page. Card details never reach us, and we take nothing from the sale.
No visitor tracking
No accounts, no analytics profile, no third-party pixels on your page. We collect nothing about a visitor unless they choose to type it.
Rotate at any time
Replace your sign-in code in one tap. The old one dies everywhere — useful when someone leaves the front desk.
Being straight with you
What we’re still building.
Messages are encrypted in transit but not yet encrypted at rest. Conversations don’t expire on a schedule yet. Both are on the list for offices that want the line to lock harder than it does today.
We’d rather tell you that here than have you find it out later.
See it for practices → Message a live one →
Questions an office manager needs answered? Message any of our live pages — that’s the product.