OVERALL RATINGS
INSTALLS
1
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appFind and fix unintended JSM customer-request sharing before it becomes an incident
See privacy risk across every JSM project
Run cross-project scans that surface unsafe Organization membership and Request participant exposure, with severity, context, and a clear reason for every finding.
Turn policy into guided remediation
Define scoped sharing policies for sensitive service desks and multi-organization sites, then turn each violation into an explainable, controlled remediation workflow.
Stay audit-ready as your site grows
Protect large and multi-organization JSM sites with bounded scans, configurable thresholds, remediation tracking, and evidence that supports repeatable privacy reviews.
Supporting media
More details
Claervo Privacy Guard for JSM helps service teams discover and correct unintended customer-request sharing before it becomes a privacy incident. It audits organization membership and request participants across JSM projects, explains why each finding is risky, and guides administrators through safe remediation. Configurable policies support sensitive service desks, multi-organization environments, and large sites. Scan history, remediation status, and action evidence make privacy reviews repeatable and audit-ready. Built on Atlassian Forge, the app keeps processing within Atlassian and does not send customer content to an external service.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy and security questionnaire has been filled by the partner
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Claervo Privacy Guard for JSM integrates with your Atlassian app
Version information
Version 2.3.0•for Jira Cloud
- Release date
- Sep 8th 2026
- Summary
- Dismissed findings stay exceptions; audit trail and event handling hardened
- Details
Dismissed findings are now treated as accepted exceptions: automatic policies never remediate them and manual remediation asks you to reopen first. The audit trail keeps working past 250 records with newest-first ordering, a durable remediation counter and retention. Issue events are pre-filtered by service project before any API call. Post-remediation state is computed from the re-fetched request, so no phantom open findings. Deleted requests and requests moved out of JSM close their findings automatically; retention runs daily even when the scheduled scan is off. Findings listing reads up to 5,000 records; incomplete field discovery is retried after 10 minutes; the console shows the real version.
- Payment model
- Paid via Atlassian
- License type
- Commercial