The Airport Board keeps its operational data collection narrow: enough to run the site, protect forms, understand real visits and measure partner-link activity, without requesting device GPS or a street address.
When a human-like browser enters the site, a server-side alert may include the landing page, referrer, IP address, browser/user-agent information, browser language, timezone, viewport and coarse location headers supplied by the hosting or CDN infrastructure.
The site does not request browser geolocation permission and does not collect device GPS coordinates. IP-based location is approximate and may be wrong.
Obvious crawlers, link previews, automated tools and repeated alerts from the same browser fingerprint are filtered so operational notifications are not flooded by machine traffic. A one-way fingerprint is used for duplicate control.
If you use the contact form, the name, reply email, topic and message you submit are sent to the site owner so the message can be answered. The destination mailbox is kept on the server and is not exposed in the page source.
A small first-party preference cookie can remember the language you chose. On a first visit to the home page, the site may use the browser's Accept-Language setting to open an available Spanish, Arabic, Portuguese or French version. Search-engine crawlers are not redirected this way.
When a visitor clicks a marked eSIM partner link, the site records the airport/page placement and may send the owner an operational click alert. Obvious bots and previews are filtered. Sponsored links remain separate from official airport sources.
If analytics is enabled, the site may use standard web analytics. The hosting provider may also maintain normal server access/security logs independently of The Airport Board's application-level visit alerts.
The visit-alert log written by the site does not store the raw IP address or the full user-agent string; it keeps a one-way visitor fingerprint plus basic operational fields such as time, page, approximate location if available and whether the alert email was sent. Contact rate-limiting stores a non-readable fingerprint rather than a raw IP address.
Questions about a message you sent or about this page can be submitted through Contact us.