LogMyTime — Privacy & Data Handling
LogMyTime runs entirely on Atlassian’s Forge platform. All app data is stored in Forge SQL, hosted by Atlassian inside your Jira Cloud site’s region. No data leaves Atlassian infrastructure — the app declares no external egress, uses no third-party services, no analytics, and no cookies of its own.
What we store
All of the following is kept in Atlassian-hosted storage, per installation:
| Category | Details |
|---|---|
| Worklogs | Author’s Atlassian account ID, issue ID/key, start time in UTC with timezone, duration, billable seconds, free-text description, origin, work-attribute selections. |
| Timesheets and approvals | Periods, statuses, submission snapshots, approver actions with comments. |
| Organizational configuration | Teams, memberships with dates, approvers, shift patterns and assignments, holiday calendars, work attributes. |
| User settings | Timezone, holiday calendar, week start, default period. |
| Pinned issues | The issues a user has pinned to their timesheet. |
| Audit log | Approval-relevant actions. |
What we do not store
- Names, email addresses or avatars — these are resolved live from Jira per viewer, respecting Jira’s permission model, and never persisted.
- Jira issue contents beyond the issue key.
- Credentials or tokens of any kind.
Data flows
The app talks only to the Jira REST API within Atlassian — for issue summaries, display names, permission checks, and the optional native-worklog import/mirror on your own site. Exports are generated in the user’s browser from data that user is authorized to see; the app sends nothing anywhere.
Retention and deletion
Worklogs are soft-deleted and permanently removed when the app is uninstalled, which deletes the installation’s entire database per Atlassian policy.
Data-subject requests
Contact support@bazoho.com; site admins can also remove an individual’s rows on request.
Sub-processors
None — Atlassian (Forge) is the sole infrastructure provider.