Data Processing Addendum — Chat Relay for Jira
Last updated: 19 October 2026
This page describes Chat Relay for Jira's service-specific processing details for use with the Bonterms Data Protection Addendum v2.0, Attachment Version. Read the Bonterms DPA and its applicable modules together with this schedule.
This service schedule is part of a DPA only when a written agreement or Marketplace order between the customer and the Provider expressly incorporates it and the applicable Bonterms DPA terms. Publishing this page alone does not execute a DPA. The effective date is the effective date stated in the agreement or order that incorporates these terms.
Parties and service
| Item | Details |
|---|---|
| Provider / Processor | Individual Entrepreneur (FOP) Ivan Danyleiko, trading as Darkwood Apps. |
| Customer / Controller | The customer identified in the applicable order. The customer is the Controller unless it processes the data for another Controller, in which case it acts as a Processor and must pass through documented instructions. |
| Service | Chat Relay for Jira, an Atlassian Forge app that evaluates customer-configured Jira issue event rules and sends selected message fields to the customer's Google Chat destination. |
| Duration | For the term of the agreement that incorporates this schedule, followed by the retention and deletion periods below. |
Processing details
- Purpose: rule evaluation, filtering, scheduling, notification delivery and recovery, connection health, security, and customer support.
- Instructions: the customer's configuration and use of the app, including selected Jira projects or JQL scope, event types, card fields, schedules, destination, and retry actions. The Provider does not use customer content for advertising or an independent commercial purpose.
- Data subjects: customer administrators and Jira users; people whose information appears in customer-selected Jira issue fields; and users identified by optional author-exclusion rules.
- Personal data: Jira account IDs selected for author-exclusion rules; issue key, project, event/status and event metadata; administrator-selected issue fields such as summary, assignee, priority, issue type, labels, due date, Sprint, reporter, or status; connection and rule settings; delivery state; and the customer's Google Chat incoming-webhook credential. The customer controls which issue fields are sent. The app does not fetch comments, attachments, or issue descriptions.
- Special-category data: the Service is not designed to request or process special-category data. Customers must not select or send that data unless the parties separately agree in writing and the Service is suitable for it.
- Processing operations: event collection, rule evaluation, temporary queue storage in Forge KVS, retrieval for scheduled or administrator-initiated retries, disclosure to the customer-selected Google Chat destination, delivery outcome logging, and deletion or expiry.
Retention and deletion
- Pending events are eligible for retry for up to 24 hours from their queue timestamp. While a connection is active and has an active Marketplace license, the scheduled worker checks pending events every five minutes. An administrator can also select Retry queued after correcting the cause. Paused or inactive-license connections are not retried by that scheduled worker. After 24 hours, an event is expired and the app will not send it.
- An expired event is removed when the queue is next processed. Pending queue values use a two-day Forge KVS time-to-live and, if not removed earlier, are automatically deleted within 48 hours of their last write. Forge expiry and deletion are asynchronous. The two-day TTL is not an additional 48 hours after the retry window.
- Each connection keeps at most its latest 100 delivery-log entries. Logs contain issue keys and delivery outcomes, not titles or card fields.
- Idempotency markers expire after 35 days. Selected Jira account IDs remain while configured in an active rule and are removed when the administrator removes them, the connection is deleted, or Atlassian's Personal Data Reporting API returns
closedfor the account. - Removing a connection deletes its configuration, destination secret, pending queue, digest batch, and visible delivery history. The pre-uninstall handler attempts to delete app records. Atlassian may retain Forge-hosted data for up to 28 days after uninstall under its platform lifecycle; the app cannot access that soft-deleted copy. Google Chat messages already delivered are separate copies governed by the customer's Workspace retention settings.
Subprocessors and destination
Atlassian Forge provides the app runtime, events, queues, hosted KVS storage, and encrypted secret storage. See the Subprocessor List and Atlassian's official subprocessor list.
Google Chat is the destination selected and controlled by the customer. The Provider does not appoint Google as its subprocessor for this Service. Google receives and stores the configured message payload under the customer's Google Workspace terms and settings. The customer controls the destination space and its membership.
Security measures
- App data is hosted in installation-scoped Forge storage; destination webhook credentials use Forge encrypted secret storage and are masked in the app UI.
- Backend egress is limited to
chat.googleapis.comover HTTPS/TLS. The Provider does not operate an application server that receives Jira issue payloads. - Jira access is read-only. The app uses an allow-list of fields and checks current project scope and issue-security visibility before sending; it skips delivery when scope or unrestricted visibility cannot be confirmed.
- Jira administrators configure connections and can view the delivery journal. The customer is responsible for Jira and Google Chat account security and for controlling destination membership.
Incident notice and assistance
The Provider will notify the customer at support@darkwoodapps.com without undue delay and no later than 48 hours after becoming aware of a personal data breach affecting the Service, subject to the terms incorporated between the parties and applicable law. The Provider will use reasonable efforts to investigate and mitigate incidents within its control and assist with information reasonably available to it.
International transfers
Atlassian's Forge DPA, including its applicable Standard Contractual Clauses, governs Atlassian's processing for Forge. The customer controls the Google Chat destination under its Google Workspace agreement. The Provider does not represent that customer content is transferred to Ukraine.
If and only if the EU SCC module in the incorporated Bonterms DPA applies, the designated governing law and courts for that module are those of Ireland. If the module does not apply, this module-specific designation does not apply.
For service privacy practices, see the Privacy Policy. For questions about this schedule, contact support@darkwoodapps.com.