Sub-processors
Every third party that processes data on our behalf, what they do, what they see, and where.
Effective 7 September 2026
We engage the vendors below to run Reckon. Each is bound by written terms that impose data-protection obligations no weaker than ours, and each is given only the data its function requires.
We give 30 days' notice before a new sub-processor starts processing customer data. To be notified, email privacy@supermargin.ai and ask to be added to the list.
A location shown as "Being confirmed" is one we are still verifying, not one we are withholding. Ask at privacy@supermargin.ai and we will tell you where a given vendor processes your data today.
1. Infrastructure
| Sub-processor | Function | Data it processes | Location |
|---|---|---|---|
| Cloud hosting provider | Runs the API, background worker and queue containers | Everything in transit through the application | Being confirmed |
| Managed MongoDB provider | Primary database | Accounts, workspaces, connections, advertising and creative data, creative tags, comments, saved boards | Being confirmed |
| Microsoft Azure Blob Storage | Stores the copies of your creative assets that the tagging pipeline reads | Images and video from your ad accounts | Being confirmed |
| Infisical | Secret management, holding our own service credentials and injecting them at runtime | Our API keys and encryption keys. No customer personal data | Being confirmed |
2. AI and media processing
These are the providers that see your creative and your figures. Model calls are routed across two providers so one being unavailable degrades a feature rather than stopping it, which is why the same data can reach either.
| Sub-processor | Function | Data it processes | Location |
|---|---|---|---|
| Microsoft Azure OpenAI Service | Creative tagging and clustering, report drafting, board planning, verdict narration, and answering questions in Ask | Creative images, video frames and ad copy; performance figures; comment text; your question and the conversation around it | Being confirmed |
| Google Vertex AI (Gemini) | The same tasks, as the second provider and the batch path for large tagging runs | As above, plus the YouTube watch URLs of video ads, which Gemini reads first-party | Being confirmed |
| Google AI Studio (Gemini API) | The alternative Gemini transport, used where Vertex is not configured for a batch | As above | United States |
| ElevenLabs | Speech-to-text (Scribe) for the audio of video ads | Audio extracted from your creative, or the video URL where no file exists | United States |
We do not train models on your data, and these providers are engaged on terms that do not permit them to train foundation models on the content we send.
3. Product services
| Sub-processor | Function | Data it processes | Location |
|---|---|---|---|
| Clerk | Authentication, sessions, organisations and invitations | Name, email, profile image, session and device metadata | United States |
| Resend | Transactional email and the daily brief | Recipient name and email, and the figures inside the brief | United States |
| Slack | Internal operational notifications to our team | Sign-up and workspace events, including the new user's name and email | United States |
| context.dev | Brand enrichment: reads your own public website for logo, colours, styleguide and page content when you set up a brand kit | The website address you give us and its public pages | United States |
| Egress proxy provider | Routes our requests to the public Google Ads Transparency Center for competitor research | The advertiser domains a workspace looks up. No customer personal data | Being confirmed |
4. Analytics and monitoring
| Sub-processor | Function | Data it processes | Location |
|---|---|---|---|
| PostHog | Product analytics and error capture: see the Cookie Policy | Pseudonymous user and workspace ids, feature events, page views, error traces, and recordings of app sessions | United States |
| Sentry | Error monitoring | Stack traces, request metadata, user id | United States |
| Datadog | Application performance monitoring, tracing and logs | Traces, metrics, request logs with correlation ids | United States |
5. Not sub-processors
- Meta and Google as advertising platforms. They are sources, not sub-processors: we read data from them on your instruction, under your own relationship with them. Their handling of your advertising data is governed by your agreements with them.
- Redis. The queue and cache run inside our own infrastructure, not on a third-party service.
- Our own affiliates. Zu Technologies group companies that support the product are bound by the same obligations and are not separately listed.
6. Objecting to a sub-processor
If you have a reasonable data-protection objection to a new sub-processor, tell us within 30 days of the notice at privacy@supermargin.ai. We will work with you to find an alternative; if we cannot, you may terminate the affected part of the service without penalty.