Last updated: . These terms replace the separate terms of service of PortalPilot (effective 12 November 2026), Simple Workflow Automation (effective 12 November 2026) and MacroMint (effective 13 November 2026).
Who these terms are between
These terms of service (the “Terms”) are an agreement between Limbus Lab LLP (“Limbus Lab”, “we”, “us”) and the organisation that installs or uses Hooq for Jira, SmartDash, PortalPilot, Simple Workflow Automation or MacroMint (“the app”) on its Atlassian site (“you”). They are the end-user agreement for each of these apps. The shared clauses below apply to every one of them; each app’s own clauses are in its section at the end.
The person who installs the app accepts these Terms on behalf of that organisation, and confirms they are allowed to do so. If you do not agree to these Terms, do not install or use the app.
Your use of the Atlassian Marketplace, Jira, Confluence and Atlassian Forge is governed by your own agreements with Atlassian. Atlassian is not a party to these Terms. If you and Limbus Lab have signed a separate written agreement about the app, that agreement prevails where it differs from these Terms.
Licence
While your site has an active subscription to the app bought through the Atlassian Marketplace, including any free trial the Marketplace offers, we grant you a non-exclusive, non-transferable, non-sublicensable licence to use it on that site, for your own business purposes. What the licence lets your admins and people do is in each app’s section.
The app is licensed, not sold. Limbus Lab keeps all rights in the app, its code, its documentation and its name that these Terms do not expressly grant to you.
Restrictions
You must not, and must not let anyone else:
- copy, modify or make derivative works of the app, except as the law expressly allows;
- reverse engineer, decompile or disassemble it, except to the extent the law allows despite this restriction;
- sell, resell, rent, lease, sublicense or otherwise make it available to anyone other than the users of your site;
- get around, disable or interfere with its access controls or security;
- use it in breach of the law, of anyone’s rights, or of your agreements with Atlassian;
- use it, or information about how it works, to build a competing product.
Your data
The app runs on Atlassian Forge, inside your Atlassian site. It sends no data to servers outside Atlassian. Limbus Lab runs no servers for it. What each app reads and keeps is in its section below.
You keep all rights in your data. We do not sell or share it.
How each app handles personal data is described in the privacy policy, and its security, data handling and subprocessors in the Trust Center.
Support
For help, use the contact page. Each app’s help centre covers setup and use.
We provide support on a best-effort basis. No service level, response time or resolution time applies unless we agree one with you in writing. How we handle security reports is described in Vulnerability Reporting.
We may release updates to the app from time to time. Updates are delivered through Atlassian Forge and are covered by these Terms.
Fees and billing
Each of these apps is a paid app. Subscriptions are bought, billed, renewed and cancelled through the Atlassian Marketplace. Prices, invoices, taxes, renewals and refunds are handled by Atlassian under Atlassian’s Marketplace terms. Limbus Lab does not bill you directly and does not receive your payment details.
We may change the price of the app. Any change applies through the Atlassian Marketplace, under Atlassian’s terms.
Term and termination
These Terms apply from when you install or first use the app until it is uninstalled from your site. Your licence to use it lasts while your site’s trial or subscription is active. What happens when a subscription lapses, and when the app is uninstalled, is in each app’s section.
We may suspend or end your licence if you materially breach these Terms and do not fix the breach within 30 days of our notice, or straight away where the law or Atlassian requires it. We may stop offering the app; if we do, we will give notice in advance where we reasonably can.
Warranties disclaimer
To the fullest extent the law allows, the app is provided “as is” and “as available”. Limbus Lab gives no warranties, express or implied, including any warranty of merchantability, fitness for a particular purpose, title or non-infringement, and does not warrant that the app will be uninterrupted, error-free or free of harmful components.
The app depends on Atlassian Forge and other Atlassian services, which Limbus Lab does not control. We are not responsible for their availability or behaviour.
Some jurisdictions do not allow certain warranties to be excluded. In those jurisdictions, the exclusions above apply only as far as the law allows.
Limitation of liability
To the fullest extent the law allows, Limbus Lab is not liable for any indirect, incidental, special, consequential or punitive damages, or for any loss of profits, revenue, business, goodwill or data, arising out of or in connection with the app or these Terms, even if we were told such loss was possible.
To the fullest extent the law allows, Limbus Lab’s total liability arising out of or in connection with the app or these Terms is limited to the amount you paid for the app through the Atlassian Marketplace in the 12 months before the event giving rise to the claim.
Nothing in these Terms limits or excludes liability that cannot be limited or excluded by law.
Changes to these terms
We may update these Terms, for example when the app or the way it is sold changes. We will post the new Terms on this page and change the date at the top. If a change is material, we will say so on this page before it takes effect.
If you keep using the app after the new Terms take effect, the new Terms apply. If you do not agree to them, stop using the app and uninstall it.
Governing law
These Terms, and any dispute arising out of or in connection with them, are governed by the laws of India. The courts of India have exclusive jurisdiction.
General
- These Terms, together with the privacy policy, are the whole agreement between you and Limbus Lab about the app, unless we have signed a separate written agreement with you.
- If any part of these Terms is found unenforceable, the rest stays in effect.
- If we do not enforce a right under these Terms, that is not a waiver of it.
- You may not transfer these Terms without our written consent. We may transfer them as part of a merger, acquisition or sale of all or part of our business.
- Neither party is liable for a delay or failure caused by events beyond its reasonable control.
Trademarks
The Limbus Lab name, mark, and product names are trademarks of Limbus Lab LLP.
Hooq for Jira
The Terms above apply to Hooq for Jira in full; it has no clauses of its own. How Hooq for Jira handles data is in its privacy section and Trust Center page.
SmartDash
The Terms above apply to SmartDash in full; it has no clauses of its own. How SmartDash handles data is in its privacy section and Trust Center page.
PortalPilot
These clauses apply to PortalPilot in addition to the shared terms above. Its privacy section: PortalPilot privacy. Its security, data handling and subprocessors: PortalPilot in the Trust Center. Setup and use: help centre.
Licence and trial
These Terms are the end user licence agreement for PortalPilot. A person who starts a trial also accepts them on behalf of their organisation.
The licence lets your Jira admins configure the app, and lets the people your admins allow, such as portal customers and agents, use it on that site. Its scope, such as the user tier, is the one your subscription has on the Atlassian Marketplace.
A free trial is available through the Atlassian Marketplace. During the trial PortalPilot works as it does with a paid subscription. To keep using it after the trial, buy a subscription through the Atlassian Marketplace.
You must also not get around, disable or interfere with PortalPilot’s licensing checks.
Your data
It reads Jira as the signed-in person, so Jira’s permissions decide what each person sees. It keeps only its settings, user scopes, field settings, filter permissions and saved filters, in the app’s own Forge storage. It lists no outside address. Limbus Lab cannot see your Jira data.
As Atlassian requires, the app reports the account IDs it stores to Atlassian’s personal data reporting API, each account at most once every 7 days, and erases what it stores for accounts Atlassian reports as closed.
PortalPilot cannot create, edit or delete requests. Lists, counts, charts and exports cover up to 1,000 matching requests, most recently active first. It works with Jira Service Management Cloud only.
If these Terms and the privacy policy differ about personal data, the privacy policy applies.
You are responsible for the content of your Jira site, for who your admins allow to use PortalPilot, and for the settings they choose.
When a subscription ends, and uninstalling
If the trial or subscription ends, is cancelled or is not renewed while the app is still installed:
- Customers see “PortalPilot isn’t available on this site right now.” in place of the banner and the full-screen view, and the app refuses every call from the portal on the server.
- Jira admins can still open the PortalPilot admin pages and change settings, with a warning that the subscription is inactive.
- Settings, user scopes, field settings, filter permissions and saved filters stay in the app’s Forge storage. Nothing is deleted because the subscription has lapsed, and everything returns as it was when the subscription is active again.
Uninstalling PortalPilot ends these Terms and removes the app’s access to your site. Atlassian deletes the app’s Forge storage, with its settings and saved filters, under the Forge platform’s lifecycle and on Atlassian’s schedule.
The Restrictions, Your data, Warranties disclaimer, Limitation of liability, Governing law and General sections continue to apply after these Terms end.
Warranties
PortalPilot depends on Atlassian Forge, Jira and other Atlassian services, which Limbus Lab does not control.
Simple Workflow Automation
These clauses apply to Simple Workflow Automation in addition to the shared terms above. Its privacy section: Simple Workflow Automation privacy. Its security, data handling and subprocessors: Simple Workflow Automation in the Trust Center. Setup and use: help centre.
Licence
The licence lets your Jira administrators set up and manage rules, actions and schedules, and lets the people on your site use the work item screens the app adds, within the permissions Jira gives them.
Your data
It reads and changes Jira only as the rules your administrators set up tell it to, as the person each rule is set to run as. It keeps its rule settings, run history, rule change history and shared, event and scheduled actions in the app’s own Forge storage and in your workflows. It declares no outside address. Limbus Lab cannot see your Jira data.
Email addresses an administrator types as recipients, and the Atlassian account id of whoever last changed or switched a rule, shared action, event action or scheduled action, are stored with that item until it is deleted. The app follows Atlassian’s personal data reporting: when an Atlassian account is closed, the account ids the app stores for it are erased.
You are responsible for the content of your Jira site, for the rules your administrators set up and the actions they allow, and for checking that a rule does what you intend before you switch it on.
Fees
Prices, invoices, taxes, renewals, payment and refunds are handled by Atlassian under Atlassian’s Marketplace terms and refund policy. Any free trial is offered through the Atlassian Marketplace.
When a subscription ends, and uninstalling
If the subscription ends, is cancelled or is not renewed while the app is still installed:
- Workflow actions stop running: post-functions, event actions, scheduled actions and shared actions do nothing.
- Conditions and validators let transitions through, so the subscription ending never blocks your team from moving work forward.
- Your rule settings stay in your workflows and in the app’s Forge storage. Nothing is deleted because the subscription has lapsed, and the rules run again as they were once the subscription is active.
Uninstalling the app ends these Terms and removes the app’s access to your site. Atlassian deletes the app’s Forge storage, with its rules lists, actions, run history and rule change history, under the Forge platform’s lifecycle and on Atlassian’s schedule. Rule settings saved in your workflows stay in Jira; once the app is gone they no longer run.
The Restrictions, Your data, Fees and billing, Warranties disclaimer, Limitation of liability, Governing law and General sections continue to apply after these Terms end.
Warranties
The app depends on Atlassian Forge, Jira and other Atlassian services. Rules change your Jira data as you set them up to; we are not responsible for the outcome of a rule you configured.
MacroMint
These clauses apply to MacroMint in addition to the shared terms above. Its privacy section: MacroMint privacy. Its security, data handling and subprocessors: MacroMint in the Trust Center. Setup and use: help centre.
Licence
The licence lets your Confluence administrators set the site brand, presets and settings, and lets the people on your site add, edit and view MacroMint components, within the permissions Confluence gives them.
Your data
It reads and changes Confluence only as the person using it, so Confluence’s permissions apply. Component text is saved by Confluence in your pages. The app keeps the site brand, presets, a change history of brand and preset edits, and short-lived usage counters in its own Forge storage. It declares no outside address. Limbus Lab cannot see your Confluence content.
The app stores people by their Atlassian account ID only, never by name or email: the account ID of the admin who made each of the last 200 brand and preset changes, AI usage counters kept for about two days, and a one-way hash of the account ID in Rovo preview records kept for 10 minutes.
You are responsible for the content of your Confluence site, for the components your people add, for the brand and settings your administrators choose, and for checking a change the AI helper or the Rovo agent proposes before you use or confirm it.
Fees
Prices, invoices, taxes, renewals, payment and refunds are handled by Atlassian under Atlassian’s Marketplace terms and refund policy. Any free trial is offered through the Atlassian Marketplace.
When a subscription ends, and uninstalling
If the subscription ends, is cancelled or is not renewed while the app is still installed:
- Existing components keep showing on your pages and in PDF export, and keep following the site brand.
- Creating or changing components stops. The component editors, the MacroMint AI start screen and the admin page show “MacroMint’s licence on this site is not active” in place of their forms, and the Rovo agent says the same.
- The site brand, presets and change history stay in the app’s Forge storage, and component settings stay in your pages. Nothing is deleted because the subscription has lapsed, and everything works again as it was once the subscription is active.
Uninstalling the app ends these Terms and removes the app’s access to your site. Atlassian deletes the app’s Forge storage, with the site brand, presets and change history, under the Forge platform’s lifecycle and on Atlassian’s schedule. Component settings saved in your pages stay in Confluence; once the app is gone, Confluence no longer draws them as MacroMint components.
The Restrictions, Your data, Fees and billing, Warranties disclaimer, Limitation of liability, Governing law and General sections continue to apply after these Terms end.
Warranties
The app depends on Atlassian Forge, Confluence, Rovo and other Atlassian services, which Limbus Lab does not control. Drafts from the AI helper and changes proposed by the Rovo agent are suggestions; we are not responsible for content you choose to use or confirm.