Trust center
Data Logging and Retention
Last updated:
Our position
We use logs to fix issues, and to fix issues earlier than they are reported. Hooq has no usage analytics or telemetry.
Where Hooq’s logs live
- Forge platform logs. Hooq’s Forge functions write log lines. These go to the Atlassian Forge logging service for the app, which Atlassian operates. Hooq keeps no separate log store.
- In-app error log. Warnings and errors are also stored in Forge hosted storage so that site administrators can see them on the Troubleshooting tab. Plain information lines are not stored. One internal diagnostic level is also stored today.
Who reads the logs, and why
The Hooq developer reads the app’s logs through the Atlassian Forge logging tools, only to troubleshoot, to fix issues that customers report, and to find and fix issues before they are reported.
Site administrators can switch the developer’s access to the logs of their site off (Atlassian Administration, Connected apps, the app’s Details tab, Logs access). Administrators can also download their own logs, and see the in-app error log on the Troubleshooting tab.
Atlassian operates the Forge logging platform and restricts access to logs by organization permissions.
What a log line may contain
Operational data only: error patterns and error text, work item keys and project keys, sync and Hooq identifiers, HTTP status codes, error classes, circuit-breaker state, attachment file names, and Atlassian site (cloud) identifiers. Error text returned by Jira or by the partner site for a failed call can echo part of a request or response.
Log lines do not contain work item summaries, descriptions, comment bodies, attachment contents, access tokens, API keys, shared secrets or private keys; Hooq does not deliberately log them.
Retention
| Location | Retention |
|---|---|
| In-app error log (Forge storage) | Stored entries are kept for 3 days and at most 400 entries per Hooq and for the app’s global log. Older entries are discarded the next time the log is written or read. Administrators can dismiss or clear errors on the Troubleshooting tab. Deleting a Hooq deletes its log. |
| Forge platform logs | Held by Atlassian under the Forge platform’s own retention. Hooq does not control or extend it. |
Controls
- Log writes are limited by design: information lines are never written to storage, and a log write failure never stops synchronization.
- Hooq follows Atlassian’s Logging guidelines for Forge app developers: minimal data, no secrets, no user-generated content by design.