New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Interest Group joined at Chrome was not available for Auction executed on WebView #1125
Comments
I'm not an expert, but WebView typically uses the app's own storage for everything (separate disk cache, separate cookie store, etc) rather than using Chrome's. Even two different apps using WebView won't share any storage. |
Backing up a bit - is there some way in the current Android ecosystem you have access to information in Chrome from an Android WebView, or vice versa? |
privacy sandbox Attribution API has chrome handing the trigger endpoint to android so it can associate the source & trigger. Similarly, please hand the Interest Groups created on chrome to the Android OS, making them available for the WebView Auction. |
Unfortunately this is not possible. Android WebViews don't have any way to isolate their information from the surrounding app. Without some new protection, letting a WebView run a Protected Audience auction would be tantamount to telling any app about all of your Interest Groups, violating the fundamental privacy goal of the API. |
@michaelkleber, eventually, the Privacy Sandbox vision will allow cross-platform functionality in a privacy-first approach. What are the plans for having Chrome IGs available in the Android Privacy Sandbox and vice versa? We can already register a source in ARA via a webview and have it available in the Chrome browser. |
We do want to support these use cases, once sufficient privacy infrastructure is available. We don't have any further announcement to make at this time. |
Thank you @michaelkleber |
Protected Audience API is available at both webView & chrome.
that had been verified using https://developers.google.com/privacy-sandbox/relevance/protected-audience-api#detect_feature_support
However, with an Interest Group joined from Chrome browser, that IG was not available at the Protected Audience Auction
triggered within WebView.
This is essential to resolve since our business has Ads displayed on WebView where Auctions are required to run.
The text was updated successfully, but these errors were encountered: