Sub-processors
The third parties that may process client data on SEMRS's behalf, and what each one can see.
Last reviewed: 7 September 2026
Current list
| Sub-processor | Why | What it sees |
|---|---|---|
| Google Workspace (Drive, Docs, Sheets, Slides) | Creating and storing client deliverables | Deliverable content, client business name |
| Google Search Console & Analytics (GA4) | Reading a client's own search and site performance | Aggregate traffic and query data from the client's own property |
| Google Ads | Managing campaigns the client has granted access to | Campaign, spend and performance data |
| Google Business Profile | Publishing and reading profile posts | Post content, profile metrics |
| YouTube | Uploading support and client video content | Video files and metadata |
| Meta (Facebook, Instagram, WhatsApp Business) | Ads management and, where enabled, lead notifications | Campaign data; lead contact details where Lead Generation is in scope |
| WordPress site (the client's own, or semrs.com) | Publishing approved content | Post content and media |
| Email delivery (Gmail SMTP) | Sending notifications, invoices and client messages | Recipient address and message content |
| Application hosting provider | Running this application and its database | All data stored by the system |
Only what you have connected
A sub-processor only ever sees data for a client who has actually connected that platform. If you have not granted Google Ads access, none of your campaign data reaches Google Ads through us.
Changes
If SEMRS adds a sub-processor that would handle client personal data, this page is updated and affected clients are told before it starts. See the Data Processing Addendum for the contractual position.
This page describes how SEMRS actually operates. It is written to match this system's documented practices rather than generic boilerplate, but it is not legal advice, and a qualified review is recommended before relying on it in a dispute.