top | item 5627795

(no title)

aaronjb | 13 years ago

Seriously guys, is it really a problem?

Developers use the information to make the product better. They use crash reports to fix bugs without you having to report them and they can determine what operating system and screen resolution you're using so the next time you open up the app, it's been optimised so those ugly black borders have been taken care of.

Granted, they could ask your permission to do this, as some applications do. However, are you really going to spend time integrating an extra layer of complexity between your game, when you're on a limited development budget and the priority should be on making the game more fun?

I believe having this stated in the privacy policy, together with the privacy rules agreed to at installation is more than adequate enough for this level of application, anything more would be overkill on the developers part.

discuss

GhotiFish|13 years ago

Also violations of EULA should be punished.

Most people don't really know or understand what facebook is doing. That is why it's unethical to hide under privacy policies that state how non-private everything is under the guise of "your privacy is our highest concern".

Personally I agree with you. Modern OS's actually police and inform users of just how overzealous these programs are, and give you an opportunity to reject the terms the program sets.

Programs in response, refuse to work if they can't get access to your data, even though that data has nothing to do with the service they provide.

All of this is wonderful.

chc|13 years ago

You're talking about something wildly unrelated to the OP's basic anonymized analytics. Yes, Facebook is very invasive. Is the OP's app anything like Facebook? No, it isn't.

shadowmint|13 years ago

It's easy to make it a non-issue. You do this:

    [ ] - Send anonymous usage statistics?

1) Opt in, not out.

2) User action required to acknowledge they know and consent to it.

3) Can be disabled by anyone concerned with privacy issues.

If you fail at any of (1), (2) or (3), you're being a douche, and writing spyware, even if you bury some ridiculous disclaimer somewhere in your EULA.