Your software inventory stays on your Mac.

Status: release policy for Chronologix 1.0, last reviewed 5 August 2026 and bound to the exact public binary.

Data kept locally

Chronologix reads approved application and package locations to identify installed software, versions, paths, receipts, architecture, and relevant signing observations. Inventory, scan history, reviewed plans, update results, preferences, and bounded metadata caches remain on the Mac.

When network requests happen

A normal local scan sends nothing. Network access starts only from an explicit check or a separately reviewed update action:

• enabled Homebrew metadata checks request one exact public formulae.brew.sh path per eligible token;
• the exact Firefox adapter requests fixed Mozilla version and checksum paths; its DMG request occurs only after plan review and explicit installation;
• self-update checks use the production HTTPS appcast and validate Sparkle Ed25519 signatures before installation.

Remote services normally observe IP, DNS, TLS, timing, and response-size metadata. Chronologix does not intentionally send local application paths, usernames, credentials, receipt bodies, the full inventory, analytics identifiers, or a stable device identifier in those requests.

Diagnostics and notifications

Diagnostic export is explicit, previewed, aggregate-only, redacted, and capped. Chronologix does not upload it automatically. Local notifications remain anonymous, bounded, and under the user’s control.

Control and retention

Users can disable future source traffic, clear metadata caches, clear local history, cancel pending reminders, and delete the application. Active recovery records may remain only while needed to complete or safely recover a direct update.

What is absent

No advertising, third-party analytics, tracking pixels, cross-site profiling, cloud inventory, account system, or sale of data exists in Chronologix 1.0.