Cancellation Policy

Overview

Routebook is a platform for discovering and coordinating travel between users. When a Guest Member elects to pay a cost-sharing contribution for a seat through the Platform, Routebook — acting as the Host Member's limited reimbursement agent — facilitates that payment through Stripe. This Cancellation Policy describes what happens on the Platform when either Member cancels before or after a payment has been settled, including the refund amounts Routebook will cause Stripe to issue in each scenario.

This Policy forms part of the Terms of Service.

1. Invitations and Confirmations Are Not Binding Contracts

When a user sends a ride invitation and another user accepts it, this exchange takes place entirely within Routebook's messaging and invitation features. It is a communication — not a contract, booking, or legal commitment.

Routebook is not a party to any travel arrangement and does not enforce any agreement between users. Users coordinate the details of their travel — including whether to proceed, what cost-sharing (if any) is appropriate, how to handle changes, and how to resolve disagreements — directly with each other.

2. Cancelling on the Platform

Either Member may cancel a confirmed booking at any time through the app. Cancellations are communicated to the other Member via in-app notification and a system message in the conversation thread.

When a cost-sharing contribution has been paid through the Platform, cancellation triggers an automatic refund under the tiers below. Cancellations where no in-platform payment was made (zero-contribution rides, or private off-Platform arrangements) do not result in any Platform refund — the booking is simply released and the other Member is notified.

We encourage Members to cancel as early as possible as a courtesy to the other party.

2.1 Refund Tiers When a Cost-Sharing Contribution Has Been Paid

The refund tier is determined mechanically from (a) who cancelled and (b) when the cancellation was entered relative to the posted departure time:

Refunds are issued to the original payment method via Stripe and typically appear within 5–10 business days, subject to the issuing bank's timing.

3. No-Shows

Routebook has no mechanism to verify, confirm, or adjudicate no-shows. If a user fails to appear as arranged, the other user's recourse is to contact them directly through in-app messaging.

Repeated no-shows that are reported to Routebook may be factored into account standing. Routebook does not guarantee any outcome in such cases.

4. Routebook's Role in Disputes

Routebook does not mediate, arbitrate, or resolve disputes between users over travel arrangements, cancellations, or any payment or cost-sharing agreement.

If users have a disagreement about a cancelled or failed trip, including any money exchanged between them, that disagreement is between the users. Routebook has no visibility into private financial arrangements and cannot take action on them.

If a user's conduct on the Platform (e.g., in messages) constitutes a violation of our Terms of Service or Community Guidelines, you may report that conduct to us. We may take account action in response to Platform conduct violations, but we cannot recover funds or enforce private financial agreements.

5. Removing a Route Posting

A user who posted a route may remove that posting at any time through the app. Removing a posting does not automatically notify other users who had accepted or expressed interest in the route — we recommend sending a message to any such users before removing the post.

6. What Routebook Does Not Handle

To be explicit about the current boundaries of this Platform:

7. Contact

For questions about this Policy or to report a concern about another user's Platform conduct:

RouteBook LLC  ·  [email protected]