Content Disclaimer

StrikeMap Is Not a Primary Source

StrikeMap is an aggregation and intelligence platform. We collect, enrich, and structure reports from third-party sources — we do not produce original reporting from the field. Every record on the platform originates from an external source: a Telegram channel, a news outlet, a government alert system, a satellite instrument, or a human contributor.

When you see an event on StrikeMap, you are seeing our structured interpretation of someone else's report. The underlying claim may be accurate, inaccurate, or somewhere in between.

Current Coverage

The platform currently focuses on the Iran/Israel/US conflict. Coverage of other conflicts and theaters will be added over time as the platform scales. The depth and completeness of our data reflects the sources available for this specific conflict and should not be assumed to generalize to other regions or theaters without equivalent source coverage.

Third-Party Data May Be Wrong

Our sources include social media channels, government feeds, news outlets, and satellite instruments. Each carries its own failure modes:

• Telegram channels — including official military channels — may post propaganda, exaggerations, premature claims, or deliberate misinformation.
• News outlets may report unverified claims from their own sources, apply editorial framing, or publish corrections after initial reporting.
• Government alert systems may issue false alerts or retract alerts after the fact.
• Satellite data detects thermal anomalies, not the cause of those anomalies. A hotspot may be a strike, a fire, industrial activity, or an instrument artifact.

Data on StrikeMap may be inaccurate, incomplete, delayed, or subsequently revised. We display what is reported, when it is reported, and update records as new information becomes available.

AI Enrichment Introduces Errors

Every report is processed through an AI enrichment pipeline that extracts structured data: locations, weapon types, attacking sides, targets, casualties, and damage assessments. This pipeline is not perfect.

• Location extraction can fail on ambiguous or colloquial place names, especially across languages. A report may be geolocated to the wrong city or the wrong country.
• Weapon classification from vague descriptions (“a missile,” “rockets”) is approximate and may be incorrect.
• Attribution of attacker and target relies on what the source states or implies, which may be wrong or deliberately misleading.
• Casualty figures from early reports are frequently revised — initial numbers are almost always unreliable.

We optimize for capturing information early and refining it as more sources report. Early records are less reliable than records that have been corroborated across multiple sources over time.

Not for Safety-Critical Decisions

Do not use StrikeMap to assess personal safety, make travel decisions, plan evacuations, or guide military or security operations.

The platform displays aggregated, unverified, AI-processed reports with known error rates and temporal delays. It is an informational and analytical tool — not a warning system, not a substitute for official civil defense alerts, and not a basis for decisions where inaccurate information could result in harm.

Always follow official government and military guidance for safety-critical matters.

Satellite Data Limitations

NASA FIRMS thermal anomaly data is used as a corroboration layer, not as proof of strikes. A thermal signature at a reported strike location increases confidence in the report but does not confirm it — the heat source could be unrelated to the reported event.

Conversely, the absence of a thermal anomaly does not disprove a strike. Cloud cover blocks satellite detection. Small munitions may not produce a detectable signature. Satellite passes have temporal gaps — events that occur between passes are missed entirely.

Source Reliability Varies

Not all sources on StrikeMap carry equal weight. Official government alert systems (like Tzofar) have high reliability for their specific domain. Satellite instruments produce objective measurements with known error margins. Vetted analyst entries undergo human review.

Telegram channels, by contrast, range from official military communications to anonymous aggregators of unknown reliability. The platform ingests all of these without editorially filtering, because even low-confidence sources sometimes carry unique information that is later corroborated.

We do not independently verify all reports. When source attribution is displayed, evaluate it accordingly.

Deduplication Is Imperfect

The deduplication system identifies when multiple reports describe the same real-world event and merges them into a single record. This process uses semantic analysis and spatiotemporal clustering, and it is not infallible.

• Distinct events occurring at similar locations within a short time window may be incorrectly merged into one record.
• The same event described in very different terms across sources may fail to be recognized as a duplicate, resulting in separate records for the same incident.

Both types of errors are expected at a low rate. If you notice a deduplication error, you can report it through the Platform's feedback mechanisms.

Our Commitment

Acknowledging limitations is not a disclaimer of responsibility — it is part of how we build trust. We are transparent about what we know, what we don't know, and where our systems can fail, because an intelligence platform that conceals its limitations is worse than useless.

For a detailed description of our data sources and their characteristics, see Our Data.