OVERALL RATINGS
SUPPORT
- Partner Supported
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 but does not store the following types of End-User Data:
summary
description
comments
issue labels
issue type names
Smart Checklist field markdown content
Data residency for in-scope End-User Data
Not applicable.
Marketplace app stores End-User Data exclusively within Atlassian apps and services, which don't support data residency options yet due to Atlassian’s current roadmap
App REST APIs
This app provides custom REST APIs for integration with external tools. These APIs are not hosted on the Forge platform.
Workflow Toolkit exposes a single public REST webtrigger endpoint for external integrations (Zapier, Make, n8n, custom scripts): • URL pattern: https://{forge-app-id}.hello.atlassian-dev.net/x1/{install-token} • Method: GET only • Response: JSON • Query parameters: - projectKey (required) — Jira project key - include (optional) — comma-separated: "templates" and/or "checklists" - issueKey (optional) — when include=checklists, return data for a single issue - token (optional) — additional auth shared secret configured by site admin The endpoint URL itself is an unguessable per-install shared secret (Atlassian-generated). For additional security, site admins can configure a token in the app's admin page; when set, the token is required as a query parameter and stored encrypted via kvs.setSecret(). The endpoint returns the project's checklist templates and Smart Checklist values from issues in the project. Read-only — no mutations. CORS not enabled. Rate-limited by Forge runtime. No external mutating endpoints.
List of in-scope End-User Data
Not applicable.
Marketplace app stores End-User Data exclusively within Atlassian apps and services, which don't support data residency options yet due to Atlassian’s current roadmap
List of out-of-scope End-User Data
Not applicable.
Marketplace app stores End-User Data exclusively within Atlassian apps and services, which don't support data residency options yet due to Atlassian’s current roadmap
Migration of in-scope End-User Data between data residency supported locations
Not applicable.
Marketplace app stores End-User Data exclusively within Atlassian apps and services, which don't support data residency options yet due to Atlassian’s current roadmap
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
No
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
Not applicable, App neither stores End-User data nor supports data residency options.
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:
support@fellowsheepstudios.comIntegration permissions with Atlassian apps
View boards, issues on a board, issues from a backlog, reports, and versions.
Read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs.
View projects.
View sprints and sprint related issues and properties.
Read and write to app storage service
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
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
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 summary, description, comments, labels, issue types, status changelog, and Smart Checklist field content (stored as the wt.smartChecklist issue entity property) — processed on behalf of the customer for AI checklist generation, template inference, Time in Status reports, and webhook/REST integration. Templates and configuration are stored in Forge KVS scoped to the customer's site.
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
Yes,
Standard Contractual Clauses (SCCs) and EU-US Data Privacy Framework certification — implemented via the customer's direct Data Processing Agreement with Anthropic PBC under the BYO API key model. Workflow Toolkit does not proxy data: Forge runtime sends requests directly to api.anthropic.com using the customer's own API key. Anthropic acts as the data importer under SCCs and is self-certified to the EU-US DPF (https://www.dataprivacyframework.gov/list).
Privacy enhancing technologies (PETs) used to protect End-User Data
Yes
TLS 1.2+ for all external connections, Forge KVS encrypted secret storage for API keys, auto-wipe on uninstall via lifecycle trigger
Data Processing Agreement (DPA) for customers
Yes,
DPA
Did you find this information useful?
Atlassian will use this feedback to serve you better.