PRIVACY

RUN BGD collects personal data in exactly two places on this site: the inquiry forms and the newsletter signup. There is nothing else — no account system, no comments, no checkout.

Inquiry forms

The forms on /agency, /concept-store, /contact, /tours (including each tour and guide page) and /stay (including each listing page) ask for your name and email address, plus the fields belonging to the kind of inquiry you chose:

• Project inquiry — company, project type, services, market, timing, budget, a free-text brief, and an optional file you attach (a brief, a deck, a budget document — up to 10 MB).
• Partnership inquiry — organisation, partner type and a free-text description of your interest.
• Press inquiry — outlet, topic and deadline.
• General inquiry — a free-text message.
• Tour booking request — from a tour page or a guide page: which tour or which guide, your preferred date, an optional alternative date, the size of your group, the language you want the tour in, and an optional free-text box for accessibility needs or anything else we should know.
• Guide application — from /tours, if you want to guide with us: the languages you speak, your specialities and a free-text description of your experience.
• Partner application — from /stay, if you have somewhere to let: your organisation's name, what kind of operator you are (landlord, letting agent, relocation agency and so on) and how many places you have. Nothing you send here publishes anything — a person reads it, and a partner is verified by hand before any listing of theirs appears.
• Stay request — if you are looking for somewhere to live: the date you want to move in, an optional move-out date, how many people are moving, your monthly budget, the areas you are interested in, optionally where you will work or study, whether you have pets, and a free-text box for anything else a landlord would need to know. You have to tick a consent box before it can be sent, and the time you ticked it is stored with the request.

A stay request is the one form on this site that asks you to consent explicitly, because what it collects is a picture of your life at a particular moment — when you are moving, how many of you there are and what you can afford. It is used to match you to listings by hand and passed on to a service partner only as part of arranging a viewing you asked for. We never publish it, and a partner's own contact address is used internally to route your request — it is never shown on a public page. RUN BGD does not take deposits or rent: Never pay a deposit through chat. Verify the contract, the owner's authority and the payment details before transferring money.

The accessibility box on a booking request deserves its own sentence, because you may choose to put health or mobility information in it. It is optional — a booking request is complete without it — and if you do write something there it is stored and handled exactly like every other free-text field on this page: kept in the same database row, readable by the RUN BGD team through the admin, and passed on to the guide only as part of arranging the tour you asked for. It is never used to segment, profile or target you, and it is deleted when the rest of the request is. Tell us only what the guide needs to know to make the day work.

A booking request is an inquiry a person answers, not a booking and not a purchase: no payment details are collected anywhere on this site, and a guide's own contact address is used internally to route your request — it is never shown on a public page.

The free-text fields are stored as you wrote them. Whatever you type into a brief or a message is what we keep, so please don't put anything in there you wouldn't want held in our records.

A file attached to a project inquiry is stored as you uploaded it, unread by anyone until someone on the RUN BGD team opens it to work on your enquiry. Only a project inquiry offers a file field — none of the other forms does, including the guide application: we would rather ask you for a CV in the conversation that follows than hold one from someone we have not spoken to yet.

Newsletter

The signup stores your email address, which list you chose (general updates or product drops), the page you signed up from, and the time you ticked the consent box. The consent box has to be ticked — the server rejects a signup without it.

Ask RUN BGD

The question box in the bottom corner of every page lets you ask about RUN BGD — where to go, what is on, information about partnerships and so on. The question and your earlier messages in the same conversation are sent to an AI model to answer your question.

Every conversation is stored: the questions you asked and the answers you received, the language you asked in, how many questions there were, the intents the system detected (place, event, tour, and so on), the paths on the site the answers pointed to, and — if an answer handed you to one of our forms — which form that was (contact, tour, rental or project). The conversation is not tied to your name, email or any account; it is used only to improve the answers and to understand what RUN BGD helps people find, never to segment, profile or target you, and it is deleted after ninety days. Don't put personal details into the question box — it is forquestions about the city, and a form or a human is the right place for anything about you.

AI answers can change if the model's thinking changes or the facts on the site are updated — what the box tells you today may not be what it tells you tomorrow. Use the links it gives you to check the source on the site.

What we do not collect

This site runs no advertising trackers and no marketing cookies. The only measurement it uses is Cloudflare Web Analytics, which counts page views without setting a cookie, without a fingerprint and without storing anything that identifies you or follows you to another site — so there is nothing here to consent to and no banner asking you to. It does not ask for your location unless you press "search near me" on the map, and if you do, your coordinates are used in your own browser to sort the list — they are never sent to us or stored.

Submissions are written to Cloudflare D1, a serverless SQL database operated by Cloudflare on RUN BGD's account. Inquiries land in a leads table and newsletter signups in a subscribers table. The website itself runs on Cloudflare Workers, so Cloudflare also processes the ordinary request data any web host sees.

A file attached to a project inquiry is stored separately, in Cloudflare R2 object storage, also operated by Cloudflare on RUN BGD's account. The leads row for that inquiry keeps only a reference to the file, not a copy of it.

When email notification is switched on, a copy of an inquiry is emailed to the RUN BGD team, delivered by Resend. Nothing is sent back to the address you gave us — the page you land on after submitting is the whole confirmation, and any reply you get afterwards is written by a person.

Access is limited to the people who run RUN BGD. We do not sell this data, and we do not pass it to advertisers or data brokers.

Every form on this site is protected by Cloudflare Turnstile. It runs a check in your browser and sends a token to Cloudflare, which we then verify server-side before accepting your submission. That check involves Cloudflare and is governed by Cloudflare's own privacy terms.

Each form also carries a hidden field that a person never sees and never fills in. Submissions that fill it are discarded without being stored. Submissions are also rate limited per network connection.

Inquiry data is held so we can answer you and, if it turns into work, run the project. Newsletter data is held to send you the emails you asked for. That is the whole purpose — we do not repurpose it for anything else.

Every newsletter we send carries an unsubscribe link, and you can ask us to remove you at any time.

Write to hello@runbgd.com and we will tell you what we hold about you, correct it, or delete it. We will not ask you to justify the request. If you attached a file to a project inquiry, the same request removes the file itself, not just the record that you sent it.

We do not currently run an automated deletion schedule: inquiries, and any attached file, stay in storage until someone removes them by hand. Setting a proper retention period is one of the things the review below has to fix.