Privacy
What happens to your code and data
What Tracks reads, what it sends out, what it stores and for how long, who can see it, and how to have it deleted.
Last changed: .
- Who runs this service
This Tracks is run by Jonathan Younes. For any question about this page, write to younesjonathan@gmail.com.
- What it reads
Tracks reads only what you connect to it.
- Your repository, through the GitHub connection you make or the token you give it: every file the agents open while analysing, proposing and building.
- Your database, if you connect one: read-only, through single queries, 100 rows at most per query, with a time limit. It cannot change a row. A query can reach anything that read access allows, so the answers can include your users' personal data.
- Feedback that people on your team paste in.
- Your errors in Sentry, if an owner connects Sentry: the unresolved errors of the last 30 days, how many times each happened and how many people it reached, and one error in full when a team asks for it. Error messages can hold what your users typed.
- Check results on its own pull requests: which job failed and the end of its log.
- What is sent to the AI provider
The AI provider (Anthropic) receives the parts of the code the agents read, the results of their queries, pasted feedback, the errors a team read from Sentry, card text, and the end of a failed check's log, so the model can read them and answer. A picture attached to a card is sent too when a team or the builder works on that card.
It is sent with the AI key set for this service, under the agreement its holder has with Anthropic.
- What else leaves this service
- GitHub: branches, pull requests and merges on the repository you connected.
- Sentry, if an owner connects it: the name of the organisation and project to read, and the name of an error to read in full. Nothing of your code or data.
- Your chat webhook, if you set one: card titles, counts and spend.
- Your mail server, if one is set: the same summary, and the email addresses of the owners and members it is sent to.
- Stripe, if you pay for a plan: your email address and which plan you chose. You pay on Stripe's own page, and your card details never reach this service.
Nothing else is sent anywhere. Tracks has no analytics.
- What is stored
- The board: cards with their evidence, history and the diff of each change, and the pictures and links a person attached to a card. Also the pictures of what was built that a connected assistant sent with its report.
- Every run of an agent: what it did step by step, its token count and cost.
- Teams, KPIs and their readings, and pasted feedback.
- People: names, emails and password hashes. Passwords themselves are not kept.
- Credentials, such as the GitHub connection's key or a token and the database address: encrypted, never shown again and kept out of logs.
- A checkout of your repository, used for reading and building.
What Sentry returns is not kept, except what a team writes on a card as evidence: the error's name, a sentence, and the two counts.
The app asks your account two questions, once each: after your first proposals, and after your first shipped change. If one of you answers, the answer is kept with the name of your account and is read by Jonathan Younes and nobody else. It is never sent to the AI provider. If you signed up with an invitation code, the code you came through and the plan it gave, with the day that plan ends, are kept with your account. Both are deleted with the account.
- How long it is kept
For as long as your workspace exists, or until you remove the product it belongs to or an owner deletes the account. One backup a day is kept for a week, so what you remove can remain in a backup for up to a week, or for up to 30 days where copies of the backups are also kept outside the server. A deleted account is not brought back from a backup.
- Who can see it
The people you invite into your workspace, each by the role you give them. Beyond them, Jonathan Younes runs the service and can reach what it stores, to keep it running and to answer you. Anthropic and the others named above receive what is listed there and nothing more.
- How to have it deleted
To remove one product, an owner chooses Remove product in its Settings. This deletes its board, runs, teams, credentials and checkout. Your repository is not touched.
To delete your account and everything in it, an owner chooses Delete this account under Your account, types the account's name and gives their password. This deletes every product with its board, runs, teams, KPIs and feedback, the people of the account with their sign-ins and invitations, the assistants they connected, the saved credentials and connections, the records of usage and of changes, and the checkouts of your code. It takes effect at once and cannot be undone. An account with a paid plan can be deleted once the plan has been cancelled and has ended.
Three things remain. Backups made before the deletion still hold the account until they age out, for up to a week, or for up to 30 days where copies of the backups are also kept outside the server; the account is not brought back from them. Invoices and payment records stay with Stripe, the payment provider, and nothing of them is deleted there. One line stays in the record of whoever runs the service: that the account was deleted by its owner, and when, with the account's name and no person's email.
A person who is not the only owner of an account can leave it under Your account. Their sign-in ends and their email is free to use again. Their name stays on what they decided.
If no owner can sign in any more, write to younesjonathan@gmail.com to have the account deleted. On GitHub, you can then uninstall the app or revoke the token you gave.
- Changes to this page
When this page changes, the date at the top changes with it. A change in what is read, sent or stored is told to the owners of each workspace by email before it takes effect.