Shooes Cookie and Local Storage Policy
Last updated 29 July 2026
Top deals today
Shooes compares running-shoe prices across every retailer in Belgium, refreshed daily.
This policy explains what ME Technologies SRL, which operates the service under the commercial name Shooes, stores on your device when you use shooes.io or the Shooes apps. It sits alongside our Privacy Policy.
ME Technologies SRL, Rue des Patriotes 6, 1000 Brussels, Belgium. Enterprise number 1018.010.743. info@shooes.io.
1. Cookies, local storage and why we cover both
A cookie is a small text file placed on your device by a website. Local storage does much the same job through a different browser mechanism: the site writes data to your device and reads it back on your next visit.
The law treats them the same way. Article 5(3) of the ePrivacy Directive covers storing information on, or reading information from, your device, whichever technique is used. So this policy covers cookies, local storage, session storage, mobile app storage and similar technologies together.
Shooes uses almost no cookies. Nearly everything we store is in your browser's local storage.
2. Your choices
Everything listed in section 3 is there to deliver something you asked for: staying signed in, keeping your wishlist, remembering your market, loading the catalogue quickly, and routing your requests to our servers. Storage and cookies of this kind are exempt from the consent requirement in Article 5(3) of the ePrivacy Directive, which is why Shooes has no consent banner.
We do not run advertising. For measurement we use a single privacy-preserving analytics tool (Vercel Web Analytics, described in section 3.6). It sets no cookies, stores nothing on your device, and does not follow you to other websites. We operate no other beacon, tag or event pipeline.
If we ever add anything that stores information on your device for analytics or advertising, we will add a consent banner, ask before storing it, and update this policy first.
You can clear anything we have stored at any time through your browser settings, or by signing out. Clearing it will sign you out and reset your saved preferences and locally held wishlist.
3. What we store
3.1 Local storage on shooes.io
| Key | Purpose | Duration |
|---|---|---|
shooes.session.v2 |
Your sign-in token, so you stay signed in between visits | Until you sign out or clear it |
shooes.favorites.v1 |
The shoes on your wishlist, so they persist on your device and sync to your account if you have one | Until you clear it or sign out |
shooes.favremovals.v1 |
Records wishlist items you have removed, so a removal is not undone when your device syncs with our server | Until you clear it or sign out |
shooes.searchindex.v1 |
A cached copy of the shoe catalogue, so search is fast and works without re-downloading it on every visit. Catalogue data only, nothing about you | One day. It is keyed by date and country, and is replaced when either changes |
shooes.stats.v1:{country}:{date} |
Six summary numbers about the catalogue in your selected country, such as how many shoes are available and the average saving. Calculated on your device from an ordinary catalogue request and cached so we do not recalculate on every visit. It holds nothing about you and is never sent anywhere | One day. Writing a new day's entry deletes the previous one |
3.2 Cookies
The shooes.io website sets no cookies at all. The only cookies involved are set by Microsoft Azure on the domain that hosts our own API, when your browser calls it.
| Cookie | Set by | Purpose | Duration |
|---|---|---|---|
ARRAffinity |
Azure App Service, on our API domain | Keeps your requests going to the same backend instance, so a sequence of calls behaves consistently | Session. Deleted when you close your browser |
ARRAffinitySameSite |
Azure App Service, on our API domain | The same purpose, with a SameSite attribute set for modern browsers | Session. Deleted when you close your browser |
Both are marked HttpOnly and Secure, which means scripts cannot read them and they are only sent over an encrypted connection. They are load-balancing cookies. They do not identify you, do not track you between visits, and are not used for any purpose beyond routing.
3.3 Mobile apps
Our apps do not use browser cookies. They store the equivalent information on the device: your sign-in token, your wishlist, your market and display preferences, and a cached copy of the catalogue. You can clear it by signing out or removing the app.
3.4 Affiliate attribution
When you click through to a retailer, we may be paid a commission if you buy something. This costs you nothing and does not change the price you pay.
Depending on the retailer, the link either goes straight to their site or passes through a redirect domain operated by an affiliate network. In both cases the attribution cookie is set by the network or the retailer on their own domain, after you have left Shooes, and is governed by their cookie and privacy notices, not this one.
Our affiliate partners include AWIN, CJ, Impact, ShareASale, Rakuten Advertising, Adtraction, Belboon, Effinity, NetAffiliation and Partnerize.
3.5 Advertising
We do not use advertising or targeting cookies. We do not sell advertising space on Shooes, we run no ad networks, and we build no advertising profiles about you.
3.6 Analytics
We use Vercel Web Analytics on shooes.io to count visits in a privacy-preserving way: which pages are viewed, roughly where visitors come from, and what devices they use.
It is designed not to need your consent, and here is why. It sets no cookies and stores nothing on your device, so the storage-consent rule in Article 5(3) of the ePrivacy Directive is not triggered. The script loads from our own domain, identifies no individual visitor, and cannot follow you to other websites. Visitors are counted per visit through a temporary hash that is discarded within a day and is never available to us; we only ever see aggregate numbers.
If we ever add a tool that does store something on your device - for example advertising measurement - we will list it here and ask for your consent through a banner before setting anything.
4. Permissions the apps ask for
Separately from storage, the apps may ask your permission for specific device functions, for example approximate location to pre-select your market. We ask through the standard prompts on your device, and you can revoke these permissions at any time in your device settings.
5. Changes
We may update this policy as what we store changes. The current version is always published here with the date it took effect.