Privacy Policy
Last updated: March 23, 2026
Overview
CapMap is an Atlassian Forge application that runs entirely within the Atlassian Cloud platform. This privacy policy explains what data CapMap accesses, how it is stored, and your rights regarding that data.
Data Controller
Jakub Duriga
Contact: [email protected]
What Data CapMap Accesses
CapMap accesses the following data from your Atlassian Confluence and Jira instances:
- Confluence pages — Titles, content, and metadata of pages used as CapMap issues and versions
- Confluence page properties — Custom properties stored on pages to hold CapMap metadata (issue type, status, links, release assignments)
- Confluence spaces — Space keys and names for organizing CapMap data
- Confluence user information — Display names of users for attribution purposes
- Jira issues — Issue keys and summaries when linking CapMap items to Jira (optional)
How Data Is Stored
- Forge Storage — CapMap stores application settings and API schema definitions using the Atlassian Forge Storage API. This data is hosted by Atlassian within their cloud infrastructure, in the same region as your Atlassian instance.
- Confluence Page Properties — Issue metadata (type, status, links, release) is stored as Confluence page properties attached to the respective pages.
- Confluence Attachments — API schema exports (YAML, XLSX) are stored as attachments on Confluence pages.
CapMap does not:
- Store any data outside of the Atlassian Cloud platform
- Transmit data to any third-party services
- Use external databases or storage systems
- Collect analytics or telemetry data
- Use cookies or tracking technologies
Data Processing
All data processing occurs within the Atlassian Forge runtime environment. CapMap operates under the Atlassian Forge security model, which means:
- The app runs in a sandboxed environment managed by Atlassian
- Network egress is restricted to Atlassian APIs only
- No external HTTP requests are made
Permissions
CapMap requests the following Atlassian scopes:
| Scope | Purpose |
|---|---|
read:page:confluence / write:page:confluence | Create and manage CapMap issue and version pages |
read:space:confluence | List spaces for settings and organization |
storage:app | Store application settings and API schema data |
read:confluence-props / write:confluence-props | Store and retrieve issue metadata on pages |
write:confluence-file | Attach API schema exports to pages |
search:confluence | Find pages by label and title |
read:confluence-user | Display user names for attribution |
read:jira-work / write:jira-work | Link CapMap items to Jira issues |
read:jira-user | Display Jira user names |
Data Retention
CapMap data persists as long as the associated Confluence pages and Forge storage entries exist. When you:
- Delete a Confluence page — the associated page properties are removed by Confluence automatically
- Uninstall CapMap — Forge Storage data is removed according to Atlassian's data retention policy. Confluence page properties and attachments created by CapMap remain on the pages.
- Use the Purge function — all CapMap metadata, settings, and schema data for a space can be explicitly removed via the Space Settings panel.
Your Rights
As a user of CapMap, you have the right to:
- Access — View all data CapMap stores via the Confluence UI and Space Settings
- Deletion — Remove all CapMap data for a space using the Purge function, or uninstall the app entirely
- Portability — Export API schemas in standard formats (OpenAPI YAML, XLSX)
Changes to This Policy
We may update this privacy policy from time to time. Changes will be reflected in the "Last updated" date above. Continued use of CapMap after changes constitutes acceptance of the updated policy.
Contact
For privacy-related inquiries, contact: [email protected]