SITE AUDIT PRO
SUB-PROCESSORS
Last updated: 4 November 2026
ABOUT THIS LIST
Veam Studios Ltd is the controller for Site Audit Pro account data. This page lists the third parties that receive customer personal data when we run Site Audit Pro. Our Privacy Policy explains how we use your data and the safeguards that apply when data leaves the UK.
Where a location lists more than one region, the provider offers a choice of region. We update this page when the list changes, and the date above shows the last update.
To ask a question about this list, including which region applies to your account, email support@veamstudios.com.
PROCESSORS
These providers process data on our behalf and on our instructions.
| Name | Purpose | Data | Location |
|---|---|---|---|
| Anthropic | AI models used by our team's internal operations tooling | When staff use it: project titles, addresses, auditor names, issue titles and thumbnail links | Stored in the US; processing may run elsewhere unless limited to the US |
| GitHub | Code hosting and support issue tracking | Support request details (message text, email address and user ID) | US (AWS), plus Azure in Canada, Chile and Mexico |
| Google Cloud / Firebase | Hosting, database, file storage, sign-in, backend functions, PDF and export processing, crash reporting, performance monitoring, push notifications and (with consent) app analytics | Account and audit data (projects, photos, reports, exports); app diagnostics with user ID and device information | US (database, file storage, backend and sign-in); Belgium (PDF and export processing) |
| Google Docs / Workspace | Internal documents, including support material | Support content users send us | Set per Workspace account: US, Europe or no preference |
| iubenda | Consent records and privacy policy hosting | App installation ID and consent choices | Ireland (AWS) and Germany (MongoDB Cloud) |
| Notion | Internal documentation, Enterprise enquiry and billing records, support notes | Enterprise contacts and support content | US by default; Europe and Asia regions offered |
| OpenAI | AI models used by our team's internal operations tooling; ad-conversion measurement | When staff use it: project titles, addresses, auditor names, issue titles and thumbnail links. Ad measurement: page views on our website (page path and title) and purchase events (event ID, type, time and plan) | Set per project: US, Europe and other regions |
| PostHog | Product analytics and session recordings in the Enterprise Console | User ID, email address, usage events and session recordings of Console screens | EU host |
| Resend | Transactional emails (invitations, password set-up, export links) | Name, email address and links | Ireland (EU sending region) |
| RevenueCat | In-app subscription status | User ID and purchase records | US |
| Slack | Team communication, including handling support requests and Enterprise enquiries | Support content users send us | US by default; data residency regions offered |
| Zendesk | Customer support tickets | Anything a user sends to support (name, email, messages, attachments) | Set per account: US, EEA, UK, Japan or Australia |
INDEPENDENT CONTROLLERS
These set their own terms for the data they receive, so they are not our processors. Each one’s own privacy policy applies.
| Name | Purpose | Data | Location |
|---|---|---|---|
| Apple | In-app purchases and receipt verification | Purchase receipts | Set by Apple under its own terms |
| Google Play | In-app purchases on Android | Purchase records | Set by Google under its own terms |
| Meta | Advertising measurement on our marketing website and in the consumer iOS app, only after consent | Ad events and device identifiers; no audit content | US |
| Paddle | Merchant of Record for website and Enterprise purchases | Billing contact and payment details | Entities in the UK, US, Ireland and Canada; may use processors worldwide; no hosting location published |