To fill in the Data safety form for a WebView app, open App content > Data safety in Play Console and declare what leaves the user’s phone: everything your own website collects inside the app, plus anything an SDK in the Android shell sends. Pages where users browse the open web don’t count. If nothing leaves the device, you still submit the form and answer No.
The WebView rule that decides most of your answers
The WebView rule is the one line in Google’s guidance that changes how a WebView app fills in the form. Google’s Data safety help page says collection “also includes user data collected from a webview which has been opened from your app, if your app is in control of the code/behavior delivered through that webview.”
It also says you “do not need to declare data collection from a webview in which users are navigating the open web.” Sharing follows the same two rules.
A wrapper around your own website is the first case. You control the site’s code, so its forms, cookies, sign-in and analytics count as your app’s collection. A link that drops users onto someone else’s site sits closer to the second.
Google defines “collect” as sending data from your app off a user’s device. Data processed only on the phone is out of scope, and so is data protected by end-to-end encryption.
What you need before you start
The Data safety form goes faster with three things ready:
- Privacy policy URL. Even apps that collect nothing must complete the form and link a privacy policy. See do you need a privacy policy for a WebView app for the format rules.
- What your website sends. Check forms, sign-in, payment pages, chat widgets, analytics and ad tags.
- Every SDK in the Android shell. Google counts data that libraries and SDKs send off the device, whether it goes to you or a third-party server.
Step by step through the Data safety form for a WebView app
The form has five steps in Play Console.
- Overview. In Play Console, open the App content page and under Data safety select Start.
- Data collection and security. Answer whether your app collects or shares any of the required user data types. If Yes, answer two more: is all collected data encrypted in transit, and do you give users a way to request deletion?
- Data types. Tick every type your app collects or shares.
- Data usage and handling. Next to each type, select Start and answer: collected, shared or both; processed ephemerally or not; required or optional; and why.
- Store listing preview. Check what users will see on Google Play, then Submit or Save as draft.
If every page and API your site uses loads over HTTPS, data is encrypted in transit. WebToAPK Free only accepts a complete HTTPS address in Website sections, but your site can still call outside services, so check those too.
Worked example: mapping a website’s features to the form
A WebView wrapper’s answers follow from the features of the wrapped site. Take a yoga studio with a booking form, member sign-in, an analytics tag and links out to Instagram:
| Website feature | Data type to tick | Purpose | Notes |
|---|---|---|---|
| Booking form (name, email, phone) | Personal info: Name, Email address, Phone number | App functionality | Required if booking is the app’s main job |
| Member sign-in | Personal info: User IDs, Email address | Account management | Triggers the account deletion rule |
| Analytics tag | App activity: App interactions; Device or other IDs | Analytics | Check whether the vendor is a service provider |
| Error tracking script | App info and performance: Crash logs, Diagnostics | Analytics | Only if it sends data off the phone |
| Link out to Instagram | Nothing | None | Users are on the open web |
| Offline text page bundled in the app | Nothing | None | Never leaves the device |
Build this table from your live site, never from memory. Open it on a phone, submit each form once and list every third-party script. Owners almost always forget the chat widget or the newsletter popup.
Collected or shared, required or optional
Collected and shared are separate answers in the Data safety form. Google says “sharing” means transferring user data collected from your app to a third party.
Google lists four transfers that are not sharing:
- Service providers, defined as an entity that processes user data on your behalf and based on your instructions.
- Legal purposes, such as a legal obligation or a government request.
- User-initiated actions, where the user reasonably expects the data to go somewhere, or prominent disclosure with consent.
- Anonymous data that is fully anonymized.
If your app’s primary functionality needs a data type, Google says to declare it required. Optional means users can opt in or out. Answer “ephemeral” only for data held in memory just long enough to serve a request. Building advertising or user profiles never counts.
Account deletion when your site has sign-up
Account deletion is required for any WebView app whose site lets users sign up from inside the app. Google’s account deletion page says such apps must offer an in-app path to request deletion and a web link where users can request it.
That holds “even if some features can be accessed without an account.” The web link must work and reference the app or developer name. A “Delete my account” page on your site often covers both, since it opens in the app and on the web.
Mistakes that cause trouble later
Google is blunt about whether the form can get an app blocked: “In short, yes.” Apps that misrepresent their data must fix it, and apps that don’t comply face blocked updates or removal.
The catch is that Google’s review process “is not designed to verify the accuracy and completeness” of your answers. Passing review proves nothing. Your site changes without an app update, so the form can go stale with no new release, and a wrong form can sit live until a complaint or audit catches it. Recheck it whenever you add a script to the site.
Common slips:
- Answering No because the Android shell collects nothing, while the site runs analytics.
- A new sign-up page with no account deletion path.
- Leaving out an SDK added to the shell.
- Importing a CSV over a half-finished draft. Google warns that importing overwrites answers already entered, so export first.
Next steps after the form
Once the Data safety form is submitted, the rest of the release still needs work. If your app uses Google sign-in, read why Google sign-in fails in a WebView. If the site asks for files, see making file upload work in a WebView. Before you submit, check why WebView apps get rejected. The Google Play publishing guide covers the remaining submission steps.
FAQ
Does a WebView app that collects nothing still need the Data safety form?
Yes. Google says even developers with apps that do not collect any user data must complete the form and link a privacy policy. You answer No to the collection question and the form is short.
Do I declare data my website collects inside the WebView?
Yes, if your app controls the code delivered through that WebView, which is the case when the app wraps your own site. Data collected while users browse the open web in a WebView does not need declaring.
Is analytics on my website collection or sharing?
It is collection when the data leaves the device. Whether it is also sharing depends on the vendor: transfers to a service provider that processes data on your behalf and on your instructions do not count as sharing.
Do I need account deletion if my website has sign-up?
If users can create an account from within your app, Google requires an in-app path to request account deletion and a web link where they can request it. That applies even if some features work without an account.
Can I fill in the form offline?
Yes. Play Console lets you download a sample CSV, complete it offline and import it. Importing overwrites any answers already entered, so export first if you have a draft.