This document describes how Board Studio handles your data. For company-wide security practices and certifications, see our Trust Center.
Runs on Atlassian Infrastructure
Board Studio “Runs on Atlassian”, which means:
| Aspect | Detail |
|---|---|
| Hosting | 100% hosted on Atlassian’s infrastructure — no external servers |
| Data Storage | All app data stored via Forge Storage API within Atlassian |
| Data Residency | Data stays in your Atlassian region — fully compliant with Atlassian data residency |
| Execution | App code runs in Atlassian’s secure, sandboxed environment |
What "Runs on Atlassian" Means
Apps with the “Runs on Atlassian” badge benefit from:
- Atlassian’s enterprise-grade security infrastructure
- Built-in compliance with Atlassian’s security standards
- No third-party hosting or data transfer risks
Data Handling
What Data Board Studio Accesses
- Jira issues — Read access to display issues on the board; write access for issue updates made through the app
- Jira projects and boards — Read access to load board configurations
- User information — Display names and avatars for assignees (from Jira’s existing data)
What Data Board Studio Stores
- Board configurations — Your layout preferences, swimlane settings, and display options
- No issue data copied — Issues are read directly from Jira, not duplicated
What We Do NOT Do
- ❌ Send data to external servers
- ❌ Use third-party analytics or tracking
- ❌ Collect personal data beyond what Jira provides
- ❌ Share or sell any data to third parties
- ❌ Store data outside Atlassian’s infrastructure
App Permissions
Board Studio follows the principle of least privilege, requesting only the minimum scopes required:
| Permission | Purpose |
|---|---|
storage:app |
Store board configurations in Forge Storage |
read:jira-work |
Read issues, projects, sprints, and boards to display on Board Studio |
read:jira-user |
Read user information for assignee display |
read:avatar:jira |
Display project and user avatars on cards |
read:filter:jira |
Load saved filters as data sources |
read:application-role:jira |
Verify user access permissions |
read:group:jira |
Read group information for permission checks |
read:user:jira |
Read user details for display and filtering |
manage:jira-configuration |
Access custom field contexts and options for proper field value display |
Data Retention & Deletion
- Configuration data — Retained while the app is installed; deleted when the app is uninstalled
- No backups outside Atlassian — We do not maintain separate copies of your data
- Uninstallation — Removing the app deletes all stored configurations
Compliance
| Requirement | Status |
|---|---|
| Atlassian Cloud App Security Requirements | ✓ Compliant |
| Atlassian EcoScanner | ✓ Scanned |
| Security Bug Fix SLAs | ✓ Adhering |
| GDPR | ✓ Compliant |
| Data Residency | ✓ Supported |
Related Documents
Contact
For questions about data handling in Board Studio:
© 2025 Huminder OÜ. All rights reserved.