Trust Center

Data Logging and Retention

Last updated: .

This page applies to Hooq for Jira, SmartDash, PortalPilot and MacroMint. Simple Workflow Automation’s logging is described on its own page.

Our position

We use logs to fix issues, and to fix issues earlier than they are reported. The apps send no usage analytics or telemetry to Limbus Lab or anyone else.

Where the logs live

The apps’ Forge functions write log lines to the Atlassian Forge logging service for the app, which Atlassian operates. The apps keep no separate log store. Hooq for Jira also keeps an in-app error log, described on its page.

Who reads the logs, and why

The developer reads an 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). Atlassian operates the Forge logging platform and restricts access to logs by organization permissions.

Retention

Log retention by location
LocationRetention
Forge platform logsHeld by Atlassian under the Forge platform’s own retention. The apps do not control or extend it.

Controls

  • The apps follow Atlassian’s Logging guidelines for Forge app developers: minimal data, no secrets, no user-generated content by design.

What each app logs