Privacy policy

Draft, not yet reviewed. Last updated 17 October 2026 (notice version 2026-10-07).

What we collect

jtaak asks who you are once, when you first use it. We never collect what you do with the app, how much you use it, your requests, workspaces or any other content.

• If you verify yourself (with an email link, Google, Microsoft or GitHub): your name and email address as that service gives them, an account id, how you signed in, and, for each computer you verify on, the app's id, edition and version, its data versions and the computer's machine ID. This is recorded once per computer, and again each time the app switches back to your account on a computer where you verified before. If you change your name in the app afterwards, the name you chose is kept too and shown in your account.
• If you choose "Later" and agree to share: the name and email address you enter, an id for your installation, the same app details and machine ID, and each later change to them.
• If you choose "Later" and don't agree: nothing leaves your computer.
• If you use a licence bought online, for each computer it's used on: its machine ID and, so you can tell your computers apart in your account and in the app, what the app reports about it: the computer's name, its operating system, kind (laptop or desktop) and model, its time zone and language, and the app's version.
• If you make CI keys for a purchase: each key's name, who made it and when, when it was last used (to the hour) and whether it was revoked, and each offline licence downloaded for it (who downloaded it, when, and when it ends). We keep a fingerprint of the key, never the key itself, and nothing about the pipelines that use it: not which runs, repositories or results. If a team's owner makes you a manager of its CI keys, that you are one.
• If you name a purchase in your account: the name, shown to you and to the members of its seats.
• If your team shares workspaces: each shared workspace's name, who made it, who has which role in it, and each version pushed (who pushed it, when, its message and its size), with the versions themselves: what the workspace held, as your team's members pushed it, so the others can get it. Values of variables marked secret stay on each computer. A workspace and its versions are kept until an owner deletes it, or, after the team's purchase ends, until we delete them.
• If you invite friends from the app: the email addresses you invite and when, with your own, so we can send the invitation, keep you from inviting the same address too often, and show you whom you've invited. Each invited address gets one email; we don't use it for anything else.
• If you leave a request from the app: your message, its status and our response, with who you are and details of the app (its edition, version and your licence plan) and your computer (its name, operating system and version, processor, memory, machine ID), so we can understand and answer it.
• If you send crash reports from the app's Diagnostics: the reports, with who you are (if you've given your details) and the same details of the app and your computer. They're sent only when you choose Send.

With each record we keep that you agreed, which version of this notice you agreed to, and when.

Why

To know who uses jtaak, to contact you about it, and, for paid licences, to tie a licence to a verified person. We don't sell your details.

Where it's kept

In Google Firebase (Firestore, Firebase Authentication and, for shared workspaces, Cloud Storage), in one region. Sign-in services (Google, Microsoft, GitHub) see that you signed in, under their own privacy policies.

Your choices

An unverified user can change their details in the app at any time, or stop sharing by unticking the consent box. To have your details deleted, email ashokkumar.ta@gmail.com. Your organisation can also turn identity off entirely.