Privacy policy

As of 21 November 2026

1. Controller

Helmut Krämer, Augasse 29, 3434 Katzelsdorf, Austria
E-mail: [email protected]

This policy explains which personal data are processed when you visit this website, for what purpose and on which legal basis (GDPR).

2. Hosting and server log files

The website is hosted by World4You Internet Services GmbH (Austria). When you open a page, the web server processes technically necessary access data (IP address, date and time, requested address, browser and operating system information) and keeps it in log files. Purpose: delivery, security and stability of the website. Legal basis: legitimate interest (Art. 6(1)(f) GDPR). The retention period is determined by the hosting provider. World4You processes these data on my behalf under a data processing agreement according to Art. 28 GDPR.

3. No tracking, no own cookies

This website uses no analytics or advertising services and sets no cookies of its own. Third-party content (sections 5 and 6) may set cookies or process data itself.

4. Fonts

The fonts of this website (Space Grotesk, IBM Plex Sans, JetBrains Mono) are delivered from this server. No data is transmitted to Google or other third parties for this purpose. The fonts are licensed under the SIL Open Font License 1.1.

5. Embedded LinkedIn posts

The start page shows posts embedded from LinkedIn. When the start page is opened, your browser loads content from LinkedIn (LinkedIn Ireland Unlimited Company); LinkedIn receives your IP address and browser data and may set cookies. If you are logged in at LinkedIn, the visit can be assigned to your account. Legal basis: legitimate interest in presenting my posts (Art. 6(1)(f) GDPR). More: linkedin.com/legal/privacy-policy.

6. AI chat on the Home Lab page

If you use the chat, your message is sent from the web server to the Anthropic API (Anthropic PBC, USA) and answered by the AI model Claude. The messages are not stored on this website. Please do not enter personal data. To limit abuse, the server keeps a hashed (not readable) form of your IP address and the time of your requests temporarily to count requests per hour. Legal basis: your request (Art. 6(1)(b) GDPR) and legitimate interest in security (Art. 6(1)(f) GDPR). Transfer to the USA is based on the data-protection terms of the provider. More: anthropic.com/legal/privacy.

7. Contact

If you contact me by e-mail or LinkedIn, I process your details and message to answer your request. Legal basis: Art. 6(1)(b) or (f) GDPR. I delete the data when the matter is settled and no retention duty applies. LinkedIn processes data under its own policy.

7a. Usage statistics, anonymous device and car data, and feedback of the Home Assistant integrations

Which values exactly, how often and why, is listed in section 7b.

The switch Share anonymous data in the Viertelstunden-Wächter and in Plugwhen (off by default) covers two things: the usage statistics described below and, from a later version, anonymous daily values of the connected devices (Wächter) or of the car (Plugwhen). These are, per device or car and day and rounded: type, manufacturer and model as known to Home Assistant, energy, highest power, running time, mean outdoor temperature, kilometres and consumption per km, and for batteries the energy charged and discharged. They are sent without date, time of day, location, names, entity ids or any id of the installation, mixed and stored without any connection to the sender; after sending they can no longer be assigned to anybody and therefore cannot be deleted individually. Purpose: models of consumption and wear per device and car model (for example consumption by temperature, battery health, a drop in wallbox power) that the integrations use, published summaries, and summaries passed on to research or partners, always from at least 10 installations and never about single installations. The integrations keep working locally and free of charge. No sale, no passing on of the daily values. Legal basis: your consent, Art. 6(1)(a) GDPR; switching it off stops all sending.

Device check (Viertelstunden-Wächter from version 0.15). With the switch on, the Wächter asks our service once a day whether the connected devices still work as usual. For this it sends, per device: type, manufacturer and model, and rounded measured values of the last 120 days at most: for wallboxes the power while charging compared with the set current and phases, for home batteries the energy and the change of the state of charge per charge or discharge, for pumps and similar devices the power while running, and for heat pumps and water heaters the daily energy with the mean outdoor temperature. Instead of a date each value carries only how many days ago it was measured, so the check can see a trend. The request contains no names, entity ids, location and no id of the installation; device numbers are valid only within one request. The service works out the answer (for example “the wallbox has charged with less power than set for days”) and sends it back; it does not store the request. It keeps only the values of finished days as anonymous rows (kind and type of device, manufacturer, model, energy, highest power, running time, outdoor temperature, for wallboxes the share of the set power, for batteries the estimated capacity, its share of the battery’s own starting value, the rated capacity and the age in half years, for heat pumps and water heaters the day compared with the device’s own usual value and, for heat pumps, how much more it needs in the cold than in mild weather; also the version of the row format and the quarter in which it arrived, so that old rows can be replaced or expire; without date and without any connection to each other or to the sender), for models per device model as described above. Users who already shared data before version 0.15 are asked once under Repairs in Home Assistant; until they confirm, the device check sends nothing. Legal basis: your consent, Art. 6(1)(a) GDPR; switching off stops the device check.

Fleet values (Plugwhen from version 0.9). With the switch on, Plugwhen sends the new trip days of the car at most once a day: car model, battery size, kilometres, consumption per km, mean outdoor temperature and the odometer only as a step of 10,000 km, and for days charged only at home the wallbox energy per full charge (for charging losses and battery ageing), and, after agreeing to the current text, per whole day parked and not charged the fall of the state of charge (loss while parked); rounded and without date, location, names or any id. The service files the car model under a model of a public list and keeps the name as sent, the version of the row format and the quarter in which it arrived. The trip days are mixed and stored without any connection to the sender; therefore they cannot be deleted individually. In return Plugwhen gets a random key valid for 180 days, with which it fetches the consumption values of the same car models. Only a hash of this key is stored, separately from the trip days. Legal basis: your consent, Art. 6(1)(a) GDPR; switching off stops the sending.

The integrations Viertelstunden-Wächter and Plugwhen can send an anonymous usage statistic once a week, but only if you switch this on (it is off by default). It contains a random id that is drawn anew every month, the versions of the integration and of Home Assistant, the country and language set in Home Assistant, roughly how long the integration has been running (0–1, 1–3, 3–6 or more than 6 months), which kinds of devices are set up and from which integrations their entities come; after agreeing to the current text also, for wallboxes that Plugwhen controls, integration, model and firmware and how fast and how reliably they take a new value, and for the Viertelstunden-Wächter rough classes of the household: the peak of the last month with and without the Wächter and the number of interventions in the last 30 days (for example “8–11 kW”, “6–20”), never the values themselves. It contains no names, entity ids, addresses, measurements or passwords. Legal basis: your consent, Art. 6(1)(a) GDPR. Switching it off deletes the data of these ids; data of an id that has not reported for 60 days is deleted automatically.

If you send feedback from an integration, your text, an optional contact address and, if you choose so, the same overview of the setup are stored to read and answer it. Legal basis: Art. 6(1)(b) or (f) GDPR. I delete it when the matter is settled. For both, the scripts store no IP address; the server log files of section 2 apply. The data is stored on the web space at World4You in Austria.

If you press Send bug report at the feedback, a bug report is sent: version, mode, which integrations control the devices, how fast and how often commands reached the devices or failed, whether the sensors deliver values, and the last warnings of the integration. Names, entity ids, addresses, IP addresses and identifiers are removed first. Afterwards a notification in Home Assistant shows you exactly what was sent. Purpose: finding and fixing errors. Legal basis and deletion as for feedback.

7b. What the integrations send, when and why

Everything in this list is sent only with the switch Share anonymous data (off by default); feedback and bug reports only when you send them yourself. Values marked announced are sent only from the version named; this is then stated in the change log of that version and in the dashboard.

What is sent when, and why

ValueExactlyHow oftenWhyActive since / announced from
Both integrations
Weekly statistics version of the integration and of Home Assistant, country and language as set in Home Assistant, roughly how long it has been running (0–1, 1–3, 3–6, more than 6 months), a random id drawn anew every month; and the set-up: how many devices or cars of each kind, from which integrations their entities come, which modes and extra functions are switched on once a week to count users and versions, to see which set-ups exist, to find errors active since Wächter 0.14, Plugwhen 0.9
Feedback and bug report your text, a contact address if you want, the overview of the set-up if you choose so; the bug report: version, mode, how commands reached the devices, the last warnings; names and ids are removed first only when you press send, also without the switch to read and answer it, to find errors active; bug report since Wächter 0.15, Plugwhen 0.9.1
Viertelstunden-Wächter
Household classes peak of the last month with and without the Wächter as a step (below 5, 5–8, 8–11, 11–15, above 15 kW) and the number of interventions of the last 30 days as a step (0, 1–5, 6–20, more than 20); never the values themselves once a week, with the weekly statistics to see roughly how much the Wächter achieves active since 0.15 (after agreeing to the current text)
Device check per device kind, manufacturer, model and rounded measured values of the last 120 days at most, instead of a date only “x days ago” (details in section 7a); the service keeps only values of finished days, without date and without any connection to the sender once a day to check whether your devices still work as usual; comparison with the same devices active since 0.15 (after agreeing to the current text)
Device counter per device once “new: yes”; with it the service counts devices per kind, manufacturer and model once per device, in the first check after agreeing to form comparison values only from 5 devices of the same model announced from 0.15.1 (otherwise 0.16.0)
Start-up of a device how much more a device draws for a short time when it starts (peak divided by steady power, step 0.1, from 1 to 10), seconds until it runs steadily (step 5 s, up to 600 s); for wallboxes seconds until the set value is reached; only for sensors that report often enough per day with a run, with the device day to hold a device back before its start raises the peak; comparison per device model announced from 0.16.0
Efficiency of the home battery energy out divided by energy in over a whole charge and discharge cycle, step 0.01 (0.5 to 1.0) per day with a finished cycle, with the device day to recognise ageing of the battery announced from 0.16.0
Plugwhen
Wallbox behaviour only in the mode Direct: integration, model and firmware of the wallbox, number of commands, share of failures, typical and long response time in seconds; 3 models at most once a week, with the weekly statistics to see which wallboxes follow reliably active since 0.9
Trip days car model, battery size (whole kWh), kilometres (step 5 km), consumption per km, mean outdoor temperature (1 °C), odometer only as a step of 10,000 km; only days with at least 30 km at most once a day consumption per car model and temperature active since 0.9
Charging days car model, battery size, wallbox energy per full charge (0.1 kWh), temperature, odometer as a step; only days charged only at home as trip days charging losses and ageing of the battery active since 0.9
Parked days car model, battery size, fall of the state of charge per whole day parked without charging (step 0.5 %), temperature as trip days loss while parked per car model active since 0.9
Charging power per charging day as a step: below 3, 3–5, 5–8, 8–12, above 12 kW (mean power of the charges of the day) per charging day, with the charging day charging loss per power instead of one mean value announced from 0.11.0
Phases per charging day 1 or 3, only if known per charging day, with the charging day to recognise the loss with one phase and low power announced from 0.11.0
Lead time of a wallbox with Next Trip number of charges of the week, typical charging power (step 0.5 kW), how much earlier the wallbox starts than needed at full power (step 15 min); no time of day, no deadline once a week, with the wallbox behaviour start values per wallbox model for the plan and “charge at the latest from” announced from 0.11.0 (learned locally from 0.10.2)
Charging energy reported by the car (optional) kWh per 100 % state of charge as reported by the car, step 0.1 kWh; only if the car integration provides the charged energy per charging day, with the charging day to tell battery capacity and charging loss apart announced from 0.12.0, optional: may not be built

All values are sent without date, time of day, location, names or entity ids. Deletion: switching off deletes the weekly data of the remembered ids (otherwise they are deleted automatically after 60 days without a report). The daily values (trip, charging and parked days, device days) carry no id; they cannot be assigned to anybody and therefore cannot be deleted. Switching off stops all further sending.

Stays in your Home Assistant

These logs are not part of the bug report either.

Never sent

Received

As of 21 November 2026, version 1 of the catalogue. Changes: 1 – first version.

8.Your rights

Please write to the e-mail address above. You also have the right to complain to a supervisory authority; in Austria this is the Datenschutzbehörde, Barichgasse 40–42, 1030 Vienna, dsb.gv.at.

Legal notice →