Two-layer resolver
Cancellation policy.
Renter-facing single source of truth. What every host must follow.
Operated by PICKRV LLC · Last updated 2026-06-06.
1. Platform floor (non-negotiable)
Every booking on PickRV carries these minimums. Vendors cannot dip below them. These are the promises PICKRV LLC makes to you.
- At least a 48-hour free-cancellation window on every booking, regardless of vendor tier.
- 100% refund + $50 rebooking credit if the host cancels on you.
- 100% refund on force-majeure events (federal disaster declaration, wildfire evacuation order).
- Water rentals: National Weather Service small-craft advisory or higher in the pickup region → 100% refund, no questions.
2. Vendor override tiers
Hosts pick one tier from this menu. They may make cancellations safer than the floor; never stricter. Moderate is the default for new hosts. The percentages below are the effective refunds after the floor is applied — the exact numbers frozen onto your booking, not the tier’s raw schedule.
| Tier | Free-cancel | 7d+ | 48h–7d | 24–48h | <24h |
|---|---|---|---|---|---|
| Flexible | 24h | 100% | 100% | 100% | 50% |
| Moderate (default) | 48h | 100% | 100% | 50% | 0% |
| Strict | 48h | 100% | 100% | 50% | 0% |
| Custom (under review) | 48h | 100% | 100% | 50% | 0% |
Custom requires platform review before a listing publishes. Whichever tier a host picks, the floor in section 1 still applies — which is why Strict and Custom read the same as Moderate at the 48h–7d band.
3. State regulatory overlay
If your pickup state has a stricter rule, the stricter rule wins. These statutes are referenced on your confirmation email and on the dispute case we open for your booking.
CA
Cal. Civ. Code §1798.100 · Cal. Civ. Code §1750 et seq. · Cal. Civ. Code §1770(a)(19)
California's CLRA bans unconscionable terms; Strict tier is unavailable on rigs under $200/night ADR.
FL
Fla. Stat. §501.171 · Fla. Stat. §501.204 (FDUTPA) · Fla. Stat. §501.142
Florida's FDUTPA + §501.142 require refund terms in writing before payment; hurricane NWS warnings trigger a 100% refund.
NY
N.Y. Gen. Bus. Law §349
New York GBL §349 forbids surprise non-refundability — Strict tier requires explicit click-acknowledgement before checkout.
TX
Tex. Bus. & Com. Code §17.46 (DTPA)
Texas DTPA §17.46 forces label-truthing: a listing advertising 'free cancellation' cannot resolve to Strict at checkout.
UT
Utah Code §13-22 (Consumer Sales Practices Act)
Utah's UCSPA bars retroactive policy changes — the snapshot frozen on your booking is the policy that governs your refund.
4. Effective policy at checkout
At checkout we run a deterministic resolver that takes vendor tier, state code, pickup time, and booking time. The result is frozen onto your booking and replayable via a source hash. Here are four real outputs.
a. Florida renter, Moderate vendor, cancels 60h before pickup
Full refund. Vendor's 48h free-cancel window is satisfied and Fla. Stat. §501.142 disclosure was shown before payment.
freeCancelHours = 48 · sourceHash = client-95cf6a8c
b. California renter, Strict vendor — CLRA safer-tier wrap
The renter sees the safer schedule: the platform floor's 50% at the 24–48h band beats the vendor's 25%. California CLRA §1770(a)(19) also bans Strict on rigs under $200/night.
freeCancelHours = 48 · sourceHash = client-c3e8920e
c. Texas boat rental, NWS small-craft advisory 18h before pickup
100% refund. The platform-floor weather trigger (NWS small-craft advisory or higher) overrides any vendor tier. DTPA §17.46 forces the listing label to match.
freeCancelHours = 48 · sourceHash = client-1a0f047b
d. Host cancels 36h before pickup
100% refund plus a $50 rebooking credit. Host-cancel remedy is platform-floor — independent of vendor tier or state.
freeCancelHours = 48 · sourceHash = client-911a59c5
5. How disputes are handled
- Every booking confirmation includes the resolved policy plus a source hash. Keep the hash — it is the replay anchor.
- Open your trips, pick the booking, and choose Open a dispute. That creates a case attached to the booking, with the frozen policy already on it.
- Support replays the exact resolver result from the snapshot frozen on your booking at checkout — not whatever the host edited later.
No booking to hand? Start at Help and include the booking reference and the source hash.
