Trust center
Data Retention and Deletion
Last updated:
What Hooq keeps, and for how long
| Data | Where | Retention |
|---|---|---|
| Configuration and operating state: pairings, project and field mappings, sync settings, links between paired work items, queue and idempotency records, pairing keys and secrets | Atlassian Forge hosted storage (the customer’s installation) | For as long as the app is installed or until the Hooq (pairing) is deleted |
| In-app error log | Forge hosted storage | Entries older than 3 days are discarded; at most 400 entries per scope; deleted with the Hooq |
| Forge platform logs | Atlassian Forge logging service | Atlassian’s retention (see Data Logging and Retention) |
| Work items, comments, attachments created by a sync | Jira (the customer’s sites) | Under the customer’s control, like any other Jira content. Hooq does not keep a copy |
Hooq keeps no backup or archive of Jira content outside Atlassian.
Data sent to another party (egress)
Synced content goes only to the partner Jira site chosen by the administrators. Hooq holds no copy of it beyond the links and idempotency records above. Data in the partner site is governed by that organization’s own Jira retention and deletion settings. Hooq has no subprocessors for customer content (see Subprocessors and Third-Party Integrations).
Deleting data
- Delete a Hooq (pairing). An administrator can delete a Hooq on the Overview page. Hooq then removes that Hooq’s configuration, drafts, error log, cached metadata, pairing record and link records from Forge storage. Work items already synced stay in both Jira sites; Hooq never deletes them when a pairing is removed. A deleted Hooq notifies the partner site, whose administrator may need to remove the partner side as well.
- Uninstall the app. Atlassian removes the app’s Forge storage under its platform lifecycle: data is first soft-deleted and kept for the rest of the retention period set by Atlassian’s Standard Data Retention and Disposal policy; Atlassian documents that hosted storage is retained for 28 days after uninstallation. After uninstall Hooq cannot read it. Hooq does not itself purge storage at uninstall; the platform does.
- Reinstalling. A new installation does not automatically see old data. Atlassian can re-link the previous data to a new installation if the app developer requests it within 21 days of uninstallation, with the customer’s consent.
- Data deletion requests. Contact the security contact in Security and Incident Response. Hooq will delete the customer’s Hooq configuration on request, within 30 days of a verified request. Data held by Atlassian follows Atlassian’s policy.
- Site deletion. When a Jira site is deleted, Atlassian’s site retention applies to the site and the app’s data; app data is deleted when the site is permanently removed.
Data residency
Forge hosted storage is data-residency enabled: it is held in the location of the host Atlassian product and moves with it when an administrator migrates the product. Forge aims to run functions in the same location. If two paired sites are in different locations, synced content moves between those locations by design.