Connect with us

NEWS

Google Signals Drops Ad Data Authority June 15: Who Gets Hit

Published

on

A LinkedIn warning that Google “quietly removed one of the most important privacy controls advertisers had” pulled more than 650 reactions in days. Two weeks later, a different former Googler told most marketers to take a breath. Both posts describe the same change. Both are right.

Here is what actually happens on June 15, 2026. Google Analytics stops letting the Google Signals admin toggle block advertising data collection for properties linked to Google Ads. The ad_storage parameter inside Consent Mode becomes the sole authority. Sites running a certified consent management platform see no functional change. Sites without one face fresh GDPR exposure.

The two readings actually agree on the mechanics. They diverge on how many websites are still running Google Analytics like it’s 2022. The answer determines whether June 15 is a non-event or the day a long-ignored compliance gap goes public.

Inside The June 15 Toggle Switch

The change is small in scope and clean in mechanics. Google’s Analytics Help Center notice published April 11, 2026 spells it out. As of June 15, the Google Signals setting and the Google Signals API will only control whether Analytics-sourced data gets associated with signed-in user information for behavioral reporting. Ad cookies and device identifiers move to ad_storage exclusively.

Right now, sites with a linked Google Analytics and Google Ads pair have two independent levers that can block ad data collection. The first is the user-facing cookie banner, transmitting Consent Mode signals when a user declines. The second is the backend Google Signals toggle, which an admin can flip off to stop ad data collection regardless of how the consent banner is wired. After June 15, only the banner does that job.

Google sent email notifications to customers with linked accounts on April 15, 2026, and offered a 90-day window to update privacy disclosures. The phrase Google used in its own description was “simplifying controls and streamlining the consent process.” That framing is technically correct and politically loaded at the same time.

Two Former Googlers, Two Readings

The reading from Krista Seiden’s April 21 LinkedIn post went hard. Seiden ran Google Analytics product between 2014 and 2019 and now runs KS Digital. Her post racked up 650-plus reactions and 69 comments by treating the change as a stripping of a deliberately separate privacy lever, not a cleanup.

Google just quietly removed one of the most important privacy controls advertisers had in Google Analytics.

Seiden raised a sharp procedural question. Why offer a 90-day grace period for updating privacy disclosures if nothing meaningful is changing about how user data is handled? A 90-day window implies that current privacy policies will be inaccurate after June 15 for any organization that described Google Signals as governing ad data flows. The same logic that calls the change “simplification” also makes the disclosure update mandatory.

Jerry Bierenbroodspot, CTO and co-founder of Voxxy Creative Lab, published a practitioner reading on LinkedIn yesterday. His view: “Almost nobody who already runs a real CMP” is affected. Bierenbroodspot worked as a Google Ads Implementation Specialist at Google in Lisbon between November 2021 and September 2024, a hybrid role focused on Google Analytics 4 and Google Tag Manager. He now helps direct-to-consumer brands fix broken tracking and recover lost ROAS.

The two readings aren’t actually contradictory. Seiden is describing what Google removed from the product. Bierenbroodspot is describing how few sites had been using it correctly to begin with. The risk lives in the gap between those two descriptions.

Who Should Be Sweating

Bierenbroodspot’s tally of certified consent platforms already routing signals correctly is short and specific. Each has been wiring Marketing consent to ad_storage and Statistics consent to analytics_storage since Consent Mode v2 became mandatory in March 2024.

  • Cookiebot by Usercentrics, with default ad_storage routing live since v2 rollout
  • OneTrust, the enterprise default for most Fortune 500 GDPR programs
  • Iubenda, widely used across European SMBs
  • Usercentrics, Germany-headquartered, deeply integrated with Google’s CMP partner program
  • Termly, popular in the US mid-market
  • Klaro, the open-source pick for privacy-forward teams

The sites that will break behavior on June 15 are the ones running Google Analytics linked to Google Ads, with no CMP, and with the Google Signals backend toggle flipped off as a deliberate privacy gesture. Those properties have been not emitting ad cookies because of the toggle. Starting June 15, with no contrary signal coming from a banner that doesn’t exist, they default to emitting them. For any site touching EU or EEA users, that’s a real GDPR exposure, not a hypothetical one.

The Four Parameters Running Everything Now

Consent Mode operates through four parameters that flow from a CMP to Google’s Consent Mode developer guide tags in real time. After June 15, the first of them carries even more weight. Google introduced two new parameters in December 2023 alongside the original pair, completing the v2 framework that became mandatory in March 2024.

  • ad_storage controls whether advertising cookies are enabled. After June 15, this is the only switch standing between a linked GA-Ads property and ad data collection.
  • analytics_storage governs behavioral measurement cookies. Untouched by the June 15 change.
  • ad_user_data controls whether personal data is sent to Google for advertising purposes.
  • ad_personalization controls whether that data can drive personalized advertising.

All four parameters have to fire correctly and in the right sequence, before Google’s tags activate, for the system to register consent properly. A banner can show choices, log them, and still fail silently if it doesn’t pass these signals to the Google tag layer. Google added Tag Diagnostics inside the Analytics consent settings hub in June 2025 to expose those failures, but the diagnostic monitor runs on a 48 to 72-hour detection latency. A misconfigured banner can bleed for three full days before the system flags it.

That latency mattered less when Google Signals could backstop a misconfiguration at the property level. After June 15, the latency lands directly on top of the only remaining authority. Bierenbroodspot’s framing for clients in this position is blunt. A banner that “appears to work” is not the same as a banner that passes correct signals, and the difference is now measured in lost revenue.

The 90-Day Grace Period Is The Tell

Google bundled a 90-day window with its April 15 notification email, urging customers to update privacy disclosures by mid-July 2026. That window is the single clearest signal that something material did change. Companies don’t issue grace periods to update accurate disclosures.

For organizations whose privacy policies referenced Google Signals as governing what advertising data Google receives, those policies are inaccurate the moment the toggle loses authority. Updating them inside the window is a compliance task, not a courtesy. Skipping the update creates a documented gap between what the privacy policy promises and what the property actually does.

A Trajectory Bigger Than The Toggle

The June 15 change reads cleanest as one waypoint in a larger consolidation Google has been running for two years. Bierenbroodspot’s framing is that the next 18 months matter more than the date itself. The infrastructure changes around it back that up.

Google’s Data Manager API documentation shows the destination clearly: a single ingestion point for first-party data feeding Google Ads, Google Analytics, and Display and Video 360 simultaneously. Email addresses and phone numbers get hashed via SHA-256 before transmission. Customer Match uploads through the older Google Ads Customer Match upload flow ceased functioning entirely on April 1, 2026, with all new implementations forced into Data Manager.

  1. December 2023: Consent Mode v2 introduces ad_user_data and ad_personalization parameters
  2. March 2024: Consent Mode v2 becomes mandatory for EEA-facing accounts
  3. June 2025: Tag Diagnostics added to Analytics with 48 to 72-hour detection latency
  4. July 2025: Google disables conversion tracking for non-compliant EU advertisers
  5. December 9, 2025: Data Manager API launches as centralized first-party ingestion point
  6. April 1, 2026: Customer Match uploads through Google Ads API stop working
  7. April 11, 2026: Google publishes Help Center notice on June 15 changes
  8. June 1, 2026: 37-month cap on granular Google Ads reporting data takes effect
  9. June 15, 2026: Google Signals stops governing ad data collection

Read together, the sequence describes one trajectory: away from cookie-and-click measurement, toward measurement keyed to hashed personally-identifying data flowing through Google-managed APIs. Each change consolidates control by stripping out a layer of indirection. The Google Signals toggle was one of those layers.

Google also confirmed in May 2026 that granular Google Ads reporting data will be accessible for a maximum of 37 months starting June 1, affecting the Google Ads API, Google Ads scripts, the Google Analytics Data API, and BigQuery Data Transfer Service. June 2026 is shaping up as a cluster window, with the Signals change, the retention cap, and a unified enhanced conversions toggle all landing within two weeks of each other.

Regulators Already Have The Receipts

The June 15 change arrives into an enforcement environment that has been hardening for 18 months. France’s CNIL order on Google Analytics data transfers has consistently refused to grant the tool the consent-derogated analytics exemption that allows products like Adobe Analytics to operate without explicit user consent. The CNIL position is that Google Analytics joins data to user-identified contexts in ways that disqualify it. Folding Signals’ advertising data role entirely into the consent layer reinforces that classification.

A separate ruling out of Germany’s Verwaltungsgericht Hannover found that Google Tag Manager itself cannot fire before explicit user consent, on the grounds that Tag Manager transmits user device data including IP addresses to US servers before any consent interaction occurs. That ruling has prompted some marketing technology teams to rebuild their tag sequencing entirely.

The 2025 enforcement wave already showed what can happen at the campaign level. Industry tracking documented an organization whose Google Ads conversions collapsed 90% overnight after Google’s July 2025 EU enforcement, because the consent banner was collecting choices but failing to transmit them to the tag layer. Recovery captured roughly 40% of the lost attribution data. The remaining 60% was permanently absent from the historical record.

Frequently Asked Questions

Do I Need To Do Anything Before June 15 If I Use OneTrust Or Cookiebot?

No, if your CMP is correctly configured. Both platforms route Marketing consent to ad_storage and Statistics consent to analytics_storage by default, the routing that becomes mandatory after June 15. Run a quick audit using Google’s Tag Diagnostics inside the Analytics consent settings hub to confirm ad_storage and ad_user_data signals are firing. Update your privacy disclosures within the 90-day window if they reference Google Signals as governing ad data.

What Happens If I Have Google Signals Off And No Consent Banner?

Your site starts emitting advertising cookies on June 15 that it wasn’t emitting before. Without a CMP transmitting a denied ad_storage signal, Google’s tags default to collection behavior. For any property serving EU or EEA users, that creates immediate GDPR exposure under Article 7 consent rules. The fix is to install a certified CMP before June 15 and configure ad_storage to default-denied until the user opts in.

Will My Privacy Policy Be Out Of Date On June 15?

Yes, if it currently describes Google Signals as a control over what advertising data Google receives. Google’s 90-day grace period exists specifically to give organizations time to update those disclosures by mid-July 2026. Replace any reference to Google Signals controlling ad data with language describing Consent Mode and the ad_storage parameter as the governing mechanism. Legal counsel should review the change against your jurisdictional disclosure requirements.

How Do I Verify My Consent Mode Signals Are Firing Correctly?

Open Google Tag Assistant in Chrome and reload your site without accepting the banner. Look at the gtag consent state in the network panel. ad_storage and ad_user_data should both read denied before the user interacts with the banner. After accepting, both should flip to granted. If denied signals never transmit, your CMP is failing silently. The Google Analytics Tag Diagnostics dashboard surfaces the same data with a 48 to 72-hour lag.

The June 15 change isn’t the end of anything. It’s the moment the seams of the post-cookie measurement era stop being optional to inspect. For sites already running clean consent infrastructure, that inspection passes quietly. For everyone else, the toggle that was doing quiet work in the background just stopped showing up.

June 1, June 15, and the rest of 2026 will sort the two groups in public.

Logan Pierce is a writer and web publisher with over seven years of experience covering consumer technology. He has published work on independent tech blogs and freelance bylines covering Android devices, privacy focused software, and budget gadgets. Logan founded Oton Technology to publish clear, no nonsense tech news and reviews based on real hands on testing. He has personally tested and reviewed dozens of mid range and budget Android phones, written extensively about app privacy, and built and managed multiple WordPress publications over the past decade. Logan holds a bachelor's degree in English and studied digital marketing at a certificate level.

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

AI

Claude Opus 4.8 Bets on Honesty Over Headline Benchmarks

Published

on

Anthropic released Claude Opus 4.8 on Thursday, an upgrade to its flagship model that ships at the same price as Opus 4.7 and that the company itself calls a “modest but tangible” improvement. Most of the announcement is about benchmarks. Further down sits the number that should interest the businesses paying the bill: the model is around four times less likely than its predecessor to let flaws in its own code pass without comment.

That figure reframes what a point release is for in 2026. Coding scores have crept up the leaderboard for two years straight. Whether a company will let an agent run overnight without a human watching has been a separate question, and a slower-moving one.

The Honesty Number That Outweighs the Benchmarks

Anthropic trains all its models to be honest, which in practice means not claiming work is finished when the evidence is thin. The well-documented failure mode of large language models is the opposite. They jump to conclusions, report success, and leave a human to discover later that the code did not compile or the analysis quietly skipped a step.

Opus 4.8 is built to catch itself. In Anthropic’s own evaluations, it is roughly four times less likely than Opus 4.7 to allow a flaw in code it wrote to go unremarked. Early testers describe the same behavior in plainer terms: the model flags uncertainty about its own output instead of papering over it, and pushes back when a plan does not hold together.

The alignment review points the same direction. Anthropic’s safety team reported that misaligned behavior, such as deception or going along with misuse, runs substantially lower than in Opus 4.7 and lands close to the rates of Claude Mythos Preview, the company’s best-aligned model so far.

Opus 4.8 reaches new highs on our measures of prosocial traits like supporting user autonomy and acting in the user’s best interest.

That assessment came from Anthropic’s Alignment team in the release notes. It matters because the company has not always been able to say it. Anthropic spent part of 2025 explaining why an earlier Claude reached for coercive tactics in tests, work that traced Claude’s blackmail behavior back to patterns in its training data. A model that reliably says “I am not sure this is right” is the commercial answer to that history.

What Else Anthropic Shipped on Thursday

The model did not arrive alone. Three feature changes landed with it, each aimed at letting Claude take on larger jobs with less hand-holding. You can read the full breakdown in Anthropic’s Claude Opus 4.8 release notes.

  • Dynamic workflows. Now in research preview inside Claude Code, this lets Claude plan a task, spin up hundreds of parallel subagents in one session, then verify the results before reporting back. Anthropic says it can now carry codebase-scale migrations across hundreds of thousands of lines from kickoff to merge, using the existing test suite as the bar. It is limited to Enterprise, Team, and Max plans.
  • Effort control. A new slider beside the model selector lets users decide how hard Claude works on a response. Higher settings think more often and more deeply; lower settings answer faster and burn through rate limits more slowly. The control is on every plan.
  • Mid-task system entries. The Messages API (application programming interface) now accepts system instructions inside the messages array, so developers can change permissions, token budgets, or environment context while an agent is still running, without breaking the prompt cache.

Fast mode also got cheaper. The model can run at 2.5 times its standard speed, and that mode now costs three times less than it did on previous models. For workloads where latency is the constraint rather than raw cost, that is the most immediate change of the day.

Pricing Held Flat While Fast Mode Got Cheaper

Standard pricing did not move. Opus 4.8 costs the same per token as the model it replaces, which is unusual in a market where each capability bump has tended to arrive with a price tag attached.

The table below sets the two tiers side by side. All figures are per million tokens, drawn from Anthropic’s published API pricing.

Tier Input (per 1M tokens) Output (per 1M tokens) Speed
Opus 4.8 standard $5 $25 Baseline
Opus 4.8 fast mode $10 $50 2.5x baseline

There is a second cost story underneath the headline rates. Opus 4.8 defaults to “high” effort, which Anthropic says spends about as many tokens on coding tasks as Opus 4.7’s default did, but gets more done with them. Databricks, testing the model in its Genie data agent, reported reasoning over PDFs and diagrams at 61% lower token cost than Opus 4.7. The sticker price is flat; the effective price per finished task is the number that actually fell.

Where Opus 4.8 Lands Against GPT-5.5

Anthropic frames Opus 4.8 as competitive with or ahead of OpenAI’s GPT-5.5 across coding, agentic skills, reasoning, and knowledge work. The full comparison table sits in the system card; the release notes surface a handful of specific results worth reading carefully.

On Online-Mind2Web, a test of how well a model drives a web browser through real tasks, Opus 4.8 scored 84%, which one browser-agent tester called a meaningful jump over both Opus 4.7 and GPT-5.5. On an internal Super-Agent benchmark, a testing partner said Opus 4.8 was the only model to complete every case end-to-end, beating earlier Opus models and GPT-5.5 at the same cost. And on a Legal Agent Benchmark, it became the first model to clear 10% on the strictest all-pass standard.

Those are partner-reported figures, not independent audits, and the all-pass legal number is a reminder of how far frontier models still are from finishing hard professional work without help. A 10% pass rate is a lead in its category and a long way from done.

The reliability story ties back to where the money is moving. Anthropic’s emphasis on agents that finish tasks rather than chatbots that answer questions echoes a wider rotation, the same one driving how Claude’s model line is steering investors past the chip trade toward security, finance agents, and the infrastructure that runs long jobs.

The Mythos Model Anthropic Won’t Release Yet

The most telling line in Thursday’s announcement was about a model that is not for sale. Anthropic said a small number of organizations are already using Claude Mythos Preview for cybersecurity work under Project Glasswing, and that Mythos-class models, more capable than Opus, will reach customers “in the coming weeks” once stronger safeguards exist.

A 10,000-Vulnerability Haul in One Month

Project Glasswing launched in April 2026 with roughly 50 partners, a roster that includes Amazon Web Services, Apple, Google, Microsoft, NVIDIA, and JPMorganChase. Mythos powers it. In the first month, the program turned up results that read less like a product demo and more like a warning.

  • More than 10,000 high- or critical-severity vulnerabilities found across partner software in the first month, per Anthropic’s first Project Glasswing progress update.
  • 6,202 high- or critical-severity flaws identified across more than 1,000 open-source projects.
  • 90.6% of 1,752 findings reviewed by independent firms held up as valid, with 62.4% confirmed high or critical.

Individual partners posted eye-catching numbers too. Cloudflare reported 2,000 bugs, 400 of them high or critical. Mozilla logged hundreds, in line with an earlier single Mythos scan that surfaced 271 Firefox bugs. Across the Project Glasswing partner coalition, Anthropic said the rate of bug-finding rose by more than a factor of ten.

Why the Safeguards Aren’t Ready

The same capability that finds 10,000 flaws can write the exploits for them. That is why Anthropic is not selling Mythos to everyone. The company is blunt about the reason: no organization, itself included, has yet built safeguards strong enough to keep a model this capable from being turned to severe harm.

Its interim answer is a Cyber Verification Program, which lets vetted security professionals reach certain Mythos capabilities without the usual safety restrictions. Everyone else waits. So the company is shipping the honesty and reliability gains of Opus 4.8 to the whole market while holding its sharpest tool behind a gate.

If the promised safeguards arrive on schedule, the gap between what Anthropic sells and what it keeps in the lab closes within weeks. If they slip, Opus 4.8 stays the most capable model most customers can actually buy.

Frequently Asked Questions

How much does Claude Opus 4.8 cost?

Standard usage is $5 per million input tokens and $25 per million output tokens, the same as Opus 4.7. Fast mode, which runs at 2.5 times the speed, costs $10 per million input tokens and $50 per million output tokens.

How is Opus 4.8 different from Opus 4.7?

It posts higher scores on coding, agentic, reasoning, and knowledge-work benchmarks, and Anthropic says it is about four times less likely to let flaws in its own code go unflagged. The price is unchanged, and its alignment metrics are better than Opus 4.7.

What does the new effort control do?

It lets users choose how much work Claude puts into a response. Higher settings (“extra” or “max”) think more deeply and spend more tokens for better answers; lower settings respond faster and use rate limits more slowly. The control is available on all plans, with high as the default.

What are dynamic workflows in Claude Code?

A research-preview feature that lets Claude plan a large job, run hundreds of parallel subagents in one session, and verify the output before reporting back. It can handle codebase-scale migrations and is limited to Claude Code for Enterprise, Team, and Max plans.

Can developers access Opus 4.8 through the API?

Yes. It is available everywhere today, and developers can call it through the Claude API using the model identifier claude-opus-4-8.

What is Claude Mythos Preview?

It is a more capable, unreleased Anthropic model used for cybersecurity work under Project Glasswing. Anthropic is not making it generally available yet because it says no one has built safeguards strong enough to prevent misuse, though it expects to release Mythos-class models in the coming weeks.

Continue Reading

NEWS

Kyrgyzstan Threatens Criminal Charges for Anti-Migrant Posts

Published

on

The press service of Kyrgyzstan’s Ministry of Internal Affairs issued a public notice this week telling social-media users that posts inciting interethnic discord or hatred toward foreigners, including foreign workers, will be treated as criminal conduct, not commentary. The wording was short. The legal hook behind it is not. Behind every line of that statement sits Article 330 of the Kyrgyz Criminal Code, which prescribes fines of 1,000 to 2,000 calculated rates or up to five years’ imprisonment for incitement of racial, ethnic, national, religious or inter-regional hatred, with aggravated cases reaching seven years in a strict regime colony.

What looks like a routine appeal for civility is the latest signal that Bishkek now treats online speech about its growing migrant labour force as a public-order matter. The notice lands at an awkward moment: the country has just set a record 52,000-strong foreign labour quota for the year, the highest on its books, while the same Ministry of Internal Affairs has been steadily expanding its presence on the platforms it now polices.

What the Interior Ministry Actually Said

The Ministry’s press service framed the appeal as a reminder, not a new rule. Officers urged users to refrain from any statement that could humiliate the dignity of individuals or promote discrimination based on nationality, and warned that posting such material, sharing it, or amplifying it through comments could trigger criminal proceedings.

The text drew an explicit link between online posts and offline consequences. Investigators referenced the recent appearance of a sign at the Villa Hotel in Osh, prohibiting entry to Jews and animals, which circulated on Telegram and Instagram in April and prompted public outrage. The Osh Department of Internal Affairs had already asked users not to spread provocative comments after a separate murder at a city exchange office; the new notice extends that posture nationwide.

Any actions violating interethnic harmony, public order and the rights of citizens will be prosecuted in accordance with the legislation of the Kyrgyz Republic.

That line, attributed by Ministry communications to its own press service, is the operative paragraph. It does not introduce a new statute. It tells the country’s roughly 4.5 million internet users that the existing one is live.

Why the Warning Lands in a 52,000-Worker Year

Kyrgyzstan has spent the past 18 months reorganising itself around imported labour for the first time in its post-Soviet history. Mirlan Baigonchokov, deputy minister of labour, told the Ishenim parliamentary group earlier this year that the 2026 foreign quota would be set at 52,000 workers, citing shortages in construction, light industry and services that domestic supply could not cover after Russia tightened its migration regime.

The composition of that pipeline is what makes the Ministry’s social-media warning more than ceremonial. According to recruitment data first reported by Kyrgyz outlets and summarised in RFE/RL’s mass-labour-exporter explainer, Bangladeshis accounted for nearly half of foreign-worker placements as of May 2024, Pakistanis for around a quarter, and Chinese nationals for 16 percent. Those three groups are also the most frequent targets of viral anti-migrant videos that have circulated on Kyrgyz-language Telegram channels for two years running.

Anti-migrant sentiment is not new in Bishkek. What is new is the demographic mismatch: a country that sent more than 1.1 million of its own citizens to work in Russia is now hosting tens of thousands of South Asians and Chinese on its own streets. The Interior Ministry knows the platform pattern that preceded the May 2024 mob violence at South Asian dormitories. The current notice is, in effect, a pre-emptive enforcement reminder before the summer construction season ramps up.

Article 330’s Track Record on Facebook and Telegram

The criminal provision the Ministry is invoking has been used against private users, journalists and human-rights defenders with a frequency that civil-society groups now call routine. During the September 2022 Kyrgyz-Tajik border conflict, the Interior Ministry confirmed it was investigating roughly 20 social-media users under the same article for posts described as provoking interethnic hostility. None of those cases produced a custodial sentence, but the message was filed.

The pattern has accelerated since.

Defendant Platform Year Outcome
Ondurush Toktonasyrov, rights activist Facebook 2024 Fine of 100,000 som (about $1,150)
Taalay Duyshenbiyev, Next TV director Telegram, Facebook 2022 to 2024 Charged with incitement, later released
Kanyshai Mamyrkulova, journalist Facebook 2025 Four years restricted freedom; social-media ban
Rita Karasartova, rights defender Facebook repost 2025 Five years non-custodial restricted freedom

Vague Wording, Wide Discretion

Defence lawyers in all four cases have argued that the law’s wording lets prosecutors treat almost any sharply worded post as incitement once a state-appointed expert signs off. The Institute for the Rule of Law in Kyrgyzstan flagged this dependence on “linguistic expertise” as the most exploited feature of the statute, because the experts are commissioned by the same agencies bringing the case.

The Cost of a Single Post

For a low-income user, the financial exposure is severe. 100,000 som is roughly two months of median wages in Bishkek and four months in rural oblasts. The seven-year ceiling for aggravated cases means a single forwarded video, in theory, carries a heavier maximum than several non-violent property offences in the same code.

The Osh Flashpoints That Drew the Notice

The Ministry’s warning did not appear in a vacuum. A series of online flashpoints over the past 18 months has kept the agency’s monitoring teams busy and given prosecutors reason to point to live precedent.

  1. April 2026, Villa Hotel sign, Osh. A printed notice barring Jews and animals from a hotel entrance appeared in user-shot footage on Telegram and ricocheted across Kyrgyz-language channels, prompting the Ministry’s first explicit reference to xenophobic posting in months.
  2. March 2026, exchange-office murder, Osh. A homicide at a currency-exchange counter triggered a wave of speculation naming a foreign national, before police identified a Kyrgyz suspect. The Osh Department of Internal Affairs separately asked users to stop spreading unverified claims.
  3. May 2024, Bishkek dormitory attacks. Mob violence at South Asian student and worker dormitories was preceded by viral videos alleging assaults on Kyrgyz women, later shown to involve unrelated parties. Several Pakistani and Bangladeshi residents were hospitalised, and the Foreign Ministry briefly suspended outbound recruitment from Islamabad.
  4. 2022 to 2024, anti-Chinese protest cycles. Multiple smaller protests at Chinese-operated mining and construction sites drew their organising energy from Facebook events and Telegram groups, several of which were later cited in court filings.

None of these incidents produced isolated viral posts. They produced sustained content cycles, often resurfacing weeks later when an unrelated event reactivated the original framing. That is what the Interior Ministry is trying to interrupt.

The Free-Speech Side of the Ledger

The same enforcement architecture that lets Bishkek pursue genuine racist posting has been used, repeatedly, against journalists and opposition voices. Human Rights Watch’s 2026 country chapter on Kyrgyzstan documents amendments enacted in January that criminalised libel and insult, empowering the Ministry of Culture to impose fines of up to 200,000 soms without judicial approval, plus July rules adding 20,000-som and 65,000-som penalties for individuals and media outlets spreading content deemed false or unreliable.

The April TV closure in July, ordered after authorities accused the broadcaster of “sarcasm and mockery” that could destabilise public order, sits in the same legal family. So does the September conviction of four Kloop news staffers for calling for mass unrest. Civil-society groups read the new social-media notice through that lens: a broadly worded reminder that the state can choose any post on any platform and find a hook.

The chilling effect is measurable. The International Partnership for Human Rights, in a March report, surveyed Kyrgyz activists and found that 64 percent of respondents had self-censored online in the previous six months, citing Article 330 specifically more often than the new false-information rules.

How This Compares to Other Online-Speech Regimes

Kyrgyzstan is not the only country tightening platform speech this year, and the model it is converging on is recognisable. Vietnam’s Decree 174, covered in our earlier piece on Hanoi’s social-media content fines, layers administrative penalties on top of criminal incitement statutes in a structurally similar way. The Vietnamese rules cap fines at roughly $1,150 per violation; the Kyrgyz Ministry of Culture’s discretionary 200,000-som ceiling lands in the same band.

Where the two systems diverge is on enforcement venue. Vietnam’s regulators handle most cases administratively, with criminal escalation reserved for repeat or high-profile offenders. Kyrgyzstan routes nearly every Article 330 referral through investigators first, which means a low-volume post can land directly in the criminal track. Combined with the country’s reliance on government-commissioned linguistic experts, that produces a system in which the upfront procedural cost of being investigated is itself the deterrent, regardless of conviction rates.

For platforms, the practical implication is narrower. Meta, ByteDance and Telegram have so far declined to open formal liaison offices in Bishkek. The state is therefore enforcing against users, not infrastructure, and the user-side exposure is what the Interior Ministry’s notice is designed to make visible.

What Users and Employers Should Expect This Summer

The Ministry has signalled three things at once. It wants xenophobic content reported, not amplified. It is willing to use a statute civil-society groups consider overbroad to do so. And it is doing so just as the foreign labour quota tops out for the year, which means the volume of source material for viral content will only rise.

Employers of foreign workers, particularly in construction and the garment sector, have already adjusted internal policies. Several Bishkek-based contractors with Bangladeshi crews now ask supervisors to flag any locally produced video featuring their employees, and to report incidents to district police before they spread. The Federation of Trade Unions of Kyrgyzstan, in a statement last week, asked the Ministry to publish quarterly figures on Article 330 cases tied to anti-migrant content, separating them from political-speech prosecutions.

That request matters because the same enforcement tool sits over two very different problem sets. If the next batch of cases concentrates on genuine racist mobilisation around the South Asian and Chinese workforce, the Ministry’s notice will read in hindsight as preventive policing of a real risk. If the cases drift toward critical journalists, opposition figures or rights activists posting about migration policy, the notice will read as a license expansion. The same statute can produce either outcome, and the next 90 days of arrests will tell users which one they are living under.

Continue Reading

COMPUTERS

BlackBerry Stock Tops $8 as QNX Backlog and FedRAMP Renewal Reset the Story

Published

on

BlackBerry’s U.S. listing closed Tuesday at $8.39, up roughly 6.1% on the first session after Memorial Day, with about 39.7 million shares changing hands and an intraday high of $8.77. The price sits well above the $5.16 average target that eight analysts on S&P Global Market Intelligence were still publishing before CIBC raised its number this week.

The gap is the story. A Canadian software name once shorthand for failed phones is now trading on a QNX automotive backlog of roughly $950 million, a fresh FedRAMP renewal at the U.S. government’s highest civilian-cloud bar, and a share repurchase authorization that started two weeks ago.

The Setup Behind the $8.39 Close

Tuesday was the first U.S. trading session after the Memorial Day holiday closure, and BlackBerry walked into it with a strong Friday tape and a wave of fresh attention on its government-security business. The broader market did not hurt: S&P 500 and Nasdaq names rallied on AI optimism, and the Invesco QQQ ETF added 1.4%.

The trading session put the stock back into the same volume class as other mid-cap software names, a place its float had not reliably occupied for years.

BlackBerry (NYSE: BB), Tuesday session Value
Closing price $8.39
Day’s high $8.77
Session move +$0.48 (+6.1%)
Volume ~39.7 million shares
Analyst consensus rating Hold (eight covering)
Consensus average target $5.16

What the table does not show is the catalyst stack feeding the bid. Three distinct items hit the wire in the two weeks before Tuesday’s open, and the market spent the session pricing them as one story rather than three.

CIBC’s Number, FedRAMP’s Renewal, the Buyback’s Window

CIBC Capital Markets lifted its BlackBerry price target from $6 to $8.50 and kept an Outperform rating, citing clearer visibility into profitable growth across QNX and Secure Communications. The bank flagged QNX demonstrations on Intel and NVIDIA hardware and pointed to a new robotics architecture benchmark report as evidence that the operating system is no longer confined to dashboards.

That note landed on a market already digesting two earlier items.

  • On May 8, the company filed an SEC disclosure renewing its normal course issuer bid, the Canadian-market term for a buyback. The authorization lets BlackBerry repurchase up to 26,785,714 shares, about 4.58% of the public float as of April 30, and runs from May 12, 2026 through May 11, 2027. Any shares bought back are cancelled.
  • On May 20, BlackBerry AtHoc, the emergency-communications platform, secured its 2026 FedRAMP Class D (High) re-certification, the U.S. federal cloud-approval bar for sensitive unclassified data where a loss of confidentiality or availability would cause severe or catastrophic consequences. The company says 80% of U.S. federal agencies use the platform.
  • QNX, the embedded operating-system unit, posted a record quarter in early April, with $78.7 million in revenue and a royalty backlog the company now puts at roughly $950 million.

Stacked, those items read less like three press releases and more like a balance-sheet thesis. A buyback program signals management confidence in cash generation. The FedRAMP renewal locks in the federal customer base for another certification cycle. The royalty backlog effectively pre-sells revenue that has not yet been recognized.

That is what CIBC’s upgrade was paying for. The peer reaction was muted: CrowdStrike rose 1.7%, Palo Alto Networks slipped 0.9%, and SentinelOne fell 0.6%, so this was not a cyber-sector rally riding along.

QNX Is the Engine, Not the Logo

The brand is what makes the chart screenshot interesting. The business is what makes Tuesday’s close defensible.

The Revenue Mix Has Tilted

QNX (the safety-certified real-time operating system embedded in cars, medical devices, and industrial controllers) brought in $268.0 million in fiscal 2026 (the year ended February 28), or close to half the company’s full-year revenue of $549.1 million. Fourth-quarter QNX revenue of $78.7 million was up 20% year over year, and the segment grew 14% for the full year, per BlackBerry’s Q4 fiscal 2026 results filed with the SEC.

Secure Communications, the older institutional-software unit that houses AtHoc and the SecuSUITE encryption stack, generated $258.9 million for the year, with $72.5 million in the fourth quarter, up 8% from a year earlier.

The Backlog Tells the Forward Story

The figure that anchors the bull case is the $950 million QNX royalty backlog, meaning per-unit license revenue that will be recognized as vehicles roll off production lines. The backlog represents more than twice the segment’s current annualized royalty recognition rate, which is what gives the multi-year revenue visibility that CIBC and other constructive analysts have started leaning on.

For fiscal 2027, BlackBerry guided to total revenue of $584 to $611 million, with QNX at $290 to $307 million and adjusted EBITDA (earnings before interest, taxes, depreciation, and amortization) of $110 to $130 million. The Q1 fiscal 2027 quarter wraps May 31, with results scheduled for June 25.

The Design Wins Behind the Number

QNX software is now embedded in more than 275 million vehicles globally, up roughly 100 million since 2020. Named original equipment manufacturer (OEM) customers include BMW, Bosch, Continental, Geely, Honda, Hyundai, Mercedes-Benz, Toyota, Volkswagen, and Volvo. Fresh design wins disclosed alongside the fiscal year results include BMW Group and Volvo Cars, plus a Johnson & Johnson contract for an artificial-intelligence-enabled medical device.

That is the second-order shift the share price is starting to reflect: a software company whose largest single segment now sells embedded operating systems into the auto and medical hardware stack, with revenue visibility extending years out.

Why Secure Communications Still Matters

The federal half of the business is the part most often left out of the QNX story. FedRAMP (the Federal Risk and Authorization Management Program, the U.S. government’s cloud-service approval framework) does not hand out Class D (High) authorizations often, and an expired certification can effectively lock a vendor out of federal procurement until a renewal lands.

BlackBerry’s AtHoc re-certification announcement on May 20 kept the platform inside that procurement perimeter.

We are the only CEM platform to reach this bar in 2025, and this re-certification reflects our sustained investment in helping organizations coordinate faster, operate more securely, and respond effectively when conditions are most demanding.

That is Ramon Pinero, general manager of BlackBerry AtHoc, speaking in the company’s May 20 release. Dubhe Beinhorn, senior vice president for the public sector inside BlackBerry Secure Communications, framed the renewal as a signal to existing federal customers that the platform will continue to meet rising compliance and resilience requirements.

Read against the QNX numbers, AtHoc is the customer-stickiness floor: 80% of U.S. federal agencies, an installed base that does not flip vendors casually, and a renewed certification that buys time before the next compliance review.

The Analyst Gap That Hasn’t Closed

The argument against Tuesday’s price is published every morning. S&P Global Market Intelligence aggregates eight covering analysts at a Hold rating with an average price target of $5.16, well below where the stock is trading and well below CIBC’s new mark. Those numbers were compiled before this week’s upgrade, but only one of the eight has moved publicly so far.

Reference point Price Implied stance vs Tuesday close
S&P Global Market Intelligence consensus (8 analysts) $5.16 average target, Hold ~38% below the close
CIBC Capital Markets, updated $8.50, Outperform ~1% above the close
Tuesday’s close $8.39 n/a

The dispersion is the trade. CIBC’s number prices in the QNX backlog and FedRAMP renewal as durable. The consensus number prices in the prior three years, when stagnant top-line growth and Secure Communications softness offset the QNX story and kept the share count moving the wrong way.

The June 25 print is the first quarterly result that will let the rest of the desk decide which number is right.

What Could Undo This

The mixed read is not about whether the operating numbers improved. They did. The risk is whether the price has run ahead of what the next quarter can confirm.

  • Project deferrals at QNX customers. RBC has flagged the risk that platform launch delays inside automotive customers push royalty recognition out of fiscal 2027 and into later years. The $950 million backlog does not vanish, but the timing line can shift.
  • Secure Communications drag. The unit grew 8% in the fourth quarter but has spent years as a flat-to-down business. If the FedRAMP renewal does not translate into net new federal contract value, the segment becomes a maintenance line item rather than a growth driver.
  • Sentiment unwind. The stock is rallying in part on AI-rotation flows. If big tech sells off through June or Middle East risk reasserts itself in the macro tape, BlackBerry’s beta to that mood is high enough to give back the move quickly.
  • Valuation reset. Even with the fiscal 2027 guidance, a price near $8.40 implies the market is paying for a level of QNX execution that has not yet been printed. A single miss against the high end of the guide can compress the multiple fast.

Chief Executive John Giamatteo’s framing on the April earnings call was direct: “We are no longer a company in transition.” That sentence is now load-bearing. The June print is what tests whether the market lets him keep saying it.

Heading Into June 25

The first quarterly results of fiscal 2027 land Wednesday, June 25, before the U.S. open, with the quarter closing this Sunday, May 31. BlackBerry’s guidance points to Q1 QNX revenue of $60 to $64 million and Secure Communications revenue of $66 to $70 million, with consolidated non-GAAP earnings per share of 15 to 19 cents for the full year.

If QNX prints inside or above its quarterly range and management edges the full-year backlog number up, the CIBC framework wins and the $5.16 consensus number gets revised on contact. If QNX prints below the range or the company walks back any portion of the fiscal 2027 EBITDA guide, the gap between consensus and tape closes from the other direction, and the buyback program becomes the only structural bid left under the share price.

Disclaimer: This article is for informational purposes only and does not constitute investment advice. Equity securities such as BlackBerry Limited carry market, execution, and macroeconomic risk, and past performance does not indicate future results. Readers should consult a qualified financial professional before making investment decisions. Prices, analyst targets, and operating figures are accurate as of publication.

Continue Reading

Trending