How iOS 14 Changed App Tracking and Data Privacy

iOS 14 introduced privacy controls designed to give users more visibility into how apps collect, combine and share personal data. The changes centered on two measures: a system setting for tracking requests and standardized App Store disclosures describing an app’s data practices.

The initial rollout came with an important limitation. Although iOS 14 included the tracking control, Apple postponed enforcement of the associated permission requirement until early 2021, giving developers and advertising companies more time to adapt.

Understanding the tracking request setting

The relevant control appears under Settings > Privacy > Tracking as Allow Apps to Request to Track. When this option is turned off, apps cannot display prompts asking for permission to track activity across other companies’ apps and websites.

During the early iOS 14 rollout, however, disabling requests did not guarantee that every app would immediately stop attempting to track users. Apple’s own description warned that apps that did not ask for permission might still try to track activity. This reflected the delayed enforcement deadline rather than the intended long-term behavior of the framework.

Keeping the setting disabled reduces tracking requests and expresses a system-level preference against cross-company tracking. Users who enable it can decide separately whether to grant permission when each participating app asks.

Why the transition mattered to developers

Behavioral data supports advertising, measurement and personalization across the app economy. Apple’s planned enforcement therefore required developers and advertisers to reassess both their technology and their business models.

Large companies may have several ways to generate revenue without cross-app tracking, while smaller developers can depend heavily—or even entirely—on advertising. The delayed deadline was intended to give affected businesses time to prepare for the change.

App Store privacy disclosures

Apple also established a questionnaire for developers submitting new apps or updates to the App Store. Developers must explain what data an app collects, how that information is used and whether it is shared with others. The resulting disclosure appears with the app’s store information.

This standardized summary is often compared with a nutrition label: it is intended to help people evaluate an app’s data practices before installing or using it.

Categories of data an app may collect

• Contact information: First and last name, email address, telephone number and physical address.
• Health and fitness information: Data associated with health or fitness services and features.
• Financial information: Payment card details, bank account numbers and creditworthiness information.
• Location: Precise or approximate location data.
• Sensitive information: Race, ethnicity, sexual orientation, religion, political views, and genetic or biometric information.
• Contacts: Information stored in the device’s address book.
• User content: Messages, email, photos, videos, audio recordings and content generated by users in games.
• Browsing history: Information about websites or other content viewed.
• Search history: Records of searches performed by the user.
• Identifiers: Identifiers associated with either the user or the device.
• Purchases: Purchase history and shopping preferences.
• Usage data: Interactions with the app, including navigation patterns, clicks, time spent in particular areas and advertisements viewed.
• Diagnostics: Performance information such as errors, crashes, launch times and energy consumption.
• Other data: Information that does not fit the defined categories.

How collected data may be used

The disclosures also identify the purposes for which an app processes data. Apple’s classifications include:

• Third-party advertising: Showing ads supplied by parties other than the developer or sharing data with companies that provide those ads.
• Developer advertising or marketing: Displaying the developer’s own ads or sharing data to support promotion of the developer’s products and services.
• Analytics: Studying user behavior or measuring the size and characteristics of the app’s audience.
• Product personalization: Customizing the experience, such as recommending posts or products.
• App functionality: Supporting authentication, security, scalability, performance and other core features.
• Other purposes: Uses that do not fall into the specified classifications.

The broad other labels deserve particular attention because they provide less immediate detail than the named categories. Users should consider them alongside the app’s full privacy policy and requested system permissions.

Activities not treated as tracking

Under the rules described for developers, certain uses of data are not classified as tracking. Examples include:

• Combining information from different sources entirely on the device, provided the data is not sent elsewhere.
• Using information for fraud detection, fraud prevention or security purposes.

These exceptions do not eliminate the need for scrutiny. Security is a legitimate reason to process data, but the scope and necessity of that processing still matter.

Review app permissions regularly

Privacy labels explain declared data practices, while iOS permission controls govern access to protected system capabilities. Both are useful, but neither should replace periodic review.

Open Settings > Privacy to inspect which apps can access features and information such as location, contacts, photos, microphones, cameras and tracking controls. Remove permissions that an app no longer needs, and reconsider apps whose requested access appears unrelated to their purpose.

iOS 14’s privacy features did not make data collection disappear. They did, however, make tracking choices and developer disclosures more visible, giving users better tools for deciding which apps to trust.