Nextcloud Desktop 3.16.7 — the first minute without a single click
How we tested: a clean Debian 13 in a disposable container; source — package nextcloud-desktop 3.16.7-1~deb13u1 from the Debian repository. Run as a regular user on a virtual screen, 60 seconds, nothing clicked. 17.10.2026. Every network request and every file written was recorded; the code was not decompiled. The container was deleted afterwards.
Program website: https://nextcloud.com/install/#install-clients
Package SHA-256: 897989a4f1dc8c9502e03ef7339fc55f95e0f71a6d94c3021fe0f7df199d430a
Summary
| What we checked | Result |
|---|---|
| Built-in telemetry, crash reporting, analytics, ad SDKs | none |
| Network requests in the first minute | not a single network request |
| Known trackers among the servers | none |
| Files written in the first minute | 162 |
| The program ran the whole time | yes — process alive at the end |
What is built in
264 files (19 MB) were checked.
No code of known telemetry, crash reporting, analytics or ad SDKs was found.
Where it connected
Not a single request: no DNS lookup, no connection.
What it wrote to disk
Folders the program wrote files to during the minute:
| Folder | Files |
|---|---|
~/.cache/mesa_shader_cache_db | 102 |
~/.cache/Nextcloud | 49 |
~/.cache/qtshadercache-x86_64-little_endian-lp64 | 6 |
~/.config/Nextcloud | 4 |
~/.config/autostart | 1 |
How to read this card
- This is the first minute after launch with no action at all: what the program does on its own. Normal use may involve more requests.
- A “built-in SDK” means the library’s code was found. It does not prove data transfer, and an address in the code is not a request.
- The review was made automatically using a single method. You can check any program yourself here.