DRAFT — pending legal review. This page describes how RevealWhy currently works; it is not yet a binding legal document. Questions: support@revealwhy.com.
Legal
Subprocessors
Last updated: 19 September 2026
Soulution Insights LDA uses the following subprocessors to provide RevealWhy. Integrations a customer switches on (for example Slack, Shopify, Webflow or Zapier) receive data only at that customer's instruction and are not listed here.
| Subprocessor | Purpose | Data | Location |
|---|---|---|---|
| Google Cloud (Google LLC / Google Cloud EMEA Ltd) | Hosting of the API and dashboard (Cloud Run), database (Cloud SQL), object storage, cache/queues | All customer and visitor data processed by the service | United States (us-central1) |
| Cloudflare, Inc. | Hosting of the public website (static pages) | The IP address and request details of people who load the public website | Global edge network |
| Google Gemini via Vertex AI (Google) | Language-model analysis of page structure and findings phrasing | Scrubbed page element text, page URLs without query strings, rendered page screenshots of customer pages | United States |
| Auth0 (Okta, Inc.) | Sign-in for dashboard users | Dashboard user account data (name, e-mail, login metadata) — not website visitor data | As configured for the RevealWhy Auth0 tenant |
| Resend | Transactional and digest e-mail to dashboard users who enable it | Recipient e-mail address and the digest content | United States |
| jsDelivr (CDN) | Delivery of the open-source session-replay library (rrweb) loaded by the tracking script | Visitor IP address and user agent as part of the HTTP request (no RevealWhy data is sent) | Global CDN |
| Customer-configured language-model providers (e.g. OpenAI, Azure OpenAI) | Only when a customer adds its own provider key in project settings | Scrubbed page element text and aggregated findings context | Per the customer's provider account |
Changes to this list are announced on this page before they take effect.