GigbustersVersion 2.0 · Last updated: 28 July 2026
You may have noticed there is no cookie pop-up here. That is not an oversight: we only store on your device what is essential for the tool to work, and for that the law does not require us to ask. There are no advertising cookies, no social media cookies, and no third parties following you around other websites.
It is a design decision and we intend to keep it: if we ever introduced something that does require consent, the corresponding banner would appear before installing it, with the option to refuse as visible as the option to accept.
Almost none of what we use is a cookie in the strict sense: most of it is browser local storage, which does not travel with every request. The only true cookie is the session renewal one.
| Name | What for | Duration |
|---|---|---|
| Session renewal cookie | Keeping you signed in without retyping your password. It is httpOnly — the page's code cannot read it — travels only encrypted, and only towards the authentication path | 30 days |
| Key | What for |
|---|---|
gb_access | Your short-lived session credential |
gb_acting | Which identity you are acting as: yourself, your band or your venue |
gb_theme | Light or dark theme |
gb_lang | Chosen language |
gb_zone, gb_radar:… | Your radar filters — area, styles, categories — remembered for each of your identities |
gb_device_id | A random device identifier. It exists so a gig confirmation made without an account counts only once. It identifies no person and never leaves your browser: the server keeps only its hash |
gb_intro_vistos, gb_tours_hechos | Which welcome messages and tutorials you have already seen, so we do not repeat them |
| Key | What for |
|---|---|
gb_intro_sesion | That you already dismissed the welcome message on this visit |
gb_radar_publico_region | The region you chose on the public radar, so we do not ask again during your visit |
gb_recarga_trozo | Recovering from a loading failure after an update to the app |
We do want to know how the tool is used in order to improve it, but we measure that on our own server, from the requests we already serve. We install nothing on your device for it, there are no pixels or third-party tags, and there is no advertising identifier. How it works and how to object is in section 5 of the Privacy Policy.
Advertising is our own and is served from our servers. We use no advertising cookies and share no identifiers with ad networks. To avoid repeating the same advert at you we keep a count on the server, tied to your account, not a marker on your device.
When a map is displayed or you play embedded audio or video, your browser connects to that provider and they can set their own cookies. That processing is governed by their policy, not ours. We load players in the most restrictive mode each provider offers — for example YouTube's cookie-free domain — and videos and audio are not loaded until you choose to play them.
The full list of third parties, with what each receives and when, is in section 8 of the Privacy Policy.
If we add, remove or change the purpose of any of the above, we will update this page and its date. And if we ever introduced something requiring your permission, we would ask before installing it.
Legal Notice · Terms · Community · Business · Privacy · Cookies · Emails