PRIVACY POLICY

EvidencePack for Jira

The Forge companion reads only data the current user can already access in Jira and generates the file in the browser. The Forge edition maintains no separate database, uses no remote services, and sends no content to the developer.

EFFECTIVE AUGUST 1, 2026

Data handled and purpose

The app reads the project name and key, issues, fields, comments, worklogs, and change history to prepare a JSON archive requested by the user. Access always respects Jira permissions.

Storage and transmission

  • No Jira content is stored by the developer.
  • No data is sent to external servers, analytics, or advertising services.
  • The JSON is created in the Forge session and downloaded directly in the user's browser.
  • Technical logs must not include issue content or credentials.

Permissions

  • read:jira-work: reads the project and authorized items needed to build the archive.
  • read:jira-user: preserves user references already visible in authorized data.

Retention, sharing, and deletion

Because the Forge edition has no separate storage, the developer retains no Jira content. The downloaded file remains under the user's control. Data is not sold, shared, or used for advertising or model training.

Contact

Questions or requests can be sent to support@bfautomations.com.