Privacy

What the site and the city store about you, why, for how long, and how to remove it.

Who is responsible

Bruges 1562 is made in Bruges, Belgium, by the team of Bruges 1562, who decide what is stored and why (the controller). Contact: hello@bruges1562.com.

The forms on this site

If you ask for a place on the waiting list, we keep your name, e-mail address, language and the note you wrote, only to send you a confirmation and your access code. The entry is deleted when you ask us to (hello@bruges1562.com) or when you delete the account you made with it.

Feedback sent from the site is filed without your name or address. If you gave them, they stay in our own database, only so we can answer you.

The access code and walking as a guest

For now the city opens with an access code. The code you came in with is remembered in your browser and kept with your guest id or your account, because it decides how long you may play.

A guest has no account. The city sets one cookie with a random id, so the server can count your play time and the steps listed under Counting. Your progress stays in your own browser; while you play, the server keeps a copy of it, the place you last stood and your browser's name and version (its user agent), so we can see how guests get on.

With an account

An account stores your e-mail address, your name in the city, the access code you came in with, when you signed up and were last seen, whether you asked for news, and your progress: where you stand in the city, your quests and your deeds. For each sign-in the server keeps a session with its dates and the type of your browser.

When you finish a horse race while signed in, your name in the city and your best time on that course, this week's and your best ever, appear on the race boards, which every player can see. Guests are never on them, and your times go when you delete your account.

Your e-mail address is used to send you sign-in links (there is no password), and to answer feedback you sent. It is not shared for advertising and not sold.

News, only if you ask

If you tick "Tell me when there's more", your address is also used for a short mail when a new part of the city opens, and for nothing else. The box is unticked unless you tick it, and you can change it at any time in the Account tab of the menu.

Play time

While you are in the city, it tells the server every half minute that you are there and where you stand, so your play time is counted and, with an account, your place and progress are saved. The server keeps the seconds played per week, not a record of where you walked. Nothing is counted while the tab is hidden or you have been away from the keyboard for three minutes.

Support payments

Payments are not open yet. Once they are, you pay on a page of Stripe, our payment provider. Your card or bank details go to Stripe only: they never pass through or reach our server. We hand Stripe the amount, the id of your account and your e-mail address (for Stripe's receipt), and the language of the page. Stripe processes the payment under its own privacy policy.

We will keep the payment's reference at Stripe, its amount and its state (paid, refunded or disputed) with your account, so the unlock stays yours.

Counting and error reports

The city counts, in its own database, which of five steps a guest or an account has reached, each once: the welcome page, entering the city, five minutes of play, the end of the play time, and Support.

When the city has loaded, it reports how much it downloaded and how much came from your browser's cache, without your name, account or any identifier, so we can see what serving the city costs.

When the city hits an error in your browser, it reports the error message, where in the code it happened, its version and the type of your browser, so it can be fixed. The report is not tied to your account.

The server also keeps an activity log of what happens to an account (created, signed in, renamed, supported, deleted and the like).

The city's page loads Vercel Web Analytics and Vercel Speed Insights, which count visits and measure loading times without cookies; Vercel describes them as not identifying visitors. The pages of this site load Vercel Web Analytics alone, to count page views, also without cookies. The site itself counts a visit once per browser session, with no cookie and nothing about who you are.

Feedback from inside the city

Feedback you send from the city (F) is filed in the project's issue tracker on GitHub with your name in the city, your note, the spot you stood on, your settings, the version, your screen size and the type of your browser. An answer may be mailed to your account's address.

Cookies and storage in your browser

Only what the city needs to work; nothing for advertising or for following you across sites, which is why there is no cookie banner. The pages of this site set no cookies.

Where it is kept, and who helps

Accounts, progress and what the forms collect are kept in a database at Supabase. The site, the city and their server run on Vercel, which also keeps the nightly backups. Sign-in mails are sent through Resend, payments will go through Stripe, feedback from the city is kept at GitHub. As with any website, the host sees your IP address while it serves you; we keep no IP addresses of visitors ourselves. Some of these companies are based in the United States and may process data there.

How long

Deleting your account, and your rights

You can delete your account at any time: Esc in the city, the Account tab, Delete my account. That removes your e-mail address, your name, your sign-in, your sessions, your progress, your play time, your counting steps and what unlocked your account, at once. What stays: the record of a payment (amount, state and Stripe's reference, no longer tied to an account), a line in the activity log saying the account was deleted, with its name and address, for 90 days, feedback you sent, and the backups of the last 30 days.

Guests remove what is in their browser by clearing cookies and site data.

To see what is stored about you, to have it corrected or removed, or to object, write to hello@bruges1562.com. You can also complain to the Belgian Data Protection Authority (gegevensbeschermingsautoriteit.be).

Last changed 11 November 2026.