Case studies

Threads, Apple and the Illusion of Privacy

+20 XP

Case study

Threads, Apple and the Illusion of Privacy

Signing up for Meta's Threads takes a few taps, and one of them quietly accepts a very wide range of data collection. We follow that journey into the App Store privacy label and ask why a platform that sells itself on privacy keeps that label out of sight.

5 min read +20 XP when you reach the end

What you will learn

  • Spot consent hidden inside an onboarding screen
  • Apply the transparency to intrusiveness ratio
  • Use visible privacy scores to reward good practice

Scroll to follow the story. The screen changes with you.

Based on the learnings from Growth.Design: Apple vs Meta Threads: The Illusion of Privacy, presented in our own format.

The new app screen

Step 1 of 12

  1. The new app screenOne tap to install

    01

    The setup

    Threads launches, and a curious user heads to the App Store.

    Meta's new text app is all over the news, so they search for it and tap 'Get'. The listing shows ratings, age rating and chart position, and nothing about how much personal data the app takes.

    TakeawayThe moment someone decides to install is the moment privacy information matters most.

  2. Easy start screenLog in with Instagram

    02

    Onboarding

    Signing in with an existing Instagram account takes one tap.

    There is no new password and no form. The 'Log in with Instagram' button carries the user straight into setup, and the experience feels light and quick.

    TakeawayA smooth start builds momentum, and momentum lowers attention.

  3. Profile
    On autopilot screenNext, again
    Privacy
    On autopilot corrected screenAnd again

    03

    Tap, tap, tap

    Each step has one big 'Next' button, so the user stops reading.

    The profile is imported and the public or private choice is clear. After a few screens like this, the user is tapping 'Next' by habit without reading what each screen says.

    TakeawayRepetitive steps train people to skim, which is exactly when important terms get missed.

  4. Hidden consent screenTerms in gray text

    04

    Problem 1

    A screen titled 'How Threads works' is really a consent form.

    Under a friendly explainer heading sits small gray text with links to the Meta Terms, the Meta Privacy Policy and supplemental policies. Tapping 'Join Threads' accepts all of them. Nothing on the screen says so plainly.

    TakeawayIf a screen asks for agreement, its title should say that it asks for agreement.

  5. Soft framing screenBorrowed trust

    05

    Problem 2

    The headings are chosen to make the terms feel safe.

    'The fediverse' borrows the reputation of privacy first networks such as Mastodon. 'Your data' suggests ownership and safety, while the linked policies allow extensive tracking. The words steer the reader away from the real trade.

    TakeawayFraming is fair when it clarifies and unethical when it conceals.

    FramingPeople's decisions depend on how information is presented. Growth.Design points out that referencing the fediverse creates a halo effect, lending Threads the privacy image of Mastodon without its practices.

  6. The real list screenHealth data

    06

    Problem 3

    The App Store privacy label tells a different story.

    Scrolled far down the listing, the 'Data Linked to You' box includes health and fitness, financial info, browsing history, sensitive info and a catch all called 'Other Data'. All of it can be tied to the user's identity.

    TakeawayThe most important facts about a product should not be the hardest ones to find.

  7. Used for ads screenThird-party ads

    07

    The details

    Tapping through shows a long list, much of it used for advertising.

    The full App Privacy page runs on for screen after screen. Under 'Third-Party Advertising' it lists purchases, financial info, precise location and contact info, and sensitive info covers categories like health, religion and political opinion.

    TakeawayLength is not transparency. A list nobody finishes reading informs nobody.

    Held back in EuropeGrowth.Design notes, citing TechCrunch and DLA Piper (2023), that Threads did not launch in the EU at first. Under European data protection law, Meta needs a valid legal basis to process personal data for ad targeting.

  8. Hard to leave screenDelete Instagram too

    08

    Problem 4

    Leaving is much harder than joining.

    Instagram's help center explains that deleting the Threads profile and its data requires deleting the whole Instagram account. The one tap sign up is matched by an exit that holds another account hostage.

    TakeawayMake leaving as easy as joining, or people will stop trusting the way in.

    The roach motelA roach motel is a dark pattern where getting in is easy and getting out is hard. Tying Threads deletion to the Instagram account is a clear example.

  9. Current
    Honest consent screenVague summary
    Transparent
    Honest consent corrected screenEach data type named

    09

    What honest looks like

    If the collection is this intrusive, the consent screen must be this explicit.

    A transparent version names every data type with its own checkbox, from credit score to sexual orientation and political opinion, states that deleting Threads means deleting Instagram, and requires all 31 boxes to be checked. Seeing it spelled out shows how much the original screen was hiding.

    What changed

    • The title says 'Accept our Privacy Policy and Data Collection Terms'
    • Each sensitive data type is listed with its own checkbox
    • The Instagram deletion condition is stated before joining

    TakeawayTransparency should grow in proportion to how risky the data is for the user.

    The T.I. ratioGrowth.Design proposes that a product's Transparency should be at least proportional to its Intrusiveness. Ask for very sensitive data, and you owe people a very clear explanation.

  10. Apple's role screenNo privacy signal

    10

    The irony

    Apple markets privacy heavily, yet keeps the privacy label below the fold.

    Apple spends heavily on 'Privacy. That's iPhone.' campaigns. But at the top of this listing, where people actually decide, there is no sign of the data practices. The label only appears after a long scroll.

    TakeawayA privacy promise is only as strong as where the information is placed.

    Privacy washingPrivacy washing means appearing to protect privacy without doing so. Growth.Design cites research from Oxford University and reporting by Recode suggesting that tracking continued through methods such as fingerprinting after users chose 'Ask App Not to Track'.

  11. Today
    Fix: a score screenNothing here
    Redesign
    Fix: a score corrected screenVery Low privacy

    11

    The fix

    Put a data privacy rating next to the stars and age rating.

    The redesign adds a 'Data Privacy: Very Low' badge to the row of facts at the top of the listing. People see it at the moment they decide, not after scrolling past screenshots and reviews.

    What changed

    • A 'Data Privacy' rating joins ratings, age and chart position
    • A red icon and plain words signal the risk
    • The detailed label stays one tap away

    TakeawayPut the warning where the decision happens.

    A familiar patternApple already does something similar elsewhere: Safari's Privacy Report tells people how many trackers it blocked. The same clarity could sit on App Store listings.

  12. Threads
    Reward good apps screenVery Low
    Mastodon
    Reward good apps corrected screenVery High

    12

    The result

    A visible score turns privacy into a reason to choose one app over another.

    Side by side, Threads shows 'Very Low' and Mastodon shows 'Very High'. Once people can compare, collecting less data becomes a competitive advantage instead of a hidden cost.

    TakeawayChange what people can see and you change what companies compete on.

    The impact of incentivesData privacy has long been an unpriced side effect, so companies neglect it. A visible score would make people less likely to download apps with poor practices, and Apple could even rank privacy friendly apps higher.

Every takeaway, in one place

  1. The setupThe moment someone decides to install is the moment privacy information matters most.
  2. OnboardingA smooth start builds momentum, and momentum lowers attention.
  3. Tap, tap, tapRepetitive steps train people to skim, which is exactly when important terms get missed.
  4. Problem 1If a screen asks for agreement, its title should say that it asks for agreement.
  5. Problem 2Framing is fair when it clarifies and unethical when it conceals.
  6. Problem 3The most important facts about a product should not be the hardest ones to find.
  7. The detailsLength is not transparency. A list nobody finishes reading informs nobody.
  8. Problem 4Make leaving as easy as joining, or people will stop trusting the way in.
  9. What honest looks likeTransparency should grow in proportion to how risky the data is for the user.
  10. The ironyA privacy promise is only as strong as where the information is placed.
  11. The fixPut the warning where the decision happens.
  12. The resultChange what people can see and you change what companies compete on.

Source: Growth.Design: Apple vs Meta Threads: The Illusion of Privacy

Be as open about data as the data is sensitive.

Consent screens, privacy labels and account deletion flows are where trust is won or lost. Zyxware can review how your product asks for, explains and releases personal data, and redesign those moments so people know exactly what they are agreeing to.

Build with Zyxware