Inference Investigation (External Handoff)

Claim investigated: Carbyne is incorporated in Israel and has a U.S. headquarters in New York. Its Israeli corporate structure means that the company and its data practices are subject to Israeli law as well as U.S. law — a jurisdiction whose intelligence-sharing arrangements with the NSA and Five Eyes are extensive but not fully public. Entity: Carbyne Original confidence: inferential Result: STRENGTHENED → SECONDARY Source: External LLM (manual handoff)

Assessment

The claim is factually accurate on corporate structure—Carbyne Ltd. is an Israeli-registered company (company number 515106409) and Carbyne, Inc. is a Delaware entity with its principal place of business in New York—making it subject to both Israeli and U.S. jurisdiction. The inference that Israeli intelligence-sharing with the NSA is extensive but not fully public is well-supported by leaked NSA documents. However, the claim implies a jurisdictional risk to U.S. 911 data that, while logically plausible, is not directly evidenced by any public record showing Israeli intelligence access to Carbyne systems or data.

Reasoning: Primary sources confirm Carbyne operates through a dual corporate structure: Carbyne Ltd. (Israeli-registered, company number 515106409) and Carbyne, Inc. (a Delaware non-practicing entity with principal place of business in New York) . Carbyne officially relocated its headquarters from Israel to New York in October 2019 while retaining R&D in Tel Aviv . Its terms and conditions explicitly reference 'Carbyne Ltd., Carbyne, Inc. or Carbyne911 Mexico S. de RL de CV' as contracting entities . The Israeli corporate entity is subject to Israeli law, including the Protection of Privacy Law and national security statutes. The Snowden leaks documented extensive SIGINT sharing between the NSA and Israeli SIGINT National Unit (ISNU), including 'information on access, intercept, targeting, language, analysis and reporting,' with Israel described as enjoying 'expanded geographic access to world-class NSA cryptanalytic and SIGINT engineering expertise' . Israel is also described as an observer to Five Eyes . However, no public record confirms that Israeli intelligence has accessed Carbyne's U.S. 911 data, or that such data is stored or processed in Israel rather than in U.S. AWS regions. The inference therefore rests on corporate structure and known intelligence relationships, not on direct evidence of data access.

Underreported Angles

• Carbyne's contractual documents reveal a tripartite corporate structure—Carbyne Ltd. (Israel), Carbyne, Inc. (Delaware/New York), and Carbyne911 Mexico S. de RL de CV—which means jurisdiction over customer data may vary by contract and geography .
• The 2024 EU adequacy decision for Israel was criticized by human rights experts for overlooking Israeli national security legislation that permits bulk surveillance and lacks independent oversight, raising questions about whether Israeli-registered companies can effectively resist intelligence agency data demands .
• Israel's Amendment 13 to the Protection of Privacy Law (effective August 2025) significantly expanded the Privacy Protection Authority's enforcement powers while maintaining broad national security exceptions, creating a tension between commercial data protection and state surveillance authority .
• Carbyne's platform is built on AWS cloud infrastructure, but the company has not publicly disclosed which AWS regions host U.S. 911 call data, leaving unanswered whether such data ever transits or resides in Israeli jurisdiction .
• The pending $625 million acquisition of Carbyne by Axon (announced November 2025, expected to close Q1 2026) could alter jurisdictional exposure, yet the deal's regulatory filings have not addressed data sovereignty or Israeli intelligence access risks .
• No U.S. state contract or federal procurement record publicly reviewed requires Carbyne to certify that U.S. emergency call data is inaccessible to foreign intelligence services or stored exclusively in U.S. territory.

Public Records to Check

• Companies House: Carbyne Ltd. Israel company registration 515106409; corporate filings and beneficial ownership Would confirm the exact Israeli corporate structure, directors, and whether U.S. subsidiaries are wholly owned, clarifying control and jurisdictional hierarchy.

• other: Delaware Division of Corporations entity search for 'Carbyne, Inc.' filing history and registered agent Would establish the incorporation date, corporate parentage, and legal relationship between the U.S. and Israeli entities.

• SEC EDGAR: Axon Enterprise SEC filings regarding Carbyne acquisition (Form 8-K, S-4, proxy) for data governance and CFIUS-related disclosures A transaction involving an Israeli company handling U.S. critical infrastructure data may trigger CFIUS review or data-security representations.

• other: FOIA to NHTSA/FCC/state 911 agencies: Carbyne data residency and sovereignty certifications in contract submissions Would confirm whether U.S. government customers have contractually required that 911 data remain in U.S. jurisdiction.

• other: AWS Partner Network or case studies confirming AWS regions used for Carbyne US deployments Would verify whether U.S. 911 data is stored in U.S.-based AWS regions or potentially replicated internationally.

• other: Israeli Privacy Protection Authority database registry for Carbyne Ltd. (if publicly accessible) Would reveal what databases Carbyne has registered in Israel and whether they include foreign-origin emergency call data.

• LDA: Lobbying disclosures by Axon or Carbyne regarding CFIUS, foreign investment review, or data sovereignty legislation Would indicate whether the companies have sought to influence policy on intelligence access or foreign ownership of emergency data infrastructure.

Significance

SIGNIFICANT — The claim highlights a genuine jurisdictional ambiguity: a company processing 150 million annual U.S. emergency calls maintains an active Israeli corporate entity and R&D presence, while U.S. contracting law does not appear to require public disclosure of where that data resides or whether foreign intelligence access is contractually precluded. Correcting the record from 'inferential' to 'secondary' matters because the corporate structure and intelligence-sharing relationships are verifiable, even if the ultimate data-access risk remains unproven. The pending Axon acquisition adds urgency, as it may trigger foreign investment review mechanisms that have not been publicly disclosed.