StayExactVerified hotel decisions
Public pilot policy

Privacy notice

This privacy notice applies to the current StayExact public pilot at stayexact.com. StayExact does not publish the owner's personal identity or personal contact details. The notice is updated when the site's material data flows change.

Privacy-minimal public pilot. No personal identity or personal contact information about the site owner is published. Centralized first-party behavioral analytics remain disabled.

What StayExact handles in the current pilot

Hosting and technical logs

The site is hosted on Hostinger. Hostinger's hosting analytics and access logs can automatically record technical request information such as request time, IP address, requested resource, browser/device information, and country inferred from IP. Those hosting logs are separate from the browser-local decision events described above.

StayExact does not use those hosting records in the current pilot to build advertising profiles or a centralized behavioral analytics funnel.

Reference: Hostinger Help Center — “How to use the analytics section on Hostinger dashboard”.

Affiliate booking links and third parties

Some booking actions are affiliate links. If a visitor uses one and completes an eligible booking, StayExact may earn a commission at no additional cost to the visitor.

When a booking link is activated, the visitor leaves StayExact and is sent through Stay22 toward the exact allowlisted Booking.com property. Stay22 and the eventual booking provider operate their own services and privacy practices. Their processing begins outside the local-only event storage used by this site.

The current pilot uses direct Stay22 Allez links only. Stay22 Global Script, Spark, Nova, Google Analytics, and Google Tag Manager are not installed.

Cookies, local storage, and tracking

The current StayExact code does not intentionally set advertising or centralized analytics cookies. It does use browser local storage for local interaction events. A visitor can remove those local events using the browser's site-data/storage controls.

After a visitor follows an external affiliate link, Stay22, Booking.com, or another destination reached through the booking flow may use their own cookies, trackers, or technical logs under their own notices and settings.

We do not claim that the entire end-to-end booking journey is cookie-free.

Browser privacy signals

StayExact currently does not run cross-site advertising trackers, Google Analytics, Google Tag Manager, or centralized first-party behavioral analytics. Because those tracking systems are not active, browser Do Not Track (DNT) or Global Privacy Control (GPC) signals do not change the current on-site behavior.

After a visitor follows an external affiliate or booking link, the destination service operates under its own privacy practices and may respond to browser privacy signals differently.

Retention and choices

Browser-local events remain on the visitor's device unless they are cleared by the browser or user. The site does not currently upload those local events to a StayExact analytics database.

Hosting log retention is controlled by the hosting environment and provider configuration. If StayExact later introduces operator-controlled retention beyond the current browser-local design, this notice will be updated before that change.

Privacy of the site owner

StayExact does not publish the owner's personal name, personal email address, postal or home address, telephone number, messaging number, personal social profile, or any other personal contact detail. StayExact also does not publish a public contact form.

This is a permanent privacy rule for this project, not a temporary staging choice. If a launch jurisdiction creates a mandatory disclosure requirement that cannot be satisfied without exposing personal information, public launch must stop for a separate decision rather than publishing personal details automatically.

Policy status and updates

Effective / last updated: 5 October 2026. This notice applies to the current public pilot and must be reviewed whenever the data flows materially change, including any future introduction of centralized analytics, a contact form, user accounts, consent tooling, or site-wide Stay22 scripts.