A limited data footprint and a separate Tiqets handoff.

Operator and privacy contact

Data controller / website operator: [Owner action required: publish the operator's verified legal name and country before final production sign-off.]

Privacy contact: [Owner action required: publish a monitored public privacy email address. No private mailbox is exposed without explicit permission.]

Data processed when you browse

The web server and hosting security systems may process standard request information such as an IP address, browser and device details, requested URL, referring page, date and time, and diagnostic or security events. This is used to deliver, secure and troubleshoot the website.

If an Eventuza page requests an approved Tiqets destination or current product information, the server may send the relevant product identifier and supported site preferences to Tiqets. It does not send payment-card or traveler details because Eventuza does not collect them.

If the hosting operator explicitly configures a trusted proxy to supply a two-letter country code, Eventuza may use that coarse code to select a local discovery section. Eventuza does not send an IP address to a separate geolocation service or request precise browser location. You can instead choose a country directly; that explicit preference takes priority over a proxy-provided code.

Device-local storage

Your shortlist is stored in browser local storage on this device. Eventuza does not receive the list merely because you save an item. To support the homepage's recently viewed section, Eventuza also stores at most three numeric Tiqets product identifiers in local storage and in the first-party cookie eventuza_recent_product_ids_v1 for up to 30 days. No product title, search phrase, price, location or customer detail is stored in that history; local storage also contains only a format version and expiration timestamp. Each validated rewrite has a maximum 30-day lifetime. Expired history cannot be revived, and current product details are rechecked before an item appears; unavailable identifiers are removed from both stores. If you choose a country for local homepage ideas, Eventuza stores only its two-letter country code in the first-party, HTTP-only cookie eventuza_country_preference_v1 for up to 180 days. It contains no precise location and is not shared with an external geolocation service. A consent preference may also be read from local storage or a cookie named eventuza_analytics_consent. You can remove these values using your browser's site-data controls.

Optional affiliate click analytics

The affiliate-link component emits an optional browser analytics event only after it finds an explicit granted consent preference. The event contains controlled campaign and placement labels. It does not include a name, email address, payment information, traveler data, Tiqets order reference or a raw search string. No optional event is emitted without that consent signal, and analytics does not delay the outbound link.

The current link code emits this event to the browser's configured analytics listeners; it does not itself make a network request. Any analytics service configured later must remain consent-gated and follow this data-minimization rule.

When you go to Tiqets

A clearly labelled affiliate link sends your browser directly to Tiqets. The outbound URL may contain approved affiliate, non-personal campaign and currency parameters so Tiqets can show the destination and attribute a qualifying booking. Tiqets then receives standard web-request information and applies its own privacy notice. Any customer and payment information is provided to Tiqets, not Eventuza.

Contact messages and retention

If you contact Eventuza, the information you choose to send is used to answer and document the request. Do not send booking or payment details. The shortlist remains until you remove it; recent-product history follows the expiry described above. Server logs and contact records should be retained only for the period needed for security, troubleshooting and the request itself; the operator must verify and publish the production retention schedule before final legal sign-off.

Your choices and updates

You can clear local storage and cookies in your browser, withhold optional analytics consent, and contact the operator about access, correction or deletion of data Eventuza controls. Applicable rights depend on your location. Material changes to this notice should be reflected by updating the date below.

Last updated: 3 August 2026.