Pro Flight Search provides flight-disruption intelligence, flight search tools, optional airport watch email alerts, embeddable widgets, and a public remote MCP server. This policy explains what information we collect, why we use it, and how to contact us.
Last updated August 16, 2026
Short version: we do not sell personal information. We use hosting, security, analytics, email, and flight-search infrastructure to operate the service. The public MCP server is read-only and does not require an account or API key by default.
Who we are
Pro Flight Search operates the website at proflightsearch.com. Use of the service is governed by our Terms of Service. For privacy questions or data requests, contact hello@proflightsearch.com.
Information we collect
Website and API requests
When you visit the site or call the API/MCP endpoint, our hosting and security provider processes standard request data such as IP address, headers, user agent, requested URL, timestamps, and security signals. We use this to serve pages, prevent abuse, cache responses, and keep the service reliable.
Product analytics
We record first-party usage events such as page views, search outcomes, route IATA codes, broad country, browser family, referrer domain, share/book clicks, and performance timings. We do not intentionally store IP addresses, full user-agent strings, or session IDs in these product analytics payloads.
Page recordings and heatmaps
We use Microsoft Clarity to see how pages are used, which records interactions such as clicks, scrolling, mouse movement, and a copy of the page layout, along with technical details such as browser, screen size, and approximate location derived from IP address. It runs in cookieless mode, so it sets no cookies and does not join this page view to your other visits. Anything you type into a search box or form field is masked before it leaves your browser and is never uploaded. If you would rather not be included at all, block clarity.ms in your browser or with a content blocker.
Searches
If you use flight search, we process the route, dates, currency, and search prompt you submit. Search prompts may be stored in truncated form to debug parsing.
Email, feedback, and contact
If you subscribe to airport watch alerts, submit feedback, or email us, we collect the information you provide, such as email address, message text, selected airports or cadence, confirmation and manage tokens, broad country, and limited delivery metadata needed to send and manage email. Legacy forecast-digest subscribers may still use unsubscribe or manage links from earlier messages; we retain only what is needed to honor those requests and do not send new forecast digests.
How we use information
- Provide the service: return airport delay data, weather-risk data, flight-search results, MCP tool responses, and embeds.
- Operate and secure the site: detect bots, troubleshoot errors, rate-limit public APIs where appropriate, cache content, and protect infrastructure.
- Improve the product: understand which pages, routes, airports, and tools are useful; diagnose failed searches; and prioritize fixes.
- Send requested email: confirm airport watch subscriptions, deliver watch alerts when thresholds are met, process unsubscribe and manage requests, and respond to messages.
- Comply with obligations: maintain records needed for security, abuse prevention, and legal requests.
MCP server privacy
The remote MCP server at https://proflightsearch.com/mcp is public and read-only by default. It currently answers airport-level delay questions. We do not require user accounts for the MCP endpoint. Requests may still be processed in hosting/security logs, and tool arguments such as airport codes, city names, or airport names are processed to return the requested response.
Processors and sharing
We use service providers to operate Pro Flight Search. Depending on the feature, these may include:
- Hetzner: application hosting on our dedicated server in Germany.
- bunny.net: CDN, edge security, and DNS.
- SMTP provider: outbound email delivery for airport watch alerts and contact replies.
- Eurolytics: privacy-focused analytics and AI/bot crawler measurement.
- Microsoft Clarity: cookieless page recordings and heatmaps used to find broken or confusing pages.
- Flight, aviation, weather, and data providers: route/date/airport parameters needed to return search results or disruption intelligence. We do not send passenger names or payment details because Pro Flight Search does not collect them.
- Email tooling: email delivery, unsubscribe handling, airport watch notifications, and legacy forecast list suppression.
We do not sell personal information and do not use it for cross-context behavioral advertising.
Retention
- Airport watch subscription records are kept until you unsubscribe or ask us to delete them, with limited status history so unsubscribe and suppression requests continue to work.
- Legacy forecast-digest subscription records are kept only as long as needed to honor unsubscribe, manage, and suppression requests from earlier digests. No new forecast emails are sent.
- Feedback and contact messages are kept as long as reasonably needed to review, respond, and maintain an audit trail.
- Analytics and security logs are retained according to our operational needs and provider retention settings.
Your choices and rights
- You can unsubscribe from airport watch emails or legacy forecast lists using the link in any message we sent for that subscription.
- You can avoid putting personal information in search prompts, MCP tool arguments, or feedback fields unless it is needed.
- Depending on where you live, you may have rights to access, correct, delete, restrict, or object to certain processing of your personal information.
- To make a privacy request, email hello@proflightsearch.com. We may need to verify that the request relates to you before acting on it.
International processing
Pro Flight Search is operated on cloud infrastructure and may process information in countries other than where you live. Where required, we rely on appropriate safeguards from our service providers for international transfers.
Changes
We may update this policy when the product, providers, or legal requirements change. The updated date at the top of the page shows when this page was last revised.