Update: Two people that work on this team both consider this to be a poor representation of what's going on. Privacy policies aren't 1:1 with apps. So you might claim the right to do something in...
Update: Two people that work on this team both consider this to be a poor representation of what's going on.
Privacy policies aren't 1:1 with apps. So you might claim the right to do something in a policy and then never declare that in the app store.
Companies like to claim they can do anything in a privacy policy even if they're not doing it. That just makes it easier to start doing it later on.
Google gives some exemptions with privacy labeling in the app store (like if the data is never stored anywhere and only exists in transit). Unrelated example (similar exemption though): I worked on a tool that takes in unique device identifiers from Android OEM factories. But it's fine because we don't store the identifiers, they're only used in error messages that get sent back to the same user that uploaded them.
Huh. I work out with someone that is a PM on this project. I’ll have to get their opinion and will report back if it’s interesting.
Update: Two people that work on this team both consider this to be a poor representation of what's going on.
Another reason to use F-Droid instead of the Play Store. Google and their partners will always prefer to be less than candid about their data usage.