Privacy
Privacy policy – Clocker for Jira
Last updated: 4 October 2026
This policy explains what personal data the Clocker app, its website
(clocker.niedzwiecki.dev) and its support process handle, and who handles it.
Who we are
Clocker is made by Dawid Niedźwiecki Development (NIP 9721310416), “we” or “us” in this policy.
Contact for anything about privacy: support@niedzwiecki.dev.
Summary
- Clocker is a Jira Cloud app built on Atlassian Forge. It runs entirely on Atlassian's infrastructure. We don't operate servers that receive your Jira data, and the app sends no data outside Atlassian.
- Your worklogs stay in Jira. The app stores only preferences, running timers and site settings, in Atlassian's Forge storage for your Jira site.
- The app and the website use no cookies, analytics, advertising or tracking.
- We handle personal data ourselves only when you contact support, and when Atlassian shares licensing details with us as the app's vendor.
The app
| Data | Where it lives | Purpose |
|---|---|---|
| Worklogs (time spent, start, description) | In Jira, created and read through Jira's API as the signed-in user | Logging time, summaries, reports, CSV export |
| Issue details (key, summary, project, status, estimates) | Read from Jira on demand, not stored | Showing what time was logged on |
| Your Jira account id, display name, time zone, locale | Read from Jira on demand, not stored except as part of the keys below | Showing your own data in your time zone |
| Your preferences (daily goal, working days, days off, pinned issues, display options) | Forge storage for your Jira site, under your account id | Personal goals and settings |
| Your running timer (issue, start time, note) | Forge storage for your Jira site, under your account id | The timer |
| Site settings (default goal, working days, holidays, rules) | Forge storage for your Jira site | Admin configuration |
The app doesn't collect email addresses.
Where it's stored. Forge storage is hosted by Atlassian, kept separate for each installation (each Jira site) and covered by Atlassian's data residency, security and compliance programmes. See Atlassian's Forge documentation and Trust Center.
Who can see it.
- The app acts with the permissions of the person using it. Jira decides which issues and worklogs they can see, create, edit or delete.
- Only Jira administrators can change site settings.
- We have no access to your Jira site or to the contents of Forge storage.
How long it's kept.
- Worklogs are Jira data and follow your Jira site's retention.
- Preferences and timers stay in Forge storage while the app is installed. Atlassian deletes an app's storage after it is uninstalled, under Forge's data retention policy.
- People can remove their days off, pinned issues and timer at any time in Clocker's settings.
- When a person's Atlassian account is closed, Clocker erases their settings and timer. It checks with Atlassian once a week, using Atlassian's personal data reporting.
For data in the app, your organization (the Jira site's owner) decides how it is used, and Atlassian hosts it. Requests about it, such as access or deletion, go to your Jira site administrator, who can involve Atlassian.
The website
clocker.niedzwiecki.dev is a static website hosted by Cloudflare. It sets no
cookies and loads nothing from other websites: fonts, images and videos come from the site
itself. Like any web host, Cloudflare processes technical data such as your IP address and
browser details to deliver the pages and protect the site from abuse; see
Cloudflare's privacy policy.
When you contact support
If you open a request in our support portal or write to support@niedzwiecki.dev, we receive your name, email address and what you send, such as screenshots or your Jira site's address. We use them only to answer you and to fix what you report. Requests are handled in Jira Service Management, Atlassian's service desk, on our own Atlassian site; the portal asks you to sign in or sign up with your email address. Emails reach it through our email, which runs on Google Workspace.
We keep support requests for as long as we need them to help you and to keep a record of the conversation, and delete them when they're no longer needed.
Licensing information from Atlassian
Clocker is sold through the Atlassian Marketplace. Atlassian handles purchases and billing, and may share licensing details with us as the app's vendor, such as the customer's organization name, the Jira site, the license type and period, and the names and email addresses of technical and billing contacts. We use them only to manage licenses, provide support and send important notices about the app, such as security notices. We don't use them for marketing without your consent.
Legal basis (GDPR)
- Support requests: our legitimate interest in answering you (Art. 6(1)(f) GDPR), or taking steps related to a contract with you (Art. 6(1)(b)).
- Licensing information: performing the contract for the app and our legitimate interest in managing licenses and support (Art. 6(1)(b) and (f)).
- Website hosting: our legitimate interest in delivering and protecting the website (Art. 6(1)(f)).
Who processes data for us
- Atlassian: hosts the app (Forge), runs the Marketplace and our support portal (Jira Service Management).
- Google (Google Workspace): our email.
- Cloudflare: hosts the website.
They may process data outside the European Economic Area under the safeguards in their own data processing terms. We don't sell personal data or share it with anyone else.
Your rights
Under the GDPR you can ask us for access to the personal data we hold about you, and to correct, delete or restrict it, to object to how we use it, or to get a copy in a portable format. Write to support@niedzwiecki.dev. You can also complain to a data protection authority; ours is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, uodo.gov.pl) in Poland.
Changes
We post changes to this policy on this page and update the date at the top.