the phone-home register

Qdrant

What Qdrant sends out of your computer by default, when, to whom, and the switch that stops it, version by version, with how we know.

The answer

By its source at v1.19.1 and its usage-statistics page, not run: Qdrant reports anonymized system information, configuration, and timings and counters of parts of its code, with a random instance ID, to telemetry.qdrant.io at start and then every hour; QDRANT__TELEMETRY_DISABLED=true in its environment (or telemetry_disabled: true in its config file, or --disable-telemetry) stops it, and its documents say that does not affect monitoring your own database.

Builds and versions

not installed: source read at tag v1.19.1On by default?yes · read in code and in its own documentsMeasured here?no · read in codeDate checked (UTC)2026-10-10

Version: 1.19.1 · the source at tag v1.19.1
Where the evidence came from: not run: the source applies to every platform
On by default?: yes · read in code and in its own documents
Measured here?: no · read in code
Date checked (UTC): 2026-10-10
Why we say so: src/common/telemetry_reporting.rs, src/settings.rs and config/config.yaml read at tag v1.19.1. The source at the tag; we did not check that the released build matches it.

Each call out

usage statistics · 1.19.1

Version · build: 1.19.1 · the source at tag v1.19.1 · not run: the source applies to every platform · not installed: source read at tag v1.19.1
Sends by default: yes · read in code and in its own documents
Kind: reports
Trigger: on its own
When: The code at v1.19.1 reports at start and then every hour; not run.
Where: vendor telemetry collector · telemetry.qdrant.io
What it sends: anonymized system information, configuration, and timings and counters of parts of the code (usage); a random ID for the instance (identifier)
The vendor's stated purpose: “In order to identify bottlenecks and improve Qdrant, we need to collect information about how it is used.” — Qdrant's documentation, 'Usage statistics', read 2026-10-10
Grade and method: read · src/common/telemetry_reporting.rs, src/settings.rs and config/config.yaml read at tag v1.19.1. The source at the tag; we did not check that the released build matches it. · read 2026-10-10
Receipts: the address and the hourly loop · the reporting loop · the switch, off by default · environment variables with the QDRANT__ prefix · the default bind · its usage-statistics page

The switch

QDRANT__TELEMETRY_DISABLED=true

Accepted values: true
What it is: environment variable
Where it must be set: in the environment of the program, before it starts (see Turn them off) · turn them off
Other spellings: telemetry_disabled: true in its config file, the --disable-telemetry command-line option
What turning it off costs: none known: its documents say turning it off does not affect monitoring your own database
Proof: documented; not tested by us
For the call: usage statistics · 1.19.1

Listens beyond the machine, and other cloud features

Listens beyond the machine by default

every interface · its shipped config/config.yaml at v1.19.1 sets the host to every interface (1.19.1 the source at tag v1.19.1)

Other cloud features

None found.

What it leaves on disk

Nothing we know of.

Brings in, and installed for you by

None on the register.

Credit

Statistics are anonymized and tied to a random instance ID, and its documents say Qdrant Cloud turns them off by default. — qdrant.tech · usage-statistics, read 2026-10-10
Its documents say it never collects your IP address, collection data, collection names or URLs. — qdrant.tech · usage-statistics, read 2026-10-10

Vendor documents it? · public discussion

Vendor documents it?

usage statistics · 1.19.1: yes · Its usage-statistics page says what is collected, how it is anonymized, and three ways to turn it off. · qdrant.tech · usage-statistics · read 2026-10-10