TalkToLeads legal
Data Processing Addendum
This Addendum governs how TalkToLeads processes personal data on behalf of a client when delivering the Services. It forms part of the agreement between TalkToLeads and the Client, alongside the Terms of Service.
- 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.
Draft addendum — not executable
1.Purpose
Copy link to “Purpose”This Addendum governs the processing of personal data contained in Client Data and Lead Data. It applies whenever TalkToLeads processes personal data on the Client’s behalf in the course of providing the Services.
Where this Addendum conflicts with the Terms of Service on the subject of data protection, this Addendum is intended to take precedence — subject to section 16.
2.Roles of the Parties
Copy link to “Roles of the Parties”- The Client is usually the Controller / Data Fiduciary in respect of Lead Data.
- TalkToLeads is usually the Processor / Data Processor in respect of that data.
- Roles may differ depending on applicable law and the actual processing carried out in a given case.
- The Client remains responsible for instructions, customer notices, legal grounds for processing, and responding to data-subject requests, unless the parties agree otherwise in writing.
3.Subject Matter and Duration
Copy link to “Subject Matter and Duration”Subject matter: lead response, qualification, routing, human handoff, follow-up, maintenance, support, reporting and troubleshooting.
Duration: the term of the Services, plus the closure and deletion period described in section 13, plus any period for which retention is required by law.
4.Nature and Purpose of Processing
Copy link to “Nature and Purpose of Processing”- Configuring and operating Workflows.
- Receiving, storing and processing enquiry data.
- Sending communications according to Client instructions.
- Routing and handing off conversations to Client personnel.
- Monitoring Workflow health.
- Generating operational reports.
- Providing support and troubleshooting.
- Preventing abuse and security incidents.
5.Types of Personal Data
Copy link to “Types of Personal Data”- Lead name and contact data (name, phone, email, messaging identifier).
- Enquiry details and message content.
- Location, budget, timeline and stated business needs.
- Consent and opt-out records.
- Technical and log data associated with the conversation.
6.Categories of Data Subjects
Copy link to “Categories of Data Subjects”- Prospects and enquirers.
- Existing customers of the Client.
- Website visitors to Client properties where a Workflow is connected.
- Buyers, sellers, tenants, renters and investors, for real-estate clients.
- Project prospects, for interior design and architecture clients.
- Borrowers and loan prospects, for mortgage and loan-advisory clients.
- Client employees and business contacts.
- Other individuals as instructed by the Client.
7.Client Instructions
Copy link to “Client Instructions”- TalkToLeads processes personal data only on the Client’s documented instructions, including as set out in this Addendum, the Order, and the agreed Workflow configuration.
- If TalkToLeads believes an instruction infringes applicable law, it will inform the Client where legally permitted, and may pause the affected processing.
- The Client warrants that it has all rights, permissions and legal bases necessary for the processing it instructs, and for the data it provides.
8.Confidentiality
Copy link to “Confidentiality”- Personnel authorised to process Client Data are bound by confidentiality obligations.
- Access is granted on a least-privilege basis and only to personnel who need it to deliver the Services.
- Access is removed when it is no longer required.
9.Security Measures
Copy link to “Security Measures”TalkToLeads uses reasonable technical and organisational safeguards designed to protect personal data. The specific measures are set out in Annex 2.
Annex 2 must reflect production reality
10.Subprocessors
Copy link to “Subprocessors”- The Client authorises TalkToLeads to engage the subprocessors necessary to provide the Services. The current list is published at Subprocessors and reproduced in Annex 3.
- Where required by law or by contract, TalkToLeads will give notice of material subprocessor changes before they take effect.
- The Client may object to a new subprocessor on reasonable data-protection grounds under the process at [INSERT OBJECTION WINDOW AND PROCESS].
- TalkToLeads remains responsible for its subprocessors’ performance of the applicable obligations, to the extent required by applicable law and the agreement.
11.Assistance to the Client
Copy link to “Assistance to the Client”Taking into account the nature of the processing and the information available to us, TalkToLeads will provide reasonable assistance with:
- Responding to data-subject rights requests relating to Lead Data we process for the Client.
- Data protection impact assessments and prior consultations, where applicable law requires them.
- Regulatory queries relating to the processing we perform.
- Providing security information reasonably necessary to demonstrate compliance.
Assistance that falls outside the standard scope of the Services, or that requires significant engineering effort, may be chargeable at rates agreed in advance.
12.Personal Data Breach
Copy link to “Personal Data Breach”- TalkToLeads will notify the Client without undue delay after becoming aware of a confirmed personal data breach affecting Client Data.
- The notification will include the information reasonably available at the time, and will be updated as the investigation progresses.
- TalkToLeads will take reasonable steps to contain and remediate the breach, and will cooperate with the Client’s reasonable investigation.
- Unless applicable law or the agreement provides otherwise, the Client remains responsible for notifications to regulators and affected individuals.
13.Return or Deletion of Client Data
Copy link to “Return or Deletion of Client Data”- On termination of the Services, or on documented request, TalkToLeads will return and/or delete Client Data within 30 days, unless retention is required by applicable law or by legitimate backup and security constraints.
- Backup copies are deleted or overwritten on our standard backup cycle rather than immediately.
- The Client is responsible for exporting any data it needs before the closure window ends. We will confirm the closure date in writing.
- On request, TalkToLeads will confirm deletion in writing where operationally feasible.
14.Audit and Information Rights
Copy link to “Audit and Information Rights”- TalkToLeads will make available information reasonably necessary to demonstrate compliance with this Addendum.
- Requests are handled first through documentary and remote means — written responses, security questionnaires, and available reports.
- An on-site audit may be considered where documentary means are genuinely insufficient, subject to [INSERT NOTICE PERIOD, FREQUENCY LIMIT, SCOPE, CONFIDENTIALITY AND COST-ALLOCATION TERMS].
- Audit rights are subject to confidentiality, the security of other clients’ data, and reasonable limits on frequency and cost.
15.International Transfers
Copy link to “International Transfers”Primary storage is in Japan and hosting is in the United States. The database and authentication run on Supabase in AWS ap-northeast-1 (Tokyo); the application runs on Vercel in the United States. Client Data and Lead Data are therefore processed outside the country in which they were collected for every Client we currently serve.
| 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] |
Generated from the same record as Annex 3 and the [subprocessors page](/subprocessors).
- 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 a transfer mechanism, appropriate safeguards will be put in place.
16.Liability and Precedence
Copy link to “Liability and Precedence”Liability under this Addendum is intended to be governed by the limitation of liability in the Terms of Service. Where this Addendum and the Terms conflict on data protection, this Addendum is intended to prevail.
17.Annex 1 — Processing Details
Copy link to “Annex 1 — Processing Details”| Item | Detail |
|---|---|
| Subject matter | Lead response, qualification, routing, human handoff, follow-up, maintenance, support and reporting. |
| Duration | Term of the Services, plus the closure and deletion period, plus any legally required retention. |
| Nature and purpose | Configuring and operating Workflows; sending communications on Client instructions; routing to Client personnel; monitoring; reporting; support; abuse prevention. |
| Types of personal data | Lead name and contact details, enquiry content, qualification answers, location/budget/timeline, consent and opt-out records, technical and log data. |
| Categories of data subjects | Prospects, customers, website visitors, property buyers/sellers/tenants/investors, project prospects, loan prospects, Client employees and contacts. |
| Client instructions | As set out in this Addendum, the Order, the approved Workflow configuration, and any later written instruction accepted by TalkToLeads. |
| Frequency of processing | Continuous, for the duration of the Services. |
- Item
- Subject matter
- Detail
- Lead response, qualification, routing, human handoff, follow-up, maintenance, support and reporting.
- Item
- Duration
- Detail
- Term of the Services, plus the closure and deletion period, plus any legally required retention.
- Item
- Nature and purpose
- Detail
- Configuring and operating Workflows; sending communications on Client instructions; routing to Client personnel; monitoring; reporting; support; abuse prevention.
- Item
- Types of personal data
- Detail
- Lead name and contact details, enquiry content, qualification answers, location/budget/timeline, consent and opt-out records, technical and log data.
- Item
- Categories of data subjects
- Detail
- Prospects, customers, website visitors, property buyers/sellers/tenants/investors, project prospects, loan prospects, Client employees and contacts.
- Item
- Client instructions
- Detail
- As set out in this Addendum, the Order, the approved Workflow configuration, and any later written instruction accepted by TalkToLeads.
- Item
- Frequency of processing
- Detail
- Continuous, for the duration of the Services.
18.Annex 2 — Technical and Organisational Measures
Copy link to “Annex 2 — Technical and Organisational Measures”Implementation-dependent — verify before publishing
| Measure | Description | Status |
|---|---|---|
| Role-based access control | Access to client systems and data is granted by role rather than individually. | [TO VERIFY] |
| Individual employee accounts | No shared logins; each person has their own credentials. | [TO VERIFY] |
| Founder-only employee administration | Creation, modification and removal of staff accounts restricted to the founder. | [TO VERIFY] |
| Multi-factor authentication | MFA/2FA on administrative and client-system access. | [TO VERIFY] |
| Tenant / organisation isolation | Client data is logically separated so one client cannot access another’s. | [TO VERIFY] |
| Row-Level Security | Database-level policies restricting row access by tenant and role. | [TO VERIFY] |
| Server-side secret handling | API keys and credentials held server-side, never exposed to the browser or written to normal UI logs. | [TO VERIFY] |
| Logging and audit trail | Administrative and access events recorded and retained. | [TO VERIFY] |
| Encryption | Encryption in transit and at rest. | [TO VERIFY — DO NOT CLAIM UNTIL ENGINEERING CONFIRMS] |
| Backup and restore | Regular backups with a tested restore procedure. | [TO VERIFY] |
| Vulnerability and patch management | Dependency and platform patching process. | [PLANNED — INSERT PROCESS] |
| Incident response | Documented detection, triage, containment and notification process. | [PLANNED — INSERT PROCESS] |
| Staff training and confidentiality | Confidentiality obligations and data-handling training for personnel. | [TO VERIFY] |
| Vendor / subprocessor controls | Review of provider security terms before engagement. | [TO VERIFY] |
- Measure
- Role-based access control
- Description
- Access to client systems and data is granted by role rather than individually.
- Status
- [TO VERIFY]
- Measure
- Individual employee accounts
- Description
- No shared logins; each person has their own credentials.
- Status
- [TO VERIFY]
- Measure
- Founder-only employee administration
- Description
- Creation, modification and removal of staff accounts restricted to the founder.
- Status
- [TO VERIFY]
- Measure
- Multi-factor authentication
- Description
- MFA/2FA on administrative and client-system access.
- Status
- [TO VERIFY]
- Measure
- Tenant / organisation isolation
- Description
- Client data is logically separated so one client cannot access another’s.
- Status
- [TO VERIFY]
- Measure
- Row-Level Security
- Description
- Database-level policies restricting row access by tenant and role.
- Status
- [TO VERIFY]
- Measure
- Server-side secret handling
- Description
- API keys and credentials held server-side, never exposed to the browser or written to normal UI logs.
- Status
- [TO VERIFY]
- Measure
- Logging and audit trail
- Description
- Administrative and access events recorded and retained.
- Status
- [TO VERIFY]
- Measure
- Encryption
- Description
- Encryption in transit and at rest.
- Status
- [TO VERIFY — DO NOT CLAIM UNTIL ENGINEERING CONFIRMS]
- Measure
- Backup and restore
- Description
- Regular backups with a tested restore procedure.
- Status
- [TO VERIFY]
- Measure
- Vulnerability and patch management
- Description
- Dependency and platform patching process.
- Status
- [PLANNED — INSERT PROCESS]
- Measure
- Incident response
- Description
- Documented detection, triage, containment and notification process.
- Status
- [PLANNED — INSERT PROCESS]
- Measure
- Staff training and confidentiality
- Description
- Confidentiality obligations and data-handling training for personnel.
- Status
- [TO VERIFY]
- Measure
- Vendor / subprocessor controls
- Description
- Review of provider security terms before engagement.
- Status
- [TO VERIFY]
19.Annex 3 — Approved Subprocessors
Copy link to “Annex 3 — Approved Subprocessors”The authoritative, continuously maintained list is published at Subprocessors. That page is incorporated into this Annex by reference, including provider name, service, purpose, data categories and status.
A provider marked *planned*, *optional* or *client-selected* on that page is not an active subprocessor for a given Client unless that Client has selected it or been notified of it.
20.Contact for DPA Questions
Copy link to “Contact for DPA Questions”| Purpose | Contact |
|---|---|
| Data protection and DPA questions | pritpalkaur112@gmail.com |
| Legal notices | pritpalkaur112@gmail.com |
| Data deletion requests | pritpalkaur112@gmail.com |
| Founder (direct) | pritpalkaur112@gmail.com |
- Purpose
- Data protection and DPA questions
- Contact
- pritpalkaur112@gmail.com
- Purpose
- Legal notices
- Contact
- pritpalkaur112@gmail.com
- Purpose
- Data deletion requests
- Contact
- pritpalkaur112@gmail.com
- Purpose
- Founder (direct)
- Contact
- pritpalkaur112@gmail.com
Subprocessor objections and DPA queries can also be raised through the privacy and requests page.