Skiplagged Travel Search Privacy Notice

Last updated: July 20, 2026

This notice describes data processing by the Skiplagged Travel Search MCP service at mcp.skiplagged.com. It supplements the Skiplagged Privacy Policy.

Data processed

• Travel-search inputs needed for the request, such as locations, dates and times, passenger or room counts, search filters, and a selected hotel identifier.
• Support questions submitted to the FAQ search tool.
• Optional coarse location metadata supplied by the client, used only to suggest a nearby origin airport. The location tool takes no user-provided coordinates.
• Limited technical data processed by hosting, security, and monitoring systems, such as IP address, user agent, route, error, and performance information.

The MCP service does not require an account and does not request names, email addresses, payment details, conversation history, account identifiers, session identifiers, request identifiers, or telemetry as tool inputs.

How data is used and shared

Travel-search inputs are sent to Skiplagged systems to return requested travel results and links. Skiplagged and relevant travel-service providers process those requests as described in the Skiplagged Privacy Policy.

FAQ question text is sent to OpenAI to create a search embedding; the embedding is compared with support content stored in Supabase. Sentry processes limited error and performance data with default collection of personally identifiable information disabled. Hosting and security providers process technical request data to operate and protect the service. Data may also be disclosed when required by law.

Tool responses

Responses contain requested travel results, support content, or a resolved city, country, and airport code. They do not include user coordinates, personal identifiers, ChatGPT conversation history, session or request identifiers, or telemetry.

Storage and retention

The MCP application does not intentionally persist tool arguments, coarse location metadata, or tool responses in its own application database. Operational logs and monitoring events are retained only as needed for security, reliability, legal obligations, and internal retention schedules, then deleted or anonymized. Other processors apply their own retention practices as described in their privacy terms.

Choices and contact

You can avoid coarse-location processing by providing a city or airport instead. You can disconnect or disable the service in your AI client at any time. For privacy requests or questions, contact [email protected]. Additional rights and contact details are in the Skiplagged Privacy Policy.