Privacy policy
Sirvely is a QR ordering system for restaurants, bars and cafés. On this page we explain, in language you can understand, which data we process, why we process them, who else sees them and what you can ask of us at any time.
Last updated: 21 October 2026
1. Data controller
Sirvely is a trading name of a Dutch company. That company is the controller of the data described in this policy and decides, within the limits explained here, what they are used for.
| Trading name | Sirvely |
|---|---|
| Chamber of Commerce (KvK) | 86964178 |
| VAT number | NL004333820B72 |
| Registered address | Zandzuigerstraat 70, 1333 HD Almere, the Netherlands |
| info@sirvely.com | |
| Telephone | +31 85 060 4404 |
| Information site | https://www.sirvely.com |
| The service | https://app.sirvely.com |
To exercise any of the rights explained below, or simply to ask us something about this policy, email info@sirvely.com or call us on +31 85 060 4404. We have not appointed a data protection officer, so everything to do with your data goes through that email address. The company's identification details are also in the legal notice.
2. Who this policy is for
Around Sirvely there are four groups of people, and they are not all in the same position, so it helps to tell them apart from the start.
You, as the owners of the restaurant, are our customer. About your business and the person who signs the set-up we process the data needed to provide the service to you and to charge for it and, before that, the data of the registration request with which you ask us to sign you up. For that part we are the data controller.
Your staff use the application to work. You enter their details yourselves, and they are processed so that each person can sign in with their PIN, see what concerns them and clock in and out and, if you use those screens, so that you can plan their shifts and prepare their payroll. We explain that in section 4.
The customers who sit at your tables scan the QR code and order from their own phone, without installing any app and without registering. We do not ask them for a name, a phone number or anything else in order to place an order; only if your venue has set a radius for the QR codes does their browser ask for their location. We only have their name, email and phone number if they book a table from the menu or if your staff enter a booking for them; we explain that in section 5.
Partners are people or companies who bring us restaurants and earn a commission for it. They work in their own dashboard, at partners.sirvely.com. For their data we are the data controller; we explain that in section 6.
For the data of your staff and of the customers at your tables, you are the data controller: it is your business that decides which menu is published, which employees exist and what is done with the orders. We act as a data processor on your behalf, we process those data solely to provide the service to you and following your instructions, and we do not use them for any purpose of our own. It is you who must inform your team and your customers that you work with a digital ordering system. The obligations we take on as a processor, which article 28 of the General Data Protection Regulation requires, are set out in section 11 of the terms and conditions, which form part of the contract between your restaurant and us.
3. Data about the restaurant and its owner
About the business we keep the trading name, the address, the phone number, the email address, the country where the company is established, which is Spain to begin with, and, if you fill them in under Ajustes, the legal name of the company and its tax identification number: for Spain the NIF, NIE or CIF, and for another member state of the European Union its VAT number. For a company established in Spain we also keep its tax territory: the peninsula and the Balearic Islands, the Canary Islands, Ceuta or Melilla. The legal name and the tax identification number appear as the employer on the payslips and, together with the address, the country and that territory, as the customer on the invoice for the subscription when we issue you one. About the owner we keep their name and their email address, which is also the one used to sign in to the panel, the password as an irreversible hash and when they last signed in. We keep the same for every email sign-in that our admins create for your restaurant, including those with the staff role rather than the owner role. To protect each account we also count failed password attempts and, after too many, lock it for a while.
The monthly fee is paid with a credit card that you link yourselves from the panel. That link is processed through Pay.nl and leaves a recurring payment authorisation on the card. We do not send Pay.nl your name or your email address: we only pass on the amount, a description with the month, such as Sirvely 2026-10, our own internal references and the addresses of the service. Of the card we keep only the brand, the last four digits, the expiry date and the reference of the authorisation, encrypted, and of every charge its month, its amount, its reference at Pay.nl and whether it went through. You can check the payments made and the state of the subscription at any time in the panel, at https://app.sirvely.com. If you cancel the subscription, we switch the card off and there are no further charges; the reference of the authorisation stays stored with us, switched off.
When we issue invoices for the subscription, before every charge we decide how VAT applies to it, from your country, your tax territory and your VAT number, and we make the same calculation when the panel or our admin panel shows what the next charge comes to. If your company is established in a member state of the European Union other than the Netherlands, within its VAT area, and you have given us a VAT number in the format of that country, we check that number in VIES, the European Commission's service for checking VAT numbers, as section 9 explains. VIES answers whether the number is valid, with a consultation number and, if your member state shares them, with the name and the address registered for that number. For every charge we store that decision: the price excluding VAT, the VAT and its rate, how it applies, the country whose VAT it is, your country, your tax territory when it puts your company outside the VAT area of the European Union (the Canary Islands, Ceuta or Melilla), your VAT number when VIES has confirmed it or your company is in the Netherlands, the VIES check with its date, its consultation number and the name and the address it returned, and whether the charge went ahead with VAT because VIES had not answered for more than three days. While VIES does not answer about your number, we note since when and what error it gave last, and that note disappears as soon as VIES gives an answer.
The invoice is issued from that decision. It carries your legal name, your address, your country and, for the Canary Islands, Ceuta or Melilla, that territory, your tax identification number and, under the reverse charge, your full VAT number, as they are at that moment, and we keep the VIES check with it. We keep the invoice exactly as it was issued. If an invoice cannot be issued correctly yet, for example because the legal name or the address is missing, we keep the payment with the reason, and the invoice waits until the reason is gone and we try to issue it again from our admin panel. Every change of your tax territory, and every new address of a company in Spain whose postal code points to another territory than before, leaves a line in the log of our admin panel, with the old and the new territory, the country, the old and the new postal code with the territory each points to, and the name of whoever made the change. Those details are processed for invoicing and for our accounts, and for nothing else. As long as we do not issue invoices for the subscription, we do not ask VIES and store none of those decisions. How VAT applies in each case, and the other financial terms, are in the terms and conditions.
If a partner brought you to Sirvely, that partner sees in their dashboard the name of your restaurant, since when you have been signed up, whether you are a customer yet and since when, or that we closed the referral because you did not become a customer after all, whether you pay monthly or yearly and the discount you had on the set-up fee. For every payment of the fee that earns them a commission they also see the month, the amount of that payment, the percentage, what they earn from it and whether and when it has been paid to them, and in total what they have earned through you and how much of it has been paid to them. They do not see your menu, your orders, your team or any data about your customers.
Before you are a customer, you can ask us to sign you up through the registration form at https://app.sirvely.com/register. That form creates no account. It asks for your email address and the name of your restaurant and, if you want to give them, your name, a phone number and the address of the restaurant in its parts: the street and number, the postcode, the city and the country of the restaurant. With them we keep the language of the form and, if you came through a partner's link, the code of that link. We store the request, our server sends a notification with all of those details, and the name of the partner whose code it is, to our own mailbox, and you receive a confirmation by email in the language of the form, which names your restaurant, your name if you gave it and your email address. We read the request in the admin panel, get in touch with you and can record with it what state it is in, such as called or declined, and a note, for example when we called you. When we sign you up, we link the request to your restaurant. Every change to the state or to the note goes into the log of the admin panel, the note included. The partner whose link you came through does not see the request.
We process those data to take the steps you ask of us before there is a contract, and that is also the legal basis: steps taken at your request prior to entering into a contract. Nothing deletes a request automatically today, and the admin panel has no way to delete one either: it stays, whatever its state. If you ask us to delete it, we delete it, together with the notes the log of the admin panel keeps about it, without undue delay and at the latest within one month, as the General Data Protection Regulation requires.
We can email the person responsible for your restaurant about our service, for example about a new feature. Such a mailing goes to the email address of the owner's login of the restaurant. For every mailing we store who it went to: the email address, the name of the restaurant, the first name we greet the person with, the language of the greeting, and whether our mail provider accepted the email, and when, or could not take it, with the error when it failed. Whether the email then reached the inbox is not something we learn. With it we keep the message itself and which of our admins sent it. Every mailing has a link at the bottom with which the person unsubscribes, and a mail program can offer the same with one click. From then on we send no more mailings to that address, not even when it is also the address of another restaurant or of a partner account, and we keep the address and the moment it unsubscribed, so that it stays that way. If the restaurant has another owner's login with an address of its own, its mailings go to that address from then on. Emails about the account itself, such as a new password or our reply to a support ticket, still reach it.
If you contact our support about a problem, we record it as a support ticket for your restaurant, with its subject, its priority and its status. We keep the whole conversation: every message, when it was written and the name of whoever wrote it, on your side or on ours, and for a message written while signed in to your restaurant also the login it was written with. When one of our admins logs a ticket for you, for example after a phone call, the first message carries the name of the person responsible for your restaurant, or the name of the restaurant when it has no active owner login, and we also store which admin logged it. Our replies are also sent by email to the email address of the owner's login of the restaurant; an answer to that email reaches our contact inbox.
4. Staff data
For each person on your team we keep their name, their role, the permissions you have given them, the venue they work at, whether they are active, when they last signed in and, if you or they add one, a photo. Every time someone signs in with their PIN, the IP address and the details of the browser are kept with that session until it expires, as with every sign-in. The photo is reduced to a small square and stored as a file on our server's disk. Everyone signed in to your restaurant sees it, because it appears next to the person's name throughout the application. When it is replaced or removed the file is deleted, and deactivating a person does not remove it. Deleting a person does not delete their photo file yet, so remove the photo first or ask us to delete it.
Those data exist because without them the work on the floor cannot be shared out and nobody would know who served which table. That is also why the application records the person's name with what they do in it: which orders they served or prepared, which tables they opened, which payments they confirmed, what they did at the till and in the stock, and every step in the log of an order. That record stays when the person leaves, because it is part of the history of your orders and your till.
For the record of hours we keep the shifts you plan, with the day, the venue, the times, the station, a note and the planned breaks; the clock-in and clock-out times each person records and the breaks they take; and the corrections made afterwards on the timesheet, with the corrected times and breaks, the reason if one was given, the name of whoever made the correction and when. A correction is stored next to the original clock-in and does not replace it; only a clock-in that was left open gets the corrected time as its end. Each person sees their own shifts and their own clock-ins in the application. The schedule and the timesheet of the whole team, with their corrections, are seen by the owner and by whoever has the staff permission, which with a PIN by default only owners and managers have, and which every email sign-in of your restaurant has once the password of that account has been entered. On the floor everyone sees which colleagues are on shift, and whoever has the orders permission, which by default owners, managers and floor staff have, also sees how long each of them has worked that day, their breaks and when they clocked out.
If you use the payroll in Administración, more is kept. For each version of a contract: the national identity number and the Social Security number, if you enter them, the venue where the person is registered with Social Security, the type of contract, its start and end dates, the contribution group and the professional group, the weekly hours, the base salary and the complements, the extra payments and the variable pay you expect over the year. With it go the data of the modelo 145 for the suggested IRPF withholding: the family situation, the year of birth, disability and reduced mobility, geographic mobility, the children with their year of birth or adoption and any disability, the ascendants with their year of birth and any disability, any compensatory pension or child support paid, and whether a reduction for a housing loan or for the region applies. For each month we keep what is confirmed before approval, such as the split of the hours, overtime, manual lines, advances and other deductions, and the cash tips of the venue, which together with the card tips are shared out among the team by the minutes each person worked. When the month is approved we keep the payslips, with the gross, the net, every line, the hours of each day and each person's share of the tips, together with who approved the month and when and, if the owner reopens it, who did so, when and why.
Disability and reduced mobility are health data. The API only returns them on the contract screen of the payroll and never puts them on a payslip, in its PDF or in an export; each approved payslip does keep an internal copy of the tax data of the contract, these included, so that the withholding of the following months can be calculated against it. The payroll, the payslips as PDF and the export for your payroll adviser, which carries the name, the identity and Social Security numbers, the family situation, the number of children, the hours and the amounts of each person, are seen only by the owner and by whoever has the payroll permission, which with a PIN by default only owners and managers have, and which every email sign-in of your restaurant has once the password of that account has been entered. That screen is locked on every device: it asks for the PIN again or, on the email sign-in, for the password of the account, and locks again after fifteen minutes without use. Each person sees their own approved payslips on their phone.
These data serve to plan the work, to keep the record of hours and to prepare the payroll, which Spanish labour law requires of you as the employer. The payroll in Sirvely is an estimate for your payroll adviser: we file nothing with Social Security or the tax office, and we send no payslip by email. As with the rest of your staff's data, you are the controller and we process them on your behalf. None of it is deleted automatically. Someone with clock-ins, corrections, a contract or payslips cannot be deleted, only deactivated, so that their history stays; someone who only has planned shifts can be deleted, and those shifts go with them. These data are kept while your restaurant's account exists, it is you who decide what is deleted, and when the relationship ends they are deleted at your request, as section 10 explains.
About the PIN we want to be clear, because it affects your team. The PIN with which each person signs in on the tablet is stored encrypted and not as an irreversible hash, and this is deliberate: the manager must be able to show the PIN again to someone who has forgotten it, and that would not be possible with a hash. It means that the PIN can be read again inside the system by anyone with permission to do so. That is why we ask that nobody on your team uses as a PIN a number they also use for their bank, their phone or anything else in their private life. To protect the PIN screen we also count wrong PINs, close it for a while after too many, and keep when the last lock began, so that you can see on the staff screen that someone was trying codes. Each wrong PIN, with the IP address it came from, and each time a PIN is shown again, with who showed it, is written to our server's technical log.
5. Data about the restaurant's customers
A customer can order without giving us any details: there is no registration, no account and no form with their name. Even so, a few things arise from using the menu that you should know about.
The first is a device identifier. When someone opens the menu, their browser stores a random code that says nothing about the person and that lets you see how many phones are ordering at the same table and who ordered what within that table. On its own, that code is not linked to any name, any phone number or any account. But when a booking is seated at the table, the visit at that table is linked to the booking, and with it the codes of the phones ordering in that visit are tied to the name, email and phone number of the person who booked.
The second is the note the customer can write next to an item. It is a free-text field, meant for things like 'no onion' or 'rare', and whatever is written there reaches the kitchen and is stored with the order. There is no need to write health data or any personal data in that note, and we recommend that your staff do not ask for them there either: if a customer writes down an allergy, that text is stored like the rest of the order and is seen by anyone with access to the order ticket.
The third is the location, and it only appears if your venue has set a radius for the QR codes, so that ordering only works from inside the venue. The menu does not ask for it in advance: the first request goes without a location, and only when our server answers that the venue has a radius does the browser ask the customer for permission to share their location. If they give it, their phone sends its GPS position and the accuracy of that reading in the x-position header with the requests for the menu, the orders, the bill, paying online, calling the waiter, entering the booking code and sending the receipt. The page keeps the last reading for one minute at most, only in the memory of that tab. Our server uses the position to calculate the distance to the venue and then forgets it: the position is not stored in the database and is not written to the server's technical log, and neither is the distance. If the customer does not give permission, or is outside the radius, they cannot order; a phone that already belongs to the open visit at that table can still see the menu and the bill.
The fourth is the email address a receipt is sent to. It appears when the customer themselves asks at the table for the receipt to be sent to them: that address is used solely to send that particular receipt, is not stored in the database, is never used to write to them again and is not shared with you or with anyone. For each visit we only record how many receipts have been sent that way, with a maximum of three, so that nobody can use that function to send email to third parties. In addition, you can send the receipt of an earlier visit, as a PDF, to an address you enter, from the history in Administración; it is meant, for example, for the customer who asks for it the next day. That needs the subscription permission: with a PIN, by default only the owner role has it, unless you give it to someone else, and every email sign-in of your restaurant has it, including one with the staff role, once the password of that account has been entered. That sending has no maximum, and the address is not stored either: it is only used for that email.
And there is the booking, the only situation in which we have a customer's name. It arrives by two routes. Anyone looking at your menu through the shareable link, without sitting at a table, can book a table from there: they enter their name, email address and phone number, the day, the time and how many people they are and, if they wish, a remark. When they send it, they receive by email, in the language they booked in, the notice that we have received their request or, if the venue confirms bookings automatically and a table is free, the confirmation straight away. The other route is your staff: whoever has the bookings permission can enter, from the panel, the booking of a customer who calls or walks in, with their name, email and phone number. That booking is confirmed at once and the customer receives the confirmation by email, in Spanish. Either way the customer receives an email when the booking is confirmed, with the code for their table, and another if you cancel it; setting a booking back to new, marking it as a no-show or undoing a no-show sends no email. Those details are stored with the booking so that you can see it in the panel. They are your restaurant's data and we process them on your behalf, like the rest.
Paying online is optional. From the panel you can link your own Mollie or SumUp account and choose, table by table, whether the customer can pay online from the menu. Without that link nothing changes: payment is taken at the table, with your card terminal or in cash. This option is still being rolled out, so you may not see it in your account yet.
If you switch it on, the payment takes place on that provider's page and the money goes directly to your account with them. We do not see the customer's card details and we do not receive the money. To be able to start the payment on your behalf we keep the key of your account with the provider, encrypted, together with the name of that account, its identifier at the provider and whether it is in test mode. For each payment we keep the amount, the tip, the payment's reference at the provider, whether it went through or not, the table, the random identifier of the phone that paid and, when the order is paid before it goes to the kitchen, what was ordered, with its notes. The provider receives the amount, our reference and a description with the name of your restaurant and of the table. In that relationship Mollie or SumUp is your provider, not ours, and it is their terms and their privacy policy that apply to the customer.
6. Partner data
A partner is a person or a company who brings us restaurants and earns a commission for it. One of our admins signs them up, and from then on they work in their own dashboard, at partners.sirvely.com. For the data of partners we are the data controller, and we process them to give the partner access to their dashboard, to show them their visits and their restaurants and to calculate and pay their commission. The legal basis is the performance of the partnership agreement we have with them, and what we pay them also goes into our accounts, which we keep under a legal obligation.
About the account we keep the name, the email address, which is also the one they sign in with, the phone number if they gave it to us, the password as an irreversible hash, the code of their link, the language of their dashboard, the country where they bring in restaurants, the commission agreement they have with us, which of our admins signed them up and when they last signed in. To protect the account we also keep failed password attempts and, after too many attempts, a temporary lock. When we sign them up, and whenever we reset their password, we send them a temporary password by email, which they have to change before they can use their dashboard.
So that we can pay them, the partner fills in their business and bank details in their dashboard themselves: the business name, the registration number, such as that of the Dutch Chamber of Commerce or the NIF, the VAT number, the address, the account holder, the IBAN and the BIC. Our admins read them to make the transfer, and the partner can correct them themselves at any time; when they change the bank account, we send them an email that shows only its last four characters. With each restaurant they brought in we keep the link between the two, its status, the discount on the set-up fee, since when the restaurant is a customer and which admin made the link. For every payment of that restaurant's fee that earns them a commission we keep a line with the month, the amount of the payment, the percentage or the fixed amount, what they are owed and whether, when and by whom it has been paid to them.
Every time someone arrives at this website through a partner's link, we keep only the moment of that visit, so that the partner can see how many visits reach them. We do not keep the IP address or the browser of the visitor, nor anything that would tell who they are.
When a partner signs in to their dashboard, our API writes the jv_partner cookie and keeps with that session the IP address and the details of the browser, as with every sign-in. The session lasts seven days by default. In their browser the dashboard also keeps the key sirvely.partner.taal with the language of the dashboard, which is only a copy of the choice their account keeps. If the partner opens the demo of the restaurant panel from their dashboard, to show it to someone, they get a session that lasts four hours in the demo restaurant that we choose; in that session they can look at everything and change nothing, and it also keeps their IP address and the details of their browser. All of this is set out in detail on the cookies page.
We can also email partners, affiliates included, about our service or about the partnership, at the email address of their account and in the language of their dashboard. For every such mailing we keep the same as for a restaurant, as we explain in section 3: the email address, the partner's name, the first name we greet them with, the language of the greeting, and whether our mail provider accepted the email, and when, or could not take it, with the error when it failed. Every mailing has a link at the bottom with which the partner unsubscribes; from then on we send that address no more mailings, and we keep the address and the moment they unsubscribed.
A partner's data are not deleted automatically. They are kept for as long as the partnership lasts. An admin can block the account, after which the partner can no longer sign in, but their data remain stored, and no screen deletes a partner. When the partnership ends and the partner asks us to delete their data, we delete them without undue delay and at the latest within one month, as the General Data Protection Regulation requires, except the commission lines, the payments we made to them and the business and bank details stored for them at that moment, with their current IBAN: those are part of our accounts, and article 52 of the Dutch Algemene wet inzake rijksbelastingen obliges the company to keep its accounts for seven years. Earlier IBANs are not kept: when the partner changes their account, the new one replaces the old one, and neither the commission lines nor the payments keep a copy of the account they were transferred to. Expired sessions are deleted on their own, as we explain in section 10. A partner exercises their rights directly with us, as explained in section 11.
7. Technical data
Every time someone signs in, the IP address they signed in from and the details of the browser they use are stored alongside that session. They serve to spot an unusual sign-in and to be able to close a particular session, and they disappear when the session expires or is closed. The IP address is also used to limit the number of requests and slow down attempts at abuse. Those counts live only in the server's memory and are not written to the database, and they have no fixed deletion period: they disappear when the server restarts or when other addresses take their place. The only limit that counts by address in the database is the one on how many demos of this website one address holds at the same time: it counts with the address that each copy of the demo keeps, as explained below, and that address is deleted with the copy. Wrong passwords and wrong PINs are counted with the account or the restaurant, not with the address.
In addition, our server writes every request it receives to its technical log, with the method, the domain and path requested, the IP address of whoever makes it, the result and how long it took. Of the path it writes only the part before the question mark, so not what someone searched for, such as the name of a customer in the search of the panel. That log does not record the cookies or any other header of the request, nor the location header. Some lines about an event also carry the internal identifiers of the restaurant and of the user or staff member concerned, such as a wrong password on the management screens or a PIN that is shown again or replaced, and the lines about a wrong PIN and about the PIN screen being closed after too many also carry the IP address it came from. The log is kept on the server itself, as the log of the container our server runs in. It is rotated by size, in at most three files of 10 MB, so the oldest lines are overwritten as new ones come in, and every update of our server replaces that container and, with it, its log. We have not set a period in days for it.
In the admin panel a log of important actions is kept, such as creating a user, resetting a password or entering a restaurant's panel, with the name of the admin who did it. When a user is created, when the password of a restaurant's user is reset and when we enter a restaurant's panel, that log records the email address of the person concerned, and when details of a restaurant or of a partner are changed, or a note is written on a registration request or a message from the contact form, it records what was changed or written. It is what lets us reconstruct afterwards who did what, and nothing deletes it automatically.
This information website, https://www.sirvely.com, sets no cookies by itself, neither its own nor third-party ones, does not measure visits, carries no advertising pixel and loads no fonts, videos or maps from outside. In your browser it stores only that you have read the information notice in the footer, the language you chose, the language of the demo if you started one, if you came through a partner's link their code and, if a demo cannot start, for a moment in that tab, the reason why. Only three things reach our API from this website: that code, once, to count the visit, what you send with the contact form, which the next paragraph explains, and a press on View the demo, which makes your own copy of the demo restaurant. So that nobody can take every demo at once, that copy keeps the IP address it was started from (of an IPv6 address only the network part), and its session, that of the jv_tenant cookie our API writes, the full IP address and the details of the browser. If you also sign in on the demo's PIN screen with the PIN it shows you, our API writes the jv_staff cookie as well, for twelve hours, and that session likewise keeps the full IP address and the details of the browser. All of it is deleted with the copy. The demo lasts two hours, or less if half an hour passes without anyone using it or if you sign out of its panel. Our server looks for expired demos every ten minutes, so an expired demo can take up to about ten minutes longer to disappear. If the copy is deleted early because half an hour passed without use, the jv_tenant cookie can stay in your browser until the two hours are up, and the jv_staff cookie can stay for up to twelve hours in any case, but once the copy has been deleted neither of them leads anywhere. The sessions that do exist are those of the application, and they are strictly necessary to keep you signed in. This is explained in detail on the cookies page.
If you write to us with the contact form on this website, we keep what you fill in: your name, your email address, the name of your restaurant and your phone number if you give them, your message, the language of the page and, if you came through a partner's link, their code. We use it only to answer you and to follow up your question or the demo you ask for. You get a short confirmation by email, at most one a day, that does not repeat your message. We keep the message for as long as we need it for that follow-up. Nothing deletes it automatically and the admin panel has no way to delete it: if you ask us to delete it, we delete it, together with the notes the log of the admin panel keeps about it, without undue delay and at the latest within one month, as the General Data Protection Regulation requires.
8. Purposes and legal basis
We do not process any data 'just in case'. Each purpose has its legal basis, and this is the full list.
| Purpose | Legal basis |
|---|---|
| Giving you access to the panel, publishing your menu, receiving the orders from the tables and letting you know that a table is asking for the bill | The performance of the contract we have with your restaurant |
| Building and maintaining the menu, including reading a photo of your paper menu, translating the names of the items and making their photos | The performance of the contract we have with your restaurant |
| Storing a registration request, letting us know, confirming it to you by email and getting in touch to sign you up | Steps taken at your request before there is a contract with your restaurant |
| Charging the monthly fee to the card you have linked | The performance of the contract we have with your restaurant |
| Deciding how VAT applies to every charge of the subscription, checking your VAT number in VIES and keeping that check with the charge and with the invoice | The performance of the contract we have with your restaurant and the legal obligation to invoice and to keep our records |
| Issuing invoices and keeping the accounts, including the commissions we pay to partners | A legal obligation that rests on us |
| Keeping you signed in, limiting the number of requests and slowing down attempts at abuse | Our legitimate interest in keeping the service running and preventing it from being misused |
| Writing every request to the server, with the IP address, to its technical log | Our legitimate interest in being able to trace a fault or a misuse of the service |
| Showing in the panel, in the copy of the demo as well, the preview of the table cards with fonts from Google Fonts and the map of the reach of the QR codes with images from OpenStreetMap, for which the browser sends its IP address to Google and to the OpenStreetMap Foundation | Our legitimate interest in showing the cards in the fonts they are printed in and a map of the reach of the QR codes |
| Recording in the admin panel who does what | Our legitimate interest in being able to reconstruct a change and respond to an incident |
| Emailing the person responsible for your restaurant, and our partners, about our service, keeping who each mailing went to and whether it was accepted, and remembering who unsubscribed | Our legitimate interest in keeping our customers and partners informed about the service they use; anyone can object to it at any time with the unsubscribe link in every mailing |
| Recording a support ticket for your restaurant, keeping its conversation and emailing our replies to the owner's login | The performance of the contract we have with your restaurant |
| Sending the receipt to the address the customer enters at the table or that you enter from the history | On your behalf and following your instructions: the receipt is your restaurant's, and the address is only used to send it |
| Checking that the customer's phone is inside the radius of the QR codes, if your venue has set one | On your behalf and following your instructions: it is you who decide to set the radius, and the browser asks the customer for permission before sending their location |
| Processing the data of your staff: their photo, their shifts, their clock-ins, breaks and corrections and, if you use it, their payroll | On your behalf and following your instructions, since it is you who determine the purpose and the legal basis for those data |
| Storing a customer's booking, whether they make it from the menu or your staff enter it, and sending them by email the notice of receipt, the confirmation or the cancellation | On your behalf and following your instructions: the booking is with your restaurant |
| Starting a customer's online payment in your Mollie or SumUp account, if you have switched that option on | On your behalf and following your instructions: the payment is to your restaurant |
| Giving a partner access to their dashboard, counting their visits and their restaurants and calculating and paying their commission | The performance of the partnership agreement we have with that partner |
| Showing a partner the restaurants they brought in, what state they are in and what commission they earn them | Our legitimate interest in letting the partner check what we pay them |
| Making your copy of the demo when you press View the demo and limiting how many demos one address opens | Our legitimate interest in showing the service to whoever asks for it and in having demos for everyone |
| Answering a message from the contact form on this website and preparing the demo you ask for | The steps you ask us to take before a possible contract, and our legitimate interest in answering whoever writes to us |
9. Who else processes these data
To provide the service we rely on a small number of suppliers who act as processors, that is, they process the data on our behalf, only for what is stated here and without being able to use them for anything of their own. They are all in this table. We do not sell data, we do not pass them to third parties for advertising purposes and there is no other company watching what happens at your tables.
| Supplier | What for |
|---|---|
| Resend | Sending all the service's email, including the receipt a customer asks for at the table or that you send from the history, the emails about a booking, a partner's welcome email, the email to a partner when their bank account changes, the notification and the confirmation of a registration request or of a message from the contact form, and the emails with a sign-in code or a password |
| Hostinger International Ltd | The server the service runs on, in Frankfurt am Main (Germany), with the database, the files, among them the photos of the menu and of the paper menu, the logo and the photos of the staff, and the technical log of the requests. We manage the server ourselves with Coolify, which runs on that same server |
Resend is a company in the United States, so that processing involves a transfer of data outside the European Economic Area. We have not signed a separate agreement with Resend: according to its data processing agreement, published at resend.com/legal/dpa, that agreement becomes binding when its terms of service are accepted, as we did. According to that same document, Resend processes the data primarily in the United States, transfers from the European Economic Area are made under the standard contractual clauses of the European Commission, and Resend complies with the EU-US Data Privacy Framework, on which the European Commission has adopted an adequacy decision. If you would like a copy of the standard contractual clauses that apply, ask us at info@sirvely.com and we will send it to you. Hostinger International Ltd is a Cypriot company and the server is in Germany, within the European Union.
To read the photo of your paper menu, to translate the names of the items and to describe an item, we send that photo and the name, the description and the category of the item to Anthropic, and to make the photo of an item we send a description of that item to Higgsfield, both companies in the United States. That is the content of your menu and contains no personal data, so they are not processors of personal data and are not in this table.
We use Pay.nl, a Dutch payment service provider, only to charge the restaurants that are our customers for their subscription with the card they have linked. It is not our processor: as a payment provider it processes the card and payment details as an independent controller, under its own responsibility and with its own privacy policy. What we send it is explained in section 3. We do not process any payment of your customers. If you want your customers to pay online, you link your own Mollie or SumUp account; they are your providers and not ours, which is why they are not on this list either, as we explain in section 5.
When we issue invoices for the subscription, our server checks in VIES, the European Commission's service for checking VAT numbers, the VAT number of a restaurant established in a member state of the European Union other than the Netherlands, Spain included, within its VAT area, as section 3 explains. We send VIES only two things: that VAT number and our own VAT number, with which VIES returns a consultation number that proves we made the check. That check carries no more personal data than the VAT number of a sole trader may be. VIES is not our processor: it is a public service of the European Commission that answers whether a VAT number is valid, and the Commission is in the European Union, so the check involves no transfer of data outside it.
Two screens of the restaurant panel also load content from outside directly in the browser, in the copy of the demo that a visitor of this website can open as well. The table cards screen loads the fonts of the preview from Google Fonts, of Google LLC, in the United States. The image of the card that our server draws uses the same fonts, but that download is made by the server and sends none of your data. The screen for the reach of the QR codes shows a map whose images the browser requests from tile.openstreetmap.org, the map service of the OpenStreetMap Foundation, in the United Kingdom. When it loads those fonts and those images, the browser sends them its IP address and its details, as with any request on the internet, and with the map images also which area of the map is being looked at. For collecting those data and sending them to Google and to the OpenStreetMap Foundation by embedding these fonts and this map in our panel, we are jointly responsible with each of them, and we do it on the basis of our legitimate interest, as section 8 explains. What Google and the OpenStreetMap Foundation do with those data afterwards is their own responsibility, under their own privacy policy; they are not our processors.
According to Google's privacy policy, Google LLC has certified that it adheres to the EU-US Data Privacy Framework and appears on the Data Privacy Framework list; the European Commission has adopted an adequacy decision on that framework. According to the privacy policy of the OpenStreetMap Foundation, its map images are served by a global network of cache servers, and which of those servers the browser reaches is decided by that content distribution network at the time of the request. The Foundation's operations team states that this network is provided by Fastly, a company in the United States. The same privacy policy says that personal data other than those of a map image request are stored in the United Kingdom and the Netherlands, and it does not say where the data of a map image request are stored. For the United Kingdom the European Commission has adopted an adequacy decision.
10. How long they are kept
We would rather tell you how things are than promise a period that is not met today. Orders, online payments, table visits, bookings, the order log and the staff's shifts, clock-ins, breaks, corrections and payroll are not deleted automatically: they are kept for as long as you are a Sirvely customer, because they form the history of your business and it is you who consult them. When the relationship ends, those data are deleted at your request, and for that it is enough to email us at info@sirvely.com.
Clock-ins, corrections, contracts and payslips are kept deliberately, even when a person no longer works for you: someone with that history can be deactivated but not deleted, because it is your restaurant's record of hours and payroll and it belongs to you. We only delete them if you ask us to.
Sessions expire on their own. Our server deletes the expired ones every hour, and with them the IP address and the browser details attached to them disappear. The copy of the demo is deleted as we explain in section 7, a registration request is kept as we explain in section 3, and what we keep about partners, as we explain in section 6. The server's technical log is kept as we explain in section 7. The email address to which a receipt is sent, from the history as well, is never stored: all that remains of the visit is the number of receipts the customer asked for at the table. The location of a customer's phone is never stored either. Invoices, the charge decisions they are issued from, and the commissions and payments to partners, are kept for seven years, the period for which Dutch tax law, article 52 of the Algemene wet inzake rijksbelastingen, obliges the company to keep its accounts, even after you have stopped being a customer or the partnership has ended. The invoices and the decisions of the charges we declare through the One Stop Shop of the European Union, those that carry the VAT of the customer's member state, are kept for ten years: that is the period the Belastingdienst, the Dutch tax administration, gives for the data of the One Stop Shop.
The mailings, with the log of who each one went to, and the support tickets, with every message, are not deleted automatically today, and no screen of the admin panel deletes them. They also stay when you stop being a customer or the partnership ends, until you ask us to delete them; the support tickets of a restaurant also go when we delete the restaurant itself at your request. If you ask us to delete them, we delete them without undue delay and at the latest within one month, as the General Data Protection Regulation requires. When an address unsubscribes from our mailings, we keep the address and the moment it did so. That is not deleted automatically either, not even when the restaurant or the partner account it belonged to no longer exists, because that is how we make sure we never write to it again. If you ask us to delete it, we delete it, and a later mailing can then reach that address again if it still belongs to a restaurant or a partner account.
11. Your rights
Anyone whose data we process can ask us to access them, to correct them if they are wrong, to delete them, to restrict their processing, to object to processing based on our legitimate interest and to receive their data in a format that can be taken to another system. Where processing is based on consent, that consent can be withdrawn at any time, without affecting what was done before.
To exercise them, email info@sirvely.com stating what you want and which restaurant you are writing from or, if you are a partner, which partner account. If the request comes from an employee or from a customer at the table, the controller of those data is the restaurant, so the request is addressed to it; we, as processor, give the restaurant the technical support it needs to deal with it and pass on any request that reaches us by mistake. We answer within the one-month period set by the General Data Protection Regulation.
If you believe we have not handled your request properly, you can lodge a complaint with the supervisory authority. In Spain that is the Agencia Española de Protección de Datos, at www.aepd.es. In the Netherlands, where the company is established, it is the Autoriteit Persoonsgegevens, at www.autoriteitpersoonsgegevens.nl. We would appreciate it if you wrote to us first: it is almost always resolved without going that far.
12. Security
All traffic between phones, tablets and our servers travels over an encrypted connection, and the session cookies only travel over that connection, cannot be read from the page's code and contain no data: they are a random code from which nothing can be deduced. Sessions have a limited validity, twelve hours in the admin panel and on the staff tablet and seven days in the restaurant panel and in the partner dashboard. Those of the restaurant panel and the tablet are extended while they are in use; the others are not, and when they end you have to sign in again.
Within the restaurant, each person has the permissions you have given them and sees only what corresponds to their role and their venue. To build your menu or to help you with an incident, our team can enter your account from the admin panel. That session lasts four hours at most and is logged, so it is always possible to check who signed in and when. If a partner brought your restaurant to Sirvely, that partner can open your panel too, to guide you: for four hours at most, able to look at everything and to change nothing, and your panel shows that they are looking.
13. Changes to this policy
The service changes, and this policy will change with it. The version that applies is always the one published at https://www.sirvely.com/privacy/, and the date of the last update appears at the very top, just below the title, so that you can see at a glance whether anything has moved since you last read it. If a change genuinely affects how we process your data, you will see it reflected in that date and in the text of the relevant section. If in doubt, email us at info@sirvely.com.