Files
OpsLog/wiki/Security.md
T
rouggy 6a28344e93 feat: remove PostHog usage telemetry entirely
Drop the once-a-day anonymous "app_opened" heartbeat to PostHog and everything
around it: telemetry.go (sendTelemetryHeartbeat, GetTelemetryEnabled/
SetTelemetryEnabled, install-ID/last-sent settings keys, PostHog host + API key)
and the startup goroutine that fired it. The 'Send anonymous usage statistics'
toggle is removed from Settings → General (TelemetryToggle + i18n keys), and the
telemetry mentions are stripped from the README and wiki.

appVersion (still used by changelog/update/livestatus/log-email) moves to a new
version.go; release.ps1 now rewrites it there instead of telemetry.go.
2026-07-24 11:52:52 +02:00

776 B

Security

Secret vault

Opt-in passphrase encryption of the stored passwords (QRZ, cluster, eQSL, SMTP, Icom network, etc.) using AES-GCM + PBKDF2.

  • Enable it in Settings; you set a passphrase.
  • Encrypted values are marked enc:v1: and are portable (they travel with the data/ folder).
  • A single unlock prompt at launch decrypts them for the session.

If you forget the passphrase, the encrypted secrets can't be recovered — re-enter them.

What OpsLog sends where

  • Callsign lookups go to QRZ.com / HamQTH with your credentials.
  • QSL uploads/downloads go to the services you configure (LoTW via TQSL, QRZ, eQSL, ClubLog, HRDLog).
  • Everything else stays local (or on your own MySQL / web server for the multi-op live status).