Anonymous usage statistics
What a Deplo instance reports once a day, how to see it, and how to turn it off.
Deplo sends one anonymous Usage report a day to a service Deplo runs itself: versions, counts and feature switches, nothing that names the instance, its servers, its people or its apps.
The switch is Anonymous usage statistics, on Settings -> Deplo -> Advanced, under Privacy. It is on by default, and any instance admin can turn it off.
What is sent
See what would be sent on that card shows the exact document your instance would send now, built by the same code that sends it.
| Field | What it holds |
|---|---|
schema | The version of this list. Adding a field never bumps it; renaming or removing one does |
instanceId | A random id, minted on the first send. Turning the switch off deletes it; turning it back on mints a new one, so the old history can't be joined to the new |
deploVersion | The Deplo version this instance runs |
expectedAgentVersion | The server agent version this Deplo expects on its servers |
installKind | plain, or the platform Deplo took over from when the install was a migration |
daysSinceFirstReport | Whole days since the current id was minted |
hosts | One entry per server, at most 500: agent version, Docker version, CPU architecture, and whether it is the Deplo host, a build server, or import-only |
counts | Teams, users, servers, environments, previews and backup schedules, plus apps by source kind, databases by engine and backup destinations by kind |
features | Six switches: MCP in use, a two-factor policy on any team or role, any passkey, any git provider connected, any notification channel, Gravatar on |
Never in a report: a hostname, an IP address, a domain, an email address, a username, an app name, a repository URL, a template name, an error message or a stack trace.
Security updates send something else, to another place: the name and version of each package your images contain.
When it is sent
- Once a day at most. The maintenance sweep, every 12 hours, sends a report when the last one is more than 24 hours old. The service also keeps one report per instance id per 24 hours.
- Never before setup is done. The setup wizard says so on its last step, and nothing leaves until the instance has an owner.
- Never from a development build.
- A failed send waits for the next sweep. One line in the log, no retry loop.
The report goes to https://usage.deplo.build/v1/report and nowhere else. The address is fixed, so
blocking it at your firewall stops reports without touching templates or updates.
Turn it off
Turn off Anonymous usage statistics (Settings -> Deplo -> Advanced). It takes effect at once: nothing more is sent, not even a final message, and the instance id is deleted. Activity records the change. A team seat can't change it, only an instance admin.
For a whole install
Set the standard DO_NOT_TRACK=1 in Deplo's environment. The card then shows the switch disabled with
Turned off by the install. There is no Deplo-specific variable.
What Deplo keeps
- The report and the time it arrived. Never the sender's address: the per-address limits live in memory and are forgotten on restart.
- Raw reports for 90 days. Daily aggregates for good, and only those feed the dashboard. There is no per-instance view.
Ask for erasure
Open See what would be sent and copy the Instance id under the report. Quote it in an issue on our GitHub and every report under that id is deleted. The id is random and names nothing, so posting it gives nothing away.
Did this page help you?