[sjtgraham]

By all means users should be asked for permission. I can't speak for others but I personally don't often read ToS and that is my choice. In the event that there is something there that I object to and I miss it because I didn't read something I was supposed to I'm not going to cry about it.

What do you suppose the best way to ask for permission is? Please provide actual examples, perhaps from the companies you respect.

[anonyfuss]

> What do you suppose the best way to ask for permission is? Please provide actual examples, perhaps from the companies you respect.

Literally ask for permission. That's what Apple does, as does almost every other traditional desktop software developer. On first launch, or when an error occurs, or when some other event that would involve sending personal/usage data to Apple occurs, they:

- Ask if you want to send the data

- Provide details on what kind of information will be sent (including, in some cases, providing access to the data itself)

- ... and usually give you the option to always send that kind of data

[sjtgraham]

I agree this is also a good way to ask for permission. Does Apple do this in iOS? I don't recall ever seeing it outside of OS X. I imagine it's difficult to clearly express why the app wants to send this data within the constraints of a UIAlertView.

iOS asks for permission before exposing location information, or access to contacts/photos and I can see why, the information is highly private. I don't agree that "this user pressed this button at this time" quite fits into the same category of privacy though.

[anonyfuss]

> I agree this is also a good way to ask for permission. Does Apple do this in iOS?

Yep, just once.

> I don't agree that "this user pressed this button at this time" quite fits into the same category of privacy though.

You're going to consume the user's resources by sending that information, and most users don't really want you to (for obvious reasons), so it seems most ethical to ask first.