Skip to content

Information Security and Data Protection Policy

Effective Date: December 19, 2025

Supersedes all prior versions

I. POLICY STATEMENT AND SCOPE

Hotel Julie (the "Hotel," "we," "us," or "our") is committed to safeguarding the confidentiality, integrity, and availability of all information assets under our control. This Information Security and Data Protection Policy (the "Policy") establishes the framework for protecting guest data, employee information, business records, and technical infrastructure against unauthorized access, disclosure, modification, destruction, or loss.

This Policy applies to all personnel (employees, contractors, consultants, temporary workers, and third-party service providers), systems, networks, and facilities operated by or on behalf of Hotel Julie. Compliance is mandatory and subject to disciplinary action up to and including termination of employment or contractual relationship for violations.

II. REGULATORY AND COMPLIANCE FRAMEWORK

Our security posture is designed to comply with applicable laws, regulations, and industry standards, including but not limited to:

  • Payment Card Industry Data Security Standard (PCI DSS) v4.0: Requirements for organizations that store, process, or transmit payment card data. We maintain Level 2 Merchant compliance validated through annual Self-Assessment Questionnaires (SAQ D) and quarterly network scans by Approved Scanning Vendors (ASVs).
  • General Data Protection Regulation (GDPR) - Regulation (EU) 2016/679: Articles 5 (principles), 25 (data protection by design and default), 32 (security of processing), and 33-34 (breach notification obligations).
  • Personal Information Protection and Electronic Documents Act (PIPEDA): Schedule 1, Principle 7 (safeguards) requiring security appropriate to the sensitivity of the information.
  • California Consumer Privacy Act (CCPA/CPRA): § 1798.81.5 requiring reasonable security procedures to protect personal information.
  • Proceeds of Crime (Money Laundering) and Terrorist Financing Act (PCMLTFA): Record-keeping and reporting obligations requiring secure retention of customer identification and transaction records.
  • Occupational Health and Safety Act (Ontario): Requirements for workplace safety systems including visitor management and emergency access controls.

III. INFORMATION CLASSIFICATION AND HANDLING

A. Classification Levels

All information assets are classified according to sensitivity and criticality:

  • Restricted: Information requiring the highest level of protection (e.g., payment card data, authentication credentials, Social Insurance Numbers, passport copies, health information, encryption keys). Unauthorized disclosure could result in severe legal, financial, or reputational harm.
  • Confidential: Proprietary business information, guest reservation details, employee personnel files, financial records, contracts. Disclosure limited to authorized personnel with legitimate business need.
  • Internal Use: Operational information intended for internal circulation (policies, procedures, internal communications). Not for public disclosure but lower sensitivity than Confidential.
  • Public: Information approved for public release (marketing materials, published rates, publicly accessible website content).

B. Handling Requirements

Restricted Data: Encrypted at rest (AES-256) and in transit (TLS 1.2+); access logged and audited; storage limited to PCI DSS-compliant systems; physical documents stored in locked containers with access logs; destruction via cross-cut shredding (minimum DIN P-4 security level) or certified electronic sanitization (NIST SP 800-88 media sanitization guidelines).

Confidential Data: Access restricted via role-based controls; encryption recommended for electronic transmission; physical documents secured in locked areas; disposal via shredding or secure deletion.

IV. ACCESS CONTROL AND AUTHENTICATION

A. Principle of Least Privilege

Access to systems, networks, and data is granted on a need-to-know basis commensurate with job responsibilities. Privileged access (administrative rights, database access, payment systems) is restricted to authorized personnel and subject to enhanced monitoring.

B. Authentication Standards

  • Password Policy: Minimum 12 characters; complexity requirements (uppercase, lowercase, numeric, special characters); no dictionary words or personal information; 90-day expiration for privileged accounts; prohibition on password reuse (last 12 passwords); immediate change upon suspected compromise.
  • Multi-Factor Authentication (MFA): Mandatory for remote access, administrative accounts, and access to systems processing Restricted data. Time-based One-Time Passwords (TOTP) or hardware security keys (FIDO2/WebAuthn) preferred.
  • Account Lockout: Automated lockout after 5 failed authentication attempts; 30-minute lockout duration or manual unlock by IT administrator.

C. Physical Access Controls

Server rooms, network equipment closets, and areas housing Restricted data are protected by electronic access control systems (proximity card readers) with audit logs retained for 90 days. CCTV monitoring of access points with 30-day retention. Visitor access requires sign-in/sign-out logs and escort by authorized personnel.

V. NETWORK AND INFRASTRUCTURE SECURITY

A. Network Segmentation

Networks are segmented into security zones:

  • Cardholder Data Environment (CDE): Isolated network segment for systems that store, process, or transmit payment card data. Firewall-protected with intrusion detection/prevention systems (IDS/IPS). Access restricted via VPN with MFA.
  • Guest Network: Isolated Wi-Fi network for guest use with bandwidth throttling and content filtering. No access to internal systems.
  • Corporate Network: Internal systems for business operations, property management system (PMS), reservation management. Protected by next-generation firewall (NGFW) with application awareness.
  • IoT/Building Systems: Separate VLAN for smart room controls, HVAC, lighting, access control systems. No direct internet access; managed via jump server.

B. Firewall and Intrusion Prevention

Stateful inspection firewalls deployed at network perimeter and between security zones. Default-deny rule sets; quarterly rule reviews; change management process for rule modifications. IDS/IPS monitors for malicious activity with Security Operations Center (SOC) alerting for high-severity events.

C. Wireless Security

Corporate wireless networks protected via WPA3-Enterprise with 802.1X authentication (RADIUS server). Guest Wi-Fi uses captive portal with terms acceptance logging. Rogue access point detection via wireless intrusion prevention system (WIPS).

D. Encryption

  • Data in Transit: TLS 1.2+ for web traffic; SSH for remote administration; VPN (IPsec or WireGuard) for remote access. Prohibition on outdated protocols (SSL, TLS 1.0/1.1, unencrypted FTP, Telnet).
  • Data at Rest: Full-disk encryption (BitLocker, LUKS) for endpoints; database-level encryption (Transparent Data Encryption) for PMS and CRM databases; encrypted backups (AES-256).

VI. ENDPOINT AND APPLICATION SECURITY

A. Endpoint Protection

  • Antivirus/Anti-Malware: Enterprise endpoint detection and response (EDR) solution deployed on all workstations and servers; daily signature updates; real-time scanning; quarterly full system scans.
  • Patch Management: Critical security patches applied within 30 days of release; operating system and application updates tested in non-production environment before deployment; automated patch deployment for endpoints via centralized management.
  • Host-Based Firewall: Enabled on all endpoints with default-deny inbound rules; exceptions documented and approved via change management.
  • USB Device Control: USB storage devices restricted via Group Policy; whitelisting for approved devices; encryption mandatory for authorized removable media.

B. Secure Development Practices

Web applications and custom software undergo secure code review and vulnerability testing prior to production deployment. OWASP Top 10 vulnerabilities addressed; input validation, output encoding, and parameterized queries employed to prevent injection attacks. Third-party libraries assessed for known vulnerabilities via Software Composition Analysis (SCA).

VII. INCIDENT RESPONSE AND BREACH NOTIFICATION

A. Security Incident Classification

Security incidents are categorized by severity:

  • Critical: Confirmed breach of Restricted data; active ransomware or destructive malware; complete loss of critical systems; unauthorized access to CDE.
  • High: Suspected data breach; successful phishing with credential compromise; significant malware outbreak; prolonged system outage.
  • Medium: Policy violations; failed intrusion attempts; minor malware infections contained by endpoint protection; unauthorized access attempts (failed).
  • Low: Suspicious activity with no confirmed impact; false positive alerts; minor policy violations.

B. Incident Response Procedures

Incident Response Team (IRT) consisting of IT Manager, Data Protection Officer, General Manager, and external legal counsel (as needed) convenes for Critical/High incidents. Response phases:

  • Detection and Reporting: All personnel required to report suspected incidents to IT department immediately. 24/7 incident hotline available.
  • Containment: Isolate affected systems from network; preserve evidence (disk images, log files); revoke compromised credentials.
  • Eradication: Remove malware; patch vulnerabilities; rebuild compromised systems from known-good backups or clean installation.
  • Recovery: Restore operations with enhanced monitoring; validate system integrity before returning to production.
  • Post-Incident Review: Root cause analysis; lessons learned; policy/procedure updates; staff training.

C. Breach Notification Obligations

Where a breach of security safeguards involves personal information that poses a real risk of significant harm:

  • PIPEDA (Canada): Notification to Office of the Privacy Commissioner of Canada and affected individuals "as soon as feasible"; record of breach maintained.
  • GDPR (EU/EEA/UK): Notification to supervisory authority within 72 hours of breach awareness (GDPR Article 33); notification to data subjects without undue delay where high risk to rights and freedoms (Article 34).
  • CCPA/CPRA (California): Notification to California Attorney General and affected residents; offer of credit monitoring services where applicable.
  • PCI DSS: Notification to payment card brands and acquiring bank within timelines specified in merchant agreement; forensic investigation by PCI Forensic Investigator (PFI) for confirmed payment card breach.

VIII. BACKUP AND BUSINESS CONTINUITY

A. Backup Strategy

  • Critical Systems: Daily incremental backups; weekly full backups; 3-2-1 rule (3 copies, 2 different media, 1 offsite); encrypted backups stored in geographically separate location; quarterly restoration testing.
  • Retention: 30-day retention for daily backups; 12-month retention for monthly snapshots; permanent archival for annual backups subject to retention schedule.
  • Ransomware Protection: Immutable backups (write-once-read-many) to prevent encryption by malware; air-gapped offline backups rotated weekly.

B. Disaster Recovery

Disaster Recovery Plan (DRP) maintained with Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) defined for critical systems. Annual disaster recovery exercises conducted; tabletop scenarios for major incident types (ransomware, fire, flood, prolonged power outage). Alternate processing site agreements in place for extended outages.

IX. THIRD-PARTY RISK MANAGEMENT

Third-party service providers with access to Hotel Julie data or systems are subject to due diligence assessments:

  • Pre-Engagement Assessment: Review of vendor security certifications (SOC 2, ISO 27001, PCI DSS); data processing addendum (GDPR Article 28) or Business Associate Agreement (HIPAA, where applicable); insurance coverage (cyber liability, E&O).
  • Contractual Requirements: Security obligations; breach notification timelines; right to audit; data deletion upon termination; prohibition on sub-processing without consent.
  • Ongoing Monitoring: Annual reassessment; incident reporting; performance reviews; termination rights for material security failures.

X. SECURITY AWARENESS AND TRAINING

All personnel receive security awareness training upon hire and annually thereafter. Training includes:

  • Information classification and handling procedures
  • Password security and MFA usage
  • Phishing recognition and reporting
  • Physical security (tailgating prevention, visitor management, clean desk policy)
  • Incident reporting obligations
  • Social engineering tactics and prevention
  • Acceptable use of IT resources (no personal use of systems handling Restricted data, prohibition on unauthorized software installation)

Specialized training provided for personnel with access to Restricted data, including PCI DSS awareness for those handling payment card data.

XI. MONITORING, LOGGING, AND AUDITING

A. Log Management

Security-relevant events are logged and retained:

  • Authentication events (successful/failed logins, privilege escalation)
  • Access to Restricted data (queries, file access, exports)
  • System changes (configuration modifications, software installations, account creations/deletions)
  • Network traffic (firewall logs, IDS/IPS alerts, VPN connections)
  • Physical access (door access logs, CCTV metadata)

Logs centralized via SIEM (Security Information and Event Management) system; 90-day online retention; 12-month archival; integrity protection via write-once storage.

B. Internal Audits

Annual internal security audits assess compliance with this Policy, PCI DSS, and regulatory obligations. Audits include access control reviews, log analysis, vulnerability assessments, and physical security inspections. Findings documented; remediation plans with target completion dates; follow-up verification.

XII. VULNERABILITY MANAGEMENT

  • Vulnerability Scanning: Quarterly external vulnerability scans by PCI DSS Approved Scanning Vendor; monthly internal scans; scans after significant infrastructure changes.
  • Penetration Testing: Annual penetration testing by qualified third-party firm; testing of web applications, network infrastructure, and wireless networks; remediation of high/critical findings prior to production deployment.
  • Remediation: Critical vulnerabilities patched within 30 days; high-severity within 90 days; compensating controls documented where patching not feasible.

XIII. POLICY GOVERNANCE

A. Roles and Responsibilities

  • Data Protection Officer (DPO): Oversight of privacy and security compliance; breach response coordination; supervisory authority liaison.
  • IT Manager: Technical implementation of security controls; patch management; incident response; vendor management.
  • General Manager: Ultimate accountability for security posture; budget allocation; policy approval; regulatory reporting.
  • All Personnel: Compliance with policy; incident reporting; secure handling of information.

B. Policy Review and Updates

This Policy reviewed annually or following: (i) significant security incident; (ii) material change in regulatory requirements; (iii) substantial changes to business operations or technology infrastructure. Updates communicated to all personnel; acknowledgment of receipt required.

C. Enforcement

Violations of this Policy subject to disciplinary action ranging from written warning to termination of employment or contract. Willful or negligent security breaches may result in civil liability or criminal prosecution under applicable law.

XIV. CONTACT INFORMATION

Questions regarding this Policy or security concerns should be directed to:

Data Protection Officer & Information Security Lead
Hotel Julie
92 St. Vincent St. N.
Stratford, ON N5A 5S8
Canada
Email: Hello@hoteljulie.net
24/7 Security Hotline: 226-271-1765 (ext. 999)

XV. LEGAL DISCLAIMER

This Policy establishes internal standards for information security and does not create contractual rights for third parties. While we employ commercially reasonable security measures, no security system is impenetrable. We disclaim liability for security incidents arising from circumstances beyond our reasonable control, including zero-day vulnerabilities, advanced persistent threats sponsored by nation-states, or force majeure events. This Policy is subject to the laws of Ontario and federal laws of Canada; where mandatory privacy or security laws of other jurisdictions apply (EU/EEA, UK, California), those laws shall govern to the extent of any conflict.