GrapheneOS -- 1d nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6w x As an example, a bank's services are privacy invasive because they track all of your payments and everything else they can see. They often provide a lot of the data to third parties including selling it. Whether or not their app uses client side analytics and telemetry connecting to a few domains dedicated to that which are considered trackers doesn't matter much. It's the difference between extremely privacy invasive vs. surface level things which tend to not matter much. reply [1 reply]nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6wx As an example, a bank's services are privacy invasive because they track all of your payments and everything else they can see. They often provide a lot of the data to third parties including selling it. Whether or not their app uses client side analytics and telemetry connecting to a few domains dedicated to that which are considered trackers doesn't matter much. It's the difference between extremely privacy invasive vs. surface level things which tend to not matter much.
thread · root 935995d9…de3a · depth 2 · · selected fb56aa96…4e2e
thread
root 935995d9…de3a · depth 2 · · selected fb56aa96…4e2e
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6wx You should figure out what's actually making the requests which are being identified that way. It could befrom web browsing where EasyList + EasyPrivacy don't block those because it would break functionality butanother list being used to evaluate the requests considers them trackers. In general, it's not going to considerthe most privacy invasive requests made to an app's own servers to be trackers because it's used for thefunctionality so it doesn't mean much at all.
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6wx As an example, a bank's services are privacy invasive because they track all of your payments and everythingelse they can see. They often provide a lot of the data to third parties including selling it. Whether or nottheir app uses client side analytics and telemetry connecting to a few domains dedicated to that which areconsidered trackers doesn't matter much. It's the difference between extremely privacy invasive vs. surfacelevel things which tend to not matter much.
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6wx You should figure out what's actually making the requests which are being identified that way. It could be from web browsing where EasyList + EasyPrivacy don't block those because it would break functionality but another list being used to evaluate the requests considers them trackers. In general, it's not going to consider the most privacy invasive requests made to an app's own servers to be trackers because it's used for the functionality so it doesn't mean much at all.
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqls4psr089gsp9hpd4as2srxqjc00d42d2ud4xug8w4eym0sl7c0s9cs6wx As another example, consider a camera app with filters which uploads every picture and video to their servers to do the processing on their cloud vs. one which does everything locally and doesn't send user data anywhere but includes a crash reporting system and basic analytics to know how much features get used. The one with the crash reporting system and analytics will be classified as having 2 'trackers' vs. the very privacy invasive one sending off your sensitive data with 0.