Cookie Policy

bildflow sets the cookies it needs to keep you signed in and to remember your cookie choice. Analytics cookies, from Google Analytics through Google Tag Manager, are set only if you accept them in the cookie banner. There is no advertising, remarketing or cross-site tracking anywhere in the product.

The banner offers two choices: Accept, which allows analytics cookies, and Essential only, which keeps just the strictly necessary ones. Until you choose, no analytics cookie is set. You can change your mind at any time from Cookie settings at the foot of every page.

It covers every page served from the bildflow application: the marketing pages, the sign-in and sign-up pages, the workspace your staff use, the buyer portal, the agent kit and these legal pages. The same cookies apply to all of them.

It does not cover a third party's own website. If you follow a link out of bildflow — to a payment page, a map provider, your own site — that site's cookie policy applies once you are there.

Cookies that carry personal data are also covered by our Privacy Policy, which explains the legal bases and your rights.

Authentication session cookies, named with an sb- prefix, are set by our authentication provider when you sign in. They hold the tokens that prove who you are to the server on each request. Without them you would be asked to sign in again on every page.

They are set on our own domain and marked HttpOnly, so no script running in the page — ours or an injected one — can read them. They are SameSite=Lax, which means a browser sends them with normal navigation to bildflow but not with cross-site subrequests from another website. In production they are marked Secure and are sent only over HTTPS.

A signed-in session is long-lived rather than per-visit: the cookie is written with a long expiry and is refreshed each time you use the product, so you are not asked to sign in every day. Signing out clears it immediately, as does clearing the site data in your browser.

The consent cookie, bf_consent, remembers whether you chose Accept or Essential only, so the banner does not ask again on every page. It holds nothing but that word, is SameSite=Lax, and expires after 12 months, when you are asked again.

Strictly necessary cookies do not need your consent under the ePrivacy rules and the Cypriot regulations implementing them, so they are set whichever option you choose.

We use Google Tag Manager to load Google Analytics, which tells us which pages are visited and how people move through sign-up, bookings, enquiries and downloads, so we can improve the product. Google Tag Manager itself sets no cookie.

We use Google's Consent Mode. Every page starts with all consent signals set to denied. If you choose Accept, analytics storage is granted and Google Analytics sets its first-party cookies, named with a _ga prefix, which keep a pseudonymous identifier for up to 2 years. If you choose Essential only, or never choose, no analytics cookie is set and Google Analytics does not run at all: every Google Analytics tag in our container requires your consent, so we do not send even the cookieless signals Consent Mode can send without it. Google Tag Manager itself still loads, which reveals your IP address to Google as fetching any file does.

The advertising signals — ad storage, ad user data and ad personalisation — always stay denied. We run no advertising or remarketing tags.

The events we record describe what happened, never who did it: for example that a lead form or a booking was submitted, that a plan checkout started, or that a document was downloaded, with the workspace's public name slug where useful. They never contain names, email addresses, phone numbers or the ids of people. Page addresses are recorded without personal identifiers: ids in the address and query values such as a buyer, unit or link token are replaced with placeholders before anything is sent.

Choosing Essential only after having accepted stops any further analytics and removes the _ga cookies we can reach from your browser.

Your light or dark theme preference is stored in localStorage on your own device. It never leaves your browser and is not sent to our servers.

Some pages keep short-lived state such as a draft you have not sent yet in the same place, so a reload does not lose your typing.

No advertising or remarketing pixels, no session-recording scripts, no social media trackers, no cross-site identifiers, and no cookies that build a profile of you for advertising.

Beyond the analytics you accept, we measure how the product is doing from our own server logs and aggregated counters, which do not follow you around the internet.

Our pages load Google Tag Manager from Google's servers, as described above, so Google receives your IP address when they do, as any server you fetch a file from does. Google processes analytics data for us under its data processing terms.

Payments happen on Stripe's own checkout and billing pages: we send you there, and your browser is on Stripe's domain while you are paying. Stripe sets its own cookies there, under its own notice, and those cookies are strictly necessary to take the payment and to prevent fraud. They are not set on bildflow pages and we cannot read them.

Project maps load map tiles from a content delivery network. Loading a tile reveals your IP address to that network, as loading any image from any server does, but no cookie is set for it.

The enquiry and booking forms that developers embed on their own websites never show the cookie banner, do not load Google Tag Manager and never set analytics cookies.

Use Cookie settings at the foot of any page to reopen the banner and choose again. Withdrawing consent is as easy as giving it and takes effect immediately.

Every browser also lets you view, delete and block cookies for a single site from its settings, usually under Privacy or Site settings. Clearing the site data for bildflow removes the session cookies, the consent cookie, any analytics cookies and the theme preference together; the banner then asks again.

Blocking our session cookies is allowed, but you will not be able to sign in: the product has no way to keep you authenticated without them.

If we add a cookie or a tool that is not described here, we will update this page first and, where consent is needed, ask for it before the cookie is set.

Questions go to bildflow@ruler.agency.