Last updated: . This policy replaces the separate privacy policies of Hooq for Jira (last updated 1 February 2026), SmartDash (13 November 2026), PortalPilot (12 November 2026), Simple Workflow Automation (12 November 2026) and MacroMint (13 November 2026), and the privacy part of the site’s Legal & Privacy page (24 October 2026).
Who we are
Hooq for Jira, SmartDash, PortalPilot, Simple Workflow Automation and MacroMint are made by Limbus Lab LLP. This policy explains how each app processes data when used within Jira Cloud, Jira Service Management Cloud or Confluence Cloud, and how this website handles what you send it. Contact for privacy: hello@limbuslab.com.
In short
Each app runs entirely on Atlassian Forge. None has servers of our own, and none sends data outside Atlassian. We can’t see your Jira data or your Confluence content.
What each app reads, keeps, and for how long differs by app, and is in the app’s own section below.
What we don’t do
We don’t sell data, share it with third parties, use advertising or tracking, or collect analytics in the apps.
Where data is held
Everything the apps keep is held by Atlassian, under Atlassian’s own terms and data residency settings. See Atlassian’s documentation for Forge. Who processes data for the apps is listed under Subprocessors.
Your rights and contact
Your site admin can stop all use of an app’s data by uninstalling the app. What else can be deleted, and by whom, is in each app’s section.
To ask what we hold about you, or to have it deleted, write to hello@limbuslab.com, or use the contact page.
Hooq for Jira
Hooq is a Forge-based application designed for Atlassian Cloud environments. It enables synchronization of Jira issues between two Jira Cloud instances or within the same instance. This section applies to the Hooq application available through the Atlassian Marketplace and installed within Jira Cloud.
More about Hooq for Jira: Hooq for Jira in the Trust Center · terms · help centre.
What data Hooq processes
Hooq processes only the data necessary to perform configured synchronization actions between Jira instances. This may include:
- Issue fields (such as summary, description, status, comments, custom fields)
- Project identifiers
- User display names (if included in synchronized fields)
- Metadata required for mapping and configuration
Hooq does not access or process data beyond the permissions granted during installation.
How data is processed
Hooq is built on Atlassian Forge and operates within Atlassian Cloud infrastructure. Data processing occurs within the Forge runtime and interacts with Jira Cloud using the permissions granted to the app. Hooq does not:
- Route customer data through external servers
- Store Jira issue content outside Atlassian Cloud
- Transfer data to third-party analytics platforms
Synchronization occurs only between Jira instances explicitly connected by administrators. Data is transmitted only between Jira instances that administrators explicitly configure to connect. No central processing server is used for issue synchronization.
Cryptographic security
Hooq uses cryptographic mechanisms to establish secure connections between Jira instances.
- Each installation generates a cryptographic key pair.
- A secure handshake establishes a shared secret between connected instances.
- Ongoing communication between instances is authenticated using signed requests.
Private keys and shared secrets are stored securely within Atlassian Forge storage and are not visible to administrators or the Hooq team.
Data storage
Hooq stores limited configuration data necessary to enable synchronization, such as:
- Connector configuration
- Project mappings
- Synchronization settings
- Cryptographic materials required for secure communication
This information is stored within Atlassian Forge storage. Hooq does not maintain external databases for customer data.
Analytics and tracking
Hooq does not include behavioral analytics, usage tracking, telemetry collection or advertising technology. No personal data is collected for marketing purposes.
Access to data
Hooq accesses Jira data strictly according to the permissions granted during installation. Administrators control the app’s access via Jira’s permission and app management controls. The Hooq development team does not have access to customer Jira data through the app.
Data retention
Hooq retains configuration data for as long as the app remains installed. When the app is uninstalled:
- Forge-managed storage is removed in accordance with Atlassian’s platform lifecycle.
- No external backups of Jira issue content are maintained by Hooq.
Security measures
Hooq relies on Atlassian Forge security controls, including runtime isolation, permission-based access controls, secure storage APIs and platform-managed infrastructure security. In addition, Hooq implements:
- Cryptographic authentication between connected instances
- Timestamp validation to prevent replay attacks
- Signed request verification
International data transfers
Because Hooq operates within Atlassian Cloud infrastructure, data processing aligns with the data residency configuration of the customer’s Jira Cloud environment. Hooq does not independently transfer data outside Atlassian infrastructure.
Changes
The latest version of this policy will always be available within the app listing.
SmartDash
SmartDash comes in two editions, Standard and Advanced. Advanced does everything Standard does and more, and this section says where they differ.
More about SmartDash: SmartDash in the Trust Center · terms · help centre.
What the app reads
SmartDash reads Jira when a widget or page is on screen, as the person looking at it. Jira’s own permissions decide what comes back. It reads only what is needed: the work items of a search and the fields shown. Time in Status also reads their status history; Calendar reads the SLA fields its owner chose; the sprint pages in Advanced read the sprint history of the work in that sprint.
One exception, Advanced only. A Jira admin or project admin can turn on “Share project data” for one SmartDash and one project. That SmartDash then reads that project with the app’s own access, so people it is shared with see that project’s numbers. It is off until an admin turns it on, and limited to the projects they approve.
SmartDash also reads two things with its own access: a project’s names (its kind, issue type names, whether it uses sprints, its SLA and story points field names), never its work items; and, once a week, whether the owners of SmartDashes still have active accounts.
What the app keeps
In both editions:
- With Jira: each widget’s settings, saved with the widget on its dashboard.
- In Atlassian’s Forge storage for this app: the list of dashboards that use SmartDash, with their ids, widget titles and search text (for site admins); migration records, including the Atlassian account id of the admin who ran one; dashboard designs people save (visible only to them); site settings; a person’s chosen style.
- In the person’s own browser: their last results, so a dashboard appears at once. This is work item data they could already see, kept for that person only and for at most 48 hours. Uninstalling the app can’t reach a browser, so these copies stay until the browser’s site data is cleared.
Advanced also keeps, in Forge storage:
- SmartDashes: each one’s title, its widgets’ searches and settings, its look, its owner’s Atlassian account id, who it is shared with, and when it was created, changed and opened, with the last 50 visitors’ account ids and times.
- Per person: favourites, recently opened SmartDashes, and their own layout of a shared SmartDash (removed after 90 days unopened). Their My view choices (role, projects, the sprint they picked) stay in their own browser.
- Per project: its key and name, its kind, the names of its issue types, whether it uses sprints, and the names of its SLA and story points fields. Names only, never work items.
SmartDash keeps people by their Atlassian account id only, never by name or email. Names are looked up from Jira, as the person viewing, each time they are shown.
SmartDash doesn’t store work item summaries, descriptions, comments or field values on Atlassian’s side. Data in Forge storage is removed when the app is uninstalled, on Atlassian’s schedule.
AI (Advanced only)
Advanced uses an AI model hosted by Atlassian (Forge LLM). It is used only when a person asks for it: to plan a dashboard from their words, or to change a widget or their My view page in words.
- What it is sent: the person’s words, and names from the site: project keys and kinds, issue type, field, priority, status and SLA names, and the title and type of the widget being changed. It is never sent work items or their field values.
- What it does: it only answers with text, which SmartDash checks against fixed lists before anything changes. It can’t change work items or anyone else’s dashboards.
- Where it runs: within Atlassian, under Atlassian’s terms for Forge. We don’t send it anywhere else and don’t train any model on your data.
- Control: a Jira admin can turn AI help off for the whole site. Use is limited per person and per site.
Rovo (Advanced only)
Rovo is Atlassian’s AI. When a person asks Rovo about SmartDash, SmartDash answers Rovo as that person with dashboard titles, widget titles, counts and chart labels they can already see. It never hands Rovo the rows of work items. What Rovo does with its answer is covered by Atlassian’s terms.
Deleting data
For anything held in Forge storage, your site admin can clear it by uninstalling the app. In Advanced, a SmartDash’s owner can delete it.
SmartDash uses Atlassian’s Personal Data Reporting API: each week it reports the account ids it holds, and when Atlassian reports an account as closed, SmartDash erases that person’s own settings, favourites, layouts and saved designs.
PortalPilot
PortalPilot is for Jira Service Management. It reads Jira as the signed-in person, keeps only its settings and saved filters, and sends nothing outside Atlassian.
More about PortalPilot: PortalPilot in the Trust Center · terms · help centre.
Because the app stores Atlassian account IDs, it also reports them to Atlassian every week, as Atlassian asks of Forge apps. When Atlassian says an account is closed, the app erases what it holds for that account.
What the app reads
- Portal requests and request types the signed-in person may see.
- Organizations and groups, to apply filters and visibility settings.
- The list of Jira fields, for Fields configuration (admins only).
- User names, for pickers and the Reporter column.
- Whether the person is a Jira admin, to open the admin pages.
Each of these is read from Jira as the signed-in person, so Jira’s own permissions apply.
What the app keeps
In Atlassian’s Forge storage for this app:
- Settings: visibility, export, banner and header link. Visibility lists hold account IDs and organization and group names.
- User scopes, field settings and filter permissions. These hold account IDs and organization and group names.
- Saved filters: name and criteria, kept under the owner’s account ID. Shared and global filters also hold the owner’s display name. Favourites and each person’s default view, kept in one private record per account ID.
It does not keep request content. Lists are read from Jira each time.
In the person’s own browser, the tab keeps the last screen they had open (never search text or custom field values) for at most 12 hours, cleared when the tab is closed, and the browser remembers their choice of compact or comfortable rows.
Why account IDs are stored
An account ID is how the app knows who may open PortalPilot, who belongs to a user scope, who may use a shared filter, and whose saved filters, favourites and default view are whose. Without it, none of these settings could work. Apart from the reporting below, the app uses account IDs for nothing else.
Reporting accounts to Atlassian
PortalPilot uses Atlassian’s personal data reporting API (the report:personal-data permission). A scheduled job runs once a day and sends the account IDs the app has stored, each with a time, to that API. IDs are sent in batches of 90, and each account is reported at most once every 7 days. A large site may take more than one daily run to finish a round, and the next run carries on where the last one stopped.
The job runs as the app, with no signed-in person, and uses only the app’s own storage and that Atlassian API. It sends nothing to us or to anyone else. Atlassian answers which accounts are closed and which have been updated.
When an account is closed or updated
For each account Atlassian reports as closed, the app:
- deletes that person’s private record: their private saved filters, favourites and default view;
- removes the account from every user list in Visibility, user scopes and filter permissions;
- keeps their shared and global filters for the people who use them, but anonymises them: the account ID and the stored time are removed and the owner shows as “Former user”. A Jira admin can delete them in Filters management.
If removing a closed account would leave the list of people allowed to open PortalPilot empty, the app puts an empty “Former users (no members)” scope in its place, so the list stays limited instead of opening to everyone.
For each account Atlassian reports as updated, the app clears the display name it stored on that person’s shared and global filters. The name is then looked up from Jira when it is shown.
The app writes only counts and codes to its logs, never account IDs or names.
How long data is kept
Settings, scopes and field settings stay while the app is installed or until an admin changes them. A saved filter stays until its owner or a Jira admin deletes it. Favourites and a default view stay until the person changes them. Everything held for an account is erased once Atlassian reports the account closed. The browser items above last as described there.
Where data is held, and uninstalling
In Atlassian Forge storage on your Jira site. When the app is uninstalled, it can no longer read that storage. Atlassian removes it under its own schedule, as PortalPilot retention and deletion explains. The app does not delete it itself.
Deleting data
A person can delete their own saved filters in the app, and a Jira admin can delete any saved filter in Filters management. Because the data is in your organization’s Forge storage, we may need your site admin to take part in a request to delete stored settings and filters.
Simple Workflow Automation
This section explains how Simple Workflow Automation processes data when used within Jira Cloud.
More about Simple Workflow Automation: Simple Workflow Automation in the Trust Center · terms · help centre.
What the app reads
The app reads from Jira only what the rules a Jira administrator sets up need: the work items a rule checks or acts on, their fields, comments, links and history, the people, groups and roles a rule names, and your workflows, for the rule list, Health and copy.
A rule reads Jira as the person it is set to run as: by default the person who made the move, or else the app or a named person. Conditions and validators are run by Jira itself.
What the app keeps
- Rule settings, saved by Jira in your workflows.
- In Atlassian’s Forge storage for this app: the rule list from the last scan, with each rule’s on or off state; shared actions, event actions and scheduled actions; the dry-run and emergency-stop switches.
- Run history: for each run, the time, the rule id, the work item key, the workflow and transition, the result, a reason, the duration and the kind of run-as (app, current or specific). Not names, email subjects or email bodies.
- Rule change history: who made a change (their Atlassian account id), when, what changed and where.
- The Atlassian account id of whoever last changed or switched a rule, shared action, event action or scheduled action, stored with that item.
- Email addresses an admin types as recipients, stored as part of the rule, shared action or scheduled action they were typed into.
- Short-lived records the app uses to work: status changes seen, for the missed-run check, and markers that stop a retried step from repeating a change.
How long
- Run history rows expire 90 days after each run.
- Rule change history rows expire after 90 days.
- Status changes seen expire after 72 hours; repeat markers after at most 7 days.
- Rule lists, actions and switches are kept until they are replaced or deleted.
- Account ids stored with a rule, shared action, event action or scheduled action, and email addresses typed into one, are kept until that item is deleted.
- Expired rows are removed by the Forge platform, usually within 48 hours.
Email addresses
Email is sent through Jira’s own notification service.
An administrator can type plain email addresses into an email rule, shared action or scheduled action. They are stored as part of that rule, shared action or scheduled action, until the administrator deletes it: for a rule in the workflow, which Jira keeps, and for a shared or scheduled action in the app’s Forge storage. Run history never stores email addresses, and the app’s logs hold no names, account ids, email addresses or message text. On sites with Jira Service Management, an address with no matching person is added to the site, through Jira’s API, as a service project customer, so it can be mailed.
People who hide their email address from apps are not matched by address. They are skipped, and run history records only that a recipient was skipped.
Where data is held
All data the app keeps is held by Atlassian, in Forge storage and in Jira, under Atlassian’s own security and data-residency arrangements for Forge apps. Atlassian is the only subprocessor. We don’t run servers, databases or analytics for the app.
Deleting data
Your Jira site’s administrators control the data: they can delete rules and actions, and uninstall the app. The app follows Atlassian’s personal data reporting: when an Atlassian account is closed, the account ids the app stores for it are erased. For any request about personal data the app processes, include your Jira site address.
MacroMint
This section explains how MacroMint processes data when used within Confluence Cloud. MacroMint keeps people by their Atlassian account ID only, never by name or email.
More about MacroMint: MacroMint in the Trust Center · terms · help centre.
What the app reads
MacroMint reads Confluence only as the person using it, so Confluence’s own permissions decide what comes back. It never reads Confluence with its own access.
- The signed-in person’s own user record, to check whether they are a Confluence admin. Only the list of what they may do is used.
- The display names of the admins in the change history, looked up when an admin opens it and never stored.
- For the usage report: the titles, spaces and content of pages that admin can already see, found through Confluence search, to count components.
- For the Rovo agent: the page the person has open.
What the app keeps
In the Confluence page:
- Each component’s settings, including the text the author typed, and a copy of the site brand at the time it was saved. This is page content, held by Confluence like any macro’s settings.
- When the Rovo agent saves a change, Confluence records a page version under the person’s own name, with a note that starts with “MacroMint agent:”.
In Atlassian’s Forge storage for this app:
- The site brand (colour, corner style, spacing), the custom colour and presets-only switches, and approved presets with their names.
- A change history of the last 200 brand and preset changes: the Atlassian account ID of the admin who made each change, the time, the action and the old and new style values.
- AI usage counters: a count per person per day, kept under their account ID for about 2 days, and a count per site per month.
- Rovo preview records: a one-way hash of the person’s account ID, the page ID and version and a hash of the inputs, kept for 10 minutes so that a save matches what was previewed.
In the person’s own browser:
- A copy of the site brand and preset styles, refreshed about once a day, so pages follow a brand change. It holds no personal data.
MacroMint doesn’t store page text, names, email addresses, pictures, locations or job titles. Data in Forge storage is removed when the app is uninstalled, on Atlassian’s schedule. Its logs hold counts and error codes only, never page text or personal data.
AI
MacroMint has an AI helper that uses a model hosted by Atlassian (Forge LLM). It is used only when a person asks for it: to build a component from a sentence, or to change the one they are editing.
- What it is sent: the sentence the person typed, the component’s own settings without links or colours, and the text in that component’s body only if the person ticks a box to share it. Never the rest of the page or other pages.
- What it does: it only fills in the component’s settings, which MacroMint checks against the same rules as the manual editor. The result is a draft the person uses or discards.
- Where it runs: within Atlassian, under Atlassian’s terms for Forge. We don’t send it anywhere else, don’t store what is sent, and don’t train any model on your data.
- Control: use is limited per person and per site. The AI helper can be switched off; in this version that switch is held by Limbus Lab.
Rovo
Rovo is Atlassian’s AI. MacroMint adds an agent to it that works as the person asking, with their own permissions. It reads the page they have open, and saves a change only after showing a preview and after the person agrees and confirms. For Confluence admins it can list where components and custom colours are used. What Rovo does with a conversation is covered by Atlassian’s terms.
Deleting data
For anything held in Forge storage, your site admin can clear it by uninstalling the app. AI usage counters and Rovo preview records expire on their own, as described above.
The change history keeps the account IDs of the admins who made the last 200 brand and preset changes, with no time limit, until newer changes replace them or the app is uninstalled. MacroMint does not use Atlassian’s Personal Data Reporting API.
Hooq for ServiceNow
Hooq for ServiceNow is in preview and not available; its privacy information comes with the release.
This website
When you send the contact form, we receive your name, your email address and your message. They create a request in our support desk (Jira Service Management, run by Atlassian) so that we can answer you.
Show interest. Sending this creates a request in our support desk (Jira Service Management, run by Atlassian) with your email address as the customer and the edition you chose. We use it only to tell you once when this edition is live. To have it deleted, write to hello@limbuslab.com.
To ask what we hold about you, or to have it deleted, write to hello@limbuslab.com.
Cookies
The pages of this site set no cookies and use no analytics or trackers. The Hooq for Jira page offers a demo video from YouTube: nothing is loaded from YouTube until you press play, and then the player comes from YouTube's privacy-enhanced mode (youtube-nocookie.com), which may store its own data in your browser while the video plays.
The Contact and Show interest forms can use Cloudflare Turnstile, a check against automated spam: while one of these forms is on screen, your browser loads a script from challenges.cloudflare.com and Cloudflare checks the visit. In our test it set no cookies and stored nothing in the browser.
For anything legal or privacy-related: hello@limbuslab.com.
Changes to this policy
This policy may be updated to reflect improvements or changes in functionality, or when an app changes what it reads or keeps. We will post changes here and change the date at the top.