Privacy & Data Use
Last updated: 2025-12-16
What we collect
We collect only the Jira data necessary to provide the app's functionality:
- Issue metadata (issue key, summary, description)
- Custom field values used for classification
- User and group identifiers required to evaluate permissions
We do not collect or transmit attachments.
How we use data
Data is processed in‑instance to:
- Compute and store rollup classifications
- Render classification banners and panels
- Store classifications into a Jira custom field
We use data to provide search/JQL, display, and automation features requested by admins.
Storage & transmission
The app stores classification data only in the host Jira instance (custom field values).
No issue data is transmitted to external services unless you explicitly configure an integration; any external calls require admin configuration and consent.
Access & security
The app respects Jira permissions and Issue Security — classification values are only presented to users who have permission to view the issue. For sensitive deployments we recommend using Issue Security levels or group mappings that the app can manage.
We follow Atlassian Marketplace security guidance. Access to configuration in the app requires Jira administrator privileges. Plugin code runs in the host instance and relies on Jira's authentication and auditing.
Third parties & analytics
By default, the app does not send issue data to third parties. If optional integrations or telemetry are enabled, the app will disclose what data is sent and require explicit admin opt‑in.
Retention & deletion
Classification values are stored in Jira custom fields and follow your Jira data retention and deletion policies. Removing the plugin does not automatically delete custom field data — administrators should remove fields if desired.
Support & contact
For questions about data handling, security, or to request removal of telemetry, contact:
Email: support@yourdomain.com