Privacy

Looking up a terminal does not need an account. A request stores what you type, and only after you consent.

This page covers the public index, the MCP server at /api/mcp, and the request forms. It was written on 14 October 2026.

What an MCP search stores

search_services, get_service, list_airports and compare_services are read-only. A call is logged as the tool name, the time, and a coarse client label such as claude, cursor, chatgpt, vscode, or other. The log has no name, no email, and no text of the search. The raw user-agent string is not stored. These MCP search tools log no personal data.

Arrangement requests

On a terminal page that offers it, and through the MCP tool request_arrangement, the form asks for a name, an email, a travel date, an airport, the number of passengers, and notes. An explicit consent checkbox is required. Without that consent, nothing is stored.

The purpose is to ask the operator about availability and a price, and to write back by email. This is a request, not a booking. No payment is taken. The request is for the terminal only and must not be packaged with a flight sale. The record includes the time consent was given, and the reply includes a reference.

Desk requests

When Desk is open, the request-access form asks for a name, an email, an organisation, and notes, plus consent of the same kind. The purpose is to reply about access. No payment is taken, and there is no checkout.

A Desk key can register watch_changes with an email address or a webhook URL, so an alert can be sent when a price, an opening, or a closure changes. The event log records that a watcher exists. It does not record the address.

Contact and the Briefing

The contact form takes a name, an email, and a message, so we can reply. The Briefing in the footer takes an email address, so we can write when a price changes or a terminal opens.

Purpose

A request is used to answer it. The consent record shows that you asked us to store those details and to email you about them. Tool-call and click counts show which tools and outbound links are used. They are not used to build an advertising profile.

Retention

Arrangement records, Desk-access records, and watcher records are kept so we can reply and so the consent stays with the request. The software has no automatic deletion date. Ask through the contact page and we will delete the copy we hold.

Tool-call and click logs contain no name and no email. They stay with the hosting logs. Vercel’s request logs may include an IP address. The Planeside event log does not. A rate limit holds an IP address in memory for the length of the limit, and then drops it.

Processors

Vercel hosts the site, the API, and the stored records.

Resend sends a notification email to Planeside when that email is switched on. The request is stored whether or not the email is sent. Resend receives nothing while the email is off.

Web3Forms relays the contact form and the Briefing to the Planeside inbox.

No sale of data

We do not sell personal data. An arrangement is not passed to an airline, and it is not sold.

Contact

Questions, corrections, and deletion requests go through the contact page, or on Telegram to the Planeside bot.

← All terminals