Is Time Tracker by Tempo safe?

Clean risk

Time Tracker by Tempo submits a hardcoded Atlassian OAuth client secret during token exchange flows.

The extension's background OAuth code posts a bundled Atlassian client ID and client secret when exchanging authorization codes and refresh tokens. Those requests go to Atlassian's OAuth token endpoint as part of Jira authentication.

Tempov2.0.18Chrome Web Store
2Risk
Who publishes it

Tempo - no other listings under this identity

What this publisher told the store about itself, and the other listings that told it the same thing.

AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.

Publishers can request a review.

What it can do

Permissions this extension asks for, as declared in version 2.0.18. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.

  • Read and change your data on every site you visit

    <all_urls>

  • See the address and title of every tab you have open

    tabs

  • Store data in your browser

    storage

  • Run its own code inside the pages you visit

    scripting

Where it sends data

Destinations our analysis observed Time Tracker by Tempo contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.

  • auth.atlassian.com

    Time Tracker by Tempo sends data to auth.atlassian.com. No other extension we have analysed sends data here.

Updated 30 September 2026nlpnopimcnncncmmjdijebhlmkfandpl