The employee is the user. The employer is a recipient.

The controller of your personal data is Louis Mateu, trading as Khronolog. Write to privacy@khronolog.com about anything in this policy.

Operator

Louis Mateu, trading as Khronolog

Legal form

a sole trader (eenmanszaak) registered in the Netherlands

KvK

99671417

BTW

NL005402732B33

Address

Nieuwe Osdorpergracht 374-G, 1068 HV Amsterdam, the Netherlands

Email

privacy@khronolog.com

The desktop app keeps its record on your computer: the apps and windows you use, titles, file paths, URLs, idle time, background video and calls, and the contents of snapshots, documents and the code in your commits. We never receive it, except one name per block, which you can read about under “Your own copy of your blocks” below. Neither do we see:

• AI requests. They go from your computer straight to the provider you chose, with your own key, and only when you click.
• Your calendars and Slack. The app reads them directly from Google, Microsoft or Slack onto your computer.
• Invoices you open in Google Sheets. The web app makes the spreadsheet from your browser straight into your own Google Drive. We keep only its link, and never your Google access.

The one exception is a bug report, when you tick the box to attach the app's log or a screenshot. The log can contain window, meeting and video titles, and the form says so before you send it.

• Your account: email address, name and picture (from Google if you sign in with it), and sign-in records. Needed to provide the service you signed up for (performance of a contract, GDPR art. 6(1)(b)).
• Organisation work, if you join an organisation: the blocks you share (start, end, project, task, note, shared tags), projects, tasks and boards, your work hours and time zone, your role and teams, invites, and the organisation's activity log. Needed to run the organisation you joined (art. 6(1)(b)). For a team, the organisation is usually the controller and we process this on its behalf (see the terms, which are our data processing agreement). On a block you tick to share, this includes its notes, its summary and the list of what you made in it.
• Your own copy of your blocks, if you're in an organisation: each block's name, notes and summary, the personal project and tags on it, and a short list of what you made in it (commit messages and line counts, After Effects versions and change counts, document change counts with a few lines of where the changes were, finished renders; never file paths, code or document text). A block you didn't name carries the name the app shows for it, taken from what was on screen: a meeting's title, or the file, repository or web page it was mostly about. Only you can read it: not your colleagues, not your organisation's admins. It is stored on our servers, so the people who run Khronolog could technically access it, and we don't except to keep the service running or when the law requires it. We keep it so your web timesheet is complete (art. 6(1)(b)). You can switch it off in the app under Settings → Team Sync, which empties what was sent. If you leave the organisation, you keep your hours, the projects they went to and the details of your private blocks; the organisation decides whether you keep your notes on its work.
• Billing, if your organisation has a paid plan: the billing contact's name and email, the business's name, address and VAT number, the plan, seats, payments and invoices. Card details go straight to Stripe. To run the plan (art. 6(1)(b)) and keep the records Dutch tax law requires (legal obligation, art. 6(1)(c)).
• Bug reports: your description, the app's diagnostics (versions, operating system, screen, sync state) and, only if you tick them, the log and a screenshot. To fix what broke (our legitimate interest, art. 6(1)(f); the attachments on your choice).
• The waitlist: your email address and, if you pick them, your role and apps. To tell you about the pre-release and send occasional updates (your consent, art. 6(1)(a), which you can withdraw with the link in every email).
• Visits to the website: anonymous, cookie-free statistics (pages viewed, rough location, device type, load speed) through Vercel Analytics and Speed Insights. To see what people read and keep the site fast (legitimate interest). We set cookies only to keep you signed in and remember view settings; none are used for advertising.
• Email you send us, to answer it (legitimate interest).

We don't sell personal data, show ads, or make automated decisions about you.

These providers handle data on our behalf, under data processing agreements. Where data leaves the EU, the transfer relies on the EU–US Data Privacy Framework or the European Commission's standard contractual clauses.

If you sign in with Google, Google handles that sign-in as its own controller under its own privacy policy. Other members of your organisation see what the organisation is allowed to see (above); nobody else gets your data unless the law requires it.

• Your account and what you shared: until you delete your account, then within one month.
• An organisation's shared work: until the organisation is deleted.
• Your own copy of your blocks: until you switch it off or delete your account. After you leave an organisation, until that organisation is deleted.
• Invoices and payment records: seven years, as Dutch tax law requires.
• Records of sign-in emails: 90 days.
• The waitlist: an address nobody confirms is deleted after 30 days; a confirmed one until you unsubscribe or ask.
• Bug reports: until they're no longer needed to fix the problem, or you ask us to delete them.
• Backups held by our database host drop deleted data on their own short schedule.

You can ask to see, correct, export or delete your data, to restrict or object to how we use it, and withdraw any consent you gave. Email privacy@khronolog.com from the address on your account; we answer within one month. If your data is in an organisation, we may pass your request to the organisation's owner, who decides about that data. You can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens, or the authority where you live.

Data travels encrypted. In the database, each row is readable only by the people its organisation allows, enforced by the database itself rather than the app. Card details go to Stripe and never touch our servers. Khronolog isn't meant for anyone under 16.

We'll update this policy when what we do changes, and ask you to accept again when the change matters. When Khronolog moves into a company, that company becomes the controller and we'll tell you first (see the terms).