title: Rejected App: 17.2: Apps that require users to share personal information
body: <p><strong>Preface:</strong></p>
  
  <p>I know this issue has been raised here before on SO, but those posts are old and I believe not currently relevant to Apple's decision making.</p>
  
  <p><strong>Rejection reason:</strong></p>
  
  <p>17.2 Details</p>
  
  <p>We noticed that your app uses Facebook login for authentication purposes but does not include account-based features offered by that site, which is not allowed on the App Store.</p>
  
  <p>Next Steps</p>
  
  <p>Please modify your app to include account-based features of that social network or use your own authentication mechanism.</p>
  
  <p><strong>My App:</strong></p>
  
  <p>My App implements Facebook authentication and grabs the user's first name and profile picture only and displays them at the user's discretion (when the user performs a certain function).</p>
  
  <p>I stated this to Apple twice and they replied that this was not enough.</p>
  
  <p>They kept parroting that I needed to add "account-based features" of Facebook. I asked them to elaborate and these were the examples I was given:</p>
  
  <p>"It would be appropriate to implement friends lists, social graphs, and game scores when applicable. "</p>
  
  <p><strong>So these questions arise:</strong> </p>
  
  <p>What if my app doesn't benefit from the above examples? </p>
  
  <p>What's wrong with using Facebook as an authentication method and for grabbing basic data? </p>
  
  <p>And the kicker - what are more examples of "account-based features" of Facebook that I could implement that would qualify for the privilege to use Facebook authentication?</p>
  
  <p>I'm sure I won't get any straight answers from Apple, so I am appealing to the experts here to hopefully enlighten me.</p>
  
  <p>Thanks in advance.</p>