Plain-English policy

Privacy at ClinicGreet.

This page says what actually happens to information you share with ClinicGreet—on this website, by email, in a public concept, and in a clinic deployment. It is written to be checked, not skimmed past.

The short version

This website sets no cookies and runs no on-page analytics or advertising trackers. Some one-to-one business outreach uses a random recipient-specific ClinicGreet link to count concept-link requests. The launch-request form works in your browser and sends us nothing until you choose to send an email. Email you send is used to reply and scope your launch—never sold or shared for marketing. Public clinic concepts use public business facts and synthetic patient scenarios. Clinic deployments get their own written data scoping before launch.

This website

clinicgreet.com is a static site. It sets no cookies and loads no analytics, advertising, or tracking scripts. It is served through Cloudflare, which processes standard request logs—such as IP address and browser type—to deliver and secure the site.

The pilot-request form

The form on the homepage builds an email draft in your browser. The details you type—clinic name, work email, coverage priority, booking path, start window—stay in your browser until you choose to open and send that draft from your own email app. Nothing is submitted to a server in the background. Please don’t include patient names, symptoms, appointment details, or other health information.

Email

Email sent to hello@clinicgreet.com lands in our business mailbox. We use it to reply, scope pilots, and run the engagement you asked about. We do not sell it, rent it, or share it with third parties for their marketing. If you want something you sent corrected or deleted, email us and we will do it.

One-to-one outreach link measurement

Some business outreach emails include a random, recipient-specific link on go.clinicgreet.com. When that link is requested, we record the request time and type, a coarse country, a broad client category, the referring host when available, Cloudflare’s request identifier, and a keyed network fingerprint used for deduplication and delivery diagnosis. We do not set cookies or store the raw IP address or full user-agent string for this measurement. New outreach messages do not use open pixels.

An observed request does not prove that a particular person clicked the link. Corporate security scanners and link previews can request it automatically. ClinicGreet reports all observed requests separately from high-confidence user-initiated browser navigations, but neither category proves identity. A direct reply or opt-out remains the reliable signal. Reply “no thanks” to an outreach email and we will stop contacting that route.

Public concepts and website demos

Public concepts use facts published on a clinic’s official website and synthetic patient scenarios. They are clearly labeled as unofficial, do not make real appointments, and should not be used to submit patient names, symptoms, appointment details, or other health information.

Clinic pilots and PHI

Production deployments are scoped per clinic, in writing, before launch: what the concierge may ask, what it must decline, which vendors touch submitted data, what is retained and for how long, access controls, and any BAA requirements. ClinicGreet does not provide medical advice, diagnosis, treatment, or clinical triage. The default workflow captures an appointment request and tells the visitor it is not confirmed until staff follows up.

Your choices and changes

Ask us what we hold from you, or ask us to delete it: hello@clinicgreet.com. If this policy changes, we will update this page and its effective date.