Data Processing Agreement (Article 28 GDPR)
This agreement is entered into between:
- the Customer, a business holding a RiLoPOS account, acting as controller;
- WellensMedia SRL, Esplanade 5, 7800 Ath, Belgium, company number 0537.612.404, acting as processor.
It forms an integral part of the terms and conditions of use and applies as soon as the account is opened. It implements Article 28(3) of Regulation (EU) 2016/679 (the "GDPR").
1. Subject matter#
The processor processes personal data on behalf of the Customer for the sole purpose of providing it with the RiLoPOS service: point of sale, back office, synchronisation, backup, and the modules activated by the Customer.
2. Duration#
The agreement applies for the entire term of the subscription and thereafter until the return and deletion of the data provided for in Article 11.
3. Nature and purposes of the processing#
Hosting, recording, synchronisation between the point-of-sale terminals and the cloud, consultation, formatting (receipts, reports, exports), transmission to the recipients chosen by the Customer (fiscal module, payment terminal, delivery platforms, receipt e-mails), backup and deletion. Purposes: enabling the Customer to take payments, manage its catalogue, customers, staff, orders and reservations, and comply with its tax obligations.
4. Categories of data subjects and data#
| Data subjects | Data |
|---|---|
| The Customer's end customers | Name, telephone, e-mail, delivery address, purchase history, loyalty points, gift cards, digital receipts, online orders |
| Persons making reservations | Name, contact details, date and time, number of covers, comments |
| The Customer's staff | Identity, code and role, clock-ins, schedule, contracts, sales made and, in Belgium, the national register number (INSZ/NISS) required by the cash register system (FDM) |
| Back office users | Name, e-mail, role, login logs |
The service is not designed to process special categories of data (Art. 9 GDPR). The Customer shall refrain from recording such data in free-text fields (comments, notes); an allergy note entered at the request of an end customer is used only to prepare that customer's order.
5. Documented instructions#
The processor processes the data only on documented instructions from the Customer. The Terms, this agreement, the account configuration and the actions carried out by the Customer in the software constitute those instructions. If the processor considers that an instruction infringes the GDPR or another data protection rule, it shall immediately inform the Customer.
Where Union or Member State law requires the processor to carry out processing (for example a court order), it shall inform the Customer before the processing, unless the law prohibits it.
6. Confidentiality#
Persons authorised to process the data within the processor are subject to a contractual or statutory obligation of confidentiality and access the data only to the extent necessary for their duties (operations, support, security).
7. Security (Article 32 GDPR)#
The processor implements the technical and organisational measures described in the annex. It may change them, provided that it does not reduce the overall level of security.
8. Sub-processors#
The Customer gives general authorisation for the engagement of the sub-processors whose list is published on the Sub-processors page. Some of them are involved only if the Customer activates the corresponding module (delivery, payment, reservations, scheduling).
The processor shall inform the Customer of any addition or replacement of a sub-processor at least 30 days in advance, by e-mail or in the back office. The Customer may object within that period on reasonable grounds relating to data protection; failing agreement, it may terminate the service concerned without penalty.
The processor imposes on each sub-processor data protection obligations equivalent to those of this agreement and remains liable to the Customer for their performance. Any transfer outside the European Economic Area is governed by an adequacy decision (including the EU–US Data Privacy Framework) or by the European Commission's standard contractual clauses.
9. Assistance with data subjects' rights#
The software enables the Customer to respond itself to requests from data subjects: viewing, correcting, exporting and erasing a customer's or employee's record from the back office. Data whose retention is required by law (receipts, Z reports, fiscal journal) are retained, detached from the individual where possible.
If a data subject contacts the processor directly, the processor forwards the request to the Customer without delay and does not respond to it itself, unless instructed by the Customer. The processor assists the Customer, as far as possible, in carrying out a data protection impact assessment or in consulting the supervisory authority.
10. Personal data breach#
The processor shall notify the Customer of any personal data breach affecting it without undue delay and at the latest 48 hours after becoming aware of it, by e-mail to the account address. The notification describes, insofar as this information is available: the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact point. Missing information is provided as soon as it becomes known.
It is for the Customer, as controller, to notify the supervisory authority within 72 hours and, where applicable, to inform the data subjects; the processor provides it with the necessary assistance.
11. End of the agreement#
At the end of the agreement, the Customer may export its data from the back office. The processor then deletes them within 30 days, unless it is subject to a legal retention obligation; copies held in backups disappear at the end of their rotation, within 30 days at most. On request, it confirms the deletion in writing.
12. Audits#
The processor makes available to the Customer the information necessary to demonstrate compliance with this agreement (description of the measures, list of sub-processors, available reports). The Customer may have an audit carried out, at its own expense, by itself or by an independent auditor bound by confidentiality, no more than once a year except in the event of a proven breach, subject to 30 days' notice and without disrupting the operation of the service or accessing other customers' data.
13. Liability and governing law#
The liability of the parties is governed by Article 82 GDPR and by the terms and conditions. This agreement is subject to Belgian law; the Tribunal de l'entreprise du Hainaut, division de Tournai has jurisdiction.
Annex: technical and organisational measures#
Confidentiality and access control
- Authentication by hashed password; signed session tokens with limited lifetime; separate device tokens for each point-of-sale terminal;
- Roles and rights per user (owner, manager, employee); personal code for each employee at the point of sale;
- Segregation by merchant: each table is linked to the account and each request is filtered on the authenticated account; automated checks of this segregation;
- Administrative access restricted to authorised staff and logged; remote access to point-of-sale terminals only with the Customer's consent.
Encryption
- Encryption in transit: HTTPS mandatory, TLS 1.2 minimum;
- Encryption at rest using AES-256-GCM of sensitive data (national register number, integration keys and secrets) and of backups.
Integrity and traceability
- Log of sensitive operations and API calls (90 days), log of login attempts (30 days), limit on the number of attempts;
- Tamper-proof fiscal journal managed by the FDM (Belgium) or RT (Italy) module.
Availability and resilience
- Backup server (Oracle Cloud Infrastructure, Frankfurt (eu-frankfurt-1)) that receives a continuous copy of the data and takes over in the event of failure;
- Point-of-sale terminals able to operate offline, with a local database and resynchronisation;
- Encrypted backups, kept for 30 days at most, and a restoration procedure.
Organisation
- Minimisation: only the data necessary for the service are requested; truncation of IP addresses where the full address is not necessary;
- Defined retention periods and automatic purges (digital receipts, delivery orders, logs);
- Data breach management procedure and internal incident register;
- Regular security updates of servers and dependencies.