Your focus log belongs on your Mac.
Lockdown is designed around local session data and explicit macOS permissions. This page explains what the app stores, why permissions are requested, and how to remove access.
What Lockdown Stores
- Session names, start/end times, durations, timer mode, and Pomodoro count.
- Blocking Setups, optional tags, and recent start defaults.
- Active-session recovery state in `state.json` while a session is running.
- SQLite history at `~/Library/Application Support/Lockdown/lockdown.db`.
What Leaves Your Mac
Lockdown does not send your session names, tags, time log, or blocking setup content anywhere. There is no account and no cloud sync in the current product.
Session history can be exported manually to CSV or JSON from the Time Log. Those files go only where you choose to save them.
Why Permissions Are Requested
- Network Extension
- Website blocking uses a macOS Network Extension so Lockdown can block configured domains while a session is active. macOS asks you to approve this in System Settings.
- Accessibility
- App blocking uses Accessibility permission so Lockdown can close configured distracting apps by bundle identifier. Lockdown asks only if your Blocking Setup includes blocked apps.
How To Revoke Access
- Network Extension: System Settings → Network → Filters, then disable Lockdown.
- System Extension approval: System Settings → Privacy & Security.
- Accessibility: System Settings → Privacy & Security → Accessibility.
- Local data: delete the Lockdown folder in Application Support after quitting the app.
Diagnostics
Lockdown's Diagnostics screen shows blocking and permission status. A support export should include technical status without session names, tags, or full history by default.