Hausfuchs Beta — Privacy Policy

Last updated: 30 October 2026 · Version 2026-10-30-r1

This document is available in English only during the beta period. The English version is authoritative.

This Privacy Policy explains what personal data we collect when you take part in the Hausfuchs beta program at beta.hausfuchs.com (the "Beta Service"), why we collect it, how long we keep it, and what rights you have. It forms part of the Hausfuchs Beta Program Terms and Conditions (business · personal).

Please read Section 3 carefully. The Beta Service is instrumented more extensively than a commercially released product would be, including session recording. Observing how participants use the service is one of the main reasons the beta exists.

1. Who is responsible for your data

The controller of your personal data is:

Hausfuchs Oy
Business ID 3643057-1
Helsinki, Finland
<privacy@hausfuchs.com>

We have not appointed a Data Protection Officer; we are not required to. Contact <privacy@hausfuchs.com> for any question about this policy or to exercise your rights.

2. Data you give us directly

Providing your email address and accepting the terms is necessary to take part. If you do not provide them, we cannot give you an account.

3. Data we collect automatically as you use the Beta Service

3.1 What we collect

Product and event analytics. Pages and views you open, buttons and controls you click, features and tools you use, searches and queries you run including the content of those queries (chat messages are not part of this), map and layer interactions, areas and properties you view, reports and results you generate, and the timing, sequence, frequency and duration of these actions. Interface interactions are captured automatically rather than being individually pre-defined, so this includes clicks we have not specifically anticipated.

Session recordings (session replay). Reconstructions of your session that let us replay how you moved through the interface — page content rendered to you, cursor movement, scrolling, clicks and the timing of input. Session recording runs only if you consent to it — and we ask for that consent when you register, so it is on by default from the moment you join. Session recording masks what you type into password, email, telephone, search and chat boxes, and leaves the chat panel out of recordings entirely, so chat messages and answers never reach our analytics provider. Appendix A of the Terms lists exactly what is masked and what is not.

Feature flags and experiments. Which variants, features or staged rollouts were enabled for you, so we can compare behaviour between groups. Different participants see different things at the same time.

Heatmaps. Aggregated views of where participants click, scroll and dwell.

Error, diagnostic and performance data. Errors, stack traces, console output, latency, and the state of the application when something fails.

Technical and device data. IP address, approximate location derived from it, browser type and version, operating system, device type, screen dimensions, language settings, referring URL, and identifiers stored in cookies or your browser's local storage.

Account identifiers. Your user ID, email address and organisation, which we link to everything above. This means your usage is not anonymous to us — it is tied to an identified participant profile.

3.2 Why we collect it

To operate, secure, debug and stabilise the Beta Service; to reproduce and diagnose problems you report; to measure feature adoption, drop-off and usability; to understand how the service performs in real use; to decide what to build, change or remove; to run experiments; to contact you about your usage or to ask for feedback; and to produce internal and aggregated statistics.

3.3 Legal basis

Legitimate interests (Art. 6(1)(f)) for analytics necessary to provide, secure and improve a service you voluntarily joined in order to evaluate it. Our interest is in developing a working product; we consider this proportionate because the beta exists for exactly that purpose, we tell you plainly that observation is central to it, and we mask the most sensitive inputs. You may object at any time — see Section 8.

Consent (Art. 6(1)(a)) for session recording, and for cookies and similar technologies that are not strictly necessary for a service you have expressly requested. We ask for it as a separate, explicit step when you register — it is not bundled into your acceptance of the Terms, and it is never pre-ticked. Once given, session recording is switched on for your account and stays on, because observing real use is what the beta is for. You may withdraw at any time at /privacy-settings or by emailing <privacy@hausfuchs.com>. Withdrawing takes effect immediately and does not affect processing already carried out; because observation is the purpose of the beta, it also ends your participation, and we tell you so before you confirm.

Storing or reading information on your device is separately governed by section 205 of the Finnish Act on Electronic Communications Services (917/2014), which is why we ask for consent rather than relying only on legitimate interests.

3.4 What you cannot switch off

Session recording, basic event analytics and error logging are all necessary to run the beta — observing how the service is used is the reason it exists. They cannot be switched off while you take part. If you would prefer not to be recorded, please do not join the beta: declining costs you nothing, no other Hausfuchs service depends on it, and you are not being deprived of anything you would otherwise have. Withdrawing consent later stops recording immediately and ends your participation.

3.5 Please do not type sensitive information into free-text fields

Because event data and session recordings may capture on-screen content and query text, please do not enter special category personal data (health, religion, political opinion, sexual orientation, biometric or genetic data), personal data about other people that you are not entitled to share, or anything you or someone else would not want recorded. This is a precaution in addition to — not instead of — our own duty to protect your data by design and by default.

3.6 Chat

When you use the chat, we send your messages to our AI service (Amazon Web Services Bedrock, EU data centres) to produce an answer. The chat window tells you that you are talking to an AI. Before a message is stored or reaches the AI service, we remove identity numbers, bank and card details, passport numbers, email addresses and phone numbers from it. Addresses you give for travel-time questions are stored only as a rough area. We store your messages, the answers and the technical steps taken to answer, linked to your account, to run and check the service, and delete the message text automatically after 90 days. A usage record without any message text (time, amount of use and cost) is kept for 12 months to manage costs and prevent abuse. You can download or delete your chats at any time in your profile; deleting removes the message text straight away and keeps only the usage record. When your account is closed, all of it is deleted. We do not look up or profile other people, and we do not use what you write in the chat for analytics or advertising. Our logs record the length of chat messages, not their content. If you mention health, religion or similar personal needs, we use them only to answer you.

4. Cookies and local storage

We use cookies and browser local storage for two purposes:

• Strictly necessary — keeping you signed in, security, and remembering your cookie choice. These do not require consent.
• Analytics and session recording — identifying your browser across visits so usage can be linked into a session. These run only with your consent.

Manage or withdraw your choice at any time at /privacy-settings.

5. Who else processes your data

We do not sell your personal data and we do not share it for anyone else's marketing. We use the following processors:

Each is bound by a data processing agreement under Art. 28 GDPR. The current list is maintained at /subprocessors, and we update it before adding or replacing a sub-processor.

We may also disclose personal data where we are required to by law, a court or a competent authority, and to our professional advisers where necessary.

6. Transfers outside the EEA

Our infrastructure is located in the EEA. Where a sub-processor is established outside the EEA — PostHog, Inc. and Amazon Web Services have US parent companies — or where data may otherwise be accessed from outside the EEA, we rely on the European Commission's Standard Contractual Clauses together with supplementary technical and organisational measures, or on an adequacy decision where one applies.

You may request a copy of the relevant safeguards at <privacy@hausfuchs.com>.

7. How long we keep it

Deleted data can remain in our database backups for up to 14 days. If we ever restore a backup, we delete it again before the service uses the data.

We may keep data longer where a longer period is required for security, legal or accounting purposes, or where we need it to establish, exercise or defend a legal claim.

Aggregated statistics — counts and summary measures computed across participants, containing no recordings, no query text and no identifiers, and from which you cannot be singled out — are not personal data and may be kept indefinitely.

8. Your rights

You have the right to:

• Access the personal data we hold about you, and receive a copy.
• Rectify data that is inaccurate or incomplete.
• Erase your data ("right to be forgotten") where the grounds in Art. 17 apply.
• Restrict our processing in the circumstances set out in Art. 18.
• Portability — receive data you provided in a structured, commonly used, machine-readable format, and have it transmitted to another controller where technically feasible.
• Object to processing based on legitimate interests, including the analytics described in Section 3. If you object we will stop unless we can show compelling legitimate grounds that override your interests.
• Withdraw consent at any time, for session recording and non-essential cookies. This is as easy as giving it — one control in /privacy-settings. It stops recording immediately and, because observation is the purpose of the beta, ends your participation in it.

You can see, download and delete your chats yourself in your profile. To exercise any of these, email <privacy@hausfuchs.com>. We will respond within one month. There is no charge unless a request is manifestly unfounded or excessive.

Complaints. If you think we have handled your data unlawfully, you may complain to the Finnish Data Protection Ombudsman:

Tietosuojavaltuutetun toimisto, Lintulahdenkuja 4, 00530 Helsinki — tietosuoja.fi

You may also complain to the supervisory authority where you live or work.

9. Automated decision-making

The Beta Service produces automated estimates, scores and classifications about properties and areas — not about you. We do not make decisions about you that produce legal effects concerning you or similarly significantly affect you, within the meaning of Art. 22 GDPR, and we do not profile you for that purpose.

The chat is an AI system. You are told this in the chat window. It does not make decisions about you.

We do link your usage to your participant profile in order to understand behaviour and run experiments, as described in Section 3.

10. Security

We protect your data with access controls, encryption in transit, hashed credentials, network isolation between environments, and default masking of sensitive input in session recordings. No system is perfectly secure, and the Beta Service is pre-release software. If a personal data breach is likely to result in a high risk to your rights, we will notify you without undue delay.

11. Children

The Beta Service is not intended for anyone under 18 and we do not knowingly collect data from children. If you believe a child has given us personal data, contact <privacy@hausfuchs.com> and we will delete it.

12. Changes to this policy

We may update this policy. We will notify you by email or through the Beta Service before a material change takes effect, and the version identifier and date at the top will change. Where a change requires your consent, we will ask for it.

13. Contact

Hausfuchs Oy, Business ID 3643057-1, Helsinki, Finland — <privacy@hausfuchs.com>