#datasegregation

0 post0 partecipanti0 post oggi

ctrg195"Fitbit will delete data if you don’t migrate to Google Account by 2026"draft - Can they keep an email and password login option? An issue with strictly Google account SSO is that it doesn't play nicely with a multiple users setup. For example, some folks, me included, have a default user logged into their "default" Google account. But then we also have an alt user where we login to our alt Google account. The idea being data segregation, especially for things like Google photos which could potentially risk cross account data contamination. Anyways, while it's fine to login with Google when in the default space, when we login to our alt user space, the whole idea is to not be logged into our "default" Google account while logged into our "alt" user space. They have sort of solved the issue a bit with private space. It works great in the default user, so when we're in the default user, we can unlock private space and access our alt Google account without having to log out of the default space. Can they please bring private space to more than just the default user? Then, when logged into a second user, we could unlock private space and have that be logged into the default user, without having to worry about cross-account data contamination. We could then also use Fitbit. Another kinda maybe simpler option is that Fitbit could also add support for login with Microsoft, since, microsoft is a non-google entity, you don't have to worry about all the Google apps syncing data. Another option would be to just keep email and password login. The same thing goes for the nest app, Google chat, Gemini, and any other apps and services which only support login with google. Thank you. <a href="https://9to5google.com/2025/03/28/fitbit-google-account-2026/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://9to5google.com/2025/03/28/fitbit-google-account-2026/</a><a href="https://infosec.exchange/tags/datasegregation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#datasegregation</a> <a href="https://infosec.exchange/tags/loginwithgoogle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#loginwithgoogle</a> <a href="https://infosec.exchange/tags/loginwithmicrosoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#loginwithmicrosoft</a> <a href="https://infosec.exchange/tags/sso" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sso</a> <a href="https://infosec.exchange/tags/multipleusers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multipleusers</a> <a href="https://infosec.exchange/tags/2usersetup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#2usersetup</a> <a href="https://infosec.exchange/tags/privatespace" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privatespace</a> <a href="https://infosec.exchange/tags/android16" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#android16</a> <a href="https://infosec.exchange/tags/googlechat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#googlechat</a> <a href="https://infosec.exchange/tags/gemini" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gemini</a> <a href="https://infosec.exchange/tags/android15" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#android15</a> <a href="https://infosec.exchange/tags/pixel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pixel</a> <a href="https://infosec.exchange/tags/pixel8" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pixel8</a> <a href="https://infosec.exchange/tags/pixel9" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pixel9</a> <a href="https://infosec.exchange/tags/pixel9pro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pixel9pro</a>

ctrg195draft - Google Photos - Could we also get an option something to the effect of like:"disable this Google Photos Account on this device." or something to that effect, so when you select that specific Google account in Google photos it would just display a big lock icon and say something like "this account is disabled on this device. If you would like to enable it, you may do so in settings" or something to that effect.<a href="https://infosec.exchange/tags/googlephotos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#googlephotos</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/datasegregation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#datasegregation</a> edit - private space on android kind of solves the issue in the default user space, but for those of us who make a dedicated alt user for ourselves, in addition to using private space to access *some* of the alt profile when logged into the default user, when we log out of the default user and into one of our alt users logged into our alt google account, there's no way to setup private space in another user. on pixel, private space works great in the default user. but it would really seal the deal if they would bring the ability to setup private space when logged into a second user. even if they don't want to bring it to more than 2 users, 2 users would be better than 1, and I think would solve the majority of issues. but, since private space is not an option in the second user, then if Google photos could just have an option in the app to do something to the effect of like "disable this account on this device" for better peace of mind when it comes to data segregation etc... that way we could still access Gmail, Google Chat, Gemini, etc, apps that aren't as worrisome from a data segregation standpoint because they don't really have like an "auto-upload" feature. i'm not saying that's a bad feature. its good and works well. i'm just saying from a data segregation standpoint, I think its disconcerting that there's not an option to the effect of ... "disable Google photos for this account on this device". so I wonder if I should add the <a href="https://infosec.exchange/tags/privatespace" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privatespace</a> hashtag since its kind of related. i'd take both solutions - both "private space" but ALSO the ability to "disable Google photos for this account on this device".

ctrg195Google chat is a good service. But it doesn't quite pass the multiple users test. Some people, myself included, have a 2 user setup on Google pixel. Meaning, a default user, and an alt user. The reason for the 2 user setup is to avoid mixing data between the 2 user spaces. An issue with Google services on Android and ChromeOS is that, if you login to one Google app, it signs into all the other Google apps and services. On Android and ChromeOS, could we get an option for a checkbox on login to Google apps for something like "just login to this one app (don't sign in to other Google apps)" or something to that effect? Either that, and/or, an option/ability to set a secondary/non-google login to Google chat with a few other alternate forms of non-google verification like microsoft/outlook account /yahoo /apple etc.basically, any method whereby it'd give users the ability to login to certain Google apps like Google chat, without carrying the baggage of an entire Google account (photos, files, email etc) when logging in.Another thing is that Google should bring private space to multiple users. The beautiful of Google pixel phones is the ability to have multiple users so users can have complete data separation. And while private space for the default profile is ok, where it would really shine is bringing private space to multiple users so we can access our "default" Google accounts in our "alt" user space without mixing data between the two users.<a href="https://infosec.exchange/tags/2usersetup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#2usersetup</a> <a href="https://infosec.exchange/tags/dataseparation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dataseparation</a> <a href="https://infosec.exchange/tags/separatespaces" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#separatespaces</a> <a href="https://infosec.exchange/tags/androidmultipleusers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#androidmultipleusers</a> <a href="https://infosec.exchange/tags/dataseparation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dataseparation</a> <a href="https://infosec.exchange/tags/android15privatespace" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#android15privatespace</a> <a href="https://infosec.exchange/tags/androidprivatespace" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#androidprivatespace</a> <a href="https://infosec.exchange/tags/umbrellaaccounts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#umbrellaaccounts</a> <a href="https://infosec.exchange/tags/umbrellaaccount" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#umbrellaaccount</a> <a href="https://infosec.exchange/tags/multipleusers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#multipleusers</a> <a href="https://infosec.exchange/tags/onepersontwoprofiles" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#onepersontwoprofiles</a> <a href="https://infosec.exchange/tags/2umbrellaaccounts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#2umbrellaaccounts</a> <a href="https://infosec.exchange/tags/android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#android</a> <a href="https://infosec.exchange/tags/chromeos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chromeos</a> <a href="https://infosec.exchange/tags/datasegregation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#datasegregation</a> <a href="https://infosec.exchange/tags/android15" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#android15</a> <a href="https://infosec.exchange/tags/googlechat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#googlechat</a> <a href="https://infosec.exchange/tags/communication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#communication</a>

Ricerche recenti

Opzioni di ricerca

Amministrato da:

Statistiche del server: