Free app
OVERALL RATINGS
INSTALLS
12
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 provides custom REST APIs for integration with external tools. These APIs are hosted on the Forge platform and are disabled by default. Once enabled, any verified Atlassian accounts in your organization can create integrations that access these APIs.
List of in-scope End-User Data
App stores the following types of in-scope end-user data:
Plan data: issue keys, summaries, statuses, dates, estimates, dependencies, assignee names and account IDs, and reporter names
Plan settings, members, roles and per-person capacity
Drafts not yet applied (kept 24 hours)
Baselines, snapshots, scenarios and portfolios
Sponsor reports, notes and sent versions
AI results stored with a plan
Audit log (60 days)
Sponsor report pages published to the customer's Confluence
Who is viewing a plan (account ID, display name, avatar), kept in app storage and dropped from view after 90 seconds of inactivity
Who holds a plan's editing lock (account ID)
REST API tokens, stored as hashes with their owner's account ID (they expire after 90 days by default)
The account IDs the app reports to Atlassian's personal data reporting API, with dates (and, while a reporting cycle runs, the new names of changed accounts)
List of out-of-scope End-User Data
App stores the following types of out-of-scope end-user data:
Plan text sent to the Atlassian-hosted Forge LLM for briefs and reviews (Atlassian lists AI data as not pinnable)
The setup backup kept as Jira user properties on the app's account (Atlassian's in-scope Jira list does not name user properties)
Forge app logs (Atlassian developer console)
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:
office@leanzero.netIntegration permissions with Atlassian apps
Take Jira administration actions (e.g. create projects and custom fields, view workflows, manage issue link types).
Create and edit project settings and create new project-level objects (e.g. versions and components).
View the configuration, project features, filters, properties, and quick filters for a board.
View boards, issues on a board, issues from a backlog, reports, and versions.
Read Assets objects, their attributes values and details.
View issue details.
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.
View page content.
View projects.
Read customer request data, including approvals, attachments, comments, request participants, and status/transitions. Read service desk and request types, including searching for request types and reading request type fields, properties and groups.
View space details
Report user accounts that an app is storing personal data for.
Read and write to app storage service
Move (rank) issues and update issue estimates.
Create and edit issues in Jira, post comments as the user, create worklogs, and delete issues.
Create and update pages.
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
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
No
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 issue keys, summaries, statuses, dates, estimates and dependencies
Assignee account IDs and display names, and reporter display names
Plan owners, members, roles and per-person capacity
Drafts (24 hours), baselines, snapshots, scenarios, portfolios, sponsor reports and notes
Plan data sent to the Atlassian-hosted Forge LLM for AI features (keys, summaries, statuses, dates, dependencies; for some features recent comment text with mentions removed and authors left out, or project and epic text), text a person types into the AI helpers, and AI results
Who is viewing a plan (account ID, name, avatar; hidden after 90 seconds, removed when they leave or the next viewer arrives) and who holds its editing lock
Audit log entries with account IDs (60 days)
Account IDs reported to Atlassian's personal data reporting API once per reporting cycle (7 days by default; 1 to 30 days when Atlassian sets the period), with dates only
Closed accounts: the person's capacity settings, last-viewed marks, AI answer caches and own drafts are deleted, they are removed from plan members, and plan owner and last writer show Former user
Closed accounts keep their name in sealed records (snapshots, scenarios, captured sponsor reports), report notes, capacity rosters, portfolios, others' capacity settings and an AI structure not rebuilt since, and their account ID where the app records who did something, such as plan ownership and the 60-day audit log
The setup backup kept as Jira user properties on the app's account (Jira admins only; its next run drops erased data, the older copies it keeps hold it until they age out; a Jira admin can delete it in Settings, Maintenance, Backup and restore)
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
Not applicable.
Company/Organization is not subject to the CCPA.
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
Yes,
DPA
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.