Android apps privacy policy

App Privacy Policy Generator

Generate a generic Privacy Policy and Terms & Conditions for your apps

Built with by Nishant and contributors.

Personally Identifiable Information

Policy Effective Date

While App Privacy Policy Generator is completely FREE, it takes money to keep it running and updated.

If you are unable to contribute with funds, consider sharing it with your friends: Twitter, Linkedin, Facebook, Reddit

. or adding a review/comment in the project’s GuestBook 🤗

Now sit back and choose the type of document you want to generate:

The accuracy of the generated privacy policy and terms & conditions on this website is not legally binding. Use at your own risk.

<< devOrCompanyName >> built the << appName >> app as <> app. This SERVICE is provided by << devOrCompanyName >> << atNoCost >> and is intended for use as is.

This page is used to inform visitors regarding <> policies with the collection, use, and disclosure of Personal Information if anyone decided to use <> Service.

If you choose to use << myOrOur >> Service, then you agree to the collection and use of information in relation to this policy. The Personal Information that <> collect is used for providing and improving the Service. <> will not use or share your information with anyone except as described in this Privacy Policy.

The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which are accessible at << appName >> unless otherwise defined in this Privacy Policy.

Information Collection and Use

For a better experience, while using our Service, << iOrWe >> may require you to provide us with certain personally identifiable information<> The information that <> request will be <>.

The app does use third-party services that may collect information used to identify you.

Link to the privacy policy of third-party service providers used by the app

Log Data

<> want to inform you that whenever you use <> Service, in a case of an error in the app <> collect data and information (through third-party products) on your phone called Log Data. This Log Data may include information such as your device Internet Protocol (“IP”) address, device name, operating system version, the configuration of the app when utilizing << myOrOur >> Service, the time and date of your use of the Service, and other statistics.

Cookies

Cookies are files with a small amount of data that are commonly used as anonymous unique identifiers. These are sent to your browser from the websites that you visit and are stored on your device’s internal memory.

This Service does not use these “cookies” explicitly. However, the app may use third-party code and libraries that use “cookies” to collect information and improve their services. You have the option to either accept or refuse these cookies and know when a cookie is being sent to your device. If you choose to refuse our cookies, you may not be able to use some portions of this Service.

Service Providers

<> may employ third-party companies and individuals due to the following reasons:

• To facilitate our Service;
• To provide the Service on our behalf;
• To perform Service-related services; or
• To assist us in analyzing how our Service is used.

<> want to inform users of this Service that these third parties have access to their Personal Information. The reason is to perform the tasks assigned to them on our behalf. However, they are obligated not to disclose or use the information for any other purpose.

Security

<> value your trust in providing us your Personal Information, thus we are striving to use commercially acceptable means of protecting it. But remember that no method of transmission over the internet, or method of electronic storage is 100% secure and reliable, and << iOrWe >> cannot guarantee its absolute security.

Links to Other Sites

This Service may contain links to other sites. If you click on a third-party link, you will be directed to that site. Note that these external sites are not operated by << meOrUs >>. Therefore, << iOrWe >> strongly advise you to review the Privacy Policy of these websites. <> have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services.

Children’s Privacy

These Services do not address anyone under the age of 13. <> do not knowingly collect personally identifiable information from children under 13 years of age. In the case << iOrWe >> discover that a child under 13 has provided << meOrUs >> with personal information, << iOrWe >> immediately delete this from our servers. If you are a parent or guardian and you are aware that your child has provided us with personal information, please contact << meOrUs >> so that << iOrWe >> will be able to do the necessary actions.

<> do not knowingly collect personally identifiable information from children. <> encourage all children to never submit any personally identifiable information through the Application and/or Services. <> encourage parents and legal guardians to monitor their children’s Internet usage and to help enforce this Policy by instructing their children never to provide personally identifiable information through the Application and/or Services without their permission. If you have reason to believe that a child has provided personally identifiable information to us through the Application and/or Services, please contact us. You must also be at least 16 years of age to consent to the processing of your personally identifiable information in your country (in some countries we may allow your parent or guardian to do so on your behalf).

Changes to This Privacy Policy

<> may update our Privacy Policy from time to time. Thus, you are advised to review this page periodically for any changes. <> will notify you of any changes by posting the new Privacy Policy on this page.

This policy is effective as of << effectiveFromDate >>

Contact Us

If you have any questions or suggestions about << myOrOur >> Privacy Policy, do not hesitate to contact <> at << appContact >>.

This privacy policy page was created at privacypolicytemplate.net and modified/generated by App Privacy Policy Generator

By downloading or using the app, these terms will automatically apply to you – you should make sure therefore that you read them carefully before using the app. You’re not allowed to copy or modify the app, any part of the app, or our trademarks in any way. You’re not allowed to attempt to extract the source code of the app, and you also shouldn’t try to translate the app into other languages or make derivative versions. The app itself, and all the trademarks, copyright, database rights, and other intellectual property rights related to it, still belong to <>.

<> is committed to ensuring that the app is as useful and efficient as possible. For that reason, we reserve the right to make changes to the app or to charge for its services, at any time and for any reason. We will never charge you for the app or its services without making it very clear to you exactly what you’re paying for.

The <> app stores and processes personal data that you have provided to us, to provide <> Service. It’s your responsibility to keep your phone and access to the app secure. We therefore recommend that you do not jailbreak or root your phone, which is the process of removing software restrictions and limitations imposed by the official operating system of your device. It could make your phone vulnerable to malware/viruses/malicious programs, compromise your phone’s security features and it could mean that the <> app won’t work properly or at all.

The app does use third-party services that declare their Terms and Conditions.

Link to Terms and Conditions of third-party service providers used by the app

You should be aware that there are certain things that <> will not take responsibility for. Certain functions of the app will require the app to have an active internet connection. The connection can be Wi-Fi or provided by your mobile network provider, but <> cannot take responsibility for the app not working at full functionality if you don’t have access to Wi-Fi, and you don’t have any of your data allowance left.

If you’re using the app outside of an area with Wi-Fi, you should remember that the terms of the agreement with your mobile network provider will still apply. As a result, you may be charged by your mobile provider for the cost of data for the duration of the connection while accessing the app, or other third-party charges. In using the app, you’re accepting responsibility for any such charges, including roaming data charges if you use the app outside of your home territory (i.e. region or country) without turning off data roaming. If you are not the bill payer for the device on which you’re using the app, please be aware that we assume that you have received permission from the bill payer for using the app.

Along the same lines, <> cannot always take responsibility for the way you use the app i.e. You need to make sure that your device stays charged – if it runs out of battery and you can’t turn it on to avail the Service, <> cannot accept responsibility.

With respect to <>’s responsibility for your use of the app, when you’re using the app, it’s important to bear in mind that although we endeavor to ensure that it is updated and correct at all times, we do rely on third parties to provide information to us so that we can make it available to you. <> accepts no liability for any loss, direct or indirect, you experience as a result of relying wholly on this functionality of the app.

At some point, we may wish to update the app. The app is currently available on <> – the requirements for the <>(and for any additional systems we decide to extend the availability of the app to) may change, and you’ll need to download the updates if you want to keep using the app. <> does not promise that it will always update the app so that it is relevant to you and/or works with the <> version that you have installed on your device. However, you promise to always accept updates to the application when offered to you, We may also wish to stop providing the app, and may terminate use of it at any time without giving notice of termination to you. Unless we tell you otherwise, upon any termination, (a) the rights and licenses granted to you in these terms will end; (b) you must stop using the app, and (if needed) delete it from your device.

Changes to This Terms and Conditions

<> may update our Terms and Conditions from time to time. Thus, you are advised to review this page periodically for any changes. <> will notify you of any changes by posting the new Terms and Conditions on this page.

These terms and conditions are effective as of << effectiveFromDate >>

Contact Us

If you have any questions or suggestions about << myOrOur >> Terms and Conditions, do not hesitate to contact << meOrUs >> at << appContact >>.

This Terms and Conditions page was generated by App Privacy Policy Generator

This template for privacy policy and terms & conditions is provided on «AS IS» basis, without warranties or conditions of any kind, either expressed or implied. It is intended for you as an inspirational document and you may use it when compiling your own privacy policy. The developer of App Privacy Policy Generator does not take any responsibility for the legal consequences associated with the use of this privacy policy or terms & conditions, and urges you to seek independent legal advice ensuring compliance with all rules applicable for the users of your application. The developer of App Privacy Policy Generator can in no way be found liable for any direct or indirect damage/loss suffered by individual/company due to the use of this document.

Источник

Privacy Policy for Android Apps

Google Play has made it a basic requirement to make certain privacy-related disclosures to users, in accordance with applicable law. These disclosures are typically made available to users via a privacy notice that is easily accessible from within the app.

In short

• Platform requirements aside, under the vast majority of legislations (and particularly under the GDPR) privacy notices are legally required.
• If your app handles personal or sensitive user data, or is in the “Designed for Families” program, you need to add a valid privacy policy in two places: your app’s Store listing page and within your app.
• If applicable, you have to disclose how you treat sensitive user and device data.
• If your app processes personal data for reasons unrelated to its functionality, you must highlight – prior to the collection and transmission – how the user data will be used and collect user consent.
• If your app is likely to be used by kids, you are subject to additional safety requirements.
• With iubenda you can create a privacy policy (and a Terms and Conditions document) for your Android app.

Here’s what Google had to say in their Developer Policy Center’s User Data guidelines:

You must be transparent in how you handle user data (e.g., information provided by a user, collected about a user, and collected about a user’s use of the app or device), including by disclosing the collection, use, and sharing of the data, and you must limit use of the data to the description in the disclosure. If your app handles personal or sensitive user data, there are additional requirements described below. This policy establishes Google Play’s minimum privacy requirements; you or your app may need to comply with additional restrictions or procedures if required by an applicable law.

Now, Google Play only explicitly requires that a link to a privacy policy be visible on your app’s store listing page and within your app in cases where:

• Your app handles personal or sensitive user data, as defined in the user data policies (including personally identifiable information, financial and payment information, authentication information, phonebook or contact data, microphone and camera sensor data, and sensitive device data).
• Your app is in the “Designed for Families” program (regardless of access to sensitive permissions or data).

However, it is critical to note here that, platform requirements aside, under the vast majority of legislations, and particularly under the GDPR, privacy notices are legally required.

Platform requirements aside, under the vast majority of legislations, and particularly under the GDPR, privacy notices are legally required.

Generally, failure to adhere to these laws can result in hefty fines, sanctions, audits and/or leave you open to litigation.

Privacy policy requirements for Android apps

A lot of people ask for sample privacy policies for apps. The exact required contents of a privacy policy depends upon the law applicable to you and may even need to address requirements across geographical boundaries and legal jurisdictions.

For this reason, it’s always advisable that you approach your (legally mandated) privacy policy with the strictest applicable regulations in mind. You can read more about determining your law of reference here or read our in-depth Legal Overview Guide here.

Let’s start with the legal minimum requirements. These are the most basic elements that a privacy policy should have:

• Who is the app owner?
• What data is being collected? How is that data being collected?
• What is the Legal basis for the collection? (e.g consent, necessary for your service, legal obligation etc.) – This is more specifically related to the GDPR and EU Law, however, even if you fall outside of GDPR obligations, under most countries’ legislations, you’ll still need to say why you’re processing the personal data of users.
• For which specific purposes are the data collected? Analytics? Email Marketing?
• Which third parties will have access to the information? Will any third party collect data through widgets (e.g. social buttons) and integrations (e.g. Facebook Connect)?
• What rights do users have? Can they request to see the data you have on them, can they request to rectify, erase or block their data? (under European regulations most of this is mandatory)
• Description of process for notifying users and visitors of changes or updates to the privacy policy
• Effective date of the privacy policy

Sensitive permissions

In addition to this, you need to make sure that you disclose your use of any of the following “dangerous” permission groups (personal or sensitive user data mentioned earlier) in your privacy policy:

Options

You have two options:

• remove all requests for user data or sensitive permissions (you will not need to add a privacy policy if you remove these requests); or
• add a valid privacy policy in two places: your app’s Store listing page and within your app.

Prominent disclosures

If your app processes the personal data of users for reasons unrelated to the functionality of your app, you’re required to make additional, easily visible disclosures about this usage and collect user consent where required.

If your app processes personal data for reasons unrelated to its functionality, you must highlight – prior to the collection and transmission – how the user data will be used and collect user consent.

Here’s what Google states about prominent disclosures:

If your app collects and transmits personal or sensitive user data unrelated to functionality described prominently in the app’s listing on Google Play or in the app interface, then prior to the collection and transmission, it must prominently highlight how the user data will be used and have the user provide affirmative consent for such use.

Your in-app disclosure:

• Must be within the app itself, not only in the Play listing or a website;
• Must be displayed in the normal usage of the app and not require the user to navigate into a menu or settings;
• Must describe the type of data being collected;
• Must explain how the data will be used;
• Cannot only be placed in a privacy policy or terms of service; and
• Cannot be included with other disclosures unrelated to personal or sensitive data collection.

Your app’s request for consent:

• Must present the consent dialog in a clear and unambiguous way;
• Must require affirmative user action (e.g. tap to accept, tick a check-box, a verbal command, etc.) in order to accept;
• Must not begin personal or sensitive data collection prior to obtaining affirmative consent;
• Must not consider navigation away from the disclosure (including tapping away or pressing the back or home button) as consent; and
• Must not utilize auto-dismissing or expiring messages.

It’s worth noting that it seems that Google considers any data collection activity that isn’t made obvious from your app page or from within your interface to be covered by this prominent disclosure policy.

Therefore a separate user notice is required in addition to your privacy policy – which your notice should ultimately link – to for a full explanation of the data processed. Again, the data must not be processed until you have affirmative consent by your user.

Furthermore, under regulations like the GDPR, you are legally required to obtain informed, explicit consent before processing any personal data of users specifically where it falls outside the what’s required for the functioning of your service.

Options

With this in mind, you have 2 options when it comes to dealing with this kind of data processing. You can either:

• remove this type of data collection; or
• properly inform via in-app disclosures, link that notice to the respective privacy policy and collect valid consent.

If you fall within the scope of the GDPR, you’ll likely also need to maintain valid records of consent.

Privacy policy example for an Android app

Google Play and child safety

Google has introduced a few policy updates in order to make the Play Store more child-friendly. If an app is likely to be used by kids, developers are subject to additional safety requirements which came into force on September 1, 2019.

Target Audience and App Content

Apps on Google Play are categorized, and policies applied, according to the following target audience groups: children, children and older users, older users. Google states that they will verify that the target audience selected is in fact correct.

All apps whose target audience is primarily children must follow Families policy and Designed for Families program requirements.

• App content that is accessible to children must be appropriate for children.
• Both new and existing apps are now subject to the target audience questionnaire. You must accurately answer the questions in the Google Play Console and ensure that those answers are correctly updated if you make any changes to your app.

APIs, SDKs and neutral age screen

Apps that solely target children must not contain any APIs or SDKs that are not approved for use in child-directed services. Apps that target both children and older audiences should not implement APIs or SDKs that are not approved for use in child-directed services unless they are used behind a neutral age screen or implemented in a way that does not result in the collection of data from children.

A neutral age screen is a mechanism to verify a user’s age in a way that doesn’t encourage them to falsify their age and gain access to areas of your app that aren’t designed for children, for example an age gate. An example of this would be a system that asks users to freely enter their month, day, and year of birth. An incorrect setup of a neutral age screen would be presetting the birth date to the required age (e.g., 13 years old) or indicating that a certain age is required to access areas of the app.

In order to make sure that any ads served to children (or users of unknown age) are appropriate and compliant with Google’s policies, you must use Google Play certified ad networks.

Apps with unintentional appeal to children

Google also wants developers to ensure that their apps don’t inadvertently attract children (for example with youthful animations or young characters in the graphic assets) if their content is actually designed for adults. More info on how to display the “Not designed for children” label in the store listing can be found here.

Terms and Conditions for Mobile Apps

Terms and Conditions (also called ToS – Terms of Service, Terms of Use or EULA – End User License Agreement) set the way in which your product, service or content may be used, in a legally binding way. Not only are crucial for protecting you from potential liabilities, but (especially in cases where something is being sold to consumers) they often contain legally mandated information such as users’ rights, withdrawal or cancellation disclosures.

In general, you’ll likely need to set Terms and Conditions if you have an app that participates in some form of commerce (whether selling to users directly or facilitating trading). Additionally, some specific instances where they might be needed are where you:

• need to make legally required disclosures related to consumer rights (especially withdrawal and cancellation rights);
• have different user levels (eg. registered vs non-registered);
• your platform allows users to sell or trade with other users;
• facilitate or otherwise process payments and/or other sensitive user data;
• want to set the rules for user behavior and state grounds for termination of accounts;
• participate in affiliate programs;
• provide a software or service which can potentially cause harm if misused;
• would like to have some legally enforceable control over, and set rules about, how your app may be used.

Particular emphasis should be given to account termination clauses, payment conditions and the limitation of liability clauses (and disclaimers).

Our Term and Conditions Generator helps you to easily generate and manage documents that are engineered to meet the specific requirements of all major app stores and up to date with the main international legislations.

How to add a privacy policy to your Android app

iubenda makes solving this issue easy: with hundreds of available clauses, our privacy policies contain all elements commonly required across many regions and services, while applying the strictest standards by default – giving you the option to fully customize as needed.

Our policies are created by lawyers, monitored by our lawyers and hosted on our servers to ensure that they are always up-to-date with the latest legal changes and third-party requirements.

The process is straightforward and intuitive, simply:

1. click to add your services;
2. fill out your web/app owner and contact details;
3. embed.

Click here to read the full guide on how to generate a Privacy Policy.

Here’s how you can use iubenda to create a privacy policy for your Android app :

1. Add your services

• If you use Twitter or other auth (=OAuth) services for user management, then add the respective service by clicking “Add a service” then start typing the name of the service you’d like to add. Remember to include all services processing personal information. If you handle user registration yourself, don’t forget to add the “Direct Registration” service.
• Select each applicable service from the list of suggestions that show up and customize by simply adding the specific types of personal data you collect. Our lawyer-crafted clauses automatically include the relevant user-rights disclosures and service definitions based on your input here.
• Add our service called “Device permissions for Personal Data access” if your app requests sensitive permissions (e.g. camera, microphone, accounts, contacts, or phone) or user data:
• If you’d like to add a custom service clause, simply click the “Create custom service” button and fill out the built-in form.

2. Fill out your app owner and contact details

• name and full address;
• email address.

Congratulations! Your policy has been created. Simply check that all the details are correct, then embed.

3. Embed

As we said above, you have to include a link to your privacy policy within the app and in the Google Play Store app listing (and – potentially – on the marketing site you operate for it).

Within the app

For apps, the direct link or direct text embedding methods are best. If your app processes user data while offline, be sure to provide users with an in-app offline method of accessing the privacy policy in order to be legally compliant.

Whichever embed method you choose, remember that you’re required to choose a location that is easily accessible and visible to users. Here’s an example by Instagram:

Google Play Store listing

When your app is ready, in addition to the app’s internal link, you’ll have to include a link to your privacy policy on the Google Play Store. Here’s how to meet this requirement:

• Go to your Google Play Console
• Select an app
• Select Store presence > Store listing
• Under “Privacy Policy”, enter the iubenda direct link (since we host your policy, you won’t get the “You are not allowed that domain for a privacy policy URL” error)
• Save your changes

This will make sure that you have your privacy policy linked under Additional information > Developer on the Google Play Store like so:

Источник