Data Processing Agreement

Version 1.0.0 — Effective from 1 November 2026

This Data Processing Agreement ("DPA" or "Agreement") forms an integral part of the LeadRescue Terms of Service ("Main Agreement") and applies whenever LeadRescue processes personal data on behalf of the Customer in the context of providing the Service.

By agreeing to the Terms of Service, the Customer also unreservedly accepts the provisions of this DPA.


1. Parties and roles

Data Controller: The Customer, being the natural or legal person who has created an account with LeadRescue and who determines the purposes and means of processing personal data of their Callers ("Controller").

Data Processor: LeadRescue, established in Belgium, reachable via privacy@leadrescue.be ("Processor").

Both parties are together referred to as the "Parties".

This DPA governs the processing of Callers' personal data by the Processor on behalf of and for the account of the Controller, in accordance with Article 28 of Regulation (EU) 2016/679 (GDPR).


2. Subject matter, nature and purpose of processing

2.1 Subject matter

The Processor processes Callers' personal data solely for the purpose of delivering the agreed Service, specifically:

  • Detecting forwarded missed calls via the Twilio Number assigned to the Controller;
  • Automatically sending Controller-personalised SMS messages to Callers;
  • Retaining call and SMS logs for reporting and management by the Controller;
  • Optionally recording voicemail messages from Callers who cannot receive SMS (fixed-line numbers, anonymous numbers).

2.2 Nature of processing

Automated processing via webhook triggers, API calls and database storage.

2.3 Duration of processing

Processing begins when the Controller activates their account and continues for as long as the Main Agreement is in force. After termination of the Main Agreement, processed data is retained in accordance with the retention periods set out in this DPA and the Privacy Policy, after which it is permanently deleted.


3. Categories of data subjects and personal data

3.1 Categories of data subjects

Data subjects are the Callers of the Controller: clients, prospects or other persons who contact the Controller by telephone.

3.2 Categories of personal data

CategorySpecific data
Contact dataCaller's telephone number (E.164 format)
Communication dataTime of call, duration (if applicable), content of SMS message sent
Technical dataTwilio Call SID, Twilio Message SID, delivery status
Audio recordings (optional)Voicemail recording (max. 30 seconds) where Caller uses a fixed line or withholds their number

3.3 Special categories

The Processor does not process special categories of personal data within the meaning of Article 9 GDPR (health data, racial or ethnic origin, political opinions, etc.) in the context of the Service. The Controller expressly undertakes not to include such data in SMS templates or voicemail greetings.


4. Processor obligations

The Processor undertakes to:

4.1 Follow instructions

Process personal data solely on the basis of documented instructions from the Controller, as set out in the Main Agreement and this DPA, unless a legal obligation applicable to the Processor requires otherwise. In the latter case, the Processor will notify the Controller before commencing the processing, unless the law prohibits this.

4.2 Confidentiality

Ensure that all persons authorised to process the personal data have committed themselves to confidentiality or are subject to an appropriate statutory obligation of confidentiality.

4.3 Security

Implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, as referred to in Article 32 GDPR. These measures include at least:

  • Encryption of personal data in transit (TLS 1.3) and at rest (AES-256);
  • Access control based on the principle of least privilege;
  • Procedures for regularly testing, assessing and evaluating the effectiveness of security measures;
  • Two-factor authentication for administrator access to production systems.

4.4 Sub-processors

The Processor may only subcontract processing to sub-processors with the prior written authorisation of the Controller. By agreeing to this DPA, the Controller gives general prior authorisation for the use of the sub-processors listed in Annex 1 to this DPA. The Processor will notify the Controller at least thirty (30) days in advance of any intended changes to the list of sub-processors. The Controller has the right to object to the appointment of a new sub-processor on reasonable grounds. The Processor imposes on all sub-processors the same obligations as set out in this DPA.

4.5 Assistance with data subject requests

Taking into account the nature of the processing, the Processor shall assist the Controller in fulfilling its obligation to respond to requests from data subjects exercising their rights under the GDPR (access, rectification, erasure, restriction, portability, objection).

4.6 Assistance with security obligations

The Processor shall assist the Controller in complying with its obligations under Articles 32 to 36 GDPR (security, data breach notification, data protection impact assessment).

4.7 Data breach notification

The Processor shall notify the Controller without undue delay and in any case within 36 hours of becoming aware of a personal data breach affecting the processed data. This notification shall include at least:

  • A description of the nature of the breach, the categories and estimated number of persons concerned;
  • The name and contact details of the data protection officer or other contact point;
  • The likely consequences of the breach;
  • The measures the Processor has taken or proposes to take to address the breach.

4.8 Deletion or return of data

Upon termination of data processing services, the Processor shall delete or return all personal data to the Controller, at the Controller's choice, unless applicable Union or Member State law requires retention of the data.

4.9 Audit rights

The Processor shall grant the Controller or a mandated auditor the right to conduct audits regarding compliance with this DPA, subject to at least thirty (30) days' prior notice, during normal business hours and without causing unnecessary disruption to operations. The costs of such audits are borne by the Controller.


5. Controller obligations

The Controller undertakes to:

  • Process Callers' personal data in compliance with applicable law, including the GDPR and the Belgian Law of 13 June 2005;
  • Only have personal data processed by the Processor for which a valid legal basis exists;
  • Correctly and transparently inform Callers of the fact that their telephone number and call data are processed by an external service provider (LeadRescue) for the purpose of automatically sending an SMS upon a missed call;
  • Immediately notify the Processor if in their opinion the Controller's instructions are incompatible with the GDPR or other applicable data protection law;
  • Not include special categories of personal data within the meaning of Article 9 GDPR in SMS templates.

6. International transfers of personal data

The Processor may only transfer personal data to countries outside the European Economic Area (EEA) where an adequate level of protection exists under Chapter V GDPR. The Processor uses only the following transfer instruments:

  • Standard Contractual Clauses (SCCs) approved by the European Commission (Decision 2021/914/EU);
  • Adequacy decisions of the European Commission for the relevant country;
  • EU-US Data Privacy Framework for certified US processors.

The specific transfer instruments per sub-processor are listed in Annex 1. The Controller acknowledges and accepts that certain sub-processors (in particular Twilio Inc. for SMS delivery) are located outside the EEA and that personal data (Callers' telephone numbers) is transferred to these sub-processors solely for the purposes described in this DPA.


7. Liability

7.1 Internal allocation

Each Party is liable to data subjects for damage caused by its processing activities in breach of the GDPR. Where a data subject claims compensation and both Parties are liable, liability is allocated according to their respective responsibility for the damage suffered.

7.2 Limitation

The Processor's liability to the Controller under this DPA is limited to the amount set out in the Main Agreement.


8. Duration and termination

This DPA is in force for as long as the Main Agreement is valid. Upon termination of the Main Agreement for any reason, this DPA terminates automatically. The provisions on deletion or return of data (Article 4.8) and confidentiality obligations remain in force after termination.


9. Governing law and dispute resolution

This DPA is governed by Belgian law. Disputes are submitted to the competent courts of Brussels, in accordance with Article 12 of the Main Agreement.


10. Contact details

For questions about this DPA or data protection requests:

LeadRescue Email: privacy@leadrescue.be Location: Belgium


Annex 1 — Approved sub-processors

Sub-processorActivitiesCountry of establishmentTransfer instrument
Twilio Inc.SMS delivery, telephone infrastructure, voicemailUnited StatesSCCs (EU-US Data Privacy Framework)
Google LLC (Firebase/Firestore)Database storage, authentication, file storageEU (Frankfurt, Germany)No transfer outside EEA
Paddle.com Market LimitedPayment processingUnited KingdomEU Adequacy decision (United Kingdom)
OpenAI, LLCAI message generation (optional, only if enabled)United StatesSCCs
Resend, Inc.Transactional emailUnited StatesSCCs
Sentry, Inc.Error logging and application monitoringUnited StatesSCCs
Vercel, Inc.Web hosting, serverless functionsEU / United StatesSCCs for US infrastructure

The Processor undertakes to keep this annex up to date and to notify the Controller of any changes in a timely manner.