I was wondering if there are like island nations in the middle of the Atlantic or pacific that would be parts of time zones with super low populations.
But I’m also guessing most such nations would want to associate with more populous neighboring time zones (for like commerce reasons, communication etc.) which is why time zones aren’t straight lines of latitude. So then that makes me wonder if for those reasons there are time zones with zero population.
It seems like alarms can trigger Google Assistant routines. Alarm sounds can either use local ringtones or YouTube Music. These things, Google Assistant and YouTube Music, they are cloud services. I imagine that the clock's privacy policy is there due to the usage of these cloud services (along with the rule from Play Store that requires every app to have a privacy policy).
most logical take. people seem to forget that modern apps are tied into all kinds of features that regular users expect to just work. if you want a bare OS with minimalist apps, install lineage or Graphene and only use apps from F-Droid.
The clock also requires location services if you want it automated instead of manually putting the time zone, which most people don't do, so that's another thing they mistanage in their privacy policy.
Apparently my company was sending non-anonymized user data and during a privacy audit by a legal company, they really gave us a threat of being sued up the ass. And we are a MASSIVE company. I can only imagine smaller companies not realizing that.
Well not necessarily, it could just require information like reading system time settings or location data, and then they have to have a policy explaining what and why to operate in some countries.
If the information never leaves the device then it doesn't need a policy - privacy is not about what an app does in the device which never leaves the device hence never gets shared, it's about what it shares with a 3rd party.
A clock doesn't need to send system time settings information to a server since that serves no purpose for it - managing that is all done at the OS level and the app just uses what's there - and that's even more so for location data since things like determining the timezone are done by the user at the OS level, which will handle stuff like prompting the user to update the timezone if, for example, it detects the device is now in a different timezone (for example, after a long trip).