Privacy Policy

Last updated: September 7, 2026

This policy covers apps published by HelzBrand for Atlassian Jira Cloud, and this website. All HelzBrand apps are built on Atlassian Forge and run entirely on Atlassian's cloud infrastructure. Our security practices are described separately in our Security Policy.

The short version

What our apps store

Apps store only their own configuration and operational records in Atlassian Forge hosted storage, inside your Jira site's context. They read and write Jira data (such as work items) only as needed to perform the function you configured, using the permissions shown to your admin at install time. Where a future app exists to integrate with a third-party service you explicitly connect, your data flows only between your Jira site and that service, and that app's section below and its Marketplace listing will state exactly what is accessed and shared.

Cadence: Recurring Work for Jira

Stores the schedule configurations you create: schedule name, project and issue type identifiers, template content you provide (summary, description, labels, subtask text), recurrence and due date settings, the Atlassian account ID of the schedule creator (display names are looked up live from Jira and never stored), and run bookkeeping (next run time, created count, last created item key). Site administrators may also store display settings (accent color, name template). The app declares zero external network egress; no data leaves Atlassian's infrastructure.

Chime: Reminders for Jira

Stores the reminders you create: the time the reminder is due, the note you attach, the Atlassian account ID of the recipient and of the person who set it, the work item the reminder belongs to, and delivery bookkeeping. Reminders are delivered using Jira's own notification system, to the address Jira already holds; the app never stores email addresses and never sends mail through a third party. Site administrators may also store display settings (accent color). The app declares zero external network egress; no data leaves Atlassian's infrastructure.

Orchestra: Dependency Graph for Jira

Reads work items and the links between them to draw dependency graphs on demand. Graph contents are not stored: each view is built from Jira at the moment you request it. The only data the app stores is site display settings an administrator configures (accent color). The app requests read access to Jira work only, so it cannot create, edit, or link work items. It declares zero external network egress; no data leaves Atlassian's infrastructure.

Notation: Dashboard Notes for Jira

Stores the note content you write, per gadget, in Atlassian Forge hosted storage, together with the appearance settings for that note. Content is written only when you save it. Editing is restricted to people with edit rights on the dashboard the note sits on. The app declares zero external network egress; no data leaves Atlassian's infrastructure.

Unison: Duplicate Custom Field Prevention for Jira

Reads your Jira custom field inventory, field configurations, and field contexts in order to compare a proposed field name against fields that already exist. Comparison happens at the moment you ask for it and results are not stored. When an administrator explicitly asks, the app creates a custom field; it never edits or deletes existing fields. The only data stored is site display settings an administrator configures (accent color). The app declares zero external network egress; no data leaves Atlassian's infrastructure.

Metronome: Harvest Time Tracking for Jira

This app communicates with a third party service, Harvest, because that is its purpose. It is the one HelzBrand app that sends data outside Atlassian's infrastructure, and it is not part of the Runs on Atlassian program.

When you connect the app, you authorize it against your own Harvest account using Harvest's own sign in page. The resulting authorization is held and refreshed by the Atlassian Forge platform, not by the app: the app never receives, stores, or transmits your Harvest password or access tokens. The following is sent to Harvest, only in direct response to an action you take: the work item key and summary, used to prefill the note on a time entry; a work item identifier and permalink, stored on the entry as an external reference so the entry links back to Jira and can be filtered per work item; and the project, task, date, and duration you select.

In Atlassian Forge hosted storage the app keeps only your Harvest account and user identifiers and display names, one account preference, site level configuration an administrator sets, and queued records for time it is preparing to log on your behalf (work item identifier, key and summary, Harvest project code, task name, duration, and the rule that queued it). No credentials are stored. When you choose to, the app also writes a Jira worklog mirroring time you logged in Harvest.

Time entries themselves live in Harvest, under your own Harvest account, governed by Harvest's privacy policy and your agreement with them. Disconnecting revokes the authorization held by the Forge platform and stops all communication with Harvest. Data already written into Harvest or into Jira worklogs remains in those systems and is managed there.

Libretto: Document Export for Jira

Stores the export jobs you start (the query, the template, format, timings, the delivery issue if any, and the Atlassian account ID of the person who started the job) and the schedules you save (the same fields plus the cadence), in Atlassian Forge hosted storage. The issue data fetched for an export and the finished PDF or Word file are held in the Atlassian Forge Object Store, inside your site's context; intermediate data is deleted as soon as the file is delivered and finished files are deleted after the retention period an administrator sets (seven days by default) or when you remove the export. Files you choose to attach to a work item stay on that work item under Jira's own rules. Manual exports run as you and contain only what you can see; scheduled exports re-check the owner's permissions before each run. Site administrators may also store display and limit settings (accent color, default format, maximum issues, retention days). The app declares zero external network egress; no data leaves Atlassian's infrastructure.

Tacet: Backlog Cleanup for Jira

Stores a record of each sweep you run (the board or project, the number of days, the action and resolution, the keys of the work items changed together with the status each one had before, and the Atlassian account ID of the person who ran it), warning records for work you chose to warn rather than close, saved search scopes, and site settings an administrator configures (defaults, comment templates, grace period, accent color), all in Atlassian Forge hosted storage. The app acts only as the person using it, using Jira's own permissions, and writes comments and transitions to work items only when you confirm a sweep. The app declares zero external network egress; no data leaves Atlassian's infrastructure.

Ensemble: Component Hierarchy for Jira

Stores, for each project where it is used, the component hierarchy (which component is nested under which, together with the component names so the JQL function can resolve them), the views you save (a name, the selected component, section filter and search text, keyed by your Atlassian account ID), and site settings an administrator configures (card fields, accent color), all in Atlassian Forge hosted storage. The app acts only as the person using it, using Jira's own permissions, and changes work items, sprints and ranking only when you drag or confirm an action. The app declares zero external network egress; no data leaves Atlassian's infrastructure.

Fermata: Field Locking for Jira

Stores the locking rules a Jira administrator configures (projects, issue types, fields, conditions, and the Atlassian account IDs, group IDs and project role IDs they exempt), a log of the most recent 500 changes it put back or would have put back (the work item key, the field, the value that was tried and the value restored, the rule, and the Atlassian account ID and display name of the person who made the change), and site settings (accent color), all in Atlassian Forge hosted storage. To decide whether a change is allowed it reads the person's group and project role membership. When it puts a change back it writes the previous value to the work item and, unless the rule turns this off, posts a comment that mentions the person; those comments stay on the work item under Jira's own rules. Only Jira administrators can create or change rules. The app declares zero external network egress; no data leaves Atlassian's infrastructure.

Stave: Gantt Charts for Jira

Stores the chart views people save and share (a name, the source: a project key, saved filter ID or JQL text, the date fields, grouping, zoom and export layout, and the Atlassian account ID and display name of the person who saved it), the scheduled exports people set up (name, chart settings, cadence, the work item that receives the file, and the owner's Atlassian account ID), a record of each export (the requester's Atlassian account ID, the query, and the work item IDs) and the finished export files, which contain the exported work items' keys, summaries, statuses, assignee names, dates, parents, fix versions and dependencies, for 7 days, and site settings (accent color), all in Atlassian Forge hosted storage. Your browser also remembers your last chart setup on that device. The app acts as the person using it, using Jira's own permissions, and changes work items only when that person drags a bar or a dependency or confirms an action. A scheduled export attaches the file to the chosen work item and adds a comment; those attachments and comments stay on the work item under Jira's own rules. The app declares zero external network egress; no data leaves Atlassian's infrastructure.

Sections for additional HelzBrand apps are added here when each app becomes available on the Atlassian Marketplace.

Data retention and deletion

Deleting an item inside an app (for example, deleting a schedule) permanently removes its stored configuration. Uninstalling an app removes its access; stored app data is subsequently deleted in line with Atlassian Forge's data lifecycle for uninstalled apps. Jira work items created by an app are normal Jira data owned by your site and are unaffected by uninstalling.

Your Atlassian data

Your use of Jira is governed by Atlassian's own privacy policy and your agreements with Atlassian. HelzBrand apps operate within that environment.

This website

helzbrand.com is a static website. It does not use cookies, does not run analytics or tracking scripts, and does not collect personal information. It is served by Cloudflare, whose infrastructure may process standard technical request data (such as IP addresses) to deliver the site; see Cloudflare's privacy policy for details.

Email

If you contact us at support@helzbrand.com or privacy@helzbrand.com, we receive the information you choose to send. We use it only to respond to you and do not share it with anyone.

Contact

Questions about this policy or any HelzBrand app: privacy@helzbrand.com