the phone-home register
pyannote.audio
What pyannote.audio 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
Per its README and the telemetry config shipped in the package at tag 4.0.7, not run: when a pipeline or model is loaded, pyannote.audio sends usage metrics to otel.pyannote.ai naming where the pipeline came from (an official pyannote name, 'huggingface' or 'local') and its Python class, and for each file it processes the file's duration and the speaker-count settings, the shipped config turning this on by default; PYANNOTE_METRICS_ENABLED=0, set before the program starts (or set_telemetry_metrics in Python), stops it.
Builds and versions
not installed: source read at tag 4.0.7On by default?yes · read in its shipped config and its own documentsMeasured here?no · read in codeDate checked (UTC)2026-10-10
- Version
- 4.0.7 · the source at tag 4.0.7
- Where the evidence came from
- not run: the source applies to every platform
- On by default?
- yes · read in its shipped config and its own documents
- Measured here?
- no · read in code
- Date checked (UTC)
- 2026-10-10
- Why we say so
- the telemetry config shipped in the package and the README's Telemetry section read at tag 4.0.7; the sending code was not enumerated
Each call out
pipeline metrics · 4.0.7
- Version · build
- 4.0.7 · the source at tag 4.0.7 · not run: the source applies to every platform · not installed: source read at tag 4.0.7
- Sends by default
- yes · read in its shipped config and its own documents
- Kind
- reports
- Trigger
- as a side effect of a local request
- When
- Per its README and its shipped config at 4.0.7: when a pipeline is loaded and for each file it processes; not run.
- Where
- vendor telemetry collector · otel.pyannote.ai
- What it sends
- where the pipeline came from (an official pyannote name, 'huggingface', or 'local') and its Python class (usage); each file's duration and the speaker-count settings (usage)
- The vendor's stated purpose
- “With the optional telemetry feature in `pyannote.audio`, you can choose to send anonymous usage metrics to help the `pyannote` team improve the library.” — its README at tag 4.0.7, the Telemetry section's opening sentence (line 114); the shipped config (src/pyannote/audio/telemetry/config.yaml, line 1) sets metrics_enabled: true, read 2026-10-11
- Grade and method
- read · the telemetry config shipped in the package and the README's Telemetry section read at tag 4.0.7; the sending code was not enumerated · read 2026-10-10
- Receipts
- the shipped config: metrics on, and the endpoint · the README's Telemetry section
The switch
PYANNOTE_METRICS_ENABLED=0
- Accepted values
- 0
- 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
- set_telemetry_metrics in Python, for the session or across sessions
- Proof
- documented; not tested by us
- For the call
- pipeline metrics · 4.0.7
Listens beyond the machine, and other cloud features
Listens beyond the machine by default
- n/a · a library (4.0.7 the source at tag 4.0.7)
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
- The README lists exactly what is tracked and three ways to set the switch. — github.com · README.md, read 2026-10-10
Vendor documents it? · public discussion
Vendor documents it?
- pipeline metrics · 4.0.7: yes · Its README lists what is tracked, the switch, and that the default comes from the shipped telemetry config. · github.com · README.md · read 2026-10-10
Public discussion
History
No dated changes yet.
Not yet checked
Nothing named.