Privacy Policy
This policy explains how the App handles information when you install or use it on Atlassian Jira Cloud. I (not Atlassian) am responsible for the privacy practices described here for data the App processes outside Atlassian’s own products, subject to the Atlassian Marketplace Partner Agreement and Forge platform rules.
1. Who this applies to
End users and site administrators of Jira Cloud sites where the App is installed.
2. What the App accesses
Through Atlassian Forge APIs (as the signed-in user, except where noted), the App may access:
- Jira issues, projects, boards, sprints, filters, and related fields needed for PI planning walls, Sync, Quick Edit, comments, and setup wizards
- Jira user profile fields needed for assignee/mention pickers and presence (e.g. account id, display name, avatar)
- Atlassian Teams catalogue data (via app-level GraphQL) for team board setup
The App does not collect Atlassian account passwords or personal API tokens from users.
3. What the App stores
| Data | Where | Retention |
|---|---|---|
| Planning wall configuration and canvas state (teams, layout, issue keys, summaries, placements, milestones, risk/ROAM placements, etc.) | Forge Key-Value Storage on Atlassian’s platform for your site | Until the wall is deleted, the App is uninstalled (subject to Atlassian retention), or you clear site data |
| Wall registry (wall names, status, timestamps) | Forge KVS | Same |
| Speaker timer state | Forge KVS (short TTL, hours) | Temporary workshop use |
| Presence (who is viewing a wall) | Ephemeral Forge Realtime — not written to durable app storage | Drops when heartbeats stop |
| Browser cache (localStorage) | Your browser | Local to that browser; mirrors wall data for performance |
Personal identifiers: The App is designed not to store Atlassian accountId or personal display names in durable Forge storage.
Assignees, comment authors, and @mentions are written to Jira (Atlassian’s systems). Presence identifiers stay ephemeral.
Issue content visible on the wall (summaries, labels, status names, etc.) may be cached in wall state so the board can render; that content originates from Jira.
4. Why data is processed
To provide the App’s functionality: multi-user planning walls, Sync with Jira, collaboration features, and related settings.
5. Sharing
- Data stays on Atlassian Cloud / Forge for your customer site.
- I do not sell End User Data.
- I do not send App data to third-party analytics or AI hosts outside Atlassian (the App is configured with no remotes / egress for that purpose today).
- If that changes, this policy will be updated and Marketplace Privacy & Security information will be revised.
6. Where data is stored
App storage uses Atlassian Forge storage and Realtime for the customer’s Atlassian cloud site / region controls as provided by Atlassian. I do not operate a separate application database outside Atlassian for this App.
7. Your choices and rights
Site admins can uninstall the App. Users control Jira issue data in Jira. For privacy requests related to data I process as publisher, contact support@agileenablementtechnology.com. Requests involving Jira-hosted content may need to be handled via your organisation’s Atlassian admin and Atlassian’s processes.
8. Security
Access to Jira APIs follows the installing user’s permissions (and limited app-level Teams catalogue reads). Communication runs through Atlassian Forge.
9. Children
The App is intended for workplace use and not directed at children.
10. Changes
I may update this policy. Material changes will be reflected by updating the effective date and the URL linked from the Marketplace listing.
11. Contact
Privacy / support: support@agileenablementtechnology.com