← StayPeek

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

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.

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

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:

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

StayPeek runs on no site other than booking.com and, if you allow it, Airbnb.

Your choices and rights

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