# Guideline 5.1.2: App Tracking Transparency > Rejected under Guideline 5.1.2 because the app tracks without the ATT prompt? When you need App Tracking Transparency, and when to fix the privacy labels. **Guideline 5.1.2 — Tracking: ask first with App Tracking Transparency.** Your App Privacy answers, or an SDK in the app, say you track people across other companies’ apps and websites, but the app never shows Apple’s tracking prompt. - App Store · Guideline 5.1.2. Tracking: ask first with App Tracking Transparency. - Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-2-app-tracking-transparency - Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer - Last updated: 2026-10-14 ## What this rejection means Your App Privacy answers, or an SDK in the app, say you track people across other companies’ apps and websites, but the app never shows Apple’s tracking prompt. ## Why reviewers send it Tracking people across other companies’ apps and websites requires their permission through App Tracking Transparency. Reviewers compare your App Privacy answers and the SDKs in the binary with what the app actually asks. ## The message App Review sends ``` Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing The app privacy information you provided in App Store Connect indicates you collect data in order to track the user, but the app does not use App Tracking Transparency to request the user’s permission before tracking their activity. ``` The exact wording changes from one review to the next; the guideline number is what to look for. ## How to fix it 1. If you don’t actually track — no ad attribution, no data shared with data brokers — correct the App Privacy answers in App Store Connect. That is often the whole fix. 2. If you do (ad SDKs, Meta or TikTok attribution), show the App Tracking Transparency prompt before any tracking starts, and add NSUserTrackingUsageDescription to Info.plist. 3. Don’t lock features behind accepting tracking. 4. Upload a new build if the app changed, and reply with what you did. ## Fix it with Lovable, Bolt or Cursor If the app was built with an AI builder, paste this into it, then check the result on a phone: ``` On iOS, show the App Tracking Transparency prompt (with a Capacitor ATT plugin) before initialising any ad or attribution SDK, and only enable tracking if the user allows it. ``` ## What to reply in App Store Connect Replace the [brackets] with what you actually changed: ``` Guideline 5.1.2 — [We don’t track users, and we corrected our App Privacy answers in App Store Connect.] [The app now asks for permission with App Tracking Transparency before any tracking.] ``` ## Got a different message? Paste the whole rejection into the [rejection explainer](https://capwr.app/free-tools/app-store-rejection-explainer). It recognises this one and 26 others, in your browser — nothing is uploaded. ## Other App Store rejections - [App Store Guideline 4.3 Spam rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-3-spam) - [Guideline 4.2 Minimum Functionality rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-2-minimum-functionality) - [Guideline 2.1 App Completeness rejection](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-app-completeness) - [Guideline 2.1 Information Needed: demo account](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-1-information-needed-demo-account) - [Guideline 4.0 Design rejection: sign-in in Safari](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-0-design) - [Guideline 2.3.3 Accurate Metadata: screenshots](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-3-screenshots) - [Guideline 2.3.10: Android mentioned in the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-10-other-platforms) - [Guideline 2.3.8: app icon or name doesn’t match](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-2-3-8-app-icon) - [Guideline 4.8 Login Services: Sign in with Apple](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-4-8-sign-in-with-apple) - [Guideline 5.1.1(v): account deletion required](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-v-account-deletion) - [Guideline 5.1.1: permission purpose string](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-purpose-string) - [Guideline 5.1.1: sign-up required to use the app](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-sign-up-required) - [Guideline 5.1.1(i): privacy policy link missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-5-1-1-i-privacy-policy) - [Guideline 3.1.1: digital goods without In-App Purchase](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-1-in-app-purchase) - [Guideline 3.1.2: subscription information missing](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-3-1-2-subscriptions) - [Guideline 1.5: support URL doesn’t work](https://capwr.app/free-tools/app-store-rejection-explainer/guideline-1-5-support-url) ## Fixed it? Send the build back to App Review CapWrapp builds the fixed commit on GitHub’s Mac machines, uploads it to TestFlight, and sends the build you pick to App Review from one page — no Xcode. [Get started free](https://capwr.app/login). ## About CapWrapp CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)