Tavelo

Version DPA-2026-10-v1.1 · As of 19 October 2026

Data Processing Agreement (DPA)

This Data Processing Agreement (DPA, German: Auftragsverarbeitungsvertrag, AVV) governs how Tavelo processes guests' personal data on behalf of a restaurant. It forms part of the trial agreement and the Terms of Service (https://tavelo.ch/terms) and follows Art. 9 FADP and, where applicable, Art. 28 GDPR.

This English version is a convenience translation. The German version is legally controlling; in case of any conflict, the German version prevails.

1. Parties and roles

The controller is the restaurant using Tavelo. The processor is Luis Angel Romero Castillo, an individual trading under the name "Tavelo", Bremgartnerstrasse 118, 8953 Dietikon, Switzerland, support@tavelo.ch ("Tavelo").

This DPA does not cover data for which Tavelo itself is responsible: restaurant and staff accounts, billing restaurants, security and abuse prevention, support and legal obligations (see https://tavelo.ch/privacy).

2. Subject matter and duration

The subject matter is the provision of the Tavelo software under the trial agreement or the Terms. This DPA applies as long as Tavelo processes guest data for the restaurant, including the export and deletion period after the contract ends.

3. Nature and purpose of processing

Storing, displaying, transmitting and analysing data in order to route orders to kitchen and bar, manage tables and reservations, receive online orders (pickup and delivery), present them for acceptance and show the guest their status on a status page, send reservation emails, verify email addresses with one-time codes, run loyalty programmes and rewards, issue and update Apple and Google Wallet cards, deliver offers to guests who consented, provide analytics and — where enabled — translate menu texts and order notes and operate the AI reservation assistant.

4. Data subjects and categories of data

Data subjectsCategories of data
Guests orderingTable, items, options, quantities, prices, notes to the kitchen, timestamps, status, paid marking
Guests ordering online (pickup and delivery)Name, phone number, email address (optional), for delivery the address (street, postal code, city, notes), items, options, quantities, prices, delivery fee, notes, requested pickup or delivery time, status and status history, rejection reason, random access code of the status page
Guests reservingName, email address, phone number, party size, date and time, requests, language, status history, internal notes
Loyalty membersEmail address, first name, visits or points, rewards and voucher codes, linked paid orders, Wallet and device identifiers, rewards-page access key, one-time code requests (email, hashed code, timestamps)
Guests with marketing consentConsent status, time, source, version of the consent wording, withdrawals, campaign deliveries and their outcome
Users of the AI assistantTyped chat text (not stored by Tavelo)

Sensitive personal data is not intended. In free-text fields guests may mention e.g. allergies; the restaurant does not ask for health data through Tavelo.

5. Instructions

Tavelo processes guest data only on the restaurant's documented instructions. Instructions are this DPA, the Terms or the trial agreement, the restaurant's settings in the dashboard and its actions in Tavelo. If Tavelo considers an instruction to infringe data protection law, Tavelo informs the restaurant.

6. Confidentiality

Persons at Tavelo with access to guest data are bound to confidentiality.

7. Technical and organisational measures

Tavelo takes measures appropriate to the risk, currently in particular:

  • encrypted connections (HTTPS/TLS);
  • separation by restaurant and role, enforced in the database (row level security);
  • credentials of external services only on the server;
  • one-time codes only hashed, with expiry and attempt limits;
  • unguessable random codes for guest links;
  • least-privilege roles for staff;
  • browser security headers;
  • backups at the hosting provider and documented recovery procedures.

Tavelo may adapt measures as long as the level of protection is not reduced. No system is perfectly secure; Tavelo does not guarantee absolute security.

8. Subprocessors

The restaurant authorises the subprocessors listed at https://tavelo.ch/subprocessors.

Tavelo informs the restaurant by email at least 30 days before engaging or replacing a subprocessor. The restaurant may object on legitimate data protection grounds; if no solution is found, it may terminate the contract.

Tavelo contractually binds subprocessors to equivalent data protection and remains responsible for them towards the restaurant.

9. International transfers

Some subprocessors process data outside Switzerland and the EEA, in particular in the United States. Tavelo discloses data only to countries with adequate data protection or on the basis of appropriate safeguards, in particular the EU standard contractual clauses with the adaptations required for Switzerland or certification under the Swiss-U.S. Data Privacy Framework. Details per provider: https://tavelo.ch/subprocessors

10. Assistance with data subject requests

Tavelo reasonably assists the restaurant with requests for access, rectification, erasure, receipt, objection and withdrawal. Requests reaching Tavelo directly that concern the restaurant's guest data are forwarded to the restaurant without undue delay. Tavelo applies a withdrawal of marketing consent immediately; guests can also withdraw themselves on their rewards page.

11. Data security breaches

Tavelo notifies the restaurant of a data security breach affecting the restaurant's guest data as soon as possible after becoming aware of it, with the information available (nature of the breach, categories and approximate number concerned, likely consequences, measures taken), and assists the restaurant with its own notification duties (to the FDPIC "as soon as possible" under Art. 24 FADP; under Art. 33 GDPR within 72 hours to the supervisory authority, where applicable).

12. Return and deletion

After the contract ends, the restaurant may request an export of its guest data within 30 days. Tavelo then deletes or anonymises the restaurant's guest data unless a statutory retention obligation applies. Backups are overwritten in the hosting provider's backup cycle.

Tavelo currently performs export and deletion manually on request; there is not yet a self-service function for all data. Independently of this, one-time code requests are deleted automatically after 30 days.

13. Evidence and audits

Tavelo provides the restaurant with the information needed to demonstrate compliance with this DPA (e.g. this DPA, the subprocessor list and a description of the measures). On-site audits are possible with reasonable notice, at the restaurant's cost and at most once a year, unless there is a specific reason.

14. Term, termination and precedence

This DPA ends when the trial agreement or the contract under the Terms ends; the obligations regarding export, deletion and confidentiality continue. Liability follows the main contract. In case of conflict on data protection matters, this DPA prevails.

Swiss law applies; place of jurisdiction is Zurich, Switzerland, to the extent permitted by law. Where the GDPR applies mandatorily, its requirements prevail. The German version is controlling.