Cookie policy
This website sets no cookies itself; only if you start the demo does our API write the session cookies of that demo. Here we explain the only things it stores in your browser, why there is no consent banner, and which cookies and which data the service behind it stores, at app.sirvely.com, at partners.sirvely.com and at admin.sirvely.com.
Last updated: 21 October 2026
1. What happens on this website
Let us start with the most important thing, which is also the shortest: this website, https://www.sirvely.com, sets no cookies. The only things it keeps in local storage are four keys: sirvely.cookiemelding, so that we do not show you the information notice again once you have read it; sirvely.taal, the language you chose in the language picker at the foot of the page or in the menu at the top; sirvely.partner, the code of the person who recommended Sirvely to you, if you arrived through their link; and sirvely.sandbox-locale, the language of the demo you started with View the demo. If that demo cannot start, it also keeps sirvely.demo-failure for a moment in the storage of that tab. We use no statistics or analytics tool, there are no tracking or advertising pixels, and we load no videos, maps, chats or any other third-party content. The fonts are served from our own server, so your browser asks nothing of Google Fonts or any other external provider. This website talks to our API in three cases only: if you came through a partner's link, it tells the API once that there has been a visit with that code, with no other data; if you press View the demo, it asks the API for your own copy of the demo restaurant, and in that case it is the API that writes the demo's session cookies, as we explain in section 3; and if you send a message with the contact form, it sends the API what you filled in, which the privacy policy explains. The form keeps nothing in your browser.
One thing follows from all this: there is nothing we need to ask your consent for. What you see when you arrive is an information notice, not a consent banner: it has no reject button because there is nothing to reject, and it blocks nothing. The absence of a consent banner is not an oversight or a technical fault but a decision. A banner only makes sense when there is something to accept or reject, and here there is not. The day there is, we will ask before setting anything, as we explain in the last section of this page.
What does have cookies is the service itself, which lives at another address and which only you and your staff use after signing in with a password. We describe it below, so that this page is just as useful to you when you are working in the panel.
2. What a cookie is
A cookie is a very small file that a website leaves in the browser of whoever visits it so that it can recognise that same browser later, for example to keep a session open, to remember a preference or to count visits. There are also other ways of storing information in the browser, such as local storage, which are technically not cookies but are worth explaining all the same, which is why you will find both on this page.
3. Cookies on app.sirvely.com, partners.sirvely.com and admin.sirvely.com
The restaurant panel is at https://app.sirvely.com, the dashboard of the partners who bring restaurants to Sirvely is at partners.sirvely.com, and the admin panel, which only we use, is at admin.sirvely.com. There are cookies there, because without them there is no way to keep someone identified after they type their password or their PIN. They are written by our API, at api.sirvely.com, and they are these four:
| Name | What it does | Duration | Type |
|---|---|---|---|
| jv_tenant | Keeps the restaurant panel session open. | 7 days by default, and it is extended while you use the panel | Technical, strictly necessary |
| jv_staff | Keeps open the session of the tablet the staff use on the floor. | 12 hours by default, and it is extended while it is in use | Technical, strictly necessary |
| jv_partner | Keeps open the session of the dashboard of a partner who brings restaurants to Sirvely. | 7 days by default | Technical, strictly necessary |
| jv_admin | Keeps open the session of the admin panel, which only we use. | 12 hours by default | Technical, strictly necessary |
All four are httpOnly, which means the page's JavaScript cannot read them, they always travel encrypted over https and they are marked SameSite Lax. Their value is not your name, your email or anything that can be interpreted by looking at it: it is a random identifier that only means something inside our database.
As they are strictly necessary to provide the service you have asked us for, these cookies are exempt from the duty to ask for prior consent. That is what article 5(3) of the ePrivacy Directive provides, as implemented in the Netherlands, where the company is established, by article 11.7a of the Telecommunicatiewet, and in Spain by article 22.2 of Law 34/2002 on information society services and electronic commerce. In other words: we do not ask whether we may keep you signed in to the panel, because without that there would be no panel. If you block them in your browser, you will not be able to sign in.
When we go in from the admin panel to look inside a restaurant's panel, for example to help you with an incident, that session lasts four hours instead of seven days, is not extended and is logged as what it is. When a partner opens the demo of the restaurant panel from their dashboard, they get a jv_tenant session that lasts four hours in the demo restaurant that we choose, in which they can look at everything and change nothing. That session is not extended either, but it is not written to the log of the admin panel: the session itself only records which partner opened it. A partner who brought your restaurant to Sirvely can open your own panel in the same way, to guide you while you look at it together: that jv_tenant session also lasts four hours, is not extended, lets them look at everything and change nothing, and your panel shows who is looking and where their pointer is.
When you press View the demo on this website, our API makes your own copy of the demo restaurant and writes the jv_tenant cookie for its panel, so that the demo opens without a password. That cookie lasts as long as the demo, two hours at most, and it is not extended. If in the demo you also sign in on the PIN screen with the PIN it shows you, the API writes the jv_staff cookie as well, which like every PIN session lasts twelve hours. So that nobody can take every demo at once, the API keeps with that copy the IP address you started it from (of an IPv6 address only the network part). With each of its sessions it keeps, as with every sign-in, your full IP address and the details of your browser. All of it is deleted together with the copy: after two hours, after half an hour without use or as soon as 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 of the demo can stay for up to twelve hours in any case, but once the copy has been deleted neither of them leads anywhere. Signing out of the demo's panel removes both.
A technical note so that it does not surprise you: depending on how the cookie domain is configured, the browser may also send them to https://www.sirvely.com, even though this website neither uses nor reads them. They are always written by the API and they only serve the panel. What we do with the personal data behind those sessions is explained in the privacy policy.
4. Local storage in the browser
On app.sirvely.com there are seven keys kept in the browser's storage, on partners.sirvely.com there is one, and on this very website there are five more. They are not cookies: they are not sent automatically with every request to the server but stay on the device until someone deletes them or the program itself changes them.
| Key | Where it is stored | What it does |
|---|---|---|
| sirvely.cookiemelding | In the browser of anyone visiting https://www.sirvely.com | Remembers that you have already read the information notice in the footer, so as not to show it to you again. It does not leave your device and we do not receive it. |
| sirvely.taal | In the browser of anyone visiting https://www.sirvely.com | Remembers the language you chose in the language picker at the foot of the page or in the menu at the top, so as to open the website in that language next time instead of guessing it from the browser. It does not leave your device. |
| sirvely.partner | In the browser of anyone visiting https://www.sirvely.com | Stores the code of the person who recommended Sirvely to you, if you arrived through their link. It only travels if you press Register on this website: it goes in the address of the registration at app.sirvely.com, so that we know who recommended you. |
| sirvely.sandbox-locale | In the browser of anyone who presses View the demo on https://www.sirvely.com | Remembers the language of the demo you started, so that the next press opens that same demo again, or makes a new one if you have changed language. It does not leave your device. |
| sirvely.demo-failure | In the storage of one tab on https://www.sirvely.com, only for a moment | If the demo cannot start from a page without the demo section, such as this one, it carries the reason to the home page, which shows it and deletes the key straight away. It does not leave your device, and it disappears when you close the tab. |
| sirvely-apparaat | On the phone of the customer ordering from the table | Stores a random identifier for that phone, so that in the panel you can see how many phones are ordering at the same table. |
| sirvely.bel.aan | In the browser where you have the panel open | Remembers whether the sound alert for a new order is on or off. |
| sirvely.zaak | In the browser where you have the panel open | Remembers which venue was chosen last, so as to open the panel where you left it. |
| sirvely.dashboard.taal | In the browser where you have the panel open | Remembers the language of the panel, so that the screen opens in that language straight away. The choice itself is kept in your account. |
| sirvely.partner.taal | In the browser where a partner has their dashboard open at partners.sirvely.com | Remembers the language of the partner dashboard, so that the screen opens in that language straight away. The choice itself is kept in the partner's account. |
| sirvely.staff_app.slug | In the browser where your staff use the staff app | Remembers which restaurant the PIN session on that device belongs to, so that the link of another restaurant never continues it. |
| sirvely.auth.arrived | In the storage of one tab of the panel, only for a moment | Tells the panel that you have just signed in, so that it slides in once. The panel deletes it as soon as it has read it. |
| sirvely-pago-<payment id> | In the storage of one tab on the phone of the customer who pays online | Only if the restaurant has switched on online payment, which is optional: while the customer pays on the page of the restaurant's own Mollie or SumUp, keeps what they were paying for, the cart or the amount of the bill and the tip, so that it is still there when they come back. It is deleted once the payment has gone through or has failed, and it disappears when the tab is closed. |
The keys of the panel sirvely.bel.aan, sirvely.dashboard.taal, sirvely.staff_app.slug and sirvely.auth.arrived never leave the device, and neither does sirvely.partner.taal of the partner dashboard: we do not receive them and we do not store them anywhere. The language in sirvely.dashboard.taal and sirvely.partner.taal is only a copy of the choice that the account itself keeps. Nor does sirvely-pago-<payment id> ever leave the customer's phone. Those of this website, sirvely.cookiemelding, sirvely.taal, sirvely.sandbox-locale and sirvely.demo-failure, do not leave your browser either, and sirvely.partner only leaves when you press Register yourselves. Only two travel on their own. The panel sends the venue in sirvely.zaak along with its requests, because that is how our API knows which of your own venues you are working in. And sirvely-apparaat travels with the order, because the phone's identifier is precisely what lets you see that there are three phones ordering at one table rather than three different tables. That identifier is a random value that says nothing about the phone or the person carrying it, and we do not cross-reference it with any other information.
None of the thirteen is used to measure audience or to advertise. All of them exist so that the service works as you expect, and they are deleted just like cookies, as we explain next.
5. How to delete them
Everything above is in your browser, and you are the one in charge of it. Any browser lets you see the cookies and data a site has stored, delete them one by one or all at once, and prevent new ones from being stored. The option is usually in the settings, under privacy or browsing data, and you can also reach it by clicking the icon that appears just to the left of the page address. If you would rather leave no trace of a particular visit, a private browsing window deletes everything when you close it.
On this website the only things you can delete are those five keys, and the only effect is that the information notice will appear once more, that the website will again choose the language from your browser, that we will forget the partner code and that View the demo will make you a new demo instead of opening the one you had. If you do it on app.sirvely.com, partners.sirvely.com or admin.sirvely.com, bear in mind that the session will be closed and you will have to sign in again with your password or PIN, and that the panel will ask you again for the venue and the sound alert because it will have forgotten your preferences. No restaurant data are lost: what is deleted is on the device, not in your account.
6. If this changes
Today we measure nothing, and we are not going to promise you that it will be like that for ever. One day we may want to know how many people reach this website and from where, or we may embed a video, a map or a third-party chat. If that day comes, we will not do it quietly: we will ask you first with a clear notice, in which saying no is as easy as saying yes, and no cookie will be set and no third-party content loaded until you have clicked. We will also update this page, and the date at the top will tell you when we last did so.
Sirvely is a trading name of a Dutch company registered with the Netherlands Chamber of Commerce under number 86964178 and with VAT identification number NL004333820B72, with its registered address at Zandzuigerstraat 70, 1333 HD Almere, the Netherlands.
If you have any question about this policy, email us at info@sirvely.com or call us on +31 85 060 4404. The company's full details are in the legal notice, what we do with personal data is in the privacy policy, and the rules of the service are in the terms.