App Rejected on 17.2 clause. Asking for email ID

Question

My app is a sync solution (imagine dropbox). The user needs to sign in to access the app\'s features, and if he does not have any account already created, he can sign up.

Answer 1

It happened same for me, although the first version was approved, the second version was rejected for this reason, I added the Skip button at the landing view.

Answer 2

It's all summarized in the last paragraph. Apparently, your application doesn't inform the user (in a clear way) that registering is for syncing and from their reply, it seems that your application is useless without the Sign Up.

If that's the case, you should be more specific why you need the user to register.

On a side note, I personally don't like the applications/websites that force you to register before you see or try anything. I hope your application isn't the same.

Answer 3

Apple does not allow apps that require you to share person information to work, like an e-mail address.

You options are, remove the need for an e-mail address or remove account creation form you app and move it to a website.

It also states that you app is asking to create an account to access the full app and even needs the account or acces features that do not require the user to have an account. You can make those features available with out the account creating you might be able to get thru the review.

The reason apps like Facebook and Dropbox got thru the review proces is because they don't have a register option which is in app only. They redirect to a website.

Answer 4

The sign up asks for email id verification, and this email id is also used if the user has forgotten his password to send him one.

Apps cannot require user registration prior to allowing access to app features and content that are not associated specifically to the user.

It seems to me that the point is that you are asking the user to provide his email address as a step towards the creation of a user account. This is different from what dropbox and other apps do (i.e, you provide your credentials for your dropbox account, which is different from your email address, although it can be the same).

You may either remove altogether email verification, or you could postpone it to a later point when you have made clear to the user that this is required to access private information.

Answer 5

I also Faced this kind of Problem and my app also Rejected due to this.And Again I Changed my App flow Like User Registration will be Optional. User can See all the Feature of the app with out Registration by skipping this step.If he want to do something user-specific then you can ask to register such as : (user like,comment,photo upload etc) or else he can use the contents and features which are public.

in Case of in-app Purchase You can Prompt user that if He will Register with your app he can able to use this Content in his all devices.

It would be appropriate to make it clear to the user that registering will enable them to access the content from any of their iOS devices, and to provide them a way to register at any time, if they wish to later extend access to additional iOS devices

Answer 6

I recently spoke to an Apple Rep over the phone in regards to an app of mine that was also accused of violating clause 17.2.

I explained to him that the email would be used for password recovery, monitoring transactions within the marketplace, and managing any inappropriate behavior (such as users uploading offensive or copyrighted content). The rep responded, "Sir, the clause states 'Apps that require users to share personal information, such as email address and date of birth, in order to function will be rejected'. I cannot allow you to require your users to submit their emails if its not account-based". He did not seem to understand that the emails are account-based for the very sole purpose of security.

I did mention to him that Instagram and Facebook alike require logins at startup. He simply replied, "Yes but those apps are entirely account-based."

Honestly, I felt he was blindly following Apple's Guidelines ("Because that's what it says we must strictly follow!"). He had little understanding of how social networking apps operate, and even less understanding of the law (specifically the DMCA - on a separate issue). Explaining to them how all that works proves to be futile; they wont budge because they are asked to follow Apple's BROAD Clauses as strictly as they do.

My conclusion: I had to compromise the app's user flow such that the app's registration page can be skipped, and all other functions within its marketplace were locked to non-registered users. It makes no sense.