Review how AssetPilot for Jira and AssetPilot Connect handle data, security and support. The pages below include release limitations and compliance status for Jira admins and security reviewers.
At a glance
|
AssetPilot for Jira |
AssetPilot Connect |
| Availability |
Available · product overview |
Beta |
| Platform |
Atlassian Forge, Jira Cloud |
Atlassian Forge, Jira Cloud |
| Servers run by Plugins Factory |
None |
None |
| Where app data is stored |
Forge storage, in your Jira site’s region |
Forge storage, in your Jira site’s region |
| Data residency |
Inherited from your Jira site |
Inherited from your Jira site |
| Data sent outside Atlassian |
None. The manifest declares no external hosts. |
Only to services your admins configure: MDM, Slack or Teams, webhook URLs |
| Encryption in transit and at rest |
Provided by Atlassian Forge |
Provided by Atlassian Forge |
| AI or machine learning |
Not used |
Not used |
| Subprocessor for app data |
Atlassian |
Atlassian |
Compliance status
| Item |
Status |
| SOC 2 Type II |
Not certified |
| ISO/IEC 27001 |
Not certified |
| Independent penetration test |
Not yet performed |
| Atlassian Marketplace Bug Bounty |
Not enrolled |
| GDPR and CCPA terms |
Draft Data Processing Addendum |
| Accessibility |
WCAG 2.2 AA target; see the accessibility statement |
| Underlying platform |
Atlassian’s own certifications cover the Forge infrastructure: atlassian.com/trust/compliance |
Documents
Ask a security question
Standard questionnaires (CAIQ Lite, SIG Lite) can be answered on request at security@plugins-factory.com.