This policy describes the site as built.
Parkgo is a static informational publication. It does not provide accounts, checkout, parking reservations, a newsletter, a message form, or a customer portal. It does not intentionally collect name, email, payment, license plate, flight, or other information through the website because no submission mechanism is implemented. The publisher identity and a privacy contact must be configured before publication; the visible email placeholder is not an active address.
This policy describes actual visible implementation, not a promise about every future host or integration. If a future publisher adds a form, analytics, advertising, affiliate links, booking functions, cookies, or another third-party service, the policy must be updated before that feature is used.
Third parties contacted by your browser.
Pages load Google Fonts from Google and Tailwind CSS from the Tailwind CDN. Pages also load remotely hosted editorial photographs from Pexels and Wikimedia Commons. When your browser requests those resources, those providers may receive technical information such as IP address, browser information, and the requesting page through normal web requests. Parkgo uses referrer policy controls on remote photographs and external links where implemented, but users should consult the third parties’ own policies for their practices.
External official airport and other source links lead to sites outside Parkgo. Those sites have their own privacy, cookie, security, and data practices. Parkgo does not control them and does not state that their policies apply here.
One optional local educational checklist.
Parkgo’s optional checklists store checked or unchecked state only in the browser’s local storage so the list can remain checked on that browser. This information is not sent to Parkgo by the checklist code. A visitor can clear the checklist with its visible control or through browser storage controls. The site does not implement analytics cookies, advertising cookies, newsletter cookies, or a consent-management platform.
The host or a CDN may use necessary technical mechanisms or logs according to its own configuration. The actual host, log fields, retention period, access controls, and legal basis are not configured in this publication. Parkgo therefore does not make the inaccurate blanket statement that no personal data is ever processed.
Server logs and retention are not configured here.
A compatible static host may log requests, errors, IP addresses, user-agent data, timestamps, or similar technical information in the ordinary operation of a website. This publication does not control or document a host’s actual logging configuration. Before launch, the publisher must identify the host, describe applicable log processing and retention accurately, and provide a real privacy contact and any notices required for the chosen hosting arrangement.
Reasonable technical safeguards are a hosting and publisher responsibility. No security claim can guarantee that internet transmission or a third-party service is risk-free. Do not transmit sensitive information to the unconfigured placeholder email address.
What to do before contact is configured.
Privacy rights and obligations can vary by location, publisher, host, and the data involved. Parkgo does not claim universal compliance with every U.S. or worldwide privacy law. If you have a concern about an external airport or parking operator, contact that organization directly. If you have a concern about this publication, the publisher must first configure a real privacy contact and update this policy.
Until then, the visible placeholder is [email protected] — Not configured — do not send messages to this address yet. The absence of a configured channel is intentional disclosure, not an invitation to send sensitive information elsewhere. See About for editorial limitations and Terms for the informational-use conditions.