What OrgPulse accesses
OrgPulse requests three read-only Jira Cloud OAuth 2.0 scopes:
read:jira-work— Issue status transition history, sprint membership, issue types, and created/updated timestamps. Used to compute team-level workflow metrics.read:jira-user— Team membership (which users belong to which project or board). Used only to group metrics by team. User identities are never stored.read:sprint— Sprint start/end timestamps and sprint names. Required for sprint-boundary metric calculations and calibration.
What OrgPulse stores
OrgPulse stores only derived aggregates — never raw issue content:
- Workflow metrics — Cycle time, lead time, throughput, WIP, and cycle time variance, computed as team-level aggregates.
- Baseline models — Exponentially weighted moving averages (EWMA) and statistical distributions per metric, per team.
- Diagnostic events — Pattern detection results (e.g. "Chronic WIP Inflation detected"), including the evidence that triggered them (metric values and sprint IDs). No issue titles or descriptions.
- Team configuration — Status mapping rules and issue type classifications set during onboarding.
What OrgPulse does NOT store
- Jira issue titles, descriptions, comments, or any free-text content
- Individual-level metrics or data attributable to a specific person
- Assignee names or user IDs in any stored key or value
- Sprint names beyond the sprint ID used for ordering
Individual data prohibition
Individual-level data is architecturally excluded. The read:jira-user scope is consumed only to determine team membership grouping. No per-user metric is computed or stored at any layer of the system.
Data retention
Metric aggregates and diagnostic events are retained for 18 months and then automatically purged. Uninstalling OrgPulse from your Jira workspace triggers immediate deletion of all stored configuration, baselines, and diagnostic events for that workspace.
GDPR compliance
OrgPulse does not store personal data as defined by GDPR. Because no personal data is stored:
- There is no data portability obligation for individual users.
- There is no right-to-erasure obligation beyond workspace deletion.
- OrgPulse operates as a data processor on behalf of the Jira workspace administrator (the data controller). The Atlassian Forge platform provides the data processing agreement.
Security
OrgPulse runs entirely on Atlassian's managed Forge infrastructure. No external server is operated. The only outbound connections from OrgPulse are:
- Slack webhook (digest delivery) — URL configured by the workspace administrator, stored in Forge's encrypted environment variable store.
- Email API (digest delivery) — API key configured by the workspace administrator, stored in Forge's encrypted environment variable store.
No customer data is transmitted to these endpoints — only formatted digest content derived from already-computed aggregates.
Contact
For privacy questions or data deletion requests, contact: privacy@orgpulse.io