Legal
Cookie policy
Last updated: 2 August 2026
1. About this policy
This policy explains how dc01sk.com, operated by VG RE GmbH, uses cookies and similar technologies. It should be read together with our privacy policy.
2. What cookies are
Cookies are small text files placed on your device when you visit a website. They let a site remember your actions and preferences, and they can be used to measure how a site is used. Content embedded from another company, such as a map, can also set cookies of its own and can see your IP address once it loads.
3. Our approach: consent first
Nothing optional runs on this site before you agree to it. Consent is managed by Cookiebot: on your first visit a banner asks whether you accept non-essential cookies, and until you accept, anything non-essential stays blocked. The Cookiebot script itself loads on every page, because it is the thing that has to ask you, and the only thing it stores is your answer. You can change or withdraw that answer at any time using "Cookie settings" in the site footer.
We do not rely on that blocking on its own. Before any Google tag exists, the page has already declared to Google that every kind of storage and every advertising signal is denied, so that a Google tag which somehow ran early would still have nothing to store and nothing to send. Your answer in the banner is what lifts that, category by category, except for the advertising signals: those stay denied whatever you accept, because nothing here uses them.
Two optional categories are used here. Statistics covers the two tools that measure how the site is used, Google Analytics and Microsoft Clarity. Marketing covers Apollo, which works out which organisation a visit appears to come from, and the Google Maps embed, which loads by itself once marketing cookies are accepted. There is no advertising on this site and no retargeting pixel, so nothing here follows you to other websites.
4. What we know is set
The list is short, because the site is deliberately light: a consent banner, three measurement tools and a map. Our own code sets no cookies at all. There is no login, no session to remember, and the enquiry form works without one. Apart from the strictly necessary cookies in the first table, nothing listed here is set until you have accepted the matching category in the banner. This section is not a complete inventory: it records what we can confirm ourselves, and where we are not certain of a name we say so instead of guessing. The automated scan described in section 5 is the complete, dated list.
Strictly necessary
One cookie is needed so the consent banner can remember your choice. It cannot be switched off, because without it you would be asked again on every page.
| Set by | Cookie | Purpose | Typical duration |
|---|---|---|---|
| Cookiebot | CookieConsent | Records whether you accepted or refused non-essential cookies | Up to 12 months |
Cloudflare, which hosts the site and screens automated traffic for us, may set strictly necessary cookies of its own as part of doing that. A short-lived bot-management cookie named __cf_bm is the usual one. These come from the platform rather than from our code, so we cannot list them from the codebase. The scan described in section 5 names whatever is actually set, with its duration.
Statistics: how the site is used
These load only after you accept statistics cookies, and stop if you withdraw that. Two tools sit in this category. Google Analytics 4 counts page views and visits and shows us how people arrive, roughly which country they are in and what device they use. Its cookies exist to recognise the same browser across a series of page views, so that one person reading five pages is not counted as five visitors. Microsoft Clarity records the session: pointer movement, scrolling, clicks and taps, replayed to us as a recording and aggregated into heatmaps. Clarity is set to Balanced masking, which masks the text you type and the images on the page, so what you enter in the enquiry form is not readable in the recording. Both are described in more detail in the privacy policy.
| Set by | Cookie | Purpose | Typical duration |
|---|---|---|---|
| Google Analytics | _ga | Distinguishes one browser from another so repeat page views can be counted as one visitor | Up to 2 years (Google's default) |
| Google Analytics | _ga_SC5B14KE48 | Holds the state of your current visit for the Analytics property used on this site | Up to 2 years (Google's default) |
| Microsoft Clarity | _clck | Keeps a Clarity identifier for this browser, so repeat visits are recognised | Up to 1 year |
| Microsoft Clarity | _clsk | Joins the page views of a single session into one recording | 1 day |
Clarity is loaded from Microsoft's own domain, and Microsoft may set further cookies of its own there while it does so, which are not set by us and which we cannot list from our code. How long a cookie lives is also a separate question from how long the data behind it is kept: Google Analytics data is deleted after 14 months, whatever the cookie duration above says. The scan in section 5 names every cookie actually found, with its own durations.
Marketing: which organisation is visiting
This loads only after you accept marketing cookies. Apollo looks up the network your visit comes from, principally the IP address, against its database of company networks, and tells us which organisation appears to be reading the site and which pages it viewed. It is set to company level only. Person-level identification, which the tool also offers, is deliberately not enabled, so it is not used to work out who you are as an individual. It keeps an identifier of its own on your device so that repeat visits from the same browser are read as one visit rather than several.
| Set by | Cookie or storage | Purpose | Typical duration |
|---|---|---|---|
| Apollo | Local storage, not a cookie: apolloAnonId, plus two keys prefixed with our
Apollo account identifier | Recognises repeat visits from the same browser, and holds pages not yet sent, so views can be grouped into one visit by one organisation | Until you clear your browser storage for this site |
We tested this ourselves rather than guessing at a cookie name: Apollo sets no cookie here. It keeps its identifier in your browser's local storage, which the banner governs in the same way but which your browser clears through "site data" rather than through its cookie list. If the scan in section 5 reports an Apollo cookie as well, the scan is right and we correct this table.
The map embed
Two pages, the home page and For buyers, can show the site location on a Google Maps embed. The map is not loaded when the page opens. It loads only if you press "Load map", or if you have already accepted marketing cookies through the banner. Until one of those happens, no connection is made to Google from these pages and no Google cookie is set.
When the map does load, your browser connects to Google, which receives your IP address and browser information and may set cookies of its own. Those cookies are Google's, not ours, and are governed by Google's own terms. If you would rather not load the map, you do not have to: the coordinates are printed on the page, and the page works normally without it.
| Set by | Cookie | Purpose | Typical duration |
|---|---|---|---|
| Google's own cookies, set only if you load the map | Delivering and securing the Google Maps embed, and Google's own purposes | Set and controlled by Google |
What is not here
We run no advertising cookie, no retargeting pixel, no social-network tracking button and no tag manager. Nothing on this site is used to follow you across other websites or to build an advertising profile of you. If that changes, this policy is updated before the tool ships, not after, and the tool will not run until you have accepted it through the banner.
5. The full declaration
Cookiebot scans dc01sk.com and produces a complete, dated declaration naming every cookie it finds, including anything set by our hosting and security provider, and including the names we have left open in section 4. That scan can only run once the site is publicly reachable, so the declaration is the authority on the cookie list and section 4 is what we can confirm ourselves in the meantime. Where the two ever disagree, the scan is right and we correct section 4.
The declaration below is generated by Cookiebot from that scan and updates itself when the scan is repeated. It carries its own date, which is the one to rely on for the cookie list; the date at the top of this page applies to the rest of the policy. It stays empty until the first scan of the live site has run.
6. Managing your consent
You can change or withdraw your choice at any time by reopening the cookie settings from the banner or from the link in the site footer. Withdrawing consent stops the tools in that category and stops new cookies being set: Google's tags go back to a denied state immediately, Clarity is told to stop recording, and from your next page load nothing in that category is loaded at all. Cookies already on your device stay until they expire or until you delete them, which you can do at any time through your browser settings. If your browser sends a Global Privacy Control or Do Not Track signal, none of the three measurement tools loads in the first place, whatever is later accepted in the banner. The site location map is the one thing that signal does not govern, because it loads only where you have asked for it: by pressing "Load map", or by accepting marketing cookies. Refusing does not limit what you can read or do here. Every page works the same way either way, and the only visible difference is that the map will not load until you ask it to.
7. Changes to this policy
We may update this policy as the tools we use change. The date at the top shows when it was last revised.
8. Contact
For any question about cookies, email info@dc01sk.com.