Security and privacy

Security for workforce monitoring

How SnitchOS separates client data, controls access, and proves the software is ours.

Client separation

Each client's information is kept separate

Separate records

Activity and settings are tied to the client they belong to.

Separate files

Screenshots and generated reports are stored under the correct client account.

Assigned access

People can view or change information only for the clients assigned to them.

Authentication and access

Secure Microsoft sign-in and clear roles

Microsoft Entra sign-in

Approved users sign in with their Microsoft account instead of a separate dashboard password.

Client assignments

Admins can work across the account. Managers see only the clients assigned to them.

Full or read-only access

Choose whether each manager can make changes or only review information.

Software integrity

Signed software and verified updates

Verified Windows software

  • The installer and Windows service are digitally signed.
  • The service is visible and removable by a local administrator.

Check the signature before you deploy — the publisher should be OS Labs Inc. or Shield Management Inc:

Get-AuthenticodeSignature .\SnitchOS.msi |
  Select-Object Status, @{n='Signer';e={$_.SignerCertificate.Subject}}

Expect Status: Valid and a subject containing either CN=OS Labs Inc. (current installers, issued by SSL.com) or CN=Shield Management Inc (older installers, issued by Microsoft). SnitchOS is a product of OS Labs Inc; we are mid-move from one signing certificate provider to the other, so both names are legitimate publishers to expect.

Verified updates

  • Updates are checked against the expected publisher before installation.
  • The downloaded package is checked for unexpected changes.
  • Older versions are not installed over newer versions.
Agent and dashboard traffic uses TLS 1.2 or 1.3, with TLS 1.3 negotiated by default. Every SnitchOS host sends Strict-Transport-Security: max-age=31536000; includeSubDomains. Databases and screenshot storage have no public listener; operators reach them only through authenticated accounts.

Data collection

Input volume is counted; typed content is not recorded

Collected from Windows devices

  • Current application, window title, user, and active or idle status
  • Application and website activity
  • Keystroke, mouse-click, and mouse-distance counts
  • Screenshots every 60 seconds — always on, skipped while idle, identical frames discarded
  • Basic device and service-health details

Not directly collected

  • Keys pressed or content typed
  • Clipboard, file, or message contents
  • Audio, microphone, or webcam data
  • Saved passwords, URL query strings, or URL fragments

Screenshots, window titles, and URL paths can still expose sensitive information — set access accordingly, and pause monitoring for anyone your policy excludes.

Default retention

  • Screenshots stay in primary storage for 30 days, move to archive storage, and are deleted at 365 days. The Privacy Policy and DPA call these two tiers hot and cold (primary/archive).
  • Activity events are kept indefinitely by default, because the value of the product is historical comparison. Pruning is one platform-wide setting, off today and not configurable per client.

These are platform-wide defaults, not per-client settings. Screenshot expiry runs regardless of the activity-log setting.

Compliance position

  • Controls are aligned to the AICPA Trust Services Criteria, with SOC 2 evidence collection underway. There is no completed SOC 2 attestation today, and we will not imply otherwise.
  • Sub-processors are named in DPA §7.1. Payment details go to Stripe; endpoint data does not.

Responsible deployment

Designed for disclosed monitoring

Use SnitchOS only on company-owned or controlled Windows devices you are authorized to manage.

Customers are responsible for lawful use, required notice or consent, and appropriate access. Requirements vary by location; involve counsel before rollout.

Deployment checklist

  • Confirm the devices are eligible for workplace monitoring.
  • Provide notice and obtain required consent before collection starts.
  • Document who can see screenshots and detailed activity.
  • Set client access to match policy, and pause monitoring for anyone the policy excludes.

Review the notice template

14-day pilot

Test the controls before a wider rollout

Use one client and one Windows device to confirm access, data collection, deployment, and uninstall behavior.

Start your 14-day pilot Read the docs