Skip to content

Privacy

Last updated 16 October 2026

Who we are

Boundl is based in Scotland, United Kingdom. We decide how your information is used. Questions or requests: contact support@boundl.app.

What we collect and why

  • Your email address, to sign you in with one-tap links and to send booking confirmations.
  • Creator profiles and trips you publish: your name, handle, bio, the days, places, photos and videos you add. These are public once you publish.
  • Bookings: where you’re starting from, dates, what you chose and what you paid, so we can book your trip and show it in your account.
  • Traveller details for each booking: everyone’s name as on their passport, date of birth and passport gender, and the lead traveller’s email and phone. Airlines and hotels require these to issue tickets and reservations, so we pass them only to the suppliers of your trip. If you book for others, please make sure they’re happy for you to share their details.
  • Saved trips, so you can find them again. Only you can see what you saved; others only see a total count.
  • Searches for places, to suggest destinations and stops.
  • Trip page views, counted once per browser session without cookies or anything that identifies you, so creators can see how their trips are doing and we can see where people stop before booking.
  • Visit statistics through Vercel Web Analytics: which pages are visited, the kind of device and the country, counted without cookies and never linked to you. We remove anything in page addresses that could say where you’re travelling from before it’s sent.

We use this to run the service you asked for (our contract with you) and, for booking confirmations, because we have to. We don’t sell your information or use it for advertising.

The waitlist

If you ask us to tell you when bookings open, we keep your email address (and the trip you were looking at, if any) to send you that one email. We don’t share it or use it for anything else. Ask us to take you off the list at any time, and we’ll delete the list once bookings are open and we’ve told everyone.

Instagram

If you’re a creator and choose to connect Instagram, we ask Instagram only for permission to read your profile name and your own posts (instagram_business_basic). We store your Instagram username and an access token so you can import posts later; the token is kept on our servers and never shown in your browser.

We only copy the posts you pick into a trip. Copies are stored with the trip and shown publicly when the trip is published, like photos you upload yourself. We don’t post to Instagram, read your messages or comments, or look at anyone else’s account.

You can disconnect at any time from the trip editor (“Import from Instagram”, then “Disconnect Instagram”): we delete the token straight away. See deleting your data.

Who we share it with

Only the services that run Boundl for us, each for its own part:

  • Supabase (database, sign-in and file storage)
  • Vercel (hosting the website)
  • Stripe (payments; we never see or store your card details)
  • Klarna, if you choose to pay with it at checkout
  • Resend (sending emails)
  • Geoapify (place search, using OpenStreetMap data)
  • Instagram (only if you connect it)
  • Travel suppliers (airlines, hotels and others), only the details needed to book your trip

Some of these may process data outside the UK, under safeguards such as standard contractual clauses.

How long we keep it

We keep your account and trips until you ask us to delete them. Booking records are kept for as long as the law requires for tax and accounting.

Your rights

You can ask to see, correct, export or delete your information, or object to how we use it. Contact support@boundl.app. If you’re unhappy with how we handle it, you can complain to the Information Commissioner’s Office (ico.org.uk).

Cookies

We only use cookies to keep you signed in, to remember which currency you see prices in, and to secure the Instagram connection. On booking pages, Stripe sets its own cookies to prevent payment fraud. No advertising or tracking cookies.