Privacy policy
A Jira app by Vudia. This page explains exactly what the app reads from Jira, what it stores, and what it never touches.
Summary#
Cost Tracker is built on Atlassian Forge and runs entirely on Atlassian's infrastructure — it has no servers of its own and makes no outbound network call to anything outside Atlassian. We do not operate any system that receives your data, and we cannot see the data your site holds in the app. The app reads issues, worklogs, and user names using the permissions of whoever is using it, and stores the projects, rates, expenses and reports your users enter in Forge storage, scoped to your own site.
What it reads from Jira#
Depending on what a feature needs, and always live, using the viewer's own Jira permissions:
- Issue key, summary, status, type, created/due dates, and the status-category change date, for issues matching a cost project's own scope
- Worklogs on those issues — author account ID and display name, time spent, and date
- The list of Jira projects on your site, to populate the project/space picker
- User search results, to add people to a team, share a project, or transfer ownership
- The caller's own account profile, and whether they hold the site's
ADMINISTERpermission, to gate site-wide setup screens
None of it is copied anywhere outside your site.
What it writes to Jira#
Nothing. The app never creates, edits, transitions, or comments on a Jira issue — it only reads.
What it stores#
In Forge storage, scoped to your site: the cost projects, portfolios, roles, hourly rates, team memberships, expenses, revenue entries, budgets, milestones, cost accounts, custom attributes and saved reports that your users create, plus a short-lived cache of computed report totals (recomputed every ~15 minutes, or sooner after a change that affects the numbers).
Rates are sensitive data#
Hourly cost and billing rates are tied to named people and can reveal compensation-related information. Who can see a project's rates is controlled by that project's own sharing settings — set, and changeable only, by its owner. There's no feature that surfaces one project's rates to someone who isn't given access to that project.
Retention & deletion#
Data stays in your site's Forge storage until your users delete it in the app, or until the app is uninstalled. Deleting a cost project removes its own rates, team, expenses, revenue, budget and milestones; it does not retroactively scrub it from a portfolio's history, which instead shows a "member was deleted" note. Removal of storage after uninstall follows Atlassian's own Forge retention policy.
Where data is stored#
Inside Atlassian's own Forge storage platform, in the same data residency as the rest of your Jira site. Nothing leaves Atlassian's infrastructure — the app declares no permission to call any external service.
Logs#
The app writes a diagnostic log line only when something fails unexpectedly. These logs are not used to reconstruct rates, expenses, or other figures you've entered.
Analytics & tracking#
None. The app contains no analytics, no tracking pixels, no advertising, and no third-party scripts of any kind.
Your rights#
Because we hold no copy of your data outside your own Forge storage, requests to access, correct, or delete it are handled directly inside the app and Jira by your site administrators — sharing settings determine who can reach a given project's data, and a site admin can always reach it. If you have a question we haven't answered here, contact us using the details below.
Changes to this policy#
If what the app reads, writes, or stores changes, this page changes with it.