the phone-home register

Ubuntu Insights

What Ubuntu Insights 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

Seen on a machine of ours, in the program's own record of four uploads dated 2026-07-06 (twice), 2026-08-06 and 2026-09-08, read 2026-09-28 with 0.9.3ubuntu installed, and read in its README: a weekly user timer uploads a report to metrics.ubuntu.com, and with consent off that report says only that you opted out; masking its two user timers (ubuntu-insights-collect.timer and ubuntu-insights-upload.timer) with systemctl --user, for each account, stops it, which we set and read back but did not wire-check; a copy of each report it sent stays on your disk.

Builds and versions

the distro's package ubuntu-insights 0.9.3ubuntuOn by default?yes · seen on a machine of ours, and read in its own documentsMeasured here?no · witnessedDate checked (UTC)2026-10-10
Version
0.9.3ubuntu · the Ubuntu 26.04 package
Where the evidence came from
Ubuntu 26.04 desktop, x86-64 (a machine of ours, not a stock install)
On by default?
yes · seen on a machine of ours, and read in its own documents: a report saying you opted out, even with consent off
Measured here?
no · witnessed
Date checked (UTC)
2026-10-10
Why we say so
the program's own upload records on a machine of ours, read 2026-09-28; its README at the package version read 2026-10-10

Each call out

opt out report · 0.9.3ubuntu

Version · build
0.9.3ubuntu · the Ubuntu 26.04 package · Ubuntu 26.04 desktop, x86-64 (a machine of ours, not a stock install) · the distro's package ubuntu-insights 0.9.3ubuntu
Sends by default
yes · seen on a machine of ours, and read in its own documents: a report saying you opted out, even with consent off
Kind
reports
Trigger
on its own
When
A weekly user timer runs the upload. Seen on a machine of ours: the program's own record of four uploads, dated 2026-07-06 (twice), 2026-08-06 and 2026-09-08, read 2026-09-28; and the upload address in the binary (seen on a working network).
Where
OS telemetry · metrics.ubuntu.com
What it sends
a report holding only an opt-out flag ("OptOut": true), when consent is off (consent state)
The vendor's stated purpose
“If consent is not given for a source, an opt-out notification will be sent regardless of the locally cached insights report's contents.” — its README at 0.9.3ubuntu, read 2026-10-10
Grade and method
witnessed · the program's own upload records on a machine of ours, read 2026-09-28; its README at the package version read 2026-10-10 · read 2026-10-10
version at the witness: 0.9.3ubuntu was installed when the records were read on 2026-09-28; the version at each upload date is not recorded here
Receipts
witness extract: the upload records (written at build by script from the private read) · its README at the package version: the opt-out notification · the package

The switch

mask its two user timers

Accepted values
masked
What it is
systemd user timers (ubuntu-insights-collect.timer, ubuntu-insights-upload.timer)
Where it must be set
for each account: systemctl --user mask on both timers · turn them off
Proof
set, read back; not wire-checked
For the call
opt out report · 0.9.3ubuntu

Listens beyond the machine, and other cloud features

Listens beyond the machine by default

  • n/a · a reporting tool (0.9.3ubuntu the Ubuntu 26.04 package)

Other cloud features

None found.

What it leaves on disk

  • .cache/ubuntu-insights/<source>/uploaded/ · a copy of each report it sent

Has it already run on your machine?

Brings in, and installed for you by

None on the register.

Credit

  • Its README documents the opt-out notification, and a copy of every report it sent stays on your disk to read. — git.launchpad.net · README.md, read 2026-10-10

Vendor documents it? · public discussion

Vendor documents it?

  • opt out report · 0.9.3ubuntu: yes · Its README says an opt-out notification is sent when consent is not given, and that uploaded reports are kept in an 'uploaded' folder. · git.launchpad.net · README.md · read 2026-10-10

Public discussion

History

No dated changes yet.

Not yet checked

Nothing named.