Privacy Policy

1. Introduction

This Privacy Policy describes how Appcento ("we," "us," or "our") collects, uses, and protects information in connection with Bulk Edit for Jira (the "App"), a Jira Cloud application available on the Atlassian Marketplace.

Bulk Edit for Jira is designed with a privacy-first, zero-egress Forge architecture - all data is processed and stored exclusively within Atlassian's infrastructure, and never leaves Atlassian infrastructure.

3. Data we do not collect

Bulk Edit for Jira does not collect, access, store, or transmit:

• Personal information beyond Atlassian Account IDs
• JQL queries (used during session only, not stored)
• Data that leaves Atlassian infrastructure
• Third-party analytics data
• Cookies or browser storage

4. Where data is stored

All data is stored exclusively in Atlassian Forge Storage (KVS and SQL databases). Data is encrypted at rest by Atlassian, scoped to the Atlassian site where the App is installed, and never transmitted to any external server or Appcento-owned infrastructure.

Bulk Edit for Jira makes zero external network calls. The App runs entirely within Atlassian's Forge runtime environment.

5. Third-party services

Bulk Edit for Jira uses no third-party services, analytics tools, or external dependencies. The only APIs accessed are Atlassian's Jira REST APIs, called from within the Forge runtime using the App's declared permissions.

6. Data processing

During execution, the App reads issue field values, applies edits via Jira APIs, and stores pre-edit snapshots for undo capability. Field values are processed in the Forge runtime and stored in Forge KVS. All processing occurs within Atlassian's infrastructure.

7. Data retention and deletion

Data retention follows these timelines:

• Undo snapshots: 7 days (Free), 30 days (Standard) - automatically cleaned by scheduled trigger
• Usage statistics: Lifetime of installation
• Entity properties: Cleared on undo or manually via API
• On uninstall: Data flagged for 30-day recovery window. Atlassian retains Forge storage for 28 days per their policy.

8. Permissions (scopes)

Bulk Edit for Jira requests the following Atlassian Forge scopes - the minimum required to function:

• read:jira-work - read issue fields, search issues via JQL, fetch issue metadata
• write:jira-work - update issue fields, execute bulk changes, transition statuses, set entity properties
• read:jira-user - read user display names for assignee/reporter fields and permission checks
• storage:app - read/write to Forge KVS and Forge SQL for undo snapshots, edit history, and configuration
• All scopes use allowImpersonation: true - the App never performs actions beyond the individual user's Jira permissions.

9. GDPR compliance

Bulk Edit for Jira is designed to be compliant with GDPR. Undo snapshots containing user-identifiable field values (e.g., assignee account IDs) are automatically purged per configured TTL.

The App does not create new personal data profiles. Users can request data deletion by contacting support.

Any Jira user data is managed directly by Atlassian and governed by Atlassian's own privacy policies.

10. Children's privacy

Bulk Edit for Jira is a business productivity tool and is not directed at children under 16. We do not knowingly collect personal information from children.

11. Changes to this policy

We may update this Privacy Policy from time to time. We will notify users of material changes by updating the "Last Updated" date at the top of this page. Continued use of the App after any changes constitutes acceptance of the revised policy.