Parking-space insurance and damage: what a host should clarify first
Insurance and damage questions should be answered before the first booking, not after a disagreement. A host should never promise that a vehicle, gate, or personal property is covered unless the relevant policy or platform terms actually say so. This guide is a preparation checklist, not legal or insurance advice.
Separate the risks
Write down the different things that can happen: damage to the driver's vehicle, damage to the building or gate, theft of items left in the vehicle, a lost key or access device, and an injury on the property. Each may be governed by a different contract or policy. Read the current Figpark terms, your property or liability insurance, and any building rules; ask an insurer or qualified adviser when the answer affects your cover.
Before publishing, photograph the space, gate, walls, markings, lighting, and any existing damage. Keep the date and the original listing description. State what the driver must do, such as staying inside the marked bay, using a particular gate, or reporting an access problem. Do not collect unnecessary personal information or publish private security details.
Make an incident easy to document
If something happens, stay factual. Record the booking, time, location, visible condition, messages, and photographs. Avoid admitting liability or promising a payment before the facts and the applicable terms are clear. Use the platform's support route for booking-related disputes and contact emergency services when there is an immediate safety issue.
The privacy and security guide covers what to share with a driver, while the host landing page is the right starting point for listing. For rules and tax questions, read the Czech rules guide and get professional advice for your situation.