Exodus-Privacy
updating two network rules
Not sure if this is the right place. I found these two network rules. They seem to be non valid regex?
\appnext.com \display.io
Further I suggest adding these trackers, though I don't know if they apply to Android as well:
app-measurement.com ioam.de userreport.com
Hi @relikd and thanks raising this!
I updated the 2 network rules. For the later ones, do you have more details?
If you want and have the time, feel free to ask for an account on ETIP and make the changes/creation directly ;) https://github.com/Exodus-Privacy/etip#contribute-to-the-identification-of-trackers
Not really more than you could extract from the respective websites. I don't even know if there is a corresponding code signature. I found this project when searching for a pulic list of known mobile trackers. And it seems "Easylist" and "Peter Lowe’s tracking server list" lack many of the mobile platform trackers.
I am in the midst of building a similar platform to exodus but for iOS applications (runtime analysis instead of code analysis). https://github.com/relikd/AppCheck
Ideally the ETIP json file could provide a list of domains per tracker (additional to the network rule). That way you could use the domains for plain DNS based blocking. Currently this affects the network rule \.exacttarget\. which can't be translated directly into matching domains.
Adding to this here are the first results of my study – and again this may not apply to Android. Also, the results are very limited as there are only 140 recorded apps so far but the tendency is very clear. I think most of the tracking domains are already in exodus but the remaining domains appear in a variety of (iOS) apps. E.g., the mentioned app-measurement.com appears in over 50 % of the tested apps. It could very well be that this is an iOS specific tracker.