ctrg195<p>"Fitbit will delete data if you don’t migrate to Google Account by 2026"</p><p>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. </p><p><a href="https://9to5google.com/2025/03/28/fitbit-google-account-2026/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">9to5google.com/2025/03/28/fitb</span><span class="invisible">it-google-account-2026/</span></a></p><p><a href="https://infosec.exchange/tags/datasegregation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>datasegregation</span></a> <a href="https://infosec.exchange/tags/loginwithgoogle" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>loginwithgoogle</span></a> <a href="https://infosec.exchange/tags/loginwithmicrosoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>loginwithmicrosoft</span></a> <a href="https://infosec.exchange/tags/sso" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sso</span></a> <a href="https://infosec.exchange/tags/multipleusers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>multipleusers</span></a> <a href="https://infosec.exchange/tags/2usersetup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>2usersetup</span></a> <a href="https://infosec.exchange/tags/privatespace" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>privatespace</span></a> <a href="https://infosec.exchange/tags/android16" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>android16</span></a> <a href="https://infosec.exchange/tags/googlechat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>googlechat</span></a> <a href="https://infosec.exchange/tags/gemini" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>gemini</span></a> <a href="https://infosec.exchange/tags/android15" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>android15</span></a> <a href="https://infosec.exchange/tags/pixel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pixel</span></a> <a href="https://infosec.exchange/tags/pixel8" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pixel8</span></a> <a href="https://infosec.exchange/tags/pixel9" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pixel9</span></a> <a href="https://infosec.exchange/tags/pixel9pro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pixel9pro</span></a></p>