Worklog LitePrivacy policy
Updated 31 October 2026. The iOS ATT provisions apply to the release that introduces the system tracking prompt.
In short. The developer of Worklog Lite does not run an intermediary server for Jira data. The app connects directly to your Jira and keeps working copies of entries, issues and reports only in memory while running. It saves your chosen language locally and, if you request it, your sign-in details. CSV exports and data copied to the clipboard may remain after the app closes. Google’s mobile modules and the store operators process the data described in sections 3–4; the promise about Jira working data does not mean these modules have no storage.
1. Developer and contact
Worklog Lite for Jira (“the app”) is made by Konrad Witkowski. Contact for all privacy matters: witkompapp@gmail.com.
The developer does not receive sign-in details, issues, entries or reports exchanged between the app and your Jira. Your chosen interface language is not sent to the developer. Advertising modules and stores operate as described below. If you email the contact address, the developer receives your message and sender details in order to reply.
2. Data that stays on your device
| Data | Where and for how long |
|---|---|
| Jira address, email and token | In the app's memory until you close it. If you check “Remember on this device”, in the system keychain; on Android, in a private file encrypted with AES-GCM using an Android Keystore key and excluded from backups. Signing out does not delete them. “Remove saved sign-in details” deletes the saved credentials and, on Android, the encryption key. |
| Time entries, issues, reports | Working copies are kept only in memory while the app runs, with no app database or persistent disk cache. Closing the app does not delete data saved in Jira itself. |
| Interface language | After you change the language manually, only its code (e.g. en) is saved in the app’s local storage until you change it again or clear the app’s data. With no saved choice, the app uses the system language, or English if that language is not supported. |
| Light or dark theme | Follows the current system settings. The app does not save a separate theme preference. |
| CSV export | A file created when you choose to export: in a location you select on a computer, or in the app’s Documents folder on a phone or tablet. It remains after the app closes until you delete or replace it. |
| Clipboard | Choosing “Copy table” places the report on the system clipboard. Closing the app does not clear it; retention and any synchronisation depend on system settings. |
Connections to Jira go directly from your device to the address you enter, with your permissions. The author of the app has no access to this data and does not receive it.
3. Ads in the iPhone, iPad and Android version
The free mobile version shows one bar with an ad served by Google AdMob. In the European Economic Area and Switzerland the service is provided by Google Ireland Limited, elsewhere by Google LLC. Google processes ad data as an independent controller under the Google Privacy Policy. How Google uses data from partner apps: policies.google.com/technologies/partner-sites.
Google’s UMP consent module remembers privacy choices. The ads module may store technical data and cached ads on the device. This is separate from the language preference and Jira working data. The macOS, Windows and Linux versions do not have these ads.
What Google receives
- the IP address, which can be used to estimate an approximate location (city or region),
- device and system information, such as the model, system version, language and time zone,
- identifiers tied to the app on the device (such as the identifier for vendor on iOS or the app set ID on Android),
- ad information: which ads were shown and whether they were tapped,
- diagnostic data from the ads module, such as launch time and errors,
- the address of the page describing the app, which Google uses to match ads to its topic.
What Google does not receive
- anything from your Jira: its address, sign-in details, issues, entries or reports,
- the Google advertising identifier on Android: the app does not have the permission required to access it.
On iPhone and iPad, Google may also receive the advertising identifier (IDFA) if you allow tracking in Apple’s App Tracking Transparency (ATT) prompt. This is separate from Google’s regional consent form.
Consent
On iPhone and iPad, the app resolves ATT before requesting Google consent and starting ads. The system prompt appears after entering demo mode or connecting to Jira, if you have not already made an ATT choice and do not own “Remove ads”. Tracking is enabled only with ATT authorization and any required Google consent. If ATT is denied or restricted, the app disables ad personalisation, requests non-personalised ads and does not access IDFA. Google’s publisher first-party identifier is disabled. If ATT is unresolved or Google does not permit ad requests, no ads are requested. Refusing either permission does not block demo mode or Jira features. You can change ATT in iOS Settings; returning to the app rechecks the decision.
In the EEA, the United Kingdom and Switzerland, the app uses Google’s consent form when the consent module determines it is required. Your choices affect the available ad mode and use of data. Refusing consent may limit ads or prevent them from loading. Limited ads do not use data for personalisation, but may still use technical storage and, depending on Google’s configuration, storage for fraud detection. See Google’s limited ads documentation. You can change or withdraw required consent using “Ad privacy settings” in the “Remove ads” window or at the bottom of the sign-in and main screens (also available after purchase) when Google makes that option available. Processing based on consent relies on Article 6(1)(a) GDPR.
4. The “Remove ads” purchase
Apple (App Store) or Google (Google Play) handles the purchase under its own terms and privacy policies. The developer does not receive card or billing details. The app obtains the price and purchase status from the store. It does not create its own persistent purchase database; the store system may keep transactions and their status on the device. Once a purchase or restoration is confirmed, both bars disappear and the app stops requesting further ads. When a purchase is recognised at launch, the app does not start the Google ads module.
After two consecutive failed ad loads, the app may show its own “Go ad-free” bar with the store price, or “Explore the ad-free option” if no price is available. It opens the existing purchase window. The app sends no separate impression or click analytics for this bar; price lookup and purchase use the store’s services.
5. Who receives data
Sign-in details and operations on issues and time entries go to the Jira instance you specify and are processed under its operator’s rules. Ad data goes to Google (section 3), and data needed for a purchase goes to Apple or Google as the store operator (section 4). The developer does not sell Jira data or receive copies of it. Google may process data outside the EEA with the safeguards described in its privacy policy.
6. Your rights
You have the right to access, rectify and erase your data, to restrict its processing and to data portability, the right to object, and the right to withdraw consent without affecting earlier processing. You can also lodge a complaint with a data protection authority, in Poland the President of the Personal Data Protection Office (uodo.gov.pl), or the authority in your country.
For data saved in Jira, contact its administrator; for ad data, contact Google (myaccount.google.com). Delete local sign-in details with “Remove saved sign-in details”; change the language in the app, and manage CSV files and the clipboard using system tools. For questions or correspondence with the developer, email witkompapp@gmail.com.
7. Children
The app is a work tool and is not directed at children. Ad requests are not marked as child-directed.
8. Changes
Changes to this policy will appear on this page together with a new effective date. Significant changes will also be mentioned in the app's update notes in the store.