Screen Privacy for Government Employees and Civil Servants

You're at a federal training session in Arlington. The hotel conference room has tables packed close. The person to your left works for a different agency, one with a different mission, and the briefing you're catching up on between sessions is internal to your bureau. You don't think much about it until the person leans slightly during a break and you realize their angle on your screen is better than yours.

Government work assumes a chain of custody that breaks down the moment a laptop opens in a hotel lobby.

What's on your screen

The document mix depends on the agency, but a typical civil servant's laptop touches:

• Classified material (where authorized), often at the SBU, FOUO, or CUI level
• Citizen records, tax returns, benefits applications, immigration files
• Internal policy memos before public release
• FOIA-exempt material, including the (b)(5) deliberative process documents
• Personnel actions, disciplinary records, security clearance adjudications
• Procurement source selection documents, which can move markets
• Law enforcement sensitive information, including investigative notes
• Inter-agency correspondence that might never become public

The CUI category alone covers everything from grant applications to OSHA inspection notes. Most federal employees handle it daily without thinking about it as sensitive.

Where shoulder surfing happens for government employees

Federal training sites and hotel conference rooms. Open-plan agency offices, which became more common after the post-2009 space consolidation push. Telework from public spaces if your agency allows it. Airline travel between regional offices and headquarters. Inter-agency meetings on third-party premises. Co-located task forces where personnel from multiple agencies share a workspace. The hearing room hallway during recesses.

Open-plan federal workspace is its own challenge. The OPM-style cubicle farm has been gradually replaced by hoteling and open floor plans where your seat changes daily.

The unique risks

The exposure layer here is regulatory, criminal, and career-ending.

Clearance levels: viewing or disclosing material above one's clearance, even passively, is a security incident that gets reported. A screen visible to an uncleared person at a hotel is exactly the scenario the incident report templates anticipate.

FISMA: the Federal Information Security Modernization Act requires agencies to maintain controls over information systems. Workstation observation is one of the controls.

Criminal exposure: the Privacy Act of 1974 imposes criminal penalties for willful disclosure of protected records, and 18 USC 798 covers communications intelligence specifically.

OPM and OIG investigations: an inspector general investigation can be triggered by an observed disclosure, and it tends to be career-ending regardless of intent.

FOIA timing: documents protected under deliberative process (b)(5) lose protection if they're disclosed, including casually. A leak resets the legal posture of the document.

The hotel lobby briefing read by an uncleared person is a security incident report waiting to be filed. The fact that nothing classified was visible doesn't matter.

Practical methods

Federal work patterns are increasingly mobile, and the methods need to fit.

Privacy filter on the GFE laptop, mandatory in most agencies, but actually installed less often than policy claims. Verify yours.

Read CUI only in approved spaces. The hotel lobby is rarely an approved space. The hotel room with the door locked usually is.

Lock the screen for every break, every time. The Cmd+Ctrl+Q habit is non-negotiable in shared environments.

Use the agency's approved travel laptop posture, which usually means the smaller second device, not the main workstation, when on the road.

No CUI on phone screens in public. The phone is easier to read at distance than people assume, especially in airport lounges.

Separate browser profile for OGA correspondence. Inter-agency work often involves names that, if seen by the wrong person, telegraph an investigation or a task force.

Where camera-based detection fits in

Be honest about the limits here. Camera-based detection is not approved for SCIF environments. It is not part of any agency's accredited control set. What it is, is a personal awareness layer for the unclassified-but-sensitive work that happens in non-SCIF places.

Peeker runs locally on the Mac, watches for faces behind you, and shows a small preview in the corner. Nothing leaves the device. Nothing is recorded. For a civil servant working CUI from a hotel room or a regional office hot desk, that awareness layer can prevent the casual exposure that triggers an incident report.

It is not for classified work. Classified work has its own controls.

FAQ for government employees

Is Peeker approved for FedRAMP environments? No. FedRAMP applies to cloud services that process federal data. Peeker is a local utility that processes no federal data, only camera frames discarded immediately. It's outside the FedRAMP scope.

Can I install it on a GFE laptop? Only with your IT security office's approval. The app is signed, notarized, and uses standard macOS camera entitlements. Most personal productivity utilities require a request through your ISSO.

Is the camera always on while it runs? Yes, while the app is active. You can disable it with one click in the menu bar. Many users disable it when entering a SCIF or secure space.

Wrap

Government work assumes controlled environments that don't actually exist anymore for most civil servants. Peeker is $5/year, and covers the unclassified awareness gap. Use it where appropriate, never where it isn't.