Privacy Policy
Last updated: October 14, 2026
Threadr is a team-chat product by innovai8 whose system of record is the JIRA your organization already runs. This policy explains, in plain terms, what we handle and why. Threadr is in early access; we will post a fuller policy as the product matures.
The short version
- Your JIRA API token is never stored — it only passes through to act as you for your session, then it's discarded.
- Your conversations are stored in your own JIRA — not in a separate Threadr database that becomes the source of truth.
- We don't sell your data, and we don't use your messages to train models.
- You can revoke Threadr's access from your JIRA/identity provider at any time.
What we process
- Identity — when you sign in, your JIRA account id, email, and display name, to authenticate you and attribute messages to the real you.
- A projection/cache — a minimal copy of the messages and metadata needed to render channels quickly. The authoritative copy lives in your JIRA.
- Operational data — basic logs and seat/usage counts per JIRA namespace, used to run the service and for licensing.
Not your API token. We authenticate to JIRA with the token you provide, but it is never written to our database, logs, or backups. It is held only in memory to make requests as you during your session and is dropped when the session ends.
What we don't do
- We don't sell or rent your data.
- We don't use your content to train machine-learning models.
- We don't write to your JIRA as anyone but you — actions use your own credentials.
Direct messages
DMs are held in an encrypted vault, separate from the ticket store.
Your controls
You can revoke Threadr's access from your identity provider or JIRA at any time. To request deletion of the projection/cache we hold for your namespace, contact us.
Contact
Questions about privacy? Open a GitHub Discussion.