Data collection policy

Why does Jira collect usage data?

Usage data helps us make educated decisions about improving Atlassian products while also protecting your privacy. We’ll use what we learn to proactively address any potential performance, security, and feature issues.

Sharing usage data is entirely optional. Atlassian won’t gather any usage data unless you choose to participate. You can stop sharing your usage data at any point. More about sharing usage data in Data Center

What data is collected?

You own your data, and you decide what we collect:

  • Basic data collects performance metrics and instance metadata to monitor security and performance.

  • Advanced data additionally includes feature usage.

  • Disabled data sharing means no data is being collected.

The type of data we collect is covered in our Privacy Policy. Please read it, as we've tried to avoid legal jargon and make it as straightforward as possible.

To view a sample of data that might be collected from your specific installation:

  1. Log in as a user with the Jira Administrators global permission.
  2. Go to Administration (), then System, then Advanced, and then Usage data sharing.
  3. Select the Sample Data link.

How is data collected from Data Center installations?

Analytics are collected using the Atlassian Analytics app. The app collects analytics events in a log file which is located in the Jira home directory under the analytics-logs sub directory. The logs are periodically uploaded using an encrypted session and then deleted. If the Jira installation is unable to connect to the Internet, no logs are ever uploaded. 

Enabling and disabling data collection in Jira Data Center

You can switch off analytics collection at any time: 

  1. Log in as a user with the Jira Administrators global permission.
  2. Go to Administration (), then System, then Advanced, and then Usage data sharing.
  3. Select Disabled
  4. Save your change.

Checking the connection

You can test the connection to check if your firewall prevents or causes traffic blockages. If the test fails, ensure our Amazon S3 IP range is allowed through your firewall. More about finding the IP address ranges

You might also need to configure specific access for outbound connections from your instance. If so, all these connections should be HTTPS to *.atlassian.com. If you additionally need a list of ports accessible through your firewall, see Ports used by Atlassian Applications.

Last modified on Nov 18, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.