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.
1.Who We Are
Copy link to “Who We Are”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 | Value |
|---|---|
| Legal entity | Pritpal Kaur |
| Entity type | Sole proprietor |
| Country of establishment | India |
| Legal contact | pritpalkaur112@gmail.com |
| Privacy / grievance contact | pritpalkaur112@gmail.com |
| Founder (direct) | pritpalkaur112@gmail.com |
- 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
2.Scope of This Policy
Copy link to “Scope of This Policy”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
3.Personal Data We Collect
Copy link to “Personal Data We Collect”We collect different categories of data for different reasons. Retention approaches below are summaries — section 10 has the detail.
| Data category | Examples | Why collected | Source | Retention approach |
|---|---|---|---|---|
| Website usage and cookie data | Cookie preferences, page views, CTA clicks, form-progress metadata, device and browser data, referral and UTM information | Operate the site, understand performance, remember your privacy choices | Your browser, subject to your consent choices | Per cookie duration — see Cookie Policy |
| Onboarding submission | 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 | Review whether a request fits our standard implementation scope, and respond to you | Submitted by you on the onboarding form at /onboarding | [INSERT RETENTION — ONBOARDING SUBMISSIONS, IN MONTHS] for requests that do not become clients |
| Checkout enquiry | Work email and agency name, entered at the first step of the checkout page before any payment is made | Let you resume checkout, and follow up if you do not complete it | Entered by you on /checkout | [INSERT RETENTION — UNCONTACTED LEADS, IN MONTHS] |
| Google sign-in profile | Email address, display name and profile picture URL, received from Google when you sign in to the client portal | Create and authenticate your portal login | Google, when you choose to sign in with it | Until you ask us to delete the account |
| Website chat messages | What you type into the chat widget, and the reply it produces | Answer your question on the site | You, in the chat widget | not retained by us — see below |
| Privacy request records | Your name, email, organisation, the request you made, the reference we issued and the response deadline we recorded | Handle the request, and evidence that we handled it within the deadline | Submitted by you on /contact-privacy | [INSERT RETENTION — PRIVACY REQUEST RECORDS, IN YEARS] |
| Account and client-contact data | Named contacts, roles, routing owners, business addresses, communication preferences | Deliver and support the contracted service | Provided by the client during onboarding | Term of service, then per contract and law |
| Billing, invoice and payment-confirmation data | Invoice references, amounts, payment confirmation records, billing contact details | Request and confirm payment, issue invoices for the monthly fee, meet accounting and tax obligations | You, and our payment provider | As required by applicable tax and accounting law |
| Client onboarding and workflow data | Lead sources, team structure, qualification requirements, approved message templates, routing rules, integration metadata, system configuration | Build, test, launch and maintain the agreed workflow | Provided by the client | Term of service, then per the DPA |
| Client lead / customer conversation data | Lead names, phone numbers, email addresses, enquiry messages, lead source, qualification answers, conversation activity, routing and handoff records | Operate the workflow the client has instructed us to run | The client’s own lead sources and channels | Per client instructions and the DPA |
| Consent and opt-out records | Records of consent captured, opt-out and suppression signals, timestamps | Honour choices and evidence that they were honoured | Leads, clients, and website visitors | Retained as long as needed to keep honouring the choice |
| Communications with us | Emails, messages, and notes from calls with our team | Answer enquiries, support clients, keep an account history | You | [INSERT PERIOD] |
| Support-ticket data | Issue descriptions, screenshots and logs you send us, resolution notes | Diagnose and resolve issues, track recurring problems | Client contacts | [INSERT PERIOD] |
| Employee and internal account data | Work identity, login and audit activity, client and project assignments | Operate our internal systems securely and control who can access what | Our own personnel systems | [INSERT PERIOD] |
| Security and audit logs | Access records, administrative actions, error and abuse signals | Protect systems, investigate incidents, prevent fraud and abuse | Generated by our systems | [INSERT PERIOD] |
- 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
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 | What it covers | Default |
|---|---|---|
| Essential | Required to run the website, keep it secure, and remember the privacy choice you make here. These cannot be switched off. | Always on — the site cannot run without it |
| Analytics | 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. | Off until you allow it |
| Session experience | Heatmaps and session recording that show where people get stuck. Sensitive form fields are masked, so what you type into them is not captured. | Off until you allow it |
| Marketing | Advertising and retargeting technologies. We list this category for completeness; nothing in it loads unless we have actually enabled it and you allow it. | Off until you allow it |
- 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.]
4.How We Use Personal Data
Copy link to “How We Use Personal Data”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
5.Legal Bases / Grounds for Processing
Copy link to “Legal Bases / Grounds for Processing”The grounds we rely on depend on where you are and which law applies. Depending on your jurisdiction, these may include:
- Consent, where applicable law requires it — for example, for non-essential cookies and certain marketing messages. You may withdraw consent at any time.
- Performance of a contract, or steps taken at your request before entering one — for example, reviewing your checkout details or delivering the service.
- Legitimate business interests, where permitted — for example, securing our systems, preventing abuse, and understanding aggregate website performance, balanced against your rights.
- Compliance with legal obligations, such as tax, accounting and lawful requests from authorities.
- Client instructions, where we act as a service provider or processor handling data on a client’s behalf.
6.Client Lead Data and Roles
Copy link to “Client Lead Data and Roles”This section matters most if you enquired with a business, not with us
- 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.
9.International Data Transfers
Copy link to “International Data Transfers”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 | What they do | Where processing happens |
|---|---|---|
| Supabase | Database and authentication | AWS ap-northeast-1 — Tokyo, Japan |
| Vercel | Website and application hosting | United States |
| Google LLC | Google sign-in for the client portal | United States |
| Cloudflare | Turnstile bot protection | Global edge network |
| Anthropic | Website chat assistant | United States |
| Wise | Payment collection | [INSERT REGION — CONFIRM IN THE WISE CONSOLE] |
| Meta (WhatsApp) | Message delivery for the service | [INSERT REGION — CONFIRM IN THE META BUSINESS CONSOLE] |
- 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.
10.Data Retention
Copy link to “Data Retention”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
11.Security
Copy link to “Security”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
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.
12.Your Rights and Choices
Copy link to “Your Rights and Choices”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.
13.Children
Copy link to “Children”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.
14.Third-Party Links
Copy link to “Third-Party Links”Our website and communications may link to sites and services we do not operate. Those are governed by their own privacy policies and terms, and we are not responsible for their content or practices.
15.Changes to This Policy
Copy link to “Changes to This Policy”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.
16.Contact and Grievance
Copy link to “Contact and Grievance”| Purpose | Contact |
|---|---|
| Privacy and grievance matters | pritpalkaur112@gmail.com |
| Legal matters | pritpalkaur112@gmail.com |
| Data deletion requests | pritpalkaur112@gmail.com |
| Founder (direct, if the above do not reach us) | pritpalkaur112@gmail.com |
| WhatsApp (general contact) | Business messaging number |
- 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
Grievance Officer / DPO