Your time data, not your manager's surveillance feed.
No screenshots. No keystroke logging. No screen recording. DevClocked tracks your output, sessions, commits, and focus time, without watching your screen.
Privacy surface
Privacy is a product boundary, not a promise.
Most time trackers prove presence with screenshots, keystrokes, app monitoring, and webcam snapshots. DevClocked records operational metadata, sessions, repos, languages, commits, focus windows, while source code, screenshots, keystrokes, and personal browsing stay outside the system.
Transparency
What we track vs. what we never touch.
What we never track
- Screenshots (ever)
- Keystroke counts or patterns
- Webcam or microphone
- Screen recording
- App names or window titles
- File contents or source code
- Personal browsing history
- Mouse movements or click patterns
What DevClocked tracks
- Session start and end times
- Active vs. idle duration
- Repository and branch names
- Commit messages (metadata only)
- File names (not contents)
- Languages detected
- Dev-domain browser time (opt-in)
- Focus windows and context switches
Comparison
Surveillance trackers vs. DevClocked
Architecture
How your data stays private.
No vague "military-grade" promises. Here's exactly how DevClocked handles your data.
Your data, your control
All tracking data is associated with your account. You can view, edit, or delete any session at any time. No approval workflows. No manager locks.
Metadata only in transit
Only summary metadata leaves your machine, session duration, repo names, language stats. Raw file contents and source code never leave your workstation.
Full export, any time
Download your complete history in JSON format. No data lock-in, no retention traps. Delete your account and all data is permanently removed.
Local-first processing
Sensitive data never leaves your machine.
The DevClocked extension processes activity events locally. Only high-level summaries are synced to the cloud for your dashboard. File contents, full paths, and source code stay on your workstation.
Data boundary
What stays local vs. what syncs.
Stays on your machine
Syncs to your dashboard
Frequently Asked Questions
Everything you need to know about DevClocked
No. Never. DevClocked tracks activity metadata, session timestamps, repo names, file names, and language stats. It never captures your screen, webcam, keystrokes, or app windows.
No. DevClocked doesn't capture screen activity. When team features are available, managers will see session summaries (duration, project, languages), never file contents, browsing history, or per-keystroke data.
Session start/end times, active vs. idle duration, repository and branch names, commit messages, file names (not contents), programming languages, and optionally developer-domain browser time. See the full list above.
Yes. Delete individual sessions, entire date ranges, or your full account. When you delete data, it's permanently removed, not archived or retained.
Those tools are surveillance-first, screenshots, keystroke logging, app monitoring, webcam snapshots. DevClocked is output-first, it tracks what you produced (sessions, commits, focus time), not what your screen looked like while you worked.
Privacy is the default
Track your work without being tracked.
Your code. Your data. Your choice. Free tier, no credit card required.
Start Tracking Free