Reporting, Data Security, and Deadlines

You can download individual reports as a report document (DOCX), as an activity record (PDF) or complete as a ZIP with all attachments. For analysis, overview tables are available as XLSX, and the checklist of areas of application can also be exported as an Excel file. Every download of a report is recorded in the activity log with the person and time, so it remains traceable who exported a report.

The case history is protected by the application: messages, system entries and activity log entries can be neither edited nor deleted, and the log has a single permission – read. However, preeco | whistleblower does not use cryptographic signatures or WORM storage, and audit-proof archiving, for example under the German GoBD rules, is not guaranteed. For external evidence, export the complete report including its history as PDF, DOCX or ZIP and file it in your own audit-proof archive.

Cloud and private cloud run in ISO/IEC 27001-certified data centers operated by Hetzner Online GmbH in Nuremberg, with daily off-site backups in Falkenstein – both in Germany. The software itself does not transfer personal data to third countries. preeco GmbH does not currently hold its own ISO 27001 certification; operation takes place in the certified data centers. On-premises, you run the software in your own infrastructure.

The activity log records who in the reporting office opened, exported or changed a report and when, with the old and new value for changes. Only administrators can view it; you set retention per team to between 3 and 36 months or unlimited. Access by the whistleblower, by contrast, is not logged: to protect them, preeco | whistleblower deliberately does without system log files and stores no IP addresses that could identify whistleblowers.

In the cloud and private cloud, all data is backed up daily and kept for seven days; an additional daily backup is stored in a separate data center in Falkenstein. preeco handles restoration. Availability is guaranteed at 99.0% per calendar month. For on-premises installations, backup, recovery and availability are agreed individually.

Users secure their login with two-factor authentication using an authenticator app; administrators can make it mandatory for the whole team. Staggered lockout periods apply after repeated failed attempts, and a session ends after 120 minutes of inactivity. In the private cloud and on-premises, single sign-on via SAML2 is optionally available. All transfers are encrypted via TLS, and sensitive content such as correspondence is stored AES-encrypted in the database.

Only after explicit activation are the facts and messages of a report, plus optional additional instructions, sent to the provider you have configured yourself. The whistleblower's name and email address are not included. Request and response contents are stored encrypted and cleared after seven days, and every call is recorded in the AI activity log. Through an OpenAI-compatible endpoint you can also connect a self-hosted model, in which case the content never leaves your infrastructure.