Trace your commute

Digital tracking explained

How app code can share data with other companies

An app can include another company's software. The InMarket case shows why a permission prompt does not explain every downstream use.

Latest source check .

Conceptual illustration

Code inside the app can have another supplier

The FTC's InMarket complaint described collection through the company's own apps and other apps incorporating its software development kit, or SDK. A user may interact with one app while another company's embedded software is involved in handling information. This describes the documented case, not every app. FTC: InMarket final settlement

The stated purpose matters

The FTC alleged that InMarket combined location with other information for targeted advertising without fully informing consumers or ensuring informed consent in the third-party apps. The finalized settlement restricts selling, sharing or licensing precise location data and sensitive-location targeting. FTC: InMarket final settlement

Compare policy with observed activity

Apple's App Privacy Report can show sensor access and contacted domains. Use those observations to ask a more specific question about an app's policy. A domain contact is a starting point for review, not a complete description of what information was sent or why. Apple: App Privacy Report

Questions and answers

Does an embedded SDK always mean data brokerage?

No. The FTC source describes particular alleged uses in a named case. It does not establish the purpose of every software component. FTC: InMarket final settlement

Can a location permission prompt describe every recipient?

Do not assume so. The InMarket case addressed inadequate disclosure about advertising use and third-party app consent. FTC: InMarket final settlement

Sources and scope

Keep exploring