Privacy notice for trackxai accounts
This notice is about your data as a person who uses trackxai: how you sign in, your account, and your invoice.
Dated 2026-11-08. This page describes the processing in place on the date shown.
1. The short version
For the content inside a workspace, the tasks your agents write and the people named in them, your organisation is the controller and Kalebtec is its processor under the data processing agreement, available on request. This notice does not cover that content.
What we hold about you is small: the identifier of the account you sign in with, a display name, when you signed in, the names you give the tokens you issue, and a record of every write you make. We hold it to run the tracker and to keep a truthful record of who did what. We do not profile you, we do not sell anything, and the only marketing we send needs a box you tick yourself.
2. Who is responsible
Kalebtec Studio S.C., a sociedad civil under Spanish law, CIF J26989384, Avenida do Alcalde Portanet 20, 4º J, 36210 Vigo (Pontevedra), Spain. Write to hello@kalebtec.com and a founder answers. We have not appointed a data protection officer. We have checked the conditions in Article 37 of the GDPR and do not meet them.
3. What we collect, why, and on what basis
| Data | Where it comes from | Why | Legal basis | Kept for |
|---|---|---|---|---|
| Your GitHub numeric account identifier, login and display name | GitHub, when you sign in with it. Article 14 applies: we receive it from GitHub, and GitHub's own privacy statement covers what GitHub does with your account | To sign you in and to record you as an operator in the workspaces you are allowed into | Article 6(1)(b), performance of the contract with you or your organisation | The session for 30 days after you last used it, and 90 days after you signed in at most. The actor row for the life of the workspace, then the retention in section 6 |
| Your email address, and the instant a sign-in link confirmed it | You, when you open an account or when a workspace member invites you. Article 14 applies to an invitation: the member who invited you gave us the address | To identify you, to sign you in, to send the account notices and to send invitations | Article 6(1)(b), and Article 6(1)(f) for an invitation, the legitimate interest of the workspace that invited you | For as long as your account exists, until you ask us to erase it |
A session cookie, __Host-trackxai_session, signed, HttpOnly, Secure, SameSite=Lax, and our record of that session: a SHA-256 digest of the secret the cookie carries, the instant you signed in, and whether it was revoked | Set by us when you sign in | To keep you signed in without a password, and to let you sign out of every device at once | Strictly necessary for a service you asked for, so no consent is needed under Article 22.2 of the LSSI | 30 days after you last used it, 90 days after you signed in at most, and ended at once when you sign out. The record is deleted after 90 days, at the next sign-in on the service |
| Your GitHub account's primary email address, where GitHub marks it verified | GitHub, when you sign in with a GitHub account not yet connected to trackxai | To suggest the address to confirm, on the page that asks which address you use here. The account connects only through a link mailed to the address you give | Article 6(1)(b) | Held in an encrypted cookie in your browser for 15 minutes and never stored on our side |
| A passkey you register: its public key, its credential identifier, the model identifier of the authenticator, its transports and use counter, and the instants you created and last used it. Never a private key | You, when you add a passkey | To sign you in with it | Article 6(1)(b) | Until you remove it, and at once when your identity is erased |
| A sign-in that did not complete: the reason and the instant, written to our server log. Never the address and never the link | You, when a sign-in does not complete | To make a failing or unauthorised attempt visible to the operator | Article 6(1)(f), our legitimate interest in the security of the service | 30 days |
| A sign-in link, stored as a SHA-256 digest and never as the link itself, and a keyed digest of the address and of the source it was asked from, which nobody without our server secret can match to an address | You, when you ask for a sign-in link | To sign you in once, and to bound how many links one address or one source may ask for | Article 6(1)(b), and Article 6(1)(f) for the bound | The link for 15 minutes or one use, whichever comes first, and its record is deleted at the next sign-in request after that. The send record for 1 hour, deleted the same way. Every link record is deleted at once when your identity is erased |
| The six-digit code mailed beside a sign-in link, stored only as a keyed digest, and the number of codes tried against that link | You, when you ask for a sign-in link and when you type the code | To sign in the tab that asked, and to stop anybody guessing a code: a link takes five tries | Article 6(1)(b) for the code, and Article 6(1)(f), our legitimate interest in the security of the service, for the count | The code for 15 minutes or one use, like its link. The address digest held beside it is cleared seven days after the link was issued |
| The names you give the tokens you issue, their creation, expiry, revocation and last-used instants. Never the token itself | You, in the token page | To let you see and revoke what you issued | Article 6(1)(b) | The life of the workspace |
| The name of a computer you link to a workspace with remotxai, the workspace and the approval you gave, and a digest of the token issued to it | You, when you approve a device code | To let that computer work the workspace's tasks, and to let you unlink it | Article 6(1)(b) | The token for 90 days after its last use, ended at once when you unlink the computer |
| Every write you make: the entity, the change, the instant, and you as the actor, in an append-only event log | You, every time you write | To show the people in a workspace who changed what, and to keep an audit trail nobody can edit | Article 6(1)(f), the legitimate interest of every member of a workspace in a truthful history | The life of the workspace, then the retention in section 6. Your name on those rows can be pseudonymised on request, section 7 |
| A report you send from inside the product: the problem or idea you write, your display name, identity identifier and workspace slug, and, if you leave technical details ticked, the page path, window size, browser language, user agent, app version and which layouts are switched on. Never your email address | You, when you send a report | To fix what you report and weigh what you suggest, and to bound how often one person or one source may send | Article 6(1)(f), our legitimate interest in running and improving the service you use | As a task on Kalebtec's own board, in our database, for the life of that board. Deleted or pseudonymised on request, section 7. The send counters for 1 day |
| Request metadata in our server access log: IP address, user agent, URL and timing. One-time codes and capability links in a URL are masked before the line is written | Your browser and your agents, on every request | To run and secure the service | Article 6(1)(f) | 30 days, then deleted |
| When the application fails with an uncaught error: the error's type and its message with tokens, email addresses, identifiers, web addresses and quoted text removed, the file names, function names and line numbers of the code that failed, the version of the service, the page's route as a template such as /w/[slug]/t/[taskId] with no workspace or task value, and whether it happened in your browser or on our server. Never your name or email address, a URL query or fragment, a cookie, a request or response body, or the content of a workspace. One anonymous event a page load says the application is running: the version of the service, the page's route as a template and that it came from your browser, with no identifier that persists | Your browser or our server, when an error is not caught, and your browser once on each page load. Not at all if your browser sends Do Not Track or Global Privacy Control. Nothing is stored in your browser for it | To find and fix faults in the service | Article 6(1)(f), our legitimate interest in the reliability of the service | In PostHog until Kalebtec deletes it. It carries no account or person identifier |
| One anonymous page view for each page of this site you open: the page's path with no query or fragment, the host name, the page's language, the version of the site, the name trackxai-site, and the name and version of PostHog's library. Never a URL with a query, a referrer, a page title, a cookie, an account or email address, or an identifier that outlives the page load. The library holds a random identifier in memory, and it is gone when the page closes | Your browser, once the page has loaded. Not at all if your browser sends Do Not Track or Global Privacy Control. Nothing is stored in your browser for it | To count which pages of the site are read, and in which language | Article 6(1)(f), our legitimate interest in knowing how the site is used. It stores nothing on your device and identifies nobody, and Do Not Track or Global Privacy Control stops it. You may also object under Article 21 | In PostHog until Kalebtec deletes it. It carries no account or person identifier |
| A trial-eligibility marker: a SHA-256 digest taken over your email address with everything after a plus sign stripped from the local part. The address itself is not stored beside it | Derived by us the first time a trial starts | To stop one mailbox taking a second free trial | Article 6(1)(f), our legitimate interest in not giving the service away | 7 years, then deleted. It answers only whether a mailbox has had a trial and cannot be read back |
| Your account's state and its dates: trial start, expiry and subscription | Derived by us | To run the trial, the subscription and the notices that go with them | Article 6(1)(b) | For as long as your account exists, then the expiry ladder in section 6 |
| A marketing consent and the instant you gave it. The box is unticked by default and never required | You, if you tick it | To send you product news | Article 6(1)(a), consent, withdrawable as easily as it was given: write to us and we stop | Until you withdraw it |
| Billing name, address, country, VAT number where given, your subscription's status and dates, and, once you subscribe, an identifier Stripe issues for your Stripe Customer and your subscription. Card numbers stay with Stripe and never reach us | You, at Stripe Checkout, and Stripe itself, which we instruct as our processor to collect and calculate VAT on it | To subscribe your account, to determine VAT with Stripe Tax, and to invoice you | Article 6(1)(b), and Article 6(1)(c) for the invoice | Invoices and accounting records for 6 years from the close of the financial year, Código de Comercio Article 30.1 |
We make no decision about you by automated means that produces a legal or similarly significant effect, and we do not profile you.
4. Who receives it
The sub-processor list names each provider with its role, the data it handles and where. In short: OVH hosts the service in the EU, Cloudflare carries the traffic and stores file attachments, GitHub signs you in when you choose it, Resend sends our email, Stripe takes payments, PostHog receives the error reports and page views described in section 3, and Google Workspace hosts our mailbox. We share nothing with anybody else unless the law requires it, in which case we tell you first unless the law forbids it.
Stripe receives your billing name, address, VAT number and card details directly, when you subscribe through Stripe Checkout, and reports back to us your subscription’s status and dates and the Stripe Customer and subscription identifiers, so we can run your subscription and invoice you. Kalebtec remains the controller of that billing data; Stripe processes it on our behalf under Stripe’s data processing agreement, which incorporates the European Commission’s Standard Contractual Clauses for any transfer outside the EEA. Your card number itself never reaches us.
5. Where it goes
The service runs on OVH infrastructure in the EU. Requests reach it through Cloudflare’s network, which can handle them outside the European Economic Area, and file attachments are stored with Cloudflare. Stripe, Resend, GitHub and Google are United States companies or can reach data from outside the EEA. Where a transfer outside the EEA takes place, the safeguard is the one named for that provider in the sub-processor list, which for Stripe, Resend and Google is the European Commission’s Standard Contractual Clauses incorporated in the provider’s data processing agreement. Ask us and we tell you which provider’s agreement covers which flow.
Our server access log, with the IP address, user agent, URL and timing of each request, is kept for 30 days and then deleted.
An error report, one anonymous event on each page load of the application that says it is running, and one anonymous page view for each page of this site go to PostHog’s EU cloud. Like any request, what your browser sends reaches PostHog with your IP address. PostHog discards it: the project has its “Discard client IP data” setting on, and the request asks PostHog not to record it as well. Our data processing addendum with PostHog is signed.
6. How long we keep it
The column “Kept for” in section 3 gives each period. A workspace and everything in it, including your actor row and your events, lives for as long as the workspace does. A workspace owner can delete a workspace from its settings, and a scheduled job then purges it.
An account whose trial or subscription has ended is read-only for 30 days, dormant for a further 30, and purged on day 90, with an export available until the purge. Notices go to your verified address on day 23, day 29, day 30, day 60, day 76. A purge writes a tombstone carrying the workspace and account identifiers and row counts, and no email address, kept for 7 years. The same schedule is published on the pricing page.
7. Your rights
Access, rectification, erasure, restriction, portability and objection, under Articles 15 to 21, and the right to withdraw a consent at any time under Article 7(3). Write to hello@kalebtec.com. We answer within one month, and we tell you if we need the two further months Article 12(3) allows.
Erasure has a limit, and it is stated here so nobody meets it in the reply. Event rows are append-only. On erasure we replace the display name on each actor row with a stable pseudonym. The event itself stays. The identifier that links your writes together stays too, so the history the other members rely on still renders. The balance is recorded under Article 17(3). When the whole workspace is purged, every row including yours goes with it.
Portability. Each workspace has a self-service export in JSON, and a CSV of its tasks, in its settings.
You may complain to the Agencia Española de Protección de Datos, www.aepd.es, or to the authority where you live.
8. Cookies
The pages of this site set no cookie. The application sets the cookies below once you sign in or start to. There is no advertising and no third-party cookie. Error reports and the page view described next store nothing in your browser. When your browser holds the signed-in flag below, a page of this site asks the application whether the session is live, so the header can offer Open app in place of Sign in. The answer is not stored, and the request appears in the access log like any other.
Counting page views. Each page of this site sends PostHog one anonymous page view. It is always on and there is no banner to answer, because nothing is stored on your device and nothing identifies you: the page’s path with no query or fragment, the host name, the page’s language, the version of the site and the name of PostHog’s library, and no cookie, no URL with a query, no referrer and no page title. The library keeps a random identifier in memory, and it is gone when the page closes. If your browser sends Do Not Track or Global Privacy Control, the library is not loaded and nothing is sent. Section 3 gives the basis, and Article 21 gives you the right to object. Write to hello@kalebtec.com.
| Cookie | What it does | Lasts | Kind |
|---|---|---|---|
__Host-trackxai_session | Keeps you signed in | 30 days after you last used it, 90 days after you signed in at most | Strictly necessary |
trackxai_signed_in | A flag with the value 1, set beside a verified session so the pages of this site ask whether you are signed in only when your browser may hold a session. It holds no identity and authorises nothing. It is readable by page script and is not HttpOnly | As long as the session it accompanies | Strictly necessary |
trackxai_oauth_state, trackxai_github, trackxai_link_confirm, trackxai_sign_in_wait, trackxai_passkey_challenge, trackxai_pending_authorize, trackxai_return | Each carries one step of a sign-in or connection you started: the state of a GitHub sign-in, the address GitHub suggests, the mailed link until you confirm it, the wait of the tab that asked, a passkey challenge, an app connection awaiting your approval, and the page to return to | 5 to 15 minutes | Strictly necessary |
trackxai_last_workspace | Remembers the workspace you were last in, so the next sign-in opens it. It holds a workspace address and nothing that identifies you | 180 days | Preference, set inside the signed-in application |
trackxai-theme | Remembers the light, dark or system choice you saved | 1 day | Preference, set inside the signed-in application |
trackxai-zone | Remembers the time zone the progress page draws your day in | 1 year | Preference, set inside the signed-in application |
The strictly necessary cookies need no consent under Article 22.2 of the LSSI. The page view stores and reads nothing on your device, so there is no consent to ask for. The preference cookies hold one value each, set inside the signed-in application, and are not used to follow you anywhere. On https, the sign-in and session cookies carry the __Host- prefix and are HttpOnly and SameSite=Lax.
9. Children
trackxai is a business tool and is not offered to anyone under 18.
10. Changes
We update this notice when what we do changes, and the date at the top says when. Where a change reduces what you get we tell you 30 days before it applies.