Google on Tuesday began rolling out a beta test of its Privacy Sandbox software for a small portion of Android 13 devices to learn how its purportedly privacy-protecting ad tech actually performs.

Google began working on its Privacy Sandbox in 2019 and its Android iteration surfaced a year ago. The ad tech do-over represents an attempt to maintain current modes of online advertising, like targeting and remarketing, once invasive third-party cookies – used for cross-site tracking and profiling – get phased out.

That was originally supposed to happen in 2022, but was pushed back to 2023, then to 2024, and may yet require longer still.

The delay has been due to the fact that the technology didn’t deliver, at least initially, and that a lot of digital ad firms worry Google’s Privacy Sandbox will leave them in the dark.

Just as law enforcement groups have fretted that encryption hinders surveillance and forensics, ad tech companies fear that privacy technology will deprive them of data that Google and other large rivals like Apple can collect through their first-party relationships with consumers who use their services.

Ad firms in turn have drawn government regulators into the debate, alongside standards bodies like W3C and privacy groups. These industry stakeholders and members of the internet community have insisted on having a say in what Privacy Sandbox technologies do and how they get implemented.

Despite the fact that W3C last month gave Google’s Topics API, a Privacy Sandbox proposal to track people’s interests for target advertising, a failing grade, Google remains committed to its third-party cookie replacement systems.

“Over the past year, we’ve worked closely with the industry to gather feedback and begin testing these new technologies,” said Anthony Chavez, VP of product management for Privacy Sandbox, in a blog post provided to The Register.

“Today, we’re entering the next phase of this initiative, rolling out the first Beta for the Privacy Sandbox on Android to eligible devices. With the Beta, users and developers will be able to experience and evaluate these new solutions in the real world.”

In the case of the Topics API, it’s appropriate that Chavez said “worked closely” rather than “is working closely” because Google’s response to W3C indicates that the company isn’t doing much to resolve negative input.

In a response last Thursday to the January W3C report, Google software engineer Michael Kleber expressed willingness to talk while making it clear that Privacy Sandbox construction and the Topics API development will continue despite disinterest from Apple, Mozilla, and W3C:

Even if Chrome does manage to drop support for third-party cookies in 2024, other aspects of the not-so-private legacy ad tech regime look likely to linger several years beyond that point. In a Privacy Sandbox blog post last week, Google indicated that a technology called Fenced Frames (a replacement for iFrames) will be required no sooner than 2026, and that a supporting placeholder technology like “entry-level auction win reporting” will remain active until then.

There’s reason to believe the current ad tech stack may remain viable until 2028. James Rosewell, CEO of data service biz 51Degrees and director of marketing advocacy group Movement for an Open Web, pointed to Google’s 2022 commitment to the UK Competition and Markets Authority (CMA) to consult with interested parties. The agreement lasts for six years [PDF] unless the CMA chooses to release Google from its obligations.

Roswell told The Register in an email there’s “zero chance of FLEDGE, et al., meeting competition requirements. Therefore existing Chrome/Android functionality remains until Feb 2028 not 2026. Privacy in practice isn’t being improved for anyone as Google and Apple continue to know everything about everyone.”

But regardless of when or whether Google’s ad tech renovation reaches general availability and industry acceptance, testing has now moved beyond desktop browsers to the Android ecosystem.

This rollout is aimed at developers involved in marketing and publishing who are interested in seeing how current Privacy Sandbox APIs perform. Hence the blog post’s mention of developer guidance and the selection of effusive quotes from industry partners.

“The Privacy Sandbox Beta provides new APIs that are designed with privacy at the core, and don’t use identifiers that can track your activity across apps and websites,” said Chavez. “Apps that choose to participate in the Beta can use these APIs to show you relevant ads and measure their effectiveness.”

The Privacy Sandbox for Android Beta is being made available to “a small percentage of Android 13 devices,” and the plan is to expand enrollment over time. According to Google, those selected to participate in the beta test will receive an Android notification.

Notified individuals outside the European Economic Area, Switzerland, and the UK will have to opt out if they prefer not to participate. Selected Android users within those areas, however, will have to opt in to sample Privacy Sandbox-based ads.

Those freed from the obligation to exempt themselves can thank their legislators. ®