We’re renaming ‘products’ to ‘apps’

Atlassian 'products’ are now ‘apps’. You may see both terms used across our documentation as we roll out this terminology change. Here’s why we’re making this change

Teamwork Graph data, privacy, and usage guidelines

It is important to understand how Atlassian handles permissions and your data.

Experiences and quality can vary and be dependent on a number of things including the knowledge sources provided, the user's access, and if you use our generative AI features, the probabilistic nature of LLMs (large language models).

Interoperation with third-party apps

Atlassian apps include features that are designed to interoperate with third-party apps. For example, you may connect third-party apps to Atlassian sites using connectors. Before connecting to a third-party app, we recommend reviewing the types of data stored in that app, and confirming that connecting the data aligns with your internal data use policies and practices.

Connecting Atlassian with third-party apps may give third parties access to information you choose to use in connection with their apps, and your use of third-party apps and information you share may be governed by their terms and policies, including their privacy policies.

For more detail, see “Third Party Services” in Atlassian’s Privacy Policy.

Permissions

Teamwork Graph synchronises with access controls and permission settings from connected third-party apps and your Atlassian apps. This helps ensure that users only see content they have access to.

Because Atlassian relies on these permissions you have set, before connecting a third-party app you should check and remind users to check the permissions set up for that app.

For example, if you connect Google Drive to Atlassian, users need to log in and connect their Atlassian account to Google Drive to use Google Drive data in Atlassian. Once authorized, users will be able to see public documents and private documents that they already had access to.

We ‘listen’ for permission changes, and update the Atlassian data stores with changes.

Deleted data

For admin-managed connectors, we ‘listen’ for content deletion, and update the Teamwork Graph the with changes. For example, once the Atlassian data store is updated, content that’s deleted from a connected third-party app will not appear in Atlassian sites. For more information on permissions and connectors, see Manage Teamwork Graph connectors.

If an organization admin uninstalls a third-party product from Atlassian Administration, we will delete the content stored in Teamwork Graph within 30 days.

Please note that certain apps may retain data longer in certain scenarios:

  • Github connector: because your GitHub data is integrated through the GitHub for Jira app, data is deleted from Atlassian experiences only if you disconnect GitHub from Atlassian Administration and uninstall the GitHub for Jira app. See how to disconnect the GitHub connector for more information.

  • Workday connector: Once you uninstall the Workday connector, Talent and Teams apps may retain and continue to process a static copy of data from this connector.

    • Talent: Workday data is retained in the Talent app unless you initiate deletion from within the Talent app (which you can initiate at any time). Learn more about how the Workday connector works with Talent

    • Teams: Workday data (and any teams created from the sync) is deleted from the Teams app, unless you previously stopped syncing Workday to Teams. Customer can delete data from Teams at anytime.

Data usage

We import and store the workspace of the third-party app you connect (for example, the entire Google Drive or the SharePoint workspace).

You can refine the scope of the data indexed with some specific connectors (such as Google Drive and SharePoint) using a blocklist. For more, see Manage blocklist.

To make your data available in Atlassian sites, we store the content for each file found in a third-party app and associated usage data. We also store permissions settings about the file to ensure that we only show content that users have access to. We use this data to serve your Atlassian features.

We may also use it for troubleshooting and debugging, or to solve support queries you or your team raise with us.

User data obtained via Google Workspace API Sensitive or Restricted scopes is not used to develop, improve, or train generalization AI and/or ML models.

Usage guidelines

As always, remember to abide by the Acceptable Use Policy when using data from Teamwork Graph in Atlassian experiences.

For more information on how Atlassian accesses, uses, stores or shares data, see Atlassian’s Privacy Policy.

Still need help?

The Atlassian Community is here for you.