ClaervoJira Service Management · Live on Marketplace
Find unintended request sharing before it becomes an incident.
Customer organizations and request participants widen who can see an HR, legal or finance request. Privacy Guard scores every request with six deterministic signals, shows the exact path, and remediates only after re-fetching live state.
from $1.35 per user / month above 10 users; up to 10 users free.
What it does
Exposure scanning
Paginated scans across service projects inspect organization and participant sharing without reading request content.
Explainable risk
Six signals with fixed weights; the same request always produces the same score.
Scoped policy
Target projects and request types, allow participant domains, roll out in monitor-only mode.
Revalidated remediation
Clear prohibited organizations or remove only violating participants after re-fetching current Jira state.
What it reads
- Issue ids, keys and service project identity
- Request type and timestamps
- Organization ids, names and bounded member counts
- Participant account ids and email domains when Atlassian exposes them
What it never touches
- Request summaries, descriptions, comments or attachments
- Passwords, tokens, payment data
- Anything used to train an AI model
Scopes and why
| read:jira-work | Read request metadata and sharing fields |
| write:jira-work | Apply approved remediation |
| read:servicedesk-request / read:customer:jira-service-management | Organizations and participants |
| storage:app | Policies, findings and sanitized evidence |
Inside the app
