Sub-processors
Confirmed third-party services and connected platforms visible in the supplied Haplo front-end files.
Last updated: 30 June 2026
Confirmed services visible in the supplied front-end files
| Service | Purpose | Data involved |
|---|---|---|
| Google Analytics / Google Tag | Optional website analytics after cookie consent. | Website usage data and device/browser information. |
| EmailOctopus | Launch-list sign-up form when the user loads or submits it. | Email address and related sign-up metadata. |
| Jotform | Feedback form opened from the feedback link. | Name, email and feedback provided by the user. |
| WordPress, Webflow, Shopify or Sanity | User-selected CMS destination for draft creation. | CMS request data and generated draft content sent to the selected platform. |
Services to confirm before full launch
The supplied HTML references keyword research, Google Ads settings, SERP data and LLM usage, but it does not name every backend provider. Before public launch, add the confirmed hosting provider, AI model/API provider, keyword-volume provider, SERP provider, email provider and any logging or monitoring tools used by the backend.
Do not publish a final sub-processor list that names providers unless those providers are confirmed in the backend or supplier contracts.