DDG and /e/ browser webview fingerprint

Hi,

If i use /e/ browser for general browsing without logging in into anything and i use DDG for accessing certain accounts obviously the DDG browser will be fingerprinted by trackers. I read somewhere that DDG uses the system webview and is not a standalone browser. My question is will this setup deanonamyze my /e/ browser fingerprint through the webview or something (leave aside IP and other factors). If i save cookies for login into DDG will this be connected to my browsing history on /e/ browser?

Thanks

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online servicesphone

First: I am no expert on this, so please do not blindly trust what I write here.

Edit: The following is probably wrong, see next comment.
As I understand, WebView offers a direct connection to a rendering engine. That’s the thing that actually turns that data a browser receives into something on your screen. It does not do all the data fetching, authentification, encryption and stuff.
Therefore, the two browsers should not be directly linked.

However, fingerprinting may also take other stuff into account to identify the device, not the Browser.

Generally, I advise against using the /e/-Browser. It is a security risk, because it’s updated only occasionally so oftentimes has several security vulnerabilities. You are better off with upstream Bromite (where /e/-Browser is forked from) or another regularly updated Privacy centric Browser (You can find a lot of discussion around this also in this forum)

DuckDuckGo Browser on Android does not have fingerprinting protection.

See these tables:

@ljahn

As I understand, WebView offers a direct connection to a rendering engine.

The WebView handles basically everything and the actual WebView API is quite limited in what can be changed.
For example WebView browsers cannot disable WebGL to prevent fingerprinting via it unless they completely disable JavaScript.

2 Likes

Fingerprinting cannot be beaten in a single browser no matter which one it is. That is why i am using 2 browsers.

Brave “creates” random fingerprints. link So no need for 2 browsers if you ask me.

@andrelam
Brave’s anti-fingerprinting is to randomize everything every time. ie. make everyone always look different
Firefox’s anti-fingerprinting (when configured or as done by Tor) is to group as many users as possible into the same buckets. ie. make everyone look the same

They’re opposites and are both arguable on their merits.