Privacy

Everything is stored on your Mac

Deylee writes every day, every segment and every setting to a SQLite database in your own home folder, at ~/Library/Application Support/deylee/deylee.sqlite. The app reads only from that file, never from a server, and the file is yours — you can open it, copy it, back it up or delete it without asking us.

An account is required to track time

Deylee will not start a day without one. You can install the app and open it signed out, but pressing Start raises sign-in and the timer begins only if that succeeds. This page said the opposite until 8 August 2026, while the app was changed to ask; it is corrected here rather than left to be discovered, because an account described as optional when it is mandatory is the one kind of error a privacy policy must never make.

What the account does not change is where your hours live. They are still written to your own machine first and read only from there, so after the first sign-in the app keeps working with no network at all — your session is stored locally and is not re-checked against a server before the timer will run.

Company accounts — where a manager can see the hours their team logged — are being built and are not in the app yet. When they arrive, this page will describe what a manager can see before the feature is switched on, not afterwards.

What is sent when you are signed in

Only the record of your hours. A synced segment carries its identifier, the day it belongs to, whether it was work or a break, when it started, when it ended, and any note you typed on it — a note is free text you wrote, so treat it as something that leaves your machine rather than a private scribble. Days carry their date and your target.

Two housekeeping values travel with them. A device identifier — a random identifier generated once when you install Deylee — lets your machines tell their own writes apart from each other’s. A position marker records how much of your own history you have already received, so a sync resumes instead of starting over. Neither describes you or your work, and that is the whole payload.

Totals are never transmitted. Every figure you see is derived by summing segments on the device showing it, which means there is no aggregate of you stored anywhere.

What Deylee never collects

Not on a paid tier, not as an admin setting, not by request:

• No screenshots and no screen recording.
• No window titles, document names or file names.
• No application names and no URLs or browsing history.
• No keystroke logging and no mouse or activity monitoring.
• No productivity scores and no ranking of people against each other.
• No webcam access, no location, no microphone.
• No analytics and no telemetry of any kind.

This is an architectural commitment rather than a policy we could quietly revise: the app never gathers this material in the first place, so there is nothing to transmit, subpoena or leak. If a future version of Deylee suggests work from local activity, the suggestion stays on the disk that observed it — you confirm a duration, and only the duration syncs.

Your account

There are two ways in, and they can both belong to the same account.

With Google, we receive the email address and name on that Google account, which is how your devices recognise each other. We do not receive your Google password, and Deylee asks for no access to your Gmail, Drive, Calendar or contacts.

With an email address and a password, we store the address and a bcrypt hash of the password — never the password itself. A hash cannot be reversed, so we cannot read your password, cannot email it back to you, and cannot hand it to anyone who asks for it. The token that keeps you signed in is stored the same way, as a digest rather than the token.

Who else touches it

The synced copy lives in a Postgres database hosted by Supabase, which holds your hours in order to store and serve them and for nothing else. Signed out, it is never contacted. There is no analytics provider, no advertising network and no data broker in the list, because there is no analytics.

Deleting your data

Deleting the local database removes your local history immediately. The two copies are separate on purpose — signing out should never wipe hours you have not been paid for yet.

For the synced copy there is no self-service delete button yet. Write to the address below and we remove your account and its hours by hand; we will confirm when it is done. One detail worth knowing in the meantime: when you delete a segment in the app, the row is marked deleted rather than erased outright, so that the deletion reaches a laptop that was asleep instead of the hours reappearing on it. Closing your account removes those marked rows too.

Asking about any of this

Write to me. If a claim on this page ever stops being true, it gets corrected here rather than dropped quietly.