Capaxima
Privacy notice · last updated 9 October 2026

What we keep, and why

Capaxima the app keeps nothing about you: a project is a folder on your disk. This page is about capaxima.com — the website, signing in with Google, and the beta program — because those do store a few things about you.

Who is responsible

The data controller is [full legal name], a sole proprietor registered in Poland, trading as Capaxima. Contact for anything on this page: [email protected]. The server that stores the data below is in Poland; Cloudflare (EU/US, under its data processing terms) sits in front of it as the network edge.

What we store, and why

DataWhere it comes fromWhyKept
Your email address and the name you typeYou, on the sign-in form. There is no password: we email you a one-time link, and following it is the sign-in.To know who is asking for the beta and to show you your own key. Email is also how we would contact you about the beta, and the address you write to us from.Until you ask us to delete it, or 90 days after the beta program ends.
Sign-in links: a one-way hash of the link, when it was asked for, from which IP addresscapaxima.com, each time you ask for a link.To make the link work once, for 30 minutes, and to stop a script from asking for thousands.7 days.
A session cookieSet by capaxima.com after you sign in.Keeps you signed in for 30 days. It is strictly necessary for signing in, so it needs no consent banner. It contains a random id, nothing else.30 days, or until you sign out.
Your beta request: the date and whatever you typed in the optional boxYou.To decide on and record the request.As the account above.
Your beta key, its status and datesIssued by us.The key is what lets the app run. Its status is how access is withdrawn or extended.As the account above.
Check-ins from the app: the key, an identifier of the computer, the app version, the Windows version, the time, and the IP address the check-in came fromThe Capaxima beta build, once a day while it is used.To confirm the key is still valid (the kill switch), to enforce the two-computer limit, and to see which build versions are in use. The computer identifier is a one-way hash — we cannot recover a name or serial number from it.Check-in records are deleted after 90 days. The computer identifiers stay with the key.
Downloads: which build you downloaded, when, from which IP addresscapaxima.com, when you press Download.To know which build a report refers to.90 days.
Feedback you send from the app: the text you typed, a screenshot only if you paste one (shrunk to a small JPEG on your computer before it is sent), its category (bug, idea, other), whether you want an email when it is fixed (only offered when the app is activated), the app version and build, the operating system name, the app's language, theme and open tab, the time, and the IP address it came fromYou, through the bug button in the Capaxima desktop app. It is linked to you through your beta key or, if the app is not activated, to an anonymous identifier of the computer (the same one-way hash used for check-ins) or a random id of the installation.To fix what you report, and — if you leave the box ticked — to email you once it is fixed and in which version. The IP address is only used to stop a script from flooding us. Nothing from your boards is attached on its own: a screenshot shows whatever was on your screen when you took it, so look at it in the preview and remove it if it shows something you would rather keep private.As the account above.
Usage statistics from the app: the key, an identifier of the computer, the app version and build, the name and version of the operating system (for example "Windows 11 Pro") and the app's language; for each day the minutes the app was open and in use, how many times it was started, how often each screen or function was opened (from a fixed list: the tabs, export, Jira import, feedback), counters of what was done from a fixed list (tasks, milestones and dependencies created or deleted, undo and redo, bars moved or resized on the Gantt chart, tasks assigned by hand or by auto-assign, people, professions and vacations added, whether any person was given a name, new projects started empty, from the sample or from the template, exports by format, whether the view was zoomed out into the sky), ranges that describe the project as it stands (how many tasks there are, how fully the plan is filled with dates, estimates and assignees, how many people and professions, how many conflicts) and the app's settings (language, theme, accessibility modes, Gantt view mode, window width), and, if the app crashes, the error's name, a short trace of the program's own code and a message with paths, email addresses, keys and long numbers cut outThe Capaxima beta build, in the background about every half hour. The IP address the request comes from is used in memory only to stop floods and is not stored.To see how the beta is used: which functions are used, where the app crashes, which versions are still running, so that we can decide what to fix first. It is linked to your key so that we can talk to the people who use it. Nothing about the content of your work is sent: no board, project, task, person or profession names, no file names or paths, no text you typed. Counters and ranges say that something was done and how much, never what it was.180 days, then deleted. If you object, write to [email protected]: we delete everything held under your key and stop storing more.
Visits to this websiteUmami, a self-hosted analytics tool.To see which pages are read. It sets no cookie and does not identify you; IP addresses are not stored.Aggregated indefinitely, never per person.

What we do not do

  • We never receive your boards, project names, task titles, team members or anything from inside the app. A check-in carries the key and the version numbers, nothing from your plan. Usage statistics are counts and ranges (minutes, how often a function was opened, a board's size as a range), never what is in a board. Feedback carries only what you type into it and the screenshot you choose to paste.
  • We do not sell, share or hand anything above to anyone, except as the law may require.
  • We do not send newsletters. If we email you at all, it is about your beta access.
  • No advertising, no tracking pixels, no third-party analytics.

Legal basis

Signing in and running the beta are a contract between you and us — the beta terms — and storing the account, key, check-ins and usage statistics is what performing it takes (GDPR art. 6(1)(b)). The website statistics rest on our legitimate interest in knowing which pages are read, with nothing about you stored (art. 6(1)(f)).

Your rights

You may ask what we hold about you, have it corrected, or have it deleted; you may also object to the usage statistics alone and keep the beta (art. 21); deleting the account ends the beta access with it. Write to [email protected] from the address you signed in with and it is done within a few days. You may also complain to the Polish supervisory authority, the President of the Personal Data Protection Office (UODO), at uodo.gov.pl.

Signing in

You type your email; we send a link from [email protected]; opening it signs you in on that device for 30 days. The email goes out through a transactional mail provider under our domain, which sees the address and the message in order to deliver it. We keep no password, because there is none.

Sign-in with Google is built and switched off for now. If it is switched on later, Google would tell us your account id, email, name and picture and nothing else, and this page will say so.

Changes

If this page changes in a way that matters, the date at the top moves and the change is named on this page.