Your data. Your control.
Understand what you can export, what history deletion removes and which records remain for the service to operate.
JSON export and privacy controls#
Settings → Download Guardian data (JSON) downloads stored customer records, including account identifiers and evidence. Only a currently authorized Jira administrator can request each page; paid-license renewal is not required. In the masking-enabled build, authorized export still contains decoded original account IDs; stored masking does not make the download anonymous. Keep the file secure. Pause scheduled scans and avoid changes while exporting. The file reflects a reading interval, is not a Jira backup and cannot be imported for restore. Browser content is limited to 256 MiB; contact [email protected] for assisted return beyond that limit. An error does not download a purportedly complete partial file.
Delete Guardian history does not cancel billing, change Jira or disable future scans. Export first if needed. Settings, capability configuration, a limited receipt and necessary privacy-restriction markers remain. The masking-enabled build also retains its installation identity key/control; unused account mappings are cleaned in bounded passes after remaining references and pending work are checked. Eligible historical data enters batched cleanup after 90 days; current/previous baselines and active findings can remain longer. Privacy maintenance can temporarily block export or changes. A warning about legacy permission data means those records need review and have been preserved.
Licensing and deletion#
Without an active/trial license, scans and Guardian-state updates fail closed; read-only views, administrator JSON export, privacy requests and history deletion remain available. Use Settings → Delete Guardian history, enter the explicit confirmation and allow the background deletion to complete. If app-level deletion is required, do this before uninstalling because Atlassian controls the Forge uninstall lifecycle.