Privacy Policy

Last Updated: October 9, 2026

At Booking Wolf, Inc., your privacy is important to us. This policy describes how we handle data across our services, with a specific section detailing the function of our Chrome Extension.

Privacy for the Booking Wolf Chrome Extension

This policy describes the data handling practices of the Booking Wolf Chrome Extension ("the Extension"). Our commitment is to provide our money-saving service transparently while protecting your privacy.

1. The Extension's Single Purpose

The Extension's single purpose is to get you a better price on travel bookings from supported third-party marketplaces (accommodation, activity and deals sites): either before you book, by sending the listing to our service, or after you book, by watching your existing hotel bookings for a cheaper identical stay if you switch Booking watch on (see section 2a). If you ask it to, it can also add one rule in your own Gmail, Outlook or iCloud settings so the booking sites' emails reach us too - that way bookings you make on your phone get watched as well (see Letting our extension set up the rule). It only activates on the specific list of marketplaces we support, and on your email's settings page only when you start that setup.

2. How and What Data is Used

The Extension's functionality and data usage differ based on the website you are on:

A) On Integrated Marketplaces (e.g., Booking.com, GetYourGuide):

The Extension injects a "Book with Booking Wolf" button onto listing pages.

When you click this button, the Extension reads non-personal page content (like the listing title and dates) to prepare your booking.

You are then redirected to our secure website in a new tab. It is on our website where you will voluntarily provide your personal information (name, email, phone) to finalize the booking. The extension itself does not handle your PII in this flow.

B) On Other Supported Marketplaces (e.g., TripAdvisor, Hostelworld):

A widget appears, allowing you to open our booking form. This form is loaded inside the extension's popup interface.

In this form, you will be asked to manually and voluntarily provide two types of information:

Non-Personal Booking Details: The name of the listing, dates, and price, which you copy from the webpage.

Personal Information: Your full name, email address, and phone number, which are required to process the booking.

C) Screenshot-Based Flow (RedBalloon, Viator, Hostelworld checkout pages):

On checkout pages for RedBalloon, Viator, and Hostelworld, you can click "Apply Your Discount" in our widget.

When you click this button, the extension captures a screenshot of the current page using Chrome's screenshot API. This screenshot is used to automatically extract your booking details (listing name, dates, guests, price) using AI technology.

The screenshot is sent securely to our servers, processed to extract booking information, and then used to pre-fill your booking form on our website. Screenshots are stored temporarily and deleted after processing.

This screenshot capture only occurs when you explicitly click the "Apply Your Discount" button - it does not happen automatically or without your action.

3. Summary of Personal Information We Collect

To process a booking request on your behalf, we require you to voluntarily submit the following Personally Identifiable Information (PII) through our secure booking form, which is presented either within the extension's popup interface or on our website:

Your Full Name
Your Email Address
Your Phone Number

This information is essential for the end-provider (e.g., the hotel or merchant) to create and confirm your reservation. In the booking flow the Extension never collects this PII from any webpage; it is only collected when you actively type it into our form and submit it. The one exception is Booking watch (section 2a), which reads your own booking pages only after you switch it on for a site.

2a. Booking watch (optional, off by default)

Booking watch looks after hotel stays you have already booked on other sites. It does nothing until you link the Extension to your Booking Wolf account and switch it on for a specific site (for example Agoda or Booking.com) in the Extension's settings. Then, while Chrome is open, about every 6 hours the Extension opens that site's "My trips" page in a background tab, using your own signed-in session on that site, and reads the text of your upcoming hotel bookings.

What is read and sent to us: the text of those booking pages - hotel name and address, dates, room, meal plan, guests, price paid, cancellation terms, the site's booking number and PIN, and the lead guest's name - plus the site's hotel identifier where the page contains one. It never reads your password, your payment card details, or any other website.

What we use it for: only to compare your booking with the same room through our suppliers and, if it is cheaper, to tell you and, with your permission, rebook it for you and, if you have allowed it, cancel the original. To cancel the original, the Extension opens that booking in a background tab in your session and follows the site's own cancel steps. Just before the final click it sends us the text of that booking's page and of the cancellation screen, so we can check it is the right booking (booking number, hotel, dates) and that cancelling is free; afterwards it sends the result page so we can check the booking shows as cancelled. Nothing is booked or charged without your approval of that rebooking, or an Autopilot permission you set up with your own limits; under Autopilot we notify you 12 hours before acting so you can stop it. Your original booking is only cancelled for you if you have given us the separate permission "After we rebook you, cancel my original booking for me while it's still free to cancel" (we keep a record of when you gave it, with your IP address and browser) or you ask us to cancel that booking; otherwise we email you a link to cancel it yourself.

Your control: switch any site off or disconnect the Extension from your account at any time in its settings; stored bookings are then no longer updated, and you can ask us to delete them at team@bookingwolf.com. Some booking sites' terms may not allow automated tools; Booking watch acts only on your instruction, in your own browser.

4. Data We Explicitly DO NOT Collect

The Booking Wolf Extension DOES NOT collect, read, or store:

Financial and Payment Information: The extension has no access to your credit card numbers or financial data.

Authentication Information: We do not access your passwords or credentials for any site.

Your email: when it sets up the email rule for you, the extension works in your email's settings pages, reading the text on screen only to find the right buttons (that can include the subject lines showing in your inbox behind the settings). It never opens or sends your emails, and nothing from those pages leaves your browser except your email address and Gmail's confirmation step (see below).

Broad Web History: The extension only checks the URL of your active tab to determine if it is a supported site. It does not log or transmit your browsing history.

5. Justification for Chrome Permissions

Host Permissions (e.g., *://*.booking.com/*): Required to display our discount button or widget on the specific marketplace websites we support.

<all_urls> Permission: Required for screenshot capture functionality. When you click "Apply Your Discount" on supported booking sites (RedBalloon, Viator, Hostelworld checkout pages), the extension captures a screenshot of your booking details using Chrome's chrome.tabs.captureVisibleTab() API. This API requires either <all_urls> permission or activeTab with a direct user gesture. We use <all_urls> to ensure reliable screenshot capture when you explicitly click our discount button. Screenshots are only captured when you click the button - we do not capture screenshots automatically or without your explicit action. The screenshot is processed to extract booking details (listing name, dates, price) and is sent securely to our servers to pre-fill your booking form. We do not store screenshots longer than necessary to process your booking request.

storage: Used to cache non-sensitive settings and to temporarily pass context (like a URL) between the extension's components.

tabs: Used to get the URL of the current active tab, to open our secure booking page in a new tab, and (Booking watch only) to open your trips page in a background tab.

alarms: Booking watch only - schedules the 6-hourly check and the check for pending cancellations while Chrome is open.

scripting: Booking watch only - reads the text of your trips and booking pages on sites you switched on, and clicks the site's own cancel steps when you approved a rebooking.

Optional site access (e.g. Agoda, Hotels.com, Trip.com): requested only when you switch Booking watch on for that site, and removable at any time in Chrome.

Optional email site access (mail.google.com, outlook.live.com, outlook.office.com, www.icloud.com): Chrome asks for the one you need only when you click "Yes, set it up" on our email-setup screen. It is used only to add the forwarding rule in a tab you can watch (scripting fills in the settings form there). You can remove it at any time in Chrome's extension settings; the rule stays until you delete it in your email.

6. Data Usage and Transfer

All personal and booking information you submit, and booking information read by Booking watch, is transmitted securely over HTTPS to our servers for the single purpose of getting you a better price on your booking and facilitating it with the relevant service provider. We do not sell or transfer your data to third parties for purposes unrelated to completing your booking, nor do we use it for lending or creditworthiness purposes.

Privacy for watching your hotel bookings (rebooking)

If you booked a hotel on Booking.com, Agoda, Expedia, Hotels.com or Trip.com, we can watch that booking and tell you if the same stay gets cheaper with us. Your bookings can reach us in three ways: by email, by our Chrome extension (section 2a above), or through Muse (below). You choose which, if any.

1. Sending us your booking emails

Where they go: booking emails sent to trips@reply.bookingwolf.com are received for us by our email provider, Brevo, and passed to our servers. You can forward one by hand, or set up a rule once in your email so new booking emails reach us by themselves: a forwarding filter in Gmail, a "Forward to" or "Redirect to" rule in Outlook, or a forwarding rule on iCloud.com. Our setup steps only forward emails from the booking sites' own booking sender addresses (in Gmail and Outlook, except emails whose subject is plainly about signing in, codes or passwords; iCloud rules can only match the sender), so the rest of your inbox never reaches us. Those addresses also send other mail, such as offers and account notices: it reaches us too and is thrown away unless it is a booking, as described below. We cannot see your inbox - only the emails that are sent to that address.

Gmail's confirmation step: when you add our address as a Gmail forwarding address, Google emails its confirmation code to us. If you are doing it yourself, we email that code and Google's own confirm link back to the Gmail address that asked for it, so you confirm it yourself. If you asked our Chrome extension to set it up (next section), we pass the code only to that extension, which types it into Gmail's own Verify box in your tab. Our servers never press Confirm for you.

Who the booking belongs to: we decide whose booking it is from the email address only. A hand forward belongs to the address you forwarded from; a Gmail or Outlook rule forward belongs to the mailbox that the forwarding headers name. An iCloud rule forward keeps the booking site as the sender, so we take the address the booking site emailed, and the first time we send that address a "Yes, it's mine" email. Until you tap it and sign in, the booking is held on a hidden placeholder and is not added to any account. If you didn't set up forwarding, you can ignore that email and nothing is added to any account. We don't reply to someone who forwards a booking that isn't theirs. If you forward from an address that has no Booking Wolf account, we keep the booking on a hidden placeholder linked to that address and email you a link to claim it into a free account.

Sign-in and code emails are thrown away first: the booking sites also send sign-in links, one-time codes, password resets, security alerts and offers from some of the same addresses. Every email that reaches that address is first checked automatically, by fixed text rules on its subject and text (no AI, no person). A sign-in, code, password or security email without clear booking details in it, and a promotion or newsletter with nothing about a booking in it, is dropped at once: it is not stored and not passed to the AI model, and our logs record only that an email was dropped, which kind, and the booking site's web address. If you forwarded it by hand, we email you a fixed reply saying so, which quotes nothing from it. An email that does mention a booking is read as usual, but any sign-in link or one-time code in it is blanked out before the AI model reads it, and an email the AI model finds no booking in is not stored.

What we read: the subject and text of the booking email (up to about 26,000 characters) are read by an AI model to pick out the booking details. The model is Alibaba Cloud's Qwen, with OpenAI as a backup if Qwen is unavailable. Email headers are used only to work out who forwarded the email and which booking site sent it; they are not sent to the AI model.

What we keep: only the booking details, not the email. Those are: hotel name, address, city and country, the booking site's hotel and booking numbers (and PIN, if the email shows one), dates, rooms, room and bed type, number of guests and children's ages, meal plan, extras, price paid and currency, whether it's refundable and until when, the lead guest's name, the link to manage the booking, and when we last saw it. We don't save the email's text or headers in our database.

What we ignore: automatic replies and bounces; emails we can't link to a person; promotions, newsletters and anything else that isn't a hotel booking, confirmation, change or cancellation from a supported site; and repeat deliveries of the same email. To prevent abuse, we stop reading emails from an address that sends us more than 20 an hour; the rate-limit counters (which use the sending address) are kept for up to a day by our rate-limiting provider, Upstash.

An email can't move money: nothing is booked or charged because of an email. A rebook needs your approval on our site with your card, or an Autopilot permission you set up. A forwarded email never counts as proof that your original booking was cancelled. A forwarded cancellation email for a booking we are rebooking is treated as you telling us "I've cancelled it", which stops our cancel reminders.

1b. Letting our extension set up the rule (optional)

What it changes: only after you say yes on a screen inside the extension (which lists exactly what it adds), it opens your own email settings in a tab you can see - you're already signed in there - and adds one rule: in Gmail, our address trips@reply.bookingwolf.com as a forwarding address plus one filter that forwards emails from the booking sites' exact confirmation sender addresses, except ones whose subject is plainly about signing in, codes or passwords; in Outlook.com or Microsoft 365, one rule named "Booking Wolf - hotel bookings" that forwards mail from the booking sites' own sender addresses, except emails whose subject is plainly about signing in, codes or passwords; in iCloud Mail, one rule per booking-site sender address, using the plain "Forward to" (never one that also deletes or marks mail as read). iCloud rules can only match the sender, so anything else those addresses send (for example a sign-in code) is also copied to us and then thrown away as described above. It never switches on Gmail's "forward a copy of all incoming mail": if Gmail switches it on when our address is added, the extension switches it back off and checks again, and if it can't confirm it is off it stops and tells you exactly how to turn it off. It only reports success after reading the saved filter or rule back. If anything on the page isn't what it expects (you're signed out, a different account is open, your email isn't in English, your work email blocks forwarding), it stops and shows you the steps to do it yourself, together with anything it had already changed and how to undo it.

What it reads in that tab: to find the right buttons and check the result, it reads the text of your email tab inside your browser. On Outlook and iCloud the settings open over your mailbox, so that text can include your message list (senders and subjects). It is used only inside your browser during the setup and is never sent to us.

What it sends us: before you say yes, only the part of your address after the @ (for example gmail.com), to look up which email service it is; after you say yes, the email address you typed and which email service it is, so we can link Gmail's confirmation code to your setup. We store that link under a one-way scrambled (hashed) version of the address, not the address itself, together with the setup's progress (started, done or stopped, and why), Gmail's confirmation code (it only works for that one confirmation), and your extension's hidden account id. We hand the code only to the extension install that started that setup, and we delete the code 15 minutes after it reaches us. If the setup stops after Gmail sent the code, we email the code to that Gmail address so you can finish it yourself.

"Where should we send your savings?": if you use the extension without a Booking Wolf account, it may ask for your email. We save it on the extension's hidden account and send that address one email with a confirm link. Nothing else is sent there until you tap it and sign in (or create your free account); your watched stays then move to that account.

How to undo: Gmail - Settings, Filters and Blocked Addresses, delete the filter (and remove our address under Forwarding and POP/IMAP). Outlook - Settings, Mail, Rules, delete "Booking Wolf - hotel bookings". iCloud Mail - Settings, Rules, delete the rules that forward to us. You can also remove the extension's email-site access in Chrome.

2. Reading your trips pages with our Chrome extension

Covered in section 2a above. In short: only for the sites you switch on, about every 6 hours while Chrome is open, in your own signed-in session. The extension sends us the text of that site's trips page and of your bookings' own pages, and we keep the same booking details as for emails (not the page text). Right after you book, it may ask "Want us to watch this one?" on the booking site's confirmation page; only if you tap it does it send us that page's text, read the same way.

3. Muse sync

If you connect Muse (see below) and ask it to check your bookings, Muse's own browser opens the booking sites' trips pages and sends us their text, which we read and keep in the same way. If Muse sends us a booking page to show that your original booking was cancelled, we use that text only to check the cancellation and keep only the result.

4. Permission to cancel your original booking for you

This is a separate permission, off unless you turn it on: "After we rebook you, cancel my original booking for me while it's still free to cancel." It only covers bookings we have rebooked for you. Our Chrome extension does it in your browser, and only after checking on the booking site that it's the right booking (booking number, hotel and dates) and that cancelling costs nothing. For that check it sends us the text of the booking page and of the final cancellation screen. An AI model (as in section 1) reads them, and we keep only the result of the check, not the text. When you turn the permission on or off, we keep a record of the exact wording you agreed to, when, from where (account page, rebooking page or the extension), your IP address and your browser. Without this permission, we email you a one-tap link to cancel the original yourself. You can also ask us to cancel one booking for you with "Cancel it for me now". Turn the permission off at any time in your Rebooking settings or in the extension's settings.

5. How long we keep it

Booking and price facts are kept. We use them to understand hotel prices and run our business (for example, how often a stay gets cheaper and by how much), so we don't delete them after a set time. When a stay is over or cancelled, we mark it inactive and stop watching it. We don't keep the emails themselves (see section 1).

While you have an account: your watched bookings stay on it with the details listed in section 1. A hidden placeholder for an address that forwarded bookings to us is kept too, so a later forward from that address joins the same booking.

When you delete your account: we remove everything that identifies you and keep only anonymous booking facts - hotel, city and country, dates, rooms, room and bed type, number of guests and children's ages, meal plan, extras, prices and currency, the booking site, any offer we made, and what happened (for example rebooked or cancelled). These are then linked only to a random id that is not connected to you. We remove: your name, email address and phone number; the lead guest's and other guests' names; booking numbers, PINs and manage-booking links; the hidden placeholder for your email address (including the forwarding address it holds) and hidden extension accounts linked to you; Gmail confirmation codes; your setup-reminder records; messages we exchanged about your bookings; the IP address and browser recorded with your permissions; your saved card (removed at our payment provider), Autopilot and cancel permissions; and connected apps such as Muse. Counts from our setup pages and of which way bookings reached us stay, without your account id.

An upcoming stay we booked for you: we keep the name and contact details on that booking until the day after check-out, so the hotel and we can still reach you about your stay. They are then removed in the same way, automatically.

Short-lived items, deleted on a schedule whether or not you delete your account: Gmail confirmation codes 15 minutes after they reach us, and our records of setup-link emails we sent (kept only as scrambled addresses, to limit how many we send) after 2 days. Rate-limit counters at Upstash expire within a day.

Your permission records are a log that can't be edited. They are deleted with your account; if your account can only be closed rather than fully deleted, the log stays without your IP address and browser. Payment records held by our payment provider, Stripe, are kept by Stripe under its own policy.

6. How to stop

Stop emails reaching us: delete the forwarding rule or filter in your email settings, or stop forwarding - also when our extension added it for you (section 1b). For Gmail, also remove trips@reply.bookingwolf.com under Forwarding.

Stop the extension: switch a site off, or disconnect the extension from your account in its settings. It stops reading; bookings already stored are kept until you ask us to delete them.

Stop Muse: disconnect Muse on your account page. Its access ends at once; bookings it already synced are kept until you ask us to delete them.

Remove a stay: there is no button for this yet. Email team@bookingwolf.com and we will delete it.

Delete everything: delete your account from your account page. Everything that identifies you is removed and only anonymous booking facts are kept (section 5). You can't delete it while a rebook is half-way through (for example while your original booking still needs cancelling); we tell you if so.

Measuring our setup pages: on our booking-watch setup pages we count which steps people reach and which email service they use (for example Gmail or Outlook), using a random id for that browser tab and, if you are signed in, your account id. To work out the service for your own domain, we look up only the part after the @. If you start the one-time setup for Gmail, Outlook or iCloud (or for Muse), we use that email address only to send you at most two reminders if the setup doesn't finish - one after about a day and one after about three days - each with a link to stop them. We stop as soon as a booking reaches us that way. That reminder record (with the address) is deleted when you delete your account.

Privacy for the Booking Wolf connector on Meta Muse

The Booking Wolf connector for Muse (mcp.bookingwolf.com/muse/mcp, documented at bookingwolf.com/muse-connector) lets you search, book and manage hotel stays from Muse.

Without an account: we receive only the search details you give (destination, dates, guests, currency) plus standard request data (IP address, headers, timestamps) for rate limiting and abuse prevention.

When you connect your Booking Wolf account: you sign in on bookingwolf.com and choose Read only (see your bookings and cancellation terms) or Book and cancel for me. Muse then receives your bookings' details (hotel, dates, room, status, confirmation number, amount paid, cancellation terms) and, for bookings you make, the guest names you provide. We never share your card details with Muse.

Bookings and cancellations: Muse asks you to approve every booking and every cancellation. A booking is charged to the card saved on your Booking Wolf account; your bank may ask you to confirm it on bookingwolf.com, where you sign in first. Your card details and payment secrets never pass through Muse.

Your control: disconnect Muse at any time from your Booking Wolf account page; its access ends immediately. Data is used only to provide the connector and your bookings: never sold, and never used for advertising, profiling or to train AI models. When you disconnect, unused price quotes Muse created are deleted, and quotes that were never booked are deleted after 30 days in any case; your bookings are kept for as long as needed for the bookings themselves and our legal records.

Privacy for AI Agent Access (ChatGPT App, Claude, Perplexity)

This section applies when Booking Wolf is accessed via an AI assistant such as ChatGPT, Claude, or Perplexity, through our Model Context Protocol (MCP) server. The MCP endpoint exposes a small, read-only surface used by AI agents to help users find and compare hotels.

1. What the AI Agent Surface Does

When an AI assistant queries Booking Wolf on your behalf, it can call three tools: search_hotels (returns hotels in a destination with their public prices), get_hotel_rates (returns rates for a specific hotel across major booking sites), and search_activities (returns tours and activities in a destination). All tools are read-only. They do not create bookings, charge payment methods, or modify any account data. To complete a booking, you visit booking-page deep links on bookingwolf.com - the same secure checkout used by all our customers.

2. Data We Receive From the AI Assistant

When you ask an AI assistant to search hotels via Booking Wolf, the assistant sends our MCP server only the search parameters you specify in that turn of conversation:

Destination (city or region name you typed, e.g. "Tokyo")
Check-in and check-out dates (when you provide them)
Number of adult guests (defaults to 2)
Display currency preference
A hotel identifier when comparing prices for one specific hotel

We receive the IP address of the AI assistant's request, standard HTTP request headers, and timestamps necessary for rate-limiting and abuse prevention. We do not receive your name, email, chat history, the rest of your conversation with the AI assistant, your account on the AI platform, your location beyond the destination you typed, or any payment data.

3. Data Returned to the AI Assistant

For each search we return public hotel data: hotel name, star rating, city, country, latitude/longitude, our published price for the dates you requested, the comparable Booking.com retail price when available, and a Booking Wolf booking-page URL. We do not return personal data of any kind in MCP responses.

4. Retention

Standard server logs for MCP requests (IP, timestamp, tool name, response status - used for rate limiting and operational diagnostics) are retained for 30 days and then deleted. We do not retain the content of search parameters or response payloads beyond what is needed to serve the immediate request.

5. Third-Party Recipients

To produce price comparisons we make server-to-server calls to our hotel-inventory providers and public OTA-pricing data sources. These calls contain only the destination, dates, and guest count you specified - never your personal data. The AI assistant platform (OpenAI, Anthropic, Perplexity) processes your conversation under its own privacy policy; please review the relevant assistant's policy alongside this one.

6. Your Controls

You can stop using the Booking Wolf assistant integration at any time by disabling or removing it inside your AI assistant's app/connector settings. Bookings already completed on bookingwolf.com are managed through the same booking confirmation channels documented in the General Privacy section below.

General Privacy for the Booking Wolf Service

The following sections apply to all our services, including data submitted through our website and the Extension. By using our services, you agree to the practices described below.

1. Information We Collect

We collect the following types of information to provide and improve our services:

1.1 Information You Provide Directly

Personal Information: Name, email address, phone number, and other contact details you provide during the booking process or when creating an account on our website.
Booking Request Details: The URL of the listing you submit from a third-party marketplace, relevant dates, number of travelers/participants, and any specific preferences related to that booking or deal.
Payment Information: Credit/debit card details and billing address, which are processed by our third-party payment processor (e.g., Stripe). We do not store your full payment card details on our servers.

1.2 Information Collected Automatically

Usage Data: Information about how you interact with our website, such as locations searched, marketplaces viewed, clicks, and time spent.
Device Information: IP address, browser type, and operating system.
Submitted URLs: We store the URLs you submit for booking requests to facilitate the booking and for analytical purposes.

1.3 Third-Party Information

We may receive information from the third-party marketplaces (e.g., Booking.com, GetYourGuide) or the ultimate service providers when we make a booking on your behalf. This information is typically limited to booking confirmation details.

2. How We Use Your Information

2.1 Service Delivery

To process your booking or deal requests using the URLs you provide.
To communicate with third-party marketplaces and service providers to make bookings on your behalf.
To provide you with booking confirmations and updates.

2.2 Customer Support

To respond to your inquiries and provide assistance.

2.3 Marketing and Communication

To send you updates, promotional offers, and other communications related to our services, if you opt-in. You can opt out of marketing communications at any time.

2.4 Service Improvement & Analytics

To analyze trends, usage patterns, and the popularity of different marketplaces and listings to improve our service.
To personalize your experience on our platform.

2.5 Compliance and Legal Obligations

To comply with applicable laws, regulations, and legal processes.

3. Sharing Your Information

We do not sell your personal information. However, we may share it with third parties in the following scenarios:

3.1 Marketplaces and Service Providers

With the specific third-party marketplace (e.g., Booking.com, Viator) from which you provided the URL, and with the ultimate service provider. This information is shared solely to facilitate and complete the booking you requested through our platform. The information shared will be what is necessary for them to process the booking (e.g., your name, contact details, booking dates, number of travelers).

3.2 Payment Processors

With payment gateways (e.g., Stripe) to process your transactions securely.

3.3 Legal and Regulatory Requirements

To comply with legal obligations, respond to lawful requests, or protect our rights and property.

4. How We Protect Your Information

We implement industry-standard security measures to protect your personal information, including:

Encryption of sensitive data (like payment information passed to our processor) during transmission.
Secure storage of your information.
Regular monitoring of our systems to prevent unauthorized access.

5. Your Rights

5.1 Access and Correction

You may request access to your personal information we hold and correct any inaccuracies.

5.2 Data Deletion

You can request the deletion of your personal information, subject to our need to retain certain information for legal, transactional, or contractual obligations.

5.3 Marketing Preferences

You may opt out of receiving marketing communications at any time by clicking the 'unsubscribe' link in our emails or by visiting our Contact Us page.

6. Cookies and Tracking Technologies

We use cookies and similar technologies to enhance your experience on our website. Cookies help us understand user behavior, remember your preferences (like recently searched locations), and improve our services. You can control cookie preferences through your browser settings. For more details, please see our Cookie Policy.

7. Data Retention

We retain your personal information only for as long as necessary to fulfill the purposes outlined in this policy, including providing our services, resolving disputes, enforcing our agreements, and as required by law.

8. International Data Transfers

If you are located outside the region where our servers are based, your information may be transferred and processed in a different country. We take appropriate safeguards to ensure your data remains protected during such transfers.

Our primary operations and servers are located in the United States. By using our services, you consent to the transfer of your information to the United States and other locations where we or our service providers operate.

9. Updates to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or legal requirements. The updated policy will be posted on our website with the effective date. We encourage you to review this policy periodically.

Contact Us

If you have any questions about this Privacy Policy, please contact us at:

Booking Wolf, Inc.
1111b South Governors Ave STE 37771
Dover, DE 19904, United States
For inquiries, please visit our Contact Us page.