How Clockit handles your data

Last updated: January 2025

Clockit is built to track coding time with minimal data collection. This policy explains what we collect, how we use it, and the choices you have.

What we collect

Coding session metadata (start/end times, duration, idle time).
Per-file and per-language focus durations for analytics and exports.
Optional context you add, such as issue keys or comments.
Account identifiers when you sign in to sync data to your dashboard.

How we use data

To show dashboards, summaries, and productivity stats you request.
To export sessions to sinks you enable (CSV, Jira, Notion, cloud backup).
To improve reliability and detect issues (minimal diagnostic logs).

Where data lives

Locally: CSV exports stay on your machine unless you move them.
Cloud: If you enable cloud backup or sign in, session data is stored in your Clockit account.
Third parties: Only when you connect a sink (e.g., Jira, Notion) and trigger an export.

Sharing and selling

We do not sell your data. We share data only to services you explicitly connect and authorize.

Retention

Data remains until you delete it or request removal. Local CSVs remain on your device. Cloud data can be cleared by deleting uploads/aggregates or contacting support.

Your choices

Disable sinks or cloud backup at any time.
Delete CSVs locally and remove uploads from your account.
Request account or data deletion by contacting support.

Contact

Questions or data requests? Reach out through the contact details in our docs or your support channel.