Cookie and local storage policy

Development tools, browser extensions, hosting infrastructure, or a service you open from Tripix may create their own technical data. Those technologies are not necessarily controlled by the public Tripix page. Production use will be reviewed separately from local development behaviour.

• Cookies are small text files a website asks a browser to store and return on later requests.
• Local storage stores a small value in the browser on a device and does not automatically send it with every web request.
• Session storage is similar to local storage but is normally removed when the browser tab or session ends.
• SDKs, pixels, and device identifiers are technologies that an app or website may use for security, diagnostics, communication measurement, or analytics.

Where one of these technologies stores or links to information about an identifiable person or device, Tripix handles that information under the Privacy Policy.

Strictly necessary

These technologies support security, network routing, fraud prevention, load balancing, form integrity, authentication, session continuity, and other features a user requests. Disabling them may prevent a sign-in, secure account, booking, or payment feature from working.

Preferences

These remember choices such as light or dark mode, language, recent trip-planning state, or accessibility preferences. The current theme preference is stored under the browser key tripix-theme and remains until you change it, clear site storage, or the browser removes it.

Diagnostics and analytics

Tripix may later use limited diagnostics or analytics to understand page reliability, errors, feature use, and booking-flow completion. Before enabling non-essential analytics that require consent, Tripix will identify the provider and purpose and provide an appropriate choice. Aggregated measurement that does not identify a person may be used where permitted.

Advertising

Tripix does not currently use the public website to create cross-site advertising profiles or retarget visitors. If that changes, this policy and the website controls will be updated before activation, and consent will be sought where required.

A Tripix booking flow may use providers for payment, maps, messaging, fraud prevention, customer support, app distribution, or embedded media. A provider may set its own cookies or identifiers when its content or interface loads, particularly after you follow a link or open a payment page. Its privacy and cookie terms apply to data it collects directly.

Tripix will not describe a third-party technology as strictly necessary merely because it is commercially useful. Before adding a provider, Tripix will assess the purpose, data collected, retention, access, and available consent or opt-out controls.

• Use the Tripix theme control to switch between light and dark mode.
• Clear cookies and site data through browser settings to remove the stored Tripix theme and any future site identifiers. The next visit will use the browser's preferred colour scheme unless you choose again.
• Block or limit cookies through browser settings. Some secure account, booking, or payment features may not work if a necessary cookie is blocked.
• Use any Tripix consent panel or settings page that appears after non-essential technology is introduced. A rejection should be as easy to communicate as an acceptance.
• Review mobile operating-system controls for app permissions and advertising identifiers.

Browser "do not track" signals are not consistently defined. Tripix will honour legally recognised opt-out signals when they apply and will otherwise rely on the controls described above.

Tripix may update this policy when website or app technologies change. A material change will be reflected in the last-updated date and, where required, a new choice will be presented before non-essential technology is used.