Clear data, in writing.
01 · Hosting
Primary infrastructure in the EU. International transfers are covered by this DPA and the applicable safeguards.
02 · Models
We do not use customer data to train models shared between customers.
03 · Exit
Return or deletion within 30 days. Backups are overwritten within 90 days.
This Data Processing Agreement ("Agreement" or "DPA") forms part of the subscription or services agreement for lapersona.ai (the "Contract") between YN MOUNTAIN, S.L., with registered address at Calle Jorge Juan 64, 1 IZQ, 28009 Madrid, España and Tax ID B24978355 ("Processor"), and the customer identified in the Contract ("Controller").
It applies when YN MOUNTAIN, S.L. processes personal data on the customer's behalf while providing lapersona.ai. It forms part of the Contract when the Contract expressly incorporates it and both parties accept it, on paper or through the electronic acceptance mechanism they use.
01Subject, duration and nature of the processing
The Processor will process personal data only to provide, maintain, protect and support lapersona.ai, for the term of the Contract and in accordance with the Controller's documented instructions, including configurations and actions performed by its users.
Processing may include collection, recording, organisation, consultation, use, transmission to authorised providers, storage and deletion, depending on the features the Controller chooses to use.
02Categories of data subjects and data
Depending on the features used, processing may include:
- Data subjects: the Controller's users and employees; customers, prospects and professional contacts; individuals whose data the Controller includes or makes accessible through instructions or integrations; and other individuals whose data is included in the processed content.
- Data: identification and professional contact data; role and company; commercial and CRM information; conversation content, instructions and files; communications and data obtained through connected integrations; and technical metadata related to use.
- Special categories: the service is not designed to process special categories of data or minors' data. The Controller will not include them unless the parties agree in writing beforehand and the necessary additional safeguards are in place.
03Controller obligations
The Controller:
- determines the purposes and means of processing and ensures it has a valid legal basis;
- provides privacy information and handles data subject rights;
- ensures its instructions and use of integrations comply with law and third-party rights;
- limits data to what is necessary and does not provide special categories or minors' data without authorisation and adequate safeguards;
- protects its credentials and manages user permissions;
- promptly notifies the Processor of any unlawful instruction it identifies.
04Processor obligations
The Processor:
- processes data only on the Controller's documented instructions and to provide the service, unless required by law;
- ensures that authorised persons are bound by confidentiality obligations;
- implements appropriate technical and organisational measures to protect the data;
- reasonably assists the Controller with data subject requests, impact assessments, prior consultations and breach notifications;
- notifies the Controller without undue delay after becoming aware of a security breach affecting data processed on its behalf;
- makes available reasonable information to demonstrate compliance and allows audits under clause 09;
- informs the Controller if, in its opinion, an instruction infringes data protection law.
05Subprocessors
The Controller generally authorises the engagement of the subprocessors identified in Annex III, which sets out their identity, function and processing location. The Processor will impose data protection obligations on each subprocessor that are no less protective than those in this Agreement and remains liable to the Controller as required by law.
The Processor will notify the Controller by email or through the platform of any planned change to the list at least 30 days in advance, except for urgent substitutions for security, continuity or legal compliance. The Controller may raise a reasoned objection on data protection grounds within 15 days of the notice.
06International transfers
The Processor will allow international transfers only when necessary to provide the service and in accordance with applicable law, through an adequacy decision, standard contractual clauses or another valid mechanism. The subprocessor list identifies known locations and applicable safeguards.
07Security
The Processor will implement appropriate technical and organisational measures to protect data against unauthorised destruction, loss, alteration, disclosure or access, taking into account the state of the art, implementation costs, the nature of the processing and the risks to individuals. On reasonable request, it will provide a current description of the measures applicable to the service.
08Return and deletion
At the end of the service, the Controller may request the return or deletion of personal data processed on its behalf within 30 days of termination, using the available features or by contacting privacidad@lapersona.ai. Once the requested return is complete, the Processor will delete remaining data from active systems within the same period, unless retention is required by law.
Backups are overwritten in the ordinary technical cycles, within a maximum of 90 days after deletion from active systems. Until then they remain protected and are not restored except for continuity or recovery needs.
09Information and audits
On reasonable request, the Processor will provide the information necessary to demonstrate compliance with this Agreement. Audits require at least 30 days' notice, take place during business hours, are limited to the Controller's processing and are subject to confidentiality, security and protection of other customers' information. Independent reports or available certifications will be prioritised. If they are insufficient, the Controller may conduct an audit no more than once a year, except after an incident or a request from an authority.
10Precedence, term and governing law
This Agreement remains in force while the Processor processes personal data on the Controller's behalf. If there is a conflict between this Agreement and the Contract regarding data protection, this Agreement prevails on that subject. Matters not covered are governed by the Contract, including its governing law and jurisdiction.
IAnnex I — Processing details
- Subject
- Provision of lapersona.ai and the features enabled by the Controller.
- Duration
- The term of the Contract and, after termination, the return/deletion period and backup cycle in clause 08.
- Purpose
- Operate the service features, process instructions and data provided or connected by the Controller, provide support and protect the service.
- Operations
- Consultation, organisation, storage, analysis, transmission to authorised subprocessors and deletion.
- Data subjects
- The Controller's users and individuals whose data the Controller enters, uploads or connects.
- Personal data
- Identification, professional contact, company, commercial data, content of instructions/conversations/files, communications and data obtained through integrations, plus technical metadata.
- Special categories
- Not envisaged. Require specific agreement and safeguards before processing.
IIAnnex II — Functional scope and data use
The Controller determines which data sources it connects and which instructions and content it provides. The Processor will process that data for the features the Controller enables, which may include consultation, synchronisation, organisation, analysis and generation of results through automated systems or artificial intelligence models.
YN MOUNTAIN, S.L. does not use the Controller's personal data or content to train or improve models shared between customers. When the service sends content to model providers to generate a response, those providers process it to provide the requested inference and are not authorised to use it to train shared models.
Connecting an external source does not by itself constitute unlimited authorisation: processing is limited to the features enabled by the Controller and the subject of this Agreement. Technical permissions for each integration are described in its functional information.
IIIAnnex III — Authorised subprocessors
The table below identifies providers that may participate in processing depending on the features used. The location describes the provider's known entity or region; processing may involve other locations or transfers depending on the provider, configuration and enabled feature, with the applicable safeguards.
| Provider | Service / purpose | Data it may process | Location / transfers |
|---|---|---|---|
| Cloudflare, Inc. | Application and workflow execution, file storage, transactional email and infrastructure. | Account and organisation; service data, conversations, files and technical logs. | Global infrastructure; transfers under Cloudflare's DPA and applicable mechanism, including SCCs. |
| Amazon Web Services (AWS) | Agent session stream via S2. | Session stream events and state. | eu-north-1 (Stockholm, Sweden) for the production basin; AWS contractual safeguards. |
| OpenRouter and model providers | Routing and response generation through AI models. | Instructions, context, content sent to the agent and generated results. | OpenRouter operates from the US; models and regions vary; exclusive EEA residency is not guaranteed. |
| Unipile | Messaging and external service connectors enabled by the Controller. | Connected account, contacts, messages and integration metadata. | Primary infrastructure in France/EEA; subprocessors may process in other locations, including the US. |
| Composio | Connection and execution of third-party tools enabled by the Controller. | Instructions, tool requests and responses. | AWS infrastructure; locations and subprocessors listed in its trust center. |
| Loops (Astrodon Corporation) | Account contact management and product lifecycle events. | Name, email, organisation and basic usage events. | Subprocessors in the United States; Loops DPA and safeguards. |
| Google LLC | Authentication for users who choose Google sign-in. | Authentication identifiers and basic profile. | US and other regions; limited to account authentication. |
Stripe is used for payments and subscriptions of YN MOUNTAIN, S.L. and processes billing data in that relationship; it does not process CRM content or agent data on the Controller's behalf as part of the service. CRM, email, calendar and other tools the Controller connects directly process data under the relationship between the Controller and those providers, not as subprocessors of YN MOUNTAIN, S.L.. Error telemetry uses its own transport and does not send events to an external Sentry service.
Privacy contact
To exercise rights, request a signed copy or ask a question about this Agreement: privacidad@lapersona.ai.