Let us go through this systematically. Feel free to skip a section you might already know enough about.
Easy check: Am I collecting/storing/sharing personal information like email, names or sensitive data such as payments information or am I using a third party service that accesses that information?
If you want to read up the statements by Google in their documentation and terms, you can find them below following the links or by reading the excerpts shown.
From the Developer Console Help:
A good example of a data type are location permissions that allow accessing the device location such as follows:
Design pattern supplied by the Permissions Pattern Library
A lot of people ask for sample privacy policies for apps. Let’s start with the legal minimum requirements. A good starting point is the California Online Privacy Protection act (CalOPPA), and even better Europe’s minimum requirements since they are more refined:
Since iubenda and mobile apps are international practically by definition, let us take some hints from two relevant diverse entities far apart from each other:
“” by the Attorney General of California and the “ ” the document produced by the German data protection agencies (which we’ll summarize in English).
The most important takeaway is, that it is ok, even encouraged, to be creative. Don’t forget to back the creativity up with the actual readable full version of your policy.
In the section Lesbarkeit (readability), the data protection authorities outline that, because of the small screen real-estate, it is particularly useful to create small “categories that can be opened one by one”.
The most important takeaway here is, that a layered approach is state of the art and explicitly welcomed by the data protection authorities for mobile apps.
We think these are very solid guidelines to be creative within. Let us show you:
All our (other) guides can be found here:
Other related interesting reading: