Now onboarding agencies in the USA, Australia, New Zealand, Singapore and the UAE.

TalkToLeads

TalkToLeads legal

Privacy Policy

TalkToLeads respects your privacy. This Privacy Policy explains how we collect, use, store, share, and protect personal data when you visit our website, pay for a plan, become a client, or interact with a TalkToLeads workflow.

Last updated
24 October 2026
Version
DRAFT-v0.1
Review status
Draft — pending legal review
Published by
Pritpal Kaur
Legal contact
pritpalkaur112@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.

TalkToLeads installs and maintains lead-response, qualification, routing, human-handoff and follow-up workflows for service businesses. We are not a CRM, a marketing agency, or a lead vendor.

Detail
Legal entity
Value
Pritpal Kaur
Detail
Entity type
Value
Sole proprietor
Detail
Country of establishment
Value
India
Detail
Legal contact
Value
pritpalkaur112@gmail.com
Detail
Privacy / grievance contact
Value
pritpalkaur112@gmail.com
Detail
Founder (direct)
Value
pritpalkaur112@gmail.com

Pending confirmation

Entity name, entity type, registered address and the official contact addresses must be confirmed before this policy is published. Some jurisdictions also require a named Grievance Officer or Data Protection Officer — see section 16.

This policy applies to personal data relating to:

  • Website visitors — anyone browsing talktoleads pages.
  • Checkout visitors — businesses that give a work email and agency name at checkout but have not yet paid.
  • Clients and business contacts — the people at a client business we work with.
  • Leads and customers of a client — individuals whose enquiries pass through a workflow we operate for that client.
  • Employees and contractors — our own personnel, where relevant to service delivery.

Two different relationships

Where we handle a client’s lead and customer data, we generally do so on that client’s behalf and under their instructions, governed by our Data Processing Addendum rather than by this policy alone. Section 6 explains the split. If your enquiry went to a business that uses TalkToLeads, that business — not TalkToLeads — is normally the organisation responsible for your data.

We collect different categories of data for different reasons. Retention approaches below are summaries — section 10 has the detail.

Data category
Website usage and cookie data
Examples
Cookie preferences, page views, CTA clicks, form-progress metadata, device and browser data, referral and UTM information
Why collected
Operate the site, understand performance, remember your privacy choices
Source
Your browser, subject to your consent choices
Retention approach
Per cookie duration — see Cookie Policy
Data category
Onboarding submission
Examples
Full name, business name, work email, phone, website URL, industry, country and time zone, monthly lead volume, current lead sources, current tools, team size, described challenge, launch priority, consent ticks, and the privacy and terms versions you accepted
Why collected
Review whether a request fits our standard implementation scope, and respond to you
Source
Submitted by you on the onboarding form at /onboarding
Retention approach
[INSERT RETENTION — ONBOARDING SUBMISSIONS, IN MONTHS] for requests that do not become clients
Data category
Checkout enquiry
Examples
Work email and agency name, entered at the first step of the checkout page before any payment is made
Why collected
Let you resume checkout, and follow up if you do not complete it
Source
Entered by you on /checkout
Retention approach
[INSERT RETENTION — UNCONTACTED LEADS, IN MONTHS]
Data category
Google sign-in profile
Examples
Email address, display name and profile picture URL, received from Google when you sign in to the client portal
Why collected
Create and authenticate your portal login
Source
Google, when you choose to sign in with it
Retention approach
Until you ask us to delete the account
Data category
Website chat messages
Examples
What you type into the chat widget, and the reply it produces
Why collected
Answer your question on the site
Source
You, in the chat widget
Retention approach
not retained by us — see below
Data category
Privacy request records
Examples
Your name, email, organisation, the request you made, the reference we issued and the response deadline we recorded
Why collected
Handle the request, and evidence that we handled it within the deadline
Source
Submitted by you on /contact-privacy
Retention approach
[INSERT RETENTION — PRIVACY REQUEST RECORDS, IN YEARS]
Data category
Account and client-contact data
Examples
Named contacts, roles, routing owners, business addresses, communication preferences
Why collected
Deliver and support the contracted service
Source
Provided by the client during onboarding
Retention approach
Term of service, then per contract and law
Data category
Billing, invoice and payment-confirmation data
Examples
Invoice references, amounts, payment confirmation records, billing contact details
Why collected
Request and confirm payment, issue invoices for the monthly fee, meet accounting and tax obligations
Source
You, and our payment provider
Retention approach
As required by applicable tax and accounting law
Data category
Client onboarding and workflow data
Examples
Lead sources, team structure, qualification requirements, approved message templates, routing rules, integration metadata, system configuration
Why collected
Build, test, launch and maintain the agreed workflow
Source
Provided by the client
Retention approach
Term of service, then per the DPA
Data category
Client lead / customer conversation data
Examples
Lead names, phone numbers, email addresses, enquiry messages, lead source, qualification answers, conversation activity, routing and handoff records
Why collected
Operate the workflow the client has instructed us to run
Source
The client’s own lead sources and channels
Retention approach
Per client instructions and the DPA
Data category
Consent and opt-out records
Examples
Records of consent captured, opt-out and suppression signals, timestamps
Why collected
Honour choices and evidence that they were honoured
Source
Leads, clients, and website visitors
Retention approach
Retained as long as needed to keep honouring the choice
Data category
Communications with us
Examples
Emails, messages, and notes from calls with our team
Why collected
Answer enquiries, support clients, keep an account history
Source
You
Retention approach
[INSERT PERIOD]
Data category
Support-ticket data
Examples
Issue descriptions, screenshots and logs you send us, resolution notes
Why collected
Diagnose and resolve issues, track recurring problems
Source
Client contacts
Retention approach
[INSERT PERIOD]
Data category
Employee and internal account data
Examples
Work identity, login and audit activity, client and project assignments
Why collected
Operate our internal systems securely and control who can access what
Source
Our own personnel systems
Retention approach
[INSERT PERIOD]
Data category
Security and audit logs
Examples
Access records, administrative actions, error and abuse signals
Why collected
Protect systems, investigate incidents, prevent fraud and abuse
Source
Generated by our systems
Retention approach
[INSERT PERIOD]

Website chat

The chat widget on this site is answered by Claude, a model operated by Anthropic. What you type is sent to Anthropic to produce the reply. We do not keep the conversation: app/api/chat/route.ts records that a question was answered and which source answered it, never the message text. [LAWYER: confirm the wording describing Anthropic’s commercial terms — specifically that inputs and outputs are not used to train models, and whether that statement needs qualifying.]

Please do not put personal data in the chat

It answers questions about the service. Use the privacy and requests page for anything involving your own data.

Cookie and consent categories

These are the four categories the banner offers, exactly as lib/consent.ts defines them. Everything except the first is off until you switch it on, and rejecting never restricts access to the site.

Category
Essential
What it covers
Required to run the website, keep it secure, and remember the privacy choice you make here. These cannot be switched off.
Default
Always on — the site cannot run without it
Category
Analytics
What it covers
Aggregate measurement of how the site performs — which pages are read and where visitors arrive from. Used to improve the site, not to profile you.
Default
Off until you allow it
Category
Session experience
What it covers
Heatmaps and session recording that show where people get stuck. Sensitive form fields are masked, so what you type into them is not captured.
Default
Off until you allow it
Category
Marketing
What it covers
Advertising and retargeting technologies. We list this category for completeness; nothing in it loads unless we have actually enabled it and you allow it.
Default
Off until you allow it

A choice you make is honoured for 6 months, after which the banner asks again. It also asks again if we change the categories materially. [LAWYER: confirm the re-prompt period is acceptable in each market served.]

We ask clients not to send us special category or high-risk personal data (such as health, financial account credentials, biometric, or government identifier data) through a workflow unless it has been explicitly agreed and is supported both legally and technically. See the Acceptable Use Policy.

We use personal data to:

  • Operate, maintain and improve our website.
  • Review onboarding submissions and decide whether a request fits our standard implementation scope.
  • Request and confirm payment through Wise, and issue invoices for the monthly fee.
  • Deliver implementation, maintenance, support and operational reporting.
  • Set up and operate the workflows a client has asked us to run.
  • Send transactional and service communications, such as onboarding steps and project updates.
  • Respond to enquiries, support requests and privacy requests.
  • Protect our systems and prevent fraud, abuse and security incidents.
  • Meet legal, accounting and tax obligations.
  • Measure website performance, where you have given consent or where otherwise permitted by applicable law.

What we do not do with client lead data

We do not use a client’s lead or customer data to market TalkToLeads, to build our own prospect lists, to train models for unrelated purposes, or for any purpose other than delivering the contracted service. We do not sell personal data.

This section matters most if you enquired with a business, not with us

If you sent an enquiry to a business and a TalkToLeads workflow replied, that business — not TalkToLeads — normally decides why and how your data is used, and is the first place to direct a privacy request.
  • For lead and customer data processed through client workflows, the client typically determines the purpose and means of processing and is generally the data controller or Data Fiduciary under applicable law.
  • TalkToLeads generally acts as a service provider / data processor, handling that data under the client’s documented instructions.
  • The client remains responsible for their own customer notices, for obtaining and maintaining valid permissions and consents, for having a legal basis to contact people, for approving message content, for any regulated-industry obligations, and for compliance with the laws that apply to them and to their recipients.
  • TalkToLeads will process client lead data only to provide the contracted services, and in accordance with the Data Processing Addendum, applicable law, and documented client instructions.

Where we act for our own purposes

Separately from operating client workflows, we process some data for our own purposes as an independent controller: securing and monitoring our platform, keeping audit and abuse-prevention records, maintaining billing and tax records, and producing aggregate operational statistics that do not identify individual leads. Those purposes are described in this policy rather than in the DPA.

7.Cookies, Analytics, and Similar Technologies

Copy link to “Cookies, Analytics, and Similar Technologies”

Our full Cookie Policy lists the technologies we use, their purpose and their duration. In summary, we group them into essential, functional/preferences, analytics, and marketing categories.

  • Essential technologies are needed for the site to work and for us to record your privacy choices. They cannot be switched off.
  • Functional / preference technologies remember settings you have chosen.
  • Analytics technologies help us understand aggregate site performance.
  • Marketing technologies are only described here so the category is complete; they are used only if and when we actually enable them.

You can accept, reject or change your choices at any time using the Cookie settings link in the footer. Optional technologies are activated according to your stated preference and applicable law. Your browser settings can also block or delete cookies independently of our banner.

Form fields and session tools

Sensitive form fields on this site are intended to be masked from session-recording and analytics tools, so the values you type into them are not captured. Masking depends on correct configuration and on the third-party tool honouring it, so we cannot promise perfect anonymity. Please do not enter sensitive personal information into untrusted third-party widgets on any website.

We share personal data only with the categories of recipient below, and only as needed. Our current providers are listed on the Subprocessors page.

  • Hosting and database providers — to run our systems and store data.
  • Email delivery providers — to send transactional and service email.
  • Analytics providers — where you have consented or it is otherwise permitted.
  • Session-replay / heatmap providers — where you have consented, with sensitive fields masked.
  • Payment provider (Wise) — to request and confirm payment.
  • Messaging providers, such as the WhatsApp Business Platform, where a client selects that channel for their workflow.
  • Automation and integration providers — where used to connect the systems a client has asked us to connect.
  • Professional advisors — lawyers, accountants and auditors, under duties of confidentiality.
  • Authorities — where we are lawfully required to disclose, or to establish, exercise or defend legal claims.
  • A recipient in a corporate transaction — if the business is sold, merged or reorganised, subject to applicable law and appropriate confidentiality.
TalkToLeads does not sell personal data, and does not share it for third-party advertising or cross-context behavioural advertising.

Primary storage is in Japan and hosting is in the United States. Our database and authentication run on Supabase in AWS ap-northeast-1 (Tokyo), and the website and its server routes run on Vercel in the United States. So if you are in Australia, New Zealand, Singapore, the UAE or anywhere else, your data is processed outside your own country.

The table below is the full list, generated from the same record the subprocessors page uses, so the two cannot disagree.

Processor
Supabase
What they do
Database and authentication
Where processing happens
AWS ap-northeast-1 — Tokyo, Japan
Processor
Vercel
What they do
Website and application hosting
Where processing happens
United States
Processor
Google LLC
What they do
Google sign-in for the client portal
Where processing happens
United States
Processor
Cloudflare
What they do
Turnstile bot protection
Where processing happens
Global edge network
Processor
Anthropic
What they do
Website chat assistant
Where processing happens
United States
Processor
Wise
What they do
Payment collection
Where processing happens
[INSERT REGION — CONFIRM IN THE WISE CONSOLE]
Processor
Meta (WhatsApp)
What they do
Message delivery for the service
Where processing happens
[INSERT REGION — CONFIRM IN THE META BUSINESS CONSOLE]

Where applicable law requires safeguards for such transfers, we will put appropriate safeguards in place.

[LAWYER: cross-border transfer mechanism for AU/NZ/SG/UAE/EU-adjacent clients.] The specific mechanisms relied on — standard contractual clauses, a UK addendum, an APEC or ASEAN arrangement, or another lawful route — must be confirmed by counsel and checked against the data locations above before this section names any of them. Do not assert a mechanism that has not been executed.

Different categories are kept for different periods. Our default retention approach is 30 days, adjusted per category as follows:

  • Lead data is retained for 30 days after cancellation, then deleted.
  • Account data is retained for 12 months after cancellation, or longer where tax law requires.
  • Client data is retained during active service, then deleted or returned in accordance with the contract and the Data Processing Addendum, subject to legal requirements, backup cycles, unresolved disputes, or security needs.
  • Setup requests that do not become clients are retained for [INSERT PERIOD].
  • Billing and tax records are retained for as long as applicable law requires.
  • Security and audit records are retained for [INSERT PERIOD].
  • Consent and opt-out records are retained for as long as needed to keep honouring the choice.

Backups are not instant

Deleting data from live systems does not immediately remove it from backups. Backup copies are overwritten on our standard cycle, and data may persist in them for a limited period after deletion. We do not claim immediate or irreversible deletion.

We use reasonable technical and organisational safeguards designed to protect personal data against unauthorised access, loss, misuse and alteration.

Do not publish unverified security claims

Specific controls — access control models, authentication requirements, logging, tenant isolation, encryption in transit or at rest, backup and restore, vulnerability management — must be listed here only after engineering has verified each one is actually live in production. Annex 2 of the DPA is the canonical list and carries the same rule. Claiming a control you do not operate is both a misrepresentation and a security risk.

No system or transmission method is completely secure. We cannot and do not guarantee absolute security. If you believe you have found a security issue, please contact us at the address in section 16.

Depending on your jurisdiction, you may have rights under applicable data-protection law, which may include:

  • Access to the personal data we hold about you.
  • Correction of inaccurate or incomplete data.
  • Deletion or erasure of data, in defined circumstances.
  • Withdrawal of consent, where processing relies on consent.
  • Objection to, or restriction of, certain processing, where applicable.
  • Data portability, where applicable.
  • Opting out of marketing communications at any time.
  • Making a complaint to us, and to a supervisory authority or grievance mechanism where one is available to you.

To exercise a right, use the privacy request page. We may need to verify your identity, or your authority to act for someone else, before we can act on a request — this protects you from someone else obtaining your data.

We aim to respond within [INSERT RESPONSE TIMEFRAME — VARIES BY JURISDICTION]. Where applicable law sets a shorter or longer period, that period applies.

If your request concerns data held by a business that uses TalkToLeads, please contact that business first. Where required under our DPA, we will assist them in responding to you.

Our website and services are directed at businesses, not children. We do not knowingly collect personal data from children.

If you believe a child’s data has been provided to us, contact pritpalkaur112@gmail.com and we will take appropriate steps to delete it.

Clients remain responsible for ensuring their own workflows are not directed at children, and that any processing of children’s data meets the requirements of applicable law.

We may update this policy as our service, providers, or legal obligations change. When we do, we update the version number and the “last updated” date shown at the top of this page.

Where a change is material and applicable law or our contract requires it, we will provide additional notice — for clients, through the account contact on file.

Purpose
Privacy and grievance matters
Contact
pritpalkaur112@gmail.com
Purpose
Legal matters
Contact
pritpalkaur112@gmail.com
Purpose
Data deletion requests
Contact
pritpalkaur112@gmail.com
Purpose
Founder (direct, if the above do not reach us)
Contact
pritpalkaur112@gmail.com
Purpose
WhatsApp (general contact)
Contact
Business messaging number

The fastest route for a formal request is the privacy request page, which records your request and routes it to a named owner.

If you contact us on WhatsApp

WhatsApp is operated by Meta under its own privacy policy and terms. Messaging us there means your phone number and message content are processed by Meta as well as by us. For a formal privacy request — access, correction, deletion or consent withdrawal — please use the privacy request page or email instead, so the request is properly recorded and tracked. Please do not send passwords, payment card numbers, or government identifiers over any channel.

Grievance Officer / DPO

Some jurisdictions require a named Grievance Officer, Data Protection Officer, or local representative to be published with contact details and a defined response window. Legal counsel must confirm whether that applies here and, if so, the name and details must be inserted before publication: [INSERT GRIEVANCE OFFICER / DPO NAME, TITLE, CONTACT AND RESPONSE WINDOW IF LEGALLY REQUIRED].