Portal Sub-tasks — Privacy Policy
Effective date: 11/11/2026 Last updated: 11/11/2026
This privacy policy describes how Portal Sub-tasks ("we", "us", "the app") handles your data. Portal Sub-tasks is an Atlassian Marketplace app distributed via the Atlassian Forge platform. By installing Portal Sub-tasks, you agree to this policy.
Summary in plain English
- All data stays inside Atlassian's infrastructure. Portal Sub-tasks performs all analysis inside Atlassian's Forge runtime. No End-User Data is transmitted to any third party or outside Atlassian's infrastructure.
- We don't operate any servers. Portal Sub-tasks runs on Atlassian Forge — Atlassian hosts every function call and storage write.
- All stored data is encrypted at rest in Forge's Key Value Store, tied to your Atlassian Cloud site. It is never logged or returned to any third party; all processing happens inside Atlassian's Forge runtime.
1. Data we access
Portal Sub-tasks shows customers the sub-tasks under their Jira Service Management request on the portal. To do that it reads, inside your Atlassian site:
- The request a customer is viewing - only to confirm that the customer can open it on the portal.
- Sub-tasks of that request - limited to the fields shown to customers: summary, status, and (only if an administrator switches them on) due date, percent done and key, plus any labels used to hide internal sub-tasks.
- Service project names and keys - to list projects on the administrator settings page.
- The administrator's own permissions - to confirm the settings page is used by a Jira administrator.
- Sub-task status changes - when an administrator has switched on status comments, to decide whether to add a comment to the parent request.
Portal Sub-tasks does not read or display sub-task descriptions, comments, attachments, assignees, reporters or any other people field. Customers only ever see sub-tasks of requests they can already open.
2. Where data is stored
Portal Sub-tasks stores the following entities in Forge Key Value Store, hosted and encrypted by Atlassian:
Portal Sub-tasks stores one kind of record in Forge storage, inside your Atlassian site:
| Entity | Contents |
|---|---|
| Project settings | Project key, on/off switch, which optional fields customers see, the internal label, the comment mode and the comment text |
It stores no sub-task content, no customer data and no personal data.
Forge Key Value Store data is encrypted at rest by Atlassian using AES-256 and tied to your Atlassian Cloud site. Portal Sub-tasks operates as a tenant inside this storage; we cannot access the data without going through Forge's authenticated APIs invoked by an admin user of your org.
Portal Sub-tasks performs all analysis inside Atlassian's Forge runtime. No End-User Data is transmitted to any third party or outside Atlassian's infrastructure.
Data residency: Forge storage follows Atlassian's data residency commitments. If your Atlassian site is in a specific data region, Portal Sub-tasks's storage stays in that region.
3. Data we share with third parties
None. Portal Sub-tasks runs entirely on Atlassian Forge and makes no external network calls. It has no analytics, no telemetry, no error-reporting service, no AI provider and no third-party SDKs. Nothing leaves Atlassian's infrastructure.
3a. Account actions and data changes
Portal Sub-tasks makes one kind of change, and only if an administrator turns it on: it adds a public comment to a service request when one of its sub-tasks changes status, using the wording the administrator configured. It does not edit, transition, create or delete work items, and it does not manage users, groups or configuration.
4. Data we do NOT collect
- Issue contents, comments, attachments
- Document contents (Confluence pages, JSM tickets, JPD ideas)
- User passwords or authentication tokens beyond what you explicitly provide via Settings
- Behavioral or telemetry data about how admins use Portal Sub-tasks
- IP addresses or geolocation
- Cookies (Portal Sub-tasks runs inside Atlassian's iframe — Atlassian's cookies apply, not ours)
5. Data retention
- Project settings are kept until an administrator changes them or the app is uninstalled.
- Sub-task information shown on the portal is read when the page loads and is not stored.
On uninstall: Atlassian automatically purges all Forge storage associated with the app within 30 days per Atlassian's Forge data lifecycle policy.
5a. Automatic erasure on Atlassian account closure
Portal Sub-tasks implements Atlassian's personal-data reporting flow. Once a week, Portal Sub-tasks posts the list of Atlassian accountIds for which it stores personal data to Atlassian's report-accounts endpoint. If Atlassian responds that an account has been closed (the user has exercised right-to-erasure, or the account has been permanently deactivated) or updated (data is stale or the user requested a refresh):
Portal Sub-tasks stores no personal data, so there is nothing to erase for an individual user. Settings contain only project-level configuration. When the app is uninstalled, Forge removes all of its stored data.
You can also trigger the same erasure path for any user by clearing their entries through any in-app "Clear all data" developer tool, or by uninstalling Portal Sub-tasks entirely.
6. Your rights
You have the right to:
- Access the data Portal Sub-tasks stores — visible in the in-app screens
- Export any in-app audit log as CSV (where the app exposes one)
- Delete all data via any in-app "Clear all data" developer tool, or by uninstalling Portal Sub-tasks
- Be erased automatically when Atlassian flags your account as closed (see section 5a)
For requests under GDPR, CCPA, or similar regulations, contact us at support@taskhooker.com. The automatic erasure flow runs weekly; if you need faster action, email us and we'll process the deletion manually.
7. Children's privacy
Portal Sub-tasks is a business administration tool for Atlassian Cloud organisations. It is not intended for, marketed to, or used by individuals under 18. We do not knowingly collect data about minors.
8. Changes to this policy
We may update this policy when materially new features ship. The "Last updated" date at the top reflects the most recent change. Material changes will be communicated via the Marketplace listing and any in-app notice we deem appropriate.
9. Contact
For privacy questions:
- Email: support@taskhooker.com
- Website: https://portalsubtasks.taskhooker.com
- Address: Melbourne, Australia