Core & Trust · legal
Privacy Policy
The plain-language privacy position for the current Star Budapest launch: no public form or account system, with optional consent-based analytics.
The short version
What matters
- No accounts or public contact form are deployed in this build.
- Google Analytics loads only after you allow analytics; advertising features are disabled.
- External links have their own privacy policies.
01
What this site collects today
The current Star Budapest application does not provide sign-in, comments, a newsletter signup, a public contact form or a booking flow. It does not intentionally collect a visitor’s name, email address, payment information, location history or travel plan through the site interface.
The hosting platform and a visitor’s own browser may still process technical data needed to deliver a web page, such as an IP address, request headers or security logs. Those infrastructure-level practices are not a substitute for a future, service-specific privacy notice if Star Budapest adds a form, email delivery or other data-processing feature.
Sources: wcag-22
02
External links and embedded services
Star Budapest links to operators such as BKK, museums, tourism bodies and ticket sellers because readers need the current source before acting. Following one of those links moves you to another organisation’s site, where its own privacy, cookie and payment policies apply.
The site should not imply control over an external operator’s tracking or data handling. Google Analytics is the optional measurement service described below. Any future map, booking tool, video or additional service will be described here before use.
Sources: budapestinfo-welcome
03
Browser storage and essential delivery
Optional Google Analytics loads only after a saved Allow analytics choice. It uses analytics cookies to measure visits; the preference is stored locally. We omit URL queries, search terms and referrer paths, disable advertising features, and respect Do Not Track and Global Privacy Control. Use Analytics preferences to withdraw consent. Google processes the resulting usage data; we use aggregate reports to improve the guide. Your browser may still keep ordinary local state, and the hosting or security layers used to deliver a website may process technical request data. Those operational details are distinct from a Star Budapest profile or marketing database, neither of which is part of the current product.
If the technical stack changes, the policy will name the new service and explain the role it plays before relying on it for analytics, consent, maps, payments, forms, email or personalisation. A privacy policy should describe the system that exists, not use vague future language to conceal a later change. The current page will remain dated when revised.
Sources: wcag-22
04
Changes and questions
This policy is written for the deployed launch configuration, not an imagined future product. Material changes to how the site collects or shares personal data will be reflected here with an updated date before or at the time the change goes live. It is reviewed annually.
Privacy questions should not include sensitive documents or account credentials. The current build has no public contact endpoint, so this page does not promise a specific response channel until one is securely configured.
Sources: wcag-22
Evidence, not footnotes in the dark