Timesheets by Tempo - Jira Time Tracking
OVERALL RATINGS
INSTALLS
25,855
SUPPORT
- Partner Supported
- Cloud Migration Assistance
TRUST SIGNALS
Privacy and Security details
The Atlassian Marketplace partner is responsible for the accuracy of the information provided below. Details with a verified status are confirmed by Atlassian. For any further queries, contact the partner.
Data storage and management
End-User Data processed and/or stored outside of Atlassian apps and services (excluding process/storage of End-User Data in logs)
The app processes the following types of End-User Data:
Jira information: Atlassian account ID, user email (SMTP notifications/reminders), Jira authentication token, project/issue ID, key, name, issue type, URL to an issue, summary and description, estimated and original remaining seconds, status, linked issue, custom fields and their values (if enabled by customer), summary of any changes to the issues via changelogs, etc. For more details on how this application handles the data from your Jira instance, you can read our in-depth white paper. It's available on the Trust Center at https://trust.tempo.io/item/white-papers
Worklogs
Workload and Holiday Schemes
Analytics, Usage data: userID, user actions, app performance metrics, feature usage, device information, browser information, etc.
Content posted, shared, received in the app by end-users.
No sensitive PII is anticipated to be processed.
The app stores the following types of End-User Data:
Jira information: Atlassian account ID, Jira authentication token, project/issue ID, key, name, issue type, URL to an issue, summary and description, estimated and original remaining seconds, status, linked issue, custom fields and their values (if enabled by customer), summary of any changes to the issues via changelogs, etc.
Worklogs
Workload and Holiday Schemes
Analytics, Usage data: userID, user actions, app performance metrics, feature usage, device information, browser information, etc.
Content posted, shared, received in the app by end-users.
No sensitive PII is anticipated to be processed.
Data residency for in-scope End-User Data
Marketplace app supports data residency and stores End-User Data independently outside of Atlassian apps and services in the following locations:
🇩🇪
Germany
🇺🇲
United States of America
More information on the Marketplace app’s data residency policy can be found in app’s product documentation or please contact the respective Marketplace app partner at
sales@tempo.ioApp REST APIs
This app provides custom REST APIs for integration with external tools. These APIs are not hosted on the Forge platform.
Tempo exposes public REST APIs that allow customers and third-party tools to integrate programmatically with Tempo data. The APIs are documented at apidocs.tempo.io and support OAuth 2.0 authentication. Customers can generate scoped API tokens with defined access levels and expiry dates via Tempo's Settings > API Integration. Available API namespaces include: Worklogs, Teams, Approvals, Workload and Holiday Schemes, and Accounts. The base URL for Cloud is https://api.tempo.io/4/ with Bearer token authentication. These APIs are used both by Tempo's own suite of apps (Timesheets, Capacity Planner, Financial Manager) and by customers building custom integrations (e.g., BI tools, HR systems, Azure Synapse, etc.). Please see API documentation for more information: https://apidocs.tempo.io/
List of in-scope End-User Data
App stores the following types of in-scope end-user data:
Jira information: Atlassian account ID, Jira authentication token, project/issue ID, key, name, issue type, URL to an issue, summary and description, estimated and original remaining seconds, status, linked issue, custom fields and their values (if enabled by customer), summary of any changes to the issues via changelogs, etc.
Worklogs
Workload and Holiday Schemes
Content posted, shared, received in the app by end-users.
List of out-of-scope End-User Data
App stores the following types of out-of-scope end-user data:
Analytics, Usage data: userID, user actions, app performance metrics, feature usage, device information, browser information, etc.
Migration of in-scope End-User Data between data residency supported locations
Yes
End-User Data shared with third-party entities
End-User Data accessed in logs
Yes
End-User Data processed and/or stored in logs outside of Atlassian apps and services
Yes
End-User Data in logs shared with third-party entities
No
End-User Data in logs shared with third party entities integral for app functionality
No
End-User Data stored after app is uninstalled
Minimum storage period post un-install:
0 days
Maximum storage period post un-install:
90 days
Custom retention period for End-User Data
Yes
Supports customer-managed egress
No.
The app only accesses domains declared during installation.
Security and compliance
Contact for app security issues
App’s e-mail contact:
sales@tempo.ioIntegration permissions with Atlassian apps
Take Jira administration actions (e.g. create projects and custom fields, view workflows, manage issue link types).
Fetch, register, refresh, and delete dynamically declared Jira webhooks.
Access and interact with your data from outside of Atlassian.
Access and interact with your data as the logged-in user from outside of Atlassian.
View email addresses of all users regardless of the user’s profile visibility settings.
View user information in Jira that the user has access to, including usernames, email addresses, and avatars.
Read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs.
Read and write to app storage service
create, modify and delete app properties data
Create and edit issues in Jira, post comments as the user, create worklogs, and delete issues.
More information on the justification of app’s integration permissions are shared by the app’s partner hereCompliance certifications
SOC2
ISO27K
SOC 2 Type 2
ISO 27001:2022
ISO 27701:2019
GDPR
CCPA
Marketplace Security Bug Bounty Program participant
Yes.
App is a participant in Marketplace Security Bug Bounty Program.
CAIQ Lite
Yes,
CAIQ Lite responseSecurity policy
Full disk encryption for data stored outside of Atlassian
Yes
App accesses Atlassian Personal Access Tokens (PATs), user account passwords, or another type of shared secret
No
Privacy
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policyCompany/Organization is a 'data controller' under the General Data Protection Regulation (GDPR) with reference to this app
Yes.
Company/Organization is a 'data controller' for the following types of End-User Data:
Analytics, Usage data: userID, user actions, app performance metrics, feature usage, device information, browser information, etc.
Company/Organization is a 'data processor' under the General Data Protection Regulation (GDPR) with reference to this app
Yes.
Company/Organization is a 'data processor' for the following types of End-User Data:
Jira information: Atlassian account ID, user email (SMTP notifications/reminders), Jira authentication token, project/issue ID, key, name, issue type, URL to an issue, summary and description, estimated and original remaining seconds, status, linked issue, custom fields and their values (if enabled by customer), summary of any changes to the issues via changelogs, etc.
Worklogs
Workload and Holiday Schemes
Content posted, shared, received in the app by end-users.
No sensitive PII is anticipated to be processed.
Company/Organization is a 'business' under the California Consumer Privacy Act of 2018 (CCPA) with reference to this app
Yes.
Company/Organization is a 'business' for the following types of End-User Data:
Analytics, Usage data: userID, user actions, app performance metrics, feature usage, device information, browser information, etc.
Company/Organization is a 'service provider' under the California Consumer Privacy Act of 2018 (CCPA) with reference to this app
Yes.
Company/Organization is a 'service provider' for the following types of End-User Data:
Jira information: Atlassian account ID, user email (SMTP notifications/reminders), Jira authentication token, project/issue ID, key, name, issue type, URL to an issue, summary and description, estimated and original remaining seconds, status, linked issue, custom fields and their values (if enabled by customer), summary of any changes to the issues via changelogs, etc.
Worklogs
Workload and Holiday Schemes
Content posted, shared, received in the app by end-users.
No sensitive PII is anticipated to be processed.
General Data Protection Regulation (GDPR) approved mechanism for transferring European Economic Area (EEA) residents’s End-User Data outside of the EEA
Yes,
Our publicly available DPA reflects all the important details regarding the intended processing, as well as incorporates the EU SCCs including technical organizational measures as a basis for transfer outside of the EU.
Privacy enhancing technologies (PETs) used to protect End-User Data
Yes
Pseudonymization and anonymization
Data Encryption
Access Control
Secure Deletion
MFA
RBAC
Data Processing Agreement (DPA) for customers
Yes,
DPA
Atlassian trust programs
ATLASSIAN ENTERPRISE CERTIFIED
This app is verified to meet common enterprise needs for compliance, security, reliability, privacy, accessibility, and responsible AI use.
Advanced security - penetration testing and Bug Bounty participation
Proven reliability - mature incident response and operational standards
Privacy and compliance - SOC 2 or ISO 27001 and data residency
How do these programs address app trust?
Marketplace programs help Marketplace partners achieve the highest consistent standards for application security and privacy.
About trust programsDid you find this information useful?
Atlassian will use this feedback to serve you better.