
This is the second installment in a series on Google and the architecture of information control. The first article, “Google and the Architecture of Information Control,” examined Google’s ranking and recommendation power, the institutional politics of its trust and safety apparatus, and the destruction of internal evidence documented in federal antitrust proceedings. That prior reporting is assumed. This article advances the inquiry into the accountability problem created when cohort-level classification, recommendation-system intervention, psychological-harm foreseeability, and communications spoliation converge inside the same institution.
What does it mean when a corporation builds systems capable of classifying people into cohorts, altering what those cohorts see, and modulating safety interventions — while also maintaining internal communications practices that federal courts later criticized for destroying vast quantities of potentially relevant evidence?
That is not a rhetorical question. It is a structural one, and the documented record now permits it to be asked with precision.
Between 2017 and 2019, Google and YouTube trust and safety culture was influenced by asymmetric harm concepts: the idea that the same speech, directed at different targets, may carry different social meaning depending on power, vulnerability, and protected status. Public enforcement controversies during that period suggested that identity-, power-, and vulnerability-sensitive judgments affected moderation outcomes. The public record does not establish that Google implemented code-level demographic harm thresholds, nor that YouTube safety filters were formally calibrated by demographic cohort.
During the same institutional window, however, Google operated infrastructure capable of classifying users and content at scale, ranking and re-ranking information flows, and deploying targeted interventions. During the same period, the broader recommender-systems literature documented psychological harm mechanisms: distress amplification, relapse triggers, crisis-adjacent recommendations, and what researchers call “algorithmic cruelty.” Google and YouTube publicly acknowledged related risks through recommendation changes, crisis-resource panels, suicide-prevention search interventions, and time-management tools. And during the same period, Google’s legal leadership maintained chat-retention practices later criticized in federal litigation for destroying relevant internal communications.
The argument that follows does not prove — and does not claim — that Google intentionally weaponized recommendation systems against demographic cohorts. It establishes something narrower and, for accountability purposes, more durable: the capability existed; the institutional preconditions made cohort-level differential treatment structurally plausible; and the communications practices criticized by federal courts may leave investigators unable to reconstruct whether such harm occurred. Capability, precondition, impunity. The article proves the accountability void, not the intentional targeting.
I. The Asymmetric Harm Doctrine
The foundation of the harm vector described in this article is not a technical system. It is a policy-cultural premise: that the meaning of “harm” can depend on the social position of the speaker, the target, and the audience.
Traditional content moderation is often described in identity-neutral terms: evaluate the content, the threat, the slur, the deception, the incitement. In practice, platforms have always made context-sensitive judgments. YouTube’s own harassment policy, for example, distinguishes protected-group targeting, threats, minors, public-interest context, scripted performance, and attacks on high-profile figures.1 That is not inherently illegitimate. Content moderation cannot be done without context.
The problem emerges when context becomes asymmetric protection. Between 2015 and 2019, Google and YouTube’s trust and safety culture operated in an environment where “punching up” and “punching down” concepts were widely used to distinguish criticism of powerful groups from abuse of vulnerable groups.2 In public-facing policy terms, this is usually expressed as protection for vulnerable users or protected groups. In contested enforcement cases, critics saw something more volatile: a platform culture in which the perceived identity or social power of the target could influence whether speech was treated as harassment, satire, political commentary, or protected expression.
The public record supports the existence of this cultural and policy controversy. It does not establish a code-level implementation of demographic thresholds. The 2019 Steven Crowder-Carlos Maza dispute on YouTube is the clearest public example: YouTube initially concluded that Crowder’s conduct did not violate its harassment policy, then demonetized the channel after public backlash, while commentators debated whether the platform was applying its harassment rules consistently or making ad hoc judgments under social and political pressure.3 That episode does not prove an internal “punching up” runbook. It does show the kind of enforcement ambiguity that asymmetric harm concepts introduce.
The ethical implications are contested. Proponents argue that historical oppression justifies heightened protection for vulnerable groups. Critics identify a structural error that social science methodology has long recognized as the ecological fallacy — the inference, formalized by Robinson in 1950, that aggregate characteristics of a group can be attributed to every individual within it.4 Applied to platform governance, the risk is simple: a system that sees cohort membership may miss individual vulnerability. A working-class user, a socially isolated user, or a user in a crisis state can be categorized as “privileged” by group identity even when their actual circumstance is one of vulnerability.
This article is not primarily about whether asymmetric moderation is moral. It is about what happens when asymmetric safety concepts meet personalized delivery systems. If moderation thresholds, demotion rules, harassment judgments, or recommendation-safety interventions are influenced by the perceived identity or vulnerability of the target, then delivery systems can inherit those judgments. A speech rule becomes a distribution rule. A distribution rule becomes a feed-level exposure pattern.
The claim here is therefore conditional and structural. If identity- or power-sensitive judgments were applied to recommendation safety, then users in less-protected cohorts could receive content that would have been demoted, interrupted, or removed for other cohorts. The public record supports that as a plausible mechanism. It does not establish that Google or YouTube actually applied such thresholds in code, policy runbooks, or safety-filter configuration.
That distinction — between speech policy and delivery policy — is the mechanism that turns a moderation philosophy into a potential vector for cohort-level psychological harm.
Evidentiary note: Documented fact: YouTube policies and public controversies show context-sensitive enforcement, protected-group analysis, public-interest exceptions, and contested harassment judgments. Source-supported inference: asymmetric harm concepts influenced the trust and safety environment. Structural plausibility: such concepts could affect recommendation-safety delivery if encoded in thresholds, labels, review guidance, or intervention rules. Not established by the public record: formal Google code-level demographic safety thresholds, formal “punching up” runbooks, or proof of cohort-calibrated safety-filter application.
II. The Cohort as Target
The harm vector described above requires a technical precondition: the ability to classify users or content into cohorts, score them, and alter delivery based on those classifications. That capability is not hypothetical. It is the operational foundation of modern advertising and recommendation systems.
Google’s commercial infrastructure — Google Ads, Display & Video 360, YouTube advertising, and the broader programmatic stack — is built on targeted delivery. Google’s own advertising materials describe audience tools that help advertisers reach users based on passions, topics they are actively researching, custom audiences built from keywords and websites, location, search intent, and other real-time signals.5 Google’s Privacy Sandbox work on Federated Learning of Cohorts (FLoC) likewise proposed clustering large groups of people with similar interests for interest-based advertising while hiding individuals “in the crowd.”6 The point is not that FLoC was sinister. The point is that cohort formation was an explicit design primitive.
The May 2024 Google Search API documentation leak sharpened the architectural picture. Analyses by SparkToro and iPullRank reported more than 2,500 pages of API documentation, 14,014 attributes across 2,596 modules, references to NavBoost and click-based systems, siteAuthority, quality signals, classifiers, whitelists, and re-ranking components.7 The leak documented complexity and granularity in Google’s ranking infrastructure. It did not prove that demographic cohort attributes were used to modulate psychological-safety thresholds. It did not prove YouTube recommendation abuse. Its relevance is architectural: Google possessed systems for classification, scoring, ranking, re-ranking, and intervention at scale.
The intersection of advertising audiences, recommendation ranking, and safety intervention creates the technical architecture for cohort-level content modulation. The public record establishes capability. It does not establish misuse. A system that can identify likely interest, vulnerability, intent, geography, device class, content category, or user segment can also alter what is shown, demoted, interrupted, or promoted for that segment. Whether Google used that architecture to apply asymmetric psychological-safety thresholds is the unresolved question.
Google’s own public work confirms that classification-triggered intervention was an accepted operational pattern. In 2019 written testimony to the Senate Commerce Committee, Google’s Derek Slater described Alphabet’s Jigsaw Redirect Method as using targeting tools and curated YouTube playlists to disrupt online radicalization. Jigsaw’s public materials describe “Info Interventions” designed to interrupt online harms, including the Redirect Method’s use of counter-narrative videos.8 This was not merely deletion after the fact. It was a targeted content-delivery intervention based on inferred user intent or susceptibility.
The Redirect Method was presented as a benign intervention — steering users away from violent extremism and toward counter-speech. It may well have been benign in its specific implementation. But the architecture is directionally neutral. A system that can identify users likely to be receptive to extremist content and steer them toward counter-messaging can, with different targeting criteria and different content destinations, steer a different cohort toward a different psychological environment.
The Redirect Method does not prove misuse. It demonstrates that classification-triggered content intervention was an accepted operational pattern.
The question this section raises is therefore not whether Google could classify users into cohorts or adjust content delivery. That is established. The question is whether the safety judgments discussed in Section I were ever operationalized at the cohort level in recommendation systems, such that a user’s classification affected whether crisis-adjacent, distressing, or psychologically destabilizing content was intercepted, downranked, or delivered.
Evidentiary note: Documented fact: Google operated audience-targeting systems, cohort-based advertising proposals, ranking/re-ranking systems, and targeted counter-messaging interventions. Source-supported inference: these capabilities are sufficient for cohort-level content modulation. Structural plausibility: those systems could be connected to safety thresholds. Not established by the public record: demographic recommendation-safety modulation, intentional psychological targeting, or the use of the API-leak attributes for cohort-level psychological harm.
III. The Psychological Harm Capability
The systems described above would be concerning but abstract without a third element: a known mechanism of harm. Recommendation systems can amplify distress, relapse triggers, crisis-adjacent content, self-harm ideation, eating-disorder material, and other psychologically destabilizing loops. That claim does not require proof of Google-specific intent. It is established in the broader recommender-systems and human-computer-interaction literature.
Milton and Chancellor’s 2022 paper, “The Users Aren’t Alright: Dangerous Mental Illness Behaviors and Recommendations,” states the problem directly: recommendation systems are “in a unique position” to propagate dangerous and cruel behaviors to people with mental illnesses.9 The paper discusses “algorithmic cruelty,” the risk of recommender systems triggering relapse or exacerbating symptoms, and examples where products or content become harmful in combination. One example involved Amazon recommendations pairing two otherwise available chemical products into a combination associated with suicide methods. The point is not that Amazon intended that result. The point is that recommender systems can generate dangerous outputs without human intent because they optimize association, co-occurrence, engagement, or predicted relevance rather than safety in context.
That distinction matters. The psychological harm literature establishes mechanism, not Google-specific malice. It shows that engagement-driven or association-driven systems can push vulnerable users deeper into harmful loops. It does not show that Google intentionally targeted any cohort with those loops.
Google-specific awareness is established in a narrower way. YouTube publicly acknowledged that recommendation systems could recommend “borderline content” and “content that could misinform users in harmful ways,” and in 2019 announced demotion changes for such recommendations.10 YouTube has also offered take-a-break and bedtime reminders, including defaults for younger users, and Google Search has long placed suicide-prevention resources at the top of relevant search results.10 These interventions do not prove intentional targeting. They do prove foreseeability: Google and YouTube understood that product design, ranking, reminders, and search-result intervention could affect user wellbeing and crisis outcomes.
The critical analytical point is the intersection of this foreseeable harm with the two capabilities documented above. Google and YouTube had the ability to classify users, score content, re-rank recommendations, and deploy targeted interventions. Their trust and safety culture operated amid asymmetric harm concepts. Recommendation systems are known to create psychological harm loops. Together, those facts create the structural precondition for a specific risk: differential exposure to psychologically harmful content if safety thresholds or interventions were applied unevenly across cohorts.
This article does not assert that this harm was intentionally engineered. It establishes that the capability existed, that the institutional knowledge to understand its consequences existed, and that public controversies suggested asymmetric moderation judgments may have affected enforcement in practice. Whether the capability was ever activated — whether any user classified within a less-protected demographic cohort received psychologically harmful content that would have been intercepted for a user in a protected cohort — may be unreconstructable from the available record because of the evidence destruction practices documented in Section V.
Evidentiary note: Documented fact: the broader literature establishes recommender-system harm mechanisms; YouTube and Google publicly deployed wellbeing, borderline-content, and crisis-resource interventions. Source-supported inference: Google had institutional awareness that ranking and recommendation design can affect user wellbeing. Structural plausibility: those mechanisms could be applied differently across cohorts. Not established by the public record: Google-specific intent to induce psychological harm, internal decisions to trade off vulnerable-user safety by demographic cohort, or a deployed demographic psychological-harm system.
IV. The 2018 Convergence
The three elements documented above — asymmetric harm concepts, cohort-level classification/intervention architecture, and known recommender-system harm mechanisms — matured within the same institution during a period of intense internal and external pressure over speech, identity, extremism, misinformation, and platform responsibility.
The 2017-2019 window was an institutional risk condition. The firing of James Damore in August 2017 and later litigation made public a contested set of internal communications and allegations about ideological conformity, internal blacklists, and hostility toward disfavored political views.11 Those allegations were disputed, and they do not prove that trust and safety personnel misused recommendation systems. But they are relevant to institutional vulnerability: they show a workplace environment in which political identity, diversity policy, and internal dissent were not abstract issues. They were sources of professional conflict.
At the same time, YouTube’s trust and safety apparatus became more proactive. In September 2019, Google’s Derek Slater told the Senate Commerce Committee that YouTube relied on machine learning, human experts, an Intel Desk that proactively looked for emerging policy-violating trends, and a Trusted Flagger program through which expert NGOs and governments could notify YouTube of bad content in bulk. He also described the Redirect Method as a targeted counter-radicalization intervention using targeting tools and curated YouTube playlists.12
That scale and posture matter. A trust and safety system with machine review, human reviewers, proactive threat scanning, expert flaggers, and targeted counter-messaging is not merely reactive. It is an active information-management infrastructure. It decides what is removed, what is demoted, what is recommended, what is interrupted, what is contextualized, and what is routed to specialized review.
The convergence of these factors does not prove a secret program. It creates elevated plausibility and elevated accountability need. During the same window, the technical capability for cohort-level intervention existed; public controversies showed the instability of asymmetric moderation judgments; recommender-system harm mechanisms were foreseeable; and chat-retention practices capable of erasing granular operational deliberations were already in place.
This is the structural core of the article’s argument. The convergence is a risk condition, not proof of abuse; elevated plausibility, not an accusation that every engineer or reviewer acted ideologically. Systems with classification, intervention, psychological impact, and disappearing internal records require external audit.
Evidentiary note: Documented fact: the Damore litigation and reporting made public allegations and internal communications showing ideological conflict; Slater’s testimony documented machine enforcement, expert review, the Intel Desk, Trusted Flaggers, and the Redirect Method. Source-supported inference: this environment increased the need for auditability around trust and safety interventions. Not established: that Intel Desk personnel executed demographic psychological targeting, that Trusted Flaggers bypassed safety systems for such targeting, or that any specific cohort was intentionally harmed.
V. The Spoliation as Impunity Architecture
The prior Oahu Underground audit documented the Walker Memo, the “history off” default, and the federal courts’ findings regarding Google’s systematic destruction of evidence. This section does not re-litigate those findings. It advances them to their logical terminus as applied to the specific harm vector described in this article.
The timeline is worth restating in compressed form because its implications for the present analysis are specific and damning.
In September 2008, a memo sent to Googlers by Bill Coughran and Kent Walker announced that, because Google was in the midst of significant legal and regulatory matters and because written communications could become subject to discovery, Google would make “off the record” the corporate default setting for Google Talk. The memo told employees that “on the record” conversations would become part of Google’s long-term document storehouse and instructed employees under litigation hold to make covered chats “on the record.”13
The practical result, as later described in federal litigation, was that many Google chats were history-off by default and deleted after 24 hours unless preserved. In the Play Store antitrust litigation, Judge James Donato found that sanctions were warranted, that history-off chats were deleted forever and could not be recovered, that Google employees routinely used Chat for substantive business topics, and that Google had effectively adopted a “don’t ask, don’t tell” policy for chat preservation.14
Judge Amit Mehta, in the Google Search antitrust case, declined to impose the requested sanctions because they did not change his liability analysis. But he did not bless the practice. He wrote that the court was “taken aback by the lengths to which Google goes to avoid creating a paper trail for regulators and litigants” and warned that any company putting the burden on employees to identify and preserve relevant evidence “does so at its own peril.”15
The forensic consequences are now partly quantified, with important limits. In a supplemental expert report filed in the Texas ad-tech litigation, Jacob Hochstetler analyzed a 68-day Google Chat metadata dataset covering five employees. He estimated that more than 87 percent of messages in that dataset — at least 18,566 out of about 21,269 — were not preserved; that 94.5 percent of conversations had chat history off for at least some portion of the relevant period; and that for Sundar Pichai, 94.2 percent of sent and received messages captured before Google’s February 2023 default change had the retention field set to history off.16 Those figures should not be misstated as a companywide percentage. They are dataset-specific. They are still devastating.
These findings, devastating as they are in the antitrust context, take on a different and more disturbing dimension when applied to the harm vector documented in this article.
Recommendation and trust and safety decisions are often granular. They involve policy interpretation, classifier labels, escalation channels, reviewer guidance, threshold adjustments, launch decisions, risk acceptances, and emergency exceptions. These are precisely the kinds of operational decisions likely to be discussed in chat, meeting notes, and informal internal coordination. If the question is whether a particular safety threshold, demotion rule, or intervention was applied differently across cohorts, the most probative evidence may not be a public policy page. It may be the internal deliberation that explains why a threshold was set, who requested it, which cohorts were affected, what risk was accepted, and what objections were raised.
That is why spoliation is the evidentiary anchor of this article. The destruction of chat history does not prove psychological targeting. It creates the conditions under which such targeting, if it occurred, may be impossible to reconstruct. It is the difference between “unproven” and “unauditable.” A corporation can say no evidence proves misuse. But where courts have found that relevant categories of evidence were not preserved, absence of evidence loses much of its exculpatory force.
Whether this parallel development was intentional — whether the spoliation architecture was designed with awareness that it would also shield granular content-governance decisions — is a question this article cannot answer. The documented record establishes the structural convergence. Intent is among the things the missing records may have rendered unknowable.
VI. The National Security / Insider Misuse Dimension
An unauditable influence infrastructure is not only a civil-accountability problem. It is a security problem.
Any infrastructure capable of cohort-level influence is exposed to insider misuse, compromised-access risk, and unauthorized intervention. That is true even if the original system was built for benign purposes: ad targeting, counter-radicalization, misinformation response, crisis support, or recommendation quality. The same tools that can identify and steer a vulnerable cohort for protective reasons can be abused by someone with sufficient access, authority, or control-plane knowledge.
The national-security implication is therefore narrow and concrete. If the same communications gaps that impaired civil discovery also impair reconstruction of operational content interventions, then investigators assessing insider misuse, compromised accounts, or foreign exploitation would face the same evidentiary deficit. The issue is not that foreign exploitation has been proven. It has not. The issue is that an undocumented or poorly preserved influence infrastructure would make exploitation harder to detect after the fact.
Federal investigators do not need proof of a secret master plan to treat that as a security concern. They need only recognize the risk created by the combination of cohort-level intervention capability and inadequate audit trails.
Evidentiary note: Documented fact: Google possessed large-scale ranking, recommendation, classification, and intervention capabilities; courts criticized and sanctioned failures to preserve relevant chats in major litigation. Source-supported inference: missing operational communications would hinder reconstruction of sensitive content-governance decisions. Speculative implication: insider misuse, compromised access, or foreign exploitation could exploit such opacity. Not established: that any foreign intelligence service exploited Google’s recommendation systems.
VII. The Accountability Void
The harm vector documented in this article — the potential for asymmetric, cohort-level delivery of psychologically harmful content through algorithmically mediated recommendation systems, combined with serious audit-trail gaps — falls into a regulatory void that existing legal frameworks were not designed to address.
The Murthy v. Missouri decision, in which the Supreme Court held that the plaintiffs lacked Article III standing for broad claims of government pressure on platforms, illustrates the proof problem.17 Even where government-platform contact is documented, plaintiffs must show a particularized injury traceable to challenged conduct and likely to be redressed by a court. Cohort-level recommendation harm is even harder. The exposure pattern may be statistical. The affected group may be inferred rather than named. The intervention may be automated. The decisive deliberation may have occurred in chat.
Judge Mehta’s 2024 liability opinion in U.S. v. Google established Google’s monopoly power in general search services and general search text advertising and criticized its chat-preservation failures. But that case operated within antitrust law. Antitrust remedies address market competition, defaults, distribution, data access, and exclusionary conduct. They do not directly answer whether a platform used demographic classification to apply asymmetric psychological-safety thresholds in recommendation systems.
Current privacy frameworks address collection, processing, sale, sharing, deletion, and access to personal data. They are not built to answer whether a platform adjusted safety thresholds, demotion rules, or recommendation interventions differently for one cohort than another. A user may be able to request data access or deletion. They cannot easily compel an audit of whether the safety architecture treated their cohort differently.
The structural inadequacy is comprehensive. Existing law struggles with a harm that is delivered algorithmically rather than by a named human actor, aimed at a cohort rather than an identified individual, implemented through ranking or safety-threshold modulation rather than overt content creation, and made difficult to reconstruct by missing internal communications. Each characteristic complicates accountability. Their combination creates the void.
This is not a failure of judicial will. Judge Mehta’s opinion made clear his concern about Google’s evidence destruction practices. It is a failure of regulatory architecture. The legal frameworks available to the judiciary were designed for a world in which harm is caused by identifiable actors, directed at identifiable victims, and documented in recoverable evidence. The harm described in this article fits none of those categories cleanly.
What the Record Establishes
The documented record, as examined across this article and the prior Oahu Underground audit, establishes the following:
Google and YouTube trust and safety culture during the 2017-2019 period was influenced by asymmetric harm concepts. Public enforcement controversies suggested that identity-, power-, and vulnerability-sensitive judgments affected moderation outcomes. The record does not establish code-level demographic thresholds.
Google maintained infrastructure capable of audience classification, content scoring, ranking, re-ranking, and targeted intervention. This capability was documented through advertising products, FLoC, the Redirect Method, YouTube recommendation changes, and the May 2024 API leak. The API leak supports ranking-architecture complexity; it does not prove demographic psychological-safety modulation.
The broader recommender-system literature establishes mechanisms of psychological harm, including algorithmic cruelty, relapse triggers, distress loops, and crisis-adjacent recommendation risk. Google and YouTube’s public wellbeing, borderline-content, and crisis-resource interventions establish foreseeability and institutional awareness of related harm mechanisms. They do not establish intentional targeting.
These elements converged during a period of institutional polarization and proactive trust and safety expansion. That convergence is a risk condition, not proof of deployment.
Throughout this period, Google maintained chat-retention practices originating in the 2008 Walker/Coughran memo. Courts later criticized or sanctioned Google’s failure to preserve chats. A dataset-specific expert report in ad-tech litigation estimated that, within a 68-day dataset for five employees, more than 87 percent of messages were not preserved and 94.5 percent of conversations had history off for at least some portion of the period. Those numbers should be read precisely: they are not a global corporate destruction percentage. They are evidence of severe preservation failure in a relevant sample.
The record does not establish — and this article does not claim — that Google intentionally weaponized its recommendation systems to deliver targeted psychological harm to specific demographic cohorts. What the record establishes is that the capability existed, the institutional conditions made its deployment conceivable, and the evidence destruction apparatus creates a serious risk that the question of whether it was deployed cannot be answered through ordinary discovery.
That unanswerability is not an accidental gap in the historical record. It is tied to a deliberate corporate communications policy, maintained through litigation and criticized by federal judges in multiple proceedings.
The convergence is not an allegation of a secret master plan. It is a structural account of documented capabilities, incentives, and missing records. And it is a structural reality that existing legal and regulatory frameworks are poorly equipped to address — because the harm it describes is algorithmic, cohort-level, and potentially unrecoverable from the records Google failed to preserve.
That void — the space between what the architecture made possible and what the spoliation may have made unknowable — is not a gap that journalism can close. It is a gap that demands federal investigation, conducted with subpoena power, forensic technical capability, and a mandate that extends beyond antitrust remedies to the national security implications of infrastructure capable of cohort-level psychological targeting with substantial audit opacity. The documented record is sufficient to justify that investigation. Whether the political will exists to undertake it is the only remaining question.
YouTube Help, “Harassment & cyberbullying policies,” including protected-group status, minors, public-interest exceptions, scripted performance, and heightened treatment of malicious insults based on protected-group status, https://support.google.com/youtube/answer/2802268?hl=en. ↩︎
Emily McTernan, “The Ethics of Offensive Comedy: Punching Down and the Duties of Comedians,” Royal Institute of Philosophy Supplements 96 (2024): 81-100, https://www.cambridge.org/core/journals/royal-institute-of-philosophy-supplements/article/ethics-of-offensive-comedy-punching-down-and-the-duties-of-comedians/A5B6FAAD512460544CB5A4D3127DE96A. ↩︎
Techdirt, “The Impossibility of Content Moderation Plays Out, Once Again, on YouTube” (June 7, 2019), https://www.techdirt.com/2019/06/07/impossibility-content-moderation-plays-out-once-again-youtube/; Nick Statt, “YouTube decides that homophobic harassment does not violate its policies,” The Verge (June 5, 2019), https://www.theverge.com/2019/6/4/18653088/youtube-steven-crowder-carlos-maza-harassment-bullying-enforcement-verdict. ↩︎
Robinson, W.S., “Ecological Correlations and the Behavior of Individuals,” American Sociological Review 15, no. 3 (1950): 351-357 — foundational formalization of the ecological fallacy in social science methodology. ↩︎
Google Ads Help, “About audience segments,” describing audience segments based on identity, interests, habits, active research, business interaction, custom segments, demographics, life events, and in-market behavior, https://support.google.com/google-ads/answer/2497941?hl=en. ↩︎
Google Ads & Commerce Blog, “Building a privacy-first future for web advertising” (Jan. 25, 2021), discussing FLoC and interest-based cohorts, https://blog.google/products/ads-commerce/2021-01-privacy-sandbox/. ↩︎
Rand Fishkin, “An Anonymous Source Shared Thousands of Leaked Google Search API Documents with Me; Everyone in SEO Should See Them,” SparkToro (May 27, 2024), https://sparktoro.com/blog/an-anonymous-source-shared-thousands-of-leaked-google-search-api-documents-with-me-everyone-in-seo-should-see-them/; Mike King, “Secrets from the Algorithm: Google Search’s Internal Engineering Documentation Has Leaked,” iPullRank (May 2024), https://ipullrank.com/google-algo-leak. ↩︎
Written Testimony of Derek Slater, Director, Information Policy, Google LLC, Senate Commerce Committee hearing, “Mass Violence, Extremism, and Digital Responsibility” (Sept. 18, 2019), https://www.commerce.senate.gov/services/files/b74be056-4446-470b-8b3c-f2e4463afb66; Google/Jigsaw, “Info Interventions,” https://interventions.withgoogle.com/static/pdf/Google-Jigsaw_Info-Interventions.pdf. ↩︎
Ashlee Milton and Stevie Chancellor, “The Users Aren’t Alright: Dangerous Mental Illness Behaviors and Recommendations,” arXiv:2209.03941 (2022), https://arxiv.org/abs/2209.03941; PDF, https://ashleemilton.github.io/files/users2022facctrec.pdf. ↩︎
YouTube Blog, “Continuing our work to improve recommendations on YouTube” (Jan. 25, 2019), https://blog.youtube/news-and-events/continuing-our-work-to-improve/; YouTube Help, “Take a break reminder,” https://support.google.com/youtube/answer/9012523?hl=en-GB; YouTube Help, “Set a bedtime reminder,” https://support.google.com/youtube/answer/9884905?co=GENIE.Platform%3DAndroid&hl=en; Google Search Blog, “Suicide prevention resources on Google Search,” https://blog.google/products-and-platforms/products/search/suicide-prevention-resources-on-google-search/. ↩︎ ↩︎
Damore et al. v. Google LLC, Complaint, Santa Clara County Superior Court (Jan. 8, 2018), via Courthouse News, https://www.courthousenews.com/wp-content/uploads/2018/01/Damore-Google-COMPLAINT.pdf; see also TechCrunch, “James Damore just filed a class action lawsuit against Google…” (Jan. 8, 2018), https://techcrunch.com/2018/01/08/james-damore-just-filed-a-class-action-lawsuit-against-google-saying-it-discriminates-against-white-male-conservatives/. ↩︎
Slater testimony, supra note 7, describing machine flagging, expert review, the Intel Desk, the Trusted Flagger program, and the Redirect Method. ↩︎
Trial Exhibit UPX1101, United States v. Google LLC, No. 1:20-cv-03010 (D.D.C.), “Business communications in a complicated world” (Sept. 16, 2008), https://www.justice.gov/atr/media/1322046/dl?inline=; Plaintiffs’ Post-Trial Brief, United States v. Google LLC, ECF No. 837, section VIII, https://www.justice.gov/atr/media/1340241/dl?inline=. ↩︎
In re Google Play Store Antitrust Litigation, 664 F. Supp. 3d 981 (N.D. Cal. 2023), sanctions order by Judge James Donato, https://www.ebglaw.com/assets/htmldocuments/noindex/IN%20RE%20GOOGLE%20PLAY%20STORE%20ANTITRUST%20LITIGATION%20664%20F.%20Supp.%203d%20981%20-%20Dist.%20Court%20ND%20California%202023%20-%20Google%20Scholar.pdf. ↩︎
United States v. Google LLC, Memorandum Opinion, No. 1:20-cv-03010-APM (D.D.C. Aug. 5, 2024), especially Intent and Sanctions, https://storage.courtlistener.com/recap/gov.uscourts.dcd.223205/gov.uscourts.dcd.223205.1033.0_3.pdf. ↩︎
Jacob Hochstetler, Supplemental Expert Report, State of Texas et al. v. Google LLC, No. 4:20-cv-957-SDJ (E.D. Tex.), filed Jan. 31, 2025, https://storage.courtlistener.com/recap/gov.uscourts.txed.202878/gov.uscourts.txed.202878.793.1.pdf; Plaintiffs’ Motion for Adverse Inference, ECF No. 752, https://ppc.land/content/files/2025/01/gov.uscourts.txed.202878.752.0_2.pdf. ↩︎
Murthy v. Missouri, 603 U.S. ___ (2024), Supreme Court opinion, https://www.supremecourt.gov/opinions/23pdf/23-411_3dq3.pdf. ↩︎