How DiPAgE works technically

Although DiPAgE is provided via the internet, the application itself runs locally in the browser of the device used. This applies both to the web version and to the installed Progressive Web App. The plant protection product records, partial data and local working states you create are stored in the local browser storage of the device.

This distinguishes DiPAgE from classic cloud applications, in which every entry is stored immediately on a central server. The Julius Kühn Institute has no access to the locally stored plant protection product records.

What data sovereignty means in DiPAgE

Users decide themselves on which device their records are kept and when they pass files on to other persons or bodies. There is no (partly) automatic transmission of the complete plant protection product records to the JKI, advisory services, authorities or other third parties.

This set-up strengthens data sovereignty, but at the same time means that there is no central body that can restore a lost local working state. Anyone who deletes their browser data, loses the device or has a technical defect can, without their own backup, also lose the locally stored DiPAgE data.

When data does leave the device

Certain functions need online services. When searching for a product, querying an indication or using map services, a technical request is sent to the service concerned. The information necessary for this specific request and, for technical reasons, also connection data such as the IP address are transmitted.

The locally stored complete plant protection product records are not automatically sent along with such requests. The actual record files are only passed on when the user creates an export themselves and then sends or otherwise provides this file.

Local browser storage: advantage and responsibility

DiPAgE uses the browser’s local storage. Normally the data is kept even after the browser is closed and after a device restart. It becomes problematic if browsers or company policies automatically delete website data on exit, if private or incognito mode is used, or if the user removes the website or browser data themselves.

An installed web app, too, remains technically tied to the storage technology of the underlying browser or operating system. Installation alone therefore does not replace a data backup.

Back up regularly

The user or the farm is itself responsible for the long-term retention of the documentation data. It is advisable to export finished plant protection product records regularly as files and, in addition, to create a complete backup of the current DiPAgE working state at sensible intervals.

A complete backup is particularly worthwhile before major changes to the device, before changing the browser, before system or browser updates, before resetting a device, and whenever a larger number of new records has been entered.

Deliberately deleting local data

Anyone who wants to remove DiPAgE data completely from the device can delete the stored website data of the DiPAgE address in the browser. Beforehand, all records and backups that are still needed should be saved externally, because deleting the local storage cannot be undone.