1. Providers and roles
A supplier's exact role depends on the service and contract. Connected Google services, independent payment activities and customer-selected destinations are not automatically all ConvertAI subprocessors. Verify the register against the actual contracts and processing configuration. Public provider terms are not evidence that our account has entered into a particular agreement, regional arrangement or transfer safeguard.
| Provider / category | Use and information | Location / contract status |
|---|---|---|
| OVHcloud | Production application, configured database/storage and same-server deployment backups. Self-hosted PostgreSQL, Redis and MinIO are software components, not evidence of separate cloud suppliers. | France, confirmed by the operator. The exact contracting entity, provider-managed copies and applicable agreement still require verification. |
| Vercel | Frontend hosting and request delivery/proxy infrastructure, including relevant request metadata. | Actual regions, subprocessors and contract/transfer safeguards require confirmation. |
| OpenAI | API processing for selected AI features; bounded reporting aggregates/public excerpts for reviews and feature-specific supplied context for conversational/setup tools. | No UK-only or Zero Data Retention claim. Account settings, contract, processing regions and transfer safeguards require confirmation. |
| 20i / Stackmail | Configured outgoing platform email and authorised lead notifications/digests through smtp.stackmail.com. | Mailbox location, provider retention and the applicable agreement must be verified. Provider terms do not establish that every mailbox or copy is UK-only. No new email is enabled by publishing this register. |
| Stripe, optional integration | Payment/billing processing where enabled. An available integration does not establish current use or the absence/deletion of historical records. | Only applicable to services actually used. Role, locations and retention depend on the agreement. Manually invoiced services remain separate. |
| Google connected APIs | Customer-authorised reporting, selected Ads features and explicitly bound Business Profile locations. | Connected-service/data-source role and Google terms apply. Not a claim of OAuth verification, Ads developer approval or Business Profile API approval. |
| Customer-configured delivery and collaboration recipients | Customer-chosen CRM/email destinations and separately authorised specialist fulfilment. | Identify in the customer's processing schedule and access records; not a universal default destination. |
2. Questions and proposed changes
Contact hello@convertai.one for the actual processing schedule, supplier details or a concern about a proposed supplier. Required authorisation, change notice and objections must follow the executed agreement. This register is not a substitute for those arrangements.