Skip to content
webtoapkfree

Do I need a privacy policy for a WebView app on Google Play?

Yes. Google Play requires a privacy policy for every WebView app, even one that collects no data, linked in Play Console and inside the app.

GuidesNookesh Karri

Light cover card with the title 'Do I need a privacy policy for a WebView app on Google Play?' in dark text and a green accent bar

Yes. Google Play requires a privacy policy for every app, including a WebView app that collects no data at all. You link it in a field in Play Console and also show a link or the policy text inside the app. If your wrapped website collects anything, such as sign-ins, forms, analytics or cookies, the policy has to describe it.

Does every Google Play app need a privacy policy?

Every Google Play app needs a privacy policy, with no exception for small or data-free apps. Google’s User Data policy says all apps must post a privacy policy link in the designated Play Console field and a link or text within the app. It adds that apps that do not access any personal and sensitive user data “must still submit a privacy policy.”

The Prepare your app for review page repeats the rule: you must link a policy on your store listing and in your app, “even if your app doesn’t access personal or sensitive user data or target children.”

Why a WebView app often collects more than you think

A WebView app’s data collection is mostly your website’s data collection. The app shell may send nothing, but the page it loads can run analytics, set cookies, show a contact form or ask users to sign in.

Google’s Data safety guidance defines “collect” as transmitting data from your app off a user’s device. Data processed only on the device does not need to be disclosed. For WebViews it splits the cases in two:

  • Your own site in the WebView: user data collected from a webview opened from your app counts “if your app is in control of the code/behavior delivered through that webview.” A wrapper around your own website fits this.
  • The open web: you “do not need to declare data collection from a webview in which users are navigating the open web.”

Take a bakery that wraps its own ordering site as an app. The site has a checkout form and a Google Analytics tag, both running inside the app’s WebView, and the bakery controls that code. Names, order details and analytics events are data the app collects. The policy must cover them.

Data sent off the device by libraries and SDKs in your app counts too, whether it goes to you or a third-party server. Add an ads or crash-reporting SDK to the Android shell and its collection goes in the policy.

What the privacy policy must include

The privacy policy must explain how the app accesses, collects, uses and shares user data. The User Data policy says it must do this “not limited by the data disclosed in the Data safety section.” The required parts:

  1. Developer information and a privacy contact or a way to send inquiries.
  2. The types of personal and sensitive data the app accesses, collects, uses and shares, and who it is shared with.
  3. Secure data handling procedures for that data.
  4. Retention and deletion: how long you keep data and how users can get it deleted.
  5. Clear labeling as a privacy policy, for example in the page title.
  6. Your name or the app’s name: the entity named on the store listing must appear in the policy, or the app must be named in it.

A WebView app with no collection can get by with a short page. Say who you are and that the app itself collects no personal data. Point to the website’s own policy for anything the site does, and add a contact email.

Where the policy must live, and the format rules

The policy must sit on a public web page, not inside a file. The review page lists the checks Google applies to avoid review delays:

Requirement What passes What fails
Address Active, public URL with a valid SSL certificate Broken link, expired certificate
Access Open worldwide, no login Geofenced page, members-only page
Format Standard, non-editable webpage PDF, downloadable file, editable doc
Scope Covers this specific app A generic policy that never names the app

In Play Console, open your app’s content declarations, find Privacy Policy, click Start declaration and enter the URL. Do this first: Google won’t let you complete the Data safety form without a privacy policy.

How to show the policy inside a WebView app

The in-app part is the step WebView developers miss most. Google wants a link or the policy text inside the app, so a link only in the store listing is not enough.

Any of these counts:

  • Footer link on your website. If the wrapped site already shows “Privacy policy” on every page, the app shows it too. Check that it isn’t buried in a collapsed mobile menu.
  • Menu item in the app, opening the policy page.
  • Policy text bundled in the app. It works offline and survives website changes.

In WebToAPK Free, a project can have Website, HTML and Text sections in a drawer or tab menu. Add your policy URL as its own Website section, or paste the policy into a Text section so it shows without a connection. Bundled text only changes when you build a new version.

Use a Website section pointing at the same URL you put in Play Console. The store listing and the app then always show the same text, and you edit one page. A Text section is the wrong choice for any policy you expect to revise.

Common mistakes that get the declaration rejected

Most privacy policy problems on Play come down to a mismatch or a bad URL.

  • Login wall: the URL needs a sign-in or redirects to one.
  • Wrong name: the policy names a different company than the store listing’s developer, and never names the app.
  • A PDF sitting in a cloud drive.
  • “We collect nothing” on a policy for a site that runs analytics or a contact form.
  • Data safety answers that contradict the policy. Google says you alone are responsible for complete and accurate declarations.

This post covers Google’s published rules and is not legal advice. Privacy laws in your country can demand more than Google does, and you have to check those yourself.

What to do next

Write the policy, publish it at a stable URL, and add it both in Play Console and in the app’s menu. Then fill in the Data safety form to match. First release? Read why WebView apps get rejected and the minimum functionality rejection guide, check the closed testing rule for new accounts, and budget with what publishing on Google Play costs. The Google Play publishing guide walks through the rest of the submission.

FAQ

Does my app need a privacy policy if it collects no data?

Yes. Google’s User Data policy says apps that do not access any personal and sensitive user data must still submit a privacy policy. The policy can say plainly that the app collects nothing.

Can I use my website’s existing privacy policy?

Often yes, if it names your app or the developer shown on the store listing, covers the data the app handles, and sits on a public, non-editable web page. Google says the policy must apply specifically to your app, so add a section about the app if the current page only talks about the website.

Can my privacy policy be a PDF or a Google Doc?

Not a PDF. Google asks for a standard, non-editable webpage on an active, public URL with a valid SSL certificate, with no login or geofencing. An editable shared document fails the non-editable rule.

Open your app in Play Console, find Privacy Policy under the app content declarations, click Start declaration and enter the URL. You also need a link or the policy text inside the app itself.

Do I have to declare what my website collects in the Data safety form?

If your app controls the code loaded in its WebView, as with a wrapper for your own site, Google counts data collected there as your app’s collection. Data collected while users browse the open web inside a WebView does not need declaring.

Sources