Marketplace rules
Guestpass does not replace Turo, Getaround, direct-rental, insurance, or local verification rules.
Security and compliance
Guest access should be narrow, time-bound, and auditable.
Levy Guestpass is built around explicit host controls: no unlock before host verification, no shared OEM credentials, and no promise that remote commands replace physical-key fallback.
The access gate is layered.
A link opening successfully is not enough. Guestpass evaluates session state, token state, phone verification, device checks, ID gate status, and the command window.
Hashed public access tokens instead of reusable public codes
Guest phone OTP before command access
Optional device binding for forwarded-link mitigation
Host-controlled ID verification gate
Trip-window and post-trip grace enforcement
Provider-specific command failure classification
Bulk revoke and per-session token rotation
Audit export for disputes, claims, and support
Provider limits
Smartcar/OEM, Uconnect, Linka, and hardware commands can fail due to auth, signal, provider outages, or vehicle state.
Fallback keys
Hosts should keep physical fob or key fallback available through an approved RF pouch or lockbox workflow.
Security review
Map your handoff controls before launch.
Send your current access process and we will flag the verification, fallback, and provider-readiness gates.