clarification on "account specific functionality"

Question

ConnahC OP

Created Jun ’15

Replies 2

Boosts 0

Views 1.5k

Participants 2

My app has been accepted before, but now seems rule 17.2 is getting enforced,

I need some clarification on "account specific functionality"

"User registration that requires the sharing of personal information must be optional or tied to account-specific functionality. Additionally, the requested information must be relevant to the features.".

My app finds "content relevant to the user", we need to know the age and gender of the user to provide relevant information for the social discovery engine.

How does most apps work, like Facebook?, you cannot use the app if no login happens.

So can you please clarify what you mean with "account-specific functionality". Thanks

Boost

Answer 1

KMT OP

Jun ’15

>So can you please clarify what you mean with "account-specific functionality". Thanks

You should ask that in the resolution center as review isn't here. Good luck.

0

Answer 2

junkpile OP

Jun ’15

As KMT says, we are not app review and they have the final word. But my take on it is that such "account specific functionality" would be the case if the personal info in question was *necessary* to access the user's data. For example if you're writing an account management app, requiring the user's phone number or other account number would be OK if it's the only unique identifier of the account. You could require an email address if that's what your back end *requires* it as a user ID (but only if the functionality of the app is related to that specific email address).

But in your case, where you want to use the age and gender just to provide more relevant search results, my opinion is that use case would require that info to be optional.

0