Privacy

Privacy for the MVP

This MVP does not include user accounts, saved trips, payment collection, memberships, or a custom booking engine.

Analytics

The site keeps a small internal event queue so decision flows can be tested without an external analytics service. When Google Analytics is configured, its tag loads only after you choose Allow analytics. Declining does not load the Google tag.

A random, session-scoped identifier is stored in the browser session only so one visit's decision steps can be connected. It is not an account identifier, is not designed to identify a person, and is cleared when the browser session ends.

Advertising storage, advertising user data, advertising personalization, Google signals, and personalized advertising signals remain disabled in the analytics configuration. You can reopen Privacy choices from any page and withdraw optional analytics consent.

Affiliate redirects

The internal redirect route prepares click events with page, destination, area, partner, offer, placement, and referrer fields. Browser clicks and redirect events use an opaque correlation ID for deduplication. These identifiers must not be combined with names, email addresses, booking details, or other directly identifying information.

Provider review

Before a production analytics, email, or form provider is activated, its notice, retention, regional privacy obligations, and consent requirements must be reviewed against the deployed configuration.