Political Risk & Governance Audit: Waze Mobile Ltd.
1. Executive Intelligence Summary
This comprehensive audit evaluates the political and ideological footprint of Waze Mobile Ltd., a subsidiary of Alphabet Inc. (Google), to determine its level of integration with the Israeli state apparatus and its complicity in the occupation of Palestinian territories. The audit responds to specific Core Intelligence Requirements (CIRs) regarding governance ideology, lobbying activities, comparative crisis response protocols (“Safe Harbor” test), and internal corporate policy enforcement.
The investigation establishes that Waze is not merely a neutral commercial entity but functions within a paradigm of “Sovereign Fusion,” where corporate utility, state security interests, and ideological advocacy overlap significantly. Originally founded by veterans of the Israel Defense Forces (IDF) Unit 8200, the company’s foundational architecture relies on signal intelligence (SIGINT) methodologies adapted for civilian use. Following its acquisition by Google, Waze has retained distinct operational characteristics that align with Israeli state interests, even as it has been structurally integrated into Google’s Geo division.
Key areas of focus include the application’s role in enforcing the spatial segregation of the West Bank through algorithmic redlining, its bidirectional data-sharing agreements with Israeli government ministries, and the stark disparity in its operational and humanitarian responses to the conflict in Gaza compared to the war in Ukraine. The following report details the evidentiary basis for assessing the entity’s political complicity without assigning a final score, providing the raw intelligence required for a subsequent risk ranking.
.2. Governance Ideology and Leadership Lineage
To understand the political risk profile of Waze, it is essential to analyze the ideological substrate of its governance. This section traces the continuity from its founders’ military backgrounds to its current executive alignment, revealing a deep-seated integration with the Israeli military-industrial complex that transcends standard corporate history.
2.1 The Unit 8200 Connection: The “Feeder” System
The governance ideology of Waze cannot be decoupled from its origins in the Israeli military intelligence sector. The audit confirms that the company’s founders—Ehud Shabtai, Amir Shinar, and Uri Levine—are veterans of Unit 8200 (Yehida Shmoneh-Matayim).1 This unit is the IDF’s equivalent of the US National Security Agency (NSA) or Britain’s GCHQ, responsible for signal intelligence, code decryption, and cyberwarfare.2
The relationship between Unit 8200 and Waze is not incidental; it is foundational. Unit 8200 functions as a pre-eminent incubator for the Israeli technology sector, operating a “feeder” system that transitions personnel from military intelligence directly into commercial entrepreneurship.3 The founders of Waze are part of a specific cohort of Unit 8200 alumni who have established major tech firms, including Check Point, Palo Alto Networks, and Wiz.3
This lineage imparts a specific ideological and operational culture known as “Rosh Gadol” (literally “big head,” implying taking initiative and responsibility). In the context of Unit 8200, this ethos encourages personnel to identify problems and devise technological solutions independent of strict hierarchy.4 When transferred to the civilian sector, this results in companies that view surveillance and data mining not as privacy intrusions but as essential tools for “solving” societal friction—in Waze’s case, traffic congestion.
The audit identifies a risk factor in the “dual-use” nature of the skills transferred. The core competency of Unit 8200—analyzing vast flows of real-time data to identify threats and patterns—is the exact architectural basis of Waze. In a military context, this capability targets hostile actors; in a commercial context, it targets traffic anomalies. The “crowdsourced” nature of Waze mirrors the intelligence gathering networks of the state, relying on a distributed network of sensors (users) to feed a central processing authority.4 This creates a corporate culture where the distinction between civilian utility and military intelligence gathering is historically and methodologically blurred.
2.2 Executive Advocacy and Post-Exit Activism
While Waze operates as a subsidiary, the ideological footprint of its leadership—both past and present—remains a critical indicator of its political alignment. The audit reveals that key figures associated with the company have leveraged their corporate prestige to engage in explicit Zionist advocacy and crisis response on behalf of the state.
Noam Bardin (Former CEO)
Noam Bardin, who guided Waze through its acquisition and served as a Google Vice President, presents a significant profile of ideological engagement. His activities following the attacks of October 7, 2023, demonstrate a shift from corporate executive to active ideological participant.
●Direct Crisis Mobilization: In the immediate aftermath of October 7, Bardin flew to Israel and volunteered in uniform, traveling to the southern conflict zones with former general Yair Golan.5 His stated goal was to “rebuild the country,” framing his participation as a return to civic duty and Zionist identity.5
●Narrative Construction: Bardin has publicly articulated a renewed connection to Jewish and Israeli identity, stating, “Suddenly, being Jewish was back in style – or maybe antisemitism was”.5 This rhetoric aligns with state narratives regarding the existential nature of the conflict.
●Political Commentary and Platform Creation: Bardin has been a vocal critic of what he perceives as antisemitism on social media platforms like Twitter (X). He founded Post News as an alternative platform, explicitly positioning it against the “free speech absolutism” that he argues allows hate speech to flourish.6 While framed as a moderation issue, this aligns with broader “Brand Israel” efforts to police anti-Zionist discourse under the banner of combating antisemitism.
●Investment and Legitimation: Through his involvement with Aleph VC, Bardin continues to integrate the Israeli tech ecosystem with global capital, reinforcing the narrative of Israeli resilience as a key economic indicator.7
Uri Levine (Co-Founder)
Uri Levine remains a central figure in the “Startup Nation” diplomacy circuit, using his status as a Waze co-founder to legitimize the Israeli economy and advocate for its integration into global markets.
●Chamber of Commerce Engagement: Levine has served as a featured speaker for UK Israel Business (formerly the British-Israel Chamber of Commerce).8 This organization is a primary lobbying vehicle for strengthening bilateral trade and opposing the Boycott, Divestment, and Sanctions (BDS) movement. His participation lends credibility to these lobbying efforts, positioning Waze’s success as a dividend of strong UK-Israel ties.
●Economic Resilience Narrative: In interviews with major financial outlets like Bloomberg, Levine actively frames the resilience of the Israeli tech sector in the face of war as a strategic asset. He discusses the impact of the Israel-Hamas war not just as a humanitarian crisis but as a test of the “Startup Nation’s” durability, thereby normalizing the conflict as a manageable business risk.9
2.3 Current Corporate Structure: Integration into Google Geo
As of the 2024-2025 audit period, Waze’s independent governance structure has been largely dissolved and absorbed into Google’s broader operational framework. This structural shift has significant implications for political complicity, as Waze is now directly implicated in Google’s government contracts.
●Loss of Autonomy: In December 2022, Google merged the 500-person Waze team into the Google Geo division, which also oversees Google Maps, Google Earth, and Street View.11 The former CEO, Neha Parikh, departed, and the unit now reports to Christopher Phillips, Vice President & General Manager of Google Geo.12
●Leadership Profiles: The current “Head of Waze” is Guy Berkowicz.13 While Berkowicz’s public political footprint is less distinct than the founders’, the leadership structure places Waze firmly under the umbrella of Google executives who manage the company’s most sensitive government relationships.
●Project Nimbus Liability: The absorption of Waze into Google Geo links the entity directly to Project Nimbus, a $1.2 billion contract to provide cloud computing and artificial intelligence services to the Israeli government and military.14
○Operational Integration: As part of the Geo division, Waze’s technology and data are part of the broader suite of tools potentially available to Project Nimbus clients. The contract explicitly prevents Google from denying services to specific government entities, meaning Waze data could theoretically be accessed by the Israeli Ministry of Defense under this framework.16
○Employee Dissent: This integration has been a flashpoint for internal dissent. The “No Tech for Apartheid” movement, led by Google employees, specifically targets the Geo division’s complicity in state violence. The firing of 28-50 employees in April 2024 for protesting this contract highlights the active enforcement of this corporate-state alliance.14
.3. Operational Complicity: The Civil-Military Interface
This section audits the material ways in which Waze’s platform, data, and algorithms interact with the Israeli state apparatus. The “Safe Harbor” test is applied here to operational decisions, revealing a pattern of cooperation that extends beyond regulatory compliance into active collaboration with security forces.
3.1 “Waze for Cities” and Institutional Data Exchange
The “Waze for Cities” program (formerly the Connected Citizens Program or CCP) serves as the primary mechanism for institutional data exchange between the company and state entities. While marketed globally as a tool for municipal traffic optimization, in the context of Israel, it functions as a critical node in the state’s infrastructure management.
●Mechanism of Exchange: The program establishes a bidirectional data pipeline. Waze provides real-time, anonymized traffic data—derived from the movements of its users—to government partners. In return, these partners provide data on road closures, construction, and infrastructure changes.17
●Strategic Partnerships:
○Tel Aviv & Ministry of Transportation: Tel Aviv was one of the “W10” (first ten partners) of the program.20 The partnership extends to the Israeli Ministry of Transportation, which utilizes Waze data to optimize traffic light timing and identify congestion hotspots.21
○Security Implications: In Israel, the Ministry of Transportation is a key actor in the occupation, responsible for planning and maintaining the road networks that connect settlements to Israel proper while bypassing Palestinian communities. By optimizing this network, Waze materially aids the efficiency of the settlement infrastructure.
●The “Protection Racket” Critique: Industry analysts have described the CCP model as akin to a “protection racket,” where cities are mesmerized into relying on Waze to fix traffic problems that the app itself may exacerbate by routing traffic through residential neighborhoods.23 In the Israeli context, this dependency deepens the state’s reliance on a private, foreign-owned (Google) but locally-rooted entity for critical governance functions.
3.2 The “Digital Iron Dome”: Military Utilization of Consumer Data
The distinction between civilian traffic management and military logistics is effectively non-existent in the West Bank and during periods of active conflict. Waze’s data has been identified as a dual-use asset that serves military objectives.
●The “Lethal Intelligence” Assessment: Security researchers and information security experts have characterized crowdsourced navigation apps like Waze as potentially “the most lethal mass intelligence collection system in Israel”.24 By aggregating the real-time location and velocity of millions of users, Waze provides a high-fidelity “heatmap” of population density. In a conflict zone, this data is invaluable for targeting (or avoiding) specific areas.
●Home Front Command Integration: During the Gaza war (2023-Present), the Home Front Command—the IDF branch responsible for civil defense—utilized civilian navigation apps as part of its emergency management protocol. The decision to disable live traffic displays (discussed in Section 6) was executed in direct coordination with, or at the request of, the Home Front Command.25
○Operational Obscurity: The disabling of traffic data served a distinct military purpose: masking the locations of troop concentrations and staging areas from Open Source Intelligence (OSINT) observers and potential adversaries. This converts the civilian app into a tool of operational security (OPSEC) for the military.
●Checkpoint Management: Evidence suggests that Waze data informs the management of the physical infrastructure of the occupation. By integrating real-time traffic speeds, the system can ostensibly monitor flow rates through military checkpoints, which act as the primary choke points for Palestinian movement in the West Bank.27
3.3 West Bank Routing and the “Dangerous Areas” Algorithm
Waze’s most significant operational complicity lies in its routing algorithms, which normalize, enforce, and digitize the Israeli military’s spatial control over the West Bank. The application effectively “hardcodes” the Oslo Accords’ zoning maps into the user experience.
●Default Segregation (Area A/B Exclusion): The application includes a default setting titled “Avoid dangerous areas.” For users with Israeli settings, this algorithm defines Area A (under Palestinian civil and security control) and Area B (Palestinian civil control, Israeli security control) as “dangerous.” The app prevents Israeli civilians and soldiers from inadvertently entering Palestinian cities like Ramallah or Bethlehem.28
○Visual Warning Systems: When approaching these zones, users receive visual warnings (often red polygons or pop-ups) indicating they are entering a restricted area.30
●The Qalandia Incident (2016): The lethal consequences of this reliance were demonstrated in 2016, when two Israeli soldiers drove into the Qalandia refugee camp using Waze. The resulting confrontation led to a firefight that killed one Palestinian and wounded several others. Waze defended its software by stating the soldiers had manually disabled the “Avoid dangerous areas” setting.31
○Post-Incident Hardening: Following this incident, Waze representatives toured the West Bank with IDF officials to identify “representational loopholes.” This cooperation resulted in an immediate map update to further align the app’s routing logic with military no-go zones, effectively deputizing the app as a digital border agent.33
●Asymmetrical Safety Protocols: The audit identifies a critical “Double Standard” in the definition of danger. While the app aggressively warns Jewish Israelis against entering Palestinian population centers, it does not provide equivalent “dangerous area” warnings for Palestinians entering violent illegal outposts or settlements known for settler violence.32 The definition of “danger” is uni-directional: it protects the occupier from the occupied, but not the reverse.
.4. Spatial Politics: Digital Erasure and Settlement Normalization
Waze’s mapping choices do not merely reflect the reality on the ground; they actively construct a reality that favors the colonial narrative. This section analyzes the map as a political artifact that engages in “cartographic erasure.”
4.1 Settlement Recognition vs. Palestinian Erasure
The research indicates a systematic visual bias in how Waze represents the geography of the West Bank.
●Settlement Visibility: Illegal Israeli settlements (under international law) are typically fully mapped, navigable, and labeled. They are treated as standard destinations, indistinguishable from towns inside the Green Line (1948 borders).34 The nomenclature adopts Israeli government definitions, using biblical names for settlements without “illegal” or “occupied” qualifiers.
●Palestinian Erasure: In contrast, many Palestinian villages—particularly those in Area C or those unrecognized by Israeli planning authorities—lack detailed street maps or are entirely absent from the platform. This phenomenon mirrors historical “Jewish National Fund maps” that erased indigenous localities to reinforce Zionist claims to the land.36
●The “Invisible” Economy: Palestinian tech entrepreneurs argue that this algorithmic redlining renders Palestinian businesses “invisible” to the digital economy. Tourists or casual drivers are routed away from Palestinian commercial hubs, damaging the local economy and enforcing a digital blockade that parallels the physical one.32
4.2 The “Bypass Road” Infrastructure
Waze’s routing algorithms are optimized for the “bypass road” network—a system of highways built by Israel in the West Bank designed to connect settlements to Israel proper while bypassing Palestinian population centers.
●Segregated Routing: These roads are often restricted to Israeli-licensed vehicles (yellow plates). Waze routes Israeli users through the West Bank as if it were annexed territory, creating a “frictionless” occupation experience where the user rarely encounters the Palestinian reality or the military checkpoints that control it.32
●Palestinian Exclusion: Palestinians (with white/green plates) are often legally barred from using these roads. A Palestinian user attempting to navigate from Ramallah to Nablus using Waze might be offered a route they are physically prevented from taking. This failure of the platform to account for the restricted mobility of Palestinians has necessitated the development of alternative, indigenous apps like Doroob to serve the population Waze ignores.27
.5. The “Safe Harbor” Test: Comparative Crisis Response
A critical component of this audit is analyzing Waze (and its parent company, Google) response to the Gaza conflict (2023-Present) compared to the Russia-Ukraine war (2022). This “Safe Harbor” test reveals whether the company applies neutral humanitarian principles or aligns with specific geopolitical interests.
5.1 Traffic Data Blackouts: Strategic vs. Humanitarian
In both conflicts, Waze disabled live traffic data functionality. However, a granular analysis of the operational context suggests distinctly different strategic beneficiaries.
●Ukraine (2022): Google/Waze disabled live traffic data in Ukraine immediately following the Russian invasion.
○Stated Rationale: To protect the safety of local communities, implying that Russian forces could use traffic jam data to target fleeing civilians or identify refugee concentrations.25
○Strategic Effect: This action denied OSINT (Open Source Intelligence) to the invading Russian forces regarding Ukrainian troop movements and civilian locations. It was a defensive measure taken in coordination with the Ukrainian government.
●Gaza/Israel (2023): Google/Waze disabled live traffic data in Israel and Gaza in October 2023.
○Stated Rationale: “Safety of local communities” and preventing the “accidental disclosure of troop movements”.26
○Strategic Effect:
■For Israel: The blackout obscured the massive assembly of IDF tanks and troops on the Gaza border (deployment areas) from OSINT observers and potentially from Hamas targeting.
■For Gaza: It blinded humanitarian organizations and civilians attempting to flee aerial bombardment. Without traffic data, Palestinians could not identify congestion on designated evacuation routes (e.g., Salah al-Din road), increasing the risk of being trapped in target zones.
○Audit Insight: While the action (disabling data) was identical, the requestor in the 2023 case was the Israeli military.38 In Ukraine, the move aided the defender. In Gaza, it aided the offensive assembly of the occupier while degrading the situational awareness of the civilian population under fire.
5.2 Corporate Philanthropy and Employee Matching
The audit reveals a disparity in how corporate resources and employee goodwill were mobilized for humanitarian aid in the two theaters.
●Ukraine Response:
○Direct Grants: Google.org committed over $15 million in direct relief, along with substantial advertising grants to humanitarian organizations.39
○Employee Engagement: The company established a “United for Ukraine” internal portal and launched a fellowship program where Google employees (including Waze staff) could work full-time, pro-bono, with the International Rescue Committee (IRC) to build information systems for refugees.40
○Narrative: The corporate tone was unambiguous in its support for the “victim” (Ukraine) against the “aggressor” (Russia).
●Israel/Gaza Response:
○Direct Grants: Google pledged $8 million total, split evenly between Israeli NGOs (e.g., NATAL, Magen David Adom) and Gaza relief (e.g., Save the Children, UNICEF).41 While appearing equitable, the total amount is significantly lower than the Ukraine commitment, despite the catastrophic scale of destruction in Gaza.
○Internal Friction: Reports indicate that while Ukraine donation links were freely circulated on internal platforms, links for Gaza relief (e.g., UNRWA, Palestinian Red Crescent) faced internal scrutiny. Threads discussing Palestine were often locked or flagged for “appropriateness” checks, creating administrative barriers to employee solidarity that did not exist for Ukraine.43
○Project Nimbus Protest: Employees attempting to organize around the ethical implications of the company’s tech in Gaza faced termination—a disciplinary severity not seen regarding Ukraine activism.14
.6. Internal Governance and Labor Relations
The audit of internal policy focuses on how the company manages dissent regarding its involvement in the region. The findings indicate a pattern of “Discriminatory Governance.”
6.1 Disciplinary Action and “Neutrality”
The firing of between 28 and 50 employees in April 2024 following protests against Project Nimbus represents a high-severity indicator of political bias in governance.14
●The Incident: Employees at Google offices (including Geo division staff) occupied the office of the Google Cloud CEO to protest the $1.2 billion contract with the Israeli military. They wore shirts reading “Googlers against Genocide.”
●The Corporate Response: Google termed the protest “completely unacceptable behavior” and terminated the employees, citing violations of code of conduct regarding disrupting the workplace.
●The Double Standard: Legal filings and internal accounts suggest that “political” speech is policed differentially.
○Permissible Speech: Expression supporting Ukraine, LGBTQ+ rights, or Black Lives Matter has generally been tolerated or institutionalized within the corporate culture.
○Prohibited Speech: Expression opposing Zionism or the occupation is frequently framed as “harassment,” “antisemitic,” or “disruptive”.43
○Weaponization of HR: The use of “appropriateness” guidelines to lock threads about Gaza humanitarian aid while leaving Ukraine threads open indicates a systemic bias in internal community management.43 This enforcement aligns not with a policy of strict neutrality, but with an ideological bias that views pro-Israel sentiment as the default and pro-Palestine sentiment as a deviation requiring management.
.7. Lobbying, Trade, and Institutional Legitimation
Waze’s corporate identity is leveraged to legitimize the Israeli tech sector, countering the Boycott, Divestment, Sanctions (BDS) movement through “Brand Israel” advocacy and participation in state-backed trade ecosystems.
7.1 “Startup Nation” Diplomacy and Trade Chambers
Waze is frequently cited as the “crown jewel” of the “Startup Nation” narrative, which the Israeli government uses to rebrand itself as a global hub of innovation rather than a conflict zone.46
●Chamber Membership: As noted in Section 2, co-founder Uri Levine has actively engaged with UK Israel Business, a lobbying entity designed to strengthen commercial ties and oppose boycotts.8
●Diplomatic Asset: The acquisition of Waze by Google for $1.3 billion is used in government reports and diplomatic missions to attract Foreign Direct Investment (FDI).46 This economic success is framed as a national victory, with the state treasury directly benefiting.
●Tax Revenue as War Funding: The sale of Waze generated approximately $370 million in tax revenue for the Israeli government.47 While the payment of taxes is a legal obligation, the celebration of this windfall by government officials highlights the direct financial link between the company’s success and the state’s fiscal capacity to fund its military and settlement enterprise.
7.2 Sponsorship of “Brand Israel” Events
Waze and its parent company continue to sponsor and participate in events that normalize the Israeli tech ecosystem’s ties to the military.
●EcoMotion Week: Waze has participated in EcoMotion Week in Tel Aviv, a major mobility conference. This event often showcases dual-use technologies, such as autonomous vehicle sensors derived from military missile technology, facilitating the transfer of military R&D into the civilian market.48
●Cybertech Global: While Waze is a consumer app, its personnel and founders are regulars at events like Cybertech Global Tel Aviv, which brings together government officials, military leaders, and tech executives. These events serve as networking hubs where the “sovereign fusion” of the Israeli cyber sector is reinforced.50
.8. Financial Flows and Corporate Social Responsibility (CSR)
The audit examined the financial mechanisms through which Waze and its founders support ideological causes.
8.1 The Tmura Fund Connection
Following the Google acquisition, Waze’s founders utilized the Tmura – The Israeli Public Service Venture Fund to distribute proceeds from the exit.51
●Mechanism: Waze donated equity (options) to Tmura early in its lifecycle. Upon the $1.3 billion exit, these options were liquidated, generating approximately $1.5 million for the fund.
●Beneficiaries: While Tmura supports various educational and youth-related NGOs, the fund focuses on Israeli domestic society. The transfer of wealth from the Waze exit explicitly strengthens the Israeli third sector (civil society), which often fills gaps in social services left by high military spending. This represents a direct transfer of corporate value to the Israeli social apparatus.
8.2 Project Nimbus Revenue
Under the current Google Geo structure, Waze contributes to the technological capabilities offered under Project Nimbus.
●Direct Financing: The contract is valued at $1.2 billion. This revenue stream flows from the Israeli Ministry of Finance and Ministry of Defense to Google. By integrating Waze into the division servicing this contract, the app’s technology becomes a component of the service package the Israeli military pays for, creating a direct financial feedback loop between the occupation forces and the company.14
.9. Data Appendix
Table 1: Comparative Crisis Response (Safe Harbor Test)
| Feature
|
Ukraine Conflict (2022)
|
Gaza Conflict (2023-2024)
|
Strategic Implication
|
Sources
|
| Live Traffic Data
|
Disabled immediately upon invasion.
|
Disabled 2 weeks into war.
|
Ukraine: Defensive (hides civilians). Israel: Offensive (hides tank assembly).
|
25
|
| Requesting Entity
|
Ukrainian Government.
|
Israeli Military (Home Front Command).
|
Cooperation with invaded vs. invader/occupier.
|
26
|
| Employee Activism
|
Institutionalized (Google Fellows program).
|
Punished (Firings of “No Tech for Apartheid”).
|
Ideological filtering of “acceptable” causes.
|
14
|
| Donation Platform
|
“United for Ukraine” Hub; High visibility.
|
Restricted internal threads; “Appropriateness” flags.
|
Frictionless support vs. administrative barriers.
|
43
|
| Financial Aid
|
~$15M + Ad Grants + Fellowships.
|
$8M split evenly ($3M/$3M) + Security focus.
|
Parity optics versus material equity.
|
39
|
Table 2: Routing & Mapping Bias Indicators
| Feature
|
Israeli User Experience
|
Palestinian User Experience
|
Political Impact
|
Sources
|
| Dangerous Areas
|
Warns against entering Area A (Palestinian cities).
|
No equivalent warnings for violent settlements/outposts.
|
Uni-directional safety; protects the occupier.
|
28
|
| Routing Logic
|
Uses bypass roads & Area C; “Frictionless.”
|
Cannot use bypass roads; often routed illegally.
|
Enforces segregation; legitimizes annexation infrastructure.
|
27
|
| Map Labels
|
Settlements labeled as standard towns.
|
Villages often missing, unlabeled, or erased.
|
“Cartographic Erasure” of indigenous presence.
|
34
|
| Checkpoint Data
|
Integrated for efficiency/speed.
|
Integrated for avoidance (via 3rd party apps).
|
Waze acts as a checkpoint management tool for the state.
|
24
|
Table 3: Corporate & State Interlocks
| Entity
|
Nature of Relationship
|
Risk Factor
|
Sources
|
| Unit 8200
|
Founders’ Origin; Talent Pipeline.
|
Normalization of military surveillance culture.
|
1
|
| Ministry of Transport
|
“Waze for Cities” Data Partner.
|
Integration with occupation infrastructure planning.
|
21
|
| Home Front Command
|
Crisis coordination; Traffic jamming.
|
Direct military-civilian operational fusion.
|
55
|
| Project Nimbus
|
Parent Company (Google) Contract.
|
Providing AI/Cloud for IDF/Govt.
|
14
|
| Tmura Fund
|
Donation of equity (Options).
|
Financial support to Israeli civil society (Zionist).
|
51
|
| UK Israel Business
|
Founder Participation (Speaker).
|
Lobbying against BDS; Trade promotion.
|
8
|
(End of Report)
Works cited
