Data Processing Agreement

Data Processing Agreement

Data Processing Agreement

SALESCALING, in its capacity as Data Processor (hereinafter the “PROCESSOR”), shall process the personal data received from the CLIENT, as Data Controller (hereinafter the “CONTROLLER”), in relation to the execution of the Service Agreement, following the instructions and purposes determined by the CONTROLLER.

For the purposes of this Agreement, “CLIENT” refers to any natural or legal person or affiliate entity of the Client that has entered into a service agreement with SALESCALING and processes personal data for which it is responsible to ensure the provision of services under the agreement between both parties.

Both parties, in the exercise of their respective powers, agree to sign this Personal Data Processing Agreement (hereinafter, the “Agreement”), in compliance with the provisions of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 (General Data Protection Regulation, hereinafter “GDPR”) and Organic Law 3/2018, of 5 December, on the Protection of Personal Data and Guarantee of Digital Rights (“LOPDGDD”), in accordance with the following,

Stipulations

1. Object

1.1. The PROCESSOR, within the framework of this Agreement, shall process personal data on behalf of the CONTROLLER in accordance with the terms and conditions established in this document.

1.2. The purpose of the processing is the provision of the Services specified in the service agreement that covers this Agreement.

1.3. The duration of the processing shall last as long as the contractual relationship between the parties is maintained and until the deletion of the personal data in accordance with the provisions of this Agreement.

1.4. In relation to the Agreement, the CONTROLLER is the person who determines the purposes and means for which the CONTROLLER's Data are processed by the processor (as defined below).

1.5. The personal data provided by the CONTROLLER to the PROCESSOR refer to the categories of data and data subjects indicated in Appendix I.

2. Obligations of the Data Processor

The PROCESSOR and all its personnel commit to the following obligations:

2.1. To use the personal data subject to processing, or those collected for inclusion, only for the purpose of this assignment. Under no circumstances may the data be used for its own purposes. 2.2. To process the data in accordance with the documented instructions of the CONTROLLER. 2.3. If the PROCESSOR considers that any of the instructions infringe the GDPR, LOPDGDD, or any other provision regarding data protection of the European Union or Member States, the PROCESSOR shall immediately inform the CONTROLLER. 2.4. Not to communicate the data to third parties, unless it has the prior express written authorization of the CONTROLLER, in the legally established and admissible cases. 2.5. The PROCESSOR may communicate the data to other processors of the same controller, in accordance with the instructions of the CONTROLLER. In this case, the CONTROLLER shall identify, in advance and in writing, the entity to which the data must be communicated, the data to be communicated, and the security measures to be applied to proceed with the communication. 2.6. The PROCESSOR shall transfer personal data to a third country or an organization only under the documented instructions of the CONTROLLER. If the PROCESSOR must transfer such personal data to a third country or an international organization, by virtue of the European Union or Member State law applicable to it, it shall inform the CONTROLLER of that legal requirement in advance, unless such law prohibits it for important reasons of public interest. 2.7. Likewise, the PROCESSOR is obliged to return to the CONTROLLER the medium or media containing the personal data, or to destroy them, at the latter's request, once the provision of services has ended, without keeping any copy thereof, unless established otherwise by the CONTROLLER.

2.8. Subcontracting.

a. The PROCESSOR may subcontract with third parties the execution of personal data processing activities for the correct provision of the services object of this Agreement, including certain necessary technical and IT services and necessary auxiliary services.

b. By virtue of the provisions of the GDPR and LOPDGDD, any subcontracting of the service carried out for the fulfillment of the contract that the PROCESSOR wishes to perform must be communicated to the CONTROLLER at the email address indicated in the Particular Conditions, indicating the processing operations intended to be subcontracted and clearly and unequivocally identifying the subcontractor company and its contact details. Subcontracting may be carried out if the CONTROLLER does not express its opposition within 5 days of the communication.

c. The list of authorized Sub-processors or providers is found in Appendix I.

d. The subcontractor, who will also have the status of data processor, is also obliged to comply with the obligations established in this document for the PROCESSOR and the instructions issued by the CONTROLLER.

e. It is the responsibility of the PROCESSOR to sign a new contract with the new processor so that it remains subject to the same conditions and with the same formal requirements as the PROCESSOR, regarding the adequate processing of personal data and the guarantee of the rights of the affected persons. In the event of non-compliance by the sub-processor, the PROCESSOR shall remain fully liable to the CONTROLLER regarding the fulfillment of the obligations.

2.9. The PROCESSOR may share the CONTROLLER's personal data with those service providers or third-party companies, including artificial intelligence services, upon instruction from the CONTROLLER. In such a case, given that the PROCESSOR acts following the instructions of the CONTROLLER, it shall not be required to notify the latter, and it shall be the CONTROLLER who ensures that said provider complies with the guarantees regarding personal data protection and its adequacy to the applicable regulations.

2.10. To maintain the duty of secrecy regarding the personal data to which the PROCESSOR has had access by virtue of the services provided to the CONTROLLER, even after the relationship between both has ended.

2.11. To ensure that persons authorized to process personal data commit, expressly and in writing, to respect confidentiality and to comply with the corresponding security measures, of which they must be duly informed.

2.12. To keep at the disposal of the CONTROLLER the documentation proving compliance with the obligation established in the previous section.

2.13. To ensure the necessary training in personal data protection for persons authorized to process such data.

2.14. To assist the CONTROLLER, taking into account the nature of the processing, through appropriate technical and organizational measures, whenever possible, so that the latter can comply with its obligation to respond to requests aimed at exercising the rights of data subjects.

2.15. When the affected persons exercise the rights of access, rectification, erasure, and objection, restriction of processing, data portability, and not to be subject to automated individual decisions before the PROCESSOR, the latter must communicate it by email to the address indicated by the CONTROLLER. The communication must be made as soon as possible, making its best efforts to ensure it occurs within 3 working days from the receipt of the request, and will include, where appropriate, other information that may be relevant to resolve the request.

2.16. Right to information. It is the responsibility of the CONTROLLER to facilitate the right to information at the time of data collection.

2.17. Notification of data security breaches

a. The PROCESSOR shall notify the CONTROLLER, without undue delay, and in any case before the maximum period of 36 hours, and through a simple communication, of any security breaches of which it becomes aware regarding the data under its charge, together with all relevant information and documentation of the incident.

b. Notification will not be necessary when it is unlikely that such a security breach constitutes a risk to the rights and freedoms of natural persons.

c. The notification shall include at least the following information:

text
  i. Description of the nature of the personal data security breach, including, where possible, the categories and approximate number of affected data subjects, and the categories and approximate number of affected personal data records.

  ii. The name and contact details of the data protection officer or another contact point where more information can be obtained.

  iii. Description of the possible consequences of the personal data security breach.

  iv. Description of the measures taken or proposed to remedy the personal data security breach, including, if applicable, the measures taken to mitigate possible negative effects. If it is not possible to provide the information simultaneously, and to the extent that it is not, the information shall be provided gradually without undue delay.

2.18. To support the CONTROLLER in carrying out data protection impact assessments, when appropriate.

2.19. To support the CONTROLLER in carrying out prior consultations with the supervisory authority, when appropriate.

2.20. To make available to the CONTROLLER all information necessary to demonstrate compliance with its obligations, as well as to carry out audits or inspections carried out by the controller or another auditor authorized by it, when required.

2.21. Security Measures. The PROCESSOR undertakes to apply to the personal data the necessary security measures to prevent their alteration, loss, unauthorized processing, or access, taking into account the state of the technology, the nature of the stored data, and the risks to which they are exposed, whether they come from human action or the physical or natural environment. In this sense, in accordance with the provisions of Articles 24 and 32 of the GDPR, the PROCESSOR is obliged to have implemented appropriate technical and organizational security measures.

2.22. Specifically, the PROCESSOR shall adopt the security measures established in Appendix I.

2.23. Destination of the data. The PROCESSOR undertakes to destroy the data once the service has been fulfilled. However, the PROCESSOR may keep a copy, with the data duly blocked, as long as liabilities may arise from the execution of the service.


3. Obligations of the Data Controller

The CONTROLLER undertakes to:

3.1. Be responsible for the personal data subject to processing.

3.2. Carry out an impact assessment on the protection of personal data for the processing operations to be carried out by the processor when appropriate.

3.3. Guarantee the duty of information to the data subjects in accordance with Arts. 13 and 14 of the GDPR.

3.4. Carry out the corresponding prior consultations.

3.5. Ensure, in advance and throughout the entire processing, the compliance with the GDPR and LOPDGDD by the PROCESSOR.

3.6. Communicate changes in the basic structure of the data that imply or may imply a change in the application of security measures.

3.7. Provide the PROCESSOR with access only to those data that are adequate, relevant, and not excessive, based on the purpose of the contracted service.

3.8. The CONTROLLER must guarantee to the owner of the personal data, depending on the nature, scope, context, and purposes of the processing, based on the provisions of Article 24 of the GDPR, that it has adopted the appropriate technical and organizational measures to maintain the security of the personal data provided.

3.9. It is the responsibility of the CONTROLLER to communicate data security breaches to the data subjects in the shortest possible time, when it is likely that the breach poses a high risk to the rights and freedoms of natural persons.

The communication must be made in clear and simple language and must, at a minimum:

a. Explain the nature of the data breach.

b. Indicate the name and contact details of the data protection officer or another contact point where more information can be obtained.

c. Describe the possible consequences of the personal data security breach.

d. Describe the measures taken or proposed by the data controller to remedy the personal data security breach, including, if applicable, the measures taken to mitigate possible negative effects.

3.10. The CONTROLLER shall ensure that the service providers or third-party companies to which the PROCESSOR communicates personal data under the instruction of the CONTROLLER comply with the guarantees regarding data protection and other current regulations and shall be responsible to the PROCESSOR.


Appendix I to the Data Processing Agreement regarding processing details

1. Purpose(s) of the processing:

To ensure the provision of the service(s) contracted by the CONTROLLER, in accordance with the Service Agreement. Said processing may include different technological services, such as the recording and transcription of calls and meetings, as well as the use of SDRs through AI Agents between the CONTROLLER and its workers or end customers.

2. Type of personal data provided by the CONTROLLER to the PROCESSOR:

  1. Identification data (e.g., name and surname, phone number, email, etc.)
  2. Professional and company data (e.g., job title, company, industry, professional contact details, user identifier in internal systems)
  3. System access and usage data (e.g., user identifiers, access logs, IP addresses, cookies, logs)
  4. Technical and operational data.
  5. Audio and video recordings of calls.
  6. The Parties will not intentionally collect or process any special categories of data. The PROCESSOR will immediately inform of any involuntary receipt of special categories of data.

3. Categories of personal data processed by the PROCESSOR:

  1. Employees of the CONTROLLER.
  2. Customers, potential customers, their employees, contacts, or end users of the CONTROLLER.

4. Type of processing performed

The Assignment will involve the following processing of personal data:

  1. Data storage and preservation, registration, retrieval, and data entry.
  2. Access and consultation of information.
  3. Voice recording.
  4. Information processing using AI.
  5. Audio transcription using AI.
  6. Semantic analysis of text.
  7. Data analysis and processing.
  8. Integration with AI platforms or third-party systems.
  9. Anonymization or pseudonymization of data.
  10. Deletion or destruction of data.
  11. Updating of data, including its correction, adaptation, alteration, alignment, and combination.

5. Security measures

Category | Implemented security measure

Organizational measures

  • Periodic security assessments.
  • Secure and automated processes (CI/CD).

Technical measures

  • Encryption of data at rest and in transit.
  • Session tokens.
  • Antivirus scanning.
  • Protection against attacks (injection, XSS, SSRF).

Access control measures

  • Authentication by trusted providers and OTP.
  • Role-based authorization (OpenFGA).
  • 2FA on administrative interfaces.

Continuity and recovery measures

  • Automated deployments with recovery <10 min.
  • Monitoring and verification of configurations.
  • Periodic backups.

6. Authorized sub-processors

Last update of the list: November 2026. Salescaling will notify changes in accordance with clause 2.8 of this agreement.

Provider/Sub-processorService providedLocation / configured regionInternational transfers
Amazon Web Services (AWS)S3 storage, CloudFront CDN (streaming), backupseu-west-1 (Ireland)N/A
Google Cloud (Vertex AI)Generative AI (Gemini)Madrid (europe-southwest1)N/A
SupabasePostgreSQL databaseEuropeN/A
DigitalOceanAPI hosting, Redis (queues and cache)EuropeN/A
VercelFrontend hostingEuropeN/A
Auth0 (Okta)Authentication and authorizationEU; possible support from USSCCs
AssemblyAIAudio transcription and diarizationEU RegionN/A
HyperdocMeeting bots and recording (incl. Desktop SDK)Flow to storage in EUPossible US — SCCs
SvixWebhook gateway (relay and retries)EUN/A
NylasEmail and calendar APIEUPossible US — SCCs
TelnyxTelephony and call signalingEU (configured EU regions)Possible US — SCCs
ElevenLabsConversational voice agentPer ElevenLabs contractPossible US — SCCs
StripePayment processingStripe Payments EuropeSCCs (Stripe group)
ResendTransactional email sendingPer Resend contractPossible US — SCCs
DatadogMonitoring and logsEU site when applicablePossible US — SCCs
PostHogProduct analytics and feature flagsEU cloud when applicablePossible US — SCCs

Optional integrations (only if the controller activates them): Slack; connected CRMs (HubSpot, Pipedrive, Zoho, Membrain, ActiveCampaign, etc.); lead enrichment providers (e.g., Wiza); Zoom in the bot flow via Hyperdoc.

Retired sub-processors (replaced or discontinued): Bunny.net (CDN → CloudFront); Crisp (chat); Meilisearch (search).