Issue Templates by Taskhooker — Privacy Policy

Effective date: 2026-05-30 Last updated: 2026-05-30

This privacy policy describes how Issue Templates by Taskhooker ("we", "us", "the app") handles your data. Issue Templates by Taskhooker is an Atlassian Marketplace app distributed via the Atlassian Forge platform. By installing Issue Templates by Taskhooker, you agree to this policy.

Summary in plain English

All data stays inside Atlassian's infrastructure. Issue Templates by Taskhooker 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. Issue Templates by Taskhooker runs on Atlassian Forge — Atlassian hosts every function call and storage write.
API keys you supply are encrypted at rest in Forge's Key Value Store. They are never logged, never returned in API responses, and never sent to any third party; all processing happens inside Atlassian's Forge runtime.

1. Data we access

Issue Templates is an authoring tool: it stores the templates a Jira administrator creates, and reads only the Jira configuration needed to build and apply them. It does not read, collect, or store the content of your existing work items.

From your Atlassian site (via Atlassian's Jira REST API inside Forge)

Projects and work item types — GET /rest/api/3/project/search — so an admin can choose where a template applies.
Create-screen field metadata — GET /rest/api/3/issue/createmeta/... — so an admin can choose which fields a template prefills, with their allowed values.
Assignable users for a project — GET /rest/api/3/user/assignable/search and GET /rest/api/3/user — used only when an admin prefills an assignee or user-type field on a template, so the chosen person is valid in that project.
Newly-created work items — via the avi:jira:created:issue event and GET /rest/api/3/issue/{key} — so the app can apply a picked template's child-item tree to the work item just created.

Personal data

The only personal data the app stores is the Atlassian accountId of the admin who authored a template (recorded as the template's author), and — if an admin explicitly prefills an assignee/user field — the accountId chosen for that field. No end-user content, page text, comments, or browsing activity is collected.

2. Where data is stored

Issue Templates by Taskhooker stores the following entities in Forge Key Value Store, hosted and encrypted by Atlassian:

tpl:<id> — a template: its name, targeting scope, prefilled field values, optional child work-item tree, the author's accountId, and timestamps.
asn:<project>:<type> / idx:<project>:<type> — per-(project, work-item-type) membership and the small index the Create screen reads.
Live-apply records — the app's custom field id, per-(project, type) field-context id, UI-modification entity id, and option ids.
applyrun:<id> — transient status of an asynchronous child-tree creation.
meta:templateCount — a simple counter.

The only personal data among these is Atlassian accountIds (a template's author, and any assignee an admin prefilled).

Forge Key Value Store data is encrypted at rest by Atlassian using AES-256 and tied to your Atlassian Cloud site. Issue Templates by Taskhooker 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.

Issue Templates by Taskhooker 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, Issue Templates by Taskhooker's storage stays in that region.

3. Data we share with third parties

None. The app makes no external network calls of any kind — no analytics, no error reporting, no AI vendor, no marketing tools. It declares no permissions.external.fetch hosts. The only API it contacts is Atlassian's own Jira REST API via Forge's internal requestJira proxy, inside Atlassian's runtime. No data ever leaves Atlassian's infrastructure.

3a. Account actions and data changes

When a user picks a template on the Create screen, the app:

Prefills field values on the work item being created, and
Creates child work items (e.g. an Epic's Stories and Subtasks) and parents them, when the template defines a hierarchy.

These actions happen in the project where the template is used, as part of creating that work item. The app also manages its own Jira configuration to enable live apply: it creates one app-owned custom field ("Apply Template"), scoped field contexts, and UI modifications. The app does not modify or delete your existing work items, does not change user accounts, and does not touch any content other than the templates it manages and the work items explicitly created from a template.

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 Issue Templates by Taskhooker
IP addresses or geolocation
Cookies (Issue Templates by Taskhooker runs inside Atlassian's iframe — Atlassian's cookies apply, not ours)

5. Data retention

Templates and the app's configuration persist until an administrator deletes a template or uninstalls the app. Deleting a template removes its stored body (including the author accountId). Uninstalling the app removes all of the app's Forge storage for your site. There is no separate off-site copy — storage lives only in Atlassian's Forge Key Value Store for your site.

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

Issue Templates by Taskhooker implements Atlassian's personal-data reporting flow. Once a week, Issue Templates by Taskhooker 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):

The only personal data to erase is Atlassian accountIds held inside stored templates (a template's author, and any assignee an admin prefilled). To erase it: delete the template (removes its author and any prefilled assignee), or uninstall the app (removes all of the app's stored data for your site). For a request under GDPR, CCPA, or similar, email support@taskhooker.com and we will process the deletion.

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 Issue Templates by Taskhooker entirely.

6. Your rights

You have the right to:

Access the data Issue Templates by Taskhooker 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 Issue Templates by Taskhooker
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

Issue Templates by Taskhooker 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://tmpl.taskhooker.com
Address: Melbourne, Australia