Privacy policy
Flowlogs is an app for Atlassian Jira Cloud, built and provided by the Flowlogs team ("the team", "we"). This policy explains what Jira data Flowlogs uses, where it is kept, and for how long.
In short
Flowlogs runs entirely on Atlassian Forge. It has no servers, database, or analytics of its own.
Exports (CSV, Excel, PDF) are created inside the viewer's browser and saved to their device. They are never uploaded anywhere.
We do not sell personal data.
Data Flowlogs processes
Flowlogs only sees Jira data that the person viewing the report is already allowed to see in Jira:
- Jira account identifiers and display names;
- project identifiers, keys, and names;
- issue keys, summaries, statuses, and original estimates;
- worklog authors, dates, descriptions, and time spent;
- the viewer's own report settings and saved report views.
Why it is processed
Only to build the worklog, capacity, estimate, and daily activity reports; to apply the filters the viewer chooses; to draw charts and the team timesheet; to export the report to CSV, Excel, or PDF; to remember settings; and to reopen saved views.
Where it is kept, and for how long
Flowlogs runs entirely on Atlassian Forge. It has no servers, database, or analytics of its own.
| What | How long |
|---|---|
| Report settings | stored in Atlassian Forge storage per Jira account, until changed or the app's data is removed. |
| Saved views | stored in Atlassian Forge storage per Jira account, until the user deletes them or the app's data is removed. |
| Report caches | up to 10 minutes for ranges that include today, up to 60 minutes for past ranges. |
| User directory cache | up to 6 hours. |
| Hourly scheduled job | deletes every cached record once its time is up. |
| In the viewer's browser | the last tab and filters used are kept in the browser's local storage on that device, so the report reopens where the viewer left it. Clearing the browser's site data removes them. |
| Exports (CSV, Excel, PDF) | are created inside the viewer's browser and saved to their device. They are never uploaded anywhere. |
The only Jira account identifiers kept longer than 24 hours are the owner of a settings record or saved view, and any person chosen in a saved view's user filter. A weekly scheduled job reports these identifiers to Atlassian through the Forge Privacy API and deletes them when Atlassian reports that an account has been closed.
Jira stays the system of record. Flowlogs never creates, edits, or deletes issues or worklogs.
Security
Flowlogs uses Atlassian's authentication. Jira data is requested as the current user, so Jira's own permissions decide what each viewer can see. Settings, saved views, and caches are stored under keys tied to the Jira account they belong to, so one user's stored data is never returned to another.
Data location
Atlassian controls where Forge stores app data. See Atlassian's data residency and subprocessor documentation for the hosting that applies to your Jira site.
Your choices and rights
Users can delete their saved views in Flowlogs at any time. Jira site administrators can uninstall the app, after which Atlassian removes its stored data under the Forge data retention rules. For access, correction, deletion, or any other privacy request about Flowlogs data, email privacy@flowlogs.org. Requests about the underlying Jira records should go to your Jira site administrator.
Children
Flowlogs is a business tool and is not directed to children.
Changes
This policy may be updated when the app or the law changes. The effective date at the top shows the current version.
Contact
Flowlogs team
Know where your team's time went, in one Jira page.
Nothing new for your team to learn. Flowlogs reads the worklogs they already keep in Jira.
Try Flowlogs free