#PrivacyShield2
Live, measured metrics for the hashtag #PrivacyShield2 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #privacyshield2
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 11:33 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 11:33 UTCNo related tags with measured usage found for #privacyshield2.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 11:33 UTCEverything below is measured over the latest 3 public posts (spanning ~14925 hours).
Posting hours (UTC)
Languages: German (3)
Avg boosts / post: 0
Top of the latest posts
Meiner bescheidenen MEINUNG nach möchte man hier Fakten schaffen, bevor #noyb @maxschrems @fsfe und Co vor Gericht wieder Recht bekommen und e.g. #PrivacyShield2 wieder gekippt wird. Dieses Zeitfenster einzurichten, ist ja der Sinn der Gese
Wer jetzt so tut als sei die EU-Kommission übergeschnappt verkennt die Realität. Drittlandsübermittlungen blieben nach den Schrems-Urteilen sind der Standard - M365, AWS, Cloudflare, Salesforce, Google, Facebook... Die genutzten rechtlichen
Aus #PrivacyShield werde bald quasi #PrivacyShield2 als "Trans-Atlantic Data Privacy Framework" - mal schauen, wie lange es zu #SchremsIII dauert... 🤣 Bisher: #SafeHarbor -> #SchremsI #PrivacyShield -> #SchremsII https://steigerlegal.ch/20
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/privacyshield2