Cookie policy
This website sets no cookies. 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 and at admin.sirvely.com.
Last updated: 10 September 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 three 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 selector in the header; and sirvely.partner, the code of the person who recommended Sirvely to you, if you arrived through their link. 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 one case 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.
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 and admin.sirvely.com
The restaurant panel is at https://app.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 three:
| Name | What it does | Duration | Type |
|---|---|---|---|
| jv_tenant | Keeps the restaurant panel session open. | 7 days by default | Technical, strictly necessary |
| jv_staff | Keeps open the session of the tablet the staff use on the floor. | 12 hours 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 three 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 and is logged as what it is.
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 three keys kept in the browser's storage, and on this very website there are three 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 selector in the header, 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 write to us from a button on this website: it goes in the text of the email, so that we know who recommended you. |
| 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. |
The two panel keys are your own preferences and never leave the device: we do not receive them, we do not store them anywhere and we do not know what value they hold. Those of this website, sirvely.cookiemelding and sirvely.taal, do not leave your browser either, and sirvely.partner only leaves in the email you send us yourselves. The only one that travels on its own is sirvely-apparaat, because the phone's identifier travels with the order, and that 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 six 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 three 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 and that we will forget the partner code. If you do it on app.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.