Data Processing Agreement

Effective: July 2, 2026 - Last updated: November 4, 2026

This Data Processing Addendum ("DPA") forms part of the agreement, order form, online terms, invoice, or other written arrangement governing access to and use of TalkToHumans (the "Agreement") between:

  • Customer: the entity or person that has entered into the Agreement with TalkToHumans, or that accesses or uses the Services under the Agreement ("Customer"); and
  • Provider: COOLSAPIENS, trade name of LABROT Robin, entrepreneur individuel registered in France under SIREN 882 596 414 / SIRET 882 596 414 00012, with registered address at 49 Avenue Alfred de Musset, 78110 Le Vesinet, France, doing business as TalkToHumans ("TalkToHumans").

Customer and TalkToHumans are each a "Party" and together the "Parties". This DPA supplements the TalkToHumans General Terms & Conditions of Use available at https://www.talktohumans.app/legal/terms, any applicable order form, invoice, or other written agreement between the Parties.

1. Purpose and Scope

1.1. This DPA applies when TalkToHumans processes Customer Personal Data on behalf of Customer in connection with the Services.

1.2. The Parties intend this DPA to satisfy the requirements for processor contracts under Article 28 of Regulation (EU) 2016/679 ("GDPR"), the UK GDPR, the Swiss Federal Act on Data Protection, and equivalent processor, service provider, or contractor requirements under other Applicable Data Protection Laws.

1.3. If there is a conflict between this DPA and the Agreement, this DPA controls for the processing of Customer Personal Data. The Standard Contractual Clauses control over this DPA where required by Applicable Data Protection Law.

2. Definitions

2.1. "Account Data" means Personal Data relating to Customer's users, administrators, billing contacts, and other representatives that TalkToHumans processes as an independent Controller for account administration, security, billing, support, legal compliance, communications, analytics, and service improvement.

2.2. "Applicable Data Protection Law" means all privacy and data protection laws applicable to a Party's processing of Customer Personal Data under the Agreement, including where applicable the GDPR, the UK GDPR, the Swiss Federal Act on Data Protection, and U.S. state privacy laws.

2.3. "Customer Personal Data" means Personal Data that Customer submits to, stores in, or otherwise makes available through the Services, or that TalkToHumans processes on Customer's behalf to provide the Services. Account Data is not Customer Personal Data except to the extent TalkToHumans processes it as Processor to provide the Services.

2.4. "Data Protection Laws" and "Applicable Data Protection Law" have the same meaning in this DPA.

2.5. "EU SCCs" means the standard contractual clauses approved by Commission Implementing Decision (EU) 2021/914, as amended, replaced, or superseded.

2.6. "Personal Data", "Controller", "Processor", "Data Subject", "Personal Data Breach", "Processing", "Subprocessor", "Business", "Service Provider", "Contractor", "Consumer", "Sell", and "Share" have the meanings given to them or to substantially similar terms under Applicable Data Protection Law.

2.7. "Restricted Transfer" means a transfer of Customer Personal Data that requires an approved transfer mechanism under Chapter V of the GDPR, the UK GDPR, Swiss data protection law, or another Applicable Data Protection Law.

2.8. "Services" means the TalkToHumans web application, Chrome extension, backend services, API, MCP server, billing and account administration surfaces, support, and related product functionality provided under the Agreement.

2.9. "Standard Contractual Clauses" or "SCCs" means the EU SCCs, the UK International Data Transfer Addendum to the EU SCCs issued by the UK Information Commissioner's Office ("UK Addendum"), and any other standard contractual clauses or transfer addendum approved by a competent authority where applicable.

2.10. "U.S. Privacy Laws" means U.S. federal and state privacy laws that apply generally to Personal Data processing, including the California Consumer Privacy Act as amended by the California Privacy Rights Act ("CCPA/CPRA"), and similar state privacy laws where applicable.

3. Roles of the Parties

3.1. Customer is the Controller of Customer Personal Data, or the Business where U.S. Privacy Laws use that term. Customer determines the purposes and means of processing Customer Personal Data, including what LinkedIn accounts, contacts, conversations, notes, tags, templates, custom fields, and other data Customer chooses to use with the Services.

3.2. TalkToHumans is the Processor of Customer Personal Data, or the Service Provider or Contractor where U.S. Privacy Laws use those terms, when TalkToHumans processes Customer Personal Data to provide the Services.

3.3. TalkToHumans may act as an independent Controller for limited business operations outside the processor scope of this DPA, including account administration, billing administration, security monitoring, fraud prevention, product analytics, service improvement, legal compliance, and communications with Customer. That processing is governed by TalkToHumans' privacy notice and Applicable Data Protection Law, not by this DPA.

4. Details of Processing and Instructions

4.1. The subject matter, duration, nature, purpose, categories of Personal Data, and categories of Data Subjects are described in Schedule 1.

4.2. Customer's documented instructions include the Agreement, this DPA, Customer's configuration and use of the Services, Customer's feature choices, Customer's written instructions that are consistent with the Agreement, and the creation and use of Aggregated Data described in Section 9.

4.3. TalkToHumans will process Customer Personal Data only on Customer's documented instructions, unless required by applicable law. If TalkToHumans is legally required to process Customer Personal Data other than on Customer's instructions, TalkToHumans will inform Customer before processing unless legally prohibited from doing so.

4.4. TalkToHumans will promptly inform Customer if, in TalkToHumans' opinion, a Customer instruction infringes Applicable Data Protection Law.

5. Customer Obligations

5.1. Customer is responsible for:

  • having a lawful basis for Customer's collection, use, and disclosure of Customer Personal Data;
  • providing any required notices to Data Subjects;
  • obtaining any required consents or permissions;
  • ensuring Customer has the right to connect or use LinkedIn accounts and related data with the Services;
  • configuring the Services in a manner consistent with Applicable Data Protection Law;
  • choosing whether to enable optional features such as AI drafting, enrichment, email finding, phone finding, API access, and MCP access;
  • avoiding submission of Restricted Data unless expressly agreed in writing; and
  • ensuring Customer's users follow Customer's instructions and policies.

5.2. Customer will not instruct TalkToHumans to process Customer Personal Data in a way that violates Applicable Data Protection Law.

6. TalkToHumans Processor Obligations

6.1. Confidentiality. TalkToHumans will ensure that persons authorized to process Customer Personal Data are bound by confidentiality obligations or are subject to an appropriate statutory obligation of confidentiality.

6.2. Security. TalkToHumans will implement and maintain appropriate technical and organizational measures designed to protect Customer Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure, or unauthorized access. Current measures are described in Schedule 2.

6.3. Personnel Access. TalkToHumans will limit access to Customer Personal Data to personnel and contractors who need access to provide, secure, support, maintain, or troubleshoot the Services.

6.4. Assistance. Taking into account the nature of processing and the information available to TalkToHumans, TalkToHumans will reasonably assist Customer with Customer's obligations under Applicable Data Protection Law, including obligations related to security, breach notification, data protection impact assessments, prior consultation, and Data Subject requests.

6.5. Data Subject Requests. If TalkToHumans receives a request from a Data Subject relating to Customer Personal Data, TalkToHumans will, where legally permitted, direct the Data Subject to Customer or notify Customer. TalkToHumans will not independently respond to a Data Subject request except on Customer's documented instructions or as required by law.

6.6. Demonstrating Compliance. TalkToHumans will make available information reasonably necessary to demonstrate compliance with this DPA, including security documentation, subprocessor information, and answers to reasonable security and privacy questionnaires.

6.7. Records. TalkToHumans will maintain records of processing activities where required by Applicable Data Protection Law.

7. U.S. Privacy Law Terms

7.1. To the extent U.S. Privacy Laws apply, TalkToHumans will process Customer Personal Data only as a Service Provider or Contractor for the limited and specified business purposes described in the Agreement and Schedule 1.

7.2. TalkToHumans will not:

  • Sell or Share Customer Personal Data;
  • retain, use, or disclose Customer Personal Data for any purpose other than the business purposes described in the Agreement and this DPA;
  • retain, use, or disclose Customer Personal Data outside the direct business relationship between the Parties;
  • combine Customer Personal Data with Personal Data received from or on behalf of another person or source except as permitted by U.S. Privacy Laws; or
  • process Customer Personal Data for cross-context behavioral advertising.

7.3. TalkToHumans will provide the level of privacy protection required by U.S. Privacy Laws and will notify Customer if TalkToHumans determines that it can no longer meet its obligations under U.S. Privacy Laws. Customer may take reasonable and appropriate steps to stop and remediate unauthorized use of Customer Personal Data.

7.4. The Parties acknowledge that Customer Personal Data is made available to TalkToHumans only for the business purposes described in this DPA and does not form part of monetary or other valuable consideration exchanged between the Parties.

7.5. Aggregated Data created under Section 9 is de-identified data under U.S. Privacy Laws. TalkToHumans will maintain it in de-identified form as described in Section 9.

8. AI, Enrichment, API, and MCP Features

8.1. The Services may include optional AI drafting, profile enrichment, company enrichment, email finding, phone finding, API access, and MCP access.

8.2. TalkToHumans will not use Customer Personal Data to train general-purpose AI models unless Customer expressly authorizes that use in writing.

8.3. AI drafting is initiated by Customer or a Customer user. When Customer invokes AI features, TalkToHumans may transmit prompts, selected variables, draft text, and relevant conversation/profile context to the AI Subprocessors listed in Schedule 3.

8.4. Enrichment, email finding, and phone finding are initiated by Customer or a Customer user, or enabled through Customer-selected plan or credit-gated functionality. When Customer invokes those features, TalkToHumans may transmit LinkedIn profile, company, or related identifiers to enrichment and contact data providers listed by category in Schedule 3. TalkToHumans may provide specific provider names to Customer during a security review or on reasonable written request.

8.5. API and MCP access require Customer-authorized credentials. Customer is responsible for authorizing and managing API keys, OAuth grants, MCP clients, and downstream tools that Customer connects to the Services.

9. Aggregated and De-identified Data

9.1. "Aggregated Data" means data that TalkToHumans derives from the operation and use of the Services and that is aggregated and de-identified so that it does not identify, and cannot reasonably be used to identify, Customer, any User, or any individual, including LinkedIn contacts and conversation participants.

9.2. Customer authorizes TalkToHumans to create Aggregated Data from Customer Personal Data and to use Aggregated Data to operate, secure, maintain, and improve the Services and to produce statistics, benchmarks, and research about LinkedIn usage, outreach, and content performance, which TalkToHumans may publish.

9.3. TalkToHumans creates Aggregated Data from counts, timestamps, and categorical metadata, such as message volumes, reply rates, response times, content formats, and engagement counts. TalkToHumans will not use message bodies, attachments, notes, drafts, or other free-text content to create Aggregated Data unless Customer expressly authorizes that use in writing.

9.4. When creating and using Aggregated Data, TalkToHumans will:

  • limit access to the Customer Personal Data used to create it to authorized personnel with a business need;
  • publish or disclose only statistics derived from enough customers and individuals that no Customer, User, or individual can be singled out;
  • not name Customer or attribute Aggregated Data to Customer without Customer's prior written consent; and
  • take reasonable measures to prevent re-identification, not attempt to re-identify Customer or any individual, and require any third party that receives non-public Aggregated Data to make the same commitment.

9.5. Aggregated Data is not Customer Personal Data. TalkToHumans may retain and use Aggregated Data after the Agreement ends, and Section 12 (Return and Deletion) does not apply to it.

10. Subprocessors

10.1. Customer grants TalkToHumans general written authorization to engage Subprocessors to provide the Services.

10.2. TalkToHumans will maintain a list of current Subprocessors. The initial list is in Schedule 3.

10.3. TalkToHumans will impose data protection obligations on each Subprocessor that are materially no less protective than those in this DPA, to the extent applicable to the Subprocessor's services.

10.4. TalkToHumans remains responsible for each Subprocessor's performance of its data protection obligations.

10.5. TalkToHumans will notify Customer of any intended addition or replacement of a Subprocessor at least 30 days before authorizing the Subprocessor to process Customer Personal Data, unless urgent replacement is necessary for security, availability, or continuity of the Services.

10.6. Customer may object to a new Subprocessor on reasonable data protection grounds by notifying TalkToHumans in writing within 15 days after notice. The Parties will work in good faith to resolve the objection. If the objection cannot be resolved, Customer may stop using the affected feature or terminate the affected Services in accordance with the Agreement.

11. Personal Data Breach

11.1. TalkToHumans will notify Customer without undue delay after becoming aware of a Personal Data Breach affecting Customer Personal Data.

11.2. Where feasible, TalkToHumans will provide notice within 72 hours after becoming aware that a Personal Data Breach has affected Customer Personal Data.

11.3. The notice will include available information reasonably required by Customer to meet its breach notification obligations, including the nature of the incident, affected categories of data, affected categories of Data Subjects, likely consequences, mitigation steps, and a contact point for follow-up.

11.4. TalkToHumans may provide information in phases as it becomes available.

12. Return and Deletion

12.1. During the term, Customer may export or delete Customer Personal Data using available Service functionality where such functionality exists.

12.2. Upon termination or expiration of the Agreement, TalkToHumans will, at Customer's choice and to the extent technically feasible, return or delete Customer Personal Data processed as Processor, unless retention is required by law or permitted for backup, security, dispute, audit, billing, or compliance purposes. Any retained Customer Personal Data will remain protected under this DPA and will not be used for ordinary Service delivery after termination.

12.3. Unless otherwise agreed, TalkToHumans will delete Customer Personal Data from active production systems within 30 days after termination or written deletion request, and from backups in accordance with TalkToHumans' normal backup retention cycle. As of the Last Updated date above, the production Aurora PostgreSQL automated backup retention period is 1 day.

12.4. Customer acknowledges that LinkedIn message bodies, message attachments, and related conversation data are synced to and stored in TalkToHumans backend systems by default as part of the core Services, because core product features depend on server-side message sync. Customer users' browsers or devices may also store local copies or caches of such data depending on product functionality, browser storage, and device configuration.

13. Audits and Security Reviews

13.1. Upon reasonable written request, TalkToHumans will provide information necessary to demonstrate compliance with this DPA.

13.2. Customer may conduct an audit no more than once per year, unless required by a regulator or following a confirmed Personal Data Breach affecting Customer Personal Data. Audits must be limited to information relevant to Customer Personal Data, conducted during normal business hours, and subject to reasonable confidentiality, security, and non-disruption requirements.

13.3. Where a third-party audit report, security documentation, completed questionnaire, or equivalent documentation provides substantially equivalent information, Customer will accept that documentation in place of duplicative audit requests.

13.4. Any on-site or live-system audit must be conducted by an independent auditor reasonably acceptable to both Parties, at Customer's cost, and in a manner that does not compromise the security, confidentiality, or availability of the Services or other customers' data.

14. International Transfers

14.1. Customer authorizes TalkToHumans and its Subprocessors to process Customer Personal Data in the countries where TalkToHumans and its Subprocessors operate, subject to this DPA and Applicable Data Protection Law.

14.2. If a Restricted Transfer occurs and no adequacy decision or other lawful transfer mechanism applies, the Parties will rely on the applicable Standard Contractual Clauses as completed by Schedule 4.

14.3. To the extent the EU SCCs are required between Customer as Controller and TalkToHumans as Processor, Module Two (Controller to Processor) will apply.

14.4. To the extent the EU SCCs are required for a transfer from TalkToHumans as Processor in the EEA to Customer as Controller outside the EEA, Module Four (Processor to Controller) will apply.

14.5. To the extent the UK Addendum is required, it is incorporated by reference and completed as described in Schedule 4.

14.6. Where Swiss data protection law applies, the EU SCCs will be interpreted to satisfy Swiss transfer requirements where applicable, including by replacing references to the GDPR with references to the Swiss Federal Act on Data Protection, and by treating the Swiss Federal Data Protection and Information Commissioner as the competent supervisory authority where required.

14.7. TalkToHumans will ensure that Restricted Transfers from TalkToHumans to Subprocessors are covered by applicable SCCs, data transfer addenda, adequacy decisions, or another lawful transfer mechanism where required.

15. Third-Party Platforms

15.1. The Services interoperate with LinkedIn through Customer's logged-in browser session and Customer-directed use of the Chrome extension. LinkedIn is not a Subprocessor of TalkToHumans under this DPA. Customer is responsible for its relationship with LinkedIn and for compliance with LinkedIn's applicable terms and policies.

15.2. Customer may choose to use third-party services, clients, browser environments, AI tools, CRM systems, automation tools, or integrations in connection with the Services. TalkToHumans is not responsible for Customer-selected third-party tools that are not listed as TalkToHumans Subprocessors in Schedule 3.

16. Restricted Data

16.1. Customer will not submit to the Services any protected health information, payment card data, government identifiers, biometric data, children's data, special categories of Personal Data, or other regulated data ("Restricted Data") unless expressly agreed in writing.

16.2. TalkToHumans does not intentionally collect or require special categories of Personal Data. Customer acknowledges that free-form messages, notes, templates, custom fields, support communications, LinkedIn messages, and attachments may incidentally contain such data if Customer or its users choose to enter or transmit it.

17. Liability

17.1. Each Party's liability under this DPA is subject to the exclusions and limitations of liability in the Agreement, unless prohibited by Applicable Data Protection Law or the Standard Contractual Clauses.

18. Term

18.1. This DPA remains in effect for as long as TalkToHumans processes Customer Personal Data on behalf of Customer.

19. Acceptance

19.1. This DPA is incorporated into and forms part of the Agreement. Customer accepts this DPA by entering into the Agreement, signing or accepting an order form or other written arrangement that references this DPA, or accessing or using the Services where the Agreement incorporates this DPA.

19.2. Customer-specific versions of this DPA may be agreed separately in an order form, signed addendum, or other written arrangement between the Parties.


Schedule 1 - Processing Details

A. Subject Matter

TalkToHumans provides a LinkedIn workspace and CRM-like operating layer for managing LinkedIn conversations, contacts, tags, notes, templates, saved views, sequences, scheduled follow-ups, enrichment, AI drafting, API access, and MCP access.

B. Duration

For the term of the Agreement, plus any post-termination period required to return or delete Customer Personal Data, comply with law, resolve disputes, maintain backups, or enforce the Agreement.

C. Nature and Purpose of Processing

TalkToHumans processes Customer Personal Data to:

  • provide and operate the Services;
  • authenticate users and manage organizations, accounts, memberships, and invitations;
  • connect Customer-selected LinkedIn accounts through the Chrome extension;
  • display, organize, search, filter, tag, and manage LinkedIn contacts, companies, conversations, and workflows;
  • execute Customer-directed LinkedIn actions through Customer's logged-in browser session;
  • schedule and run Customer-configured follow-ups and sequences;
  • store drafts, templates, AI actions, saved views, tags, notes, custom fields, and related workflow state;
  • provide API and MCP access to Customer-authorized workspace data;
  • sync, store, search, and organize LinkedIn messages and related conversation data for Customer-enabled LinkedIn accounts;
  • provide optional AI drafting when Customer invokes AI features;
  • provide optional profile enrichment, email finding, and phone finding when Customer invokes those features;
  • manage billing, subscriptions, invoices, credits, and usage reservations;
  • provide support, troubleshooting, security, abuse prevention, analytics, and service improvement;
  • create Aggregated Data as described in Section 9; and
  • comply with legal obligations.

D. Categories of Personal Data

Customer Personal Data may include:

  • Customer user and administrator data: name, email address, organization membership, role, authentication identifiers, account settings, and invitation data.
  • LinkedIn account data: selected LinkedIn account identifiers, public LinkedIn profile identifiers, session-related status metadata, sync status, quota status, and safety policy state.
  • LinkedIn contact and company data: names, profile URLs, public identifiers, headlines, avatars, cover images, locations, languages, education, experience, company information, follower counts, connection counts, relationship status, invitation status, and similar LinkedIn-derived profile or company information.
  • Conversation and workflow data: conversation identifiers, participant identifiers, timestamps, unread/favorite/archive state, tags, notes, custom fields, saved views, templates, drafts, scheduled messages, sequence steps, template runs, reply-guard metadata, and related workflow metadata.
  • Message content: LinkedIn message bodies, attachments, conversation history, drafts, generated replies, sent messages, scheduled messages, reply metadata, and related conversation content processed as part of the core Services, including when Customer invokes AI features using conversation context, sends messages through the Services, requests support involving message content, or otherwise transmits message content to TalkToHumans.
  • Enrichment data: enriched profile, company, work email, phone, and related status metadata when Customer uses enrichment features.
  • API and MCP data: access tokens, API keys, OAuth authorization metadata, tool request metadata, and Customer-authorized workspace data returned through API or MCP tools.
  • Billing data: plan, seat count, subscription status, invoice identifiers, payment method metadata, credit grants, credit usage, and usage reservations. Full card details are handled by Stripe and are not stored by TalkToHumans.
  • Support and operational data: support messages, troubleshooting information, logs, device/browser metadata, usage events, product analytics, diagnostic events, and security events.

E. Categories of Data Subjects

Customer Personal Data may concern:

  • Customer users, administrators, employees, contractors, and invitees;
  • Customer's LinkedIn contacts, prospects, leads, candidates, customers, partners, and other conversation participants;
  • employees or representatives of companies appearing in LinkedIn profile or company data;
  • individuals included in Customer notes, templates, messages, custom fields, support requests, or integrations.

F. Sensitive or Special Categories of Personal Data

The Services are not intended to process sensitive or special categories of Personal Data. Such data may be processed only if Customer or its users include it in free-form fields, messages, notes, templates, custom fields, support communications, LinkedIn messages, attachments, or other Customer-controlled content.

G. Processing Frequency

Continuous for hosted Services and as initiated by Customer or Customer users for specific features.


Schedule 2 - Technical and Organizational Measures

TalkToHumans maintains the following technical and organizational measures, taking into account the nature, scope, context, and purposes of processing.

1. Product Privacy Architecture

  • LinkedIn message bodies, attachments, and related conversation data are synced to and stored in backend systems by default, because core product features depend on server-side message sync.
  • Local browser persistence may also be used for caches, helper data, message copies, mutation intents, local app context, quota snapshots, link previews, and local participant caches.
  • Backend canonical storage is used for business entities and workflow data such as accounts, participants, chats, messages, chat participants, tags, notes, saved views, templates, AI actions, drafts, schedules, sequence steps, template runs, sync states, billing, subscriptions, invoices, and usage records.
  • API and MCP access to Customer workspace data is authenticated and Customer-authorized.

2. Authentication and Access Control

  • User authentication and organization membership are backed by WorkOS.
  • Backend requests are authenticated and scoped to organization/user tenant context.
  • Extension authentication uses backend-brokered extension sessions and short-lived extension JWTs.
  • Extension session tokens are stored server-side as hashes, and the extension does not store a WorkOS refresh token.
  • Backend authorization uses organization and user scoping to prevent cross-tenant access.
  • API and MCP access require authenticated, Customer-authorized credentials.
  • Production access is restricted to authorized personnel and contractors with a business need.

3. Chrome Extension and LinkedIn Boundary

  • LinkedIn actions execute through the Customer user's real logged-in browser session.
  • The extension accepts external requests only from allowlisted TalkToHumans origins.
  • The extension validates the active LinkedIn session and live LinkedIn headers before privileged LinkedIn requests.
  • Backend relay requests strip unsafe caller-provided authorization, cookie, CSRF, and LinkedIn tracing headers.
  • The extension applies safety gates, hard daily caps, token-bucket throttling, spacing, concurrency limits, jitter, and quota checks to LinkedIn actions.
  • The extension uses Chrome alarms for scheduled sequence execution while the user's browser is open.

4. Infrastructure and Network Security

  • The frontend is hosted on Vercel.
  • The backend runs on AWS ECS Fargate.
  • The primary database runs on AWS Aurora PostgreSQL / RDS in private subnets.
  • Backend tasks run in private subnets and connect to the database over restricted network paths.
  • Public backend traffic is routed through an AWS Application Load Balancer.
  • Organization media is stored in an AWS S3 bucket with public access blocked, bucket-owner enforced object ownership, versioning enabled, and CloudFront origin access identity for distribution.
  • Secrets are stored in AWS Secrets Manager and injected into backend tasks as secrets.
  • GitHub Actions uses AWS OIDC for deployment access rather than long-lived AWS user credentials where configured.
  • Application endpoints use HTTPS/TLS in production.

5. Logging, Monitoring, and Observability

  • Backend logs are written to AWS CloudWatch Logs with a one-year retention period in the current infrastructure configuration.
  • Production structured logs are also sent to Better Stack where configured.
  • Product analytics are sent through Segment and Mixpanel where configured.
  • Mixpanel session replay is disabled for the Services.
  • Analytics events are typed and designed to avoid arbitrary event names and arbitrary property bags.
  • Message text is intentionally excluded from backend analytics events for message sending and AI action tracking.
  • Internal logging guidance prohibits logging secrets and raw message bodies.

6. Data Minimization in AI and Enrichment

  • AI drafting is initiated by the user and sends only the prompt and selected variables needed for the requested output.
  • AI prompt preparation removes or compacts certain identifiers and verbose fields to reduce unnecessary prompt content.
  • TalkToHumans will not use Customer Personal Data to train general-purpose AI models unless Customer expressly authorizes that use in writing.
  • Enrichment, email finding, and phone finding are user-initiated or plan/credit-gated and run through configured upstream providers.
  • Credit-consuming upstream work uses local reservations before paid provider calls.

7. Security Operations

  • TalkToHumans restricts production access to authorized personnel and contractors with a business need.
  • TalkToHumans uses secrets management for production credentials.
  • TalkToHumans investigates suspected security incidents and notifies affected Customers as described in this DPA.
  • TalkToHumans applies reasonable development, review, deployment, and change-management practices appropriate to its size and stage.
  • TalkToHumans intends to begin pursuing an initial third-party security assessment targeting SOC 2 Type I starting in 2027.

8. Availability, Backup, and Recovery

  • TalkToHumans relies on managed infrastructure providers for database, storage, hosting, and operational resilience.
  • TalkToHumans maintains reasonable backup and recovery practices for hosted production systems. The production Aurora PostgreSQL cluster has automated backups enabled with a 1-day retention period.
  • Browser-local cached data may not be recoverable by TalkToHumans if deleted locally and not stored in backend systems.

9. Deletion and Retention

  • Customer Personal Data in active hosted systems is deleted or returned as described in the DPA and Agreement.
  • Billing, security, audit, and legal records may be retained where required or permitted by law.
  • Backup deletion follows normal backup expiration cycles.
  • Browser-local data is controlled by the Customer user's browser/device and may need to be deleted locally by the user or through browser/device management.

Schedule 3 - Subprocessors

This list reflects the current Services as of the Last Updated date above.

SubprocessorPurposePersonal Data ProcessedProcessing Location / Transfer NotesUse
Amazon Web Services (AWS)Backend hosting, database, object storage, logs, secrets management, email sending, CDN/media deliveryCustomer Personal Data stored or processed in backend systems, logs, media, secrets, operational metadata, support email metadata where applicablePrimary production AWS region: eu-west-3 (Paris). Includes ECS Fargate, Aurora PostgreSQL/RDS, S3, CloudFront, Secrets Manager, CloudWatch Logs, SES where enabled. Transfer mechanisms such as DPA/SCCs apply where requiredCore
VercelFrontend hosting and deliveryBrowser request metadata, application delivery metadata, frontend logs/telemetry where enabledUsed for frontend hosting and delivery. Transfer mechanisms such as DPA/SCCs apply where requiredCore
WorkOSAuthentication, organization management, user management, invitations, OAuth/MCP authorization supportUser names, emails, organization IDs, membership metadata, auth/session identifiersUsed for app auth and organization membership. Transfer mechanisms such as DPA/SCCs apply where requiredCore
StripeBilling, checkout, subscriptions, invoices, payment methods, credit grants, metered usageBilling contacts, payment metadata, invoice data, subscription data, usage and credit metadataFull payment card data is handled by Stripe, not stored by TalkToHumans. Transfer mechanisms such as DPA/SCCs apply where requiredBilling
Better StackLogging and observabilityOperational logs, diagnostic metadata, error/security events; excluding secrets and raw message bodies by policyProduction logging where configured. Transfer mechanisms such as DPA/SCCs apply where requiredOperations
SegmentProduct analytics routingUser/account/organization identifiers, event names, safe event properties, product usage metadataUsed for typed product analytics where configured. Transfer mechanisms such as DPA/SCCs apply where requiredAnalytics
MixpanelProduct analyticsUser/account/organization identifiers, event metadata, browser/device metadata, and product usage metadataEU Mixpanel endpoints; session replay disabled. Transfer mechanisms such as DPA/SCCs apply where requiredAnalytics
OpenRouterAI model routing and generationUser-submitted AI prompts, selected variables, draft text, and conversation/profile context when Customer invokes AI featuresDownstream model provider may vary by configured model; current code references OpenAI models through OpenRouter. Transfer mechanisms such as DPA/SCCs apply where requiredOptional AI
Enrichment and contact data providersLinkedIn profile enrichment, company enrichment, work email finding, and phone findingLinkedIn profile/company identifiers and returned profile, company, work email, phone, and related enrichment data when Customer invokes or enables these featuresUsed only for enrichment, email finding, or phone finding where configured. Specific provider names may be provided during a security review or on reasonable written request. Transfer mechanisms such as DPA/SCCs apply where requiredOptional enrichment

Schedule 4 - Standard Contractual Clauses

1. EU SCCs

1.1. The EU SCCs are incorporated by reference for Restricted Transfers that require them.

1.2. Modules. Module Two (Controller to Processor) applies where Customer is Controller and TalkToHumans is Processor. Module Four (Processor to Controller) applies where TalkToHumans is Processor in the EEA and Customer is Controller outside the EEA and a Restricted Transfer from TalkToHumans to Customer occurs.

1.3. Clause 7. The optional docking clause does not apply.

1.4. Clause 9. For Module Two, Option 2 applies, and the time period for prior notice of Subprocessor changes is 30 days as described in Section 10.

1.5. Clause 11. The optional language does not apply.

1.6. Clause 17. Option 1 applies. The EU SCCs are governed by French law.

1.7. Clause 18. Disputes under the EU SCCs will be resolved before the courts of France.

1.8. Annex I. The details of the Parties and processing are set out in this DPA, the Agreement, and Schedule 1.

1.9. Annex II. The technical and organizational measures are set out in Schedule 2.

1.10. Annex III. The Subprocessor list is set out in Schedule 3.

1.11. Competent supervisory authority. The competent supervisory authority will be determined under Clause 13 of the EU SCCs. Where TalkToHumans is the Data Exporter, the competent supervisory authority is the Commission Nationale de l'Informatique et des Libertes (CNIL) in France.

2. UK Addendum

2.1. For Restricted Transfers subject to the UK GDPR, the UK Addendum is incorporated by reference and completed as follows:

  • Table 1: the Parties' details are set out in this DPA and the Agreement.
  • Table 2: the selected EU SCC modules, clauses, and annexes are described in Section 1 of this Schedule 4.
  • Table 3: Annex I is completed by this DPA, the Agreement, and Schedule 1; Annex II is completed by Schedule 2; Annex III is completed by Schedule 3.
  • Table 4: neither Party may end the UK Addendum except as permitted by the UK Addendum.

3. Supplementary Measures

3.1. For Restricted Transfers, TalkToHumans will apply the technical and organizational measures in Schedule 2 and will take reasonable steps to evaluate transfer risks where required by Applicable Data Protection Law.

3.2. If TalkToHumans receives a legally binding request from a public authority for access to Customer Personal Data, TalkToHumans will review the request, challenge it where legally available and appropriate, and notify Customer where legally permitted.