Skip to main content
Limbus LabGet Hooq for Jira (opens the Atlassian Marketplace)

Trust center

Hooq Trust Center

Last updated:

Hooq, work item sync for Jira Cloud, runs entirely on Atlassian Forge. This page lists how Hooq handles security, privacy and availability.

Contact: hello@limbuslab.com.

Documents

Controls summary

  • Runs on Atlassian Forge, with no Hooq-operated servers or databases.
  • Data is stored only in Forge hosted storage, encrypted on disk by Atlassian; for data residency Hooq relies on the Forge platform, as described in Atlassian’s documentation.
  • Signed, time-limited, replay-protected messages between paired sites.
  • Least-privilege Jira scopes, listed in the Marketplace listing.
  • Logging practices and retention as documented in Data Logging and Retention.
  • A public status page.

Security contact and disclosure

Report suspected vulnerabilities to hello@limbuslab.com. We acknowledge a report within 3 business days. See Security and Incident Response for the disclosure policy and fix targets:

Fix targets by severity
SeverityFix or mitigation target
Critical7 days
High30 days
Medium90 days
LowBest effort

Subprocessors

Subprocessors
SubprocessorRole
AtlassianForge hosting, storage and logs; Jira Cloud. Hooq’s only subprocessor.

Details in Subprocessors and Third-Party Integrations.

Request more information

To request security documentation or to ask a question about this page, email hello@limbuslab.com from a company address with the subject “Hooq trust request”. We reply within 3 business days.

More

We update this page when our practices change.

Hooq overview · Trust center · Questions: hello@limbuslab.com