OOmnistu

Blog / Startup Guides

Startup Guides

Apple's App Store privacy labels and in-app account deletion: what the documentation requires

Review Apple's privacy-label declarations and in-app account deletion requirements, including third-party data practices and retention questions.

OOmnistu
Reviewed 2026-11-16 · 5 min read

Two parts of Apple's submission process catch teams who built the app first and read the rules last: the privacy details you declare in App Store Connect (shown on the product page as the privacy label), and the rule that an app with account creation must let people delete the account inside the app. This article summarises Apple's own pages as read on 15 November 2026. It is not legal advice. Apple's pages change; read them again before submitting.

The privacy label

Apple says you must give information about your app's privacy practices in App Store Connect, including the practices of third-party partners whose code you add, and that you are responsible for keeping answers accurate and up to date. You can update answers without a new app version.

What counts as collecting. Apple defines "collect" as transmitting data off the device so that you or third-party partners can access it for longer than needed to service the request in real time. Data processed only on the device is not collected. Apple's example: an authentication token or IP address sent on a server call and not retained does not need to be declared. "Third-party partners" means analytics tools, ad networks, third-party SDKs and other outside code in your app. Apple says data collected only for app functionality still needs to be declared.

The data types Apple lists are grouped as: contact info, health and fitness, financial info, location (precise and coarse), sensitive info, contacts, user content (emails or messages, photos or videos, audio, gameplay content, customer support, other), browsing history, search history, identifiers (user ID, device ID), purchases, usage data, diagnostics, surroundings, body and other data. Payment info need not be declared if a payment service takes it outside your app and you never have access to it.

Purposes you choose from: third-party advertising, developer's advertising or marketing, analytics, product personalization, app functionality and other purposes.

Linked to the user, and tracking. Data is treated as linked to the user unless de-identified before collection and never relinked; Apple says personal information as defined by privacy laws is considered linked. "Tracking" means linking data from your app with third-party data for targeted advertising or ad measurement, or sharing it with a data broker. Apple's examples include a third-party SDK that combines your users' data with other developers' apps to target ads, even if you do not use it for that.

Optional disclosure. Apple lists narrow cases where a data type need not be disclosed, such as infrequent, optional, user-initiated submissions unrelated to the app's main purpose, and sets criteria that must all be met. Meeting some is not enough. Opt-in product improvement programs, certain regulated financial services data and health research data have their own all-criteria lists. Do not rely on these exceptions without reading the full lists.

Practical cases Apple gives: web views (declare data collected, unless users browse the open web), stored IP addresses (declare according to how you use them), in-app messaging (declare messages), precise location that is coarsened immediately (declare coarse location), and free-text fields (declare "other user content", though specific requested data types such as name or email must be named).

Links. A publicly accessible privacy policy URL is required. A privacy choices URL (where users can access data, request deletion or make changes) is optional.

Account deletion in the app

Apple's guideline reference says apps that support account creation must let people start deletion of the account within the app. What it describes:

What this means for a project plan (Omnistu advice)

Limits

Apple's pages only; not the Google Play equivalent (see our Play release article). We read three pages in full but not the whole App Review Guidelines (sections 4 and 5 are unread). Tracking-consent prompts (App Tracking Transparency) were mentioned on the privacy page but not researched. No claims about approval, review times or rejection rates.

By Omnistu.

Sources

Previous
iOS App Store review checklist: what to prepare before you submit