Placing the app in the Appstore
There is such a non-standard situation:
The application works with a certain Internet service, which, of course, requires a username and password. When sending data (login, password), the application warns the user that his personal data will be sent to the "network", i.e. via the Internet to the desired address. The Internet service itself does not use any OAuth2, etc. for authorization. Just a request-response.
The problem is that Apple doesn't want to accept this the application, explaining that:
We found your app does not obtain user consent before collecting the user's personal data, as required by the App Store Review Guidelines.
To collect personal data with your app, you must make it clear to the user that their personal data will be uploaded to your server and you must obtain the user's consent before the data is uploaded.
IOS 8 includes keys for specifying the reason the app will access the user's protected data. When the access prompt is displayed, the purpose specified in these keys is displayed in that dialog box. If your application will be transmitting protected user data, the usage string in your access request should clearly inform the user that their data will be uploaded to your server if they
That is, in short, a simple user warning is not enough for them.
So, will it be enough to add a startscreen with a description of the application, which will indicate that, that the application will send his personal data to the network. Something like a user agreement.
If anyone has encountered such things, please describe how you got around them. Thanks.
1 answers
IMHO, we need to warn you that you are collecting data, and not before sending it. And the point, I think, is not in the password with the username, but in the data that you receive in the phone, such as the user's contacts, etc.
The rules state about the user's consent to the transfer of the location, for example. On SO there is a topic about a similar refusal to publish for transmitting the mac address, and apparently, this case was caught by calling the corresponding function.
So you need to decide what you are collecting and in what time will you notify the user.