Privacy

Without an account (the free app)

Everything you track is written to your own browser’s local storage and stays there. Clockflux keeps app for your sessions and days off, appSettings for your holiday allowance and start date, hoursFormat for whether you prefer decimal or h:mm, appVisited to remember that you have seen the landing page, setupCompleted to remember that you have been through (or skipped) the quick setup, and appInstallState to remember whether you have installed the app to your home screen or dismissed that offer. None of it is sent anywhere, and there is no server holding a copy. That also means clearing your browser data for this site erases your history for good. Consider Clockflux Pro if you would rather not rely on a single browser.

With an account

Signing in uses Google. Google tells us your name, email address and profile picture, and gives us a stable identifier for your account; we never see your Google password. We store those three details, your plan and, on Pro, your time entries, days off and settings, so they can sync between your devices. Our servers and database are hosted by cloud providers in the EU.

If you connect an AI assistant, we also keep a record of each change it makes for you (a check-in or check-out, a break, a corrected session, days off booked or cleared): which connection made it, when, and the values before and after. You can see it in Settings → AI assistants. It is kept for 90 days and deleted with your account.

Like most servers, ours keeps a log of the requests it handles: when each arrived, which part of the API it was for, how it went, and the IP address it came from. We use it only to keep the service secure and to work out what went wrong when something fails, never for analytics.

Signing in also adds local storage entries on the app: appUser for the cached profile the app renders, appAccessToken for the short-lived token it calls the API with, appLastSyncedSnapshot and appDataOwner (plus appDataOwnerBackups) so sync can tell your data apart from another account’s on a shared browser, clockflux-features-cache for the last list of features your plan unlocks, so the app keeps working while our server can’t be reached, and appHasSignedInBefore, which is deliberately kept even after you sign out, purely so the app can say “you have signed in here before” instead of looking like it silently downgraded you.

Connecting an AI assistant such as claude.ai from its own sign-in page keeps pendingOAuthRequest in session storage while you sign in with Google: the assistant’s connection request, so the app can bring you back to it. It is removed once you answer, and your browser drops it when you close the tab.

Staying signed in needs one cookie: refresh_token, set by our own API on .clockflux.app. It is HttpOnly, so no script can read it, and it exists only to keep your session alive across page loads. It is not used to track you, here or anywhere else.

On this site and the account site

This site (info.clockflux.app) keeps one entry in your browser’s local storage: clockflux.blog.read, the blog posts you have opened, so their “New” badge goes away once you have read them.

The account site (account.clockflux.app), where you see the price and upgrade, keeps clockflux:language in local storage to remember the language you chose, and clockflux:returnTo in session storage, which lasts only as long as the tab and is ignored after ten minutes, to bring you back to the page you were on after signing in with Google. Signing in there also stores its own appUser and appAccessToken, as the app does.

The read posts, the language and the return-to page never leave your browser. None of these entries is used to track you, and clearing your browser data for that site removes them.

Emails we send you

If you have an account, we may email the address Google gave us about Clockflux itself: a welcome email when you create your account, new posts on the Clockflux blog, news about the product and a weekly summary of your hours, if you turn it on. We tell you this when you sign in, and you can stop these emails at any time: every one of them has an unsubscribe link, which works in one click and needs no sign-in. Unsubscribing does not affect your account or your data. We send these emails because you are a Clockflux user, on our legitimate interest in telling you about the product you use. We never send emails on behalf of anyone else, and we never share your address with anyone but the provider that delivers them.

Emails are delivered by Resend, from news@clockflux.app, and replies go to info@clockflux.app. Resend receives your email address and the content of each email, and tells us when an email cannot be delivered or is marked as spam. If that happens, we stop emailing that address. We store whether, and since when, you have unsubscribed, so we keep respecting it.

If you turn on the weekly summary, we also store your time zone so it arrives on Sunday evening your time, and the email contains your hours, target and overtime balance, so Resend receives those figures too. It stops when you turn it off in Settings, use the link in any summary, or leave Pro.

Paying for Pro

Payments are handled by Stripe, which is the merchant of record for the sale. Your card details go to Stripe and never touch our servers. We store a Stripe customer and subscription identifier against your account, plus your plan and renewal date, so we know what you are entitled to. Stripe keeps the invoice and tax records the law requires it to.

Analytics

The site uses our hosting provider’s privacy-friendly analytics to count visits. It records page views and referrers only. It sets no cookies, it does not follow you to other sites, and it never sees the hours you log. To tell repeat visits apart it derives a hash from your IP address and browser details, which is discarded and regenerated each day, so it cannot be used to recognise you over time. That processing rests on our legitimate interest in knowing roughly how many people use Clockflux.

The app also uses the same provider’s performance monitoring to measure how quickly its pages load. It sends load-time measurements along with the page address and your connection type. Like the analytics, it sets no cookies and never sees the hours you log, and it rests on the same legitimate interest, in keeping the app fast.

There is no cookie banner because there is nothing to ask you about. The only cookie we set is the sign-in one described above, which is strictly necessary for a feature you asked for, and analytics sets none at all.

Your data, and getting rid of it

We do not sell your data, we do not use it to build a profile of you, and we do not use it to train anything. You can export your entries from the app at any time. You can delete your account from Settings, which cancels any subscription and erases everything we hold for you. The one exception is the invoice and tax records Stripe and we are legally required to keep. Deleting your account does not touch the copy in your own browser.

While you have an account, we keep your data for as long as the account exists. On Pro we also keep earlier versions of your synced data for 30 days, so a sync that wipes or loses entries by mistake can be undone; deleting your account erases those too. Sign-in sessions expire on their own within 30 days of last use.

You have the right to access, correct, export or erase your data, and to object to the analytics processing above. Email info@clockflux.app and we will sort it out.