1. Summary of Request
We are requesting a modification to the default logging behavior of URLs within the HCL Notes Client. Currently, hovering over a URL (mouseover) automatically logs the URL into the "Notifications --> Status" tab. To comply with European data protection laws (GDPR) and international IT security standards (e.g., BSI IT-Grundschutz), this behavior must be disabled by default. Mouseover events should only display in the Status Bar, while logging to the Client Status Notifications (Bell Icon -->Notifications --> Status) should be strictly reserved for actual user clicks.
2. Current Behavior
When a user hovers a mouse cursor over a URL in the Notes Client, the URL is simultaneously displayed in the Notes Status Bar and logged in the "Bell Icon -->Notifications --> Status" register. HCL Development has currently classified this 1:1 synchronization as "Works as Designed."
3. Requested Behavior (Proposed Solution)
To establish compliance with the European market, the client behavior must be adjusted to follow a "Privacy by Default" approach:
Requirement 1: Change Default Mouseover Behavior Automatic logging of links in the Notification Center upon a mere mouseover must be disabled by default. Displaying the URL temporarily in the Status Bar is completely sufficient for user orientation.
Requirement 2: Restrict Mouseover Logging to Debugging Mouseover logging in the Notification Center should only be activatable temporarily for administrative diagnostic purposes, controlled via a dedicated configuration parameter (e.g., a specific notes.ini flag).
Requirement 3: Retain and Harden Click Logging The actual clicking of links must continue to be logged consistently, securely, and in an audit-proof manner within the Notification Center.
4. Business & Compliance Justification
The current product design neglects fundamental legal requirements and creates a compliance deficit for European enterprise customers. This request is driven by the following critical factors:
A. Data Privacy & GDPR Compliance
Data Minimization (Art. 5 (1) (c) GDPR): Default logging of unintentional cursor movements generates massive amounts of data without a specific processing purpose.
Illegal Behavioral Monitoring: Logging every mouseover effectively maps the reading behavior of employees. For public and private sector entities, this constitutes impermissible behavioral monitoring, which is legally prohibited without strict agreements with employee representation (Works Councils/Staff Councils).
B. IT Security & Audit Integrity (BSI IT-Grundschutz)
Audit Log Dilution: Security standards (e.g., BSI IT-Grundschutz Module OPS.1.1.5) require purpose-driven logging of security-relevant events. A fleeting mouseover does not trigger external network data flow. Storing these events dilutes audit logs and severely increases the risk of false positives, as security systems may falsely interpret a mouseover as an actual website request.
Data Leakage Risk: URLs frequently contain sensitive session IDs, tokens, or personal information. Uncontrolled replication of these URLs into the local Notification Center increases the attack surface for unauthorized data access on the endpoint.
C. Effective Incident Response In contrast to a mouseover, an actual click is a conscious user action legally justified by the organization's legitimate interest in securing its IT infrastructure (Art. 6 (1) (f) GDPR). Only by restricting logs to actual clicks can IT security teams accurately identify and isolate affected endpoints during malware or phishing incidents.
