I use telemetry to understand how BrickTracker gets used across installations: how many exist, which versions people run, and which pages get visited. That's what tells me where to spend development time.

What is send

• A random anonymous ID for this installation, not tied to your hardware, network, or username
• BrickTracker version and database schema version
• Which optional features you have turned on (e.g. BrickData/sidecar, client- or server-side pagination)
• Which pages you visit, by name only (e.g. "Statistics", "Sets")
• Aggregate collection counts (e.g. total sets, total missing parts)

What is never send

• Set, part, or minifigure names, numbers, or IDs
• Your wishlist contents, filenames, or search queries
• Usernames, passwords, API keys, or any Rebrickable credentials
• Your IP address (anonymized)

Data goes to a self-hosted Matomo instance, not Google Analytics or any other third party.

Telemetry is off by default and fully optional. You can turn it off any time in Admin → Static Settings (a restart is needed for that change to take effect). The code deciding what gets sent lives in bricktracker/telemetry.py, open source and auditable.