OVERALL RATINGS
SUPPORT
- Partner Supported
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 Marketplace app does not process or store End-User Data outside of Atlassian apps and services.
Data residency for in-scope End-User Data
Yes.
Marketplace app stores End-User Data exclusively within Atlassian apps and services which support data residency options, as outlined
here.App REST APIs
This app does not provide REST APIs.
List of in-scope End-User Data
App stores the following types of in-scope end-user data:
Access snapshots: Atlassian account IDs of users and app accounts, their Jira project permissions, and how each was granted (group or project role name)
Review campaigns: campaign name, projects in scope, due date, creator's account ID
Reviewer assignments: reviewer's account ID and submission status per project
Review decisions: outcome, written justification, decider's account ID and time
Evidence log: hash-chained record of review actions with actor account IDs, timestamps, and reasons given for cancelling or reopening
App settings: the list of permissions the site treats as elevated
List of out-of-scope End-User Data
App stores the following types of out-of-scope end-user data:
App logs in the Forge developer console: snapshot and campaign identifiers, project keys, counts and Jira error messages; no account IDs, names or text typed by users
Display names and account types read from Jira while an evidence pack is exported, held in memory for that request and never stored
Snapshot work items in the Forge async events queue while a snapshot runs: project IDs and batch offsets, deleted once processed
Evidence packs (JSON and HTML) after a site user downloads them, stored on that user's device under the customer's control
Migration of in-scope End-User Data between data residency supported locations
Yes.
Marketplace app stores End-User Data exclusively within Atlassian apps and services which support data residency options, as outlined
here.End-User Data shared with third-party entities
Not applicable.
Marketplace app does not store End-User Data outside of Atlassian apps and services.
End-User Data accessed in logs
Yes
End-User Data processed and/or stored in logs outside of Atlassian apps and services
No
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
Yes.
Marketplace app stores End-User Data exclusively within Atlassian apps and services which support data residency options, as outlined
here.Custom retention period for End-User Data
Not applicable.
Marketplace app does not store End-User Data outside of Atlassian apps and services.
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:
help@8lax.comIntegration permissions with Atlassian apps
View application roles.
View system and custom avatars.
View fields.
View user groups.
Read issue type hierarchies.
View issue types.
View permission schemes.
View permissions.
View project categories.
View project roles.
View project versions.
View project components.
View project properties.
View projects.
View users.
Read and write to app storage service
More information on the justification of app’s integration permissions are shared by the app’s partner hereCompliance certifications
None.
Marketplace Security Bug Bounty Program participant
No
CAIQ Lite
CAIQ Lite Questionnaire has not been submitted
Security policy
Response not provided by the partner
Full disk encryption for data stored outside of Atlassian
Not applicable.
Marketplace app does not store End-User Data outside of Atlassian apps and services.
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:
Licence, billing and technical contact details that Atlassian shares with the partner through the Marketplace (name, email address, organisation)
Support correspondence sent to help@8lax.com (sender's name, email address and message)
App logs that Atlassian shares with the developer: identifiers, project keys, counts and Jira error messages
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:
Atlassian account IDs of the site's users and app accounts, with their Jira project permissions and the groups or project roles that grant them
Display names and account types read from Jira when an evidence pack is exported
Review records: campaigns, reviewer assignments, decisions with written justifications, and reasons for cancelling or reopening
Evidence log of review actions with actor account IDs and timestamps
Company/Organization is a 'business' under the California Consumer Privacy Act of 2018 (CCPA) with reference to this app
Not applicable.
Company/Organization is not subject to the CCPA.
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:
Atlassian account IDs of the site's users and app accounts, with their Jira project permissions and the groups or project roles that grant them
Display names and account types read from Jira when an evidence pack is exported
Review records: campaigns, reviewer assignments, decisions with written justifications, and reasons for cancelling or reopening
Evidence log of review actions with actor account IDs and timestamps
General Data Protection Regulation (GDPR) approved mechanism for transferring European Economic Area (EEA) residents’s End-User Data outside of the EEA
Not applicable.
Marketplace app does not process or store End-User Data outside of Atlassian apps and services.
Privacy enhancing technologies (PETs) used to protect End-User Data
Not applicable.
Marketplace app does not process or store End-User Data outside of Atlassian apps and services.
Data Processing Agreement (DPA) for customers
No
Atlassian trust programs
RUNS ON ATLASSIAN
This app runs on Atlassian infrastructure to meet enterprise needs.
Hosted on Atlassian
Data stored within Atlassian
Data residency compliant
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.