Privacy Policy
Last updated October 29, 2026
The short version: Inbound Webhook Router for Jira and ParentSync for Jira do not collect, store, or transmit any customer data or Jira issue details to Crewlabs or any third party. Everything runs on Atlassian's own infrastructure, inside your Atlassian Cloud instance.
Scope of this policy
This policy applies to all Crew Labs Atlassian apps: Inbound Webhook Router for Jira and ParentSync for Jira. The sections below that apply to every app come first; app-specific details follow under each app's own heading.
Data collection and transmission
Neither app collects, stores, or transmits any customer data or Jira issue details to Crewlabs or any third-party servers. No personal data is collected or sent anywhere by either app beyond what is stated for that app below. Neither app contains third-party tracking scripts, telemetry, or external analytics SDKs.
Subprocessors
Both apps run entirely on Atlassian Forge infrastructure. Crewlabs engages no additional cloud hosting providers or data subprocessors for either app.
Accounts and sign-in
Neither app has accounts or sign-in of its own - each operates entirely within your existing Jira Cloud site's authentication and permissions.
Inbound Webhook Router for Jira
Data collection and transmission
Inbound Webhook Router does not collect, store, or transmit any customer data, webhook payloads, or Jira issue details to Crewlabs or any third-party servers.
Data storage and encryption
All app configuration settings (destination project key, default issue type, summary prefix) and deduplication keys are stored strictly inside your own Atlassian Cloud Key-Value Store (KVS) — tenant-isolated to your instance.
Shared secret tokens are stored securely in Atlassian's encrypted storage and are never returned in plain text or rendered over network APIs after saving.
Subprocessors
Inbound Webhook Router runs entirely on Atlassian Forge infrastructure (*.atlassian-dev.net and *.atlassian.net). Crewlabs engages no additional cloud hosting providers or data subprocessors for Inbound Webhook Router.
Data retention and deletion
Uninstalling Inbound Webhook Router from your Jira Cloud instance automatically deletes all app configurations, stored secrets, and deduplication keys from Atlassian's Key-Value Store.
ParentSync for Jira
Data accessed
ParentSync reads issue keys, statuses, and story point values of subtasks and their parent issues, along with the parent/subtask relationships. It transitions parent issues and updates the parent's story points field. This data is processed inside Atlassian Forge and is not collected by or sent to Crewlabs or any third party.
Data storage
ParentSync stores only its own settings - the feature toggles and the story points field id - in Atlassian Forge storage under the key parentsync_config_v1, tenant-isolated to your instance.
External servers and credentials
ParentSync runs entirely inside Atlassian Forge. It uses no external servers, makes no third-party calls, and has no shared secret or credentials of any kind.
Data retention and deletion
Uninstalling ParentSync from your Jira Cloud instance automatically deletes its stored settings from Atlassian's Forge storage.
Changes to this policy
If this policy ever changes, the updated version will be posted at this same URL with a new "last updated" date.
Contact
Questions about this policy can be sent to support@crewlabs.io.