Confida

Self-hosted whistleblowing portal for organizations in the scope of EU Directive 2019/1937 (50 or more workers, Article 8(3)): the 7-day acknowledgment and 3-month feedback clocks, tracked per report.

The problem it solves

The EU Whistleblowing Directive (2019/1937) sets out internal reporting channels for organizations with 50 or more workers (Article 8(3)), with a seven-day acknowledgment and a three-month feedback period (Article 9). National laws vary. Confida records reports and tracks both clocks. A shared "ethics@company.com" inbox is none of those things — it can't take a report without a name attached, it doesn't track deadlines, and it can't show who handled what.

• No route for a reporter who won't attach their name
• No tracking against the 7-day / 3-month statutory clocks
• No usable record of what happened and when

Every feature

• Reporter photos, stripped to pixels. An uploaded photo is rebuilt without its metadata — photos are rebuilt from their pixels, which removes EXIF, GPS, camera, author and timestamp metadata; what is visible in the image stays — then sealed with AES-256-GCM at rest. Documents are refused on purpose: their author history cannot be reliably stripped.
• Deadlines that respect your calendar. An acknowledgment or feedback deadline landing on a weekend or your own holiday shows an observed date moved later — never earlier — beside the untouched statutory date. Your holiday list, no country's calendar shipped or guessed.
• No identity fields. No name, email, phone, or IP is ever asked for or stored; a reporter gets a case code and sets a passphrase as the only way back in.
• SLA deadline tracking. The dashboard counts acknowledge-overdue, feedback-overdue, and due-within-7-days cases using exact calendar-month math.
• Two-way anonymous messaging. A handler posts a message on a case; the reporter reads and replies using their code and passphrase, still anonymous.
• Reporter pages in ten languages. English, German, French, Spanish, Italian, Polish, Dutch, Portuguese, Romanian and Greek. Offer the ones your workforce speaks; a reporter picks one, or lands in the one their browser asks for, and the case shows the language so your handler can reply in it.
• Self-hosted, no vendor in the loop. Reports live on your own PHP + MySQL/SQLite server. Confida adds no external service and no API key, so Ownware never processes your reports.
• Configurable acknowledgment window. Set the acknowledgment window in Settings to match your jurisdiction's transposition of the Directive.
• Handler console with audit trail. A console that tracks every case against its clock, with an append-only audit trail on every change.
• Installable mobile app (PWA). Add it to a phone or tablet home screen straight from the browser — a full-screen app served from your own server, with no app store involved. Business data is not stored offline on the device; what you see is read live.
• Retention you set. Closed cases can be purged automatically after the number of days you choose (0 keeps them). Check your own jurisdiction's retention rule before you set it.
• An owner on every case. Name the handler who owns a case. Switch reminders on and the owner is emailed before the acknowledgment and feedback deadlines — case code and date only, never the report.
• Save and finish later. A reporter who is not ready can keep what they have written for 30 days under a draft code and their own passphrase. Nobody sees a draft, and no clock starts until it is sent.
• Questions for each kind of concern. Up to five optional questions per category, asked when the reporter picks it.
• Linked cases and escalation. Link two reports about the same matter; name someone above the owner who hears about a deadline still missed a set number of days later.
• Updates from inside the app. The Updates page installs a new release with your license key: Ownware's signature is checked, a backup is taken first, and the app puts the previous version back by itself if the update is interrupted or the database step or start-up check of the new version fails. It never checks by itself.
• Backups by themselves. Automatic backups, an optional copy to S3-compatible storage you own, and a weekly check that the latest backup reads back. The Health page names anything that needs attention.
• Own It 4.0.1 — fixes and an up-to-date manual. For Confida, 4.0.1 fixes an installer that had lost its styling, a rollback that a page opened during an update could stop and a command-line update that ended in an error after putting the previous version back. Its manual, FAQ and QUICKSTART now cover everything 4.0 added, including two Nginx rules that keep the data folder private. Your license covers it: press Check for updates on the Updates page, or download it from your order page.
• Own It 4.0.2 — the installer opens on every host. For Confida, 4.0.2 fixes a fresh install on an Apache host: the one-page setup at /install/ looped back to itself and never opened, and now it opens. Confida's Docker image also gives the web server the whole app folder, so a Docker install can finish and update itself. Your license covers it: press Check for updates on the Updates page, or download it from your order page.

Release notes in full

• Own It 4.1: client installations and your other tools. For Confida, 4.1 makes two changes that every app gets. An Extended license bought from October 4, 2026 covers up to ten client installations, one per client project: hand each one over to the client or host it for them, with the client's logo and colors from the app's branding settings. The API reference now shows how to connect Confida to Zapier, Make or n8n, using its own webhooks and API key. Your license covers the update: press Check for updates on the Updates page, or download it from your order page.
• Own It 4.0: it updates and backs itself up. For Confida, 4.0 means updates from inside the app: the Updates page checks for a new release with your license key, verifies Ownware's signature, takes a backup and puts the previous version back by itself if the update is interrupted or the database step or start-up check of the new version fails. A new install can start with a sample business and remove it in one click; backups run by themselves, with an optional offsite copy and a weekly check that the latest one reads back; and the Health page says whether the install is looking after itself.
• Own It 3.2: room to speak up. The 3.2 wave gave Confida's reporting channel room for the person speaking up: the reporting pages in ten languages, a report saved and finished later under a draft code, and questions asked for each kind of concern. Handlers gained linked cases and escalation to someone above the owner, a statistics page drawn from counts and dates only, and one line in the team's chat that carries the case code and nothing from the report.
• Own It 3.1: it writes to the people you serve. The 3.1 wave gave the catalog a way to reach the other side of the transaction: counterparty email through your own SMTP server, calendar feeds your own calendar subscribes to, attachments filed where the paperwork belongs, and export presets other people's software imports. Each outbound feature ships switched off and runs on your own credentials; a failed send is recorded, and the action that triggered it stands. What this app gained is listed at the top of this section.
• Own It 3.0: works for your AI, not just for you. Two-person case access is the headline: seal a case and it stays sealed until two different handlers are on the record — the requester cannot be the confirmer, and admins are not exempt. The MCP endpoint works under the same handler guards, and reporter anonymity survives every new surface.
• Own It 2.0: API, 2FA, backups, dark mode. Confida 2.0 adds the 2.0 owner layer. Upgrade by replacing the files — the database migrates itself, and it is still the same one-time purchase.