I. SCOPE AND LEGAL FRAMEWORK
Hotel Julie (the "Hotel," "we," "us," or "our") hereby provides this Cookie Policy (the "Policy") in accordance with our obligations under Directive 2002/58/EC of the European Parliament and of the Council of 12 July 2002 concerning the processing of personal data and the protection of privacy in the electronic communications sector, as amended by Directive 2009/136/EC (the "ePrivacy Directive"); the Privacy and Electronic Communications (EC Directive) Regulations 2003 (SI 2003/2426) as amended ("PECR"); Regulation (EU) 2016/679 (the "GDPR"); and other applicable federal, provincial, state, and international laws governing the use of cookies and similar tracking technologies.
This Policy constitutes an integral component of our Privacy Policy (available at /privacy) and governs the deployment of cookies, web beacons, pixel tags, local storage objects, software development kits (SDKs), and other automated data collection mechanisms (collectively, "Cookies") on our website, mobile applications, and digital properties (collectively, the "Platform"). Where this Policy conflicts with the Privacy Policy, the more specific provision shall govern with respect to Cookie-related processing.
II. DEFINITIONS AND TECHNICAL SPECIFICATIONS
A. Cookie Taxonomy
A "Cookie" is a small text file consisting of alphanumeric identifiers deposited on the terminal equipment (computer, mobile device, tablet) of a user by a web server and retrieved upon subsequent visits. Cookies are classified according to multiple taxonomies:
- By Origin: First-party cookies (set by the domain being visited) vs. third-party cookies (set by domains other than the one being visited, typically for advertising or analytics purposes).
- By Duration: Session cookies (deleted when the browser session ends) vs. persistent cookies (remain on the device until expiration date or manual deletion).
- By Purpose: Strictly necessary, performance/analytics, functionality, and targeting/advertising cookies, as further elaborated in Section IV infra.
B. Similar Technologies
In addition to HTTP cookies, we deploy:
- Web Beacons / Pixel Tags: Transparent graphic images (typically 1×1 pixels) embedded in web pages or emails to track user interactions, email open rates, and page views.
- Local Storage Objects: HTML5 localStorage and sessionStorage APIs used to store data locally on the user's browser with no automatic expiration (localStorage) or session-based expiration (sessionStorage).
- Flash Cookies (LSOs): Locally Shared Objects stored by Adobe Flash Player (deprecated but may exist in legacy contexts).
- Device Fingerprinting: Collection and algorithmic combination of device attributes (user agent, screen resolution, installed fonts, plugins, timezone, language settings, canvas fingerprinting hash) to probabilistically identify devices without explicit identifiers. Fingerprinting is employed only where legally permissible and subject to transparency obligations.
- Software Development Kits (SDKs): Third-party code libraries embedded in mobile applications to collect device identifiers (IDFA, AAID), app usage analytics, crash reports, and attribution data.
III. LEGAL BASIS FOR COOKIE DEPLOYMENT
A. ePrivacy Directive and PECR Compliance
Article 5(3) of the ePrivacy Directive and Regulation 6(4) of PECR require that the storing of information, or the gaining of access to information already stored, in the terminal equipment of a user is permitted only on condition that the user has given his or her consent, having been provided with clear and comprehensive information. Exceptions exist for cookies that are:
- (i) Strictly Necessary: Cookies used for the sole purpose of carrying out the transmission of a communication over an electronic communications network, or as strictly necessary to provide an information society service explicitly requested by the subscriber or user (e.g., shopping cart, authentication tokens, load balancing).
- (ii) Legitimate Interest (Limited Scope): Where cookies are not strictly necessary but serve a legitimate interest (e.g., security, fraud prevention), we conduct a balancing test and provide transparent notice; however, consent is generally required for non-essential cookies under the ePrivacy framework.
B. GDPR Article 6 Interplay
While the ePrivacy Directive governs the placement of cookies, the GDPR governs the processing of personal data collected via cookies. Where cookies process personal data (e.g., unique identifiers, behavioral profiles), we rely upon the following GDPR lawful bases:
- Consent (Article 6(1)(a)): For analytics, marketing, and targeting cookies, we obtain freely given, specific, informed, and unambiguous consent via our Consent Management Platform ("CMP"), which presents granular opt-in choices and records consent timestamps, user identifiers, and consent scope.
- Legitimate Interests (Article 6(1)(f)): For security cookies, fraud detection, and certain first-party analytics (subject to balancing tests and minimization principles), processing is justified under legitimate interests. Legitimate Interest Assessments ("LIAs") are documented and available upon request.
C. Canadian Anti-Spam Legislation (CASL) and PIPEDA
Under CASL, implied consent may exist for installation of computer programs (including tracking scripts) where the program's function and purpose are clearly disclosed and consent is obtained for any data transmission. PIPEDA's consent requirements apply to the processing of personal information collected via cookies. We provide clear notice and obtain express opt-in consent for non-essential cookies.
D. California Consumer Privacy Act (CCPA/CPRA)
Under CCPA § 1798.135, we provide California residents with a "Do Not Sell or Share My Personal Information" opt-out mechanism. Cookies used for cross-context behavioral advertising constitute "sharing" under CPRA § 1798.140(ah); we honor Global Privacy Control ("GPC") signals transmitted by browsers as an opt-out of sale/sharing pursuant to California Attorney General regulations.
IV. ENUMERATION OF COOKIES DEPLOYED
The following table enumerates cookies and similar technologies deployed on our Platform, categorized by purpose in accordance with the International Chamber of Commerce UK Cookie Guide and Information Commissioner's Office guidance:
Category 1: Strictly Necessary Cookies
These cookies are essential for the operation of the Platform and cannot be disabled without materially impairing functionality. Deployment does not require consent under ePrivacy Directive Article 5(3) exemption.
| Cookie Name | Purpose | Duration | Origin |
|---|
| PHPSESSID / ASP.NET_SessionId | Session management; maintains user state across HTTP requests | Session | First-party |
| CSRF-TOKEN | Cross-Site Request Forgery protection | Session | First-party |
| load_balancer | Server load balancing; routes requests to appropriate backend node | Session | First-party |
| cookieconsent_status | Records user's cookie consent preferences to avoid repeated banner display | 12 months | First-party |
Category 2: Performance and Analytics Cookies
We employ Cloudflare Web Analytics, a privacy-preserving analytics solution that does not set cookies, does not track users across websites, and does not collect personally identifiable information. Cloudflare Analytics operates server-side and processes only aggregated, anonymized metrics (page views, referrers, browser types, geographic regions at country-level granularity) without individual user tracking.
| Service | Provider | Purpose | Cookie Usage |
|---|
| Cloudflare Web Analytics | Cloudflare, Inc. (third-party) | Privacy-first web analytics; aggregated traffic metrics, performance monitoring, security threat detection | Cookieless (server-side beacon) |
| __cflb, __cf_bm | Cloudflare (infrastructure) | Load balancing, bot management, DDoS mitigation (classified as strictly necessary for security) | Session / 30 minutes |
Note: Cloudflare Web Analytics complies with GDPR, CCPA, and ePrivacy Directive without requiring consent banners, as it does not process personal data or employ tracking cookies. Cloudflare's infrastructure cookies (__cflb, __cf_bm) are classified as strictly necessary for security and performance optimization under ePrivacy Directive Article 5(3) exemption. Data Processing Addendum executed with Cloudflare pursuant to GDPR Article 28; Standard Contractual Clauses govern U.S. data transfers.
Category 3: Functionality Cookies
These cookies enable enhanced functionality and personalization (e.g., language preferences, accessibility settings). Consent is required; granular opt-in provided via CMP.
| Cookie Name | Purpose | Duration |
|---|
| lang_pref | Stores user's preferred display language | 12 months |
| accessibility_mode | Stores accessibility preferences (high contrast, font size adjustments) | 12 months |
Category 4: Targeting and Advertising Cookies
These cookies track browsing activity to deliver targeted advertisements and measure campaign effectiveness. Explicit opt-in consent required; third-party cookies subject to Standard Contractual Clauses for cross-border data transfers.
| Cookie Name | Provider | Purpose | Duration |
|---|
| _fbp, fr | Facebook Pixel (third-party) | Conversion tracking, retargeting, lookalike audience generation | 90 days / 90 days |
| IDE, DSID | Google DoubleClick (third-party) | Display advertising, remarketing, frequency capping | 13 months / 14 days |
Note: We do not deploy targeting cookies without affirmative consent. California residents and EEA/UK users may opt out via CMP or Global Privacy Control signals.
V. CONSENT MANAGEMENT AND USER CONTROLS
A. Consent Management Platform (CMP)
We deploy a Transparency and Consent Framework ("TCF") v2.2-compliant CMP that presents a layered notice on first visit, providing:
- Granular Choices: Separate opt-in toggles for each cookie category (Strictly Necessary cookies are pre-enabled and non-toggleable).
- Vendor List: Access to full list of third-party cookie providers with links to their respective privacy policies.
- Purposes and Legal Bases: Clear explanation of each purpose (e.g., "Personalized Advertising") and legal basis invoked (consent vs. legitimate interest).
- Right to Withdraw: Persistent link to re-access CMP and modify preferences at any time.
Consent records are stored for a minimum of three (3) years for regulatory audit purposes and include: user identifier (cookie ID or pseudonymized IP hash), timestamp, consent scope (categories accepted), CMP version, and user agent string.
B. Browser-Level Controls
Users may configure browser settings to block or delete cookies. Instructions for major browsers:
- Google Chrome: Settings > Privacy and Security > Cookies and other site data
- Mozilla Firefox: Options > Privacy & Security > Cookies and Site Data
- Safari: Preferences > Privacy > Manage Website Data
- Microsoft Edge: Settings > Cookies and site permissions
Note: Blocking strictly necessary cookies will impair Platform functionality (e.g., inability to maintain session state, complete reservations).
C. Do Not Track (DNT) and Global Privacy Control (GPC)
The Platform does not respond to Do Not Track ("DNT") signals due to lack of industry consensus on interpretation. However, we honor Global Privacy Control ("GPC") signals transmitted by compliant browsers as an opt-out of sale/sharing under CCPA/CPRA and as a signal of non-consent for non-essential cookies where technically feasible.
VI. DATA TRANSFERS AND PROCESSOR OBLIGATIONS
Third-party cookies deployed on our Platform may result in data transfers to non-EEA jurisdictions (notably the United States for Cloudflare, Facebook Pixel, and other U.S.-domiciled processors). Such transfers are governed by:
- Standard Contractual Clauses: We execute European Commission SCCs with all third-party cookie providers processing EEA personal data, supplemented by Transfer Impact Assessments where required.
- Adequacy Decisions: Where transfers occur to jurisdictions subject to adequacy decisions (e.g., Canada for commercial organizations under PIPEDA), no additional safeguards are required.
- Processor Obligations: Third-party providers are contractually obligated to process data only on our instructions, implement appropriate security measures, and facilitate Data Subject rights requests.
VII. RETENTION OF COOKIE DATA
Cookie data is retained for periods commensurate with the purpose:
- Session Cookies: Deleted upon browser closure or session timeout (typically 30 minutes of inactivity).
- Analytics Data: Cloudflare Web Analytics retains aggregated, anonymized metrics indefinitely for performance benchmarking; no individual user-level data is stored. Cloudflare infrastructure cookies (__cf_bm) are session-based or expire within 30 minutes.
- Advertising Cookies: Retained for 90 days to 13 months depending on provider; interest segments and behavioral profiles purged upon opt-out or expiration.
- Consent Records: Retained for three (3) years post-withdrawal to demonstrate compliance with consent obligations.
VIII. SECURITY MEASURES
Cookie data transmitted to our servers or third-party processors is protected via HTTPS/TLS encryption. Cookies containing sensitive identifiers (authentication tokens, session IDs) are flagged with Secure and HttpOnly attributes to prevent interception and client-side script access. SameSite attribute is configured (Lax or Strict) to mitigate cross-site request forgery attacks.
IX. CHILDREN'S PRIVACY
Our Platform is not directed to children under the age of 16 (or applicable age of digital consent in the user's jurisdiction). We do not knowingly deploy cookies to collect personal data from children. Where we obtain actual knowledge that a user is below the applicable age threshold, we will delete associated cookie data and terminate processing.
X. CHANGES TO THIS POLICY
We reserve the right to modify this Policy to reflect changes in legal obligations, cookie providers, or business practices. Material changes (e.g., introduction of new cookie categories requiring consent) will be communicated via updated CMP notice and, where feasible, direct notification to users who have provided contact information. Continued use of the Platform following notice of changes constitutes acceptance of the amended Policy, subject to renewal of consent where required by law.
XI. CONTACT AND COMPLAINTS
Questions, requests to exercise Data Subject rights with respect to cookie data, or complaints regarding cookie practices may be directed to:
Data Protection Officer
Hotel Julie
92 St. Vincent St. N.
Stratford, ON N5A 5S8
Canada
Email: Hello@hoteljulie.net
Data Subjects retain the right to lodge complaints with supervisory authorities (Information Commissioner's Office, European Data Protection Board member authorities, Office of the Privacy Commissioner of Canada, or California Attorney General) without prejudice to other remedies.
XII. GOVERNING LAW
This Policy is governed by the laws of the Province of Ontario and the federal laws of Canada applicable therein. Where mandatory privacy laws of other jurisdictions apply (EU/EEA, UK, California), such laws shall govern to the extent of any conflict. In the event of inconsistency between this Policy and applicable mandatory law, the latter shall prevail.
XIII. LEGAL DISCLAIMER
This Policy constitutes a binding legal document governing cookie deployment and data processing on the Platform. It does not constitute legal advice to third parties. The regulatory landscape governing cookies and online tracking is subject to ongoing evolution (including proposed ePrivacy Regulation); we endeavor to maintain compliance but disclaim liability for reliance on this Policy as legal advice beyond the controller-user relationship contemplated herein. Users with specific legal questions should consult qualified counsel in their jurisdiction.