summaryrefslogtreecommitdiff
path: root/doc/faq.asciidoc
diff options
context:
space:
mode:
authorFlorian Bruhin <me@the-compiler.org>2021-02-10 12:34:02 +0100
committerFlorian Bruhin <me@the-compiler.org>2021-02-10 16:13:22 +0100
commit439c5b14ea80c4728a967e3f0152f28b9fede4f6 (patch)
tree736352fd8de007722d69aec9da1ff06fcadeb5b3 /doc/faq.asciidoc
parent78b0e8c6a1b22f94553afc61adfa71e1055b1352 (diff)
downloadqutebrowser-439c5b14ea80c4728a967e3f0152f28b9fede4f6.tar.gz
qutebrowser-439c5b14ea80c4728a967e3f0152f28b9fede4f6.zip
Update privacy policy
Only I have access to crash reports now
Diffstat (limited to 'doc/faq.asciidoc')
-rw-r--r--doc/faq.asciidoc7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/faq.asciidoc b/doc/faq.asciidoc
index 4343ad61f..83268fe00 100644
--- a/doc/faq.asciidoc
+++ b/doc/faq.asciidoc
@@ -522,8 +522,11 @@ privacy policies.
When qutebrowser crashes or you use the `:report` command, you have the
possibility to send a crash report. If you decide to do so, your crash report
-is stored on qutebrowser's server, where core qutebrowser developers (four
-people at the time of writing) can access it.
+is stored on qutebrowser's server, where qutebrowser's maintainer (Florian Bruhin / The
+Compiler) can access it. Before February 2021, other core qutebrowser developers (a
+maximum of four people total) could access the reports as well (access was restricted
+based on the sensitive nature of those reports, not because of any known issues with
+those individuals).
If you select the option to include a debug log with your report, it's possible
that sensitive information is contained in your report. You can show and edit