Privacy at Georgian Stays.
Browsing Georgian Stays does not require an account. Personal information is mainly provided voluntarily through property claims or correction reports; limited technical, affiliate and optional directory-usage data is described below.
Information processed when you visit
Infrastructure serving and securing the site can process technical request information such as IP address, browser information, requested URL, timestamps and diagnostic logs.
Claims and correction reports
Owner claims can include a name, email, phone number, relationship to the property, evidence URL and message. Correction reports can include an optional email, evidence URL and explanation. These submissions are stored privately for review and are not published automatically.
Property information
Accommodation information can come from property websites, booking and review services, map data and other public sources. We use it to help travelers compare places to stay and reach the relevant property or booking page.
Affiliate measurement
Some travel links can be routed through affiliate networks such as CJ Affiliate or Impact before reaching the travel provider. For Booking.com, an eligible link may pass through CJ so the network can attribute a completed booking to Georgian Stays. Travel links created by the site can also carry provider, product and placement labels so a configured first-party analytics endpoint can distinguish, for example, a property booking exit from a car, transfer or experience partner exit. Affiliate networks and participating travel providers may process browser, device and interaction information for attribution according to their own privacy practices.
External sites
Property pages may link to official websites, map services, rating providers and property sources. Those services have their own privacy practices and operate independently from Georgian Stays.
Behavior analytics
The site includes a provider-neutral event layer for limited product analytics such as property impressions and property clicks, booking exits, configured car, transfer or experience partner exits, filter use and directory searches. When an event is emitted it includes the event name, current page path without the query string, and a timestamp. Property clicks can include page-placement context, such as whether the click came from a guide. Partner and booking events can include the provider, product, placement, outbound host and the relevant property or guide slug; they do not include the full outbound URL. If a directory list/map switch is explicitly instrumented, the selected view can also be recorded. The event layer does not create or store a visitor or user ID, IP address, cookie value, contact data, claim/correction form contents, arbitrary form contents or full referrers. For directory searches, the search text is read in the browser only long enough to classify it into a coarse word-count bucket (one word, two to three words, or four or more words); only that bucket is eligible for storage and the raw search text is never included. Directory filter events can include the selected region, destination, stay type and sort value. Event properties are restricted to a small per-event allowlist and are accepted only by a same-origin endpoint. If that endpoint is not configured, the event layer remains local to the browser.
Embedded maps
Map view is loaded only when you open it. The embedded OpenStreetMap frame then makes a direct request to OpenStreetMap, which necessarily exposes ordinary connection information such as your IP address and browser user-agent to that service. The map frame is configured not to send this page as the HTTP referrer.
Changes
This notice will be updated if we add accounts, broader consent-based analytics, newsletters, payments or other features that materially change how visitor data is handled.