By using the app, the site and the client page you agree to what is written below. The text was written by the author, not by a generator.

Who is who

How to read this text

There is no legal jargon here wherever it can be avoided. “We” is the author of the app, one person. “You” is whoever uses it.

Words you will meet below

Here is what they mean:

• Account — signing in with Telegram. Almost everything works without it: an account is only needed for the cloud part.

• Author — the individual who made WorkClient and answers for it. Not a company and not a registered business: one person.

• We — this is what the author of WorkClient is called in this text.

• Cookies — small files a site puts in your browser. We have exactly as many as it takes for the client page to recognize you.

• Law — Russian.

• Device — the computer, phone or tablet you open the app, the site or the client page from.

• Personal data — anything that can identify a particular person.

• Service — the macOS app, the iPhone app, the site and the client page.

• Who gets the data — the services WorkClient cannot work without: Supabase keeps the cloud part, Telegram signs you in, OpenRouter passes requests to the Claude model, Resend sends emails to your client, Sentry takes error reports. Nobody else.

• Usage data — what is collected on its own: the address the site was opened from, which browser, which pages and how long.

• Site — this address right here, and the client page lives at portal.uxcode.agency: https://workclient.app

• You — the person who opened the app, the site or the client page.

What is collected and why

The main thing: your data sits on your computer

What exactly the app reads

Projects, tasks, time, rates, invoices, clients, the board, the notes by the notch and the clipboard history are kept in a database on your Mac. The iPhone app keeps no database of its own: it shows the cloud part and keeps on the phone only the last snapshot it showed, so the screen isn’t empty when there is no connection. The app works without the internet, and then nothing leaves at all. Only what you switched on yourself goes to the cloud:

• signing in with Telegram — it sends the account number, the name and the username; Telegram gives us no phone, no email and no photo

• sync between machines, project files and the client page — if you switched them on

• the usage data of the site — the address you came from and the pages you looked at

What the site collects

The notes by the notch and the clipboard history never go to the cloud — they live only on your computer.

The app works out where your working day went: every five seconds it looks at which app is in front and what the title of its window says. It takes no screenshots, reads no keystrokes, pulls no page addresses out of the browser — only the window title. If nobody touches the mouse or the keyboard for five minutes, nothing is written down.

Raw activity records don’t go to the cloud — they stay in the database on your computer. But once an hour and once a day the app names and window titles are sent to the model, so that it sorts them into work or personal and puts together the day’s summary. Project and task names, public comments and the earnings for the period go with them.

Every five minutes the names and icons of apps that are new to us go into a shared catalog: it is how everyone learns what an app on a computer actually is. There is nothing personal in it — only the app’s name and its icon.

Cookies and tracking

We have no advertising or tracking cookies. No counters, no pixels, no passing data to ad networks. There is only this:

• The client page sign-in cookie. It is how the client page remembers that a link with this code has been opened already. Block cookies and you will have to enter the code on every page. If you have not set your browser to refuse cookies, our service may use them.

• Error reports. When something breaks, a description of the error and a short recording of what was on the screen before it go to Sentry. All the text in that recording is replaced with gray blocks and the images are hidden. It is only there so we can fix things.

The sign-in cookie lives until the end of the session. There are no other cookies on the site. Questions go to Телеграм .

What the one cookie is for:

• The client page sign-in cookie

  Lives until the end of the session

  Set by us

  Without it the client page cannot recognize the client and will ask for the code on every page. It is not needed for anything else.

• There is no “accept cookies” banner

  Because there is nothing to accept

  Set by us

  We don’t set cookies that the law says you have to be asked about.

• Settings

  Because there is nothing to accept

  Set by us

  The app settings — theme, window sizes, keyboard shortcuts — are kept on your computer, not in the browser and not with us.

If any of this is unclear, write to us on Telegram and we will answer in plain words.

Why we need your data

Only to make the service work:

• To keep the service running — and so we can see that it hasn’t broken.

• To recognize you when you sign in: Telegram tells us whose account this is, and we pull your cloud part up to it.

• To show the work to your client: only what you opened up on a particular project goes to the client page: hours, tasks, revisions and, if you allowed it, money.

• To write to you: daily and weekly reports come to Telegram if you switched them on. Your client gets a report by email — again, only if you switched that on. We send no marketing mail.

• We don’t sell data to anyone and we don’t pass it to ad networks. We are not going to make money on it.

• To answer your question: if you wrote to us, we read it and reply.

• If the service passes to someone else: we will give notice in advance, and you will have time to take your data or to opt out.

• What else it is for: anonymous statistics — how many people use what. It cannot identify a particular person.

Who the data does go to:

• Services it cannot work without: Supabase keeps the cloud part, Telegram signs you in, OpenRouter passes requests to the Claude model, Resend sends emails to your client, Sentry takes error reports. Each one gets only what it needs to do its job.

• If the service passes to someone else: If the service ever passes to another owner, the data goes with it, and we will say so in advance.

• Subsidiaries: there are none. The author is one person.

• Partners: nothing goes to them.

• Other people: only those you opened access to yourself: the client with a link to the client page and the employees you invited to the team.

• With your consent: in any other case, only if you allowed it.

How long all this is kept

Data on your computer stays until you delete it: it has no time limit. The cloud part lives as long as the account does.

The usage data of the site is kept for a short time and is only there to show that the site opens.

Where the data physically sits

The local database is on your Mac. The cloud part is on Supabase servers. The client page and the calls are on the author’s server. Some of those servers are outside Russia.

When you send something to the cloud, you agree that it ends up there.

We do what is reasonable to keep data from leaking: access by a link with a code, a secure connection, and no stranger opens someone else’s project.

How to delete it

You can delete everything there is about you.

Local data is deleted right in the app — together with the project, the task or the note.

We delete the cloud part and the account itself on request: write on Telegram and we will remove everything tied to your sign-in.

Sometimes something has to be kept — when the law requires it, for instance. Then we will tell you what exactly and why.

When we have to disclose data

Handing over the service

If the service passes to another owner, the data goes with it. We will give notice in advance.

A demand of the law

If the law obliges us, we will hand over what we must and no more.

Other cases

We can disclose data if it is truly needed in order to:

• meet a requirement of the law

• protect our own rights

• deal with abuse of the service

• protect someone’s safety

• defend ourselves in court

Security

We do what we can, but there is no absolute protection on the internet. The safest thing here is something else: most of your data never leaves your computer at all.

Children

The service is not for children: you have to be 18 to use it. We do not collect children’s data on purpose. If it turns out that some reached us anyway, write to us and we will delete it.

If the law of your country requires a parent’s consent, we will ask for it.

Links to other sites

The app and the site have links to other people’s sites. Follow them and you end up where other people’s rules apply.

We don’t answer for what happens to your data there. Read their policy.

Changes

The policy can change. We put the new version right here and change the date at the top.

We will give notice of material changes in advance — on the site, and on Telegram too if you have reports switched on.

Look in here now and then: changes take effect the moment they appear on this page.

Get in touch

Questions about this policy go to Telegram:

• Write to us here: https://t.me/timeclient_bot