ConfidentialHJMT Solutions Patent Position Review

Section 06.2

Getaround — Patent-Position Technical Mapping

Publicly described Getaround Connect functionality assessed against MarketMind technical elements. Public observation, HJMT analysis, HJMT inference and evidence gaps are recorded separately.

06.2

Getaround — Company Profile

Company

Getaround

Vertical

Technology-enabled connected vehicle sharing

Evidence Basis

Publicly available first-party material

Review Note

High-priority detailed review environment. This classification reflects evidential value for technical review only.

Current publicly available material concerning Getaround Connect provides unusually useful technical evidence because it describes interaction between identity verification, connected vehicle hardware, remote access, location, vehicle condition, mileage, fuel, rental state, late return, automatic financial adjustment and vehicle immobilisation.

VehicleVerified DriverConnected VehicleDigital AccessTelematicsActive RentalAutomated Adjustment / Return

06.2.1

Getaround Connect Architecture

Public observation

Getaround publicly describes Getaround Connect as a telematics device installed in a vehicle.

Remote lock / unlockVehicle locationImmobiliser integrationMileage recordingFuel-level recording for compatible vehiclesConnected transaction operation

HJMT technical analysis

This architecture is relevant to several MarketMind elements simultaneously and therefore warrants analysis not only feature-by-feature but also as an integrated transaction relationship.

Relevant MarketMind technical elements

01 — Event-Driven Transaction Activation02 — Multi-Variable Transaction Intake05 — Asset-Driven Transaction Control13 — Live Transaction Monitoring19 — Verification-Driven Control21 — Programmable Transaction Framework22 — State-Based Transaction Control25 — API-Driven External Platform Integration

Getaround Application

Identity / Booking

Getaround Connect

Vehicle Access + Telematics

Active Rental

Return / Automated Data

Financial / Transaction Outcome

06.2.2

Identity → Access

Public observation

Getaround states that renter identity is verified.

Renter identity can be verified using facial scanningDriving licence / identity documents are verifiedVehicle location becomes available after the required verification stageThe renter documents vehicle conditionThe vehicle can then be unlocked through the smartphone application

HJMT technical analysis

Access to the asset is sequenced behind completion of verification, and location information is released at a defined stage of the transaction rather than at booking.

Relevant MarketMind technical elements

01 — Event-Driven Transaction Activation03 — Behavioural Intelligence19 — Verification-Driven Control21 — Programmable Transaction Framework22 — State-Based Transaction Control

Identity

Verification

Vehicle Location / Access

Transaction Start

Assessment

01Event-Driven Transaction ActivationStrong Correspondence

19Verification-Driven ControlStrong Correspondence

22State-Based Transaction ControlStrong Correspondence

Evidence confidence — High

High — first-party driver profile verification and Connect material.

06.2.3

Asset Condition & Transaction State

Public observation

Getaround publicly describes digital vehicle inspection at the beginning and end of Connect rentals. Drivers document the vehicle condition through photographs.

Connected systems can also record vehicle data such as mileage and, where supported, fuel.

HJMT technical analysis

Asset data is captured at defined transaction stages and during the rental, providing multi-variable intake and monitoring inputs to the transaction record.

Relevant MarketMind technical elements

02 — Multi-Variable Transaction Intake05 — Asset-Driven Transaction Control13 — Live Transaction Monitoring19 — Verification-Driven Control20 — Conditional Settlement

Assessment

02Multi-Variable Transaction IntakeStrong Correspondence

05Asset-Driven Transaction ControlRelevant Correspondence

13Live Transaction MonitoringStrong Correspondence

19Verification-Driven ControlStrong Correspondence

Evidence confidence — High

High — first-party Connect rental documentation.

06.2.4

Automated Financial Adjustment

Public observation

Getaround states that for compatible Connect vehicles mileage and fuel levels can be automatically recorded.

At the end of a rental, price adjustments can be made automatically based upon distance travelled and/or fuel consumed or returned. Additional mileage can result in an additional charge, and fuel differences may result in charges or refunds.

HJMT technical analysis

Verified connected-asset data is used as a direct input to the financial outcome of the transaction.

HJMT technical inference

For MarketMind Element 04 this evidence is more precisely described as transaction-data-to-financial coupling rather than behaviour-to-financial coupling, because the observed input is asset and transaction data rather than participant behavioural history. It nevertheless demonstrates the broader architectural concept of transaction data directly affecting financial outcome.

Relevant MarketMind technical elements

04 — Behaviour-to-Financial Coupling05 — Asset-Driven Transaction Control10 — Financial Governance19 — Verification-Driven Control20 — Conditional Settlement21 — Programmable Transaction Framework

Connected Asset Data

Verified Transaction Outcome

Calculation

Automatic Financial Adjustment

Assessment

10Financial GovernanceStrong Correspondence

19Verification-Driven ControlStrong Correspondence

21Programmable Transaction FrameworkStrong Correspondence

Assessed as strong to relevant correspondence depending on the degree of rule configurability disclosed.

20Conditional SettlementRelevant Correspondence

04Behaviour-to-Financial CouplingPartial Correspondence

Current evidence demonstrates asset / transaction-data-to-financial coupling more clearly than behavioural-history-to-financial coupling.

Evidence confidence — High

High — first-party Connect pricing and adjustment material.

06.2.5

Time / Late Return

Public observation

Getaround publicly states that Connect rentals can detect late return.

Late-return fees can apply automatically after a defined periodAdditional rental time can be chargedExtensions may depend on future vehicle availabilityA conflicting subsequent rental can affect extensionOwners can be alerted when a vehicle is not returned on time

HJMT technical analysis

A time threshold operates as a monitored condition that produces detection, notification and financial response within the active transaction.

Relevant MarketMind technical elements

12 — Time as a Risk Variable13 — Live Transaction Monitoring14 — Event-Based Trigger Engine15 — Exception Management21 — Programmable Transaction Framework22 — State-Based Transaction Control

Expected Return

Time Threshold

Late Event Detected

Additional Time + Penalty / Support Response

Assessment

12Time as a Risk VariableStrong Correspondence

13Live Transaction MonitoringStrong Correspondence

14Event-Based Trigger EngineStrong Correspondence

15Exception ManagementStrong Correspondence

21Programmable Transaction FrameworkStrong Correspondence

Evidence confidence — High

High — first-party owner guidance concerning late returns.

06.2.6

Immobilisation / State Control

Public observation

Getaround Connect publicly describes integration with vehicle immobilisation.

Historical and current Getaround material indicates that vehicle state and authorised rental periods can interact with vehicle access and security functionality.

HJMT technical analysis

Authorised transaction state and physical asset enablement appear to be related within the connected environment.

Relevant MarketMind technical elements

01 — Event-Driven Transaction Activation14 — Event-Based Trigger Engine19 — Verification-Driven Control21 — Programmable Transaction Framework22 — State-Based Transaction Control

Authorised Transaction State

Access / Vehicle Enablement

Transaction End / Security State

Vehicle Control

Assessment

22State-Based Transaction ControlStrong Correspondence

21Programmable Transaction FrameworkStrong Correspondence

Evidence confidence — Medium

High to medium depending on the currency of the identified source. Current first-party material is used where available.

06.2.7

Getaround — Summary

Current high-value observations

Identity verification tied to transaction accessConnected vehicle telemetryLocation-based transaction informationDigital pre/post condition inspectionMileage and fuel captureAutomated price adjustmentsLate-return detectionAutomatic late chargesAvailability-dependent extensionsRemote vehicle accessVehicle state / security controls

Strongest MarketMind reference areas

Event-Driven Transaction ActivationVerification-Driven ControlLive Transaction MonitoringTime as a Risk VariableEvent-Based Trigger EngineFinancial GovernanceProgrammable Transaction FrameworkState-Based Transaction Control

No overall Technical Correspondence Index is generated for this company.

06.2.8

Getaround — Evidence Gaps

Internal risk-scoring logic requires further reviewBehavioural-history-to-financial coupling requires further evidenceBackend orchestration implementation not fully public

Gap classification recorded for this review: Implementation Detail Limited. Missing evidence has not been filled with assumptions.

06.2.9

Getaround — Potential MarketMind Enhancement

If MarketMind were integrated around the observed platform environment, what additional control capability could the architecture potentially provide?

Broader multi-variable risk could potentially extend the connected data already captured into a wider transaction risk model.
Cross-transaction behavioural intelligence could potentially extend participant history across rentals and asset classes.
Dynamic financial security could potentially condition held security against assessed risk rather than fixed terms.
Predictive late-return risk could potentially anticipate overrun before a threshold is crossed.
Predictive damage risk could potentially combine condition evidence with telemetry.
Cross-platform behaviour could potentially extend reliability information beyond one environment.
Adaptive settlement conditions could potentially extend automated adjustment into conditional settlement.
Future transaction conditioning could potentially apply observed outcomes to subsequent transactions.

These are potential extensions of the architecture. They are not statements that the platform lacks the capability.

06.2.10