Privacy

Page views are recorded without storing anything that identifies you. There is no cookie for analytics and no advertising identifier involved. Each event stores the page path, the language, the type of event, and a visitor hash.

The visitor hash is worth explaining, because it is the part people are usually right to be suspicious of. It is a keyed hash of your IP address, your browser user-agent string, and the current date. Your IP address is never written to the database — only the hash is — and because the date is part of the input, the hash changes every midnight UTC. That means we can tell that two page views in one day came from the same browser, and we cannot tell that today’s visitor is the same person as yesterday’s.

Requests that identify themselves as bots are discarded before anything is stored.

These rows currently have no automatic expiry. That is a gap rather than a policy, and it is being addressed.

When you request a quote, the form collects what an operator needs in order to answer you:

• your name and email address
• your phone or WhatsApp number, if you choose to give one
• where you want to go, when, and how many of you there are
• a budget range, if you enter one
• the message you write
• the page you came from, so we can tell which listing prompted the enquiry

This is passed to the operators we match you with. That is the entire point of the form — an enquiry nobody receives is not an enquiry — but it does mean your details leave this site and reach a tour company. We match on where you are going and what you asked for, and we tell you which companies received it.

If you create an account, we store your email address, your name, and whatever you add afterwards: saved trips, saved listings, reviews you write. Sign-in is handled by Supabase; where Google or Apple sign-in is enabled, that provider tells us your email address and name and nothing else.

Two different things on this site ask a browser for a location, and they are worth separating.

On the near-me page, pressing "Use my location" asks your browser for your position and sends it to our server once, to run one query. It is not written to the database, it is not logged, and it is not put in the address bar — the search is a form submission rather than a link, precisely so that your position does not end up in your history or in a referrer header. It is also used to centre the map, which means OpenStreetMap receives a request for the tiles around you and can infer roughly where you are from it. The prompt only appears when you press the button.

If you run a business listed here, the dashboard offers to record your location so that travellers searching nearby can find you. That coordinate is stored, and it is shown publicly on your listing and on maps — that is what it is for. It is only stored if you press the button; nothing is captured in the background, and you can change it whenever you like.

Where a listing has no coordinates of its own, it may be placed at the centre of the town named in its address. Those are marked as approximate everywhere they appear, and no distance is shown for them, because the centre of a town is not an address.

Signing in sets a session cookie. It is necessary — without it you would be signed out on every page — and it is removed when you sign out.

A short-lived cookie also remembers where you were heading when you were asked to sign in, so you land back on the right page afterwards.

Your language and light or dark preference are stored in your browser, not on our servers.

Google AdSense is loaded on travel guide pages and sets its own cookies, which are outside our control and are governed by Google’s policies. There is currently no consent banner offering you a choice about this before it loads. If you are in the EU or UK, that is not the standard you are entitled to, and it is being fixed rather than defended.

• Supabase — hosts the database and handles sign-in. All of the above is stored there.
• Vercel — serves this site and processes the requests that reach it.
• Tour operators — receive the enquiries you send them, and only those.
• Flutterwave — processes payments from operators subscribing to paid plans. Card details go to Flutterwave directly; this site never sees or stores them.
• Google AdSense — serves advertising on guide pages.
• OpenStreetMap — serves the map tiles on destination, directory, listing and near-me pages. Loading a map sends your IP address and the tile coordinates you are looking at to their servers. On the near-me page those tiles are centred on you, so the request reveals roughly where you are. A map is only loaded once it is on screen, so a page you do not scroll through sends nothing — but on the near-me page the map is the first thing under your results, so it loads as soon as they appear.

We do not sell anything to anyone, and we do not share your enquiry with operators you were not matched to.

You can ask for a copy of what we hold about you, ask us to correct it, or ask us to delete it. Deleting your account removes your profile, your saved trips, your saved listings and your reviews.

Enquiries you have already sent are the exception worth being straight about: once an operator has received your message, we cannot reach into their inbox and remove it. We can delete our copy.

To make any of these requests, use the contact page.

This site is for people arranging travel and is not intended for children. We do not knowingly collect information from anyone under 16.

When this page changes, the date at the top changes with it. There is no notification list; the date is the record.