Disable Google Safe Browsing in WebViews #13743
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By default, Google Safe Browsing is enabled in WebView objects; see https://developer.android.com/develop/ui/views/layout/webapps/managing-webview#safe-browsing. Safe Browsing requires sending any URLs loaded in WebViews to Google to check for malicious contents. As the WebView URLs loaded are generally either Signal websites or reputable payment providers for donations, the potential security benefits of Google scanning for phishing websites outweigh the privacy issues of sending this information to Google.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First time contributor checklist
Contributor checklist
Fixes #1234syntaxDescription
By default, Google Safe Browsing is enabled in WebView objects; see https://developer.android.com/develop/ui/views/layout/webapps/managing-webview#safe-browsing. Safe Browsing requires sending any URLs loaded in WebViews to Google to check for malicious contents. As the WebView URLs loaded are generally either Signal websites or reputable payment providers for donations, the potential security benefits of Google scanning for phishing websites do not outweigh the privacy issues of sending this information to Google.