I use Firebase for user authentication, I just resubmitted my app and got the following rejection:
Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing
We noticed you do not use App Tracking Transparency to request the user's permission before tracking their activity across apps and websites. The app privacy information you provided in App Store Connect indicates you collect data in order to track the user, including Other Diagnostic Data, Audio Data, Performance Data, Crash Data, Product Interaction, Phone Number, User ID, Emails or Text Messages, Photos or Videos, and Search History.
Starting with iOS 14.5, apps on the App Store need to receive the user’s permission through the AppTrackingTransparency framework before collecting data used to track them. This requirement protects the privacy of App Store users.
Next Steps
Here are two ways to resolve this issue:
- You can remove the tracking functionality from your app and update your app privacy information in App Store Connect.
- If you decide to continue tracking users, you must implement App Tracking Transparency and request permission before collecting data used to track the user or device.
My app has no ads but I have to track users throughout the app using their userID so that I know what post belongs to which user etc etc.
If the user declines the prompt AppTrackingTransparency
isn't that basically saying that I can no longer track them? I have no idea what to do here.
Here are the Privacy checkboxes that I filled out. Apparently i can change something but I don't know what to change.
iOS app rejected - Guideline 5.1.2 - Legal - Privacy - Data Use and Sharing. "create a unique identifier for the user's device" 0 App Tracking Transparency privacy checkboxes and app store release rejection
Bug Fix Submissions: For apps that are already on the App Store, bug fixes will no longer be delayed over guideline violations except for those related to legal or safety issues.
The App Store Review Guidelines provide guidance and examples across a range of development topics, including user interface design, functionality, content, and the use of specific technologies. These guidelines are designed to help you prepare your Apps for the approval process.
2.5.9 Apps that alter or disable the functions of standard switches, such as the Volume Up/Down and Ring/Silent switches, or other native user interface elements or behaviors will be rejected. For example, apps should not block links out to other apps or other features that users would expect to work a certain way.
I resubmitted my app and it got approved. Seems the key is to make sure it is only Used for App Functionality
.
To make that happen I made these changes to the App Policy page in App Store Connect.
App Functionality
:No, user IDs collected from this app are not linked to the user's identity
.No, we do not use phone numbers for tracking purposes
. Notice on the 3rd screen, under Definitions and Examples, it says:Tracking does not apply in the following situations:
• When the data broker uses the data shared with them solely for fraud detection or prevention or security purposes
Here is a screen shot with it in purple underline:
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With