LARP← All policies

LARP — Identity Verification & Trust Policy

Last updated: August 18, 2026 · Effective date: August 18, 2026


Trust is everything when people meet in person. This Policy explains how LARP verifies identity and the other safeguards built into the platform.

1. Why we verify identity

On LARP, Owners meet Creators in person at a Session, around a high-value car. To make that safer and to deter fraud and fake accounts, we verify that both sides of that meeting are a real, identifiable person: an Owner before their first Listing is published, and a Creator before they can book a Session. Verified hosts get a badge on their profile.

2. What we check

It is the same check for everyone, and you only do it once. For an Owner it happens before your first Listing is published and unlocks publishing; for a Creator it happens before your first booking and unlocks booking. Re-verification may be requested if information changes or for safety/fraud reasons.

3. Who performs it

Verification is performed by Stripe Identity, a third-party identity-verification service. Stripe captures and processes the ID and selfie and acts as the biometric processor; LARP minimizes its own handling of biometric data. Because the selfie/face-match involves biometric information, you must accept the Biometric Consent Notice before capture, and all of it is handled per the Privacy Policy.

4. Verify to transact — not to browse

You can download LARP, create an account, and browse Cars without verifying. Verification (and the biometric consent) is required the first time you transact — when an Owner goes to publish their first Listing, and when a Creator goes to book their first Session. If you choose not to verify, you can still browse, but you can't publish a Listing or book a Session.

5. What verification is — and isn't

6. The rest of LARP's trust & safety model

Verification is one layer. Others are built into the product:

7. Owners

Owners complete Stripe Identity verification (the government-ID + selfie check described above) before they can publish a Listing, and onboard with Stripe Connect Express as individuals to receive payouts. Each vehicle is also VIN-verified — the VIN is checked against the Listing's stated year, make, and model, and changing a VIN suspends publishing until it's re-verified. Owners are subject to the same conduct standards and reviews.

8. Creators

Creators complete the same Stripe Identity verification (government ID + selfie) before they can book a Session. A booking request from an account that has not verified is refused. Creators do not receive payouts, so there is no Stripe Connect onboarding on the Creator side — verification and the Biometric Consent Notice are the only identity steps.

9. Your data

How verification data (including biometric data) is collected, stored, retained, and deleted is described in the Privacy Policy and the Biometric Consent Notice. You can request deletion as described there, or contact us at admin@larp.global.

LARP · admin@larp.global · Legal hub · Delete account