New Zealand rules out VPN ban after privacy backlash



TL;DR

New Zealand’s government has ruled out banning or restricting VPNs as part of its planned under-16 social media ban, after PM Christopher Luxon and Education Minister Erica Stanford moved to quell a fierce privacy backlash. The idea surfaced via a report that Stanford had floated VPN restrictions; ministers now say it was never on the table, though coalition partner NZ First warned an early proposal could have led to VPN limits and digital IDs. The episode mirrors a global tension between age-verification laws and encryption tools.

The New Zealand government has ruled out restricting or banning VPNs as part of its planned under-16 social media ban. Prime Minister Christopher Luxon and Education Minister Erica Stanford both moved to kill the idea after a rapid privacy backlash, TechRadar reports.

“I can reject that outright. There’s no plan to ban VPNs at all,” Luxon told reporters.

Stanford’s office followed up to say the government is “not looking at restricting or banning VPNs”.

The row began with a report in The Post that Stanford had floated VPN restrictions as part of the ban. Because a VPN can mask a user’s location and slip past network blocks, some officials reportedly saw it as a threat to enforcing age checks.

Accounts of how serious the idea ever was now diverge. Stanford says a ban was never considered, according to Stuff, though coalition partner NZ First reportedly warned an early proposal could have opened the door to VPN limits and digital IDs.

A red line, quickly drawn

Whatever the intent, the reaction was swift and cross-partisan. Coalition partner ACT reportedly treated any anti-encryption measure as a strict red line, and the Free Speech Union called the concept “censorship infrastructure” rather than child protection.

The pushback landed because VPNs are not merely a teenager’s workaround. They are everyday security tools for businesses, journalists, and ordinary people guarding data from hackers, ISPs, and surveillance.

New Zealand’s under-16 ban is still being finalised, part of a wave of similar laws worldwide. The country was weighing its options as neighbours and allies pressed ahead with their own age-gating regimes.

VPNs keep landing in the crosshairs

The episode is a smaller echo of a fight playing out globally. The UK’s own under-16 ban has drawn warnings that parallel plans to curb children’s VPN use would force intrusive age checks on adults too.

The pattern repeats across borders, from proposals that could see EU lawmakers bar under-16s from major platforms to Greece’s planned under-15 ban. In each case, VPNs surface as both the obvious loophole and a line regulators are wary of crossing.

Enforcement is the recurring stumbling block, as even Australia’s pioneering ban has struggled to work as intended. Age verification has redrawn the internet, and governments are still hunting for borders that hold.

For now, New Zealanders keep their VPNs, and privacy advocates have their win. The harder question, how to police a teen ban without weakening everyone else’s security, remains stubbornly unanswered.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


TL;DR

Meta stripped NameTag facial recognition code from its AI app one day after WIRED exposed it on 50 million phones. Meta says no decision has been made.

Meta removed nearly all traces of an unreleased facial recognition system from its smart glasses companion app on Friday, one day after WIRED reported that the software had been quietly embedded in an app installed on more than 50 million phones. The feature, which Meta internally called NameTag, was designed to convert faces captured by the company’s Ray-Ban smart glasses into unique biometric signatures and compare them against a database stored on the user’s device. WIRED also found that faces the system failed to recognise were cropped, indexed, and stored locally for future processing.

Andy Stone, Meta’s vice president of communications, told WIRED on Monday that the feature is “purely exploratory,” adding that no final decision has been made on what to do with it. That characterisation sits uneasily with the evidence WIRED documented. The version of Meta AI published the day of WIRED’s Thursday report contained several code libraries explicitly named for face recognition, a process for running the NameTag recognition pipeline, and a “Person recognised” alert the app would have shown if someone were identified.

Friday’s release stripped all of it out, along with a folder where the app would have stored the cropped images and biometric signatures of unrecognised faces. Meta did not answer WIRED’s questions about why the code was removed or whether the changes were planned before the story was published. A few fragments remain in the latest version, including an internal debug menu label and a dormant link meant to open a recognised person’s profile, pointing to parts of the system that are no longer there.

The 💜 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol’ founder Boris, and some questionable AI art. It’s free, every week, in your inbox. Sign up now!

The gap between Meta’s public statements and the code WIRED found is the central tension. Before the Thursday report, Stone dismissed the findings by writing that the company could not answer questions about how the system would work because “the feature does not exist.” Andrew Bosworth, Meta’s chief technology officer, called the reporting “incredibly misleading” and “absolutely dishonest.” Yet the code was functional enough to include three AI models, one to detect faces, another to crop them, and a third to encode them as biometric data, all embedded in the companion app for a product already at the centre of a mounting privacy crisis.

Meta declined to answer ten questions WIRED posed before publishing, including whether it had already created the database of face profiles NameTag uses, how long the app retains photographs and biometric data of unrecognised people, and whether that data would ever be sent back to Meta’s servers. The company also did not respond to questions about whether it was building NameTag for blind or low-vision users, or to criticism from privacy advocates who warned the system could let stalkers and abusers identify strangers in public.

NameTag first surfaced in February, when The New York Times, citing internal Meta documents, reported that the company was developing face recognition for its smart glasses and considering a launch as early as this year. One internal memo reportedly described releasing the feature during a “dynamic political environment” when privacy and civil liberties advocates would be distracted by other concerns. WIRED subsequently found that much of NameTag’s machinery had been built into the Meta AI app as early as January, months before any public acknowledgement, adding another layer to the company’s pattern of shipping first and disclosing later when it comes to its smart glasses.

Kade Crockford, director of the technology for liberty programme at the American Civil Liberties Union of Massachusetts, said the removal does not undo the original decision to ship the code and pointed to it as evidence that consumer privacy needs stronger legal protection than Congress has been willing to provide. The Massachusetts House of Representatives last week unanimously passed a consumer privacy bill that, if enacted as written, would impose strong enforcement provisions including a private right of action allowing aggrieved users to sue. “State lawmakers need to do their job and step up to protect consumer privacy,” Crockford said.

Meta’s sneaky tactics in slipping the face-recognition code into its smart glasses show exactly why data privacy bills need the teeth of strong enforcement,” Crockford added. “Companies like Meta prioritise their bottom line, so lawmakers need to speak in the only language its C-suite understands.” Whether a code removal prompted by investigative reporting constitutes a victory or merely a tactical retreat depends on what Meta does next, and on whether the regulatory pressure building on both sides of the Atlantic produces enforceable consequences before the feature quietly returns under a different name.



Source link