1. Overview
HighAdsROI uses the sub-processors below to deliver the service. Customer end-user data does not leave the customer's GCP project; sub-processors only see metadata (e.g. service health, billing) or website-visitor data (demo requests).
2. Current sub-processors
| Provider | Purpose | Data | Region |
|---|---|---|---|
| Google Cloud Platform | Customer data plane (Firestore + BigQuery + Cloud Run) | Customer end-user events (hashed PII), processed inside customer GCP project | Sydney / Tokyo / Singapore (customer choice) |
| Cloudflare | CDN, DDoS protection, Workers, Pages hosting | IP, request metadata, WAF logs | Global edge |
| HubSpot | CRM and demo request workflow | Demo form submissions (name, email, company, role, market) | United States |
| Slack | Internal team notifications | No PII. Aggregated counts only | United States |
| Sentry | Error monitoring | Stack traces (PII scrubbed); session IDs | United States |
| Stripe | Subscription billing (customers only) | Billing contact and payment instrument | United States |
3. Notification of changes
We notify customers at least 30 days in advance of any new sub-processor (or material change to an existing one). Notification channels:
- Email to your designated DPO contact.
- This page is the canonical source — diff-able via the version number above.
- Customers may object during the 30-day window; we work in good faith to find an alternative.