TalkToLeads legal

Subprocessors and Third-Party Service Providers

TalkToLeads may use carefully selected third-party providers to host systems, send communications, process payments, measure website performance, and support service delivery. This page identifies categories of providers and, where applicable, specific subprocessors.

Effective date: [INSERT EFFECTIVE DATE]
Last updated: [INSERT LAST UPDATED DATE]
Version: DRAFT-v0.1
Review status: Draft — pending legal review

Published by: [INSERT LEGAL ENTITY NAME]
Legal contact: kaurpritpal112@gmail.com

Draft policy — legal review required before accepting payment or processing client lead data.

This document is a working draft prepared for review. It is not legal advice and should not be relied on. Passages in [INSERT …] mark decisions still to be made. Current version: DRAFT-v0.1.

Statuses must be verified before publication

Every provider below is currently marked planned, optional or client-selected. No provider may be marked *Active* until it is genuinely processing data in production. This list is incorporated into Annex 3 of the Data Processing Addendum, so an inaccurate row is a contractual misstatement.

What each status means

Active: Currently in production and processing data.
Planned: Intended for future use; not processing data today.
Optional: Used only for specific engagements or features.
Client-selected: Used only where a client chooses that integration.

Provider	Service & purpose	Data categories	Location	Status	Updated
SupabasePrivacy policy for Supabase (opens in a new tab)	Database, authentication and backendStore application and workflow data; authenticate internal users	Client contact data, workflow configuration, lead and conversation data, audit logs	[INSERT REGION]	Planned	[INSERT DATE]
VercelPrivacy policy for Vercel (opens in a new tab)	Website and application hostingServe the website and application; edge and server request handling	Request metadata, IP address, technical logs	[INSERT REGION]	Planned	[INSERT DATE]
ResendPrivacy policy for Resend (opens in a new tab)	Transactional email deliverySend setup-request notifications, invoices, onboarding and service email	Name, email address, message content	[INSERT REGION]	Planned	[INSERT DATE]
WisePrivacy policy for Wise (opens in a new tab)	Invoicing and paymentIssue invoices, receive and confirm payment	Billing contact details, invoice and payment records	[INSERT REGION]	Planned	[INSERT DATE]
WhatsApp Business Platform (Meta)Privacy policy for WhatsApp Business Platform (Meta) (opens in a new tab)	Messaging channelDeliver and receive messages where a client selects WhatsApp as a channel	Lead phone number, message content, delivery metadata, consent records	[INSERT REGION]	Client-selected	[INSERT DATE]
Google AnalyticsPrivacy policy for Google Analytics (opens in a new tab)	Website analyticsAggregate website performance measurement	Pseudonymous usage events, device and browser data, referral data	[INSERT REGION]	Optional	[INSERT DATE]
Microsoft ClarityPrivacy policy for Microsoft Clarity (opens in a new tab)	Behaviour and session analyticsHeatmaps and session replay with sensitive fields masked	Pseudonymous interaction events, masked page content	[INSERT REGION]	Optional	[INSERT DATE]
Anthropic (Claude API)Privacy policy for Anthropic (Claude API) (opens in a new tab)	AI assistanceOptional internal drafting and assistant features, only where enabled	Content submitted to the assistant feature	[INSERT REGION]	Optional	[INSERT DATE]
Automation provider (Make / n8n / Pipedream)	Integration and orchestrationConnect systems within a client workflow, where such a provider is used	Lead and conversation data in transit between connected systems	[INSERT REGION]	Optional	[INSERT DATE]
CRM and calendar providers	Client-elected integrationsPass qualified lead context into the tools a client already uses	Lead contact details and qualification answers	Determined by the client’s own provider	Client-selected	[INSERT DATE]
Cloud storage, logging and monitoring providers	Operational infrastructureError monitoring, log retention and operational alerting	Technical logs, error traces, request metadata	[INSERT REGION]	Planned	[INSERT DATE]

Supabase

Planned

Service: Database, authentication and backend
Purpose: Store application and workflow data; authenticate internal users
Data categories: Client contact data, workflow configuration, lead and conversation data, audit logs
Location: [INSERT REGION]
Last updated: [INSERT DATE]

Provider privacy policy

Vercel

Planned

Service: Website and application hosting
Purpose: Serve the website and application; edge and server request handling
Data categories: Request metadata, IP address, technical logs
Location: [INSERT REGION]
Last updated: [INSERT DATE]

Provider privacy policy

Resend

Planned

Service: Transactional email delivery
Purpose: Send setup-request notifications, invoices, onboarding and service email
Data categories: Name, email address, message content
Location: [INSERT REGION]
Last updated: [INSERT DATE]

Provider privacy policy

Wise

Planned

Service: Invoicing and payment
Purpose: Issue invoices, receive and confirm payment
Data categories: Billing contact details, invoice and payment records
Location: [INSERT REGION]
Last updated: [INSERT DATE]

Provider privacy policy

WhatsApp Business Platform (Meta)

Client-selected

Service: Messaging channel
Purpose: Deliver and receive messages where a client selects WhatsApp as a channel
Data categories: Lead phone number, message content, delivery metadata, consent records
Location: [INSERT REGION]
Last updated: [INSERT DATE]

Provider privacy policy

Google Analytics

Optional

Service: Website analytics
Purpose: Aggregate website performance measurement
Data categories: Pseudonymous usage events, device and browser data, referral data
Location: [INSERT REGION]
Last updated: [INSERT DATE]

Provider privacy policy

Microsoft Clarity

Optional

Service: Behaviour and session analytics
Purpose: Heatmaps and session replay with sensitive fields masked
Data categories: Pseudonymous interaction events, masked page content
Location: [INSERT REGION]
Last updated: [INSERT DATE]

Provider privacy policy

Anthropic (Claude API)

Optional

Service: AI assistance
Purpose: Optional internal drafting and assistant features, only where enabled
Data categories: Content submitted to the assistant feature
Location: [INSERT REGION]
Last updated: [INSERT DATE]

Provider privacy policy

Automation provider (Make / n8n / Pipedream)

Optional

Service: Integration and orchestration
Purpose: Connect systems within a client workflow, where such a provider is used
Data categories: Lead and conversation data in transit between connected systems
Location: [INSERT REGION]
Last updated: [INSERT DATE]

CRM and calendar providers

Client-selected

Service: Client-elected integrations
Purpose: Pass qualified lead context into the tools a client already uses
Data categories: Lead contact details and qualification answers
Location: Determined by the client’s own provider
Last updated: [INSERT DATE]

Cloud storage, logging and monitoring providers

Planned

Service: Operational infrastructure
Purpose: Error monitoring, log retention and operational alerting
Data categories: Technical logs, error traces, request metadata
Location: [INSERT REGION]
Last updated: [INSERT DATE]

Changes to this list

We may update this list as our service providers change. Where required by law or contract, we will provide applicable notice of material changes.

Questions or objections

Clients can raise a question or object to a subprocessor under the process in the Data Processing Addendum. Write to kaurpritpal112@gmail.com, use the privacy request page, or contact the founder directly at kaurpritpal112@gmail.com.

Subprocessors and Third-Party Service Providers

Effective date

[INSERT EFFECTIVE DATE]

Last updated

[INSERT LAST UPDATED DATE]

Version

DRAFT-v0.1

Review status

Draft — pending legal review

Published by

[INSERT LEGAL ENTITY NAME]

Legal contact

kaurpritpal112@gmail.com

Draft policy — legal review required before accepting payment or processing client lead data.

This document is a working draft prepared for review. It is not legal advice and should not be relied on. Passages in [INSERT …] mark decisions still to be made. Current version: DRAFT-v0.1.

Provider

Service & purpose

Data categories

Location

Status

Updated

SupabasePrivacy policy

Database, authentication and backendStore application and workflow data; authenticate internal users

Client contact data, workflow configuration, lead and conversation data, audit logs

[INSERT REGION]

Planned

[INSERT DATE]

VercelPrivacy policy

Website and application hostingServe the website and application; edge and server request handling

Request metadata, IP address, technical logs

[INSERT REGION]

Planned

[INSERT DATE]

ResendPrivacy policy

Transactional email deliverySend setup-request notifications, invoices, onboarding and service email

Name, email address, message content

[INSERT REGION]

Planned

[INSERT DATE]

WisePrivacy policy

Invoicing and paymentIssue invoices, receive and confirm payment

Billing contact details, invoice and payment records

[INSERT REGION]

Planned

[INSERT DATE]

WhatsApp Business Platform (Meta)Privacy policy

Messaging channelDeliver and receive messages where a client selects WhatsApp as a channel

Lead phone number, message content, delivery metadata, consent records

[INSERT REGION]

Client-selected

[INSERT DATE]

Google AnalyticsPrivacy policy

Website analyticsAggregate website performance measurement

Pseudonymous usage events, device and browser data, referral data

[INSERT REGION]

Optional

[INSERT DATE]

Microsoft ClarityPrivacy policy

Behaviour and session analyticsHeatmaps and session replay with sensitive fields masked

Pseudonymous interaction events, masked page content

[INSERT REGION]

Optional

[INSERT DATE]

Anthropic (Claude API)Privacy policy

AI assistanceOptional internal drafting and assistant features, only where enabled

Content submitted to the assistant feature

[INSERT REGION]

Optional

[INSERT DATE]

Automation provider (Make / n8n / Pipedream)

Integration and orchestrationConnect systems within a client workflow, where such a provider is used

Lead and conversation data in transit between connected systems

[INSERT REGION]

Optional

[INSERT DATE]

CRM and calendar providers

Client-elected integrationsPass qualified lead context into the tools a client already uses

Lead contact details and qualification answers

Determined by the client’s own provider

Client-selected

[INSERT DATE]

Cloud storage, logging and monitoring providers

Operational infrastructureError monitoring, log retention and operational alerting

Technical logs, error traces, request metadata

[INSERT REGION]

Planned

[INSERT DATE]