What is GetTerms.io?
Why do I need a terms of service statement?
Technically, a terms of service statement is not required for an app. It’s not mandatory by law, nor is it required by the iTunes App Store or Google Play Store. But to cover expectations and agreements between you and your users, it’s usually a good idea to publish one.
Most of the time, app developers and users behave in a fair and reasonable fashion, making your terms and conditions info redundant. However, in unusual circumstances, such as those involving abuse, intellectual property theft or unlawful behaviour, having your terms and conditions stated explicitly can offer basic protections for you and your business by limiting your liability and clarifying your rights over the content you publish.
Unlike with terms of service statements, privacy policies may be required by law, depending on where you operate and what audiences you target. In any case, it’s good practice to have one, especially if you maintain a mobile app that collects any sort of personal data from users (e.g. contact details, payment details, cookie data).
Do I have to give credit when using a GetTerms.io policy?
No. Policies generated by GetTerms.io may be used without credit or a link back. If necessary, you may also change and adapt the content for your particular purpose.
Do I need to register an account?
No account required. Just fill in your company details and policy disclosure preferences, then click the generate button to begin your one-time transaction.
How much does it cost?
Our Mobile Apps Pack starts at just $49, with optional language add-ons available at the time of purchase.
The types of personal data your app collects from users.
You must review and clearly itemise the categories of personal information collected by your app.
It’s important to note that the definition of “personal information” varies across different privacy laws.
For example, under the GDPR, you must disclose the collection of any information which are “related to an identified or identifiable natural person.”
The California Consumer Privacy Act (CCPA), however, has a slightly broader definition.
“Personal information” is classified as any data that “identifies, relates to, describes, is capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular consumer or household.”
While these differences may seem trivial, you should be thorough in your disclosure of all data that may be protected by certain laws.
How your app collects personal data.
From account creation to cookies, you must explain to users how their data is being collected.
To remain as transparent as possible, you should highlight when information is collected voluntarily from users; when information is collected automatically; and whether any information is collected from third-party services.
How your app uses this data and why it’s necessary.
You must explain how and why you use any personal data collected by your app. According to some privacy legislation, such as the GDPR, you may also need to provide a “lawful basis” for processing this data.
With that said, it’s best practice to collect data only when it is necessary for you to achieve a specific purpose.
Third-party data sharing.
What rights users have over their data.
For example, the GDPR states that users must have the right to view, edit or delete any personal data collected by your business, amongst others stipulated by the regulation.
Besides these general requirements, there are some additional clauses you may need to include before publishing your app through the App Store or Google Play.
IOS App Terms and Conditions
Your policy should also include information about:
Data retention and deletion policies.
You must explain where and how long user data is stored by your business, as well as the time period and conditions after which their data will be deleted.
How users can revoke their consent to personal data collection and/or request the deletion of their data.
Android App Terms and Conditions
Your app handles personal and sensitive user data.
This can include “personally identifiable information, financial and payment information, authentication information, phonebook, contacts SMS and call related data, microphone and camera sensor data, and sensitive device or usage data.”
Your app is designed for families and children.
Taking a “privacy by design” approach early in the app development process can save you a lot of time and money down the track from trying to retrofit your app to be legally compliant.
By giving your users more control over their privacy, your app will quickly earn a trusted reputation and help drive your user acquisition strategy.