Issue Templates Privacy Policy
This notice supplements the Fulstech Privacy Policy for Issue Templates & Hierarchy Builder for Jira Cloud.
Where data is processed
Section titled “Where data is processed”The app runs on Atlassian Forge. App-owned configuration and operation data is stored in Atlassian-hosted Forge SQL or in app-owned Jira entity properties. The app does not declare an external remote, egress domain, or runtime analytics service, and does not transfer Jira customer data to a Fulstech database or another third-party system.
Data the app may store
Section titled “Data the app may store”Depending on the features used, stored data can include:
- Template names, descriptions, field values, variables, comments, attachment references, and hierarchy definitions.
- Jira project, issue-type, field, option, Sprint, group, account, and issue identifiers needed to validate or run a template.
- Atlassian account-ID references selected for user fields or access rules. Copied profile labels, email addresses, avatars, locale, and time-zone data are removed before app storage. Jira resolves the current user label when it renders a user picker or Jira field.
- Defaults, revisions, run plans, run and child status, actionable error text, provenance, and bounded audit events.
- Versioned same-tenant backup documents when an administrator creates or restores them.
The app does not ask for passwords, Atlassian personal access tokens, payment card data, or unrelated profile information.
How data is used
Section titled “How data is used”Data is used only to provide the installed app: author and find templates, preview changes, create or update selected Jira work, enforce availability, prefill an administrator-approved Jira Create context, show provenance, recover partial runs, and back up app configuration.
Access and sharing
Section titled “Access and sharing”Jira and app permissions determine who can read or change a template and the related Jira work. Fulstech does not sell customer data or share it with an external advertising or analytics provider.
Retention
Section titled “Retention”The app defines no external retention store. Templates can be archived in the product, and issue-relation records are cleaned when Jira reports the related issue deleted. Forge-hosted data after uninstall follows Atlassian’s Forge application-data lifecycle. Contact support for a tenant-specific data request before uninstalling if you need help identifying the relevant configuration.
Contact
Section titled “Contact”For privacy questions or requests, use the Fulstech support portal. Do not include passwords, tokens, or unrelated confidential issue content.