Privacy commitments in plain language

Only the minimum needed to show you your attention patterns:

• App identity: The name and ID of whichever app is in the foreground. Nothing about what's inside it.
• Timing: When an app was active, how long you used it, and whether your device was idle.
• Device info: A generated device ID and your platform (macOS or Windows) so you can track across machines.
• Your edits: Any custom categories, labels, or manual corrections you make to your timeline.

• No screenshots, screen recordings, or audio
• No keystrokes or text input
• No document, message, or email content
• No browser URLs or page content
• No location data

Lapse sees that you switched to Chrome. It has no idea what you looked at.

Your data lives locally first in a database on your machine. If you sign in, a minimal set of timing data syncs securely to your account so you can access insights across devices. Idle time stays local unless you've manually edited it.

Yes. Lapse requires an account, so app identity and timing data sync securely over HTTPS. Lapse never transmits content such as keystrokes, messages, documents, screenshots, or URLs.

Only you. There is no anonymous telemetry, no usage analytics piped back to us, and no sharing by default. Your attention data is yours.

No. Your data is never sold, never shared with advertisers, and never used to build profiles for anyone other than you.

No. Lapse is a personal tool. There is no admin dashboard, no team reporting, and no way for anyone else to access your data unless you explicitly grant it.

You have full control:

• Local data: Delete the app's data folder on your machine and it's gone.
• Synced data: Remove your account to delete all synced history.
• Quit the app at any time to stop tracking entirely.
• Data deletion/GDPR requests: Email [email protected] and we'll process your request.

Your manual edits always take priority over automatically tracked data. If you delete an entry locally, it's also removed from your synced account on the next sync.

All sync traffic is sent over HTTPS. Data is only transmitted when you're signed in, using a short-lived authentication token.