Even the display of ads or the use of analytics means you're collecting personal data the user should know about.
Services like Google Analytics or AdSense require you to have a privacy policy stating the use of their service.
Every major country and state, from the European Union to California, has laws requiring the use of a privacy policy.
Even if privacy policy fields might be optional, you are running the risk of being rejected after the app submission process.
It most famously happened to Path/Delta, but smaller cases are out there more frequently than you might expect.
Users want you to play fair. Collecting and using users' private data without their knowledge is an unprofessional practice.
Path collected and stored personal data upon opening the app and made false claims in its privacy policy. The case was settled with a $800,000 civil penalty.
Delta got sued by the Attorney General of California for not including a privacy policy at all.
Our privacy policies have been designed by web people, but written by lawyers.
Our list of services is massive. Anything we don't have, we'll add it upon request.
It's a 3-step process: add your app name,
select your type of data collection, embed, run.
All we constantly think about is, how can we make this simple, beautiful and usable.
Our policies are modular and can be switched to other languages (we're adding new ones as we speak).
Update from our service anytime, no need to fiddle in the app stores, no need to update across OSes.
Generate policies in English, Spanish, German, French, Brazilian Portuguese and Italian. More coming soon.
privacy policies already generated