App privacy policy
As of October 2026
This is a translation; the German app privacy policy is the binding version.
1. Controller
Responsible for the processing of data in the Tropfwerk App within the meaning of the General Data Protection Regulation (GDPR):
Capanna Engineering
Owner: Stephan Oschmann
Zum Mühlbach 13
92676 Speinshart
Germany
Email: kontakt@tropfwerk.de
This policy applies to the app at app.tropfwerk.de, to the connection between app and system via link.tropfwerk.de and to the sign-in at auth.tropfwerk.de. For the website, the live demo and the newsletter, the website’s privacy policy applies.
2. How the app works
Your system stands at your home and holds all of your garden’s data. If you switch on “App access” at the display (it is off from the factory), the system itself opens a connection to my server. The app on your phone sends its requests to your system through this server, and the server passes request and answer on. With app access off, this connection does not exist.
3. Server and server log files
App, connection and sign-in run on the same server of my own in Germany as the website, which I operate myself. I do not use a hosting provider. Data only goes to countries outside the EU if you switch on notifications on your phone (section 9). When you visit, the server automatically records server log files with IP address, date and time of access, address requested, amount of data transferred, referrer and browser details. They serve only secure operation and are deleted automatically after 7 days at the latest. The legal basis is my legitimate interest in secure operation (Art. 6(1)(f) GDPR).
4. Your account
You need an account for the app. You create it after scanning the QR code on your system’s display. Account and sign-in are managed by sign-in software (Authentik) at auth.tropfwerk.de on the same server. It holds your name, your email address, which is also your user name, and the public part of your passkey. The secret part of your passkey stays on your device, and there is no password.
The sign-in records sign-ins and sign-in attempts with IP address and browser details. These records are deleted after 30 days. For every active sign-in session it also keeps the IP address and browser until the session ends. To keep the app signed in, the sign-in gives it a renewal key that is valid until it expires or you sign out. For the sign-in session, auth.tropfwerk.de sets a technically necessary cookie that needs no consent (Section 25(2) no. 2 TDDDG).
The legal basis for the account is the performance of the contract of use (Art. 6(1)(b) GDPR), for the sign-in records my legitimate interest in secure access (Art. 6(1)(f) GDPR).
5. What my server stores
- Account. An identifier from the sign-in, your name, your email address and when you first and last used the app.
- System. A random identifier, its name, the controller’s software version and when it was last connected. The server stores its access key only as a checksum that cannot be turned back into the key. The system only signs in to my server with an admission code I hand out for it. The server stores this code only as a checksum too, along with my note of whom I gave it to.
- Access. Which account may see which system, as owner, co-user or garden service, and since when.
- Pairing. The pairing code, also only as a checksum. The server remembers a used QR code for 30 days so that a second scan can show “Already paired”. A system that is not paired within a day is deleted again. When paired, your system receives the owner account’s name, or its email address instead, and shows whom it is connected to.
- Log. Changes to your system, such as a watering started, as well as pairings, links for creating an account, access given and removed, switching off app access, devices reported as lost and refused requests. Each entry records when it happened, which account and which system were involved, which function was requested and with what result. Merely viewing is not logged, and IP addresses are not in it. The entries are deleted after 90 days.
- Notifications. If you switch them on, your browser’s address for them (section 9).
I need account, system, access and pairing so that the app works for you (Art. 6(1)(b) GDPR). The log serves security, because valves and pump are switched through the app (Art. 6(1)(f) GDPR).
6. What my server does not store
- Your garden’s data, that is zones, water in the soil, weather, history and what is running, is only passed on by the server between app and system. It does not keep it, and the data stays on your system.
- Apart from the server log files (section 3) and the sign-in (section 4), the server stores no IP addresses. To fend off too many requests it holds them briefly in memory and forgets them two hours after the last request at the latest.
- For the live state the app gets a ticket that exists only in memory, is valid for 60 seconds and can be used only once.
7. In your browser
The app sets no cookies. Your browser’s storage (localStorage) holds the renewal key that keeps you signed in. The app also remembers there the system you last chose, settings such as language, light or dark and display size and, while a manual control you started is running, its number and start, so that the app finds it again after a reload. During a sign-in a check value is kept there briefly, and after signing out a note that the next sign-in asks for your passkey again. In session storage (sessionStorage), which ends when the tab is closed, it notes during an update which version it expects after the reload.
A service worker keeps the app’s files ready so that it starts quickly. It never stores your garden’s data, requests to my server or the sign-in. If you switch on notifications, it receives and shows them, and your browser remembers the address for them until you switch them off again.
These entries stay on your device. Signing out deletes the renewal key, and you delete everything else in your browser’s settings for app.tropfwerk.de. The entries are strictly necessary for the app and therefore need no consent (Section 25(2) no. 2 TDDDG).
8. Co-users and garden services
You can give other accounts access to your system, for example someone in your household or a garden service. They then see your garden in the app and can operate it. Some settings only the owner can change. As the owner you see in the app who has access, with name or email address, role and since when, and you can remove any access.
With every request from the app the server tells your system which account is making it, with identifier, name or email address and role. This is how the system checks what this account may do. If you start a watering or a refill through the app, the system notes your name with it in its history.
9. Notifications on your phone
Under Settings › Account › Notifications you can switch on notifications. Tropfwerk then lets you know on your phone when frost is forecast, when your system reports an alarm and when my server has not reached it for an hour. The owner and the co-users of a system receive notifications.
When you switch them on, your browser creates an address for notifications. My server stores it with two keys for the encryption, for at most ten browsers per account. If you switch notifications off or your browser gives the address up, it is deleted, and also after five failed delivery attempts in a row. So that a notification does not arrive twice, the server remembers for 30 days for which system and for what reason it has already sent one.
Delivery runs through your browser’s push service. Which one that is depends on browser and device. On the iPhone it is Apple, in Firefox Mozilla, in Edge on a computer Microsoft and otherwise mostly Google. Some of these providers are based in the USA. My server encrypts the content of the notification so that only your browser can read it. The push service only sees the address, the time, the size, how urgent the notification is and its kind, such as frost or alarm, with a random short code of your system.
The legal basis is the performance of the contract of use (Art. 6(1)(b) GDPR). Google and Microsoft are certified under the EU-US Data Privacy Framework, so the European Commission’s adequacy decision on it applies to them. Apple and Mozilla are not. The transfer to them is necessary for the contract with you (Art. 49(1)(b) GDPR), because you switched the notifications on and your device receives them only through its push service. They come only occasionally, when frost is forecast, on an alarm or when your system cannot be reached. With Apple and Mozilla the data does not have the level of protection it has in the EU, and US authorities may be able to access it. Even they cannot read the encrypted content of your notifications. If you switch notifications off, the transfer ends.
10. No analytics, no advertising
There is no analytics, no tracking and no advertising in the app or the sign-in. Fonts, pictures and all other files come from my server, and no content is loaded from third parties.
11. Deleting your account
Write to me at kontakt@tropfwerk.de if you want your account deleted. I then delete your account at the sign-in and on the server, together with your access and your addresses for notifications. Log entries disappear after 90 days at the latest, sign-in records after 30 days. Your garden’s data is on your system and stays there.
As the owner you can remove a disconnected system from the app. The server then deletes it together with its pairing and access; only its log entries remain until their deadline.
12. Your rights
Your rights of access, rectification, erasure, restriction of processing, data portability and objection and your right to lodge a complaint apply here just as for the website. They are set out in the website’s privacy policy in sections 7 and 8. A message to kontakt@tropfwerk.de is enough to exercise them.
Right to object under Art. 21 GDPR
If I process data on the basis of my legitimate interest (Art. 6(1)(f) GDPR), for example the server log files, the sign-in records or the log, you can object to this processing at any time on grounds relating to your particular situation. I will then no longer process the data unless I can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims.