Subprocessors
This page lists the third-party providers ("subprocessors") that ClinicPage uses to operate its service and process personal data on behalf of clients. We maintain this page to satisfy GDPR Article 28 transparency obligations and equivalent obligations in other jurisdictions.
For more detail on our data-handling, see our Privacy Policy. For our contractual relationship with clients, see our Terms of Service.
Current Subprocessors
| Subprocessor | Purpose | Data processed | Location | Safeguards |
|---|---|---|---|---|
| Netlify, Inc. Privacy Policy · DPA |
Static site hosting; serverless functions; form delivery for clinic lead forms | Site visit logs (IP, user agent), form submissions in transit, hosted HTML/CSS/JS files | United States; EU edge | EU SCCs; DPA available; ISO 27001 |
| Cloudflare, Inc. Privacy Policy · DPA |
CDN, DNS, edge functions, hosting (migration in progress / planned) | Cached static content, DNS queries, edge request logs (IP, user agent) | Global edge network; HQ in United States | EU SCCs; DPA available; ISO 27001, SOC 2 |
| Cloudinary Ltd. Privacy Policy · DPA |
Image storage, transformation, CDN delivery for clinic sites | Uploaded images (clinic logos, doctor photos, before/after with consent, interior photos); access logs | Israel and United States (AWS) | EU SCCs; DPA available; ISO 27001, SOC 2 |
| Google LLC / Google Ireland Ltd (Workspace — Sheets, Apps Script, Gmail) Privacy Policy · Workspace DPA |
Content management (clinic site content lives in a per-client Google Sheet); backend automation; operational email | Clinic content (text, image URLs, settings); operator email correspondence; Apps Script execution logs | United States (Google data centers globally) | EU SCCs; Google Workspace DPA; ISO 27001, ISO 27017, ISO 27018, SOC 2 / 3 |
| Google LLC (Google Analytics 4) Privacy Policy |
Aggregate analytics on clinic sites and clinicpage.online — loaded only after explicit visitor consent | Truncated IP, user agent, page-view events, conversion events (clicks, form submits) | United States; EU options where configured | EU SCCs; EU-US Data Privacy Framework; visitor consent required |
| Cal.com, Inc. Privacy Policy |
Optional doctor-booking embed on clinic sites — loaded only when a visitor clicks "Book" | Booking details (name, email, time slot) provided by the patient at booking | United States | EU SCCs available; patient-supplied data |
| Calendly LLC Privacy Notice |
Optional doctor-booking embed alternative to Cal.com — loaded only on click | Booking details provided by the patient at booking | United States | EU SCCs available; patient-supplied data |
| SociableKit Inc. Privacy Policy |
Embeddable Google Reviews widget (clinic sites only; not used on clinicpage.online) | Public Google review content (no patient personal data) | Philippines and United States | Publicly available data; no patient PII transferred |
| Meta Platforms, Inc. (WhatsApp) Privacy Policy |
Click-to-chat WhatsApp links on clinic sites and clinicpage.online — visitor initiates contact, only then is data transmitted to Meta | Phone number, message content (controlled by visitor and clinic/operator) | United States; global infrastructure | Meta's standard cross-border data transfer mechanisms |
| Payment processor (To be confirmed at launch — typically Stripe or Razorpay) | Card processing and billing | Card details (tokenized by provider, never stored by ClinicPage), billing name, email, address | Provider-dependent | PCI-DSS; provider's own DPA and SCCs |
Notice of Changes
We may add, remove, or replace subprocessors as our service evolves. When we make a material change — typically a new provider that processes client or patient personal data — we update this page with the new "Last updated" date and notify clients by email at least 10 days before the change takes effect, except where a change must be made urgently for security or legal reasons.
Subscribe to Updates
If you would like to be notified directly of subprocessor changes, email us with the subject "Subprocessor updates — subscribe":
Object to a Subprocessor
If you are a current client and you object to a newly added subprocessor on reasonable data-protection grounds, contact us within 10 days of the notice. We will work with you in good faith to find a path forward — typically by helping you migrate off our service if no alternative configuration is workable. Pending resolution, we will not begin sharing your data with the new subprocessor.