Data processing agreement

Under article 28 GDPR, version 3.0, 14 November 2026

Note: this data processing agreement applies when Joep processes personal data on behalf of the Customer, the controller. Joep is the processor within the meaning of article 4(8) GDPR. The agreement has a part per module, Phone and Ordering site: what is listed under a module only applies when the Customer’s package has that module, and what is listed under “Always” applies to both. The Customer enters into this agreement by accepting it in My Joep at sign-up, or at the first login after a new version. Joep records which account accepted which version at which moment (article 28(9) GDPR).
English: this is a translation of the Dutch agreement, the language of the contract. Where the two differ, the Dutch text applies.

Parties

  • BullNice B.V., Torenlaan 5B, 1402 AT Bussum, the Netherlands, Chamber of Commerce 84835850, VAT number NL863401259B01, trading as Joep (“Joep” or “Processor”), and
  • the business that uses Joep for its venue, as recorded in the account in My Joep (“Customer” or “Controller”).

Article 1: Subject and duration

1.1 Joep processes personal data on behalf of the Customer to deliver the service Joep, in the modules the Customer’s package has (together the “Service”):

  • Phone: a phone assistant that takes phone orders or reservations for the Customer’s venue, sends the Customer’s customer or guest a confirmation and answers questions;
  • Ordering site: an ordering site at an address of the Customer’s own (joep.ai/bestellen/yourvenue) where the Customer’s customers order and pay, get a confirmation and follow the status of their order.

1.2 This agreement applies for as long as the Customer uses the Service, and after that for as long as Joep still holds personal data of the Customer (article 11).

1.3 The terms and conditions of BullNice B.V. and the NLdigital Terms 2025 also apply. Where they conflict on the processing of personal data, this agreement prevails.

1.4 When the Customer adds a module, the processing and sub-processors of that module as set out in this agreement apply from that moment; no new acceptance is needed for that. When the Customer takes a module off, Joep stops the processing of that module; what happens to the data is set out in article 11.

Article 2: Nature and purpose of the processing

Joep processes personal data only for these purposes, and for nothing else. What is listed under a module only happens when the Customer’s package has that module.

Always

Part of the ServiceWhat Joep does for it
Orders on the receipt printerPrinting the order on the Customer’s receipt printer and showing it in the Joep app on the counter PC.
ConfirmationSending the Customer’s customer a WhatsApp message with the overview of their order.
Delivery areaChecking whether a delivery address lies within the Customer’s delivery area.
My JoepGiving the Customer insight into orders, reservations, callback requests and settings, and letting the Customer download their orders.

Module Phone

Part of the ServiceWhat Joep does for it
Answering the phoneHolding the conversation with the caller, on behalf of the Customer’s venue.
Orders (takeaway and delivery venues)Noting and pricing the order.
Reservations (restaurants)Noting and recording the reservation, and sending the guest a confirmation by email.
Payment linkWhere the Customer has set this up, a payment link in the confirmation.
Answering questionsAnswering questions about opening hours, menu, allergens and delivery based on what the Customer has set in My Joep.
Callback requests and transferringNoting a callback request and passing it on to the Customer, or transferring the caller to the number the Customer has set.

Module Ordering site

Part of the ServiceWhat Joep does for it
OrderingTaking the order with name, phone number and, for delivery, the address; calculating the price; starting the payment in the Customer’s Mollie account; and putting the order on the Customer’s receipt printer after the payment and the minute to cancel.
CancellingCancelling the order at the customer’s request within a minute of paying, and refunding the amount through Mollie.
StatusShowing the customer the state of their order on a status page with a secret address.
SecurityStopping robots and abuse with a check at checkout and with limits per IP address, phone number and venue.
OverviewsWorking out “Most ordered” and “Often ordered with this” from the Customer’s own orders, without showing personal data.

Joep does not use the personal data of callers, customers and guests for its own purposes, for marketing or to train models. Joep keeps counts per venue without personal data, such as the number of orders per channel, the revenue and the cost of messages, to run and invoice the Service.

Article 3: Data subjects and personal data

3.1 Data subjects: the callers, customers and guests of the Customer’s venue, visitors who check out an order on the Customer’s ordering site, and where applicable employees of the Customer who call Joep or place a trial order.

3.2 Personal data per module:

Module Phone

CategoryDataWhere it comes from
IdentificationName as the caller gives it; phone number of the callerThe call; the number comes with the call
OrderDishes, quantities, remarks, requested time, pickup or delivery, total amountThe call
DeliveryDelivery address and postcodeThe call
PaymentWhether a payment link was paid in advance, and the amount. No bank or card details; those stay with MollieMollie, through the Customer’s connection
ReservationDate, time, number of people, lunch, drinks or dinner, email address for the confirmation, particularsThe call
MessagesThe content of the WhatsApp messages and emails Joep sends on behalf of the CustomerJoep itself
CallThe speech during the call and a transcript of it, for as long as needed to hold the call, and as kept by the voice processor (annex 1)The call
Callback requestName, phone number, reasonThe call

Module Ordering site

CategoryDataWhere it comes from
IdentificationName as the customer fills it in; phone numberThe order form
DeliveryPostcode, house number, addition, street and townThe order form; street and town from the address lookup
OrderDishes, choices and extras, quantities, a remark, pickup or delivery, chosen time, discount code, packaging or own container, cutlery, language, total amountThe order form
PaymentIn advance through Mollie or at the counter; the state of the payment; when cancelled, the moment and the refund. No bank or card detailsMollie, through the Customer’s connection
Status addressA secret code in the address of the status pageJoep itself
MessagesThe content of the WhatsApp messages about the orderJoep itself
Technical dataIP address, browser, TLS fingerprint and the address of the site, for the robot check and the limitsThe customer’s browser

3.3 Special categories of personal data. A caller, customer or guest may mention allergies, dietary needs or a disability, on the phone or in the remark with an order on the ordering site. That is data concerning health (article 9 GDPR). Joep only processes it as part of the order or reservation, and never for anything else. The allergen filter on the ordering site works only in the customer’s browser: Joep does not receive which allergens a customer excludes. As controller, the Customer is responsible for being allowed to process this data.

3.4 What Joep does not process: bank or card details of callers and customers (they go straight to Mollie, into the Customer’s Mollie account), and data not needed for the order or reservation. On the ordering site Joep asks for no email address. What a customer has remembered with “Remember my details on this device” stays in their own browser and does not reach Joep.

3.5 Data of the Customer itself (account details, billing details, use of My Joep) Joep processes as controller. The privacy statement applies to that, not this agreement.

Article 4: Instructions of the Customer

4.1 Joep processes personal data only on documented instructions of the Customer. Instructions are: this agreement, the terms and conditions, and the settings the Customer makes in My Joep (such as opening hours, menu, delivery area, payment link or not, transferring, tone and language, and for the module Ordering site the settings of the ordering site: on or off, address, ways to pay, times, limits and additions to the standard texts).

4.2 If the Customer wants something else, they pass it on in writing through support@joep.ai. Joep tells the Customer if, in Joep’s view, an instruction conflicts with the GDPR or other legislation.

Article 5: Obligations of Joep

Joep:

  1. processes the personal data only in line with article 4, including where it concerns transfers to countries outside the EEA;
  2. makes sure that everyone at Joep with access to personal data is bound to confidentiality, by agreement or by law;
  3. takes the security measures of annex 2 and keeps them in line with the state of the art;
  4. engages sub-processors only in line with article 7;
  5. helps the Customer, as far as can reasonably be expected, with requests of data subjects (article 10);
  6. helps the Customer with its obligations around security, reporting data breaches and a data protection impact assessment (articles 32 to 36 GDPR), given the nature of the processing and the information available to Joep;
  7. deletes or returns in line with article 11;
  8. makes available to the Customer all information needed to show that article 28 GDPR is complied with, and cooperates with audits in line with article 12.

Article 6: Security

6.1 Joep takes appropriate technical and organisational measures to protect personal data against loss and unlawful processing. The measures at the time of this version are in annex 2.

6.2 Joep may adjust the measures as long as the level of protection does not go down. On request Joep provides the current list.

Article 7: Sub-processors

7.1 The Customer gives Joep general permission to engage the sub-processors of annex 1 for the modules of its package. Joep imposes on every sub-processor in writing the same obligations as in this agreement, in particular around security and instructions.

7.2 If Joep wants to add or replace a sub-processor, Joep reports it at least 30 days in advance by email to the account address of every Customer whose package has the module that sub-processor works for, and updates annex 1 on this page. A sub-processor that works for every module, Joep reports to every Customer. If the Customer objects with reasons within those 30 days, the parties look for a solution; if that fails, the Customer can cancel the Service as of the moment the change takes effect, at no cost.

7.3 Joep remains liable to the Customer for the acts of its sub-processors.

Article 8: Transfers outside the EEA

8.1 Joep stores the personal data of the Customer within the EEA (annex 1).

8.2 For parts of the Service, personal data is processed by sub-processors in the United States (annex 1). That transfer takes place under the EU-US Data Privacy Framework where the recipient is certified for it, and otherwise under the Standard Contractual Clauses of the European Commission (Decision (EU) 2021/914), with supplementary measures where needed.

Article 9: Data breaches

9.1 Joep reports a breach involving personal data of the Customer without undue delay and at the latest within 48 hours of discovery to the Customer’s account address, so the Customer can meet its own 72 hours towards the Dutch Data Protection Authority.

9.2 The report contains what is known at that moment: the nature of the breach, the categories and approximate number of data subjects and records, the likely consequences, the measures taken and proposed, and a contact person. What is not known yet follows as soon as it is known.

9.3 Joep does not report a breach to the supervisory authority or to data subjects itself, unless the Customer asks for it or the law obliges Joep to.

Article 10: Rights of data subjects

10.1 If Joep receives a request from a caller, customer or guest (access, correction, erasure, objection, portability), Joep forwards it to the Customer within 2 working days and does not answer it itself, other than to refer the data subject to the Customer.

10.2 At the Customer’s request, Joep deletes or provides the data of a data subject within 10 working days. The Customer can also look up orders, reservations and callback requests itself in My Joep and in the Joep app.

Article 11: Keeping, deleting and returning

11.1 During the Service, Joep keeps:

Always

DataRetention
Verification codes, sessions, password resetsMinutes to days; deleted after that.
Log filesContain no personal data of callers and customers (annex 2).

Module Phone

DataRetention
Orders, reservations and callback requestsBy default 90 days, deleted automatically after that. The Customer agrees another period through support@joep.ai.
Confirmations and payment linksFor as long as the order they belong to is kept.
Content of calls (speech, transcript)Joep stores no recordings or transcripts itself. The voice processor keeps the recording and the transcript for 30 days, only to deliver the Service and investigate faults; they are deleted after that. Joep sets that period on every agent and checks it with every change.
The number Joep transfers calls toFor as long as the Customer has the module Phone. If the Customer takes the phone off, Joep empties it after 90 days without the phone.

Module Ordering site

DataRetention
OrdersBy default 90 days, deleted automatically after that, as orders by phone are. The Customer agrees another period through support@joep.ai.
Status address, cancellation and refundFor as long as the order they belong to is kept.
Trial orders of the CustomerDeleted after a day.
An order that is not paidThe payment lapses after fifteen minutes. The order then never reaches the Customer, and goes with the retention of orders.
IP address for the limitsOnly in the memory of the server.
Logo and photos of the venueUntil the Customer removes them or the ordering site stops.
In the customer’s browserThe basket for two hours; with “Remember my details” name, number and address until the customer switches it off; the address of the status page of the last order for a day. This is not with Joep.

11.2 The Joep app on the Customer’s counter PC keeps a copy of the orders on that PC, encrypted, for the period the Customer sets in the app. That copy is on the Customer’s equipment and under the Customer’s control.

11.3 Taking the module Phone off is not an end of the Service. The data of the phone follows the periods above and the settings of the phone are kept, except the number Joep transferred calls to (article 11.1).

11.4 After the end of the Service, Joep deletes all personal data of the Customer within 30 days, unless a legal retention obligation prevents it. Within those 30 days the Customer can download its orders itself in My Joep, under Orders, as a CSV file, or request an export through support@joep.ai; Joep delivers it in a common file format.

Article 12: Information and audit

12.1 Joep answers reasonable questions of the Customer about compliance with this agreement and provides on request the description of the security measures and the current list of sub-processors.

12.2 If the Customer then has good reason to doubt compliance, it may, or an independent auditor it appoints who is bound to confidentiality may, carry out an audit at most once a year, announced at least 30 days in advance, during office hours, without disturbing the service to other customers. The costs are for the Customer, unless the audit shows a material shortcoming of Joep.

Article 13: Liability and fines

13.1 For liability, the provisions of the terms and conditions and the NLdigital Terms 2025 apply, also to damage and fines arising from this agreement.

13.2 Each party is responsible for the fines the supervisory authority imposes on it for its own shortcomings.

Article 14: Final provisions

14.1 Changes to this agreement are published as a new version on this page and put to the Customer for acceptance in My Joep. Until acceptance, the version the Customer last accepted applies.

14.2 Dutch law applies to this agreement. Disputes are submitted to the competent court in the district where BullNice B.V. is established.

14.3 Questions about this agreement: support@joep.ai. A signed copy or a custom agreement, for instance for a chain, is available on request.

Annex 1: Sub-processors

Joep engages sub-processors for the Service for the parts below, per module. The current list with name, place of establishment and basis for transfer is in My Joep under Account, Data processing agreement, for the modules of the Customer’s package, and is provided by email on request through support@joep.ai. An addition or replacement is reported at least 30 days in advance under article 7.2. Services that only process data of the Customer itself (billing, calendar, website analytics) are in the privacy statement.

ModulePart of the ServiceCategory of sub-processorWhich dataLocation and basis
AlwaysDatabase and servers of Joep, My Joep and the ordering sites, and the internal automation of BullNiceCloud hostingAll data of article 3 that Joep stores or passes on, also logos and photos of the ordering siteEU. No transfer.
AlwaysConfirmations and messages to the Customer’s customerWhatsApp Business Platform (Meta Platforms Ireland Ltd.)Phone number, content of the message (order, time, amount, payment link or status page)EU entity; processing partly in the United States. Standard Contractual Clauses of Meta.
AlwaysChecking whether a delivery address lies within the delivery area, only for a venue that delivers by radiusMap and geocoding serviceDelivery address, without name or phone numberUnited States. EU-US Data Privacy Framework.
AlwaysReading the menu the Customer uploadsProvider of language modelsThe Customer’s menu; normally contains no personal dataUnited States. EU-US Data Privacy Framework or Standard Contractual Clauses.
PhoneHolding the call, speech to text and text to speech, the call history (30 days), the phone numbers Joep answers onVoice technology, with the carrier it engagesSpeech, transcript, phone number of the caller, what the caller says in the callUnited States. EU-US Data Privacy Framework or Standard Contractual Clauses.
PhonePayment link and paymentMollie B.V., in the Customer’s own Mollie accountAmount and order number; Mollie processes the caller’s payment details itselfNetherlands. The Customer has its own agreement with Mollie for this.
Ordering sitePaying at checkout, and refunding when cancelledMollie B.V., in the Customer’s own Mollie accountAmount, order number and refund; Mollie processes the customer’s payment details itselfNetherlands. The Customer has its own agreement with Mollie for this.
Ordering siteRobot check at checkoutSecurity service against robots and abuseIP address, TLS fingerprint, browser and the address of the site; no name, number or orderUnited States. EU-US Data Privacy Framework.

Internal notices from Joep to the Customer and to BullNice (callback requests, faults) run through BullNice’s own automation on servers in the EU. For a callback request they contain the caller’s name and phone number, and for a failed WhatsApp confirmation the customer’s phone number, so the venue can still call.

Annex 2: Security measures

As in the code and the setup of Joep at the time of this version.

Encryption in transit

  • All connections to joep.ai, app.joep.ai, My Joep and the ordering sites run over TLS, with HSTS (two years, including subdomains).
  • The connection between the API and the database is encrypted and checks the certificate of the database provider.
  • The Joep app on the counter PC only talks to the API over TLS, and only to the address it was paired with.

Encryption at rest

  • Account passwords are stored as a scrypt hash; never readable.
  • Tokens of sessions, password resets and pairing codes are stored only as a SHA-256 hash.
  • Access tokens for the Customer’s Mollie connection and the secret keys of two-step verification are encrypted with AES-256; the key is not in the database.
  • On the counter PC the Joep app keeps orders and the pairing token encrypted with Windows DPAPI, bound to the Windows user.
  • Backups of the database stay within the EU.

Access

  • One customer account per venue. The admin environment of BullNice is only reachable for administrators, with two-step verification.
  • Every counter PC has a token of its own, which the Customer can revoke itself in My Joep; the number of devices per venue is limited.
  • The voice assistant can only call the API with a secret issued per environment, and only for the venue the call belongs to.
  • An order, reservation or callback request is only visible to the venue it was taken for; automated tests guard this.

On the ordering site

  • A robot check at checkout, and limits per IP address, phone number and venue.
  • Only the server calculates the amounts, and an order has a maximum.
  • An order only reaches the Customer once Mollie has confirmed the payment and the minute to cancel is over.
  • The status page is at a secret address, shows no phone number and is not taken up by search engines.
  • A strict Content Security Policy.

Data minimisation and logging

  • Joep only asks what is needed for the order or reservation.
  • Log files contain no personal data of callers and customers: phone numbers and addresses are not logged, error messages are stripped of personal data, and orders are referred to in logs only by their number.
  • Orders and callback requests are deleted automatically after 90 days, or the period agreed with the Customer; recordings and transcripts after 30 days at the voice processor.

Separation and organisation

  • Production and staging are separate environments with their own databases, keys and tools; test data does not go into production and vice versa.
  • Payment details of callers and customers never pass through Joep; Mollie processes them in the Customer’s account.
  • Changes are tested before they go to production; the code is in a version control system with history. Sub-processors are assessed before they are engaged.

Annex 3: Change history

VersionDateChange
1.01 January 2026First version.
2.029 September 2026Full revision: data subjects and data set out per part of the Service; health data; confidentiality; help with rights of data subjects; return besides deletion; audit; sub-processors per service with location and basis; security annex; report of a data breach within 48 hours; recording of the acceptance per version in My Joep.
2.126 October 2026Annex 1 names sub-processors per category; the list with names is in My Joep and provided on request. The retention of recordings and transcripts at the voice processor is set at 30 days. Orders: by default 90 days, another period on request instead of a setting in My Joep.
3.014 November 2026A part per module, Phone and Ordering site: the ordering site as part of the Service, with its purposes, data subjects, data and retention; a robot check as sub-processor; Mollie also for payments and refunds on the ordering site; a new sub-processor is reported to the Customers whose module uses it; adding a module needs no new acceptance; the number Joep transfers to, after 90 days without the phone; the download of orders in the 30 days after the end; security of the ordering site.