Current list
The table below reflects the subprocessors engaged as of the date above. Some are engaged only when a customer opts into the relevant feature (for example, Anthropic is used only when AI features are enabled). The Cloudflare lead pipeline and Attio process prospect data submitted through markst.com; neither holds Verus platform data.
| Subprocessor | Purpose | Data categories | Location | Transfer basis |
|---|---|---|---|---|
| Cloudflare, Inc. | CDN, DNS, TLS termination, bot management (Turnstile), cookie-free web analytics, static hosting for markst.com, and the Pages Functions, D1 database and R2 storage behind the demo-request, NDA-signing and article endpoints | Request metadata, IP address, user-agent, access logs; Turnstile challenge tokens; where submitted via /book-demo, the lead fields (name, work email, firm, role, AUM bracket, notes, NDA-ack timestamp) and signed NDA envelopes | Global edge; control plane US | Cloudflare DPA + EU SCCs + UK IDTA Addendum |
| Amazon Web Services (AWS) | Hosting for the Verus application: compute, encrypted block storage for the database and file store, encrypted object-storage backups, parameter store for secrets, logging and alarms. Amazon Bedrock serves the in-app assistant (Anthropic Claude models operated by AWS, routed within UK/EU regions) | All platform data (at rest and in transit) | UK (eu-west-2) by default; EU (eu-central-1) or US (us-east-1) by agreement at contract time | AWS Data Processing Addendum + EU SCCs / UK IDTA Addendum where control-plane metadata leaves the UK |
| Google LLC (Google Workspace) | Transactional email for the Verus platform via the Google Workspace SMTP relay (verification codes, password resets, welcome and notice emails) and for markst.com via the Gmail API (demo-request confirmations, NDA delivery, prospect follow-up). The Workspace tenant also hosts company email and provides single sign-on into our vendor consoles | Recipient email address and message content; correspondence sent to markst.com mailboxes | Global (Google data centres); control plane US | Google Cloud / Workspace DPA + EU SCCs + UK IDTA Addendum |
| Anthropic PBC | Large-language-model inference via the Anthropic API for deal extraction, borrower research (web search) and the Ask Verus assistant, only when AI features are enabled by the customer | Prompt contents (excerpts of deal documents, borrower names, user questions); not used to train Anthropic models under the commercial API terms | United States | Anthropic DPA + EU SCCs + UK IDTA Addendum |
| GitHub, Inc. | Source-code hosting, CI/CD workflows, dependency and code scanning, deploy automation | Engineering artefacts only — no customer data | United States | GitHub DPA + EU SCCs + UK IDTA Addendum |
| Stripe Payments UK Ltd. | Subscription billing, invoicing, payment processing | Billing contact, payment instrument metadata (Stripe holds PAN; we never see it) | UK / EU | Stripe DPA |
| Attio Limited | CRM for prospects and demo requests: contact records, outreach-sequence state and follow-up notes for the markst sales pipeline. Holds no Verus platform data | Prospect contact details (name, work email, firm, role) and outreach history | United Kingdom (entity); platform hosted on Google Cloud, contracted through Google Cloud EMEA (Dublin); sub-processor chain in the US and EU per the Attio DPA | Attio DPA + EU SCCs + UK IDTA Addendum |
Changes in this revision
Revised 26 September 2026. Four entries changed:
- Added: Google LLC (Google Workspace). Transactional email now runs through our Google Workspace tenant. This replaces Resend, Inc., which has been retired and receives no data.
- Added: Attio Limited. CRM for demo-request and prospect follow-up. Marketing pipeline only; no Verus platform data.
- Removed: Sentry. Never engaged. Error telemetry stays in the Verus application log inside our AWS region.
- Amended: Amazon Web Services. Wording updated from planned to live hosting, with Amazon Bedrock noted as the in-region model host for the in-app assistant.
The objection window under the policy below runs from the date of the customer-contact email for this revision.
Change-notice policy
Commitment. markst will notify customer contacts at least 30 calendar days before a new subprocessor is engaged in production or an existing subprocessor is replaced, except where a shorter notice period is strictly required by security, legal, or force-majeure circumstances — in which case we will notify as soon as reasonably possible and explain why the standard window could not be honoured.
Channels. Notifications go out via two channels:
- Email to your designated customer contact. The contact(s) named on your order form receive a direct email summarising the change: subprocessor name, purpose, data categories, region, transfer mechanism, and go-live date.
- Update to this page. The table above is updated at the same time; the Last updated stamp is bumped. The page ships with a diff log on request.
Subscribe. To be added to the notification list (beyond your order-form contacts), email dpo@markst.com with the subject line Subprocessor change-notice subscription and the email address(es) to add. Subscription is free; removal on request.
Emergency changes. If a security incident, a sub-processor breach, or a sudden vendor-continuity event forces a replacement inside the 30-day window, we will (a) make the change, (b) notify you immediately, (c) publish a post-hoc rationale within five business days, and (d) preserve your objection rights under §3 below on a prospective basis.
Objection
Customers with a signed DPA may object to a new subprocessor on reasonable grounds within the notice period. We will work in good faith to address the concern (for example by isolating the affected customer tenant from the new subprocessor, or by identifying an alternative) or, as a last resort, allow termination of the affected service with a pro-rata refund of pre-paid fees.