Your data, plainly.

Who is responsible

beatbox·world operates this site and decides how the data described here is used (that makes it the “data controller” in GDPR terms). For anything privacy-related, the fastest route is the privacy contact form — it lands directly with the team.

The archive: data about beatboxers

The heart of the site is an archive of beatbox competitions. For the people who competed, it holds: stage names (blazes), competition results and placements, event line-ups, jury votes as announced at events, country, and photos or videos already published by organizers.

This information is referenced by trusted contributors from what competitions made public. We process it on the basis of legitimate interest: keeping the history of a scene that would otherwise scatter and disappear — results that were announced on a stage, in public.

If you’re a beatboxer in the archive, it’s your data. You can ask for a correction, object to an entry, or request deletion of personal details — we reply within one month. Claiming your profile in the app also lets you fix your own details directly.

Cookies

The site sets one strictly functional cookie: PARAGLIDE_LOCALE — it remembers the language you picked so the site stays in it. It identifies a preference, not a person.

A second cookie, wb_consent, only remembers your answer to the banner — accepted or refused — for a year. Google's measurement script is downloaded on every visit, so Google sees your IP address at that moment; that is what lets the tag exist without waiting for your answer. But it is loaded with every consent signal denied: as long as you haven't accepted, it stores nothing on your device and sends no measurement data — not a single page view. Accept, and measurement starts along with its cookies. Refuse, and nothing is ever sent. No advertising signals are ever granted, no advertising cookies, no fingerprinting.

Third parties the site loads

Some things are served from other companies’ servers. When your browser fetches them, those companies technically see your IP address — that’s how the web works. Here’s the full list:

• Google Analytics audience measurement: which pages are viewed, where visits come from. Its script loads on arrival with storage and measurement denied — no page view is sent, and no cookie is set, until you agree.
• YouTube battle videos, embedded in privacy-enhanced mode (youtube-nocookie): YouTube sets no cookies until you press play. Video thumbnails also come from YouTube’s servers.
• CARTO the map tiles behind the globe on the home page.
• Google Fonts the site’s typefaces.

That's all. No ad networks, no social widgets.

The contact form

When you write to us, the name, email and message you send are used to answer you, and for nothing else. They’re kept as long as the conversation needs, then left alone.

Server logs

Like any web server, ours keeps short-lived technical logs (IP address, requested page, timestamp) to keep the site running and detect abuse. They rotate away on their own.

Your rights

Under the GDPR you can ask for: access to what we hold about you, correction, deletion, objection, restriction of processing, and portability. One message is enough — no form, no proof-of-motive.

We answer within one month. If you feel we handled it wrong, you can complain to your data-protection authority (in France, the CNIL).