This policy describes the static implementation of Airparks as delivered. Publisher identity, host selection, retention settings, and a working privacy contact must be completed before publication.
Privacy at a glance
Airparks does not implement analytics, advertising trackers, affiliate tracking, newsletter signup, accounts, bookings, payments, a contact form, or a database. The site contains static HTML, an inline mobile-navigation script, a Tailwind CSS CDN script, Google Fonts requests, and remote photo requests from Pexels. It also links to external websites.
Information that may be processed
Hosting and server logs
Any host that serves this website may process technical request data such as IP address, browser/user-agent information, requested URL, timestamp, referrer, and error information in server logs. The host, log fields, access controls, retention period, and purpose are not configured by this static site. The publisher must select and disclose the actual host and retention practice before publication. For that reason, this site does not claim that no personal data is collected.
Messages and forms
No contact form, newsletter form, account, comment system, booking form, or active mailbox is implemented. The displayed [email protected] address is explicitly unconfigured and must not be used until the publisher configures it. If the publisher later adds a form or mailbox, this policy must be updated with the data categories, recipient, legal basis where relevant, retention, and rights-contact information.
Third-party requests
Pages load Tailwind CSS from its CDN and request the Bitter and Nunito Sans font families from Google Fonts. Pages with editorial photos request images directly from Pexels. Those providers may receive technical request data necessary to deliver the resource. Remote photos include a no-referrer policy attribute where supported. The site does not configure analytics through these services.
External airport/operator and source links lead away from Airparks. The destination may have its own cookies, tracking, privacy policy, and terms. Airparks does not control those practices. Links use rel=noopener noreferrer and a no-referrer policy where implemented, but readers should review the destination’s own policy.
Cookies and local storage
This site does not set its own cookies or use local storage. Third-party resource providers or a host may use their own technical mechanisms; the actual publisher should verify the deployment before making a final statement about cookies.
Security, retention, and choices
Static delivery cannot guarantee security of networks, hosts, or external providers. The publisher must configure transport security and any operational safeguards through the chosen host. Because no publisher identity or privacy contact is configured, Airparks cannot currently process a privacy request. Before launch, the publisher must add a real contact route and explain which rights requests it can process under the laws that apply to its actual operations.
Changes and contact
This document describes the implementation checked October 15, 2026. It should be revised before publication if hosting, forms, analytics, advertising, booking links, fonts, images, or any other third-party service changes. Publisher identity and contact configuration are required before publication.