From 70418dcb259084be10240488d523f0c68278e6c8 Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Sat, 6 May 2023 15:22:21 -0400 Subject: [PATCH] improve default connections introduction --- static/faq.html | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/static/faq.html b/static/faq.html index 565aa1a6..4f520b9c 100644 --- a/static/faq.html +++ b/static/faq.html @@ -767,11 +767,17 @@

What kind of connections do the OS and bundled apps make by default?

-

GrapheneOS makes connections to the outside world to test connectivity, - detect captive portals and download updates. No data varying per user / - installation / device is sent in these connections. There aren't analytics / - telemetry in GrapheneOS. By default, remote connections are only made to - GrapheneOS services and the network provided DNS resolvers.

+

By default, GrapheneOS only makes remote connections to GrapheneOS services + and the network provided DNS resolvers. There aren't any analytics/telemetry + in GrapheneOS. None of the default connections sends any data varying based on + the user, installation or specific device. The only information revealed to + the GrapheneOS servers are the generic device model (such as Pixel 7 Pro) and + OS version which are necessary for obtaining updates. The default connections + provide the OS and apps with updates, set the system clock, check each network + connection for internet connectivity, download a global database (does not + vary based on location) with predicted satellite locations when using Location + and obtain attestation chain signing keys for the hardware keystore needed for + the hardware-based attestation feature.

Make sure to read the other connections section below this one too which covers non-default connections triggered by