Skip to main content
Skip table of contents

Data Privacy FAQ

This documentation is provided “as is” as part of a Beta program, independent of TempoLabs.  As such, the features and functionality presented are subject to change, may not work as expected, and may not match the current or final released version of the software.

For a complete look at Tempo’s data privacy and security policies, visit trust.tempo.io.

Where does my data reside?

Capacity Insight data resides in the US. You can only install Capacity Insights on Tempo apps located in the US. For information about moving your Tempo data to the US, see https://support.atlassian.com/security-and-access-policies/docs/moving-your-marketplace-apps-data-to-another-location/

If your Jira instance or Tempo app is hosted in Europe, you can’t install Capacity Insights. You must migrate your data to the US.

How is my data used?

Anonymized data is used to improve Capacity Insights predictions.

How is my data from app integrations used?

The data is read to provide work insights. We do not copy, modify, or delete any information that we can access through app integrations. App integrations include:

  • Google Calendar

  • Microsoft Office 365 Calendar

  • GitHub

  • GitLab

  • VS Code

  • Jetbrains

Google Calendar

The following is collected and stored:

  • Masked User ID that is untraceable

  • Event ID (associated with your calendar events and activities)

  • Calendar title and description

  • Rejected and Accepted events

  • Duration and time of calendar event

We require read access to the calendar and the user profile. We use the user profile to associate calendar events with the appropriate Tempo user.

Microsoft Office 365 Calendar

The following is collected and stored:

  • Masked User ID that is untraceable

  • Event ID (associated with your calendar events and activities)

  • Calendar title and description

  • Rejected and Accepted events

  • Duration and time of calendar event

We require read access to the calendar and the user profile. We use the user profile to associate calendar events with the appropriate Tempo user.

GitHub

The app reads data from the following events, captured through GitHub’s webhooks:

  • Create

  • Push

  • Commit

  • Pull Request

We require read access to code, metadata, and pull requests. No code or other information is retained from GitHub. We only create worklogs based on the activities performed in GitHub.

GitLab

The app reads data from the following events, captured through GitLab’s webhooks:

  • Merge Request

  • Merge Request Comment

  • Push

    • If your email is public, the app also reads the commit details of the push

We require read access to your GitLab API. No data is retained from GitLab. We only create worklogs based on the activities performed in GitLab.

VS Code

No data is retained from VS Code. We only create worklogs based on the activities performed in VS Code.

JetBrains IntelliJ

The app reads data from the following events:

  • Save

  • Commit

  • Checkout

No data is retained from IntelliJ. We only create worklogs based on the activities performed in IntelliJ.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.