Subprocessor List — Chat Relay for Jira
Last updated: 19 October 2026
This list identifies providers appointed by Darkwood Apps to process personal data for Chat Relay for Jira. Atlassian maintains a separate list for providers it appoints to support Forge.
| Provider | Service and role | Data and purpose | Location information |
|---|---|---|---|
| Atlassian Pty Ltd / Atlassian Forge | App runtime, Forge events and queues, installation-scoped KVS, and encrypted secret storage. Atlassian processes app data to host and operate the Service. | Configured app data, issue/event data needed for rule processing, selected account IDs used by optional author-exclusion rules, delivery state, and the customer's webhook credential. | Forge-hosted storage follows the applicable data-residency setting of the customer's host Atlassian app. Runtime and onward processing follow Atlassian's applicable terms and DPA. See Atlassian's official subprocessor list. |
Customer-selected destination
Google Chat receives the notification payload at chat.googleapis.com because the customer selects and controls that destination. Google is not appointed by Darkwood Apps as a subprocessor for this Service; it is an external recipient and processing path selected by the customer. Google's processing and message retention follow the customer's Google Workspace terms and configuration.
Darkwood Apps does not operate a backend for Chat Relay and does not use an external log-export provider for customer issue data. The static documentation website does not receive Jira event payloads.
Changes and notices
For a new or changed subprocessor appointed by Darkwood Apps, this page will be updated at least 30 days before that provider begins processing customer personal data. Customers may request a notice through support@darkwoodapps.com.
Atlassian maintains its own onward-subprocessor list and change process under its terms. The linked Atlassian page is authoritative for those providers and is outside Darkwood Apps' publication control.
See the Data Processing Addendum, Privacy Policy, and Support.