Subprocessors
LeadArivo subprocessors
Customer Data suppliers, website recipients and customer-connected platforms have different roles. This page identifies the verified scope and the information still awaiting confirmation.
Website services and recipients
| Service | Purpose / role | Data involved | Verified scope |
|---|---|---|---|
| Google Analytics | Conditional website measurement recipient | Browser/network, page and measurement signals | Disabled by default; requires explicit configuration/enablement and Analytics permission on eligible public pages |
| Microsoft Clarity | Conditional website session-insight recipient | Browser/network and interaction signals | Disabled by default; requires explicit configuration/enablement and Analytics permission on eligible public pages |
| Cloudflare Turnstile | Form security / bot protection | Technical and security signals | Conditional on site-key configuration; no hosting or CDN claim |
| YouTube / Vimeo | External resource video players | Browser/network and playback information | Only if a resource embeds the player and Functional is permitted |
These service names identify conditional website recipients, not a verified inventory of every contracting legal entity, country, retention setting or data-processing agreement. First-party consent does not use an external consent provider. Google Tag Manager, CookieYes and arbitrary legacy CMS snippets do not run and are not active recipients in this architecture. Refer to the Cookie Policy for choices and inventory limitations.
What is not listed yet
Production hosting, database, transactional email, payment processing, error monitoring, customer-support platforms and AI model providers for the LeadArivo application are not named here because those production vendors have not been verified on this website. Local development storage (including SQLite used in development) is not a production subprocessor.
When a production vendor that processes Customer Data is confirmed, it will be added to this page. This list is not an integrations catalogue for lead sources.
Recipients of Google and YouTube user data
The Privacy Policy’s Google and YouTube section identifies TEAL Infotech as operator, authorized workspace users as recipients, Google/YouTube as the connected platform and recipient of API requests and approved public replies, infrastructure suppliers as application/database/backup processors, and the configured AI service as a recipient of comment/context inputs when AI is enabled.
The YouTube API connection is separate from an optional YouTube video player or Google Analytics on the marketing website. Enabling website Analytics does not authorize sending Google account or comment content to those measurement services.
Infrastructure and AI provider identities, processing countries, relevant data-processing arrangements and retention/training settings require confirmation before you enable processing that depends on them. Ask privacy@leadarivo.com for the current verified list. A software adapter or integration library alone is not proof of a supplier contract, geography or provider privacy setting.
Operator and customer-connected platforms
TEAL Infotech is the operator of LeadArivo, not its own subprocessor. It acts as processor for instructed Customer Data and determines purposes for its own website/account records as described in the Privacy Policy and DPA.
A platform connected by a customer, such as a messaging, advertising, mailbox or calendar service, may act independently under its own customer contract. Its role depends on the actual arrangement; an integration or development library alone does not make it a LeadArivo subprocessor. Ask for the verified Production provider/legal-entity/country/contract list and the agreed change-notice and objection process before approving relevant processing.
