Cookies
The ones this needs to work, the Meta one that is only set if you say yes, and how to change your mind.
What you decide, and what you do not
For a long time this site had no third parties at all, and this page said that was why there was no banner. That stopped being true: we run ads on Instagram and Facebook, and to know which ones work we use the Meta pixel. That needs your permission, so now there is a banner.
The necessary cookies and the language one are not up for consent: without the first there is no service, and the language one is your own choice. Spanish law (art. 22.2 LSSI) exempts both. The Meta pixel is the only thing we ask about, and it does not load until you say yes: if you say no, or say nothing, your browser never receives a single line of its code.
Refusing costs exactly what accepting costs: two identical buttons, side by side. And the site works just as well either way.
The necessary ones, and the language one
oido_session — necessary. Keeps you signed in. Without it you would have to type your password or PIN on every screen. Not readable from JavaScript, sent over HTTPS only, expires when you sign out.
oido_org — necessary. Only for Groups plan customers: remembers which restaurant of the group you are working in. It holds an identifier the server always checks against the restaurants that are actually yours. Lasts one year.
oido_lang — preference. Stores the language you picked so you need not pick it again. Written only when you change the language. Lasts one year.
oido_consent — necessary. Stores your answer to the banner so we do not ask again. It holds a yes or a no and a version number, nothing else. Lasts one year. If a third party other than Meta is ever added, that number changes and you are asked again: permission given for one thing does not cover another.
oido_origen — necessary. If you arrive from one of our ads, it stores that ad's tags (utm_source, utm_medium, utm_campaign, utm_content, utm_term) so that, if you end up signing up, we know which ad brought you. It never leaves our server, Meta and nobody else sees it, and it holds nothing about you: they are the ad's details, not yours. It is deleted as soon as you sign up, and in any case after 30 days.
The Meta one, only if you say yes
_fbp, and _fbc if you arrived from an ad — advertising. Set by the Meta pixel. They let Meta tell us how many of the people who saw our ad ended up here or signed up. Without them we would be advertising blind.
They are received by Meta Platforms Ireland Limited, which does not act on our behalf: it decides on its own what to do with that data, and may process it outside the European Economic Area. What it does with it is explained in its own privacy policy.
They load only on the public pages — this marketing site and the sign-up. They never enter the app: someone dictating their kitchen orders is not who an ad is measured on, and there is no pixel there even if you said yes.
What the necessary ones do not do
None of the first five can track you across other websites, build a profile about you, or is shared with anyone. They hold no personal data: a random identifier, a restaurant identifier, a two-letter language code, a yes or a no, and one of our own ads' details.
How to change your mind, and how to remove them
To withdraw permission for Meta, delete the oido_consent cookie from your browser settings: next time you visit the banner will appear again and you can say no. From that moment on we stop loading the pixel.
All of them can be deleted or blocked from your browser. Note that blocking oido_session makes signing in impossible: without it the server cannot tell it is still you from one page to the next.