Effective 13 October 2026

Privacy policy

Advanced Structured Gantt is a Jira Cloud app built on Atlassian Forge. It processes Jira data only to provide the timeline, grouping, progress, date-editing and export features requested by the user.

Data the app accesses

The app may read Jira work items returned by a user-provided JQL query, Jira field metadata and Jira filters available to the current user. This can include work item keys, summaries, statuses, assignees, dates, estimates, story points and values of fields selected for display or grouping.

How data is used

Jira data is used to build the on-screen list and timeline and to generate exports initiated by the user. Choosing new dates in the timeline opens a preview of the current and proposed Jira dates. The app writes those dates only after the user explicitly confirms and Jira permits the edit. Undoing the latest date change also requires confirmation.

Storage and external sharing

The app does not use a developer-operated database and does not send Jira data to an external analytics or processing service. Saved view names, JQL queries, field mappings and display preferences are stored in the user's browser local storage, separately for each Jira site and account. These user-entered names or queries may contain personal information. The namespace includes the Jira cloud ID and account ID. When that context or persistent storage is unavailable, preferences stay in memory for the current view. Jira requests run through Atlassian Forge in the current user's Jira context.

User-requested PDF and PNG exports contain the selected Jira data and are downloaded to the user's device. The user controls any subsequent sharing of those files.

Permissions

read:jira-work is used to read work items, fields and filters. write:jira-work is used only when an authorized user confirms an update to the configured date fields, including an undo.

Retention and deletion

The app does not persist fetched Jira work items or profile data in a developer-operated database or Forge storage. Browser-local preferences persist until the user clears them. In Settings > Browser records, the user can confirm deletion of the current Jira site's and account's saved view names, JQL queries and preferences. The app then reloads. This control leaves other account/site records and downloaded files unchanged; uninstalling alone does not clear browser records.

Legacy preferences created before account/site separation are not imported automatically and are not removed by the account-specific control. They can be removed by clearing the relevant browser site data. Downloaded reports remain on the user's device until the user deletes them.

Security

Authentication and hosting are provided by Atlassian Forge. The app does not request or store Jira passwords or API tokens. Access remains subject to Jira permissions. See the separate security practices page for security controls and vulnerability management.

Privacy and security contact

Contact Veysel Baysal at vyslbaysal@gmail.com for questions or incident reports. Please do not include passwords, API tokens or unnecessary Jira work item data.

Changes

This statement may be updated when the app's data practices or features change. The effective date above identifies the current version.