On one of my Pixel devices, I’m signed into my Google account. The phone isn’t connected to a cellular network and only connects to a WiFi network with a VPN on. I’m using NextDNS and various blocklists. I have configured Brave using PG’s guide. I’m not signed into Google with Brave. I typically don’t use Brave for YouTube, but I just decided to give it a shot. Wow. Some of the recommendations that I’m seeing is causing me to be paranoid. I’m seeing recommendations that are related to what I was searching for on Brave. Google’s data collection power and ability to profile me is probably second to none. I’m probably losing this war.
1 Like
Are you using GrapheneOS?
2 Likes
Not on this Pixel.
1 Like
install it on this device and use google services and everything related to google on a separate user profile
3 Likes
What search engine are you using? Brave search on Brave browser?
Im guessing there was some third party cookies configured to be shared in the browser
1 Like
I know, but I guess my point is that even with PG’s guides and using what the privacy community suggests, Google still seems to know something about me.
1 Like
I’m using Google Search in Brave’s browser with third-party cookies blocked and trackers set to strict.
2 Likes
Oh, yeah that’s probably the leak. Cookies on Google Search fingerprinted you more finely than Brave could mitigate, & fed data to YouTube for ads. Since YouTube is Google, they’re probably able to share some data
This was not the question you asked. I just like to yap. Thanks for coming to my Ted Talk
4 Likes
Try resetting the ad ID in your account settings.
2 Likes
Sure, if you voluntarily hand it over to them.
3 Likes
I understand that they are already collecting a large amount of unique device data even if accounts are not activated, according to this link. For some reason, in these support articles, they always share some of the data they collect, their purposes, and some of the things they do, they never say everything.
Device & account identifiers
Examples of data
- IMEI, MEID, and ESN numbers
- Device serial number
- Google Services Framework Android ID (or “Android ID”) Note: This is different than the Settings Secure Android ID.
- Google Account (when it’s activated) [1]
- MAC addresses
How Google uses the data
To protect your account, we use device identifiers to help us detect suspicious sign-in behavior.
Device attributes
Examples of data
- Hardware type
- Product
- Model
- Manufacturer
- Supported native platforms / CPU types
- Keyboard, navigation, & screen layout types
- Screen size (height & width in pixels)
- Total memory
- Locale
- Time zone
How Google uses the data
Google Play may use attributes like screen layout to ensure you’re offered compatible software versions.
…
If more than one account is signed in to a single device, Google Account information may not be provided in the data download. ↩︎
2 Likes
Well the OP is also not using GrapheneOS on their specific Pixel either, assuming it is supported on the device, but that has already been discussed earlier in the topic. There are also various Google-dependent practices that can be swapped for alternative solutions and/or dropped entirely.
4 Likes
I did that a long time ago.
1 Like
It does feel like that, knowing what I know right now. I think the problem lies in me signing into my Google account. I’m also assuming Android isn’t as good at preventing cross-app tracking as iOS.
1 Like
but I guess my point is that even with PG’s guides and using what the privacy community suggests
I’m also assuming Android isn’t as good at preventing cross-app tracking as iOS.
PG literally recommends only GrapheneOS for a reason and you have a Pixel device. Only way to escape Google from its own device is using GrapheneOS (or the new OEM soon with GrapheneOS too).
6 Likes
Yes, deal with one issue at a time. As you continue to achieve success with adjusting your behavioural practices, your momentum will snowball and tackling greater challenges becomes feasible. The hardest step in any journey is starting the first one.
3 Likes