Privacy Policy

1. Information we collect

What we collect depends on how you use Brek.

• Hosts and their teams. Your name, email address and sign-in details (email links or Google sign-in); your business details; the homes you list, including descriptions, photos, prices, house rules, location and availability; data from the property management systems and calendars you connect; and payout and billing details, which Stripe collects for us.
• Travelers using stay-search or booking services. For services that support these features, an AI assistant sends us search details such as destination, dates, number of guests and preferences. When you book or ask a host a question through Brek, we collect your name, email address, phone number if you provide it, trip details and your message. The Direct Booking Finder MCP connector processes lookup and, when enabled, destination-search inputs as described in the next section. A direct booking request also collects the contact and trip details you submit with consent.
• Automatically. Basic device and usage information, such as IP address, browser type, pages visited and timestamps, and the cookies and analytics described below.

2. Direct Booking Finder MCP connector

This section applies to Brek — Direct Booking Finder in ChatGPT, Claude and other compatible AI assistants. Its lookup_direct_booking tool finds existing property-manager booking links for a specific Airbnb listing. When enabled, search_vacation_rentals searches vacation homes using your destination, dates and guest counts and returns source-platform prices. Neither tool creates reservations or processes payments; mapped direct links are not direct-price quotes.

• Lookup inputs. We receive one to ten Airbnb listing URLs or listing IDs selected for the tool call. We may also receive an optional language preference (locale), currency and pagination settings (limit and offset). A submitted URL includes any query parameters it contains; only its listing ID is used to match the property.
• Destination-search inputs. When destination search is enabled, we receive the destination, travel dates, adults, children, pets, optional currency and traveler language, property types, amenities, sort and pagination settings. We send the details needed for the search to our rental-search backend and geocoding providers. Search results are cached for two minutes, and trip-specific listing and price snapshots for 15 minutes. Stay dates remain calendar dates at the destination. We do not use traveler time zones. ChatGPT locale and country hints can select default language and currency; raw location metadata is not stored in admin activity.
• Connection information. Our service receives the connecting client’s IP address, user-agent and protocol headers, and the assistant channel, such as ChatGPT or Claude. The connecting IP may belong to the AI provider rather than your device. We use this information to route requests, limit request rates and protect the service against abuse.
• How inputs are used. We validate the listing reference and query Brek’s existing mapping database. We return the submitted reference, whether a mapped link was found, booking URLs, a Brek room-page link for valid Airbnb IDs and, when available, property names, image links and pagination information to your AI assistant. The lookup does not fetch the Airbnb listing or contact the property manager, and does not send your lookup inputs to an AI model or embedding service.
• Operational records. Our application records the assistant channel, request time and duration, counts of matched or unmatched listings, and error categories to measure reliability and diagnose problems. Admin activity records also include normalized listing IDs and, for destination search, the destination, travel dates, guest counts, currency, supplied traveler language, property types and amenities sent to the tool. Raw listing URL query parameters, raw IP addresses and conversation text are not added to these activity records. For rate limiting, we store counters keyed by a pseudonymous identifier derived from the connecting IP; the identifier changes each day.
• Information the connector does not request. No Brek or Airbnb sign-in is required. The tool does not request your name, email, payment details, account credentials, full conversation history, local files or access to a property-management-system account. Brek receives the tool inputs your assistant sends, rather than automatic access to the rest of your chat. The assistant’s handling of chats and its choice of tool inputs are governed by its provider’s policies and your settings.

Service providers and external links. Our hosting and database providers, including Porter, Vercel and MongoDB, process the information needed to serve requests and display results. Infrastructure and error logs may contain technical request metadata and diagnostic information separately from the lookup outcome records described above. A lookup does not send your request to a host as an inquiry or booking. If you open a returned booking link, the destination website receives that visit and handles information you provide under its own privacy policy.

Storage and retention. Normalized tool-call and direct-booking click activity is stored for up to 90 days for the staff dashboard. Direct-click records include the listing ID, destination domain and entry point. Booking-request contact and trip details are stored so the Brek team can follow up. Submitting a lookup does not add your listing to the mapping database. Rate-limit counters use one-minute windows and are marked to expire one minute after the window ends, normally one to two minutes after creation. Database cleanup runs in the background, so physical deletion may occur later. Hosting access and diagnostic logs have separate retention settings managed by the infrastructure providers; the counter expiry is not a deletion deadline for those logs or for your AI provider’s chat history.

Your choices. You can choose which listing references to share and stop using or disconnect the connector in your AI assistant. For questions about this connector’s data handling, or to request access, correction or deletion of personal information we hold, email leo@pageonelab.com. We may need additional information to identify a relevant record because the public lookup does not create a user account. General privacy rights and contact options also appear below.

3. BrekDB — public direct booking database

You can look up an Airbnb listing without signing in. If you contribute a link, we save the Airbnb listing ID, the direct booking URL, your stated connection to the property and any note you provide. An essential cookie keeps your saved submission available for seven days while you complete sign-in.

Google sign-in connects an activated submission to your Brek account. After review, the listing ID and booking URL can appear in BrekDB and in responses to AI agents using Brek. Your email address, Google identity and private submission or review notes are not included in public mapping results.

Unactivated drafts expire after seven days. We retain activated submissions and review history to maintain the database. Contact us using the privacy choices below to request a correction or removal. Database queries and outbound clicks use the normalized operational records described above.

4. How we use information

• To run the feature you use: look up mapped direct-booking links, publish listings to AI assistants, or, for services that support them, answer travelers’ questions, check availability, quote prices and process bookings.
• To send sign-in links or codes, booking-request follow-ups, booking confirmations and other messages about your account or trip.
• To keep the Services secure, prevent fraud and enforce our Terms.
• To understand how the Services are used and improve them.
• To meet our legal obligations.

Some Brek services use AI models to write and check listing content and to answer travelers’ questions. The Direct Booking Finder lookup uses the existing mapping database, without sending its inputs to these models. We don’t sell personal information, and we don’t use it for third-party advertising.

5. How we share information

• With hosts. When you submit a direct booking request, book or ask a question, we share the details with the host and, if they use one, their property management system, so they can host your stay. Hosts handle that information as independent businesses under their own policies.
• With AI assistants. Listing information is published to AI assistants, and our answers to your searches go back to the assistant you’re using. Your use of an assistant is governed by its provider’s privacy policy.
• With service providers that process data for the features you use: Porter, Vercel and other cloud providers (hosting and storage), MongoDB (database), Stripe (payments), Resend (email), Google (sign-in, if you choose it), Anthropic and Voyage AI (AI models), and Mapbox or OpenStreetMap (maps). Not every provider receives data from every feature; the Direct Booking Finder lookup does not use payments, sign-in, AI-model or map services.
• For legal reasons, when the law requires it or to protect the rights, safety and property of our users, the public or Brek.
• In a business transfer, such as a merger or acquisition, under the protections of this policy.

6. Payments

Hosts are the merchant of record for their bookings. Payments go to the host through Stripe, which handles card details under its own privacy policy. Brek never sees or stores full card numbers.

7. Cookies and website analytics

We use essential cookies to keep you signed in, remember your workspace and protect sign-in. We also use first-party identifiers to understand which campaigns bring visitors to BrekDB and whether they submit, activate or receive approval for a link. Campaign activity is retained for up to 90 days. The attribution cookie lasts 30 days and the visitor identifier lasts one year.

We use PostHog in the United States for public-website analytics and session replay. Replay helps us see how visitors use pages and diagnose usability problems. Form inputs are masked; admin, account, authentication and checkout pages are excluded. Our analytics integration does not send submitted booking links, form notes, emails or sign-in codes as event properties. Recordings are retained for 30 days. Enabling your browser’s Do Not Track or Global Privacy Control signal disables PostHog capture and recording; first-party campaign counts remain separate.

8. How long we keep information

We keep account and listing information while your account is active. We keep booking records as long as needed to support the stay and meet legal, tax and accounting requirements, then delete or anonymize them. Hosts can remove homes or close their account at any time.

9. Security

We protect information with encryption in transit, restricted access and encryption of sensitive fields such as phone numbers. No system is perfectly secure, so contact us right away if you think your account has been compromised.

10. Your rights and choices

You can ask to access, correct, export or delete your personal information, and to limit or object to certain uses. Depending on where you live, for example in the EU, the UK or California, local law may give you additional rights. Email hello@brek.ai to make a request. We’ll respond within the time the law requires, and we won’t treat you differently for exercising your rights.

If you booked a stay, the host also holds your booking details, and you can contact them about their copy.

11. International transfers

We’re based in the United States and work as a distributed team, so your information may be processed in the United States and other countries. Where the law requires it, we protect transfers with safeguards such as the European Commission’s Standard Contractual Clauses.

12. Children

The Services aren’t directed to children under 16, and we don’t knowingly collect their personal information. You must be 18 or older to book a stay or create a host account.

13. Changes to this policy

We may update this policy. We’ll post changes on this page with a new date and, for significant changes, let hosts know by email.

14. Contact us

PageOne Lab, Inc.
500 108th Ave NE, Suite 1100
Bellevue, WA 98004, USA
hello@brek.ai