TimeFlow Exporter for Jira Cloud
Effective date: October 24, 2026
Vendor: Imdad_hub
This policy describes how Imdad_hub ("we", "us", or "our") handles data and security matters for TimeFlow Exporter (the "App"), an Atlassian Forge app for Jira Cloud. It covers the App's processing of Jira worklog information and its transmission of exported data to a webhook destination configured by a Jira administrator.
Atlassian's handling of data on its platform, and the handling of data by any webhook recipient, are governed by their respective terms and policies.
To perform an export, the App processes Jira worklog information returned by Jira. Depending on the records returned, this may include:
The App queries for worklogs updated during the most recent seven days and exports only those whose worklog start date also falls within that period. Exports may be initiated by a scheduled job or manually by an administrator.
The App uses Atlassian Forge Key-Value Storage (KVS) to store the configured webhook URL and the latest export status, such as the export time, outcome, and worklog count. The App is not designed to store full exported worklog records in KVS.
When an export runs, the App sends the relevant worklog data to the
webhook destination configured by the Jira administrator. The current
Forge egress configuration permits outbound requests only to
https://webhook.site, so other destinations may not be
reachable unless the App's egress configuration is changed and deployed.
The App's URL handling may accept HTTP or HTTPS, but that does not mean
every destination is permitted by the current egress configuration.
HTTPS is recommended to protect data in transit.
The receiving service may process, store, or further transmit the data according to its own practices. Administrators should review the recipient's access controls, security, and retention practices before using it.
The App runs on Atlassian Forge. Imdad_hub does not operate a separate server to receive the exported worklog payloads.
The App may generate operational logs through the Forge platform to help troubleshoot problems and record export status. Earlier versions of the App logged the configured webhook URL and save payloads that could contain that URL. The current development version has been updated to remove those direct logging statements. This change does not remove entries already retained in logs from earlier versions, and the fix has not yet been released to Marketplace customers.
Do not include passwords, access tokens, or other secrets in a webhook URL. Because historical logs may contain previously logged webhook URLs, users should treat an affected endpoint as potentially exposed and replace it where appropriate. Operational logs are subject to Atlassian Forge's platform practices and applicable retention controls. The App's operational logs are not intended to contain the exported worklog payload.
The App runs on Atlassian Forge, which provides its application runtime and platform services. The App uses Forge KVS for configuration and export-status values.
The App requests the following Jira/Forge permissions:
read:jira-workread:jira-userstorage:app
These permissions support retrieving Jira worklog and related issue or
user information, and storing App configuration and status. The App makes
outbound webhook requests from its Forge backend, subject to its configured
Forge egress permissions. The current configuration permits outbound
access only to https://webhook.site.
We aim to limit the App's processing and storage to what is needed for its export and operational functions. We recommend that administrators use an HTTPS webhook destination and avoid putting credentials or other secrets in webhook URLs.
Once data has been delivered to a webhook destination, the security and handling of that data depend in part on the receiving service and its configuration.
To report a suspected security vulnerability or security incident involving the App, contact us through the Atlassian Marketplace support channel listed for TimeFlow Exporter. Include a description of the issue, its potential impact, and steps to reproduce it when available. Do not include passwords, access tokens, or other secrets in a report.
We will review reports, assess their scope and severity, and take appropriate steps to investigate and address confirmed issues. We do not promise a fixed response or resolution time.
When we become aware of a potential vulnerability or security incident involving the App, we will assess the information available, investigate as appropriate, and take reasonable steps to contain and remediate confirmed issues. Where appropriate, we may coordinate with Atlassian and notify affected customers through the Marketplace support channel or another suitable communication method.
App fixes and updates are delivered through Atlassian Forge deployments and the applicable Marketplace release process. Administrators should install available updates and keep their Jira site and configured webhook destination appropriately secured.
Jira administrators are responsible for:
We may update this policy when the App's functionality, data handling, or security practices change. The latest version will be published at this URL. Please review this page periodically for updates.
For privacy or security questions about TimeFlow Exporter, contact Imdad_hub through the Atlassian Marketplace support channel listed for the App.