TooLooLoo

Privacy policy, Worklog Reports for Jira

Last updated 28 August 2026.

The short version

The app runs entirely inside Atlassian's Forge platform. It declares no external domain, makes no outbound network call, and stores nothing outside Atlassian's own storage. No data leaves your Atlassian site because of this app, and the publisher operates no server that could receive any.

What the app reads

Through Jira's REST API, with the read:jira-work scope only:

It reads nothing else. It never writes to Jira.

What the app stores, and where

In Forge storage, which lives in Atlassian's infrastructure under your site:

Aggregates are stored per project and served only to a reader who holds BROWSE_PROJECTS on that project. The scheduled rebuild runs as the app and therefore sees every worklog on the site; the permission check happens when a report is read, not when it is built.

What a shared link carries

The view only: project, period, person, grouping, sort and search. Never a figure. Anyone opening a shared link is checked against their own account and sees nothing if they cannot browse that project.

Problem reports

The in-app "Report a problem" button builds a pre-filled URL and hands it to your browser. Your browser navigates there if you choose to; the app itself never sends anything. A report carries a fixed list of eight fields: app version, locale, tab, the name of the period, the grouping, the project id, the browser, and the error. No hours, no names, no work item titles. The page shows you the exact payload before you send it, produced by the same function that stores it.

Retention and deletion

Uninstalling the app removes its Forge storage. There is nothing else to delete, because there is nowhere else data was sent.

Sub-processors

None. The publisher operates no infrastructure for this app.

Contact

support@toolooloo.fr