Data Processing & Sub-processors
Last Updated: October 24, 2026
1. Overview
When we build or run systems that handle personal data belonging to your customers or users, you are the data controller and Rogue Digital Ltd (Company No. 15403136) is the data processor. In that arrangement we enter into a Data Processing Agreement (DPA) that meets Article 28 of the UK GDPR, and we are transparent about the sub-processors involved. For data collected through this website, we are the controller: see our Privacy Policy.
2. Requesting Our DPA
We provide our DPA as part of an engagement so it can be reviewed and signed by both parties. To request a copy for your legal or procurement review before we start, email privacy@roguedigital.ai and we will send it over. If you have your own DPA template, we are happy to work from yours.
3. What Our DPA Covers
Our DPA sets out the standard Article 28 protections:
- Subject matter, duration, nature and purpose of the processing, and the types of data and data subjects
- Processing only on your documented instructions
- Confidentiality obligations on the people who process the data
- Appropriate technical and organisational security measures
- Terms for engaging sub-processors, with notice of changes
- Assistance with data-subject requests and with your own compliance duties
- Personal-data breach notification
- Deletion or return of data at the end of the engagement
- Information and audit rights so you can verify our compliance
4. Website Sub-processors
The third parties that may process personal data submitted through this website:
| Sub-processor | Purpose | Location | Transfer basis |
|---|---|---|---|
| Vercel Inc. | Website and application hosting, where the work includes it | United States and European Union | UK Addendum to the EU Standard Contractual Clauses, in the provider's data processing terms |
| Supabase, Inc. | Database hosting, where the work includes it | The region chosen for each project | UK Addendum to the EU Standard Contractual Clauses, in the provider's data processing terms |
| Plus Five Five, Inc. (Resend) | Sends transactional email from the applications and forms Rogue runs | United States | UK Addendum to the EU Standard Contractual Clauses, in the provider's data processing terms |
| Google LLC (Google Analytics) | Website analytics: cookies only after the visitor accepts; before that, cookieless pings with storage switched off | United States and global | UK Extension to the EU-US Data Privacy Framework |
| Google LLC (Google Ads) | Measures Rogue's Google ads; ad cookies and the ad click identifier only after the visitor accepts | United States and global | UK Extension to the EU-US Data Privacy Framework |
| LinkedIn Corporation (LinkedIn Insight Tag) | Advertising measurement and retargeting audiences, loaded only after the visitor accepts | United States | UK Extension to the EU-US Data Privacy Framework |
| Plausible Insights OÜ (Plausible Analytics) | Aggregate visit counts for every visitor, with no cookies and nothing stored in the browser | European Union | None needed: UK adequacy (EU or EEA) |
| Google LLC (Google Calendar) | Booking a call through Jamie's appointment page | United States and European Union | UK Extension to the EU-US Data Privacy Framework |
| Cloudflare, Inc. | DNS for Rogue's website domain | Global network | UK Addendum to the EU Standard Contractual Clauses, in the provider's data processing terms |
5. Engagement Sub-processors
For client engagements, the sub-processors that may process client personal data are the ones below. Which of them touch your data depends on the work, and your DPA says which. We give you notice before we add or replace one.
| Sub-processor | Purpose | Location | Transfer basis |
|---|---|---|---|
| Anthropic PBC | AI models that read and draft text for the work, used through Rogue's own Claude subscription accounts under Anthropic's consumer terms | United States | None: Anthropic's consumer terms (clause 5.4) |
| Hetzner Online GmbH | The server Rogue's agents run on | European Union | None needed: UK adequacy (EU or EEA) |
| GitHub, Inc. | Source code hosting | United States | UK Addendum to the EU Standard Contractual Clauses, in the provider's data processing terms |
| Google LLC | Email, documents and file storage (Google Workspace) | United States and European Union | UK Extension to the EU-US Data Privacy Framework |
| Vercel Inc. | Website and application hosting, where the work includes it | United States and European Union | UK Addendum to the EU Standard Contractual Clauses, in the provider's data processing terms |
| Supabase, Inc. | Database hosting, where the work includes it | The region chosen for each project | UK Addendum to the EU Standard Contractual Clauses, in the provider's data processing terms |
| Convex, Inc. | Database and backend hosting, where the work includes it | The region chosen for each project | UK Addendum to the EU Standard Contractual Clauses, in the provider's data processing terms |
| Functional Software, Inc. (Sentry) | Error monitoring for the applications Rogue builds and runs | United States | UK Extension to the EU-US Data Privacy Framework |
| Plus Five Five, Inc. (Resend) | Sends transactional email from the applications and forms Rogue runs | United States | UK Addendum to the EU Standard Contractual Clauses, in the provider's data processing terms |
| Cloudflare, Inc. | DNS, and the secure tunnel to the server Rogue's agents run on (Cloudflare Tunnel) | Global network | UK Addendum to the EU Standard Contractual Clauses, in the provider's data processing terms |
| Otter.ai, Inc. | Transcribes meetings with the Client | United States | UK Addendum to the EU Standard Contractual Clauses, in the provider's data processing terms |
AI models
Rogue's AI agents use Anthropic's Claude models through paid subscription accounts that Rogue holds with Anthropic, under Anthropic's consumer terms. Rogue does not use an Anthropic enterprise plan or a commercial API agreement for this work, and has no separate data processing agreement with Anthropic. Rogue sends client personal data to those models only where the work needs it, and keeps what it sends to the least the task needs. Whether Anthropic keeps or trains on that data follows Anthropic's consumer terms and the privacy settings on Rogue's accounts, not a commitment Anthropic has made to Rogue for the client. If a client needs enterprise or API terms for AI processing, the client tells Rogue before the work starts and Rogue says in writing whether it can meet that.
6. International Transfers
Where a sub-processor processes data outside the UK, we rely on UK adequacy regulations, the International Data Transfer Agreement or the UK Addendum to the Standard Contractual Clauses. The AI models in section 5 are the exception: Rogue has no transfer agreement with Anthropic, and data sent to them goes to the United States under Anthropic's consumer terms.
7. Contact
Questions about data processing, our DPA, or our sub-processors:
Email: privacy@roguedigital.ai
See also our Privacy Policy, Security & Trust, and Responsible AI pages.