Data Processing Agreement (DPA)
This Data Processing Agreement ('the Agreement' or 'DPA') is concluded between [COMPANY NAME] in its capacity as data processor and each Business that has registered an account on the Plater platform, in its capacity as data controller. The Agreement governs the processing that [COMPANY NAME] carries out on behalf of the Business, in accordance with Art. 28(3) of Regulation (EU) 2016/679 ('GDPR').
01Parties, incorporation and precedence
Processor: [COMPANY NAME], registered in the Republic of Bulgaria, UIC: [_________], address: [registered seat and address] ('the Processor' or 'Plater'). Controller: the Business, identified by the details in its platform account ('the Controller' or 'the Business').
The Agreement forms an integral part of the Terms of Service and is incorporated into them by reference. On data-protection matters, the Agreement prevails over the Terms in case of conflict. The Agreement applies automatically to every active Business account as of the last-updated date shown at the top of this page.
The Agreement covers guest, customer and staff data processed on the Business's site. For Business-owner accounts, platform billing, support tickets and platform analytics, [COMPANY NAME] acts as an independent controller — the Privacy Policy applies to those, not this Agreement.
02Definitions
- 'Controller' — the party that determines the purposes and means of the processing of personal data; in this Agreement — the Business.
- 'Processor' — the party that processes personal data on behalf of the controller; in this Agreement — [COMPANY NAME].
- 'Personal data' — any information relating to an identified or identifiable natural person.
- 'Data subject' — the natural person to whom the personal data relates.
- 'Sub-processor' — a processor engaged by the Processor to carry out specific processing activities on behalf of the Controller.
Terms not defined here have the meaning given to them in the GDPR or, as applicable, in the Terms of Service.
03Subject matter, duration, nature and purpose of processing
- Subject matter: the processing of personal data necessary to provide the Service — hosting a digital menu, receiving orders via QR table sessions, pickup or delivery on the Business's subdomain, reservations, reviews, and staff accounts with 6-digit PIN codes. Plater does not process end-customer payments — payments happen at the restaurant.
- Duration: for as long as the Business account exists, plus the deletion window under Section 11.
- Nature: collection, storage, structuring, transmission, display and deletion of data within a hosted software service (SaaS).
- Purpose: solely the provision of the Service to the Business. The Processor does not process the data for its own purposes.
04Categories of data subjects and personal data
Categories of data subjects:
- Guests ordering via a QR table session, pickup or delivery.
- Customers with a registered account with the Business (optional).
- Staff of the Business (staff accounts).
Categories of personal data:
- Order data — contents, timestamp, type, notes.
- Contact details — name, email, phone.
- Delivery addresses and geocoordinates.
- Reservation data.
- Reviews and ratings.
- Staff names and PIN identifiers.
- QR sessions and short-lived device identifiers.
The Service is not intended for the processing of special categories of personal data (Art. 9 GDPR). The Controller undertakes not to submit such data through the platform.
05Controller's instructions
- The Processor processes personal data only on documented instructions from the Controller, including with regard to transfers to a third country or an international organisation. The Terms of Service, this Agreement and the settings configured by the Controller in the admin panel constitute the complete documented instructions.
- An exception applies only where EU or Bulgarian law requires otherwise; in that case the Processor informs the Controller before processing, unless that law prohibits it on important grounds of public interest.
- The Processor immediately informs the Controller if, in its opinion, an instruction infringes the GDPR or other data-protection provisions.
06Confidentiality
The Processor ensures that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. Access is granted strictly on a need-to-know basis, and individual customer data is accessed only with a documented reason.
07Technical and organisational measures (Art. 32)
The Processor implements appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including:
- Encryption in transit via HTTPS/TLS everywhere.
- Passwords are stored only as salted hashes using industry-standard algorithms.
- Hosting in an EU data centre with physical security.
- Role-based access control.
- Logical segregation of each business's data — one Business's data is never accessible to another.
- Automatic abuse protection — request limiting and temporary account locking after failed sign-ins.
- Employee access to customer data only with a documented reason.
- Security logs retained for 90 days.
08Sub-processors
The Controller grants a general written authorisation for the engagement of sub-processors. The Processor gives the Controller at least 14 days' prior notice of intended changes — the addition or replacement of a sub-processor — via email or an in-platform notice, and the Controller may object within a reasonable period. If a justified objection cannot be resolved, the Controller may terminate the Service in accordance with the Terms.
As of the last-updated date, the sub-processors cover the following service categories: hosting and storage, transactional email, on-demand machine translation of menus and — once activated — subscription billing. The authoritative, always-current list of sub-processors is maintained on the Sub-processors page.
The Processor imposes on each sub-processor on that list the same data-protection obligations as set out in this Agreement and remains fully liable to the Controller for the performance of the sub-processor's obligations.
For clarity: the provider of 'Sign in with Google' (only when it is used), the social network operator when a Facebook page is connected, and the provider of delivery-address geocoding are not sub-processors — they act as independent controllers or standalone recipients of data. Their names and details are on the Sub-processors page.
09Assistance with data-subject rights
Taking into account the nature of the processing, the Processor assists the Controller by appropriate technical and organisational measures in fulfilling its obligation to respond to requests to exercise the rights under Chapter III of the GDPR — access, rectification, erasure, restriction, portability and objection. Requests received directly from data subjects concerning data processed on behalf of the Business are forwarded to the Controller without undue delay. Data subjects may also use the request form.
10Breach notification and impact assessments
- Upon becoming aware of a personal data breach, the Processor notifies the Controller without undue delay, providing the information available under Art. 33(3) GDPR — the nature of the breach, the categories and approximate number of data subjects affected, the likely consequences, and the measures taken.
- The Processor assists the Controller in fulfilling its obligations under Art. 32–36 GDPR — security of processing, notification of the supervisory authority and of data subjects, data protection impact assessments (DPIAs) and prior consultations — taking into account the nature of the processing and the information available to it.
11Deletion or return of data
Upon termination of the Service the Processor, at the Controller's choice, deletes or returns all personal data processed on its behalf within 30 days, and deletes existing copies, unless EU or Bulgarian law requires their storage — orders and invoices are kept for 10 years under the Bulgarian Accountancy Act. Return is provided on request, in a structured, commonly used format.
During the term of the Agreement the following retention periods apply:
- Sign-in and session data — up to 30 days from last use.
- Inactive customer accounts — deleted after 24 months of inactivity.
- Orders and invoices — 10 years (Bulgarian accounting law).
- Support tickets — 24 months from closure.
- Security logs — 90 days.
12Audits and information availability
The Processor makes available to the Controller all information necessary to demonstrate compliance with the obligations under Art. 28 GDPR, and allows for and contributes to audits, including on-site inspections, conducted by the Controller or an auditor mandated by it. An audit takes place no more than once per calendar year, upon reasonable written notice, during business hours, at the Controller's cost, and in a manner that does not compromise the security of the Service or the confidentiality of other Businesses' data. Where possible, the request is satisfied first by providing up-to-date documentation. The once-per-calendar-year limit does not apply where the audit is prompted by a personal-data breach affecting the Controller's data or is required by a competent supervisory authority.
13International transfers
Processing takes place in the European Economic Area (EEA), with one exception — delivery-address geocoding via a provider in the United Kingdom (named on the Sub-processors page), transferred on the basis of the European Commission's UK adequacy decision (GDPR Art. 45). Any future transfer to a third country takes place only on documented instructions from the Controller and in compliance with Chapter V of the GDPR, with Standard Contractual Clauses (SCCs) available as a fallback for future sub-processors where needed.
14Liability, governing law and final provisions
- The parties' liability under this Agreement is governed by Art. 82 GDPR and by the 'Liability' section of the Terms of Service, save where mandatory data-protection provisions provide otherwise.
- The Agreement is governed by the laws of the Republic of Bulgaria. Disputes are resolved by the competent courts in Bulgaria.
- The competent supervisory authority is the Bulgarian Commission for Personal Data Protection (CPDP, cpdp.bg).
- The Agreement applies automatically to every active Business account as of the last-updated date. Material changes are announced in accordance with the Terms of Service.