These MCP Service Data Processing Terms ("Data Processing Terms") describe how WPF Holdings LLC, doing business as Stayker ("Stayker," "we," "us," or "our"), collects, processes, stores, and protects data in connection with the Stayker MCP (Model Context Protocol) service ("MCP Service"). The MCP Service enables AI platforms and developer-built AI agents to search hotel inventory, retrieve rates, and initiate hotel bookings through Stayker's platform.
These Data Processing Terms supplement Stayker's general Privacy Policy and SaaS Terms of Service. In the event of a conflict between these Data Processing Terms and the general Privacy Policy or SaaS Terms of Service with respect to data processed through the MCP Service, these Data Processing Terms shall control.
By integrating with or using the Stayker MCP Service, you ("Developer" or "you") agree to these Data Processing Terms on behalf of yourself and your end users.
These Data Processing Terms cover every AI platform and LLM connector that uses the MCP Service. Where a platform completes bookings differently, a platform addendum at the end of these terms describes the differences. Addendum A covers the 1Stay integration for Muse.
"MCP Service" means the Stayker MCP server and associated APIs that enable AI platforms and agents to access Stayker's hotel search, rate retrieval, and booking initiation capabilities via the Model Context Protocol.
"Developer" means any individual or entity that integrates the Stayker MCP Service into an AI agent, application, or platform.
"End User" means any individual who interacts with a Developer's AI agent or application that uses the Stayker MCP Service.
"Search Data" means information submitted through MCP tool calls for the purpose of searching hotel inventory, including destination, check-in and check-out dates, number of guests, and geographic coordinates.
"Booking Data" means information associated with a hotel booking initiated through the MCP Service, including reservation details and the guest information collected on Stayker's secure checkout page. Booking Data does not include full payment card numbers or security codes (see Section 5).
"Personal Data" means any information that identifies or can be used to identify a natural person, including name, email address, and phone number.
"Travel Provider" means the third-party hotel, lodging provider, or booking fulfillment partner that provides the actual accommodation service.
When an AI agent calls the Stayker MCP search or rate tools, the following data may be transmitted to Stayker:
Search Data is transient. It is used solely to query hotel inventory in real time and is not stored beyond the duration of the API request, except in aggregated, anonymized form for service performance monitoring.
When an AI agent initiates secure checkout through the MCP Service, the booking tool may transmit:
The MCP booking tool does not accept the guest's name, email address, phone number, or payment card details. Guest identity details required to complete a new booking are collected only on Stayker's secure checkout page. Payment card details are entered in card fields on that page provided by Basis Theory, a payment card vault, and are submitted directly to Basis Theory (see Section 5).
For reservation lookup and support, MCP tool calls may transmit limited verification information such as the guest's name, email address, hotel confirmation number, payment card last four digits, and check-in date. Booking Data collected through checkout is stored by Stayker for the purpose of creating and managing the hotel reservation, communicating booking confirmations, and providing customer support. Booking Data may be shared with the applicable Travel Provider solely to fulfill the reservation.
Developers who register for the MCP Service provide account information including name, email address, organization name, and API credentials. This data is used to authenticate API requests, manage the Developer's account, and communicate service updates. Developers who subscribe to a paid plan enter their billing details on a Stripe-hosted checkout page; card details go directly to Stripe and never reach Stayker's servers.
Stayker automatically collects technical data associated with MCP Service requests, including API call timestamps, tool names invoked, response times, error codes, and IP addresses. This data is used for service monitoring, rate limiting, debugging, and security purposes.
Stayker processes data collected through the MCP Service for the following purposes only:
Stayker does not: (a) sell, rent, or lease any Personal Data; (b) use Personal Data for advertising, profiling, or marketing; (c) train machine learning models on Personal Data or End User queries; or (d) retain Search Data beyond the API request except in anonymized, aggregated form.
The MCP tools do not accept or store full payment card numbers or security codes. When a hotel reservation requires a payment guarantee or deposit, the guest enters card details on Stayker's secure checkout page in card fields provided by Basis Theory, a payment card vault. Card data is submitted directly to Basis Theory over an encrypted connection and never reaches Stayker's servers. Stayker receives only a token for the card, with the card brand and last four digits. Within Basis Theory's vault, the card number and expiry date (never the security code) are passed to the hotel solely to fulfill the reservation requirement. Stayker does not receive, store, log, or retain the full card number or security code. Stayker may retain the card's last four digits with the booking record and accept those last four digits through the MCP Service solely as a reservation-verification factor. Stayker is not the Merchant of Record for the stay — the hotel retains guest payment details and charges the room rate, taxes, and any hotel fees directly under the selected rate's terms. Some bookings include a 1Stay booking fee. When one applies, it is shown as its own line before the guest books, and it is charged by Stayker and processed through Stripe, separately from the hotel's charges.
Stayker shares data only in these limited circumstances:
Stayker does not share data with advertising networks, data brokers, or any other third parties for their own commercial purposes.
| Data Type | Retention Period |
|---|---|
| Search Data | Not retained beyond the API request. Anonymized metrics retained indefinitely. |
| Booking Data | Personal information (guest name, email, phone number) is retained for the duration of the reservation plus six (6) months after checkout, then permanently deleted. Anonymized booking records (dates, property, revenue metrics) may be retained indefinitely for reporting and compliance purposes. |
| Developer Account Data | Retained for the duration of the account plus 90 days after closure. |
| Technical and Usage Data | API logs retained for 90 days. Aggregated metrics retained indefinitely. |
Stayker implements industry-standard security measures to protect data processed through the MCP Service, including:
Stayker is based in the United States. Data processed through the MCP Service is stored and processed in the United States. For Developers or End Users located in the European Economic Area (EEA) or the United Kingdom, Stayker relies on Standard Contractual Clauses or other approved transfer mechanisms to ensure adequate protection of personal data transferred internationally.
End Users whose Personal Data is processed through the MCP Service may exercise the following rights, subject to applicable law:
Requests may be directed to service@stayker.com. Stayker will respond to verified requests within 30 days.
Developers integrating the Stayker MCP Service agree to:
Stayker receives only data explicitly passed through MCP tool calls. Stayker does not receive or access broader conversations between End Users and AI agents, conversation history, prompts, or any AI platform internal data. The scope of data received by Stayker is limited strictly to the parameters included in each MCP tool invocation.
Stayker uses the following categories of subprocessors in connection with the MCP Service:
A list of specific subprocessors is available upon request by contacting service@stayker.com.
In the event of a data breach affecting Personal Data processed through the MCP Service, Stayker will notify affected Developers within 72 hours of becoming aware of the breach. Notification will include a description of the nature of the breach, the categories and approximate number of data subjects affected, the likely consequences, and the measures taken or proposed to address the breach.
Stayker may update these Data Processing Terms from time to time. Updates will be posted at stayker.com/legal/mcp-policy. Material changes will be communicated to registered Developers via the email address on file. Continued use of the MCP Service after the effective date of any changes constitutes acceptance of the updated terms.
WPF Holdings LLC, d/b/a Stayker
Email: service@stayker.com
Phone: 704-686-8006
Mailing Address:
WPF Holdings, LLC
30 N Gould St STE N
Sheridan, Wyoming 82801
This addendum applies only to data processed through the 1Stay integration for Muse at https://mcp.stayker.com/mcp/muse. All other sections of these Data Processing Terms continue to apply. Where this addendum conflicts with them for data processed through Muse, this addendum controls.
The Muse endpoint is separate from the general developer MCP endpoint. It accepts connections without an API key and does not use OAuth. The reference to API key authentication in Section 8 does not apply to the Muse endpoint; all other Section 8 security measures do.
The categories are the same as in Section 3: Search Data, Booking and Reservation Support Data, and Technical and Usage Data. Search Data is transient and is not stored beyond the API request, except in anonymized, aggregated form for service performance monitoring.
In Muse, the booking and cancellation tools are each used in three steps: prepare, check status, and confirm the approved action. In addition to the items listed in Section 3.2, MCP tool calls through Muse may transmit a booking or cancellation session identifier, a verification token scoped to one booking, the approval summary, and an approval hash, which are used to confirm exactly what the user approved. The booking tool does not accept the guest's name, contact details, or payment card details as parameters.
For reservation lookup and support through Muse, only limited verification information may be transmitted, as described in Section 3.2.
For Muse, payment details are handled as follows, and this controls over Sections 3.2 and 5 where they differ. The guest enters their name and contact details on Stayker's secure form. The card fields on that form are provided by Basis Theory, a payment card vault, and card data is submitted directly to Basis Theory. It never reaches Stayker's servers or Muse. Stayker receives only a token for the card, with the card brand and last four digits, and never receives the full card number or security code. Card details are never typed in the conversation or sent as MCP tool parameters. Stayker may retain the last four digits with the booking record as a verification factor.
Within Basis Theory's vault, the card number and expiry date (never the security code) are passed to the hotel to guarantee the reservation, and, when the booking has a service fee, a Stripe payment token is created for it. Submitting the form does not book or charge anything. The guest then approves the final booking in the Muse conversation, and the reservation is created only after that approval.
The hotel is the Merchant of Record for the stay and charges the room rate, taxes, and any hotel fees directly, under the selected rate's guarantee, deposit, and cancellation terms. Some bookings have no service fee. When a booking has one, Stayker charges a separate 1Stay service fee, processed through Stripe. The fee is shown as its own line in the summary the user approves, is authorized before booking, is charged only after the hotel confirms the reservation, and is non-refundable once the booking is confirmed, except where required by law.
In Muse, cancellation is completed in the conversation. The guest's identity is verified first. The cancellation tool then shows a summary of the reservation, the hotel's recorded cancellation terms and deadline, and the email address that will receive the cancellation confirmation. The user must accept or deny every cancellation: the reservation is cancelled only after the user accepts that exact summary in Muse, and nothing is cancelled if they deny it. Stayker then sends one cancellation confirmation to the email on the booking. Cancellation terms, including any refund or penalty, are set by the hotel, and Stayker does not estimate them.
For Muse bookings, the subprocessors in Section 13 also include payment processing providers: Basis Theory, which vaults card data, and Stripe, which processes the 1Stay service fee.
Sections 4, 6, 7, 9, 10, 12, and 14 apply to data processed through Muse without change. In particular, Stayker does not sell Personal Data, use it for advertising or profiling, or train machine learning models on Personal Data or End User queries, and End Users may exercise the rights in Section 10 by contacting service@stayker.com.
© 2019–2026 WPF Holdings LLC, d/b/a Stayker. All Rights Reserved.