Skip to main content
Question

Handling Apple App Review Rejection with RevenueCat’s ‘Keep with Original App User ID’ Setting


Forum|alt.badge.img+5

We received feedback from Apple’s app review.

Our app is designed with RevenueCat’s “Transferring purchases seen on multiple App User IDs” setting set to “Keep with original App User ID”, which prevents users from making in-app purchases without registering an account.

 

However, Apple’s review guidelines prohibit requiring user registration before allowing content purchases.

 

We would appreciate any suggestions for the best workaround to comply with Apple’s guidelines while maintaining a seamless purchase experience.

 

References:

RevenueCat Documentation: Keep with original App User ID

 

Feedback from Apple:

Guideline 5.1.1 - Legal - Data Collection and Storage

 

We noticed that your app requires users to register with personal information to purchase in-app purchase products that are not account based.

 

Apps cannot require user registration prior to allowing access to app content and features that are not associated specifically to the user. User registration that requires the sharing of personal information must be optional or tied to account-specific functionality.

 

Next Steps

 

To resolve this issue, please revise your app to not require users to register before purchasing in-app purchase products that are not account based. You may explain to the user that registering will enable them to access the purchased content from any of their supported devices and provide them a way to register at any time, if they wish to later extend access to additional devices.

 

Please note that although App Review Guideline 3.1.2 requires an app to make subscription content available to all the supported devices owned by a single user, it is not appropriate to force user registration to meet this requirement; such user registration must be optional.

 

Resources

 

- Watch a video from App Review with tips for doing more for users with less data.

- See guideline 5.1.1(v) - Account Sign-In to learn more about our requirements for apps with account-based content and features.

2 replies

Forum|alt.badge.img+8
  • RevenueCat Staff
  • 523 replies
  • March 19, 2025

Hi, I believe that Apple isn’t rejecting you specifically for having user registration as we’ve had devs do this with no issues, but rather this might be due to the “sharing of personal information“ that you are gathering. Could you provide some more details on this and the types of purchases you are offering your users?


Forum|alt.badge.img+5

Thank you for your feedback.

We have explained to Apple that we have adopted a design that utilizes RevenueCat and that a major redesign would be required to make the modifications you have indicated, and the Review has passed. Therefore, there is no problem with closing this case.

However, there is a possibility that we may receive a similar point of view again, and we will respond again in that case.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings