OVERALL RATINGS
INSTALLS
1
SUPPORT
- Partner Supported
TRUST SIGNALS
- Requires
- JIRA
- Works with
- CONFLUENCE
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:
Atlassian account IDs of requirement authors, approvers, signers and substitutes
Group and project role IDs and names
Sign-off and rejection receipts with timestamps
Rejection reasons, approval comments and requirement text typed by users
Due dates and approval rules
Salted hashes of signature PINs
Hash-chained audit trail, per-person index of open sign-offs and erasure log
List of out-of-scope End-User Data
App stores the following types of out-of-scope end-user data:
Jira issue property with approval status and pending approver account IDs (Jira data, follows Jira data residency)
Reminder notifications sent by Jira
Forge platform logs
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:
security@stankiguild.comIntegration permissions with Atlassian apps
This app will perform the following actions. It can also perform these actions on behalf of users:
Read and write to app storage service
Jira
Read Assets objects, their attributes values and 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.
Send notifications.
create, modify and delete app properties data
Create and update issue properties.
Create and update project properties.
Confluence
View content permission in Confluence.
Check if a user or a group can perform an operation to the specified content.
View page content.
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
Yes.
Company/Organization is a 'data controller' for the following types of End-User Data:
Only for data we receive outside the app: support correspondence sent to us, and the licence contact details (company, country, site hostname, technical and billing contacts) that Atlassian provides for each licence. For End-User Data stored by the app we are a processor.
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:
The app stores, in Forge hosted storage on the customer's site only: Atlassian account IDs of requirement authors, named approvers, signers and substitutes; group and project role IDs and names; sign-off and rejection receipts with timestamps; rejection reasons, approval comments and requirement text typed by users; due dates and approval rules; salted hashes of signature PINs; for people who enrol an authenticator app, its enrolment record, with the shared secret in Forge encrypted secret storage; a hash-chained audit trail that uses random pseudonyms instead of account IDs; a per-person index of open sign-offs; and an erasure log. In the paid edition it writes the approval status, counts, the earliest open due date and the account IDs of pending approvers to a Jira issue property for JQL; it writes three read-only fields of its own (Approval status, Pending approvers with the account IDs of the approvers who still have to sign, and Approval progress as a percent); and, when an administrator turns reminders on, asks Jira to send reminder and escalation notifications. For a requirement whose approvers follow an Assets field it reads the attributes of the Assets objects (read only, not stored; only the users found become named approvers). It reads a work item's reporter to apply separation of duties, without storing it. For AI agent approvals (paid edition, off by default) it stores, per request, the account ID of the person the agent works for, the agent's self-reported name, the requested action as structured fields with a hash, and the decision and signed receipt; for bulk signing it keeps a short-lived session record with a hash of a one-time token, never the token. Display names are looked up for display and not stored. Where Approval Flow is installed in Confluence it writes one property on a linked page when a requirement asks for acknowledgement: the work item key, the requirement, the account IDs of up to 20 people, the page version, and when and by whom. Erase a person replaces the person's account ID in it with a pseudonym; the uninstall clean-up deletes the app's stored records only, so the property stays on the page after uninstall. It writes one Jira project property per project with the chosen work types. Evidence pack jobs hold changelog data (authors as pseudonyms) and are deleted after 24 hours. We have no access to this data.
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.