BugForesight privacy policy
Last updated 28 October 2026
BugForesight (“the app”) is a Jira Cloud app built on Atlassian Forge. It is published by BeyondX Informatics Analytics Private Limited, a company incorporated in India (“BeyondX”, “we”, “us”). You can reach us at support@beyondxia.xyz.
This policy explains what the app does with data when your organisation installs it. It covers the app, and this website's pages, which don't use cookies, analytics or tracking.
1. Who is responsible for what
- Your organisation (the Jira site owner) decides to install the app and controls its Jira data.
- For the Jira data the app processes, we act as your processor, on your instructions (installing and using the app).
- The app runs on Atlassian Forge. Atlassian hosts the app's code, its database and the AI model, and is our sub-processor. We don't run any server that receives your Jira data.
2. What the app accesses and stores
The app asks for one Jira permission, read:jira-work. It never writes to your Jira issues.
| Data | Why |
|---|---|
| Past bugs (issue type Bug): key, project, title, a short snippet of the description (about 700 characters), the root-cause line if present, labels, components, priority, status, resolution, created and updated dates | To find past bugs related to a new story |
| A word index built from that text | To rank related bugs |
| The story being viewed: title and the first 4,000 characters of its description | Compared with past bugs and sent to the AI model (section 3). Results are cached. |
| Warnings: which past bugs were flagged, the reason and a suggested test scenario | Shown in the tab, and cached for speed |
| Your Atlassian account ID, and your Useful / Not useful votes with issue keys | To remember your feedback and keep results per viewer |
| Counts of AI checks for the site, per day and per month | To apply the AI-check limits |
| A list of the account IDs we hold, with the date each was last reported to Atlassian | Atlassian's personal data reporting (section 8) |
All of this is stored in a database that belongs to your installation, inside Atlassian's Forge infrastructure.
We don't store names, email addresses, avatars or phone numbers of Jira users. Account IDs are Atlassian's opaque identifiers. Bug and story text written by your team may itself contain personal data. The app treats it as ordinary ticket text and doesn't extract or profile people.
3. AI processing
To judge which past bugs matter for a story, the app sends the story title, up to 4,000 characters of its description, and about 20 candidate past bugs (key, labels, title and a snippet of up to 500 characters) to a large language model (Claude) through Atlassian's Forge LLM service. The app makes no call to any AI provider outside Atlassian. How Atlassian handles those requests is covered by Atlassian's own Forge terms.
If the AI is unavailable, or a site's AI-check limit has been reached, the app uses keyword matching instead, which makes no AI call.
4. Logs
Our logs hold counts, timings, issue keys and error names. They're written to avoid ticket text, AI prompts and responses, and account IDs.
5. Sharing, selling, advertising
We don't sell data, share it with advertisers or send it to third parties. The only other party involved is Atlassian, for hosting, the database and the AI. Emails you send us for support (for example with a screenshot) are used only to answer you.
6. Where data is stored
Data stays inside Atlassian's Forge infrastructure. Atlassian decides the region and any data residency options. Atlassian's own processing is covered by its Forge data processing addendum.
7. Keeping and deleting data
- We keep data while the app is installed, so that it keeps working.
- When the app is uninstalled, Atlassian removes the app's stored data under its Forge retention rules.
- When a bug is deleted in Jira, the app drops it from its index.
- To ask us what we hold, or to ask for deletion sooner, write to support@beyondxia.xyz. For a whole site, uninstalling the app is the fastest route.
8. Atlassian's personal data reporting
The app keeps Atlassian account IDs (votes and per-viewer cached results). In line with Atlassian's rules, it regularly reports those IDs to Atlassian's personal data reporting service. If Atlassian says an account has been closed, the app deletes that account's votes and cached results. If Atlassian says an account was updated, the app clears the cached results for it. We don't store names, emails or avatars, so there is nothing else to refresh.
9. Your rights
Depending on where you are, for example under the EU or UK GDPR or India's Digital Personal Data Protection Act, 2023, individuals may have rights to access, correct and erase their data, and to object to its use. Because we act for your organisation, we pass requests that reach us on to the site's administrators and help them respond. You can also write to us directly at support@beyondxia.xyz.
10. Security
The app has the protections of the Forge platform: an isolated runtime, a private database per installation, and Atlassian-managed encryption and access control. On top of that it uses the smallest Jira permission it can and makes no outbound network calls. If we find a security incident that affects your data, we tell Atlassian and affected customers promptly. More on the security page.
11. Children
The app is for business use and isn't meant for anyone under 16.
12. Changes
We'll post changes to this policy on this page and tell Atlassian and customers promptly about material ones.
13. Contact
BeyondX Informatics Analytics Private Limited, India. Email: support@beyondxia.xyz. See also the support page.