Before an app goes into a Jira or Confluence site, a security review asks the same three questions. What does the app store? Where is it stored? Does anything leave Atlassian? This post answers them for each of our apps, with a link to the page where each answer is written down in full.
The short answer#
All five apps are built on Atlassian Forge. What they keep sits in Atlassian's Forge storage for that app, or in Jira or Confluence itself. Limbus Lab runs no server, database or file store that your work passes through.
Hooq for Jira#
Hooq keeps work items in sync between two Jira Cloud sites, or two projects in one site.
- Synced work items, comments and attachments live in your Jira sites, like any other Jira content. Hooq does not keep a copy of them.
- Hooq stores its configuration, drafts, cached metadata, pairing records and link records in Forge storage.
- Its error log is kept for 3 days and at most 400 entries per Hooq.
- Between two sites, the Hooq on one site sends a signed request straight to the Hooq on the other, over Atlassian's platform. There is no Hooq server in the middle.
- Deleting a Hooq removes its configuration and records from Forge storage. Work items already synced stay in both sites.
Full details: Hooq data retention and deletion.
SmartDash for Jira#
SmartDash adds charts, lists, Time in Status, a calendar and filters to Jira dashboards.
- Jira data is read live, as the person looking, so each person sees only what Jira lets them see. SmartDash does not store issue summaries, descriptions, comments or field values.
- Widget settings are saved by Jira with the widget. Dashboard setups, site settings and project names are kept in Forge storage and removed when the app is uninstalled.
- People are stored by Atlassian account id only. When Atlassian reports an account as closed, SmartDash deletes that person's settings.
- The viewer's browser keeps their own last results for up to 2 days.
- Nothing leaves Atlassian.
Full details: SmartDash data and privacy.
PortalPilot for Jira Service Management#
PortalPilot adds a full-screen request list with filters and export to the customer portal.
- It keeps its settings, saved filters, favourites and each person's default view. Requests are read from Jira each time and never stored by the app.
- All of it is in Forge storage for that site. The app declares no outside address and sends no analytics.
- Its logs hold the function name, outcome and duration, with no request content, names or emails.
- For a closed account, private filters, favourites and the default view are deleted, and shared filters show "Former user".
Full details: PortalPilot data retention and deletion.
Simple Workflow Automation for Jira#
Simple Workflow Automation adds workflow conditions, validators, post-functions and scheduled actions.
- Rule settings are saved in the workflow by Jira. Everything else is in Forge storage for the app.
- Run history keeps ids, work item keys, results, reasons and durations for 90 days, not names or email content. Rule change history is also kept for 90 days.
- Work item content is read when a rule runs and is not copied into app storage.
- Email goes through Jira's own notification service, so mail leaves from your Jira site.
- When an Atlassian account closes, the account ids the app holds for it are erased.
Full details: Simple Workflow Automation data and retention.
MacroMint for Confluence#
MacroMint adds branded components (Callout, Steps, Cards, Button, KPI, Status) to Confluence pages, all following one site brand.
- Component settings and text live in the Confluence page itself, like any macro.
- The site brand and presets are kept in Forge storage until an admin changes or deletes them.
- People are stored by account id only, never names or emails. The change history keeps the last 200 changes.
- Every call to Confluence is made as the person using it. The app has no servers of its own and no outside address.
- The optional AI helper uses an Atlassian-hosted model and is sent only the author's request, the component's settings and, if the author shares it, its text.
- Logs hold counts and error codes only, with no page text.
Full details: MacroMint data and privacy.
What this means for your review#
- Your Jira and Confluence content stays in your Atlassian sites.
- What each app keeps is small, named, and listed on its Trust Center pages.
- According to Atlassian's Forge documentation, Forge hosted storage is held in the location of the host Atlassian product, so app data follows your data residency choice.
Every app's help centre and Trust Center are linked from Documentation.



