AI transparency
AI transparency
Which AI models BauWalker uses, where your data is processed, where the limits lie and what you confirm yourself. As of: 08.10.2026.
Note: This page is information from the provider (Bergstone GmbH). It is not a certification, not a seal of approval and not a confirmation by third parties. The authoritative documents are the privacy policy and the AGB.
What BauWalker uses AI for
BauWalker uses AI language models for document analysis, text summarisation, research and decision support. Specifically: answers in the chat, preparing documents (e.g. invoice, offer, Nachtrag), reading photos and scans (e.g. receipts, letters), evaluating meetings, and review hints on contracts. Calculations and finished documents are produced by the platform using fixed rules and templates, not freely by a language model.
Which models, where processing takes place
| Model / service | Operation | Purpose |
|---|---|---|
| Qwen (open language model, size 27B) | On our own servers in Germany (Hetzner), not at an AI provider | Standard route for project, contract and personal data: chat answers on them, document analysis, contract review, reading photos and scans |
| GLM via z.ai | External provider, processing may take place outside the EU/EEA | Questions on public building law that our PII gate (technical check for personal data) classifies as non-personal; evaluation of meetings (transcript and, in project matching, project-related amounts) |
| Firecrawl (web search) | External provider, optional | Internet research; queries are first checked for personal content by a rule-based gate |
Which other service providers are involved in individual cases is stated in the privacy policy (section "Recipients and processors").
How data is processed
- Principle: Project, contract and personal data are, as a rule, processed via the locally operated model.
- Rule-based check: Whether a question may go to an external service is decided by a rule-based technical check. It is not anonymisation and can make mistakes. Read more about the PII gate →
- Exception is explicitly configured: the meeting evaluation (z.ai), see table.
- Logging: The chosen model route and security-relevant accesses are logged. Full content logging of every intermediate AI step does not take place.
- Encryption: The connection to BauWalker is encrypted via TLS (HTTPS).
- Tenant separation: Data of different customers is separated at database level.
Limits of AI outputs
- AI outputs are machine-generated and can be incomplete, outdated or incorrect .
- They are drafts and working aids, not binding information.
- BauWalker provides no legal or tax advice and does not replace a lawyer or a tax advisor. BauWalker does not check whether claims, Nachträge or deadlines exist in an individual case.
- Calculations (e.g. Abschlags- and Schlussrechnungen, Zahlungspläne) are based on your inputs and documents. BauWalker does not check the accuracy of the inputs or the legal permissibility of the billing towards third parties.
Human control
- You review AI results before use, in particular amounts, deadlines, legal provisions and documents that go to third parties (e.g. client, authorities, tax office).
- The platform carries out invoicing and payment releases only after your separate, active confirmation . Invoices sent by email to your customers likewise go out only after your explicit confirmation in each individual case.
- A solely automated decision with legal or similarly significant effect (Art. 22 GDPR/DSGVO) does not take place.
Labelling
You are notified in the application when you interact with an AI system or when content is AI-generated (Art. 50 of Regulation (EU) 2024/1689, AI Act).
Questions
Please direct questions about the AI functions and data processing to info@bergstone.de, subject "AI transparency".