From f55cca4d3b895aa59a31f2470ae13b0cd9838dcf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lauren=C8=9Biu=20Nicola?= Date: Thu, 23 Dec 2021 09:55:39 +0200 Subject: [PATCH] Update privacy note --- PRIVACY.md | 2 +- docs/user/manual.adoc | 4 +++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/PRIVACY.md b/PRIVACY.md index 718fbed120..89e252be73 100644 --- a/PRIVACY.md +++ b/PRIVACY.md @@ -1 +1 @@ -See the [Privacy](https://rust-analyzer.github.io/manual.html#security) section of the user manual. +See the [Privacy](https://rust-analyzer.github.io/manual.html#privacy) section of the user manual. diff --git a/docs/user/manual.adoc b/docs/user/manual.adoc index 1335f8df7c..13165e8d3f 100644 --- a/docs/user/manual.adoc +++ b/docs/user/manual.adoc @@ -653,10 +653,12 @@ Here is a **non-exhaustive** list of ways to make rust-analyzer execute arbitrar The LSP server performs no network access in itself, but runs `cargo metadata` which will update or download the crate registry and the source code of the project dependencies. If enabled (the default), build scripts and procedural macros can do anything. -The Code extension automatically connects to GitHub to download updated LSP binaries and, if the nightly channel is selected, to perform update checks using the GitHub API. For `rust-analyzer` developers, using `cargo xtask release` uses the same API to put together the release notes. +The Code extension does not access the network. Any other editor plugins are not under the control of the `rust-analyzer` developers. For any privacy concerns, you should check with their respective developers. +For `rust-analyzer` developers, `cargo xtask release` uses the GitHub API to put together the release notes. + == Features include::./generated_features.adoc[]