Keepclock for Jira: Privacy Policy
Effective date: October 1, 2026 Publisher: Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA Contact: hello@greatwork.company
This policy explains what information the Keepclock app for Jira Cloud (the "App") processes, where it is kept, and your rights. It covers only the App, not Atlassian's products, which are governed by Atlassian's own privacy policy.
1. Summary
- The App runs entirely on Atlassian's Forge platform ("Runs on Atlassian"). It has no servers of its own and sends no data to Great Work or to any third party.
- It reads work items and their change history to run SLA clocks, stores the clock results in Atlassian-hosted storage for your site, writes SLA values into the custom fields your admins create from its field type, and sends SLA emails through Jira's own notification service.
- Great Work LLC cannot see your work items, your SLA results or who used the App.
2. What the App processes
| Data | Why | Where it lives |
|---|---|---|
| Work item facts: id, key, summary, project, work type, priority, created time, status, resolution, assignee (account id and display name) | To run and report SLA clocks | Clock records in Forge SQL for your site (below); otherwise in memory while a calculation runs |
| Change history entries for status, assignee, resolution, priority and any field an admin picks in a "field changes" condition (time, field, from and to values) | To know when clocks start, pause and stop | In memory while a calculation runs; not stored |
| SLA clock records: work item id, key, summary, project, work type, priority, assignee id and name, SLA, cycle start and stop times, working time used, goal, calendar, state, deadline, notification flags | The SLA panel, the report page, the dashboard widget, the scheduler | Forge SQL for your site, until the work item or the SLA is deleted, or the App is uninstalled |
| SLA values (state, deadline, minutes used and left, a short label) | So Jira can show, search and export SLAs | In your Jira, in the custom fields created from the App's field type, like any other field value |
| SLA definitions, working calendars, settings, including the account ids of people an admin chose to notify | To apply your admins' choices | Forge app storage until changed or uninstall |
| Recalculation jobs (the JQL used, progress counts) and an activity log (time, kind, short message with work item keys) | So admins can see what the App did | Forge app storage; deleted automatically after 30 days |
| Short-lived cache of status names and categories | Speed | Forge app storage; deleted automatically after 10 minutes |
SLA emails are sent with Jira's issue notification API to the people your admins choose, and Jira delivers them only to people who can see the work item. The App does not read descriptions, comments, attachments or worklogs, and does not collect email addresses, IP addresses, passwords, API tokens, payment information or analytics. It sets no cookies and loads no third-party scripts.
3. Where data is stored
All App data is stored by Atlassian: in your Jira site (field values), in Forge app storage and in Forge SQL for your site, subject to Atlassian's data residency settings. Atlassian is the hosting provider and acts as a subprocessor under Atlassian's terms. Great Work LLC uses no other subprocessors.
4. Who can see what
- SLA field values are visible to everyone who can see the work item, like any Jira field.
- The SLA panel shows the SLAs of the work item being viewed.
- The report page and the dashboard widget show only projects the viewer can browse, and their work item lists show only work items the viewer can see.
- Jira admins see the admin page, its jobs and activity log.
- Great Work LLC: no access. If you open a support request, we see only what you send us.
- Atlassian: as the platform operator, under Atlassian's privacy policy.
5. Retention and deletion
Clock records are removed when their work item is deleted, when the SLA is deleted, or when the App is uninstalled. Jobs, the activity log and caches expire automatically (see section 2). Uninstalling the App removes its Forge storage and Forge SQL data according to Atlassian's Forge data deletion process. Fields created from the App's field type disappear from Jira when the App is uninstalled and come back with their data if it is reinstalled within 30 days (Atlassian's rule for Forge custom fields).
6. Support requests
If you contact support through our help desk or by email, we process what you send (name, email, message, attachments) only to answer you, keep it up to 24 months, and delete it sooner on request.
7. Your rights
Depending on where you live (for example EU/UK GDPR or US state privacy laws), you may have the right to access, correct, delete or port personal data and to object to processing. For data in your Jira site, your organization (the Atlassian customer) is the controller and Atlassian processes it on your behalf; your admins can delete SLAs, delete the fields or uninstall the App. For support data, Great Work LLC is the controller: email hello@greatwork.company. We respond within 30 days.
8. Security
The App uses only Atlassian-hosted compute and storage. It can write only to fields of its own field type (Jira enforces this), admin functions run only from the admin page Jira shows to Jira admins, and the report checks the viewer's own permissions. It keeps no secrets of its own. Report vulnerabilities to hello@greatwork.company.
9. Children
The App is a business tool and is not directed to children under 16.
10. Changes
We will post changes here and update the effective date. Material changes will also be announced in the App's Marketplace release notes.
11. Contact
Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA. hello@greatwork.company