Security & Trust
Who runs 2kw.ai, where your data is processed, what we can show today and what we do not claim. Each statement on this page describes the running platform or a signed agreement. The pages linked at the bottom give the full text.
Who we are
- Company
- Manfred Kunze Development GmbH
- Address
- Franz-Wachter-Straße 28, 70188 Stuttgart, Germany
- Commercial register
- Amtsgericht Stuttgart, HRB 802423
- Founded
- 2025
- Managing directors
- Robin Kunze, Falk Wittmann
- Imprint
- manfred-kunze.dev/en/imprint
Where your data is processed
- The application, the sign-in service, document conversion and stored files run at Hetzner Online GmbH in Falkenstein and Nuremberg, Germany, and Helsinki, Finland. Hetzner's data centres are certified to ISO/IEC 27001:2022 and attested under BSI C5 Type 2 for February to August 2025 (Hetzner's certificate and attestation). 2kw.ai itself is not certified.
- The platform database runs on Tiger Cloud from Timescale, Inc. (USA, SOC 2 Type 2), in the AWS data centre region in Frankfurt, Germany. The data stays in Frankfurt; because the contracting party is in the US, the EU standard contractual clauses apply.
- Built-in models run on Azure OpenAI in the EU Data Zone, with the resource in Sweden Central. Your inputs are not used to train models. Dictation runs on Azure AI Speech in the same region, and sign-in and notification e-mails go out through Azure Communication Services with the data location Germany.
- Cloudflare (USA) sits in front of the websites for TLS and protection against DDoS attacks.
- If you bring your own provider key, those requests go to that provider under your own contract with it.
- Billing runs through Stripe, infrastructure monitoring through Grafana Labs (Germany region), and the built-in web search for agents through Linkup (France, EU region).
Every third party, with its purpose, location and safeguards, is on the sub-processor list.
What we can show today
- Encryption
- TLS on every public endpoint, and HTTP redirects to HTTPS. Provider keys you store are encrypted at rest.
- Tenant isolation
- Every record belongs to exactly one organisation. Row-level security in the database is a second barrier behind the application's own checks.
- Access control
- The roles Viewer, Member, Admin and Owner are checked on every API endpoint.
- Approvals
- An agent asks before it changes something, and the platform records who decided.
- Prompt capture
- Prompt and completion text is kept out of traces unless an admin switches capture on for the organisation. Both switches are off by default.
- Backups
- Database: point-in-time restore to any moment in the last 14 days, in the same region. Stored files: a daily copy to a second Hetzner location in Germany, kept for 30 days; a restore has been tested.
- Documents
- A public data processing agreement with annexes, the sub-processor list with notice before a change, and security.txt (RFC 9116).
What we do not claim
- Certification
- ISO/IEC 27001 is in preparation. We are not certified yet. The ISO/IEC 27001:2022 certificate and the BSI C5 Type 2 attestation named on our pages are Hetzner's and cover its data centres and hosting services, not our application. We have no SOC 2 report.
- Penetration tests
- No third-party penetration test report is published at this time.
- Availability
- No specific availability figure is guaranteed unless agreed in writing (general terms, section 4).
- Single sign-on
- Sign-in through your own identity provider (SSO) and user provisioning (SCIM) are not available yet.
Support and contact
- Support
- [email protected], Monday to Friday, 9:00 to 17:00 (Europe/Berlin).
- Sales and demos
- Contact form
- Security
- [email protected], see reporting a vulnerability.
Reporting a vulnerability
Send security reports to [email protected], in English or German. The same contact is published in security.txt (RFC 9116).
- Test only against accounts and data that are yours, and stop once you have shown the issue.
- Do not degrade the service for others: no load tests and no denial-of-service attempts.
- Say what is affected, how to reproduce it and what the impact is. Leave out secrets and other people's data.
- Give us reasonable time to fix the issue before you publish it.
We confirm that we received your report within 3 working days and give you a first assessment within 10 working days. We keep you informed and tell you when the fix is live. We do not run a paid bug bounty.
If you act in good faith and follow these rules, Manfred Kunze Development GmbH will not file a criminal complaint or take legal action against you for the research, including under sections 202a to 202c of the German Criminal Code (StGB) as far as our own systems are concerned, and will not ask anyone else to. This does not bind third parties such as customers or hosting providers, and it does not cover anything outside these rules.