Cookie Policy

On this website

We store your theme preference, whether you dismissed the announcement bar, and your cookie choice itself. These are required for the site to behave as you asked and carry no personal data.

If — and only if — you choose "Accept all", we load Google Analytics 4, run by Google LLC, to understand which pages help and which confuse. It is optional. Until you accept, no Google script is loaded, no Google cookie is set, and your browser makes no request to Google at all — unless you load one of the forms described below. Declining changes nothing about how the site works.

Google Analytics sets its own first-party cookies in your browser: _ga, which holds a random identifier for the browser and lasts about two years, and a _ga_ cookie holding session state for about the same period. A short-lived _gid cookie may also appear. Decline, and none of them exists.

What we send Google is the address of the page you are on, the page title, and what your browser tells any website it visits — including your IP address, from which Google derives an approximate location. We do not send your name, your email address, or anything you typed. We do not use Google Analytics for advertising: ad storage, ad personalisation and Google Signals are switched off in the code that loads it, so the data is not used to build an advertising audience.

Google processes this on infrastructure that includes servers in the United States, so accepting means this information leaves Singapore, where the rest of BildrX runs. The Privacy Policy says the same and marks the legal question it raises.

Two more services load only when you ask for them, or once you have chosen "Accept all". Featurebase runs the support chat, which loads when you press Support in the corner of the page, and the changelog, which loads when you press "Load the changelog" on the changelog page. Each form, hosted by Tally, loads when you press "Load the form". Until then your browser makes no request to Featurebase, Tally or Google for them, and none of them stores anything in your browser. Choosing "Essential only", or sending a Do Not Track or Global Privacy Control signal, leaves all of them available: each one simply waits until you open it.

Once the support chat has loaded, Featurebase keeps a note in your browser's local storage of which BildrX workspace it belongs to, keeps the chat connected while the page is open, and may set its own cookies to recognise the conversation on a later visit. Once a form has loaded, Tally and Google reCAPTCHA — which Tally uses to keep out spam — may set their own cookies, and the form fetches its typefaces from Google Fonts. "Open the form in a new tab" takes you to the same form on tally.so instead.

Until the changelog is loaded, its page shows a short note and a plain link to the changelog on Featurebase; opening the page on its own makes no request to Featurebase. Once loaded, the changelog is Featurebase's own page shown in a frame on ours: it may keep a note in your browser's storage or set its own cookies, as it would if you visited bildrx.featurebase.app directly. It does not load the support chat, and it receives nothing about you from BildrX. The link, and the Support Portal link at the foot of every page, take you to Featurebase's site instead. The old guides library address, /guides, now forwards you to the help centre on help.bildrx.com, which Featurebase runs.

In the product

Signing in sets a session cookie. It is required — without it you cannot stay logged in — and it is not used for anything else.

app.bildrx.com asks the same cookie question this site does, with the same two answers, and it asks separately: your browser keeps the two answers apart because they are different addresses, and joining them up would mean setting a cookie across both — which is the sort of thing you are being asked about. Accept there and the same Google Analytics described above loads there too; the address it is told about has record identifiers and share links stripped out of it first, so a page like the cap table is reported as a cap table and not as your cap table.

The product also measures itself without any third party: a small number of events — a page opened, a module used, a deck uploaded — are written to BildrX's own database in Singapore. No script, no cookie, and nothing sent to anyone else. That is not optional, because it is how the product is kept working, and it is described in the Privacy Policy.

When you open a shared deck or data room

Opening a BildrX share link sets a cookie called deck_viewer_token that lasts one year. It lets the founder who shared the link see whether a returning visit is the same person rather than a new viewer. The Privacy Policy describes the whole of what a shared-link visit records, including the viewer's IP address.

Changing your mind

Clear this site's browser storage and the consent banner will ask again on your next visit. In the product, Settings then Security has an Analytics cookies control that changes the answer or clears it outright, at any time and without asking us. Turning analytics off there reloads the page, because a script a browser has already loaded cannot be taken back out of it.

If your browser sends Do Not Track or Global Privacy Control, we treat that as "Essential only" on both the site and the product. You are not asked again, and nothing optional loads. You do not have to do anything else.

Clearing cookies in the browser you used to open a share link removes the viewer token too.