Security

What the software protects today, and what is still missing

This page describes the state of the software, not a promise. Each measure has a status and states what it covers and what it does not. Status as of 8 November 2026.

active wired into the code and used in the flow partial present, with named gaps in preparation built or planned, not yet in the flow disabled present, but switched off missing not yet implemented
6active
15partial
2in preparation
1disabled
6missing

Sign-in and access

Who can sign in and how long a session lasts.

01active

Sign-in to the server

The desktop app signs in to the server and checks the session at start. No further check runs while the app is in use.

02partial

Lock of the interface

The firm interface appears only after approval. Some background commands run before sign-in. This gap is open.

03in preparation

Password policy

Rules for length and strength are defined and tested. They are not yet built into the sign-in flow.

04disabled

Two-factor sign-in for auditors

Currently switched off. Sign-in works with a password only.

05partial

Client sign-in with e-mail code

Starter password and a code by e-mail. The code is valid for 10 minutes and locks after 5 failed attempts; attempts are 60 seconds apart. Sending the code requires a configured mail service.

06partial

Separation of clients

Clients see only their own requests and files. Restricted starter-password sessions can neither upload nor download.

Data and documents

How files are uploaded, protected and deleted.

07partial

Check on upload

File extension, size (25 MB), file header and macro check for auditor uploads. An older upload path for client documents checks only the size.

08partial

Release code for protected changes

The code arrives by e-mail, is valid for 10 minutes, allows 5 attempts and can be used once. It protects clients, projects and documents. Deleting an account in the admin area needs no code, and the desktop app has no code step yet.

09active

Balance confirmation by link

The reply link is valid for 30 days and works only once. Only a hash of the token is stored. Amounts are compared in cents.

10partial

End-to-end encryption for uploads

Optional. Whoever chooses it uploads the file content encrypted (AES-256-GCM). The device key stays in the browser of the device. Without this choice the file is uploaded in plain text.

11partial

Deletion of accounts and clients

Deleting an account removes its files and data. Deleting a client does not yet remove all audit-result and sync data.

12missing

Retention periods

There is no automatic deletion after a retention period has expired yet.

13in preparation

Encrypted storage in the browser

A module for passphrase-protected storage exists. It is not yet used by any product part.

Traceability

How changes are detected and assigned to a user.

14partial

Hash-chained audit log

Every entry in the database is linked to its predecessor. A manipulation in the database is detected. Exported copies do not contain the full chain.

15active

Findings store with checksum

Stored findings carry a SHA-256 hash. A change shows up in the check.

16partial

User and role in the log

Each entry names the signed-in user. The role is fetched from the server at every sign-in. A change of role takes effect at the next sign-in.

17partial

Four-eyes release

The release levels check the right against the state the server provides. The sign-off button in the file area is not yet bound to this check.

18missing

Write protection after completion

After the risk assessment is completed there is no technical write protection yet. A change is only shown as a flag.

AI features

What the AI sees, where the data goes and who starts it.

19partial

Anonymisation before AI submission

Identifiers such as IBAN, tax and commercial register numbers, e-mail, phone, social security number, IP address and credit card number are replaced. Personal names are not reliably recognised.

20active

AI only on click

AI tools start only when you act. They deliver drafts for review.

21partial

Models and data path

AI calls go through our own worker. Most tools use DeepSeek. The OCR correction uses Gemini. These providers process data outside the EU; the AI policy describes this.

Desktop app and website

Protection on the device and on the public pages.

22partial

Connection to server and worker

The default addresses use HTTPS. The app does not enforce HTTPS for custom addresses in the configuration file.

23active

Website with Content Security Policy

The public pages send a Content Security Policy, HSTS and protection against framing. They load only our own files and Cloudflare services.

24missing

Content Security Policy of the desktop app

The app sets no Content Security Policy. The desktop interface is reachable from every script in the window.

25missing

Encryption of the local database

The local database with journal, balances, documents and findings is stored unencrypted on the device. Protection relies on the operating system and the device lock.

26missing

Session and AI tokens on the device

The session token and the AI token are stored unencrypted in files in the app data folder. The system keychain is not used.

27active

Copy protection

It stops casual copying in the interface. It is not a real lock: developer tools or disabled JavaScript bypass it.

28partial

Third-party libraries

Some libraries are bundled with the program. Others are loaded from CDNs at runtime, without a checksum.

29missing

File access, updates and dependencies

File access from the interface is not limited to one folder. Updates are not signed. The build check does not scan dependencies.

Working together in the team

How people work together on a client and what the server sees of it.

30partial

Encrypted metadata of the team state

The team state itself is encrypted. Since this version, the details about it are encrypted too: who saved, who is currently in the client file, which view is open and who sets a lock. The key comes from the team passphrase and stays in the browser. The server no longer stores an e-mail address for this. Visible remain timestamps, the kind of action, the size of the state and the internal user ID. Older desktop versions show no names until they are updated.

What comes next

No dates. The order follows the risk.

  1. Content Security Policy for the desktop app and restriction of the desktop interface for scripts.
  2. Move session and AI tokens into the system keychain.
  3. Encrypt the local database with a key concept.
  4. Build the password policy into the sign-in flow.
  5. Bind the "Sign off" button in the file area to the server's permission check.

There is no certification, for example under ISO 27001 or SOC 2. The statements rest on a review of the source code by the developer, not on an external audit. Please report security issues by e-mail to [email protected].