These are the providers PatientPulse uses to process personal data on behalf of clinics under our Data Processing Agreement. Each is bound by written data protection terms. We email each clinic's account owner at least 30 days before we add or replace one, and update this page at the same time.
Providers that process patient data for clinics
Railway
- What they do for us: Hosts the PatientPulse application and its database.
- Data involved: All clinic data held in PatientPulse, including enquiries.
- Where: United States (US West region).
Cloudflare
- What they do for us: Stores encrypted off site backups of the database (R2 storage).
- Data involved: A full copy of the database, kept on a rolling basis of about 30 days while backups run normally.
- Where: Cloudflare R2 storage, not restricted to a European Union location. Cloudflare is a United States company.
Resend
- What they do for us: Sends email (enquiry alerts to your team, sign in links, and the results copies, availability emails and consultation quotes that go to patients) and receives the website form messages you choose to forward to your PatientPulse address.
- Data involved: The contents of those emails, including patient contact details and enquiry details.
- Where: Email is sent and received in the European Union (Ireland). Resend is a United States company, so its staff may access data from the United States.
OpenAI
- What they do for us: Interprets the words a visitor types into AI Search, so the Treatment Finder can show matching treatments. Also provides Codex, an AI assistant our administrator directs to help support, test, secure and maintain PatientPulse, which can open our administration pages.
- Data involved: For AI Search, only the typed wording and, if one follow up question is needed, the answer with the earlier structured result. Those requests are sent with storage disabled and PatientPulse does not store the wording. OpenAI states that API data is not used to train its models by default and may be kept in abuse monitoring logs for up to 30 days. For Codex, whatever an administration page it opens shows, which can include clinic account details, patient contact details and enquiry details.
- Where: United States.
Anthropic
- What they do for us: Provides Claude, an AI assistant our administrator directs to help support, test, secure and maintain PatientPulse. It can open our administration pages.
- Data involved: Whatever an administration page it opens shows, which can include clinic account details, patient contact details and enquiry details.
- Where: United States.
Cloudinary
- What they do for us: Delivers before and after treatment images already stored on a clinic account. Uploading new images is not currently available.
- Data involved: Those images, which can show a patient.
- Where: Outside the UK.
Google Workspace
- What they do for us: Hosts our email inboxes (hello@, support@ and privacy@patientpulse.co).
- Data involved: Anything a clinic or patient sends us in a support or privacy request, which can include enquiry details.
- Where: Google data centres, which may be outside the UK.
Providers that do not process patient data
These providers are part of how PatientPulse runs, but they receive no patient or enquiry data, so they are not sub-processors under the Data Processing Agreement.
- Polar: payment provider and merchant of record for clinic subscriptions. It never receives patient data.
- Google Analytics, Google Ads, Meta and LinkedIn: measurement of our own marketing on patientpulse.co and our sign up pages, only with consent. They are never loaded by the Treatment Finder on a clinic website and never receive patient data.
- SiteGround: hosting for our marketing website, patientpulse.co.
- Google Business Profile and Google Places: review sources a clinic can choose to connect. They send review information to us; we do not send them patient data.
Services that handle no personal data at all, such as uptime checks of our public pages, are not listed.
Questions and objections
Write to privacy@patientpulse.co. How to object to a new sub-processor is set out in section 7 of the Data Processing Agreement.