Privacy Policy — Chat Relay for Jira

Draft — pending owner approval. The legal identity and remaining legal placeholders must be completed before these terms become effective.

• Provider: ФОП {{LEGAL_NAME}}, trading as Darkwood Apps
• Product: Chat Relay for Jira
• Website: darkwoodapps.com
• Privacy and support contact: support@darkwoodapps.com
• Effective date: {{EFFECTIVE_DATE}}

1. Scope

This Policy explains how {{LEGAL_NAME}} handles information when a customer installs or uses Chat Relay for Jira. The app runs on Atlassian Forge and sends selected Jira issue updates to Google Chat using incoming webhooks configured by the customer's Jira administrator. The customer’s use of Jira, Google Workspace, and Atlassian Marketplace is also subject to those providers’ terms and privacy notices.

2. Information processed by the app

The app processes information needed to evaluate saved rules, construct message cards, and deliver them:

• Jira issue key, project, event type, status and changelog data used for rule matching;
• selected card fields, which may include summary, status, assignee, priority, issue type, labels, due date, sprint, and reporter;
• connection name, project/JQL scope, selected event types and fields, and delivery schedule;
• delivery timestamps, outcomes, HTTP status, short error reasons, health state, retry queue state, and aggregate usage counters;
• the Google Chat incoming webhook URL selected by the administrator.

The app does not fetch issue comments or worklogs. It excludes issues with a security level; if the app cannot confirm that an issue is unrestricted, it skips delivery. The administrator chooses which supported fields are sent to the selected Chat space.

3. Webhook and destination

The webhook URL is a secret credential that allows posting to the configured Chat space. The app stores it using Forge encrypted secret storage and masks it in the settings page. It sends message cards containing the configured issue fields to chat.googleapis.com. The customer controls the destination space and its membership. Anyone who can read that space may see messages delivered there.

The app does not send issue data to a separate {{LEGAL_NAME}}-operated application server. Atlassian Forge provides the app runtime and storage; Google Chat receives the message content selected by the administrator. Their processing and data locations are subject to their own terms and configuration.

4. Purposes and legal basis

The app uses the information above to provide routing, scheduling, message delivery, retries, connection health, support troubleshooting, and service security. The customer is responsible for choosing an appropriate Jira scope and Chat audience, providing required notices, and establishing a lawful basis for sharing information with that audience. {{LEGAL_NAME}} must confirm and complete the applicable legal bases and regional disclosures before publication.

5. Retention

Current app behavior is:

• queued or failed events are retained for up to 24 hours;
• each connection retains its most recent 100 delivery-log entries;
• idempotency markers expire after 35 days; platform deletion of expired values may be asynchronous;
• delivery counters cover a rolling 31-day window; installation-level first-use milestones remain with app usage metadata;
• removing a connection deletes its webhook secret, settings, pending queue, digest batch, and visible delivery log; separate idempotency markers expire under their 35-day lifetime;
• uninstalling the app triggers the app's Forge uninstall cleanup, subject to platform behavior.

The Owner must verify the current retention implementation before release and update this section if it changes.

6. Access and security

Jira administrators with access to the app's administration page can configure connections and rules. Forge scopes are limited to Jira work data, the optional Jira Software Sprint field, and app storage. The app does not sell information or use it for advertising. Webhook secrets are stored through Forge secret storage. Administrators should protect their Atlassian and Google Workspace accounts, limit access to the destination space, and rotate a webhook if it is exposed.

No internet-facing vendor backend is used by the app. Runtime processing, storage, and transfer are provided by Atlassian Forge and Google Chat; consult their security and data-residency documentation for details about those services.

7. International transfers

Atlassian and Google may process information in locations determined by the customer’s service configuration and their applicable terms. {{LEGAL_NAME}} must confirm the transfer disclosures and any required safeguards for the provider’s location and intended customer regions before publication.

8. Data subject and customer requests

Jira administrators can change or remove a connection, pause deliveries, or uninstall the app. For privacy questions, access/deletion requests, or concerns about the provider’s processing, contact support@darkwoodapps.com. The customer remains responsible for its Jira content and Chat messages and may also need to contact Atlassian or Google.

9. Children and sale of data

The app is a business product and is not designed for children. {{LEGAL_NAME}} does not sell personal information or use it for targeted advertising.

10. Changes and contact

We will update this Policy when processing changes and publish the revised effective date. Contact {{LEGAL_NAME}} at support@darkwoodapps.com for privacy questions.