Last updated: .
Summary
Every Limbus Lab app runs entirely on Atlassian Forge. Limbus Lab operates no servers for them, and the apps use no third-party service in their runtime. The only subprocessor of each app is Atlassian. No other subprocessor receives customer data.
What Atlassian provides for each app
| App | What Atlassian provides |
|---|---|
| Hooq for Jira | Forge hosting, storage and logs, and web triggers between the customer’s own paired sites; Jira Cloud |
| SmartDash | Forge hosting, storage and logs; Forge LLM for AI help in the Advanced edition; Jira Cloud |
| PortalPilot | Forge hosting, storage and logs; Jira Cloud |
| Simple Workflow Automation | The Forge platform; Jira Cloud |
| MacroMint | Forge hosting, storage and logs; Forge LLM for the AI helper; Confluence Cloud |
Per Atlassian’s Forge documentation, Forge hosted storage is kept in the location of the host Atlassian product. How each app uses AI is in the AI Usage Policy.
Outbound (egress) addresses
SmartDash, PortalPilot, Simple Workflow Automation and MacroMint declare no outside address in their app manifest, so Forge does not let them call any host outside Atlassian. Hooq for Jira calls one kind of address: the Hooq web trigger of the partner Jira site that the administrators of both sites paired, a Forge-hosted endpoint on an Atlassian domain. No app makes a call to a non-Atlassian host. The details are on each app’s page.
Not used
No Limbus Lab app uses analytics, telemetry, advertising, an error-reporting service, an email service, an external database or a CDN of its own, and Limbus Lab does not sell or share customer data. No Limbus Lab server, database or file store is involved in any of them.