Back to Legal & Trust Centre
Subprocessors
Public summary of the subprocessors ANCHOR may use.
- Status
- Public summary
- Version
- v1.0
- Stage
- Contract-adjacent summary - agreement controls
- Last updated
- 15 June 2026
This is a public summary of the subprocessors ANCHOR may use. Entries marked conditional, future candidate, or to be confirmed are not active by default. The signed data processing agreement and customer agreement control.
Vercel
active- Purpose
- Frontend hosting and deployment
- Possible data categories
- Public website delivery; request metadata and logs possible
- Region / transfer status
- Hosting region not asserted here; confirmed in the data processing agreement
- Notes
- Hosts the public ANCHOR frontend.
Render
active- Purpose
- Backend and API hosting
- Possible data categories
- Governance metadata processed server-side
- Region / transfer status
- Hosting region not asserted here; confirmed in the data processing agreement
- Notes
- Hosts the production backend and API.
Managed database provider
to be confirmed- Purpose
- Backend data persistence
- Possible data categories
- Governance metadata persisted for the backend
- Region / transfer status
- Not asserted here; to be confirmed from the deployment architecture
- Notes
- A managed database provider supports backend persistence; the specific provider is to be confirmed from the deployment architecture.
Anthropic
conditional- Purpose
- AI generation provider (live Workspace generation)
- Possible data categories
- Transient prompt and output routing, only if live generation is enabled
- Region / transfer status
- Not asserted here; addressed before any live generation with real data
- Notes
- Relevant only if and when live Workspace generation is enabled. Live generation is production-off by default; Anthropic becomes a subprocessor only when it is enabled and the legal and subprocessor documentation supports it.
ImprovMX
active- Purpose
- Inbound email forwarding and contact routing
- Possible data categories
- Sender email address, recipient alias, and message headers and content as part of a forwarded email
- Region / transfer status
- Region and transfer position not asserted here; subject to provider terms and data processing agreement review
- Notes
- Used for inbound domain email forwarding and contact routing only, supporting public aliases including hello, support, security, privacy, legal, and procurement. It is not app transactional email, has no SMTP or send-as integration, and has no ANCHOR backend email integration.
Analytics or cookie provider
to be confirmed- Purpose
- Website analytics or marketing
- Possible data categories
- None identified in this frontend review
- Region / transfer status
- Not applicable unless implemented
- Notes
- No analytics or cookie provider was identified in this frontend review.
Stripe
future candidate- Purpose
- Future candidate payment processor for billing and payment foundations (M5.8)
- Possible data categories
- Payment and billing data, only if and when billing is activated
- Region / transfer status
- Not applicable unless activated
- Notes
- Future candidate payment processor for billing and payment foundations. Not active. ANCHOR does not currently process customer payment data through Stripe, and Stripe is not currently used for ANCHOR customer billing. Activation is subject to security, legal and commercial, pricing, VAT and accounting, cancellation and refund, and founder-approval gates.
How to read this register
- This subprocessor list is a public summary.
- The signed data processing agreement and customer agreement control.
- A subprocessor change-notice process may be added later.
Important notice
ANCHOR helps clinics evidence responsible AI governance practices. It does not make a clinic compliant with any law or professional standard, and it does not replace veterinary judgement. These pages are prepared for transparency and solicitor review and are not legal advice.