BedsEye (“the extension”) is a Chrome extension that shows availability from iCal (.ics) calendar feeds you choose to connect. This policy describes what information the extension handles and how it is used.
You may add one or more calendar feed URLs (for example from Airbnb, Booking.com, Vrbo,
NightsBridge, Google Calendar export links, or other platforms), optional labels, and
which feeds are enabled. This information is saved in chrome.storage.local on
your device so the extension can show your calendars on later visits.
When you connect or refresh a feed, the extension’s background service worker sends a request to the URL you provided and downloads the iCal file as text. The extension parses that text (for example reservation dates with check-in and check-out) to display blocked and open days in the popup. Parsed events may be cached locally to improve load time. Content of iCal files is determined by your booking platform, not by BedsEye.
The extension uses optional host permissions. When you connect or refresh a calendar, Chrome may ask you to allow access to that feed’s website host so the extension can download the iCal file. Requests are limited to URLs you saved. The extension does not read or change ordinary web pages you browse.
All extension code is included in the package installed from the Chrome Web Store. The extension does not download or execute remote JavaScript. iCal downloads are data only, parsed locally.
If you select dates and use copy actions in the popup, availability text is copied to your clipboard only when you choose to do so.
The extension does not send your calendar URLs, events, or usage to a server operated by the extension developer for analytics, marketing, or profiling. We do not require you to create an account to use the extension.
If you choose to upgrade to BedsEye Pro, the extension may open our hosted page at
pro.html on the same site as this policy. If you submit the founding-cohort
or early-bird form, your email is included only in a message you send to us (for example
via your email app through a mailto: link). We use that contact to respond
with billing or license-key information. The extension validates a license key locally;
it does not call a separate activation API.
Distribution and updates are handled through the Google Chrome Web Store. Google’s own privacy practices apply to the store and browser separately from this policy.
We may update this policy from time to time. The “Last updated” date at the top will change when we do. Continued use of the extension after changes means you accept the updated policy.
For privacy questions about BedsEye, contact the developer via the support channel listed on the extension’s Chrome Web Store listing, or email: anton@stayhere.co.za.