Security & Privacy

This page describes how NASA handles data, where it runs, and what security certifications apply.

Architecture

Forge Platform

NASA is a Forge app. Unlike Connect apps that run on the vendor's servers, Forge apps execute on Atlassian's infrastructure within your Cloud environment.

• No external servers - NASA does not operate servers outside Atlassian's infrastructure

• No data transfer to third parties - Meeting data stays within your Atlassian Cloud instance

• Atlassian-managed execution - The app runs in sandboxed compute environments managed by Atlassian

• Automatic updates - App updates deploy through the Atlassian Marketplace without downtime

Data Storage

NASA stores all data within your Atlassian Cloud instance using Forge Storage:

• Stream configuration - Meeting questions, settings, schedules, and participant assignments

• Meeting data - Prepared updates, meeting items, comments, emoji reactions, and follow-up flags

• Team Journal - Meeting records retained for 30 days per stream (oldest entries auto-deleted)

• No persistent storage outside Atlassian - When the app is uninstalled, all NASA data is removed

Data Access

What NASA Accesses

NASA accesses Jira and Confluence data within the scope of its permissions:

• Jira issues - Read issue details (summary, status, assignee, priority, story points, comments) for display during preparation and meetings

• Jira boards - Read board configuration to determine which issues to suggest

• Jira users - Read user profiles for participant assignment, avatars, and account IDs

• Confluence pages - Read page titles and content when used as agenda items (requires Data Sources configuration)

• Jira filters - Read saved filters when used for Suggested Issues configuration

What NASA Modifies

• Jira issues - Create new issues, add comments, and update fields (when triggered by user actions during meetings)

• Confluence pages - Create or update pages when exporting Team Journal entries

What NASA Does Not Access

• Email content or personal messages

• Data from other Atlassian apps

• Billing or financial information

• Data outside the Jira and Confluence instances where NASA is installed

OAuth 2.0 Scopes

NASA uses Atlassian's OAuth 2.0 framework with the following scope categories:

• Jira read/write - Required for issue display, creation, and updates during meetings

• Confluence read/write - Required for Confluence page items and Team Journal export

• User identity - Required for participant identification and role assignment

Compliance

Cloud Fortified

Cloud Fortified requires:

• Passing Atlassian's security review process

• Meeting performance and reliability benchmarks

• Maintaining an incident response plan

• Regular security assessments

Marketplace Bug Bounty

NASA participates in the Atlassian Marketplace Bug Bounty program. Security researchers can report vulnerabilities through the program for responsible disclosure.

GDPR

NASA processes personal data (user names, account IDs, meeting participation) as a data processor under the Atlassian Marketplace terms. Since all data is stored within Atlassian's infrastructure, data residency follows your Atlassian Cloud instance's settings.

Webhook Security

Post-Meeting Automation uses outgoing webhooks to trigger Jira Automation rules. These webhooks:

• Are configured per stream by the Scrum Master

• Include a webhook secret for request authentication

• Only fire when a meeting ends (not continuously)

• Send data to Jira Automation endpoints within your Atlassian instance

Related Pages

• Jira Administrator Guide - Installation and permissions management

• App Use Permissions - Control who can access NASA

• Post-Meeting Automation - Webhook-based automation setup

• Getting Started - First-time setup and orientation