Privacy notice
What this static site does and does not do.
This notice describes the Flypark implementation as delivered. Flypark is a static informational website. It does not provide accounts, reservations, payments, newsletters, advertising, analytics, behavioral profiling, a server-side contact form, or third-party booking transactions. Publisher identity, hosting provider, host-log retention, and an active privacy contact are not configured; they must be finalized before public launch.
This notice is an implementation disclosure, not a claim of compliance with every law in every place. A future publisher should obtain advice appropriate to its identity, host, audience, and data practices before launch.
Information and local storage
The optional checklist saves only in this browser.
The homepage includes an optional departure checklist. When a visitor ticks its boxes, the page uses browser local storage under a Flypark key so the checks can persist on that browser. The information is not sent to Flypark by this code. The “Reset this local checklist” button removes that key from the browser. Visitors can also clear site data through their browser controls.
Do not place reservation numbers, payment details, license plates, passport data, or other sensitive information into this site. Flypark has no active contact form and does not ask for it. The displayed email address is not configured; do not use it yet.
Remote requests and external links
Fonts, styling, photos, and source links involve other providers.
The HTML requests Google Fonts to display Space Grotesk and IBM Plex Sans, and it loads Tailwind CSS from the Tailwind CDN. It also embeds three remote Wikimedia Commons image URLs. A visitor’s browser may send technical request information, such as IP address, browser headers, and requested resource details, to those providers when the relevant resource loads. Remote photos and outbound source links use a no-referrer policy attribute where implemented, but that does not eliminate all information a network request can reveal.
Flypark links to airports, operators, Creative Commons, Wikimedia Commons, and other external websites. Those sites have their own privacy practices. Leaving Flypark through a link is a separate interaction; review the destination’s notice before providing information.
Cookies, logs, and retention
No analytics or advertising cookies are implemented here.
Flypark’s own JavaScript uses local storage for the optional checklist rather than a cookie. This implementation does not add analytics tags, ad trackers, pixels, newsletter tools, or booking widgets. However, a web host, CDN, browser, internet provider, font provider, image host, or linked site may process technical data or set their own cookies under their policies.
Host logs may exist. The host and retention period are not configured in this project, so Flypark does not claim that no personal information is collected or that no logs exist. A future publisher must identify the host, determine what log information is retained, define the retention period and security measures, and update this notice before launch.
Choices and questions
What visitors can control now.
Visitors can avoid using the checklist, reset its local state, block or clear browser storage, use browser privacy controls, and choose not to follow external links. Requests relating to information held by external providers should be directed to the relevant provider. Since the publisher identity and privacy mailbox are not configured, there is no active channel for privacy requests through Flypark. The future publisher must add accurate contact details and a process before public release.
Read About for the publication limits and Terms for informational-use conditions.