[Privacy] PRIVACY.md summary says only data you explicitly send leaves the device #603

New issue

Closed

opened 2026-07-22 16:19:50 +00:00 by brenno · 0 comments

brenno commented

2026-07-22 16:19:50 +00:00

Owner

Found in the pre-publication privacy review.

Evidence: docs/PRIVACY.md:14-16 — "The only data that leaves your device is data you explicitly send — by importing from a URL, saving to your own Nextcloud/git server, or turning on the AI assistant."

One hundred and seventy lines further down, docs/PRIVACY.md:183 says the fetch-proxy "is used automatically, without a separate prompt". The table at :161-172 has ten rows, not three. The same file already corrected this once at :197-199, for the table — but not for the summary above it.

Why this matters now: the summary is the paragraph most readers actually read, and it is demonstrably wrong for the one path where the user gets no choice. A reader who finds the correction note at :197 concludes the error was left standing exactly where it counts most. That costs the whole document its credibility — and this document is the strongest selling point the product has.

Proposal: extend the third bullet: "…plus three you do not choose yourself: the CORS fallback on the web build, the CVE mirror if you switch it on, and a YouTube or Vimeo embed. The table below is complete."

Found in the pre-publication privacy review. **Evidence:** `docs/PRIVACY.md:14-16` — "**The only data that leaves your device is data you explicitly send** — by importing from a URL, saving to your own Nextcloud/git server, or turning on the AI assistant." One hundred and seventy lines further down, `docs/PRIVACY.md:183` says the fetch-proxy "is used automatically, **without a separate prompt**". The table at `:161-172` has ten rows, not three. The same file already corrected this once at `:197-199`, for the table — but not for the summary above it. **Why this matters now:** the summary is the paragraph most readers actually read, and it is demonstrably wrong for the one path where the user gets no choice. A reader who finds the correction note at `:197` concludes the error was left standing exactly where it counts most. That costs the whole document its credibility — and this document is the strongest selling point the product has. **Proposal:** extend the third bullet: "…plus three you do not choose yourself: the CORS fallback on the web build, the CVE mirror if you switch it on, and a YouTube or Vimeo embed. The table below is complete."

brenno added the

privacy

docs

labels

2026-07-22 16:19:50 +00:00

brenno referenced this issue from a commit

2026-07-22 17:01:56 +00:00

docs(privacy): breng vier beloftes terug naar wat de code doet

brenno referenced this issue from a pull request that will close it,

2026-07-22 17:02:16 +00:00

docs(privacy): breng vier beloftes terug naar wat de code doet (#603, #628, #643, #644) #653

brenno closed this issue