truthtrail / privacy.md
Privacy policy
Last updated 11 November 2026
TruthTrail records the product decisions a coding agent makes and posts them on your tickets. It never reads, uploads or stores your source code.
Without signing in, the CLI keeps everything in your repository and sends nothing to us. This policy covers the TruthTrail server, which you use only after you or your team lead connect Jira or GitHub.
Who we are
TruthTrail is built and run by an independent developer, Dhairya Modh. In this policy “we” means the operator of TruthTrail. For any privacy question or request, email modhdhairya@gmail.com.
When your company connects Jira or GitHub, your company decides which projects and repositories TruthTrail can use. For that data your company is the controller and we process it on its behalf.
Local mode
The truthtrail CLI and its MCP server run on your computer. Until you run truthtrail login, decisions are written to the .decisions/ folder in your repository and nothing is sent to us. npm, the registry you install the CLI from, has its own privacy policy.
What we store
Once you sign in, the server stores:
| Data | Why |
|---|---|
| Decision text | The question, the options, the chosen answer and the reason. Encrypted at rest. Needed to post it on the ticket and show it in history. |
| Decision details | Ticket key, status, the file paths the decision refers to, which agent recorded it, and when. Needed to show decisions next to the right code and ticket. |
| Confirmations | Who confirmed or rejected a decision, and the reason they gave. |
| People | Atlassian account id and display name, and email address if Atlassian shares it. For GitHub, user id and login. Used to show who decided and who confirmed, and to mention the right person. |
| Access | Which Jira projects or GitHub repositories each person can read, so nobody sees decisions on tickets they can't open. |
| Connection tokens | Atlassian and GitHub access tokens, encrypted. Used only to read tickets and post or update the TruthTrail comment and PR check. |
| Pull requests | Repository name, pull request number and commit id, to post the TruthTrail check. |
| Team settings | Tracker repository, who confirms, and whether waiting decisions fail the check. |
| Sessions | A hashed key for each signed-in CLI and browser session. |
What we don't store
- Source code, diffs or file contents.
- Your conversations with the coding agent.
- Ticket descriptions or other comments. We read the comments that reply to TruthTrail, and only keep the command and reason in them.
- Passwords. Sign-in goes through Atlassian or GitHub.
- Analytics or advertising data. This website and the server use no trackers.
How we use it
Only to run TruthTrail: post decisions on tickets, record confirmations, mention the person who needs to confirm, show decision history, and post the PR check. We don't sell data, use it for advertising, or use your decisions to train AI models.
Who processes it
- Cloudflare hosts the server, the database and this website.
- Atlassian and GitHub receive the comments and checks TruthTrail posts, and the requests it makes on your behalf.
- Google Fonts serves the fonts on this website, so your browser requests them from Google.
We disclose data to anyone else only if the law requires it.
How long we keep it
- Decisions are kept while your team uses TruthTrail, because they explain why the code behaves the way it does.
- Expired browser sessions and sign-in requests are deleted daily. Sign-in codes are deleted after one day.
- Once a week we report the Atlassian accounts we store to Atlassian, as Atlassian requires. When an account is closed, we replace its name with “(closed account)” and delete its email address.
- If your team disconnects TruthTrail and asks us to, we delete its decisions and tokens within 30 days.
Your rights
You can ask to see, correct or delete the personal data we hold about you, or object to how we use it. Email modhdhairya@gmail.com. We reply within 30 days. If the data belongs to your company's workspace, we may need your company to agree before we delete it. You can also complain to your local data protection authority.
You can sign out of a laptop at any time with truthtrail logout, and withdraw a decision you recorded with truthtrail withdraw.
Cookies
This website sets no cookies. The server sets two, only when you use it: one that keeps you signed in to the settings pages, and a short-lived one that protects the connect flow from forged requests. Both are needed for the service to work.
Security
Decision text and tokens are encrypted at rest. All traffic uses HTTPS. Requests from Jira and GitHub are verified before they're processed. Each person only sees decisions on tickets they can open. No system is perfectly secure; if we learn of a breach that affects you, we will tell you.
Changes
If we change this policy, we update the date at the top. For a significant change, we tell connected teams before it takes effect.