Privacy Policy - Hooq - Work Items in Jira

Hooq is a Forge-based application designed for Atlassian Cloud environments. It enables synchronization of Jira issues between two Jira Cloud instances or within the same instance.

This Privacy Policy explains how Hooq processes data when used within Jira Cloud.

This Privacy Policy applies to the Hooq application available through the Atlassian Marketplace and installed within Jira Cloud.

Hooq does not operate external servers for data processing and does not collect personal data outside the Atlassian Cloud environment.

Hooq processes only the data necessary to perform configured synchronization actions between Jira instances. This may include:

• Issue fields (such as summary, description, status, comments, custom fields)
• Project identifiers
• User display names (if included in synchronized fields)
• Metadata required for mapping and configuration

Hooq does not access or process data beyond the permissions granted during installation.

Hooq is built on Atlassian Forge and operates within Atlassian Cloud infrastructure. Data processing occurs within the Forge runtime and interacts with Jira Cloud using the permissions granted to the app.

Hooq does not:

• Route customer data through external servers
• Store Jira issue content outside Atlassian Cloud
• Transfer data to third-party analytics platforms

Synchronization occurs only between Jira instances explicitly connected by administrators.

Hooq uses cryptographic mechanisms to establish secure connections between Jira instances.

• Each installation generates a cryptographic key pair.
• A secure handshake establishes a shared secret between connected instances.
• Ongoing communication between instances is authenticated using signed requests.

Private keys and shared secrets are stored securely within Atlassian Forge storage and are not visible to administrators or the Hooq team.

Hooq stores limited configuration data necessary to enable synchronization, such as:

• Connector configuration
• Project mappings
• Synchronization settings
• Cryptographic materials required for secure communication

This information is stored within Atlassian Forge storage. Hooq does not maintain external databases for customer data.

Hooq does not sell, rent, or share customer data with third parties.

Data is transmitted only between Jira instances that administrators explicitly configure to connect. No central processing server is used for issue synchronization.

Hooq does not include:

• Behavioral analytics
• Usage tracking
• Telemetry collection
• Advertising technology

No personal data is collected for marketing purposes.

Hooq accesses Jira data strictly according to the permissions granted during installation. Administrators control the app's access via Jira's permission and app management controls.

The Hooq development team does not have access to customer Jira data through the app.

Hooq retains configuration data for as long as the app remains installed.

When the app is uninstalled:

• Forge-managed storage is removed in accordance with Atlassian's platform lifecycle.
• No external backups of Jira issue content are maintained by Hooq.

Hooq relies on Atlassian Forge security controls, including:

• Runtime isolation
• Permission-based access controls
• Secure storage APIs
• Platform-managed infrastructure security

In addition, Hooq implements:

• Cryptographic authentication between connected instances
• Timestamp validation to prevent replay attacks
• Signed request verification

Because Hooq operates within Atlassian Cloud infrastructure, data processing aligns with the data residency configuration of the customer's Jira Cloud environment. Hooq does not independently transfer data outside Atlassian infrastructure.

This Privacy Policy may be updated to reflect improvements or changes in functionality. The latest version will always be available within the app listing.

For privacy-related inquiries regarding Hooq - Work Items in Jira, please visit here.