Conditions for booking and using the fips transport service
General Terms and Conditions of Business
§ 1 Scope of application
(1) These General Terms and Conditions ("GTC") apply to all legal relationships in connection with the provision and use of the "fips" transport service of Rhein-Neckar-Verkehr GmbH ("rnv"). rnv expressly reserves the right to adapt the fips offer at any time.
(2) The transport services are subject to the conditions of carriage and fare regulations of Verkehrsverbund Rhein-Neckar ("VRN"). The current version is available at vrn.de/tickets/tarifsystem/befoerderungsbedingungen.
§ 2 Subject matter of the contract
(1) rnv operates a transport service without fixed departure times and fixed routes under the product name fips. The chargeable transport service ("journey/journeys") is provided by rnv or by third parties commissioned by rnv.
(2) The service allows registered passengers ("customers") to submit journey requests, stating the desired departure and destination points and the desired departure or arrival time, and to make binding bookings for specific journey offers. Journeys take place in cars/vans and are potentially shared with other passengers.
§ 3 Registration & contract of use
(1) In order to be able to use the fips service, the passenger must create a fips customer account ("customer account") by providing the following information truthfully and completely:
- Full name and address
- date of birth
- contact details
- If applicable, payment method and corresponding payment information
- Details of existing ticket, if applicable
- Consent to the General Terms and Conditions
- Consent to the privacy policy
- Consent of the legal guardian(s) or legal representative for underage users (surname, first name and address)
(2) Registration can be carried out in the fips app and at designated registration centres.
(3) By registering and opening a user account, a contract of use for the use of the fips platform is concluded between rnv and the passenger and the passenger accepts these GTC and the validity of the VRN fare regulations and conditions of carriage referred to in the GTC.
(4) The customer undertakes to keep the data essential for the contractual relationship up to date in the fips customer account.
(5) If the customer fails to fulfil his obligation to provide information, the customer may be charged for the additional costs incurred as a result.
§ 4 Software licence for the fips app
(1) rnv provides the customer with software ("app") for using the fips service. The app user ("User") must install this on their own mobile phone.
mobile phone. A compatible mobile phone is required for use. The user can use the app to request, book and pay for journeys without obligation.
(2) By accepting these GTC, rnv authorises its customers to use the fips app for the purposes described above. The customer is prohibited from using, changing and/or modifying the software in any other way. In this respect, the customer is also not permitted to rent, lend, sell, licence, assign or otherwise transfer the right granted to him to the software.
(3) The customer further undertakes to refrain from determining the source code of the software. rnv does not assume any warranty with regard to the applicability and performance of the software. With regard to liability, the provisions of § 11 shall apply.
(4) No fees are charged for downloading or using the app. The user shall only bear the connection costs arising from the use of the app and the download.
(5) When using the fips app for the booking, the customer must ensure the technical requirements for the proper use of the app.
§ 5 Booking in the fips app
(1) To request a journey, the user must enter or select the desired departure and destination. The user can activate an automatic location recognition service in the app.
(2) If the departure and destination requested by the user are within the service area and the request is within the operating hours, the user can provide further information on the desired departure or arrival time, the number of passengers and accessibility requirements in the next step.
(3) If not already stored in the customer account, information on the ticket used per passenger and, if applicable, manual selection of the corresponding fare product is required.
(4) In the next step, the user is shown a summary of the details provided for the desired journey. By clicking on the "Request journey" button, the user submits an offer to rnv to conclude a transport contract for the selected transport service.
(5) As a result, the user receives confirmation of the journey request as well as information on the boarding and alighting locations, the estimated departure and arrival times and the vehicle assigned to him/her. This process represents a purely formal summary of the booking request for the customer and not yet a declaration of acceptance for the conclusion of a contract of carriage. The specified journey time may be shortened or extended depending on the traffic situation and the bundling of the journey with other guests.
(6) If no journey is available at this time, the user will be informed accordingly. No costs will be incurred; a new journey request can be made at any time.
(7) Until the start of the journey, the user has the option of changing the details provided in the journey request.
(8) Upon commencement of the journey, a chargeable contract of carriage is concluded between the passenger and rnv.
(9) The user is not obliged to start the journey in person. A booking for a third party is permitted.
(10) In the event of repeated non-appearance at the specified pick-up time at the specified pick-up location, rnv reserves the right to temporarily or permanently exclude the user from the fips service.
§ 6 Booking by telephone
(1) rnv provides registered customers without access to a mobile phone with the option of booking journeys by telephone. The booking of journeys by telephone is limited compared to the functional scope of booking by app.
(2) To make a telephone booking, the customer ("caller") must identify themselves to the service employee on the telephone ("service employee") using the information provided during registration.
(3) To request a journey, the caller must state the desired departure and destination.
(4) If the departure and destination requested by the caller are within the service area and the request is within the operating hours, the passenger can provide further information to the service employee in the next step regarding the desired departure or arrival time, the number of passengers and accessibility requirements.
(5) If not already stored in the customer account, details of the ticket used per passenger are required so that the service employee can select the appropriate fare product.
(6) A ticket valid at the time and place of the requested journey is required for a journey booked by telephone, as VRN tickets are not sold by telephone or in the vehicle.
(7) When booking by telephone, availability is checked, possible journeys are selected and a journey is booked in a dialogue between the caller and the service employee.
(8) In the next step, the service employee provides the caller with a verbal summary of the information provided about the desired journey.
(9) With the caller's verbal confirmation ("Request journey"), the user submits an offer to rnv to conclude a transport contract for the selected transport service.
(10) As a result, the caller receives confirmation of the journey request from the service employee as well as information on the boarding and alighting locations, the estimated departure and arrival times and the vehicle assigned to him/her. This process is purely a formal summary of the booking request for the customer and does not constitute a declaration of acceptance for the conclusion of a contract of carriage. The specified journey time may be shortened or extended depending on the traffic situation and the bundling of the journey with other guests.
(11) If no journey is available at this time, the caller will be informed accordingly. No costs are incurred; a new journey request can be made at any time.
(12) A chargeable contract of carriage is concluded between the passenger and rnv upon commencement of the journey.
(13) The caller must start the journey in person. The booking is not transferable to third parties.
(14) In the event of repeated non-appearance at the specified pick-up time at the specified pick-up location, rnv reserves the right to temporarily or permanently exclude the caller from the fips offer.
(15) Furthermore, rnv reserves the right to temporarily or permanently exclude passengers from booking the fips service by telephone in the event of repeated misbehaviour.
(16) rnv may adjust the scope and availability of the telephone booking service at any time or discontinue it completely.
§ 7 Tickets, surcharge
(1) For journeys with fips, a VRN ticket valid in terms of time and area and, if applicable, a validated ticket is required. It is not possible to purchase VRN tickets in the vehicle.
(2) In addition to the ticket, a quality surcharge is levied per passenger and journey in Mannheim in accordance with the VRN fare regulations. This quality surcharge must be paid via the fips customer account. It is not possible to pay the surcharge in the vehicle.
(3) The fips app also offers the option of purchasing tickets for the airline fare. For customers who make use of this option, the general terms and conditions of the Luftlinientarif also apply. The current version is available at https://www.rnv-online.de/tickets/ticket-kaufen/digital/etarif/. The best price optimisation offered as part of the airline fare is currently not possible when purchasing airline fare tickets for fips.
(4) If the journey is cancelled prematurely by the user or passenger, the fare owed will not be refunded.
(5) Severely disabled ID cards with a corresponding token are also recognised by fips within the scope of their validity for local transport. The surcharge payable for fips is also waived for severely disabled persons. For this purpose, holders of severely disabled ID cards with a corresponding token must present them once electronically at the e-mail address fips(at)rnv-online.de or in person at the designated registration centres for verification and registration. Activation is carried out by rnv in the same way as the validity of the token for the severely disabled person's ID card and is stored in the customer account.
§ 8 Transport, inspection
(1) The customer must arrive at the specified pick-up point at the time specified in the booking. If the passenger is not present, the customer has no right to expect the vehicle to wait or the driver to contact the passenger.
(2) A journey can only be started with a valid ticket in accordance with the VRN fare regulations and a fips booking.
(3) To identify the passenger, the driver will ask for the last four digits of the telephone number and/or the initials of the customer when entering the vehicle.
(4) In addition, depending on the VRN ticket, an automatic ticket check or a visual check of the VRN ticket is carried out by the driver.
(5) If the number of persons specified in the booking is exceeded at the time of collection, the driver is authorised to exclude excess persons from the journey.
(6) The user or passenger must fasten their seatbelt before the start of the journey and must remain fastened until the end of the journey. For the transport of children up to 12 years of age or a height of up to 150 cm, child seats are compulsory in the vehicles. For this purpose, some vehicles have child seats for children aged 9 months and over, which must be booked at the time of booking. There is no entitlement to availability.
(7) In the event of an inspection, the customer must provide the ticket inspector with the valid booking together with an official photo ID and the VRN ticket for inspection. The risk for the proof of validity lies with the user.
(8) In the event of a ticket inspection, the customer hereby agrees that if there are any doubts about the correctness of the ticket, a detailed inspection will be carried out by the inspection staff.
(9) In the event of any doubts, the customer hereby agrees to initially pay an increased fare in accordance with the relevant fare regulations and conditions of carriage.
(10) The customer shall not be entitled to claim damages for loss of time in connection with a detailed inspection, in particular the assertion of any loss of profit.
§ 9 Cancellation by rnv, refund
(1) Bookings can be cancelled by rnv. This may be the case, for example, in the event of a technical defect, accident or serious traffic obstructions due to traffic jams or weather conditions. If the booking is cancelled by rnv, the customer will not incur any costs and any payments already made will be refunded.
(2) Promotional credit credited to the passenger by rnv cannot be refunded or paid out. It can only be used within the framework of the customer account.
§10 Payment procedure and billing
In addition to the conditions described above, the following regulations apply to the payment of purchased tickets.
(1) The customer can choose between the following payment methods for orders via the fips customer account:
- Payment by SEPA direct debit
- Payment by credit card
(2) Invoices are issued in the name of rnv. Billing is carried out via the payment service provider Stripe Payments Europe Ltd.
§ 11 Liability of rnv and its service providers
(1) The liability of rnv, its legal representatives and/or vicarious agents is excluded in the event of simple negligence in the event of a breach of non-essential contractual obligations and, in the event of negligence, is otherwise limited to the foreseeable damage typical of the contract. Essential contractual obligations are those without the fulfilment of which the purpose of the contract is jeopardised or on the observance of which the contractual partner may rely. However, this shall not apply in the event of injury to life, limb and health or in the event of breach of a guarantee and liability under the German Product Liability Act (ProdHaftG).
(2) rnv expressly points out that the contractual partner of the transport contract concluded with the use of fips is the respective transport company and that the transport is carried out exclusively in accordance with the tariff regulations and conditions of carriage of the VRN. Accordingly, any warranty and/or liability on the part of rnv for any damage, complaints or claims by the customer with regard to the services received under the transport contract is excluded, unless the transport is provided by rnv. In such cases, the customer must contact the transport company directly.
(3) rnv does not guarantee the permanent, uninterrupted and fault-free availability of the fips app. This may lead to the temporary impracticability of the ticket purchase. There is no entitlement to compensation for damages resulting from the unavailability of the fips app.
(4) Likewise, rnv accepts no liability for the incorrect, incomplete or non-existent transmission of the fips ticket, provided that the error is not the responsibility of rnv or is not attributable to it.
§ 12 Blocking
(1) If the customer's payment fails, the possibility of booking journeys in the customer account will be blocked.
(2) If the customer discovers misuse of his customer account, he is obliged to block his customer account access with rnv or have it blocked by rnv. Until such time as access is blocked or the contract is terminated, any further use of services made via the customer's customer account shall be deemed to have been initiated by the customer.
(3) In the event of misuse, rnv may temporarily or permanently deactivate the customer account. This shall occur in particular in the event of repeated or individual serious violations of the VRN fare regulations and conditions of carriage as well as these GTC.
§ 13 No right of cancellation
The customer has no right of cancellation with regard to the tickets purchased, as the provisions for distance selling contracts do not apply to contracts for the carriage of passengers in accordance with Section 312 (2) No. 5 BGB.
§ 14 Cancellation of the customer account
(1) The customer may cancel the customer account with rnv electronically or in writing at any time without observing a cancellation period. Outstanding claims against the customer (e.g. settlement of unpaid journeys) shall remain unaffected by the cancellation.
(2) Promotional credit credited to the passenger by rnv shall expire. Any remaining credit that was purchased by the customer in advance will be refunded.
(3) rnv may cancel the customer account at any time by sending an e-mail to the e-mail address provided by the customer, giving 14 days' notice. Ordinary cancellation
cancellation shall take place in any case if the customer has not purchased any tickets within two years and has not made any changes to their contract data.
§ 15 Data protection in the context of the e-Payment Service
(1) The payment information you provide includes different data depending on the payment method. This personal data, the information about your ticket purchases and any changes will be processed and used by the financial company Stripe Payments Europe Ltd, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, for the purpose of processing payments and managing receivables.
(2) In the event that a customer does not fulfil their payment obligations, their personal data will be forwarded to Paigo GmbH, Gütersloher Straße 123, 33415 Verl, Germany, for the purpose of collecting the receivables (e.g. through payment reminders/reminders) and enforcing the receivables (e.g. in the context of legal dunning proceedings or cooperation with a law firm in the event of legal enforcement).
(3) If blocking lists are used, data from blocking list entries shall be deleted six months after the reason for blocking no longer applies.
(4) Customers can revoke the above-mentioned consents at any time by sending an email to kundenservice@rnv-online.de. After exercising the right of cancellation, the use of the fips offer, in particular the booking of journeys, is no longer possible.
§ 16 Amendment of GTC
(1) rnv is authorised to amend these GTC unilaterally insofar as this is necessary to eliminate any subsequent equivalence problems or to adapt to changes in the legal or technical framework conditions or due to changes in supreme court rulings.
(2) The user shall be informed of any amendment by notification of the content of the amended provisions to the last known e-mail address. The amendment shall become part of the contract if the user does not object to its inclusion in the contractual relationship in writing or text form to rnv within six weeks of receipt of the notification of amendment.
§ 17 Final provisions
(1) The law of the Federal Republic of Germany shall apply exclusively, excluding the UN Convention on Contracts for the International Sale of Goods (UNCITRAL/CISG). If the customer is a merchant or resides outside Germany, the exclusive place of jurisdiction shall be the registered office of rnv (Mannheim).
(2) Should one or more provisions of these General Terms and Conditions prove to be invalid, void or incomplete, the validity of the remaining provisions of the contract shall remain unaffected. The
The contracting parties shall replace the ineffective or void provision with such a provision or fill the contractual gap with such a provision with which the economic purpose pursued by them can best be achieved.
Data protection
As a matter of principle, rnv processes personal data only in compliance with the applicable data protection laws. You can find the privacy policy for fips here.
Mandatory information according to § 36 VSBG
rnv takes the concerns of its customers very seriously and handles them carefully in-house. Therefore, rnv does not participate in dispute resolution proceedings before a consumer arbitration board within the meaning of the VSBG. Nor is it obliged to do so.
Status: 31.10.2024