Hosting
The application runs on a virtual server (Windows Server) at STRATO in Germany. The application and the database server run on this one machine. There is no second machine and no automatic failover: if the server fails, it is restored from backup – by hand, by the operator. For the launch phase that is the honest statement about availability; we do not promise a figure the architecture cannot carry. Maintenance windows for updates are announced.
Customer Separation
Every workspace has its own database. A query from one customer cannot reach another customer's data, because it is not reachable over the same connection at all – a property of the architecture, not a policy. Uploaded files live in their workspace's database: a backup contains everything, a deletion deletes everything. Automated tests check on every build that a tampered identifier reaches no other workspace.
What Is in the Product – and What Never Is
Your workspace holds the documentation: the record of what you process and why, the vendors, the measures, the documents with their approvals, the deadlines of incidents and requests, and the evidence. It holds no copy of your customers' personal data: there is no connection to your customer file, your mailbox or your file storage, and a data subject request is recorded with a reference, never with the name.
Encryption
- In transit: TLS 1.2 or newer, HSTS, security headers; certificates renew automatically.
- At rest: the database files on the server itself are not encrypted; the edition of the database server in use does not offer it. What is encrypted is everything that leaves the server – every backup – and, field by field with the application key, the most sensitive free text: descriptions of incidents and data subject requests.
- Credentials: passwords as PBKDF2 hashes; privileged roles must set up a second factor; repeated failed logins lock the account; public endpoints are rate-limited.
Backups
Every database is backed up daily. Each backup is encrypted on the server right after it is written (AES-256-GCM), before it can leave the machine; only the encrypted file is downloaded and copied to a second location in the EU. Backups are kept for 30 days. A backup that cannot be encrypted is discarded, not kept in the clear.
The Assistant Pilo
Pilo is switched on per workspace, deliberately. The language model runs on Amazon Bedrock, called in Frankfurt with the EU inference profile: inside the EU, never outside. Only what the published rule allows for the task at hand is sent; names the application knows are replaced by codes, e-mail addresses and phone numbers removed, data subject requests never sent. Amazon Bedrock stores no inputs and does not train on them. Every call is logged with time, person, purpose and size – never with the text.
Access by the Operator
The operator does not open your workspace on his own initiative. If you need help, you grant access in the application for a limited time – read-only, with a visible banner and an end time. Every access is logged, and you can end the grant at any time.
Deletion and Hand-over
When a subscription ends, the hand-over package is available at once and for 30 days: every approved document as PDF, the registers as Excel, the history as a report, a JSON file. Then the workspace's database is dropped – dropping a database is a cleaner and more provable statement than deleting rows – and the deletion is confirmed by e-mail. The backups expire after a further 30 days; at the latest 60 days after the end of the hand-over period nothing remains.