Skip to content

Privacy Policy and Notice of Personal Information Processing Practices

Effective Date: December 19, 2025

Supersedes all prior versions

I. GOVERNING FRAMEWORK AND APPLICABILITY

Hotel Julie, operating as a limited liability hospitality enterprise domiciled in the Province of Ontario, Canada (hereinafter "the Hotel," "we," "us," or "our"), hereby provides this comprehensive Notice of Personal Information Processing Practices (the "Notice") pursuant to our obligations under, inter alia, the Personal Information Protection and Electronic Documents Act, S.C. 2000, c. 5 ("PIPEDA"); Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data ("GDPR"); the United Kingdom General Data Protection Regulation as incorporated by the Data Protection Act 2018 ("UK GDPR"); the California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act of 2020, California Civil Code §§ 1798.100 et seq. ("CCPA/CPRA"); Brazil's Lei Geral de Proteção de Dados Pessoais, Law No. 13,709/2018 ("LGPD"); Japan's Act on the Protection of Personal Information, Act No. 57 of 2003 ("APPI"); and other applicable federal, provincial, state, and international data protection statutes, regulations, and common law privacy obligations.

This Notice constitutes a binding component of the contractual relationship established upon reservation confirmation and governs all processing activities undertaken by the Hotel qua data controller, joint controller, or processor, as the case may be, in connection with the provision of accommodation services, ancillary hospitality offerings, digital platforms, and related commercial activities. Capitalized terms not otherwise defined herein shall bear the meanings ascribed to them in the applicable statutory instruments referenced above.

II. DEFINITIONS AND INTERPRETIVE PROVISIONS

"Personal Data" or "Personal Information" shall mean any information relating to an identified or identifiable natural person ("Data Subject") as defined in GDPR Article 4(1), PIPEDA section 2(1), and cognate provisions, including but not limited to: identifiers such as name, identification number, location data, online identifier, or one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.

"Special Categories of Personal Data" (GDPR Article 9) or "Sensitive Personal Information" (CCPA/CPRA § 1798.140(ae)) shall include, without limitation: racial or ethnic origin, political opinions, religious or philosophical beliefs, trade union membership, genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health, data concerning a natural person's sex life or sexual orientation, social security numbers, precise geolocation, and any information subject to heightened statutory protection. Processing of such data is subject to enhanced safeguards and explicit statutory authorization.

"Processing" bears the meaning set forth in GDPR Article 4(2) and includes any operation or set of operations performed on personal data, whether or not by automated means, including collection, recording, organization, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction.

III. ENUMERATION OF PERSONAL DATA CATEGORIES PROCESSED

In furtherance of our commercial operations and statutory compliance, we process the following categories of Personal Data:

A. Identification and Contact Information

Full legal name, postal address (including domicile and correspondence addresses), electronic mail address, telephone numbers (fixed and mobile), date of birth, government-issued identification numbers (processed solely where mandated by immigration, tax, or anti-money laundering legislation), and photographic identification documents.

B. Reservation and Transactional Data

Booking reference numbers, arrival and departure dates, accommodation unit assignment, rate codes, channel attribution data, corporate affiliation codes, special service requests (including dietary restrictions, accessibility accommodations, and room preferences), guest folios, billing entity information, invoice recipients, and reservation metadata including timestamps and modification histories.

C. Financial and Payment Information

Payment card primary account numbers (PANs) are processed exclusively by third-party Payment Card Industry Data Security Standard ("PCI-DSS") Level 1 certified service providers acting as our processors. We retain only truncated card identifiers, transaction authorization codes, payment network references, billing postal codes for address verification system ("AVS") validation, and aggregated settlement data. Bank account information for wire transfers or electronic funds transfers is processed in encrypted form and retained only for the duration required to effect payment and for subsequent audit and dispute resolution purposes.

D. Device, Network and Technical Telemetry

Internet Protocol ("IP") addresses (including both IPv4 and IPv6 addresses), Media Access Control ("MAC") addresses, device identifiers (including Universally Unique Identifiers and advertising identifiers where applicable), user agent strings, operating system version data, browser type and version, screen resolution, referring URLs, access timestamps (in UTC), session identifiers, geolocation metadata derived from IP geolocation databases or GPS coordinates (where expressly consented), and server log data including HTTP headers and request parameters.

E. Physical Access Control and Surveillance Data

Electronic keycard assignment logs, door access event data (including timestamps and access point identifiers), closed-circuit television ("CCTV") recordings captured in common areas, lobbies, corridors, parking facilities, and perimeter zones for the purposes of loss prevention, incident investigation, and compliance with occupational health and safety statutes. CCTV systems are configured to minimize capture of Special Categories of Personal Data; however, incidental capture may occur and is subject to enhanced access controls and minimized retention periods.

F. Communications and Correspondence

Electronic mail correspondence, web form submissions, customer service inquiry transcripts, call recordings (where permitted by applicable wiretap and consent-to-record statutes), chat session logs, and feedback survey responses. Call recordings are retained subject to state-specific consent requirements (e.g., two-party consent jurisdictions).

G. Preference and Behavioral Data

Marketing communication preferences, opt-out/opt-in election records, loyalty program enrollment and tier status, propensity scores derived from behavioral analytics, clickstream data, and inferred demographic attributes for purposes of personalization and direct marketing (subject to applicable opt-out rights).

IV. LEGAL BASES FOR PROCESSING UNDER APPLICABLE PRIVACY REGIMES

A. GDPR and UK GDPR Compliance (Articles 6 and 9)

Where processing is subject to GDPR or UK GDPR, we rely upon the following lawful bases as enumerated in Article 6(1):

  • Article 6(1)(b) – Contractual Necessity: Processing is necessary for the performance of a contract to which the Data Subject is party (i.e., the reservation agreement and related terms of service) or to take steps at the request of the Data Subject prior to entering into a contract (e.g., providing a quote, provisional hold).
  • Article 6(1)(c) – Legal Obligation: Processing is necessary for compliance with legal obligations to which we are subject, including but not limited to: value-added tax and goods and services tax remittance obligations; immigration reporting requirements under provincial and federal statutes; anti-money laundering customer due diligence pursuant to the Proceeds of Crime (Money Laundering) and Terrorist Financing Act, S.C. 2000, c. 17; occupational health and safety incident reporting; building code fire safety register maintenance; and preservation of records for audit and tax examination purposes.
  • Article 6(1)(f) – Legitimate Interests: Processing is necessary for the purposes of legitimate interests pursued by the Hotel or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the Data Subject. Legitimate interests invoked include: fraud detection and prevention; network and information security (including intrusion detection, malware scanning, and log analysis); direct marketing (subject to balancing test and provision of opt-out mechanisms); credit risk assessment; litigation and dispute resolution; and operational analytics to enhance service quality. Balancing assessments are documented in our Legitimate Interest Assessments ("LIAs") maintained pursuant to Article 6(1)(f) and available upon request to our Data Protection Officer.
  • Article 6(1)(a) – Consent: Where none of the foregoing bases apply, we obtain explicit, informed, freely given, and specific consent. Consent mechanisms include checkboxes, granular preference centers, and recorded verbal consents (where permissible). Consent may be withdrawn at any time via the mechanisms provided in Section XII infra.

For Special Categories of Personal Data (Article 9), we rely upon explicit consent (Article 9(2)(a)), processing necessary for reasons of substantial public interest (Article 9(2)(g)), or processing necessary for the establishment, exercise or defense of legal claims (Article 9(2)(f)).

B. PIPEDA Compliance (Principles-Based Framework)

Under PIPEDA, we adhere to the ten fair information principles set forth in Schedule 1. Processing is undertaken only for purposes that a reasonable person would consider appropriate in the circumstances, with consent obtained where required by PIPEDA section 6.1. Consent may be express or implied depending on sensitivity and context; for sensitive personal information, we obtain express opt-in consent.

C. CCPA/CPRA Compliance

Under California law, we process Personal Information for the business purposes enumerated in CCPA § 1798.140(e), including: performing services on behalf of the business (e.g., customer service, payment processing); detecting security incidents; debugging; short-term transient use; performing services such as maintaining accounts and processing transactions; quality and safety assurance; and internal research for technological development. We do not "sell" Personal Information as defined in CCPA § 1798.140(ad) nor "share" Personal Information for cross-context behavioral advertising without providing opt-out mechanisms. California residents may exercise rights enumerated in Section XII infra.

V. HOTEL-SPECIFIC LEGAL OBLIGATIONS AND INNKEEPER LIABILITY

The operation of a hotel implicates specific statutory and common law obligations distinct from general commercial data processing. The following provisions apply:

A. Innkeepers' Statutory Register Requirements

Pursuant to municipal by-laws and provincial regulations governing transient accommodations, we maintain a guest register containing name, address, and arrival/departure dates. Certain jurisdictions (notably Quebec under the Act respecting tourist accommodation establishments, CQLR c. E-14.2) impose explicit register-keeping obligations. Such registers may be subject to inspection by municipal, health, or law enforcement authorities acting under statutory authority. Processing is justified under legal obligation (GDPR Article 6(1)(c)).

B. Immigration and Border Control Reporting

For non-resident guests, immigration statutes may require collection and retention of passport or identity document information. In the European Union, certain member states mandate reporting of guest identity data to national authorities (e.g., Alloggiati in Italy, Meldeschein in Germany). Such processing is carried out solely to the extent required by statute and data is retained only for the prescribed period.

C. Innkeeper Liability and Safekeeping Obligations

At common law and under statutes such as the Innkeepers Act, R.S.O. 1990, c. I.7, innkeepers bear strict liability for guests' goods unless notice is provided and safekeeping facilities (e.g., safe deposit boxes) are made available. Processing of records related to valuables deposited for safekeeping, including itemization and signature logs, is necessary for the establishment, exercise, or defense of legal claims (GDPR Article 9(2)(f) for signatures analyzed as biometric identifiers).

D. Anti-Money Laundering and Counter-Terrorist Financing

The Proceeds of Crime (Money Laundering) and Terrorist Financing Act and associated regulations impose customer due diligence and suspicious transaction reporting obligations on certain accommodation providers. Where these obligations apply, we collect and verify identification, maintain records for prescribed periods (typically five years), and report to FINTRAC as required. Similar obligations exist under the EU's Fourth and Fifth Anti-Money Laundering Directives in applicable member states.

E. Occupational Health and Safety and Public Health Reporting

Incidents on premises may trigger reporting obligations under occupational health and safety legislation (e.g., workplace injuries to staff) or public health statutes (e.g., communicable disease outbreaks pursuant to the Health Protection and Promotion Act, R.S.O. 1990, c. H.7). Processing of health-related data in such contexts is carried out under legal obligation and limited to the minimum necessary for statutory compliance.

F. Fire Safety and Building Code Compliance

Provincial and municipal fire codes may require maintenance of occupancy logs and emergency contact information for guests. Electronic keycard access logs are retained to facilitate emergency egress verification and compliance with occupancy limits. Processing is justified under legal obligation and vital interests (GDPR Article 6(1)(c) and (d)).

G. Accessibility Legislation and Human Rights Obligations

The Accessibility for Ontarians with Disabilities Act, 2005, S.O. 2005, c. 11 ("AODA"), and federal accessibility legislation require provision of accessible accommodations upon request. Processing of disability-related information (a Special Category under GDPR Article 9) is undertaken under explicit consent or substantial public interest grounds (equality of opportunity and treatment). Access to such information is strictly limited to staff with a need-to-know and subject to enhanced confidentiality obligations.

VI. DATA RETENTION SCHEDULES AND DISPOSAL

We retain Personal Data only for as long as necessary to fulfill the purposes for which it was collected, comply with legal obligations, resolve disputes, and enforce our agreements. Specific retention periods include:

  • Financial and Tax Records: Six (6) years from the end of the taxation year to which they relate, pursuant to Income Tax Act subsection 230(4); provincial tax statutes may impose longer periods (e.g., seven years in certain provinces). Foreign tax obligations (e.g., IRS retention for U.S.-source income) are assessed on a case-by-case basis.
  • CCTV Footage: Thirty (30) days in ordinary course; up to ninety (90) days where incident investigation or legal hold is in effect. Footage subject to legal proceedings or regulatory investigation is preserved until final disposition.
  • Electronic Access Logs: Ninety (90) days for operational audit; extended retention (up to two years) for investigation of security incidents or fraud.
  • Reservation and Stay Records: Operational data retained for two (2) years to facilitate re-bookings and customer service; aggregated/anonymized data retained indefinitely for analytics.
  • Marketing Consents and Opt-Outs: Consents retained until withdrawn; opt-out/suppression records retained indefinitely to honor do-not-contact requests.
  • Legal Hold: Where litigation, regulatory investigation, or audit is reasonably anticipated, a legal hold is instituted suspending routine deletion until the matter is resolved.

Upon expiry of retention periods, Personal Data is securely deleted or anonymized in accordance with data disposal procedures incorporating cryptographic erasure, physical media destruction (e.g., degaussing, shredding), and audit logging of disposal events.

VII. SECURITY MEASURES AND ORGANIZATIONAL SAFEGUARDS

We implement a defense-in-depth security posture incorporating administrative, technical, and physical controls commensurate with the risk, volume, and sensitivity of Personal Data processed. Specific measures include:

A. Technical Controls

  • Encryption: Personal Data in transit is encrypted using Transport Layer Security (TLS) 1.2 or higher with forward secrecy; data at rest is encrypted using AES-256 or equivalent. Encryption keys are managed via hardware security modules (HSMs) or cloud key management services with role-based access controls.
  • Access Controls: Role-based access control (RBAC) and principle of least privilege; multi-factor authentication (MFA) required for administrative access; access logs retained and periodically audited.
  • Network Segmentation: Guest-facing networks isolated from administrative systems via VLANs and firewall policies; intrusion detection/prevention systems (IDS/IPS) deployed at network perimeter and critical segments.
  • Vulnerability Management: Quarterly vulnerability scans, annual penetration testing, and timely patching of systems per vendor security bulletins.

B. Organizational Controls

  • Data Protection Impact Assessments (DPIAs): Conducted for high-risk processing activities per GDPR Article 35; documented and reviewed by the Data Protection Officer prior to commencement of processing.
  • Privacy by Design and Default: Privacy considerations integrated into system design, procurement, and operational processes; default settings configured for maximum privacy protection.
  • Staff Training: Mandatory annual privacy and data security training for all staff with access to Personal Data; role-specific training for data processors.
  • Incident Response: Documented breach response plan tested annually; designated breach response team; notification procedures aligned with GDPR Article 33/34, PIPEDA breach notification regulations, and state breach notification statutes.

C. Payment Card Industry Compliance

We do not store, process, or transmit full payment card data (PANs, CVVs, magnetic stripe data) on our systems. All payment processing is outsourced to PCI-DSS Level 1 certified processors. Our environment is subject to annual PCI-DSS Self-Assessment Questionnaires (SAQ A or SAQ A-EP as applicable) and quarterly network scans by Approved Scanning Vendors (ASVs).

VIII. DATA SUBJECT RIGHTS AND REQUEST PROCEDURES

Subject to applicable law and identity verification, Data Subjects may exercise the following rights:

A. Right of Access (GDPR Article 15, PIPEDA Principle 4.9, CCPA § 1798.110)

Individuals may request confirmation of whether we process their Personal Data and obtain a copy thereof, along with supplementary information including purposes, categories, recipients, retention periods, and rights available.

B. Right to Rectification (GDPR Article 16, PIPEDA Principle 4.6)

Correction of inaccurate or incomplete Personal Data without undue delay. Where data has been disclosed to third parties, we will notify recipients of rectifications unless impossible or involving disproportionate effort.

C. Right to Erasure / "Right to be Forgotten" (GDPR Article 17)

Deletion of Personal Data where: (i) no longer necessary for original purpose; (ii) consent withdrawn and no other legal basis exists; (iii) objection raised and no overriding legitimate grounds exist; (iv) processed unlawfully; or (v) required by legal obligation. This right is not absolute and may be restricted where processing is necessary for legal claims, legal obligations, or public interest grounds.

D. Right to Restriction of Processing (GDPR Article 18)

Limitation of processing where: accuracy is contested; processing is unlawful but erasure is opposed; data no longer needed by controller but required by Data Subject for legal claims; or objection pending verification of overriding legitimate grounds.

E. Right to Data Portability (GDPR Article 20, CCPA § 1798.100(d))

Receipt of Personal Data in a structured, commonly used, and machine-readable format (e.g., CSV, JSON) where processing is based on consent or contract and carried out by automated means.

F. Right to Object (GDPR Article 21, PIPEDA Principle 4.3.8)

Objection to processing based on legitimate interests or direct marketing purposes. We will cease processing unless we demonstrate compelling legitimate grounds that override the interests, rights and freedoms of the Data Subject, or for the establishment, exercise or defense of legal claims.

G. Right to Withdraw Consent

Where processing is based on consent, withdrawal may be effected at any time without affecting the lawfulness of processing prior to withdrawal. Withdrawal mechanisms are provided in marketing communications and our preference center.

H. California-Specific Rights

California residents may request: (i) disclosure of categories and specific pieces of Personal Information collected; (ii) categories of sources; (iii) business purposes; (iv) categories of third parties with whom information is shared; (v) deletion (subject to exceptions); and (vi) opt-out of sale/sharing (though we do not sell or share Personal Information as defined by CCPA).

Request Submission: Rights requests may be submitted via email to Hello@hoteljulie.net or by postal mail to our Data Protection Officer at Hotel Julie, 92 St. Vincent St. N., Stratford, ON N5A 5S8, Canada. We will verify identity using reasonable means (e.g., matching request details to account information, government-issued ID where proportionate) and respond within one (1) month (GDPR), thirty (30) days (PIPEDA), or forty-five (45) days (CCPA), with possible extensions communicated in advance. No fee is charged for the first request; manifestly unfounded or excessive requests may be subject to a reasonable administrative fee.

IX. SUPERVISORY AUTHORITY CONTACT AND COMPLAINT PROCEDURES

Data Subjects retain the right to lodge complaints with competent supervisory authorities without prejudice to other administrative or judicial remedies. Relevant authorities include:

  • Canada: Office of the Privacy Commissioner of Canada, 30 Victoria Street, Gatineau, QC K1A 1H3; www.priv.gc.ca
  • European Union: Supervisory authority of the member state of habitual residence, place of work, or place of alleged infringement (list available at edpb.europa.eu).
  • United Kingdom: Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF; ico.org.uk
  • California: California Attorney General's Office, Privacy Enforcement and Protection Unit, 300 South Spring Street, Los Angeles, CA 90013.

X. CONTACT INFORMATION AND DATA PROTECTION OFFICER

Inquiries, rights requests, and complaints may be directed to our designated Data Protection Officer:

Data Protection Officer
Hotel Julie
92 St. Vincent St. N.
Stratford, ON N5A 5S8
Canada
Email: Hello@hoteljulie.net

For EU/EEA Data Subjects, our EU representative (where appointed pursuant to GDPR Article 27) contact details will be provided upon request.

XI. AMENDMENTS AND VERSIONING

This Notice may be amended from time to time to reflect changes in legal obligations, business practices, or technological capabilities. Material changes will be communicated via prominent notice on our website and, where feasible and required by law, direct notification to affected Data Subjects. The "Effective Date" at the head of this Notice indicates the date of the current version. Prior versions are archived and available upon request.

XII. GOVERNING LAW AND JURISDICTION

This Notice and all processing activities are governed by and construed in accordance with the laws of the Province of Ontario and the federal laws of Canada applicable therein, without regard to conflicts of law principles. For Data Subjects in the European Union, United Kingdom, California, or other jurisdictions with mandatory privacy laws, nothing herein is intended to limit rights conferred by such laws. Where conflicts arise between this Notice and applicable mandatory law, the latter shall prevail to the extent of the inconsistency.

XIII. DISCLAIMER AND LEGAL ADVICE

This Notice constitutes a binding legal document governing the relationship between Hotel Julie and Data Subjects. It does not, however, constitute legal advice to third parties. While we endeavor to maintain compliance with all applicable privacy laws, the legal landscape is complex and evolving. Data Subjects with specific legal questions should consult qualified counsel in their jurisdiction. The Hotel disclaims liability for any reliance on this Notice as a source of legal advice beyond the controller-Data Subject relationship contemplated herein.