GigbustersCookie Policy
Version 4.0 · Last updated: 25 September 2026
1. How the banner works, and what happens depending on what you choose
The banner has two layers. The first, the strip at the bottom, offers three options with the same size and the same weight — Accept all, Reject all and Settings — because a decision where one option costs more than the other is not a decision. The second, opened from «Settings», breaks down the three categories in the next section with a switch each (except «Necessary», which has none) and the buttons Save selection, Accept all and Reject all.
What you save per category is respected to the letter: if you turn off «Statistics», Google Analytics is not installed or, if it already was, it is withdrawn and its cookies are deleted; if you turn off «Third-party content», every video or audio stays behind a cover with «Play» until you press it, from the next time you open the page. Any cookies those services had already stored are theirs and we do not delete them when you withdraw consent: you can delete them from your browser (section 7).
You can change your mind whenever you like from the «Cookie settings» link, which is in the footer of every page and, inside the app, in the profile menu. Either way we ask again after a year, or sooner if the banner's categories change: neither the yes nor the no is forever.
What we still do not do: there are no advertising cookies, no social media cookies, and nothing following you around other websites, and we share no identifiers with any ad network. There is no «Marketing» category — the day advertising needs one, it will be added.
2. The three categories
| Category | State | What it covers |
|---|---|---|
| Necessary | Always on, no switch | Your session, the decision you make about this banner, and the preferences you choose yourself — language, theme, radar area — together with the cache that lets the app work offline. Spanish data-protection guidance exempts what the user themself expressly requests from needing consent |
| Statistics | Off by default |
Google Analytics 4 (_ga, _ga_9MMW1ZE8DD): tells us which screens
get used and which ones get stuck. Withdrawing consent deletes those cookies and we stop
sending anything
|
| Third-party content | Off by default |
The YouTube (on its cookie-free domain, youtube-nocookie.com), Vimeo and
SoundCloud players. Without your permission you see a cover with a «Play» button: nothing
loads until you press it, and from there you can also «Always allow»
|
Outside this banner, because they do not belong in it: Google reCAPTCHA on the contact form (it is security, not measurement or advertising — section 6) and OpenFreeMap maps, which set no cookie at all.
3. Exactly what we store
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 true cookies are the session renewal one and the one holding your decision on this banner.
Cookies
| Name | What for | Duration |
|---|---|---|
gb_refresh |
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 (app.gigbusters.com/api/v1/auth). Necessary category |
30 days |
_ga · _ga_9MMW1ZE8DD |
Only if you accepted Statistics. Set by Google Analytics, which is a third party, to tell whether a visit is new or returning — not to tell who you are. The data is also processed outside the European Union, under the safeguards the law requires for such transfers. If you refuse they are not installed; if you accept and later withdraw consent, they are deleted | 2 years |
gb_consent |
Your choice for each category and the date you gave it, so we do not ask again. It is set
on the .gigbusters.com domain — shared by the web, the app and the blog, so
the banner is not repeated when you move between them. It is not a third-party cookie and
it is stored even when you reject everything — precisely so that decision is respected.
Necessary category
|
1 year |
Local storage (stays until you clear it)
| 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 |
gb_asistencias_pendientes | Attendance confirmations that were not sent yet (for example, without coverage) until they are actually sent |
gb_codigos:… | The batch of attendance codes for your profile, so it can be shown without asking the server again |
gb_escaneos:… | The scans you have made as an organiser for an event, so they are not lost if the connection drops |
gb_cache:… | A copy of your data so the app can open offline |
gb.ubicacion_decision | Whether we already asked about your location and what you answered, so we do not ask again on every visit |
Session storage (cleared when you close the tab)
| 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 |
gb_recarga_version | The new version this tab has already reloaded itself for, so it does not reload twice |
gb_toast_vistos | Which notices you have already been shown on this visit, so we do not repeat them |
gb_pila | This tab's screen history, so «Back» works |
gb.recien_entrado | That you just signed up, so an in-between screen is skipped once |
gb_escenarios_… | The planned stages you marked while building a festival lineup, for the length of the session |
4. How we measure usage
In two ways, and only one of them needs your permission.
Always: we count on our own server, from the requests we already serve. Nothing is installed on your device for it, there are no pixels and there is no advertising identifier.
Only if you accept: Google Analytics, which does store the two cookies listed in the previous section. It tells us which pages get used, which ones get stuck, and from which country and kind of device people arrive. We do not send it your name, your email or your user number. We tell the web apart from the app, and nothing else.
How all of this works and how to object is in section 5 of the Privacy Policy.
5. Advertising
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.
6. What others set
When 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. That
is why it sits inside the «Third-party content» category: without your permission, each player
stays behind a cover with a Play button and nothing loads until you press it;
from there you can also choose «Always allow» so the cover does not come back. We load players in
the most restrictive mode each provider offers — for example YouTube's cookie-free domain,
youtube-nocookie.com.
OpenFreeMap maps set no cookie at all, which is why they are always shown, without going through this banner.
When you start using the contact form, Google reCAPTCHA is loaded to check that you are a person and not an
automated program. Google may set a security cookie on its own domain (_GRECAPTCHA)
and use local storage. It is a security measure for the form you are using, not measurement or
advertising, which is why it does not go through the cookie banner. It is not loaded when
the page opens: only if you use that form. It is governed by
Google's policy.
The full list of third parties, with what each receives and when, is in section 8 of the Privacy Policy.
7. How to clear or block it
- From your browser settings you can clear or block cookies and local storage for this site.
- Clearing session data will sign you out of Gigbusters and lose any radar filters you had saved.
- If you block all storage, the app will still open but will not be able to keep you signed in.
- Your browser's private browsing mode clears everything when you close the window.
8. Changes
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 · Cookie settings · Emails