Privacy Policy

Effective: September 23, 2026

This policy describes the current CapacityPulse Forge architecture. Provider identity details will match the Atlassian Marketplace partner record before public paid launch.

What CapacityPulse accesses

CapacityPulse may read Scrum board metadata, sprint metadata, issue status, issue type, and status-category-change timestamps that the current Jira user is permitted to access.

What CapacityPulse stores

CapacityPulse stores only app settings such as a selected default board identifier in Atlassian Forge-hosted KVS. It does not intentionally persist Jira issue descriptions, comments, attachments, historical issue lists, or individual productivity profiles.

Planning Brief

The Planning Brief is generated deterministically from aggregate forecast statistics inside Forge. It makes no external AI or LLM request.

External data transfer

The current release is designed without an external application server, third-party analytics endpoint, or external AI service. Application execution and app storage use Atlassian Forge services.

Authorization

Jira data reads use the current user's Jira authorization context. CapacityPulse does not bypass Jira permissions.

Contact

Privacy inquiries: privacy@capacitypulse.net