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 | Hosted on Atlassian’s infrastructure, with no Huminder-hosted app backend |
| Data Storage | All app data stored via Forge Storage API within Atlassian |
| Data Residency | Governed by the Atlassian services used by the app and the installation’s residency settings |
| 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 work and dependencies. Links can open Jira for actions; AI never automatically updates Jira
- Jira projects and filters: read access to load the selected data source
- User information: display names, avatars and account identifiers from Jira
- Groups: recipient discovery and access checks for shared configurations
What Data Board Studio Stores
- Board configurations: layout preferences, swimlane settings, display options and sharing recipients
- User preferences and release read state: app preferences and per-account records of which bundled release notes have been read
- AI assessments: generated analyses, supporting indexes and provenance in Atlassian-hosted app storage for up to 30 days
- Background analysis jobs: metadata retained for two days
AI is disabled by default and controlled by a Jira administrator. Assessments run only when requested and use Anthropic Claude Haiku 4.5 through Atlassian’s hosted AI service. Opening Board insights or Inspector does not start an AI assessment. Evidence reads respect the requesting user’s Jira permissions. See Board insights and Inspector for scope and limits.
Change events and sharing notifications
Atlassian-hosted realtime channels provide change hints so the app can reread authoritative data. Subscriptions are scoped and authorised; a hint is not permission to read Jira work or a shared board. Jira and configuration reads enforce access again. Periodic reconciliation recovers missed data-change events rather than relying on a permanent event history.
Sharing sends best-effort hints to newly added individual recipients, not a notification to every group member. The current sharing notification stack is session-only, with no persistent sharing inbox or delivery guarantee. Board-sharing discovery and access checks remain separate from notification delivery.
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 |
read:field:jira |
Discover Jira fields for configuration and display |
read:custom-field-contextual-configuration:jira |
Read custom field contextual configuration |
read:field.option:jira |
Read field options for display and ordering |
Data Retention & Deletion
- Configuration data: retained in Forge Storage; uninstall retention and deletion follow Atlassian’s policies
- AI evidence and results: retained for up to 30 days, with background-job metadata retained for two days
- No backups outside Atlassian: Huminder does not maintain separate copies of app data
- Uninstallation: subject to Atlassian Forge retention policies, not a promise of immediate deletion
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.