- Only data shared directly with the app developer or contracted parties needs to be reported.
- Some categories that aren't vague are way too broad.

Mastodon reporting an empty list here is in fact very obviously wrong. When you log in to mastodon.social from the Mastodon app, you are sharing contact info (email address), identifiers, as well as usage data.

So at the very least you should conclude Threads is doing a better job of informing its users re: privacy than Mastodon gGmbH is.

Overall the App Store privacy labels are a terrible implementation of a potentially good idea. There is no way for a user to figure out how accurately a developer filled that info, and there's no baseline of quality because nobody on the Apple side reviews or enforces this.

Large companies are in fact more prone to over-declaring here because that has ~ no cost except for pissing off privacy loonies (which you can never satisfy anyway) while covering your ass legally.

Disclaimer for this post: I worked for ~2 years as a privacy reviewer for infra services at Google. This is what I would minimally declare for the Mastodon app, from my reading of Apple's policy:

- Contact Info (email address, obviously)
- Location (coarse location, Mastodon stores IP addresses in logs)
- Contacts (your follows/followers)
- User Content (your toots)
- Search History
- Identifiers (handle)
- Usage Data (logs, anti-abuse)

Not far from Threads' list...

My wish for today is for people to actually read Apple's documentation about privacy labels before replying with something wrong that is very clearly stated in the policy document: https://developer.apple.com/app-store/app-privacy-details/

If whatever I've stated seems wrong to you it's likely because the policy is vague, counter-intuitive, and just stupid in some areas. Or please justify your replies with proper quotes from the policy so we can at least start discussing differences in interpretation...

> just stupid in some areas

For example, the definition of collecting "Location" data includes "Coarse location" data. Which is defined as "Information that describes the location of a user or device with lower resolution than a latitude and longitude with three or more decimal places".

Collecting and/or inferring (e.g. via IP address) country of residence is collecting coarse location data.

A checkbox where the user states "I am a resident of planet Earth" is collecting coarse location data.