StayPeek privacy policy
Effective date: 10 November 2026
StayPeek is a Chrome extension that marks booking.com and Airbnb search results and property pages with icons and a match score for the facilities you choose to track, lets you compare properties and search both sites from one page. Airbnb works only after you allow it. This policy explains what data the extension handles, where it goes and what you can do about it.
StayPeek has no account, no advertising and no analytics. It does not sell data and does not use it for anything other than the features described here.
StayPeek is developed by Alex Komendant, who is responsible for the data described here (the "controller" under the GDPR). Contact: support@pseudodevprod.com.
Data that stays in your browser
- Your settings: the facilities you track, their order and settings, your templates, card icon size, match score size, whether card icons and the match score are shown, interface language (a language, or the same as booking.com or Airbnb), whether "What's new" opens after an update and the on/off switch. These are saved in Chrome's synced storage. If you use Chrome sync, Google stores and syncs them across your Chrome profile under Google's privacy policy; StayPeek's developer never receives them except as described under "Feedback" below.
- Checked properties: what booking.com or Airbnb states about properties you check or whose page you open: name, location (Airbnb's is approximate), city and country code, the place label (Airbnb's, or booking.com's district and city), whether an Airbnb host is a private person or a business, star rating, review scores or rating, facilities (on Airbnb, amenities and safety items) and house rules, staff or host languages, room types or units (name, description, size, beds, capacity and facilities) and photo addresses with booking.com's captions and upload dates, plus when it was read. Kept on your device for up to 30 days (at most 500 properties), longer for properties saved in a compare list. "Clear cache" in StayPeek's settings removes them.
- Stay prices and availability: for a property or listing whose page you open with dates, or that you check or save from a search page (booking.com or Airbnb), not only those in a compare list: the room options for those dates and guests, with prices in the currency the site showed you (on booking.com including member prices), each offer's discounts (kind, amount and the site's label), the credit Airbnb pays back after a stay, Airbnb's offer of an extra night (the dates and the amount it adds), meal plans, cancellation and payment terms, room facilities, photo addresses, whether Airbnb flagged the listing as a "Rare find", and, for a property in a compare list, the last error when loading it failed. Up to 6 stays are kept per property: the ones your compare lists use, the newest and upcoming ones. Removed with its property (30 days, at most 500; longer for properties saved in a compare list). "Clear cache" removes them all.
- Check counters: the number of properties checked on booking.com and Airbnb since installation and how many checks failed, and whether you already answered the prompt asking you to rate StayPeek. Kept on your device.
- Compare lists: list names, each list's dates and guests (including how the guests are split into rooms, if you set that), and the properties saved in it, with the price the search result showed when you saved it and the room you picked. For each saved property: its name, location, photo and review scores, and its stay prices as described above. Kept on your device with no expiry. "Clear cache" deletes the loaded stay prices and keeps the lists with each property's name and location; removing a property from its last list, or deleting the list, leaves the property and its stay prices to expire like any checked property.
- Stay history: the last 20 upcoming stays you searched for on booking.com or Airbnb, on StayPeek's search page, or applied in the compare tab: dates, guests, number of rooms, how the guests are split into rooms (when set in compare) and the destination, which is the text you typed in booking.com's search, the place you searched on Airbnb, the destination on StayPeek's search page or, for a stay applied in compare, the city or country picked in the area filter. It may also keep booking.com's destination id and, for a place picked on the search page, its type, coordinates, map box and country. It is recorded on every search, even if you never use compare, and is kept on your device only; it is never sent anywhere. Past stays drop out automatically. "Clear cache" does not remove it; the × on an entry in the compare tab does.
- Search results: for the last 10 searches on StayPeek's "Search stays" page: the search (destination, dates, guests and children's ages, currency, filters and map area) and, for each site, the result cards as received: name, approximate location, photo addresses, price (and the site's own price when converted), rating, the site's labels, unit and space details, terms, credit, and whether the host is a business or a private person when the card says so (Airbnb's host line, which can name the host, is not kept). Searches whose check-in date has passed are dropped at the next save. Kept on your device only; never sent. "Clear cache" removes them.
- Search helpers: booking.com's map area for each destination you searched (the latest 50), the place and map area of the Airbnb search a listing was opened from (1 day, at most 50), whether Airbnb flagged a listing as a "Rare find" for your dates (1 day, at most 200), and until when StayPeek's requests to Airbnb are paused after Airbnb blocked them. Kept on your device only; never sent.
- Interface preferences: theme, whether booking.com follows it, zoom, which sections (such as the icon legend or compare rows) are expanded, whether the compare and search maps are open, where each is docked and its size, the map style and hidden map layers, the currency compare shows prices in, which search units and card footers are folded, your "prefer free cancellation / breakfast" choices, where the StayPeek tab sits on booking.com and Airbnb pages, which "Allow Airbnb" prompts on StayPeek's own pages you dismissed, the language each site last showed (such as "en-gb", so StayPeek can match it) and the text of an unsent feedback message and the topic you picked for it (not its images).
- Short-lived markers: whether booking.com or Airbnb asked StayPeek to slow down its requests, when you last pressed "Check for updates" and whether Chrome is in dark mode, as last reported by the popup or a page showing the StayPeek menu (for the toolbar icon). Cleared when Chrome closes. The compare tab also keeps the dates and guests it is showing until you close that tab.
- Dark mode style cache: style rules generated from booking.com's public stylesheets, so dark mode doesn't have to rebuild them on every page. No personal data; entries not used for 14 days are removed.
Requests to booking.com
To show facilities, StayPeek reads the booking.com pages you have open and, when you check a property or open its page, requests that property's page and facility list (in English) from booking.com. On a search page it also requests the same search with booking.com's pets filter applied. These requests go only to the booking.com address the page is on (www.booking.com, or another booking.com address such as sp.booking.com if you allowed it), the same as if you opened those pages yourself; property pages and the filtered search are requested with your normal booking.com session, the facility list without it. The one difference: the facility list is also requested from StayPeek's own pages (compare, search), and there StayPeek removes the request's "Origin" header (see Permissions), because booking.com rejects the extension's origin. When the facility list is requested from a booking.com page, StayPeek copies booking.com's own firewall token from that page's cookie into a request header, so booking.com's firewall lets it through; the token goes only to booking.com and is not stored, and the request still carries no cookies. booking.com handles these requests under its own privacy policy.
Compare lists request each saved property's page for the list's dates and guests (and the room you picked), one at a time and a few seconds apart, with your normal booking.com session. If you pick a currency in compare, StayPeek also requests, without your session, a booking.com search page for the list's city, dates and guests, only to read booking.com's exchange rate. If booking.com's bot check stops a request from the compare or search page, it is made from a booking.com tab instead: one you already have open, or a pinned, inactive tab on booking.com's home page that StayPeek opens, keeps for later requests and closes when the compare or search tab that opened it closes (or is left open if you switch to it yourself). Page requests then use that tab's session; the facility list, destination suggestions and rate pages carry that tab's firewall token instead of cookies. The compare and search pages show property photos from booking.com's image host (cf.bstatic.com). With dark mode on, StayPeek loads booking.com's public stylesheets from bstatic.com, without your session, to build its dark style rules. "Continue on booking.com" in compare and the cards on the search page open the property's booking.com page in a new tab.
StayPeek's "Search stays" page, only when you search, load more results or move its map, requests booking.com's search page for your destination, dates, guests, currency and filters with your normal booking.com session, one request at a time and a few seconds apart. More results and "Search this area" use booking.com's own paging query. If your signed-in session answers in another currency than you picked, an anonymous copy of the search is requested in the picked currency to read the exchange rate. If booking.com redirects the rate page requested for compare, it is requested once more by city name only. As you type a destination (2 characters or more, after a short pause), the text you typed is sent to booking.com for suggestions, without cookies; it is sent to booking.com only.
The compare and search pages' maps, only once you open one, load map tiles from StayPeek's own server (api.pseudodevprod.com/tiles, on Cloudflare), which fetches them from Protomaps with a server-side key, so Protomaps sees only that server and not you. Our server and Cloudflare see your IP address and the tiles requested, which is the map area you look at; the IP address is used only for a per-IP rate limit and is not stored by StayPeek's own code. Cloudflare, which runs our server, keeps request logs that may include the IP address and the tile requested, on Cloudflare's schedule, to operate and debug the service; StayPeek does not use them to identify anyone. The map's fonts and icons load directly from GitHub Pages (protomaps.github.io), which sees your IP address and the font and icon files requested. None of these requests carries anything about your lists, properties, searches or the sites. Map data © OpenStreetMap contributors.
Nothing read from booking.com is sent to StayPeek's developer.
Requests to Airbnb
StayPeek does nothing on Airbnb until you click "Allow" in StayPeek on an Airbnb page or on one of StayPeek's own pages (welcome, What's new, Search stays, compare), where you can also dismiss the prompt, and Chrome grants access to Airbnb's addresses (see Permissions). After that, StayPeek reads the Airbnb search and listing pages you open and makes the requests below. Each goes to the Airbnb address the page is on (www.airbnb.com when made from StayPeek's own pages), with your normal Airbnb session, the same as if you opened those pages yourself. If Airbnb answers with a block or a bot check, StayPeek stops all requests to Airbnb until the time Airbnb names (at least 30 minutes). Airbnb handles these requests under its own privacy policy. Nothing read from Airbnb is sent to StayPeek's developer.
- Reading pages: on Airbnb search and listing pages StayPeek reads the data the page already contains, with no request. A small StayPeek script, running in the page's own JavaScript world on Airbnb pages, copies the answers to the page's own stay-price requests to StayPeek, for the "Rare find" flag and the stay's price and terms. It sends no request of its own and leaves all other requests untouched.
- Checking a listing: when you check a listing on a search page, or open a listing whose page doesn't contain its data, StayPeek requests the listing page. One at a time, at least 2 seconds apart.
- Stay and price: for compare lists, when you save from a page or check a search card, StayPeek sends Airbnb's own page query for the listing, with the dates, the number of adults, children and infants (no ages, no pets) and the currency. It uses Airbnb's public web key, read from the page for each request and not stored.
- Search stays page: only when you search or load more, StayPeek requests Airbnb's search page for your destination, dates, guests, the map area (for a picked place, an area or a moved map), price range and filters, and the next-page position. The filters include room type (entire place or private room), amenities, accessibility features, self check-in and Luxe; they go only to Airbnb. No currency is sent, so your own Airbnb currency setting is left alone. Only the results embedded in the answer and the currency they are shown in are read. If that currency differs from the one you picked, or you set a price range, StayPeek requests, without your session, a booking.com search page (destination text, dates, guests) only to read booking.com's exchange rate, which it uses to convert the prices and the price range; the currency your Airbnb tab shows is read from the tab itself, with no request. One at a time, at least 5 seconds apart.
- An Airbnb tab: StayPeek's own pages (compare, search) can't call Airbnb directly, so the two requests above are made inside an Airbnb tab: one you already have open (StayPeek never closes or navigates it), or a pinned, inactive tab on www.airbnb.com that StayPeek opens, keeps for later requests and closes when the compare or search tab that opened it closes, unless you have switched to it yourself.
- Photos and links: the compare and search pages show listing photos from Airbnb's image host (muscache.com). "Continue on Airbnb" in compare and the cards on the search page open the listing in a new tab.
- Dark mode: StayPeek changes Airbnb's own theme settings in the page and adds a style. It makes no request and doesn't touch Airbnb's cookies.
Feedback
Data reaches the developer only when you submit the feedback form, opened from the StayPeek menu on booking.com or Airbnb, or from StayPeek's own pages. A message contains:
| Sent if you add it | Your message, a star rating, a reply email address, the address of the booking.com or Airbnb page you are on (only if you tick "Attach the page you're on"), and up to 3 images: files you attach, paste or drop, or screenshots of an area of the current tab that you select after accepting Chrome's "share this tab" prompt, with the file name of an attached file. Images are compressed on your device, with their metadata (such as camera location) removed, before sending. |
|---|---|
| Always sent with it | The topic you pick at the start of the form (bug, feature or other), extension version and build type, browser user agent (browser and operating system version), browser language, the list of facilities you track with their settings and the name of the matching template, and how many properties you have checked, how many checks failed and how many are cached |
Feedback is received by the developer's server on Cloudflare Workers, stored in a Cloudflare D1 database (images in Cloudflare R2 storage) and forwarded to the developer through a Telegram bot as a plain text message with the topic, rating, message, email, page address, template, facilities, counts, version, build type, language, browser, the number of images and private links to the images. The first image is shown as a link preview, so Telegram's servers fetch it themselves. The page address is cut to 300 characters in the Telegram message (the full address stays in the database). Your IP address is used only to limit how many messages can be sent per minute and to confirm the bot check below, and is not stored by StayPeek's own code. Cloudflare's own server logs, which may include the IP address, are not deleted by hand and expire on Cloudflare's schedule (see the map section above). The developer's code logs no IP address; it logs only errors, an unrecognised topic value and the daily message count. The data is used only to read and answer your feedback and to improve StayPeek, and is kept until you ask for it to be deleted or it is no longer needed for that.
To keep out automated spam, the feedback form runs Cloudflare Turnstile from the moment you pick a topic (at once for a saved draft that has one), whether or not you send anything. Turnstile collects your IP address and technical information about your browser and device to tell people from bots, under Cloudflare's Turnstile privacy addendum. It gives the form a single-use token that is sent with your message, and the developer's server checks that token with Cloudflare. The developer does not receive the information Turnstile collects.
Service providers involved: Cloudflare (hosting, storage, the Turnstile bot check and the map tile server), Protomaps (map tile data, fetched by our server; it receives no data about you), GitHub Pages (the map's fonts and icons, which you load directly) and Telegram (delivery to the developer). They may process the data outside your country; Cloudflare transfers data from the EU under the EU-U.S. Data Privacy Framework and the European Commission's standard contractual clauses. Feedback is sent over an encrypted (HTTPS) connection and is accessible only to the developer and these providers.
Other links StayPeek opens
- After you have checked enough properties, StayPeek may ask whether you'd like to rate it, at most twice, and not again once you choose to rate. Choosing to rate opens StayPeek's Chrome Web Store reviews page; a review you post there is handled by Google.
- "Check for updates" in StayPeek's settings asks Chrome's own extension update service for a newer version, the same request Chrome makes on its own every few hours.
Uninstall survey
When you uninstall StayPeek, Chrome opens a short optional survey (a Google Form) in a new tab, with the extension version and interface language filled in. Nothing is sent unless you submit the form. Answers are stored by Google under Google's privacy policy.
Legal basis
For people in the EU, EEA, UK and Switzerland, data is processed on these grounds:
- Your settings, checked properties, stay prices, compare lists and search results: they never leave your device or Chrome profile, and are kept only to provide the features you use.
- Requests to booking.com and Airbnb: started by your use of a page, of compare or of the search page (for Airbnb, only after you allow it) and sent to the site with your own session there, the same as browsing there. The destination text you type on the search page goes to booking.com for suggestions. The search filters you set, including accessibility needs, go only to Airbnb with your own session and are kept on your device. A page address you tick in Feedback is sent as it is, with any filters you set on that site.
- Feedback: your consent, given by sending it. You can withdraw it at any time by asking for your feedback to be deleted.
- Stay history, search helpers and map and layout settings: like your settings, they never leave your device or Chrome profile.
- Compare and search maps: a map is a feature you open yourself. Your IP address reaches Cloudflare (our tile server) and GitHub (fonts and icons), and our tile server uses it for a per-IP limit without storing it (Cloudflare keeps its request logs on its own schedule, as above). The developer's legitimate interest in showing the map you asked for and in keeping the tile server within its limits.
- IP address for the message limit and the bot check: the developer's legitimate interest in keeping the feedback service free of spam and abuse.
StayPeek makes no automated decisions about you and builds no profile of you.
Chrome Web Store User Data Policy
StayPeek's use of the data it handles complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used only to provide the features described here; it is not sold, not used or transferred for advertising, and not used or transferred to determine creditworthiness or for lending.
Permissions
- Storage (storage): to save your settings, checked properties, stay prices, compare lists and search results in your browser.
- Unlimited storage (unlimitedStorage): to keep that data on your device without Chrome's 10 MB limit.
- Scripting (scripting): to run StayPeek's own scripts on the booking.com addresses you allowed and, once you allow Airbnb, on Airbnb, and to make a compare or search request inside a booking.com or Airbnb tab when an extension page can't or a bot check stops it, and, after an update, to re-run the updated scripts in your open booking.com and Airbnb tabs (it checks only for StayPeek's own marker on the page). No remote code.
- Active tab (activeTab): to show the "Allow" prompt when you open StayPeek on a booking.com or Airbnb page it can't reach yet. The address of any other tab is never stored or sent.
- Page rules (declarativeContent): to show a "!" on StayPeek's toolbar icon on booking.com pages it can't reach yet and on Airbnb pages until you allow Airbnb; Chrome matches the page, StayPeek reads no tab address.
- Request rules (declarativeNetRequestWithHostAccess): one fixed rule that removes the "Origin" header, only from StayPeek's own requests to www.booking.com/dml/graphql (the facility list), because booking.com rejects the extension's origin there. It reads nothing and changes no other request.
- Access to www.booking.com (host permission): to show the icons on booking.com pages and request property details from booking.com.
- Access to other booking.com addresses (optional host permission): asked for only when you click "Allow" in StayPeek on a booking.com address such as sp.booking.com, used there the same way as on www.booking.com. You can remove it on StayPeek's details page in Chrome (Site access).
- Access to Airbnb addresses (71 optional host permissions: airbnb.com and Airbnb's country sites such as airbnb.de and airbnb.co.uk): asked for only when you click "Allow" in StayPeek on an Airbnb page or on StayPeek's own pages (welcome, What's new, Search stays, compare), one request covering all of them; Chrome shows no warning at install or update. Used to show the marks on Airbnb pages and for the requests under "Requests to Airbnb". You can remove it on StayPeek's details page in Chrome (Site access).
StayPeek runs on no site other than booking.com and, if you allow it, Airbnb.
Your choices and rights
- Clear checked properties, stay prices and search results at any time with "Clear cache" in StayPeek's settings. It leaves your stay history; remove entries with the × on each in the compare tab, or uninstall StayPeek.
- Delete a compare list, or remove a property from it, in StayPeek's compare tab.
- Take back StayPeek's access to Airbnb (or to other booking.com addresses) at any time in Chrome, on StayPeek's details page under Site access.
- Uninstalling StayPeek removes everything it stored on your device.
- For feedback you sent, you can ask for a copy, a correction or deletion, ask for its use to be restricted, or object to it, by writing to support@pseudodevprod.com. If you sent it without an email address, describe the message and when you sent it so it can be found. Requests are answered within one month. Deleting it removes the database entry, the images and the Telegram message; Cloudflare's own logs are not deleted by hand and expire on Cloudflare's schedule.
- You can also complain to the data protection authority where you live or work.
Children
StayPeek is not directed at children and does not knowingly collect their data.
Changes
If this policy changes, the new version is published on this page with a new effective date. Changes to what data StayPeek sends will be described here before they ship.
Contact
StayPeek is developed by Alex Komendant. support@pseudodevprod.com