Cookie Policy

1. Who is responsible?

Vizgu ApS is responsible for the cookies and similar technologies used on vizgu.com.

2. What are cookies and similar technologies?

Cookies are small text files stored on or read from your device when you use a website. Vizgu may also use browser storage and comparable technologies. These technologies can maintain a session, remember a choice, support a requested feature or record how a ticket link was used.

3. Our consent model

Vizgu separates technologies into four categories: necessary, functional, statistics and marketing.

• Necessary technologies are always active because they are required for security, consent management, authentication or a service you explicitly request.
• Functional, statistics and marketing technologies remain inactive until you actively opt in, unless a particular functional technology is strictly necessary to deliver a feature you request.
• Accept all and Reject all are presented with equal prominence. No optional category is preselected.
• Rejecting optional technologies does not prevent you from browsing Vizgu.
• You can reopen Cookie preferences from the footer on every page and withdraw consent as easily as you gave it.

Consent is recorded with your choices, the date and time, and the applicable policy version. Vizgu will ask again if a new vendor or purpose is introduced, the policy version materially changes, or the consent needs to be renewed.

4. Cookie categories

4.1 Necessary

These technologies support core operation, security, authentication, consent choices and features expressly requested by you. They cannot be switched off through the consent tool, but you may be able to block them in your browser. Doing so can cause parts of Vizgu to stop working.

4.2 Functional

Functional technologies remember choices and improve convenience, for example saved places, language, currency and search settings. A preference may be treated as necessary where it is stored only to provide a setting you actively selected and is not reused for another purpose. Other functional storage requires opt-in.

4.3 Statistics

Vizgu currently uses no general analytics technology. This category is included so that future statistics tools cannot operate without a separate opt-in. The policy and vendor list must be updated before such a tool is activated.

4.4 Marketing

Vizgu currently uses no advertising cookies, Google advertising tags, Meta Pixel or third-party advertising scripts. Affiliate attribution is placed in this optional category because it supports Vizgu's commercial commission measurement. If you opt in, an anonymous session identifier may be used to connect your outbound ticket click with later affiliate reconciliation. Vizgu does not receive card details, billing addresses or complete purchase information.

4.5 Third-party content we embed

Photographs on Vizgu are currently loaded directly from Wikimedia Commons, and map tiles from OpenFreeMap. Because your browser fetches these files from those providers, they can set or read information on your device, and Wikimedia does so — it sets an identifier named WMF-Uniq that lasts about 12 months. This happens as the page loads, so the consent tool cannot prevent it. Vizgu is working to serve these photographs from its own storage, which will remove this. Neither provider is an advertising network, and Vizgu receives nothing from them about you.

5. Current technology inventory

The inventory below names each cookie exactly as your browser stores it, so that you can check it yourself. It reflects a scan of the deployed website on 12 August 2026 and must be repeated whenever an integration changes.

Vizgu currently stores nothing in localStorage or sessionStorage. Map tiles are requested from OpenFreeMap, which sets no cookie but does receive your IP address as part of that request.

6. Ticket links and Tiqets

When you open a ticket link, your browser first visits a Vizgu redirect route and is immediately redirected by HTTP 302 to the ticket seller, currently Tiqets. Tiqets then operates its own website and checkout as an independent data controller.

Vizgu does not process your payment, card number, billing address, ticket delivery or refund. Vizgu's click record may include an anonymous session identifier, timestamp, user agent, derived country code, referring page, destination URL, place and provider. Vizgu stores the derived country code in the click record, not the IP address.

If you reject marketing, the redirect still works exactly as before and you can still buy a ticket. The click is counted without any identifier, so it cannot be connected to you or to a later purchase.

7. Providers

• Supabase provides database and passwordless authentication services.
• Vercel provides website hosting and edge delivery.
• Cloudflare R2 provides image storage and delivery.
• Tiqets receives visitors who choose to follow a ticket link and processes checkout data under its own policy.
• Wikimedia Foundation hosts photographs that your browser loads directly, and sets its own cookies when it does.
• OpenFreeMap serves map tiles that your browser loads directly, and receives your IP address as part of that request.

Resend provides transactional email but does not need to set a website cookie merely to deliver Vizgu emails. Providers must be added to the cookie inventory if a deployed integration actually stores or reads information on a visitor's device.

8. Legal basis

Necessary technologies are used where storage or access is technically necessary to provide the service or functionality requested by you. Where cookie consent is required, Vizgu relies on your consent under the Danish cookie rules and GDPR Article 6(1)(a). You can withdraw that consent at any time without affecting processing that occurred before withdrawal.

9. How to change or withdraw consent

Select Cookie preferences in the footer on any Vizgu page. You can change individual categories, reject all optional technologies or withdraw a previous consent. The change takes effect immediately for future storage and access. You may also delete existing cookies through your browser settings; doing so may remove saved places, sign you out and reset preferences.

10. Changes to this policy

Vizgu will update this policy and its technology inventory when purposes, providers or technologies change. Where a change affects an existing consent, Vizgu will request a new choice before activating the changed processing.

11. Contact

Questions about cookies, consent or personal data can be sent to privacy@vizgu.com. Further information about Vizgu's processing of personal data is available in the Vizgu Privacy Policy.