Deposit, Verification & Cancellation Policy

Part I. Owner Verification

1. Purpose of verification

Owner verification aims to reduce the risk of unreliable, misleading, or fraudulent Offers being published on the Platform and to increase Guest safety. Access to the listing-creation features (for campervans and camping pitches) depends on successfully completing this process.

2. Required documents

Depending on the declared type of activity, an Owner submits: For "campervan" Offers (vehicle rental): • a copy/photograph of the vehicle registration certificate, • proof of current mandatory third-party liability (civil liability) insurance for the vehicle, • optionally: a document confirming legal title to use the vehicle, if the Owner is not listed as the owner/co-owner on the registration certificate. For "camping" Offers (provision of overnight accommodation): • a document confirming legal title to the land (ownership, lease, a rental agreement with a right to sublet) or another document reasonably confirming the entitlement to offer overnight accommodation on the given site, • optionally: confirmation of registration of agritourism/camping activity in the relevant register, where applicable. The Operator reserves the right to request additional documents or clarification in individual cases.

3. Process

1. The User completes a request form on the Platform, indicating the type of activity planned (campervan / camping / both), a brief description, and attaching the required documents. 2. The request is manually reviewed by an authorized Operator representative. The indicative review time is up to 3 business days from submission — this timeframe is indicative and may be extended in the event of a high volume of requests or the need to clarify doubts. 3. The User is informed of the outcome of the review (approved / rejected) on the Platform and, where technically possible, also by electronic means. 4. If a request is rejected, the User may submit a new request after remedying the identified deficiencies or clarifying any doubts.

4. Legal nature of the verification

The review conducted by the Operator constitutes an examination of the documents submitted by the User for completeness and reliability, not an independent legal, technical, or expert assessment. Approval of a request does not constitute: confirmation of the technical condition of the vehicle/site, a guarantee that a given Owner's future Offers will conform to the actual facts, or a recommendation by the Operator as to the quality of that Owner's services.

5. Revocation of status

The Operator may revoke Verified Owner status where: there are reasonable doubts as to the authenticity of the documents submitted, there are repeated and substantiated Guest complaints regarding a given Owner, these Terms have been breached, or applicable law has been breached. Revocation results in the loss of the ability to publish new Offers; it does not automatically affect already confirmed Bookings, unless their continuation would endanger Guest safety.

Part II. Guest Identity Verification

6. When required

Identity verification via Stripe Identity is required before a Guest's first Booking of a "campervan" type Offer. Subsequent campervan bookings by the same Guest do not require re-verification, unless the Operator decides otherwise for safety reasons. This requirement currently does not apply to bookings of "camping" type Offers or standalone Add-ons.

7. Process

The Guest submits — directly to Stripe Identity, outside the Operator's infrastructure — a photograph of an identity document/driving licence and a "selfie" photograph for matching purposes. The Operator receives only the result: verified / not verified / processing. If the result is "not verified," the Guest may retry the verification.

8. Limitations

A positive identity verification result confirms only that the data matches the submitted document in the assessment of the Stripe Identity system — it does not confirm that the Guest holds a valid driving licence entitling them to operate the specific type of vehicle, nor that any other conditions required by a given Owner (e.g. minimum age, minimum driving experience) are met — verifying these upon vehicle handover remains the Owner's responsibility.

Part III. Deposit / Security Deposit

9. Setting Deposit terms

For each Offer, the Owner independently sets: (a) whether a Deposit is required, and if so, its amount, and (b) the permitted settlement method: • card only (an authorization/hold on funds, not a charge), • cash only, upon handover of the subject matter of the Booking, • the Guest's choice between the two options above. These terms are visible to the Guest before making the Booking.

10. Card Deposit — mechanism

1. The hold (authorization) on the Guest's card is placed via Stripe, as an operation separate from the main Booking payment, on the Owner's settlement account (Stripe Connect). 2. The hold is placed within a time window preceding the Booking's start date — currently 2 days before the start date (the Operator reserves the right to change this window in the future, and will inform Users in accordance with the rules on amending the Terms of Service). 3. If, at the time a Guest or Owner visits the given Booking's page within this time window, the hold has not yet been placed, the Guest is presented with a form to authorize their card. 4. After the Booking ends, absent any objection raised by the Owner, the hold is released. The technical release of funds to the Guest's bank account may take a further few business days, depending on the card-issuing bank — the Operator has no control over this. 5. In the event of documented damage, additional charges arising from the Offer (e.g. excess mileage fees, fees for non-compliance with the Offer's rules), or other justified claims, the Owner may initiate a capture (charge) of the held amount, in whole or in the part corresponding to the claim.

11. Cash Deposit

A cash Deposit is handed over and settled directly between the Guest and the Owner upon collection and return of the subject matter of the Booking, outside the Platform's payment system. The Operator does not act as an intermediary in its physical handover, custody, or return, and is not liable for the correctness of this settlement — responsibility rests solely with the parties to the agreement (Guest and Owner).

12. Disputes regarding the validity of a Deposit retention

1. In the event of a dispute regarding the validity of a Deposit retention (capture), the parties should first attempt an amicable resolution via the Platform's messaging system. 2. The Operator does not act as an arbitrator or mediator in such disputes and does not determine whether the damage actually occurred or whether its amount corresponds to the amount retained — such an assessment falls outside the Operator's role as a technology intermediary described in §2 of the Terms of Service. 3. Absent an agreement, either party may pursue its claims through the means provided by law, including out-of-court consumer dispute resolution (§19 of the Terms of Service) or court proceedings. 4. It is recommended that the Owner document the condition of the subject matter of the Booking with photographs upon collection and return — such documentation facilitates the resolution of any dispute, although it is not currently a technical requirement of the Platform.

Part IV. Cancellation and Refunds

13. Cancellation policies — three options available to the Owner

1. When listing an Offer, the Owner selects one of three cancellation policies available on the Platform, applicable to that specific Offer. The selected policy is visible to the Guest on the Offer page, before making a Booking: • Flexible — full refund (100%) for cancellations made 30 or more days before the Booking start date; 50% refund for cancellations made within the last 30 days before that date. • Moderate (the default if the Owner does not make a selection) — full refund (100%) for cancellations made 30 or more days before the start date; 50% refund for cancellations made 8–29 days before; no refund (0%) for cancellations made within the last 7 days before the start date. • Strict — full refund (100%) for cancellations made 30 or more days before the start date; no refund (0%) for cancellations made within the last 30 days before that date. 2. Before the Booking is confirmed — if, for any reason, the Booking does not go through (e.g. a technical payment failure), any previously placed payment authorization is cancelled automatically, with no refund obligation arising (since funds were never actually captured). 3. Cancellation by the Guest after Booking confirmation — the Guest may initiate cancellation at any point until the end of the Booking period, directly on the Platform. Before confirming the cancellation, the Platform shows the Guest an exact preview: the number of days remaining until the start date, the cancellation policy applicable to that Offer, the refund amount due and — if the policy does not provide for a full refund — the cancellation fee amount. 4. If, under the selected policy, the Guest is entitled to a full refund (100%), the cancellation is processed immediately, and the entire amount paid is automatically refunded to the Guest via Stripe. 5. If, under the selected policy, the refund is partial or none, the technical mechanism works as follows: the booking system underlying the Platform (Sharetribe) always refunds the Guest 100% of the amount paid upon cancellation — the Platform collects the difference corresponding to the non-refundable percentage (the cancellation fee) from the Guest through a separate payment transaction (Stripe) before the cancellation is finalized. The Guest must actively confirm this fee (by entering card details or confirming payment) — only once it is paid is the Booking actually cancelled and the dates released. 6. After the Booking period ends — the Booking is automatically marked as completed 48 hours (2 days) after the end of the booked period, which triggers payout of funds (less the Operator's commission) to the Owner. After this point, cancellation and refund are no longer available through the Platform's standard mechanism — any claims are handled through the complaint procedure (§19 of the Terms of Service). 7. The above applies to the main Booking payment. Settlement of the Deposit (authorization/hold) occurs independently, in accordance with Part III of this document, and is not covered by the refund mechanism described above. 8. Cancellation by the Owner for an unpaid split-payment balance — if the Guest used split payment (point 15) and did not pay the balance by the specified deadline, the Owner may manually close such a Booking in order to release the dates for other Guests. Due to the technical limitation described in paragraph 5 (Sharetribe always fully refunds the amount paid upon cancellation), using this option results in the previously paid deposit being refunded to the Guest despite the balance never being paid — the Owner is explicitly informed of this before confirming the action, and takes it knowingly, in exchange for the ability to offer the dates to other Guests.

14. Refunds

Refunds are processed via Stripe, to the payment method used to make the Booking, within the customary timeframe for such operations (up to a few business days, depending on the Guest's bank).

15. Split payment (deposit and balance)

1. If a Booking is made at least 30 days before the start date of the stay/rental, the Platform allows the Guest to split payment into two parts: a deposit equal to 30% of the total Booking value, payable immediately upon making the Booking, and a balance equal to the remaining 70% of the Booking value. 2. The balance must be paid no later than 30 days before the start date of the stay/rental. During the 7 days preceding that deadline, the Guest receives reminders via the Platform (notifications visible in the Guest's Account) about the need to pay the balance. 3. If the Guest does not pay the balance by the above deadline, the deposit (30% of the Booking value) is non-refundable, and the Booking will not be fulfilled. The Owner is notified of this via the Platform. 4. The balance is settled through a separate payment transaction (Stripe) from the deposit and is subject to the same Operator commission as the main payment for the Booking. 5. Settlement of the Deposit (authorization/hold) proceeds independently of the split payment, in accordance with Part III of this document.

Part V. Offer Add-ons

16. Nature of Add-ons

Add-ons (e.g. additional equipment, a bicycle, extended insurance) are independently defined by each Owner for their own Offer — the Platform does not maintain a shared, independent catalogue of Add-ons available from different Owners. The name, description, and price of an Add-on are set entirely by the given Owner and relate solely to their Offer.

17. Liability for Add-ons

The Owner is liable for the accuracy of an Add-on's description and price to the same extent as for the Offer itself (§9 and §16 of the Terms of Service). An Add-on is booked together with the main Offer and settled as part of the same payment. This document is also available in a Polish-language version. In the event of any discrepancy between the Polish version and the English version, the Polish version shall prevail.