Should I provide a EULA for an iPhone app?
I understand that apps are covered by the default EULA that the App Store provides but, during some research today, three apps in a row asked me to agree to an explicit EULA when the app first started. It made me wonder if I should have one.
If it makes any difference to your answer, my app will send a small amount of data to a central server. Nothing sensitive.
I plan to have a privacy policy within the app but to not make the user explicitly acknowledge it....and no EULA Does that sound right?
A lot of iphone apps seem to bury their EULA in the settings page - my intended compromise is to have the user acknowledge the EULA and privacy policy only at the point where they will post data back to to the server.
For local use - no EULA.
If it makes any difference to your answer, my app will send a small amount of data to a central server. Nothing sensitive.The App Store EULA already covers this case (if the data is used only to improve the app). If you are not sure about whether you should provide one, it is likely that the one written by Apple's layers is better than anything that you would mash-up.
So my opinion is not to provide a custom EULA until you are successful enough to afford professional legal advice.