ConfidentialHJMT Solutions Patent Position Review

Section 08.2

Outdoorsy — Recreational Asset Mapping

Peer-to-peer RV / recreational vehicle rental. Marked as a high-priority detailed review environment because first-party documentation expressly describes state-dependent financial outcomes.

08.2.0

Why Outdoorsy Receives Strong Analytical Weight

Scheduled security-deposit authorisationTransaction-specific holdsAutomatic releaseAutomatic retention during insurance claimsPost-trip fee collectionMileage / generator overagesInsurance deductible relationshipsDigital contract requirementsAlternative security-deposit waiver structures

Review Priority

High-Priority Detailed Review Environment

Public documentation describes a security hold that may be placed, released, retained, converted into a charge, extended or linked to an insurance deductible depending on events and transaction state.

Host-Defined Security Amount

Pre-Trip Authorisation

Active Trip

Post-Trip Claim Window

Release / Retain / Charge

08.2

Outdoorsy — Company Profile

Company

Outdoorsy

Vertical

Peer-to-peer RV / recreational vehicle rental

Evidence Basis

Publicly available first-party material

Review Note

High-priority detailed review environment.

Outdoorsy's current first-party documentation expressly describes scheduled security-deposit authorisation, transaction-specific holds, automatic release, automatic retention during insurance claims, post-trip fee collection, mileage and generator overages, insurance deductible relationships, digital contract requirements and alternative security-deposit waiver structures.

Guest / HostHost-Defined Security AmountPre-Trip AuthorisationActive TripPost-Trip Claim WindowInsurance ClaimRelease / Retain / Charge

08.2.1

Security Deposit Architecture — Conditional Financial Hold

Public observation

Outdoorsy states that its Security Deposit is generally a temporary authorisation / hold rather than an immediate charge. The Host determines the refundable deposit amount, and Outdoorsy places the hold on the Guest's payment method two days before the trip begins.

CleaningMinor interior damageTollsParkingRule violationsOther ancillary charges

HJMT technical analysis

The deposit is host-defined rather than demonstrated as dynamically risk-scored by the platform. This is therefore not classified as full MarketMind dynamic security determination.

Relevant MarketMind technical elements

09 — Dynamic Bond / Security Determination10 — Financial Governance11 — Conditional Escrow / Holding Logic12 — Time as a Risk Variable20 — Conditional Settlement22 — State-Based Transaction Control

Host-Defined Security Amount

Pre-Trip Authorisation

Active Trip

Post-Trip State

Release / Claim / Retain

Assessment

10Financial GovernanceStrong Correspondence

11Conditional Escrow / Holding LogicStrong Correspondence

20Conditional SettlementStrong Correspondence

12Time as a Risk VariableStrong Correspondence

09Dynamic Bond / Security DeterminationRelevant Correspondence

Evidence confidence — High

High — first-party security deposit documentation.

08.2.2

Automatic Release

Public observation

Outdoorsy's current documentation states that where no claim is made, the system automatically releases the security-deposit hold after the defined post-trip period. Current Host material describes a seven-day claim window and automatic release on the seventh day if no action is taken.

HJMT technical analysis

A timed, event-conditioned release operates as an automated settlement rule rather than a manual administrative step.

Relevant MarketMind technical elements

10 — Financial Governance11 — Conditional Escrow / Holding Logic12 — Time as a Risk Variable14 — Event-Based Trigger Engine20 — Conditional Settlement21 — Programmable Transaction Framework22 — State-Based Transaction Control

Trip Ends

Post-Trip Claim Window

Claim Filed?

No → Automatic Release

Yes → Alternative Financial State

Assessment

14Event-Based Trigger EngineStrong Correspondence

21Programmable Transaction FrameworkStrong Correspondence

22State-Based Transaction ControlStrong Correspondence

Evidence confidence — High

High — claim window and release behaviour are documented.

08.2.3

Insurance Claim → Financial State

Public observation

Outdoorsy's current Security Deposit documentation states that if an insurance claim is filed, the security-deposit hold may be maintained rather than released. Host documentation states that filing an official insurance claim before expiration of the standard claim period can automatically retain the deposit for an extended period, and the deposit can then be applied in connection with the Protection Package deductible.

HJMT technical analysis

This is among the clearest publicly documented relationships in the current review between an event (claim filing), a transaction state (retained hold), an insurance process and a conditional financial outcome (deductible application).

Relevant MarketMind technical elements

10 — Financial Governance11 — Conditional Escrow / Holding Logic14 — Event-Based Trigger Engine15 — Exception Management18 — Insurance Integration20 — Conditional Settlement21 — Programmable Transaction Framework22 — State-Based Transaction Control

Active Security Hold

Trip Completion

Insurance Claim Filed?

No → Release Path

Yes → Retain Hold

Claim Investigation

Deductible / Financial Outcome

Assessment

18Insurance IntegrationStrong Correspondence

15Exception ManagementStrong Correspondence

Evidence confidence — High

High — first-party deposit and claim documentation.

08.2.4

Post-Trip Financial Events

Public observation

Outdoorsy's public Host documentation identifies expected and unexpected post-trip charges. Expected / rule-based overages can include cleaning, late return, mileage, generator use and pre-agreed charges. Post-trip events can include tolls, parking tickets, missing equipment and other identified post-trip costs.

Some mileage and generator overages can be handled through Outdoorsy's in-app Digital Key Exchange.

HJMT technical analysis

Post-trip data and events are classified and then processed against rules and evidence before a financial charge is applied.

Relevant MarketMind technical elements

02 — Multi-Variable Transaction Intake05 — Asset-Driven Transaction Control10 — Financial Governance14 — Event-Based Trigger Engine15 — Exception Management19 — Verification-Driven Control21 — Programmable Transaction Framework

Trip Data / Post-Trip Event

Classification

Rule / Evidence

Financial Charge

Assessment

02Multi-Variable Transaction IntakeRelevant Correspondence

05Asset-Driven Transaction ControlRelevant Correspondence

Evidence confidence — High

High — charge categories are documented in Host material.

08.2.5

Digital Contract / Verification

Public observation

Current Outdoorsy support material states that for certain additional manual post-trip charges, the Digital Rental Contract must have been signed by both Host and Guest through the Outdoorsy application during the key-exchange process.

HJMT technical analysis

A verified transaction record operates as a precondition of a defined post-trip financial action.

Relevant MarketMind technical elements

01 — Event-Driven Transaction Activation19 — Verification-Driven Control20 — Conditional Settlement21 — Programmable Transaction Framework22 — State-Based Transaction Control

Signed Digital Transaction Record

Eligibility for Defined Post-Trip Action

Assessment

19Verification-Driven ControlStrong Correspondence

01Event-Driven Transaction ActivationRelevant Correspondence

Evidence confidence — High

High — stated in current support documentation.

08.2.6

Security Deposit Waiver — Alternative Financial / Protection Path

Public observation

In 2026 Outdoorsy introduced a Security Deposit Waiver for eligible listings. Public material states that guests may choose between a traditional security deposit authorisation or a security deposit waiver / flat fee, and that the waiver can operate as a deductible buy-down for an approved insurance claim, subject to limits and conditions.

HJMT technical analysis

Alternative security paths produce different post-claim financial outcomes from the same underlying transaction, which is relevant to MarketMind's conditioning and programmable-framework concepts.

Relevant MarketMind technical elements

08 — Dynamic Transaction Conditioning09 — Dynamic Bond / Security Determination10 — Financial Governance18 — Insurance Integration20 — Conditional Settlement21 — Programmable Transaction Framework

Booking

Available Security Paths

Deposit Hold → Conditional Funds

Waiver → Flat-Fee / Deductible Protection

Different Post-Claim Financial Outcome

Assessment

08Dynamic Transaction ConditioningRelevant Correspondence

Evidence confidence — High

High — published product material.

08.2.7

Long-Duration Hold Management

Public observation

Outdoorsy states that on longer bookings, payment-authorisation expiry can require the security-deposit hold to be released and re-authorised to keep the financial security mechanism active.

HJMT technical analysis

Transaction duration is treated as a condition requiring an active financial-control action, rather than as a passive attribute of the booking.

Relevant MarketMind technical elements

10 — Financial Governance11 — Conditional Escrow / Holding Logic12 — Time as a Risk Variable21 — Programmable Transaction Framework22 — State-Based Transaction Control

Longer Transaction Duration

Authorisation Expiry Condition

Re-Authorise Hold

Maintain Transaction Security

08.2.8

Outdoorsy — Summary

Current high-value observations

Pre-trip security authorisationHost-defined security amountTimed hold placementPost-trip claim windowAutomatic releaseInsurance-claim-triggered hold retentionSecurity deposit applied to insurance deductibleRule-based ancillary chargesMileage / generator overagesDigital Key ExchangeSigned Digital Rental ContractAlternative Security Deposit WaiverState-dependent financial outcomes

Strongest MarketMind reference areas

Financial GovernanceConditional HoldingConditional SettlementTime as a Risk VariableEvent-Based TriggeringInsurance IntegrationProgrammable Transaction FrameworkState-Based Transaction ControlVerification-Driven ControlException Management

No overall Technical Correspondence Index is generated for this company.

08.2.9

Outdoorsy — Evidence Gaps

Host-defined deposit is visible, but MarketMind-style dynamic risk-calculated deposit is not established.Internal risk model is not public.Behaviour-to-financial coupling based on historical participant conduct is not yet established.Adaptive learning is not established.Future transaction conditioning based on prior outcomes is not established.Cloud / API architecture requires later review.

Gap classification recorded for this review: Backend Implementation Not Public. Missing evidence has not been filled with assumptions.

08.2.10

Outdoorsy — Potential MarketMind Enhancement

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

MarketMind could potentially extend the transaction-control architecture by modelling predictive late-return probability.
MarketMind could potentially extend the architecture by modelling predictive damage likelihood.
MarketMind could potentially extend the architecture by modelling predictive dispute risk.
MarketMind could potentially extend the architecture by applying dynamic behaviour-based security requirements.
MarketMind could potentially extend the architecture through a cross-transaction reliability score.
MarketMind could potentially extend the architecture with contextual and weather-related risk inputs.
MarketMind could potentially extend the architecture with location-risk conditioning.
MarketMind could potentially extend the architecture with dynamic insurance decisioning.
MarketMind could potentially extend the architecture with real-time transaction reconditioning.
MarketMind could potentially extend the architecture with downstream booking-dependency protection.
MarketMind could potentially extend the architecture with adaptive future transaction conditions.
MarketMind could potentially extend the architecture with cross-platform behavioural intelligence.

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

08.2.11