Privacy & local

Døgn is built as privacy-first time tracking: time data is stored locally on your Mac by default, while configured webhooks and connected MCP clients form explicit integration boundaries. This chapter sums up what that means in practice.

What stays on your Mac

Døgn stores time data in local Core Data by default. The privacy summary under „Settings → General" names the boundaries explicitly:

• Time data is stored locally on your Mac by default.
• No cloud synchronization of your time data.
• No telemetry or usage tracking.
• Configured HTTPS webhooks send selected time-entry, timer, client and project payloads.
• Connected MCP clients can read local suite data; their own network behavior applies.
• App updates and license checks are operational connections and contain no time entries.

When Døgn goes online

App updates and license checks create operational network traffic but contain no time entries. If you configure HTTPS webhooks, they send the selected payloads to your endpoint. The local MCP server exposes suite data to the connected client; that client's own network and privacy behavior is outside Døgn. Collaboration with folo runs locally through the shared app container. Billing is separate: Døgn publishes time entries through the local KveikGraph, and tjent owns the living invoice-draft workflow.

Your data in your hands

Døgn does not operate a cloud store for your time data. Through the CSV export in the popover (see Reports) and the backups (see Backup & data), you always have your times available as your own files.