The services behind HyperCRM

Always active

These three run on every HyperCRM deployment. Without them there is no application.

• Neon — the PostgreSQL database. This is where your practice data lives: patients, appointments, clinical notes, invoices and staff accounts.
• Vercel — hosting and compute for the application itself, and Vercel Blob for stored files. Patient documents, imaging and 3D scans are held in Blob's private storage and served only through short-lived signed links.
• Google (Firebase) — account authentication. Firebase verifies the identity behind each sign-in; it handles account identifiers such as email, not clinical records.

Active only when a practice turns them on

These are opt-in. When their credentials are not configured, the feature is simply skipped, so a deployment that does not use a channel never sends data to its provider.

• Twilio — SMS appointment reminders. Processes the recipient's phone number and the reminder text. Active only where SMS reminders are configured.
• Brevo — transactional email: appointment reminders and messages from the contact form. Processes the recipient's email address and the message body. Active only where email is configured.
• Google (reCAPTCHA) — bot protection on public booking and form pages. Processes visitor interaction signals to tell a person from a script. Active only where reCAPTCHA is enabled.
• OpenAI — the in-app assistant. Processes what a member types to it, and the practice records it reads or writes in order to answer — which can include patient details, appointments, clinical notes and invoices. This is the only provider on this page to which clinical content is sent in the ordinary course of a feature working, so it is worth reading twice. Active only where the assistant is configured; where it is not, no request is ever made and the assistant does not appear in the product at all.

This website, and not the product

One entry on this list has nothing to do with your patients. It is here because leaving it off would make the list incomplete, not because it touches clinical data.

• Google (Analytics via Tag Manager) — visitor analytics on hypercrm.app itself: which of our pages get read. It runs on this marketing website only. It is not present in the application, it never sees a patient, an appointment or a note, and nothing is set until a visitor accepts the cookie banner — before that the tag loads in a mode that stores nothing. Your practice's own website, generated by HyperCRM, carries analytics only if you add them yourself.

Active once your practice pays us

• Stripe — subscription billing. Processes your practice's billing contact details and its payment method, and issues your invoices. Card details are entered on Stripe's own payment page and are held by Stripe, not by us: we never receive a card number. What we do receive is a card fingerprint — an opaque token that identifies a card without revealing it — which our referral programme compares between referrals to catch a practice referring itself for the reward. The privacy policy sets out that use, its lawful basis and how long each signal is kept. Nothing reaches Stripe while a practice is on the free trial.

What this page does not claim

This list is drawn from what the software actually connects to. It does not, by itself, assert the data-centre region each provider runs in, nor which certifications a provider holds — those are stated only where they are confirmed facts rather than assumptions. The security page covers how HyperCRM protects data inside its own boundaries; if you need something in writing for your own compliance, get in touch.

Every sub-processor