YOUR DATA.
NO BULL.

01 / THE BASICS

Who is responsible

This website is operated for Bulls on Parade, a Rage Against The Machine tribute band based in Belgium. For questions about personal data on this site, contact tomadde@bullsonparade.be.

This notice describes the site's current intended data practices. The exact processing can depend on which services are enabled and on your interactions with the site.

02 / FIRST-PARTY VISITOR INSIGHTS

How this site counts visits

The site uses a first-party analytics script, loaded as a deferred public asset, to understand how people find and use the band website. The owner has chosen not to display a cookie banner. That choice is not a claim that consent or a banner is legally unnecessary. Whether consent is required depends on the technologies used, their purpose, and applicable law.

• A pseudonymous visitor identifier is stored in your browser for up to one year; an inactive session ends after 30 minutes.
• Recorded events include page views, referring website hostnames, campaign UTM values, time on page, scroll depth, and clicks on booking buttons, video play buttons, ticket links, Bandsintown, promo downloads, social links, and email/phone links. Outbound destination hostnames are recorded, not full destination URLs or email/phone values.
• Device category, operating system, browser, browser language, and screen dimensions are recorded. Common bots are excluded.
• Full URL query strings are not collected. The presence of fbclid or gclid is recorded only as a yes/no flag, not as the identifier value.
• Approximate country, region and city are derived locally on the server through GeoIP. The IP address is used transiently for that lookup and is never stored in the site's analytics database or application logs. Hosting and network providers may process connection information separately.
• Analytics records are retained for a maximum of 13 months.

These insights are available to the band owner in a private visitor report. They are intended to describe traffic, not to identify visitors by name.

03 / OPTIONAL AD MEASUREMENT

Meta Pixel & Conversions API

If a Meta Pixel ID is configured, the site may use the Meta browser Pixel and server-side Conversions API (CAPI) to measure activity. The browser and server events use deduplication identifiers so Meta can recognise the same event sent by both routes. Events can relate to page views, video interactions, contact, booking, and ticket actions.

• When a booking email address is available for a booking event, a SHA-256 hash of that email may be sent to Meta for matching. The raw email is not sent to Meta by this matching step.
• A visitor's IP address and user-agent may be sent transiently to Meta with an event for matching. The website application does not store those values as part of this event context.
• Event IDs, event names, event time, the public page URL without its query string, and a hashed pseudonymous visitor ID are sent by the server. The browser Pixel can additionally observe the browser's page URL, referrer, device information and Meta cookie identifiers under Meta's own practices. The site's own analytics stores only presence flags for fbclid and gclid, but that does not prevent Meta's browser script from accessing URL signals.

Meta processes data under its own terms and privacy information, potentially outside the European Economic Area. No Meta script or CAPI event is loaded or sent while the Pixel ID is empty. With an ID, the browser Pixel is enabled; CAPI additionally requires a server-side access token. Automatic Pixel configuration is disabled; this site explicitly sends PageView, ViewContent on video playback, Contact for email/phone clicks, Lead after a successful booking email, and a custom Tickets event.

04 / ENQUIRIES

Booking enquiries

When you send a booking enquiry, the details you provide are emailed using One.com. Booking details are not stored in a website database. The email provider handles the message so the band can respond and coordinate a potential performance. Avoid including information that is not needed for your enquiry.

The analytics system may record that a booking action occurred, separately from the enquiry's message details. The booking email itself is not copied into the analytics dashboard.

05 / VIDEO

YouTube videos

Video embeds use YouTube's privacy-enhanced embed domain and are intended to load only after you choose to play a video. Once you play one, YouTube may receive information about your device and viewing activity under Google's terms.

If video IDs and thumbnails are configured on the page, thumbnail images may be requested from YouTube before you press play. That request can disclose technical connection information to YouTube even though the video player itself has not yet loaded.

06 / CONTROL & RETENTION

Retention, choices & rights

First-party analytics data is kept for no more than 13 months. The browser identifier can be removed by clearing site data in your browser. Blocking scripts, cookies, or third-party requests may limit some site functionality or measurement, but does not affect the ability to read public pages.

Depending on applicable data-protection law, you may have rights to access, correct, erase, restrict, object to, or receive a copy of personal data, and to complain to your supervisory authority. These rights can depend on the circumstances and applicable legal basis. Contact the band to make a request; we may need enough information to understand and respond to it.

External services such as Meta, Google/YouTube, and One.com may process information under their own policies and may have separate retention practices.

Page fonts are requested from Google Fonts, which receives the technical connection information needed to deliver them. Hosting infrastructure processes requests to serve this website. These third-party connections are separate from the site's first-party analytics database.

07 / GET IN TOUCH

Questions about your data?

For a privacy question, data request, or a correction to this notice, write to the band. Please say what your request concerns; do not send passwords or sensitive information.