Notifications
Clear all
Topic starter
02/08/2026 12:30 pm
TL;DR: Shared computers can leave pay statements, tax documents, and other sensitive records visible to the next user, and Island describes a browser-based policy approach that warns on access and deletes records after use. The governance problem is not just browser hygiene, but enforcing privacy controls across shared endpoints and regulated workflows.
NHIMG editorial — based on content published by Island: WWLW Ep. 21, The Case of Employee Privacy on Shared Devices
Questions worth separating out
Q: How should organisations protect sensitive employee documents on shared computers?
A: Use context-aware controls that warn users before sensitive documents open on shared endpoints and remove residual records after the workflow ends.
Q: Why is shared-device access a privacy risk even when authentication is correct?
A: Authentication only proves the right person opened the document.
Q: What do security teams get wrong about shared workstation privacy controls?
A: They often treat the issue as a user behaviour problem instead of a lifecycle problem.
Practitioner guidance
- Define shared-device document handling rules Classify which employee records can be opened on shared endpoints and require browser-side warnings for those document types before access begins.
- Add automatic post-session deletion Delete cached records, desktop copies, and local artefacts when a shared-device workflow ends so the next user does not inherit residual exposure.
- Align privacy controls with regulated workflows Map payroll and tax document handling to the privacy obligations that apply in each region and verify the control works across those jurisdictions.
What's in the full article
Island's full post covers the operational detail this post intentionally leaves for the source:
- Workflow examples for handling sensitive employee records on shared computers
- How the browser warns users at the point of access and removes records after use
- The privacy and legal considerations behind shared-device document handling
- Practical guidance for organisations operating across multiple state and federal privacy regimes
👉 Read Island's case study on protecting employee privacy on shared devices →
Shared-device privacy leaks: what IAM and privacy teams need to fix?
Explore further
02/08/2026 1:28 pm
Shared-device privacy is a lifecycle problem, not just a browser problem. The exposure in this case came from the gap between authorised access and unmanaged persistence on a shared endpoint. That gap matters because employees often need legitimate access to payroll and tax records, but the organisation still has to govern what remains on the device after the session ends. The practitioner conclusion is that session closure and data removal must be treated as part of access governance.
A question worth separating out:
Q: Who is accountable when employee pay or tax documents are left visible on a shared device?
A: Accountability usually sits across privacy, legal, IT, and security because the exposure involves both data handling obligations and endpoint control. The organisation must be able to show that it governed the access path and the post-use state of the data, especially where regional privacy laws apply.
👉 Read our full editorial: Shared-device privacy leaks expose the limits of browser controls
