Privacy notice
Automatic cookie-free counts
We count public HTML page requests served by this website and requests to its booking redirects automatically on the server. These basic counts do not use analytics cookies, browser storage, persistent visitor identifiers or a reference that follows a click to another website. Refreshing a page may add a view. A booking-redirect request is an intention to open the partner's page, not a completed booking. Known bots are filtered imperfectly, and basic counts do not identify unique people or sessions.
Optional visit insights
You can separately allow first-party cookies for optional insights into which pages were viewed together, when activity happened, approximate visible page time and visit engagement. Allow and Reject are offered together; either choice leaves basic cookie-free counts running. No cookie for these insights is set before an explicit choice. The server then remembers your Allow or Reject preference for six months. An optional visit cookie is created only after Allow and is HttpOnly, so website JavaScript cannot read its identifier.
A visit ends after 30 minutes without recorded activity and has a maximum lifetime of 24 hours. With optional insights allowed, this page sends its server-issued page reference and cumulative time while the tab is visible. Hidden-tab time is excluded; visible time is capped at two hours per page and is not proof of attention. Browser Do Not Track or Global Privacy Control signals keep optional measurement off. They do not switch off the separate basic counts.
Use Cookie settings in the footer to change your choice. Rejecting after Allow stops further optional signals and clears the optional visit cookie. The service also removes the current optional visit when storage is available; if that removal fails, the settings notice explains the retained record and its expiry. A Reject preference can remain so the site remembers your choice. This does not delete basic aggregate counts or records held separately by a booking provider.
Duration, engagement and bounce
Optional visit insights describe only visits where measurement was allowed. Observed visit span and measured visible time are different estimates. A visit is engaged when it has at least two page views, a booking handoff, or at least ten seconds of measured visible time. Bounce is calculated for closed visits with enough evidence to classify engagement that do not meet those conditions. Open visits and single-page visits with no timing signal or handoff are excluded; two pages or a handoff already establish engagement. Basic request counts are never used as that denominator. Past basic counts cannot reconstruct earlier visit duration or page journeys, and earlier permission-based records are incomplete.
Information retained
Request and optional insight records use normalized routes, tours, server dates, recognized source/referrer categories and allowlisted non-personal campaign labels. Optional records can associate pages and handoffs within the allowed first-party visit. We do not retain IP addresses, user-agent strings, full page queries, full referrer URLs, customer contact, passport, health or payment-card details in these analytics records. We use no browser fingerprint, third-party analytics service, localStorage or sessionStorage. Records have a 90-day expiry with bounded traffic-triggered cleanup. Non-personal campaign labels may be carried on internal links without an identifier.
Affiliate bookings and conversions
Booking redirects preserve the provider URL's existing affiliate account parameters. We do not add a per-click reference or cross-site visitor identifier. A handoff is a key website action, not a purchase. Provider conversion reports and separately verified commission states are kept distinct; unmatched reports are not assigned to a visit or campaign by guesswork.
The affiliate integration can retain opaque conversion, program and affiliate references, currency, reported commission and dates. Verified records may identify pending, approved, cancelled or paid commission. These minimal financial/report records are kept separately for business reconciliation and reviewed for appropriate retention.
Hosting and external websites
The site uses Sites-managed cloud execution, a D1 database and R2 image storage. Insights and setup screens are restricted to the owner. Hosting infrastructure separately processes technical requests to serve and protect the website. Bookings and payments happen on the provider's website, under its own privacy notices, cookies and consent settings. Review those notices before entering booking or payment details.
Contact
Publisher: Evangelos Tzimas. Privacy questions: evanktz9@gmail.com.