#threads also has a supplemental #privacy policy to the #meta privacy policy: (caution this is an Instagram link) https://help.instagram.com/515230437301944

There’s a section, “Information From Third Party Services and Users,” where it states “we collect information about Third Party Services and Third Party Users who interact with Threads.”

(Third Parties would naturally include other Fediverse instances and their users.)

Federated Fediverse platforms share some data, but this seems to be a whole other level.

In this section of their #privacy policy, it’s stated “We collect information about the Third Party Services and a third party users who interact with threads…”

Interaction includes following #threads users, interacting with threads content, and especially threads users following/interacting with your “third party” content.

Data collected includes IP address, instance info, profile information

So, in theory, any interaction with a Threads user would subject you to this data collection…

It looks like Meta could use the #fediverse to collect metadata on… a lot of people. In my opinion, it’s similar to the Facebook Pixel - which allows Meta to collect data on users who are off its platforms.

This could seem like no big deal (and I guess it could be), but let’s face it: Meta isn’t exactly #privacy friendly and has been accused (with proof) of abusing collected information.

#threads

@avoidthehack
> It looks like Meta could use the
fediverse to collect metadata on… a lot of people

Only to the degree that they always could. The same way anyone can. By scrapping public-facing posts from URLs.

According to the creator of Mastodon, the first developer to  implement ActivityPub;

"A server you are not signed up with and logged into cannot get your private data or track you across the web. What it can get are your public profile and public posts, which are publicly accessible."