Personal Data Processing Agreement
Version 1.0 · Last updated: 13 November 2026
(Article 28 of Regulation (EU) 2016/679 (GDPR) and Article 33 of Organic Law 3/2018 (LOPDGDD))
This agreement forms part of the Commercial Agreement for Establishments and is deemed accepted together with it.
Parties
- Data controller: the participating Establishment, identified in its registration application (hereinafter, the "Controller").
- Data processor: Joe Fernando Rodríguez Blanco, Tax ID 55297395J, registered address at Calle Chile, 7 - 28330 - San Martín de la Vega (Madrid), Spain (hereinafter, "QuienPide" or the "Processor").
1. Purpose and scope
QuienPide will process personal data on behalf of the Controller only to the extent necessary to provide the service described in the Commercial Agreement (management of orders, service points, diners, payments and the Establishment's staff). Excluded from this agreement are the processing activities in which QuienPide acts as controller (user accounts, the customer's personal history, consents, platform security and invoicing to establishments), which are governed by the Privacy Policy.
2. Description of the processing
| Element | Description |
|---|---|
| Nature | Hosting, recording, organisation, consultation, transmission to staff and to the service's diners, retention, backup and deletion |
| Purpose | To manage the Controller's hospitality service: assign service points, take and manage orders, split and record payments, communicate with the kitchen/bar |
| Duration | The term of the Commercial Agreement, plus the retention period in section 8 |
| Categories of data subjects | The Establishment's customers/diners; staff and managers linked to the Establishment |
| Types of data | Identification (name or alias, user), service point and service, orders, amounts and payment method, order notes (which may contain, if the data subject so decides, health data such as allergies or intolerances), staff contact data and role |
| Special categories | Not requested; they may appear voluntarily in order notes. The Controller assumes the legal basis (explicit consent or vital interest) and will avoid their use for purposes other than fulfilling the order |
3. Obligations of the Processor
QuienPide undertakes to:
- Process the data only on the Controller's documented instructions (this agreement and the configured use of the platform), including with regard to international transfers, unless required to do so by law, in which case it will inform the Controller before processing unless prohibited by law. It will inform the Controller if, in its opinion, an instruction infringes the applicable rules.
- Not use the data for its own purposes nor disclose it to third parties, except as provided in this agreement.
- Ensure that the persons authorised to process the data have committed themselves to confidentiality (or are under a statutory obligation) and receive the necessary training.
- Apply the technical and organisational measures in section 6 (art. 32 GDPR).
- Sub-processors: the Controller grants general authorisation to engage sub-processors, of the categories and providers indicated in section 7. QuienPide will inform the Controller of any addition or replacement 30 days in advance, during which the Controller may object on justified grounds; it will impose on sub-processors the same data protection obligations and will be liable to the Controller for their non-compliance.
- Assist the Controller, by appropriate technical and organisational measures, in responding to data subjects' rights (access, rectification, erasure, objection, restriction, portability). If a data subject contacts QuienPide, it will refer them to the Controller, unless the data is data for which QuienPide is the controller.
- Notify the Controller without undue delay, and in any event within 48 hours, of becoming aware of a personal data breach, with the information available (nature, categories and approximate number of those affected, likely consequences and measures taken) so that the Controller can meet its obligations to the authority and the persons affected.
- Assist the Controller with data protection impact assessments and prior consultations where appropriate, taking into account the information available to it.
- Keep a record of processing activities carried out on behalf of the Controller (art. 30.2 GDPR) and appoint a data protection officer where mandatory.
- Make available to the Controller the information necessary to demonstrate compliance and allow for audits, including inspections, carried out by the Controller or an authorised auditor, with 15 days' notice, once a year except in the event of incidents, during business hours, without compromising the security or confidentiality of other customers, and at the Controller's expense unless they reveal a material breach. QuienPide may demonstrate compliance by means of reports or certifications from independent audits.
4. Obligations of the Controller
The Controller undertakes to:
- Comply with the GDPR and the LOPDGDD as controller: have a legal basis for the processing, inform data subjects (customers and staff) and respond to their rights.
- Provide QuienPide with the necessary data and instructions and not enter unnecessary or excessive data on the platform (for example, health data in free-text fields).
- Correctly configure the roles and permissions of its staff and safeguard their credentials.
- Inform QuienPide without delay of any circumstance affecting this agreement.
- Answer to data subjects and authorities for its own decisions and instructions.
5. International transfers
The data is hosted in the European Union. QuienPide will not transfer data to countries outside the European Economic Area without complying with Chapter V of the GDPR (adequacy decision, standard contractual clauses or other safeguards) and without the Controller's documented authorisation, which is deemed granted for the sub-processors in section 7 with the safeguards indicated there.
6. Security measures
QuienPide applies, among others, the following measures (which may be replaced by others offering at least the same level of protection):
- Encryption in transit (TLS) and at rest; encryption of sensitive fields.
- Role-based access control with isolation per establishment (each establishment can only access its own data); principle of least privilege.
- Strong authentication: passwords hashed with Argon2id, short-lived tokens, attempt limits and mandatory MFA for administrators.
- Logging and auditing of critical actions; absence of personal data and secrets in technical logs.
- Encrypted backups, replication in another EU region and periodic restoration tests (RPO ≤ 15 min, RTO ≤ 1 h).
- Pseudonymisation or anonymisation where possible; minimisation and automatic purging according to the periods in section 8.
- Vulnerability management, updates and incident response; separation of environments.
7. Authorised sub-processors
| Category | Provider / example | Purpose | Location |
|---|---|---|---|
| Cloud infrastructure | Provider to be appointed (to be notified under the sub-processor clause), EU region | Hosting, database, backups | EU |
| Transactional email | Provider to be appointed (to be notified under the sub-processor clause) | Sending service emails | EU/EEA (or with art. 46 safeguards) |
| Notifications to administrators | Telegram (optional) | Internal operational alerts (without customer data) | Depending on provider, with safeguards |
| Observability | Provider to be appointed (to be notified under the sub-processor clause) | Metrics and traces without personal data | EU |
Payment providers currently play no part in the service: collections are made through the Establishment's traditional method. The AI provider only receives menu content (photos of dishes, ingredients), not personal data, and is therefore not a sub-processor.
8. Retention, return and deletion
- While the Agreement is in force, data is retained in accordance with the platform's periods: services, orders, accounts and payments, 24 months online and restricted archive for up to 7 years for legal obligations; email events, 90 days; tokens, until expiry.
- Upon termination of the Agreement, and at the Controller's choice notified within the following 30 days, QuienPide will return the data to it in a structured, commonly used format and, afterwards, will delete or anonymise it, including copies, except data it must retain by legal obligation, which it will keep blocked and solely for that purpose.
- Backups are deleted naturally according to their retention cycle (up to 12 months), without intermediate use.
9. Liability
Each party is liable for the damages and penalties it causes by breaching the GDPR and this agreement, in accordance with Article 82 GDPR and the liability rules of the Commercial Agreement. QuienPide is liable for damages resulting from having departed from the Controller's lawful instructions or from failing to comply with the GDPR obligations specific to processors.
10. Term, governing law and jurisdiction
This agreement lasts for as long as QuienPide processes data on behalf of the Controller. It is governed by Spanish law and the GDPR, and is subject to the jurisdiction agreed in the Commercial Agreement. In the event of conflict with the Commercial Agreement on data protection matters, this agreement prevails.
11. Privacy contact
QuienPide: jfrodriguezb@gmail.com · DPO (if applicable): No Data Protection Officer has been appointed (not mandatory). Contact: jfrodriguezb@gmail.com