RideLoop

Trust

What’s enforced, not just written down.

You’re trusting us with your takings, your guests’ details and your busiest weekends. So here are the rules RideLoop runs on, where each one is enforced, and the few things we don’t do.

Read the house rulesWho sees your data

Money

Your money never passes through us.

RideLoop isn’t a payment middleman. Every booking, payment link, card-at-the-counter charge and deposit is a direct charge on your own Stripe account.

Paid out by Stripe, to you
Payouts, refunds and disputes live in your own Stripe dashboard, not in a support ticket to us.
We never see your Stripe keys
RideLoop stores your account ID and nothing else. There are no keys of yours on our servers to leak.
Our commission comes back with every refund
Refund a booking and RideLoop refunds its own cut alongside. Lose a chargeback and our commission is reversed automatically.
Deposits and tax are never commission-bearing
A damage claim is never RideLoop revenue, and tax is itemised separately and left out of the commission sum.

Honest by default

Nothing on your storefront manufactures urgency.

Every nudge a guest sees is backed by a real number with a real threshold. We decided the rules once, so no one has to argue about them per booking.

“Almost full” only when it is
The scarcity badge on a tour appears only when 1–5 real places remain.
“Popular” only after real views
Built from real 7-day view counts, and never shown before at least five real views.
A dash, never a fake zero
If a figure can’t be honestly computed, reports show a dash or a labelled estimate. “All time” shows no invented trend arrow.

The AI assistant

It looks things up freely. It asks before it touches anything.

Miles has more than 48 tools. Nine of them can change something, and every one of those needs a person to approve it. It works inside the same staff permissions as the rest of the app, so a counter login can’t do more through the chat than it can on the desktop.

  • Always disclosed as an AI assistant, to meet EU AI Act Article 50.
  • Never concedes fault, offers a refund or promises a policy change on its own.
  • Won’t override a guide’s recorded time off, even when asked.

Your guests’ data

Kept as long as the law needs, and no longer.

Retention runs on a nightly schedule, not a policy someone has to remember. The same figures are in our published Privacy Policy.

Any time

Erasure on request

A guest’s name, phone and identity are redacted as soon as the request is actioned, with a visible “Redacted” marker.

12 months inactive

Identity anonymised

Identifying details on bookings, quotes and chats are removed automatically. The record stays; the person doesn’t.

24 months inactive

Chats and audit rows deleted

Guest chat threads and internal audit-log rows are deleted by the same nightly sweep.

Always kept

Bookings and money

Booking and financial records are kept, as UK tax and accounting law requires.

Your team sees what their role allows
Five roles and a nine-action permission matrix, checked on the server for every change. A section a role can’t use simply isn’t there.
Guides see their own groups
A guide sees only the groups they’re assigned, never your wider bookings or finances.
Your data leaves with you
Export your bookings and customer records as CSV whenever you like. No contract and no exit fee, so you’re never kept by your own data.

Every change, and who made it, on your own audit log.

Engineering

Tested the way you’ll use it.

A change that breaks a real booking fails before it ships, not after you find it on a Saturday.

100% automated test coverage
Lines, branches, functions and statements on the business logic and API, enforced on every change.
Real browsers, real Stripe
A separate suite signs in, checks out in Stripe test mode and sends real emails against a throwaway database. No stand-ins.
Daily backups, stated plainly
The database is backed up every day. It isn’t point-in-time, so a worst-case restore could lose up to the last 24 hours.
A status page that explains itself
Every incident on rideloop.co.uk/status is resolved with a written explanation. There’s no numeric uptime SLA, and we don’t pretend otherwise.

Read the fine print before you sign up.

Our Terms, Privacy Policy and Cookie Policy are published in full. No contract, no exit fee, and your bookings and customers export as CSV any time.

Book a walkthrough