REINDEER GAMES
Corporate Conduct. Technical Evidence. Organizational Accountability.
Organizations make decisions. Systems operate within configurations, controls, and processes. People respond when problems are brought to their attention. Reindeer Games is the documentary collection examining those events, the available evidence, and what happens next.
What Is Reindeer Games?
Reindeer Games is an organizational and corporate-conduct collection within the Hunter Storm Independent Intelligence Research & Analysis Collection. It brings together documented events, technical observations, communications, historical records, and other source materials involving organizations and their responses to identified problems.
The collection spans cybersecurity, technology operations, infrastructure, customer support, corporate governance, institutional processes, and organizational accountability. It is designed to preserve a factual record that can be examined across individual incidents and over time.
Some organizations recognize a problem, investigate it, correct it, and improve. Others delay, deflect, repeat mistakes, or make an existing problem worse. The record should reflect what each organization actually does.
Systems and Infrastructure
Configuration, access controls, cybersecurity, data integrity, service availability, technical operations, and system behavior.
Corporate Conduct
Support interactions, escalation practices, governance, accountability, decision-making, and organizational responses.
Events Across Time
Earlier incidents, subsequent developments, repeated events, corrections, and documented changes in organizational behavior.
Resolution and Follow-Through
What was corrected, what remains unresolved, what commitments were fulfilled, and what can be independently verified.
Part of the Hunter Storm Independent Intelligence Research & Analysis Collection
Reindeer Games is not a separate evidence repository. It is a subject-area collection within the larger Hunter Storm Research (HSR), and documented within the Hunter Storm Evidence Repository (HSER), using the existing records-management architecture, and preserving the relationships among source materials, exhibits, publications, and analytical work.
Hunter Storm Evidence Repository (HSER)
The overarching documentary environment for source records, evidence, exhibits, chronologies, research artifacts, and related materials.
Reindeer Games
The organizational and corporate-conduct collection: incidents, company interactions, technical observations, responses, and outcomes.
Playing Reindeer Games
The existing publication series that discusses accuracy, intervention, integrity, and how documented events fit into the broader investigative picture.
The repository preserves the evidence. Reindeer Games organizes a subject area within that evidence environment. Playing Reindeer Games examines and explains the significance and relationships of documented events.
Foundational Platform Records
The initial entries in this collection include records involving Bing and Google. These are existing materials, not newly created claims. They remain part of the historical record and provide the starting point for the collection’s platform-related documentation.
Bing
Existing repository materialExisting Bing-related entries and observations are retained as source records. Their dates, original content, context, and associated evidence should be preserved when indexed in the repository.
Existing Google-related entries and observations are retained as source records. Additional observations can be appended as new entries without rewriting or replacing earlier records.
Search, Indexing, and Content Classification
Existing publications provide additional context for the platform-related record. These publications are related research, not substitutes for the original source entries.
- How Algorithmic Mislabeling Hides Helpful Content — Part 1: Yandex
- How Algorithmic Mislabeling Hides Helpful Content — Part 2: Google
- Google Site Kit Metrics Anomaly Analysis
- Cross-Platform Suppression Telemetry Inquiry — Part 1
- Cross-Platform Suppression Telemetry Inquiry — Part 2
- Cross-Platform Suppression Telemetry Inquiry — Part 3
New Google observations belong in the chronological record as new entries. Earlier observations should remain intact. Each entry should identify its source, date, context, and evidentiary limitations.
Organizations and Documented Interactions
This collection can include organizations across industries and time periods. A case record is not a verdict. It is an organized account of available documentation and subsequent developments.
GoDaddy — Hosting Environment and Support Escalation
Evidence documentation in progressThis record concerns observed filesystem permission values affecting selected image files on Black Star Institute and ZStormGirl, together with the associated image-display concerns and the support interaction.
The current observations include selected image files showing permissions of 666, other files showing 644, and directories showing 755. The reported scope is limited to selected images on two hosted properties; HunterStorm.com and SDSUG were reported unaffected.
The displayed file modification date does not, by itself, establish when a permission change occurred. File modification time and filesystem metadata-change time are distinct.
The cause of the permission changes, the identity of any responsible person or process, and the relationship between the permissions and the reported image-display behavior remain matters for investigation.
The support record includes the attempt to obtain incident documentation and the disagreement over troubleshooting and changes to the hosting environment before the current state had been documented.
Subsequent restoration, verification, provider responses, and available technical records can be added to the chronology.
Cisco
A place for documented Cisco-related interactions, technical issues, organizational responses, and subsequent developments. Individual incidents will be represented by their own source records.
Historical and Developing Cases
Other organizations may be added as their source records are identified and organized. Historical cases are welcome; the collection is not limited to recent events.
Connection to the Federal Whistleblower Record
Reindeer Games exists within the broader Hunter Storm Evidence Repository, which also preserves materials associated with the federal whistleblower documentary record and the development of The Storm Project.
The federal whistleblower materials provide historical, professional, and documentary context for portions of Hunter Storm’s research and investigative work. Reindeer Games may include records that are relevant to that larger context, as well as organizational cases that are entirely independent of the federal whistleblower matter.
Where a documented relationship exists, the relevant records can be cross-referenced. The existence of two records in the same repository does not, by itself, establish a common cause, actor, intent, or purpose.
Each record must be evaluated according to its own source, chronology, provenance, technical context, and evidentiary significance. Connections and hypotheses should be identified as such and should not be presented as established facts without supporting evidence.
Hunter Storm | Federal Whistleblower
The federal whistleblower hub provides the broader historical record, primary-source materials, timelines, and related research.
Documentation and Evidentiary Methodology
The purpose of this collection is to preserve facts and supporting materials. Analysis may identify questions, relationships, or competing explanations, but those interpretations must remain distinguishable from the underlying evidence.
Original Source Records
Preserve original correspondence, screenshots, documents, system observations, and other source artifacts.
Chronology
Record dates, sequence of events, discovery, actions, communications, and subsequent developments.
Technical Exhibits
Preserve relevant configuration information, permissions, metadata, logs, system behavior, and comparison records.
Organizational Responses
Record support interactions, escalation attempts, official explanations, corrections, and remediation.
Evidence Evaluation Sequence
-
Identify the observation
Establish exactly what was observed, where, and when. -
Preserve the source
Retain original records and distinguish them from later annotations, summaries, or derivative copies. -
Establish context
Identify the relevant system, organization, configuration, process, and known history. -
Compare the evidence
Identify affected and unaffected records, relevant differences, and alternative explanations. -
Document the response
Record what the organization said and did, including any explanation or remediation. -
Update the record
Append verified developments without silently replacing or rewriting the original historical record.
An observation is not an attribution. A correlation is not proof of causation. A hypothesis is not an established fact. The record must support the conclusion.
Organizational Conduct Over Time
Reindeer Games is not a permanent blacklist. Organizations can make mistakes, recognize them, correct them, and improve. Those actions are part of the record and deserve recognition.
Equally, repeated failures, inadequate responses, and decisions that compound an existing problem may become part of the documented history.
A case may therefore evolve. Its record can include an initial incident, subsequent explanations, corrections, verified remediation, recurrence, and long-term outcomes.
Corrective Action
Documented acknowledgment, meaningful remediation, and independently verifiable improvement.
Unresolved Issues
Outstanding questions, incomplete remediation, unavailable records, and matters requiring further review.
Repeated Events
Subsequent incidents or recurring conditions documented with their own dates and source materials.
Organizational Improvement
Evidence that an organization changed its processes and followed through over time.
Documentation Is Not Retaliation
Reindeer Games does not exist to punish organizations for making mistakes. It exists to preserve an accurate record of events, examine the available evidence, and document what organizations do when problems are brought to their attention.
What Happens Next Is Their Choice.
We document what happened. We preserve the evidence. We distinguish what is known from what remains unknown. We record subsequent actions and outcomes.
Accountability is not retaliation. Documentation is not punishment. Consequences are not necessarily something the person reporting a problem chose.
