01 Purpose
Vertical Real Estate B.V., registered with the Dutch Chamber of Commerce (KvK) under number 99566346, located at Zanddwarsstraat 12, 1011 HP Amsterdam, the Netherlands (“Company”, “we”, “us”, or “our”), trading under the brand name BrickPilot, uses a strictly necessary cookie to remember your cookie choices. With your analytics consent we also use analytics cookies and similar technologies from Google Analytics 4, Mixpanel and, on our landing pages, Hotjar. With your marketing consent we load the LinkedIn Insight Tag, which sets marketing cookies. When you open the demo dialog, Calendly’s scheduling page loads and Calendly sets its own cookies, as described in section 3.5.
A tool described in this policy runs only when we have switched it on for this website, and never before you have given the consent it needs.
This Cookie Policy explains what cookies are, how we use them, and your rights concerning cookie usage. This Cookie Policy should be read together with our Privacy Policy and Terms of Service.
03 Types of cookies we use
3.1 Strictly necessary cookies
We use one strictly necessary cookie, bp_consent, solely to record and honour your cookie choices. It is not used for authentication, tracking, or personalisation. Because it is necessary to remember whether you accepted or rejected optional cookies, it cannot be disabled through the cookie banner. You can delete or block it in your browser, but the banner may then appear again because your choice cannot be remembered.
Legal basis: Legitimate interest (Article 6(1)(f) GDPR) and the strictly-necessary exemption (Article 11.7a(3) of the Dutch Telecommunications Act (Telecommunicatiewet)).
3.2 Functional or preference cookies
We do not currently set functional or preference cookies. The bp_consent cookie is classified as strictly necessary because its only purpose is to retain your cookie choices.
3.3 Analytics cookies
Analytics cookies are off by default. Only after you give analytics consent do we load:
- Google Analytics 4 (Google Ireland Limited), through the Google tag, for aggregated statistics on page views and on two actions: booking a demo and requesting a report. It sets the first-party
_gaand_ga_*cookies. - Google Tag Manager (Google Ireland Limited), which we use to manage measurement tags. According to Google, Tag Manager itself does not collect personal data about visitors.
- Mixpanel (Mixpanel, Inc., United States), to measure page views, how far you scroll, and steps such as clicking a demo or report button, starting a check and requesting a report. We send this data to Mixpanel’s EU servers, and we configure Mixpanel not to use your IP address for location, not to collect clicks automatically, and not to record sessions. It sets the first-party cookie
mp_<project>_mixpaneland can keep a queue of unsent events in local storage. - Hotjar (Hotjar Ltd), on our landing pages only, to understand how visitors use those pages, for example where they click and how far they scroll. It sets first-party cookies whose names start with
_hjand uses local and session storage.
With analytics consent we also keep the campaign of your visit (the target group and the UTM parameters of the link you arrived through) in your browser’s session storage as bp_ctx, so that our measurements and forms can attribute your visit to that campaign.
Our landing pages link to the vergunningvrij check on app.brickpilot.ai/vergunningvrij. This policy also applies there: with the same analytics consent, that check uses Mixpanel as described above (including the mp_<project>_mixpanel cookie), keeps the campaign of your visit in session storage as bp_ctx and, when you place an order, keeps which order is on its way in session storage as bp_order_pending, so that the purchase is counted once.
Google Consent Mode v2 is implemented in basic mode: no Google tags load at all before analytics consent. Your choices are passed to Google as consent signals: analytics consent for analytics_storage, marketing consent for ad_storage, ad_user_data and ad_personalization.
Legal basis: Consent (Article 6(1)(a) GDPR).
3.4 Marketing or advertising cookies
Marketing cookies are off by default. Only after you give marketing consent do we load the LinkedIn Insight Tag of LinkedIn Ireland Unlimited Company. We use it to measure the reach and results of our LinkedIn advertising and, where we set this up in LinkedIn, to show our advertisements on LinkedIn to people who visited this website. The tag sets the first-party cookies li_fat_id and li_giant on brickpilot.ai, and LinkedIn can set or read cookies on linkedin.com, as listed in section 4. According to LinkedIn, the tag collects the page URL, the referring page, your IP address, device and browser characteristics and a timestamp. See LinkedIn’s Cookie Table and Privacy Policy.
Your marketing choice also counts for Calendly’s scheduling page in the demo dialog (section 3.5).
Legal basis: Consent (Article 6(1)(a) GDPR).
3.5 Calendly scheduling page (third party)
To let you book a demo, the demo dialog shows the scheduling page of Calendly, LLC (United States) in a frame. It loads only when you open the demo dialog, never on page load. Inside that frame Calendly sets the cookies it needs to show the scheduling page and process a booking, and it can set optional cookies. In its own cookie banner Calendly says it uses cookies and similar technologies “to improve and personalize your experience, to understand website interactions (including clicks, cursor movement and screen recordings), and for marketing”. Calendly decides which cookies it sets, and does not list them by name; see Calendly’s Privacy Notice.
How your choice applies: if you accepted both analytics and marketing cookies in our banner, we treat that as your consent to Calendly’s optional cookies for the purposes above and hide Calendly’s own cookie banner in the frame. If you rejected optional cookies, accepted only one of the two categories, or have not made a choice yet (a choice made in an earlier version of our cookie banner counts as no choice, and we ask you again), Calendly shows its own cookie banner in the frame and asks for your consent itself.
Legal basis: Consent (Article 6(1)(a) GDPR) for Calendly’s optional cookies, given in our banner or in Calendly’s own banner. The cookies Calendly needs to show the scheduling page and process a booking fall under the strictly-necessary exemption (Article 11.7a(3) of the Dutch Telecommunications Act (Telecommunicatiewet)).
3.6 Links that open another service
The WhatsApp button in the demo dialog is a plain link to WhatsApp. It loads nothing from WhatsApp on our website and sets no cookies here; only when you click it do you go to WhatsApp, which then processes your data under its own privacy policy.
Our error reporting (Sentry) sets no cookies and stores nothing on your device; see our Privacy Policy.
05 How we use cookies
We use cookies and similar technologies to:
- remember and honour your cookie choices through
bp_consent; - with your analytics consent, measure how the website is used through Google Analytics 4, Mixpanel and, on our landing pages, Hotjar, and attribute visits to our campaigns;
- with your marketing consent, measure and target our LinkedIn advertising through the LinkedIn Insight Tag; and
- when you open the demo dialog, show Calendly’s scheduling page so you can book a demo (section 3.5).
Optional cookies are blocked unless and until the relevant consent is given. Under Consent Mode v2 basic, Google tags do not load before analytics consent. The website remains fully functional if you reject all optional cookies.
06 Managing your cookie preferences
6.1 Cookie consent banner
On your first visit, our first-party cookie banner presents three equally weighted choices:
- Accept all;
- Reject all; or
- Manage preferences.
The second layer opened through Manage preferences lets you toggle each optional category separately. Strictly necessary cookies remain enabled. Analytics and marketing are off by default, and rejecting them does not limit website functionality.
A permanent Cookie settings link appears in the footer of every page. It reopens your preferences so you can change or withdraw consent at any time. Withdrawing consent requires the same number of clicks as granting it and takes effect for future use.
When you withdraw consent for a category, we delete that category’s first-party cookies from brickpilot.ai (_ga, _ga_* and the cookies starting with mp_ and _hj for analytics; li_fat_id and li_giant for marketing), remove the analytics providers’ storage items starting with __mpq_, mp_ or _hj, and reload the page if one of those tools was running. Cookies on other domains, such as linkedin.com and calendly.com, cannot be deleted by us; you can delete them in your browser.
Your choice also decides whether Calendly asks for consent itself in the demo dialog (section 3.5). If you withdraw analytics or marketing consent, Calendly shows its own cookie banner again the next time you open the demo dialog; if the dialog is open at that moment, the scheduling page reloads right away with Calendly’s banner. Cookies Calendly has already stored can be managed through Calendly’s own cookie settings or deleted in your browser.
6.2 Browser settings
You can also manage cookies through your browser settings. Most browsers allow you to block or delete cookies and set preferences for first-party and third-party cookies. If you block or delete bp_consent, we may be unable to remember your choice and the consent banner may reappear. Rejecting all optional cookies through our banner does not impair the website.
For instructions on managing cookies in common browsers:
- Google Chrome: Settings → Privacy and Security → Cookies
- Mozilla Firefox: Settings → Privacy & Security → Cookies
- Safari: Preferences → Privacy → Cookies
- Microsoft Edge: Settings → Cookies and Site Permissions
07 Data collected through cookies
The bp_consent cookie contains a JSON value recording:
- your choice for each cookie category;
- the applicable policy text version; and
- the timestamp of your choice.
With your analytics consent, Google Analytics 4 processes cookie identifiers, device and browser information, page interactions, and referral information to produce aggregated usage statistics. Mixpanel receives the page views and steps described in section 3.3, each with the page, the campaign of your visit and a random visitor ID. Hotjar receives how you interact with our landing pages, such as clicks and scrolling, together with device and browser information.
With your marketing consent, LinkedIn receives the data described in section 3.4 and can link it to your LinkedIn account if you have one. According to LinkedIn, it removes members’ direct identifiers within seven days and deletes the remaining pseudonymised data within 180 days.
When the demo dialog loads Calendly’s scheduling page, Calendly receives technical data such as your IP address, browser and device information, and time zone. With consent to its optional cookies (section 3.5), Calendly can also use cookies and similar technologies to understand how you interact with the page, including clicks, cursor movement and screen recordings, to personalise your experience, and for marketing. If you book a demo, Calendly processes the details you enter (name, email address, and any answers to the booking questions) and the time you choose. See our Privacy Policy and Calendly’s Privacy Notice.
Separately, we log consent choices—including rejections and withdrawals—server-side as evidence of consent under Article 7(1) GDPR. Each record contains a timestamp, the choice for each category, the policy text version, a hashed IP address, and a truncated user agent. These records are used only as evidence of consent and never for another purpose. For more information on how we process personal data, please refer to our Privacy Policy.
08 Retention of cookies
bp_consent: retained for 6 months, unless you delete it sooner.bp_ctx: removed when you close the browser tab, or when you withdraw analytics consent.- Analytics and marketing cookies: retained for the durations in section 4, unless you withdraw consent or delete them sooner.
- LinkedIn’s and Calendly’s cookies on their own domains: retained for the periods LinkedIn and Calendly set, unless you delete them sooner.
- Data the providers receive: how long Google, Mixpanel, Hotjar, LinkedIn and Calendly keep the data they receive through these cookies is determined by the provider and, where the provider offers a choice, by the settings of our account with that provider. This policy sets no separate period; see the providers’ documentation linked in this policy.
- Server-side consent records: kept no longer than necessary to demonstrate compliance with our consent obligations, then deleted.
09 Children’s privacy
Our website is not intended for children under 18. We do not knowingly use cookies to collect data from children.
10 Updates to this cookie policy
We may update this Cookie Policy periodically to reflect changes in technology, law, or our business practices. We will notify you of material changes by updating the version date at the top of this policy. We encourage you to review this policy regularly.
11 Contact us
If you have questions about this Cookie Policy or wish to exercise your rights regarding cookies, please contact us at:
Vertical Real Estate B.V. (trading as BrickPilot)
Zanddwarsstraat 12, 1011 HP Amsterdam
The Netherlands
KvK: 99566346
Email: [email protected]
12 Version history
| Version | Date | Description | Created by | Approved by | Published by |
|---|---|---|---|---|---|
| 1.0 | 3 March 2026 | Initial release | Laurens van Duin | Manouk Termaaten | Laurens van Duin |
| 1.1 | April 2026 | Added specific cookie names, removed advertising cookies, added contact details, aligned with Privacy Policy | Laurens van Duin | Manouk Termaaten | Laurens van Duin |
| 1.2 | 2026-07-31 | Rewritten to describe the implemented consent mechanism (bp_consent, Consent Mode v2 basic, consent logging) | — | — | — |
| 1.3 | 2026-10-09 | Added Calendly’s scheduling page in the demo dialog and how the banner choice applies to its cookies | — | — | — |
| 1.4 | 2026-10-11 | Added Google Analytics 4 through the Google tag, Mixpanel, Hotjar and the LinkedIn Insight Tag with their cookies; marketing cookies are now set with marketing consent; also covers the vergunningvrij check on app.brickpilot.ai | — | — | — |