Cookie policy

What a cookie is

A cookie is a short piece of text that a website places in your browser and reads again on your next visit. This lets a site remember something, for example that you are signed in. For cookies that are technically necessary for operation, the law does not require consent. For everything else it does, and there is no such "everything else" here.

If you only read: a single, technical cookie

Even the first visit sets one cookie, ds_besucher, further down in the table: a random number with no link to your person, which only protects the free questions to the property chat from abuse. Every other cookie only comes into being through an action of yours: changing country or language, signing in.

The cookies that can arise

All six are set only by us and are not passed on to anyone. There are no third-party cookies on this site. The first four arise from operating the service, the last two only because you were asked and answered.

Two of these cookies were named differently until 11 August 2026, namely domoscan-land and domoscan-sprache. If you were here before that, they may still be sitting in your browser. We keep reading them so your setting is not lost, but we no longer write them. They will expire on their own.

What your browser additionally keeps to itself

These are not cookies. They are never sent to our server and do not leave your device:

• scanmyhome-land: the same country selection again, so the page knows it without reloading.
• immolens-job: the state of an analysis currently in progress, so it is not lost after a page reload.
• immolens-grundriss: your drawing in the floor plan editor, so it is there again the next time you open it.
• scanmyhome-intro-seen: remembers, for the duration of the browser tab, that you have already seen the welcome message.
• smh-ansprache-zu: remembers, for the duration of the browser tab, that you have dismissed the note next to the chat button. It does not appear again after that.
• smh-chat-verlauf: keeps your conversation with the assistant for the duration of the browser tab, so it is not lost when you switch to another page. It stays on your device and is deleted when the tab is closed.

The save box, if you have agreed

If you say yes to the save prompt, we create an entry on our server against the random number from smh_merker. It contains: which checks you have started (as an identifier, not an address), a rough location such as "Vienna", the country and language, the role you stated yourself, which calendar days you were here, and whether a purchase resulted.

It does not contain: your name, your email address, the street and house number, your IP address, amounts, your device or your browser. The entry is also capped, not just in the software but in the database itself: at most five properties, at most forty steps, at most thirty days. It is deleted after 180 days without a visit.

What we use it for: so you can find a check you started again, and so we can judge where our site is still unclear. What we do not use it for: advertising, passing it on, prices. Your price depends on what you order, and on nothing else.

Changing your decision

Withdrawing must be as easy as agreeing was. That is why it sits here rather than in a submenu, and it needs neither an account nor a reason.

If you have consented, a button appears here that deletes your decision along with the memory cookie. If it does not appear, for example because JavaScript is off in your browser, two other ways get you just as far: delete this site's cookies in your browser, and your decision is gone at once. Or write to us informally, and we delete the memory cookie on our side. No reason is needed either way.

How we count, and why that needs no cookie

We count how many visitors start a check, get a preview and finally receive a report. For this, a line is written at every step containing no IP address and no email, only a value that cannot be reversed. This value includes the calendar date. That means the same person counts as somebody else for our count on the next day. This is deliberate. It makes the count useless for tracking a person, and is still enough for the question at hand, since a purchase journey takes minutes, not days.

This count does not access anything on your device; it runs exclusively on our own server. That is exactly why it needs no consent: cookie law regulates access to your device, and that does not happen here. If we ever want to add up the count across several days as an exception, we ask you first; that is the second question in the save prompt.

Maps are the exception, and one you trigger yourself

If you open the "Location" tab in a report, your browser fetches the map images directly from map providers. They learn your IP address in the process. Whether they in turn store anything on your device is their own decision; we have no influence over that. The request itself cannot be avoided if a real map is to appear. Which providers these are and what they learn is set out in full in the privacy policy, in the section "Maps and address search". No such request goes out on any other page.

How to get rid of cookies

You do not need anything from us for this: every browser can delete cookies individually or for an entire site, and block them from being stored in the first place. In Chrome, Edge, Firefox and Safari you find this under "Settings" and then "Privacy". Delete the session cookie and you are signed out; delete country and language and both reset to the default; delete the two save cookies and you will be asked again next time. Nothing you have paid for is lost this way: your reports are tied to your account, not to your browser.