DeepWork

Legal

Privacy policy

DeepWork is a timer, a task list and a habit tracker that keeps its data on your own machine. This policy describes the little that happens outside it.

Covers this website and the DeepWork app

The short version

Your DeepWork data is not collected. No account, no profile, no advertising and nothing sold. Whatever you write in DeepWork is yours, and it stays on your own machine. Nothing is charged, and nothing is taken from you.

Four things exist outside it. The GoatCounter count of visits to the front page and the web app, the captcha on the contact form and a message you deliberately send me do not say who you are. The fourth, Google Analytics, is loaded by the front page and uses Google's own cookies; it is described below with the others.

Who is responsible

DeepWork is a personal open-source project, not a company. I am Rajat Malik, based in Gurgaon, India, and I am the person responsible for the processing described on this page. There is no data protection officer, no registered company and no business partner with access to anything described here.

Write to contact@rajatmalik.dev about this policy, or about anything that concerns your data.

This website

The site at deepwork.rajatmalik.dev is a set of static files. It has no server of its own, no database, no login and no comment form.

Hosting

The files are published through GitHub Pages, so GitHub processes the request the way any web host does: your IP address, the time, the file you asked for and your browser's description appear in its server logs. I do not receive those logs and cannot read them. GitHub's handling is described in GitHub's privacy statement.

The visit count

The front page and the web app each send one pageview to GoatCounter (deepwork.goatcounter.com), so that "is anybody using this?" has an answer without DeepWork running a backend. The page sends the request itself — no third-party script is loaded to make it — and it contains:

  • the address of the page and its title;
  • the referring page, if your browser sends one, and any query string;
  • the width of your screen;
  • a flag saying whether the browser is automated, and a random value that stops the request being cached.

It writes no cookie, reads no identifier, and GoatCounter stores no IP address for it. What I can see is totals and grouped counts — pages, referrers, locations, browsers — never an individual visitor. A browser sending Do Not Track or Global Privacy Control is not counted, and neither is a local build, a preview deployment or the automated audit.

These three documents are not counted. The privacy policy, the terms and this contact page send no pageview at all.

The Google tag

The front page also loads Google Tag Manager, which in turn loads Google Analytics. That is the one third-party script on the main page. Google receives the page address, the referring page, your IP address, a description of your browser and device, and an approximate location derived from the request, and it sets its own analytics cookies to recognise a returning browser.

Google processes that under its own privacy policy. The tag is loaded by the front page only — not by this policy, the terms or the contact page. A content blocker that stops Google is enough to opt out, and the page still works without it.

The Site stats panel

The footer of the front page has a Site stats button. It reads the totals and the month's breakdowns back through GoatCounter's read-only API, with a token that can only read. Nothing is fetched until the panel is opened, and opening it reports nothing about your visit.

Cookies and third-party scripts

This site's own code sets no cookie and writes nothing to identify you beyond the theme preference described below. The typefaces and screenshots are shipped with the site rather than fetched from a font service or an image host. There is no advertising network, no social widget, no session recorder and no fingerprinting by the site itself.

Two third-party scripts are loaded by this site, and each is confined to one page. The front page loads Google Tag Manager, which loads Google Analytics and sets Google's analytics cookies. The contact page loads hCaptcha (Intuition Machines, Inc.), which decides whether the form was filled in by a person and works by setting its own cookies and device signals. Each exists for a stated purpose — measurement on the front page, an unguarded public form on the contact page — and neither is loaded by the other's page.

This policy, the terms and the contact page do not load the Google tag. With JavaScript turned off, the page still reads and the contact form falls back to email. hCaptcha's handling is described in hCaptcha's privacy policy.

What is stored on your device

One preference of this site's own is stored. It lives in localStorage, which is not a cookie: it is a file in your browser's own storage, it is never sent with a request, and clearing site data removes it.

Name What it holds Why
deepwork-site-theme dark or light So the theme you chose is the theme you get on the next page, without a flash of the other one. It is read on this site only and never transmitted.
Your DeepWork data Tasks, sessions, habits, journal entries and settings — only in the web app The app works. It is written by the app into your browser's storage or into a local database, and it never leaves the device. See below.

The Google Analytics cookies described under This website are also stored in your browser when the front page's tag runs. They are Google's cookies, not this site's, and the documents do not set them. Apart from the theme preference and those cookies, this site stores nothing in your browser: no fingerprint, no advertising identifier and no preference beyond the theme you chose. The captcha on the contact page keeps its own cookies, which are hCaptcha's and are described above, not this site's.

The web app

The browser build at app.deepwork.rajatmalik.dev has no account and no sign-in. Everything you enter is kept in your own browser storage, on your own device, and is not sent anywhere. The web app can also be installed, and then it keeps working offline.

It counts visits with the same counter and the same promises — one pageview per load, no cookie, no stored IP address, and the page never sending a task or a journal entry. Settings → Count my visits turns that off; with the switch off, the counter is never loaded. The desktop build is never counted, and there is no collection of your tasks, your journal or anything else you write — not in aggregate, not anonymously, not at all.

Clearing your browser's site data deletes that data as well. To move it or to keep it, use the app's own JSON backup.

The desktop app

The Windows, macOS and Linux builds keep everything in a local SQLite database on your computer. There is no DeepWork server, no account and no sync: nothing you record is uploaded, and there is no telemetry about your work.

The desktop app makes three kinds of network request, and no others:

  • a release check — it asks the public GitHub API whether a newer version exists. GitHub sees the request and your IP address; the app sends no identifier of its own;
  • a download you press — an installer or update comes from GitHub's release page;
  • a link you open — the app opens it in your browser, where the destination's own policy applies.

The app's logs are local files on your machine, written so that a fault can be understood without anyone connecting to your computer.

Messages you send

You can write to contact@rajatmalik.dev for anything, or to support@rajatmalik.dev for help installing or using the app. A message sent by email passes through your mail provider and mine, and arrives in my mailbox.

I keep it for as long as it takes to answer, and afterwards for as long as ordinary correspondence is kept. It is not added to a mailing list, not sold, not shared, not used for advertising, and not used to train a model. Ask me to delete a thread and I will delete it.

The contact page has a form. Pressing Send posts the fields you filled in — your name, your email address, the topic and the message — to Web3Forms, which forwards them to contact@rajatmalik.dev as an email. The browser also sends its usual request headers, including your IP address, to that service. Nothing is stored on this site: it is a set of static files with no server and no database. With JavaScript turned off, the button composes the message in your own email app instead, so it travels through your provider and mine.

A form submission is kept no longer than the email it becomes. Web3Forms processes it only to deliver it and keeps its own logs under its privacy policy. Once it arrives, the message is treated exactly like one you send by email, as described above. The captcha on the form is hCaptcha, described under This website.

There is no phone number for DeepWork and none is requested. Nothing on this site asks for a date of birth, an address, a payment detail or an identity document.

Who else is involved

These are the only third parties in the picture. Each one handles its own part under its own policy; none of them receives your DeepWork data.

Who What they do What they see
GitHub Hosts this site, the downloads and the issue tracker Ordinary web-server request logs, under its own policy
GoatCounter Counts visits to the front page and the web app The page and the fields listed above — no cookie, no stored IP address
Google Provides Tag Manager and Google Analytics, which measure visits to the front page The page address, referrer, IP address, browser and device details, and its own analytics cookies, under Google's privacy policy
Mail providers Carry an email you choose to send The message, as any mail provider does
Web3Forms Delivers a message sent through the contact form to the inbox The name, email address, topic and message you submit, and the IP address the request came from
hCaptcha Checks that the contact form was filled in by a person, not a script Your IP address, the page it is loaded on and device signals, under its own policy; it sets its own cookies

The Google tag currently loads Google Analytics; there is no advertising network and no data broker configured by this site, and nothing is sold. The only measurement is the GoatCounter count and Google Analytics, both described above.

Your rights

Because there is no account and no profile, there is very little to hold. I hold only what you choose to send me; Google holds the analytics data described above under its own policy. Where laws such as the GDPR or India's Digital Personal Data Protection Act, 2023 apply, you may ask to:

  • be told what is held about you, and receive a copy;
  • have it corrected or erased;
  • object to being contacted, or withdraw a consent you gave;
  • complain to your local data protection authority.

Write to contact@rajatmalik.dev and I will act on the request. There is no automated decision-making about you anywhere in this project.

Children

This site and the app are not directed at children. There is no account, no profile and no advertising network, and the Google tag described above is not directed at children. If a child writes to me, the message is treated like any other correspondence and deleted on request.

Changes to this policy

When this policy changes, the date at the top changes with it, and the change is described here. There is no mailing list to notify, so the date is the notice.

  • 8 November 2026 — the front page gained Google Tag Manager and Google Analytics, and this policy names Google and what it receives.
  • 30 October 2026 — the contact form gained a form-handling service, Web3Forms, and this policy names it and what it receives.
  • 28 October 2026 — first published, with the privacy, terms and contact pages.

Questions

If something here is unclear, or you think it does not match what the site actually does, tell me. That is a bug in this document, and I would rather fix it than have it stand: contact@rajatmalik.dev.