> For the complete documentation index, see [llms.txt](https://hiera.gitbook.io/safe-groups-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hiera.gitbook.io/safe-groups-docs/safe-groups-for-jira-cloud/privacy-policy.md). # Privacy Policy ### What Data the App Reads Safe Groups reads Jira Cloud data needed to identify supported Jira group references. The app may read: * Jira group metadata, including group names and group IDs * Permission schemes and permission grants * Project metadata needed to scan project roles * Project roles and project role actors * Saved filter metadata and filter share permissions * Dashboard metadata and dashboard share permissions * Related Jira metadata returned by Jira REST APIs, such as user, owner, avatar, field, application role, and project metadata where required by the API responses ### Why the App Reads This Data Safe Groups reads this data to help Jira admins find where a selected Jira group is referenced before changing, cleaning up, or deleting that group. The app uses the data to display: * A group explorer * Impact summary * Risk labels * Impact references * CSV export generated from the current displayed results * Advanced scan details for validation and troubleshooting ### What the App Does Not Do Safe Groups does not: * Modify Jira groups * Delete Jira groups * Change permission schemes * Add or remove project role actors * Change filter shares * Change dashboard shares * Write Jira configuration * Send scan results to external services ### External Data Egress Safe Groups does not currently configure external egress. The app uses Jira REST APIs through Forge. Custom UI calls Forge resolver functions. The Forge backend calls Jira Cloud REST APIs through Forge. Safe Groups does not currently send scan results to external services. ### Data Storage Safe Groups does not currently use Forge Storage. Safe Groups does not currently use an external database. Impact results are generated during the current analysis flow and displayed in the browser session. ### CSV Export CSV export is generated client-side from the current displayed results. The exported CSV is downloaded by the user's browser. Safe Groups does not currently send the CSV or scan results to an external service. ### Contact For privacy or security questions, contact `shv.support@germanmorales.org` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://hiera.gitbook.io/safe-groups-docs/safe-groups-for-jira-cloud/privacy-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.