Security and privacy
SnitchOS separates client data, scopes access, and verifies its own software.
Separate data, scoped access
Separate per client
Activity, screenshots, and settings, per client.
Microsoft 365 or Google sign-in
No dashboard passwords; sign in with Microsoft 365 or Google.
Scoped roles
Admins see everything; managers see only assigned clients.
Signed software and verified updates
Verified Windows software
- Installer and service are code-signed and visible; any local admin can uninstall.
Publisher: OS Labs Inc. or Shield Management Inc (older); both ours. Check the signature.
Verified updates
- Publisher and package integrity verified; no downgrades.
All traffic is TLS 1.2/1.3 with HSTS; no public database or screenshot endpoint.
Counts, not content
Collected from Windows devices
- Active app, window title, user, active or idle
- Apps and websites used
- Keystroke, click, and mouse-distance counts
- Screenshots every 60 seconds by default, idle and duplicates skipped
- Device and service health
Not directly collected
- Keys or content typed
- Clipboard, files, or messages
- Audio or webcam
- Saved passwords or query strings
Screenshots and URLs can still show sensitive content; limit viewers.
Default retention
- Screenshots: 30 days live, archived, deleted at 365 days.
- Activity events: kept indefinitely.
Platform-wide defaults, not per-client settings.
Compliance position
- No SOC 2 attestation yet; controls follow AICPA Trust Services Criteria, evidence collection underway.
- Sub-processors: DPA §7.1. Stripe sees payment details only, never endpoint data.
Designed for disclosed monitoring
For company-owned Windows devices you're authorized to manage.
Notice, consent, and lawful use are on the customer; consult counsel.
The agent runs as a visible service that any local admin can remove with msiexec /x. Disclosure comes from your notice.
Deployment checklist
- Confirm devices are company-owned.
- Give notice; collect required consent.
- Record who can view screenshots.
- Match access to policy.