Privacy Policy — Honest Timesheets for Jira

Effective: 15 September 2026

Honest Timesheets for Jira ("the app") is published on the Atlassian Marketplace by Two Little Moons Consulting, ABN 49 732 400 198, Penrith, NSW 2750, Australia ("we", "us"). Contact: support@twolittlemoons.com.

This policy explains what the app does with data.

What the app does

The app reads and writes Jira worklogs and presents them as a per-person timesheet inside Jira, with approvals, reporting and planning. It runs entirely on Atlassian's Forge platform and sends data to no server outside Atlassian.

Data the app reads from Jira

Always on your behalf and with your own Jira permissions — never with elevated rights:

worklogs (issue, project, author account id, start time, seconds, comment) on issues you can already see;
issue key, summary and parent, for labelling and for grouping reports by epic;
your Atlassian account id, and the display name and timezone of people whose timesheets you are entitled to view;
project roles and their members, when a role is named as a timesheet approver;
your permissions on a project, to decide what you may do.

Data the app writes to Jira

Worklogs, created, edited and deleted as you. The app cannot write a worklog authored by anybody else, including itself: the module that calls Jira does not have access to app-level authentication at all.
A worklog property (timesheets-attributes) on each worklog the app creates or edits, holding its billable flag and any worklog attributes your project configured. It lives on the Jira worklog so any other tool can read it.
An issue property (timesheets) holding per-issue totals and approval status, so timesheet facts are searchable in JQL. It is written only when the value changes.
A Jira notification, only if a project administrator switches reminders on and enables the notification option. It is delivered by Jira's own notification scheme to the person concerned.

The app never creates, edits, transitions or deletes an issue, and never posts comments.

Data the app stores in Forge app storage

This section changed in version 4. Earlier versions stored nothing.

All of the following is held in Atlassian's own Forge storage, inside your site's installation. None of it is issue content and none of it is worklog text.

What	Why	Keyed by
Project settings — period shape, working pattern, public holidays, approval stages and approver account ids or role ids, worklog attribute definitions, rounding policy, reminder settings, charge-out rates, team and manager account ids	So the timesheet behaves the way the project decided	project
Personal working pattern	So somebody working part time is measured against their own hours	project + account
Approval state and history — status, current stage, and each transition's actor, timestamp and comment	So a sign-off is auditable and cannot silently change	project + account + period
The running timer — the issue and the start/stop instants of each segment	So a timer survives closing the tab or changing machine	account
In-app notices — the text of a reminder or approval notice	Forge apps cannot send email; this is how you are told	account
Workplans — an issue, a date and an intended number of hours	So planned time can be compared with actual without being written to Jira as fake worklogs	project + account + month
Saved report definitions — a name, the groupings and the range length	So a report can be re-run	project
A mirror of worklog attributes — billable flag and attribute values, by worklog id	Jira holds the authoritative copy on the worklog; this mirror exists only so a grid of eighty entries costs one read instead of eighty	account + month

Charge-out rates are figures an administrator types in; the app does not connect to any payroll or finance system and holds no salary data.

Removal

Uninstalling the app deletes everything in the table above, because Forge app storage belongs to the installation. Your worklogs are not deleted — they are ordinary Jira worklogs and always were, which is the point of the design. The worklog and issue properties the app wrote remain on the worklogs and issues; a Jira administrator can delete them through Jira's own REST API if you want them gone.

Data leaving Atlassian

None. The app declares no external fetch permissions, so it is not technically capable of contacting any host other than Jira's own REST API through Forge. It qualifies for Atlassian's "Runs on Atlassian" designation, and data residency follows your Jira site.

Logging

Forge keeps invocation logs for troubleshooting. They contain timestamps, the Jira REST path called, HTTP status codes, Jira's own error messages, and counts. They do not contain worklog text, timesheet figures, display names or email addresses; account ids are not written to them. Site administrators control whether log access is shared with us.

Your rights

To export or delete what the app has stored, uninstall it — that removes all of it at once. For anything more specific, or any question about this policy, email support@twolittlemoons.com and we will respond within 30 days.

Changes

We will update this page and the effective date if the app's data handling changes. Adding an external service, or any new category of stored data, would be announced in the app's release notes before it ships.