Cookie Policy

1. What cookies are

Cookies are small pieces of data that a website or related service can store in a browser. They can support essential functions, preferences, measurement, security or advertising, depending on how a site is configured. Similar technologies can include local storage, pixels, device identifiers or other browser-based mechanisms.

Cookies can be described by purpose, duration and origin. Some exist only for a browser session, while others remain for a defined period. First-party cookies are associated with the visited site, while third-party technologies can be introduced by external services embedded in a page.

Canadian privacy guidance recognizes that cookies and related tracking technologies can raise privacy issues when they are used to observe online activity or create profiles. The appropriate notice and consent approach depends on the information involved and the purpose for which the technology is used.

2. Cookies in this website package

The current static package does not include code that writes cookies for advertising, analytics, personalization or behavioural targeting. It does not include a third-party advertising widget, a marketing pixel, an analytics library or a cookie consent pop-up.

This description applies to the files delivered with the website. A hosting platform, content-delivery service or future integration can introduce separate technical behaviour, so the live site should be checked after deployment rather than assuming that the production environment is identical to the static files.

3. Current cookie categories

No first-party advertising cookie, analytics cookie, preference cookie or behavioural-profile cookie is intentionally created by the supplied JavaScript. The core navigation and inquiry interface is designed to work without those categories.

This policy does not claim that a visitor's browser or hosting provider creates no technical records at all. Server-side records and browser-level functions are separate from a cookie intentionally written by this project's front-end code.

4. Essential browser functions

The website uses standard browser features to display pages, open the mobile navigation, change the gallery image and read URL parameters used by the inquiry confirmation page. These functions do not require this project's script to create a cookie.

The contact form uses a GET request to move submitted fields to the confirmation page through URL parameters. Visitors should therefore avoid entering unnecessary sensitive information in the form or message field.

Browser history, address-bar data and cached resources are not the same thing as cookies, although they can still contain information about a browsing session. Visitors can use their browser controls to manage history and cached site data.

5. Local storage and session storage

The supplied script does not intentionally write to localStorage or sessionStorage. These browser storage mechanisms can be used by websites for preferences or short-term state without using traditional cookies, but they are not part of the current implementation.

If local or session storage is added later, the purpose, duration and any consent requirements should be documented before deployment. The Privacy Policy should also be updated if the stored information is linked to an identifiable visitor.

6. Analytics

No analytics service is configured in the supplied files. The website does not currently include an analytics tag that measures visitor numbers, page paths, device characteristics or campaign performance.

If analytics is added later, the operator should determine what information is collected, whether identifiers or cookies are used, how long information is retained and what notice or consent is required under applicable Canadian privacy law.

The Privacy Policy should identify the actual provider and data handling where an analytics integration materially affects personal information. A generic statement should not be used as a substitute for reviewing the provider's real configuration.

7. Advertising and behavioural tracking

No behavioural advertising tracker is implemented in this website package. The static site files do not intentionally create an advertising profile, retargeting audience or cross-site browsing identifier.

If online behavioural advertising technology is introduced later, visitors should receive clear information about the purpose and meaningful choices consistent with applicable privacy requirements. The operator should also review whether the technology transfers information to another party or combines data across services.

8. Consent approach

Because the supplied website code does not intentionally set non-essential cookies, this package does not include a cookie consent banner. A banner should not be added merely as decoration if no consent choice is actually needed for the deployed technology.

If non-essential tracking or storage is later introduced and consent is required, the consent interface should accurately describe the relevant categories and should not rely on a pre-selected acceptance option. A visitor's choice should correspond to the technology that is actually enabled.

9. Third-party media and fonts

The project does not embed external video players, social media feeds or remote image services. Content images are referenced as local files under assets/images so the site owner can supply and control the photographs used.

The stylesheet uses system font families and does not require a remote font service. This keeps the visual layer independent of an external font request in the delivered project.

If a map, video, social feed, external font or other embedded service is added later, the operator should check whether that service places cookies or uses similar technologies before deployment.

10. Server logs

Web hosting systems commonly can create technical records needed to deliver and secure a site. These records may include request time, requested page, network information or diagnostic details depending on the hosting configuration.

The exact server-log configuration is not part of these static files. The live operator should review its hosting configuration and update the Privacy Policy if log data is retained or used in a way that involves personal information.

11. Session management and accounts

The supplied website does not provide customer accounts, sign-in sessions, saved trip dashboards or an authenticated booking portal. It therefore does not need a login-session cookie for those functions.

If account features are introduced later, essential session cookies may become necessary for security and authentication. Their purpose and duration should be documented as part of the live implementation.

12. Browser controls

Modern browsers provide controls for clearing cookies and site data, blocking third-party cookies and managing tracking preferences. Browser menus and wording vary by product and version, so visitors should refer to the controls available in the browser they use.

Because the current project code does not intentionally set cookies, changing cookie controls should not be necessary for the core navigation and inquiry interface described here. Clearing browser history can still remove URL history associated with a submitted inquiry.

13. Do Not Track and browser privacy signals

The current website does not include behavioural tracking code that changes its operation based on a Do Not Track setting or similar browser signal. There is therefore no advertising-profile feature for such a signal to disable in the supplied front-end package.

If tracking technology is introduced in the future, the operator should review the privacy signals supported by the chosen provider and the legal requirements that apply to those signals.

14. Changes after deployment

Deployment can materially change a site's technical behaviour. A hosting service, security layer, analytics integration, embedded content provider or advertising tool can introduce cookies or related storage even when the original static project did not include them.

The live site should therefore be tested after deployment and after material technical changes. The published Cookie Policy should describe the actual production configuration rather than relying permanently on the original development package.

15. Future changes to this policy

If a cookie-based feature is added, this policy should be updated before or at the time of deployment. The update should describe the category, purpose, provider, duration and available user choices with enough clarity for visitors to understand the change.

Where meaningful consent is required, the consent mechanism should not be bundled with unrelated choices or rely on a pre-selected option. The update date at the top of this page should be changed when the policy is materially revised.

16. Relationship with the Privacy Policy

This Cookie Policy focuses on browser storage, tracking and related technical functions. The Privacy Policy explains the broader handling of personal information submitted through the inquiry form and other data-handling principles relevant to the site.

The two documents should be read together where a technology both stores information in the browser and processes personal information. If the implementation changes, both documents should be checked for consistency.

17. Contact about this policy

The supplied company details are European Tour Operators, 149 Tottenham Court Road, London. The supplied telephone number is +16137014271 and the supplied email address is [email protected]. Questions about this Cookie Policy may be raised using those published contact details.

Questions about the technical practices described here can be raised at [email protected], through the supplied telephone contact, or by using the company address. The website's legal Contact page repeats the published company particulars.