Data and statistics

Backup advice and details of optional AI features and usage statistics.

Backups

All software can contain errors. Keep regular external backups and do not use one device as the only copy of important records.

To the extent permitted by law, we provide no warranty for data security and accept no liability for data loss. This does not limit liability that cannot legally be excluded, including liability for intentional misconduct, gross negligence or injury to life, body or health. Mandatory statutory rights remain unaffected.

Optional AI features

When you choose OpenAI in Settings → AI and start an AI action, your input text, prompt and selected sources, including visible time boundaries and project, tag and person references, are sent directly to OpenAI using your API key. Audio stays on your Mac. The key is stored in the macOS Keychain and excluded from worklog backups. This website does not receive these AI requests. The Local to this Mac option processes text on your Mac after its model download. LumeWorklog does not switch providers automatically.

Optional app statistics

Technical usage statistics are enabled by default for new installations. Your saved choice is preserved. You can turn them off at any time in LumeWorklog → About LumeWorklog, without restricting any app feature. These events help count testing installations, app starts, versions and active use.

No worklog entries, titles, notes, projects, people references, calendar content or reports are transmitted by app statistics. We do not send your name, email, Mac account, device name, serial number or advertising ID.

Events go only to lumeworklog.com. They are stored for up to 90 days. A small local queue retries failed requests; switching statistics off clears unsent events. To request deletion of already received events, contact us with the selectable installation ID shown in About. Your IP address is necessarily visible to the hosting server during the connection; it is not included in the app event record. Hosting access logs are separate. The operator may separately receive one Pushover notification for a new app session reported through Spark Statistics, containing only a fixed app-start category and app version/build. This does not reveal your worklog data, installation UUID or alias. Counted download requests may additionally trigger one notification with only a fixed download category and the app build number, without confirming a completed transfer. Optional app-event statistics do not trigger notifications.

Website notifications

Each recorded public LumeWorklog pageview may also send the operator one Pushover notification containing only the known page path and server receipt time in UTC. Reloads and returns from the browser history cache count as new views; repeated reports of the same view do not. No IP address, referrer, browser/device details or event ID is included. Do Not Track and Global Privacy Control remain respected. Network failures or blocked scripts can prevent a notification.

An example call

These UUIDs are fictional. This illustrates the first-launch callback; it is not a request you need to run.

POST https://lumeworklog.com/api.php?action=app-event
Content-Type: application/json

{
  "schema": 1,
  "event_id": "31c1b92a-48a3-4c51-8c58-29454c5e0460",
  "installation_id": "73594684-a9a1-4b48-853c-bd86b5db3029",
  "session_id": "5b19ef6c-27a8-4d0a-9966-352910ae87e1",
  "event": "install",
  "version": "0.8.6",
  "build": "53",
  "active_seconds": 0
}

Later events use "event": "launch" or "event": "usage". For example, a usage event with "active_seconds": 60 means one minute in the foreground. The API rejects additional fields.

Downloads & release notes ↗

Questions or feedback? me@wolfgangvieregg.com