Privacy & Data Protection
DecisionRadar is designed for data-protection-compliant use under German and EU law, in particular the General Data Protection Regulation (GDPR / DSGVO), the German Federal Data Protection Act (BDSG) and, for local device storage, the TDDDG.
In the standalone, device-local configuration, personal and decision-related content—including questions, options, criteria, ratings, notes and Triage cases—is processed and stored locally in the user’s browser. It is not transmitted to a DecisionRadar database, analytics service, AI provider or other DecisionRadar application backend.
Only ordinary technical data required to load the website, such as the IP address, browser information and requested pages, is transmitted to the hosting provider Netlify. In the standalone configuration, decision data leaves the device only when the user deliberately exports or shares it. Where an organisation deliberately enables an institutional integration—such as SharePoint, Outlook / Exchange, LightAssist or host-side persistence—only the data required for that selected workflow is passed to the authorised host under that organisation’s own approved permissions and data-handling rules.
This architecture follows the GDPR principles of data minimisation (Art. 5 GDPR) and data protection by design and by default (Art. 25 GDPR). Where local browser storage requires consent under § 25 TDDDG, DecisionRadar is intended to be used with that consent in place.
In short: DecisionRadar processes the decision where it is made—on the user’s device—and avoids unnecessary transmission of personal data.
The organisation using DecisionRadar remains responsible for ensuring that it has the appropriate legal basis or consent for the personal data it enters and processes, and for configuring any institutional integrations in accordance with its own data-protection, access, retention and security requirements.
Feedback submissions
If you deliberately use the Feedback form on the main page, the name, institution, email address and feedback text you enter are transmitted to and stored in DecisionRadar’s restricted feedback backend, configured in Netlify’s EU Central Blobs region, so the operator can review the message and reply. Feedback is separate from your DecisionRadar decision content. The private Access Monitor shows these submissions only to the operator and allows them to be marked as processed.
How the local architecture works
Storage
The current DecisionRadar draft—including a Triage queue when used—and local usage counters are stored on the device. The fast draft path uses browser local storage for ordinary radars and smaller queues; where available, the same normalized draft is mirrored in IndexedDB for recovery and larger device-side headroom. Large Triage queues use the IndexedDB mirror as the device-side save path rather than repeatedly writing the full queue to localStorage. The application has no built-in customer database, remote analytics or external runtime dependency. Hosting receives ordinary page requests, but DecisionRadar does not send the contents of your decisions to an application backend.
Share links
When you copy a share link, the DecisionRadar data is encoded after the # fragment in the URL. Large Triage queues are intentionally not offered as share links; use JSON or CSV export instead. Browser fragments are not included in ordinary requests to the hosting server. Anyone who receives the complete link can read the shared radar, so treat the link like a document.
Triage cover scan
The Cover Scan button uses the device's ordinary image capture / file-picker flow. DecisionRadar does not open a continuous live camera feed. The captured cover image is held in browser memory for the active case session only and is not written into local storage, JSON/CSV exports or share links. A connected LightAssist host may receive that active image under the host's approved data-handling rules; DecisionRadar asks the adapter not to retain the source image.
Triage source PDFs
Up to 10 PDFs can be attached to the active Triage case. The PDF files stay in browser memory for the active session only and are not written into DecisionRadar local storage, JSON/CSV exports or share links. Switching cases, clearing the source list, starting a new radar or closing the page releases those session attachments. A connected LightAssist host may receive the active session files, or resolve the case documents directly from the host repository by case reference, under the host’s approved data-handling rules; DecisionRadar asks the adapter not to retain source files.
Device permissions
This edition does not use a continuous live camera feed, microphone or geolocation. Cover Scan uses the device's standard image capture / file-picker interface. The origin may use camera permission for capture compatibility, but DecisionRadar does not call a live getUserMedia camera stream.
Institutional-scale persistence
The device-local draft and IndexedDB recovery mirror are convenience layers, not the authoritative institutional records store. Browser quotas still vary. For shared or high-volume deployments, an optional host persistence adapter should write normalized DecisionRadar state back to the authorised host repository while source documents, identity, permissions, retention and audit remain there.
Backups and deletion
Export the DecisionRadar as JSON before changing devices or clearing browser data if you need a portable copy. Starting a new radar replaces the current local draft; browser storage can also be cleared through your browser settings.
Sensitive decisions
Do not share a radar link containing confidential personal, medical, security or commercially sensitive information unless the receiving channel and recipients are appropriate.
Recovery mirror and host write-back
The IndexedDB recovery mirror stores only normalized DecisionRadar state. Raw cover images and dossier PDFs are never added to that mirror. An authorised institutional host may also receive normalized state through the optional persistence adapter; source files and credentials are excluded from that payload.