Claervo Privacy Guard for JSM
Privacy notice
How Claervo processes JSM metadata, where that data stays and how to make a privacy request.
Effective: 1 August 2026Provider and contact
Claervo provides Claervo Privacy Guard for JSM. Privacy and data-rights requests can be sent to support@claervo.com.
Product boundary
The app is built on Atlassian Forge. Compute, Custom UI assets and app storage run in Atlassian's environment. There is no Claervo-operated remote backend, external database, advertising technology or product analytics endpoint.
Data the app processes
The app processes only the metadata needed to detect and remediate request-sharing exposure.
- Jira issue IDs and keys, service project identity, request type and relevant timestamps.
- JSM organization IDs, names and bounded member counts.
- Request-participant and administrator Atlassian account IDs.
- Reporter and participant email domains when Atlassian exposes an address; only the domain is stored.
- Policies, thresholds, scan state, findings, remediation state, audit evidence and license context.
Data the app does not collect
The product does not request or persist request summaries, descriptions, comments, portal message bodies, attachments, passwords, payment-card data or customer authentication tokens. Customer data is not used to train AI models.
Storage and retention
App data is stored with Atlassian Forge storage. Open findings remain while action is required; resolved or dismissed findings follow the tenant-configured 30–730 day retention period, with a 180-day default. Customers should export evidence they must retain before uninstalling.
Security and rights
Administrative features require Jira administrator permission and issue-level actions re-check edit permission. Customers can narrow policies, disable scheduled scans, use monitor-only mode, export evidence or uninstall. Applicable rights requests may be sent to the customer organization or support@claervo.com.
