Levora
What happens to your data – and what does not
Where your data sits, who sees it and what happens to your documents – no asterisks, no “coming soon”.
From photo to approval
What happens to a measurement ticket
A site ticket records where work took place and what was done. Names and signatures can link it to an individual. Here is how you review it in Levora:
- Capture the photo. Take a photo of the completed ticket and upload it.
- Review the suggestion. Levora reads the item and quantity from the photo. Compare the suggested values with the original and correct them if needed.
- Approve the quantity. Once you confirm it, the quantity is ready for billing. The photo stays attached to the record so you can trace the quantity back to its source.
Measurement ticket
Fictional example- Work site
- Musterweg 12
- Date
- 14 Oct 2026
- Item
- 01.02.0030
- Quantity
- 12.50 m²
A measurement ticket may also contain names and signatures.
Where
Where the data sits
Data centre in Germany
Operated at Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen. The servers are in Germany; there is no transfer to a third country. The specific data centre location is named in the data processing agreement – that is where it is binding, not on a website that can change.
One processor, not three
There is no chain of analytics, mail and storage services in different countries. The hoster is the only third party that gets to see data – and even it only as a processor under Art. 28 GDPR.
In place today
What is in the product today
Every point here is implemented in code and verifiable – not planned, not in progress.
Customer separation at the data layer
Every access to a record is restricted to the customer. There is no way to reach another firm’s data through an ID.
Roles and permissions
Personnel data and contracts are visible to administrators only; so are write operations. A colleague capturing Zettel does not see a personnel file.
Access log
Access to staff and contract data, and every invoice cancellation, is logged: who, when, which record. That is the evidence required by Art. 30 and 32 GDPR.
Encrypted documents
ID cards, driving licence scans and contracts are stored AES-256-GCM encrypted in object storage – never in clear text. The driving licence number is encrypted in the database as well.
Invoices stay what they were
An issued invoice is neither overwritten nor deleted. A cancellation sets the original to “cancelled” and creates a credit note – both remain in place.
GoBD export for the tax audit
The auditor gets the Z3 package: a ZIP with invoice headers, invoice lines and an index.xml following the description standard. Not assembled on request, but a button.
Site diary as evidence
A closed diary entry is immutable – the precondition for it to be worth anything under VOB/B in a dispute.
Encrypted transport
Mutual TLS authentication between gateway and data service is set up and active – a service without its own certificate does not get through; the reflection interface is switched off in operation.
The Zettel recognition and the AI
Two points on which we have committed ourselves – and which no competitor discloses this way:
At Levora, data protection is built in and absolutely secure:
- No data retention: Every time a text (for example a document for text recognition) is sent to a language model, Levora enforces the strictest data protection rules. The system tells the providers in no uncertain terms: “Store nothing and use none of it for training!”
- Non-negotiable: This is not a simple setting that could be switched off or forgotten by accident. The rule is written directly into the program code – it does not live in a configuration file that can be changed.
- Automatic checks: Automated tests in the Go and Python programming languages make sure the program raises the alarm and stops immediately if anyone tries to remove this safeguard.
In short: data protection is hard-coded into Levora and cannot be switched off by accident – neither by users nor by developers.
The AI helps – a person decides:
- Read and suggest: The AI assistant answers questions and makes suggestions. It changes invoices or other data only once you confirm.
- Only your own data: The AI sees only your firm’s data. Every firm works in its own sealed-off area – the AI cannot reach another firm’s data.
Your data is yours – technically too
The full data export is a function, not a favour: master data, bills of quantities, measurements and invoices as CSV and GAEB, at any time during the term. It is restricted to administrators and is logged – a complete dump of a firm’s data is itself a sensitive operation.
Why this is here: “What happens to my data if I switch?” is one of the first questions a German construction firm asks, and the usual answers are vague. This one is not.
Frequently asked
Questions from firms working in Germany
Does our data leave Germany?
Our client asks for data protection evidence. What can you supply?
Is the interface in English?
We are an EU company operating in Germany. Does GDPR change anything for us?
Go through these points in the conversation
If your client demands evidence, tell us which. We will tell you what we can prove today and what we cannot – before the contract, not after.
