Smart Field Defaults for Jira
Last updated: 2026-09-22
This Data Processing Addendum ("DPA") supplements the ‣ between Workflowly ("Processor") and the customer ("Controller") and applies to the extent Processor processes personal data on Controller's behalf in connection with the Smart Field Defaults for Jira app ("App").
For personal data processed through the App, the Controller determines the purposes and means of processing (e.g., which rules to configure and which Jira users to reference in them). Processor processes that personal data solely on the Controller's documented instructions, as expressed through the Controller's use of the App.
Processing covers the personal data described in Section 3, for the duration the App remains installed on the Controller's Jira site, plus any period required to comply with Processor's own legal obligations.
| Category | Data | Data subjects |
|---|---|---|
| Identifiers | Atlassian account IDs referenced in rule actions (e.g., an assignee default) | Controller's Jira users (employees/contractors of Controller, or their end customers if Jira is used externally) |
| Usage metadata | Execution log entries (issue key, timestamp, matched rule, applied fields, status) | Same as above, indirectly, where a log entry references an account ID |
The App does not process special categories of personal data (Art. 9 GDPR), nor data relating to criminal convictions.
Personal data is processed solely to: (a) evaluate and apply the Controller's configured field-default rules when issues are created or updated, and (b) record execution logs so the Controller can audit rule behavior. See ‣ for retention specifics.
Processor uses Atlassian (Forge platform infrastructure, including the Forge Entity Store) as its sole sub-processor. Atlassian's sub-processor list and compliance certifications are published at atlassian.com/trust/compliance. Processor will provide reasonable advance notice of any change to this sub-processor and an opportunity for Controller to object.
Processor relies on the security architecture described in the Security Statement: encryption in transit and at rest (via Atlassian's Forge platform), Forge-managed OAuth authentication, admin-only access to the App's configuration, and minimal, least-privilege API scopes.
Because all processing occurs within Atlassian's Forge infrastructure, any cross-border transfer of personal data is governed by Atlassian's own data residency and transfer mechanisms (including Standard Contractual Clauses where applicable), as described in Atlassian's own DPA at atlassian.com/legal/data-processing-addendum.
Processor will assist Controller, insofar as reasonably possible, in responding to data subject requests (access, rectification, erasure, restriction, portability, objection) as described in Section 7 of the Privacy Policy. Controller can independently fulfill most such requests directly within the App (editing or deleting rules, disabling rules, uninstalling the App).