Legal
Privacy Policy
Last updated: May 2026
Short version: All Jira API requests are relayed through our server as a proxy. Your credentials, tokens, and worklog data pass through in transit but are never stored, logged, or retained in any form. The only thing we record is your IP address, for abuse prevention.
1. Who we are
Worklogging (worklogging.de) is a browser-based tool that helps individuals and teams enter Jira worklogs faster. The application is delivered as static HTML/CSS/JavaScript files hosted at app.worklogging.de.
2. What data we collect
2.1 Server / access logs
Our web server (like every web server) automatically records standard HTTP access log entries when you visit the site. These entries contain:
- Your IP address (or the IP of your proxy / NAT gateway)
- The requested URL, HTTP method, and response status code
- Timestamp and, where present, the referring URL and browser user-agent string
We retain access logs for up to 14 days solely for abuse prevention (e.g. detecting and blocking automated attack traffic or excessive scraping). Logs are not shared with third parties and are not used for advertising, profiling, or analytics.
3. What we do not collect
The following data never reaches our servers and is never logged, stored, or processed by us:
- Your Jira email address or API token
- Any other credentials, passwords, or authentication secrets
- The content of your worklogs, comments, or issue descriptions
- Your Jira project names, issue keys, or worklog history
- Any data you enter into, or retrieve from, the Worklogging application
All application data (configuration, templates, tracked issues, settings) is stored exclusively in your own browser's localStorage. It never leaves your device unless you explicitly export it.
4. Local data storage
The application stores the following items in your browser's localStorage under the domain app.worklogging.de:
- Your Jira base URL and API access mode preference
- Your Jira email address and API token (used to authenticate directly to the Jira API from your browser)
- Tracked issue keys and colours you have configured
- Worklog templates you have created
- Application settings (e.g. daily target hours, display preferences)
This data is managed entirely by your browser. You can clear it at any time via your browser's developer tools or by using the "Clear all data" option within the app.
5. Jira API requests — server proxy
All Jira API requests made by the Worklogging application are relayed through our server as a reverse proxy. The server forwards each request to the Atlassian Jira API on your behalf and returns the response to your browser.
This means that request and response data — including your API token, Jira base URL, worklog entries, and any other payload — passes through our server in transit.
None of this data is ever written to disk, logged, stored, cached, or retained in any form. Our server processes each request purely as a transparent relay and discards it immediately after forwarding the response. The only information our server records is the IP address of the connecting client, as described in Section 2.
Atlassian's own privacy policy governs how Jira processes the data once it reaches their servers. See atlassian.com/legal/privacy-policy.
6. Future paid accounts (if applicable)
Should paid account tiers be introduced in the future, the following additional data may be stored on our servers for account management purposes:
- Your Jira base URL (e.g.
yourcompany.atlassian.net), to associate a subscription with an instance - A one-way cryptographic hash (e.g. bcrypt or Argon2) of your email address, used for account identification — the original email address is not stored in recoverable form
No API tokens, passwords, or worklog content would ever be stored server-side even in paid tiers. Any changes to data handling for paid accounts will be communicated clearly before they take effect, and separate, explicit consent will be obtained where required.
7. Cookies and tracking
We do not set any cookies. We do not use any third-party analytics, advertising, or tracking scripts (e.g. Google Analytics, Meta Pixel). There are no session cookies, tracking pixels, or fingerprinting techniques in use.
8. Third-party services
The Worklogging website and application do not embed any third-party scripts, fonts loaded from external CDNs, or external resources that could track you. All assets (HTML, CSS, JavaScript, images) are served directly from our own infrastructure.
9. Children's privacy
Worklogging is a professional productivity tool intended for use by adults in a work context. We do not knowingly collect any information from anyone under the age of 16.
10. Your rights
Depending on your jurisdiction, you may have the right to:
- Access the personal data we hold about you
- Request deletion of your personal data
- Object to or restrict certain processing
- Lodge a complaint with a data protection authority
Because we hold only IP-level access logs (retained for at most 14 days), the practical scope of these rights is limited. To exercise any of these rights or to ask a question about privacy, contact us at the address below.
11. Changes to this policy
We may update this policy from time to time. Material changes will be indicated by an updated "Last updated" date at the top of this page. Continued use of the service after a change constitutes acceptance of the revised policy.
12. Contact
For privacy-related questions or requests, please reach out via the contact details published in the legal notice (Impressum) at worklogging.de.
Jira® is a registered trademark of Atlassian Corporation Plc. Worklogging is an independent project and is not affiliated with, endorsed by, or sponsored by Atlassian.