Your financial data is some of the most sensitive information there is. That is why security is not a feature we added later but the foundation Kontavio is built on. This page explains openly how we protect your data.
1. Our security philosophy
We follow three principles:
- Minimal attack surface: We only store data the app needs to work. No credit card numbers, no bank passwords.
- Defense in depth: Several layers of security instead of a single wall: network, application, database, encryption, two-factor authentication.
- Transparency: We say openly how our systems work instead of pretending to be secure through secrecy.
2. Hosting & infrastructure
| Aspect | Details |
|---|---|
| Provider | Hetzner Cloud, Germany |
| Location | Falkenstein (Saxony), EU |
| Jurisdiction | German data protection law + GDPR |
| Operating system | Ubuntu 24.04 LTS with automatic security updates |
| Reverse proxy | Caddy with automatic TLS certificate management (Let's Encrypt) |
| Network | Only port 443 (HTTPS) is publicly reachable. SSH only with key-based authentication. |
Why Hetzner? Hetzner is a German infrastructure provider with ISO 27001 certified data centers. The app and the database run in Falkenstein, in the EU. Unlike US cloud providers, Hetzner is not subject to the CLOUD Act. For payments, emails and the AI features we work with service providers in the US; which data they receive is described in the privacy policy (section 6).
3. Encryption
In transit
- TLS 1.3 for all connections between your browser and our servers
- HTTPS only: HTTP requests are redirected to HTTPS automatically
- HSTS (HTTP Strict Transport Security) enabled
- Caddy manages certificates automatically via Let's Encrypt, with OCSP stapling
At rest
- The database is only reachable via
localhost; no access from outside the server is possible - Passwords are hashed with bcrypt (cost factor 12) and never stored in plain text
- Session tokens are cryptographically random 256-bit values
- Secure flag on all session cookies, so they are only sent over HTTPS
4. Authentication & account protection
Kontavio protects your account with several layers:
Two-factor authentication (2FA)
- Email confirmation: After registering, you confirm your email address via a link (double opt-in)
- TOTP authenticator (optional, recommended): Works with common authenticator apps such as Google Authenticator, Authy, 1Password or Bitwarden
- Recovery codes: 8 single-use backup codes for emergencies, in case your authenticator app is not available. Recovery codes are stored as bcrypt hashes.
- With 2FA enabled, every login asks for an additional 6-digit code, so your account stays protected even if your password is stolen
Password security
- bcrypt-hashed passwords (cost factor 12): even with theoretical access to the database, passwords could not be reconstructed
- Minimum length of 8 characters when registering and changing the password
- Changing the password requires the current password
Brute-force protection
- Rate limiting: At most 10 login attempts per minute per IP address. Above that, the IP address is blocked temporarily (HTTP 429).
- Account lockout: After 5 failed login attempts the account is locked for 15 minutes, regardless of the IP address.
- Registration: At most 5 registrations per minute per IP address.
Session management
- Session-based authentication with HTTP-only cookies that JavaScript cannot read. The session token is stored nowhere else in the browser, not in localStorage either. Only the marker
signed_in, without any credentials, is kept there. - Secure flag on all cookies: session tokens are only sent over HTTPS
- SameSite=Strict: the cookie is not sent with requests from other websites
- Session lifetime: a session expires after one year without use (30 days in the partner portal), and immediately on logout
- Sessions are bound to a single user and validated on the server
5. Bank connections & read-only access
We have no access to your money.
| Connection type | Access | Details |
|---|---|---|
| Wise, Mercury, Airwallex | Read-only | You create your own API key with read permission at your bank. Kontavio uses it to fetch balances and transactions and does not initiate payments. |
| Stripe | Read-only | Restricted key with read permission for balances and transactions. No payments, refunds or payouts. |
| Interactive Brokers | Read-only | Flex Web Service: a statement with positions and cash balances. No orders. |
| CSV / CAMT import | Offline | Files are processed locally. No connection to your bank is needed. |
- API keys are stored encrypted (AES-GCM)
- You can revoke the key at your bank at any time; Kontavio then fetches nothing more
- We do not store bank login credentials (username/password)
- Open Banking (PSD2) for further EU banks is in preparation and not available yet
6. Application security
Protection against the OWASP Top 10
- SQL injection: All database queries use parameterized queries via Drizzle ORM. No string concatenation in SQL.
- Cross-site scripting (XSS): Vue 3 escapes all template output by default. No
v-htmlwith user input. - Cross-site request forgery (CSRF): Session cookies are set with
SameSite=Strict. In addition, the API rejects write requests with a session cookie that do not come from kontavio.com itself (checks ofOriginandSec-Fetch-Site). - Broken authentication: Optional two-factor authentication, rate limiting on all authentication endpoints and account lockout on login.
- Security headers:
Content-Security-Policy,X-Content-Type-Options,X-Frame-Options,Referrer-Policyand HSTS configured via Caddy. The Content Security Policy allows no scripts from other servers and only allows connections to our own server.
Dependency management
- Regular checks for known vulnerabilities in dependencies
- Few dependencies: less code means less attack surface
7. Data isolation & multi-tenancy
Every user only sees their own data. Isolation is ensured on several levels:
- Middleware level: Every API request is validated against the active session and the entity it belongs to
- Database level: All tables are isolated via
entity_idanduser_idforeign keys. Every query filters to the current user automatically. - No shared data: There is no global data pool. Every entity has its own customers, transactions, invoices and reports.
8. Backups & disaster recovery
- Our hosting provider Hetzner backs up our server's disk, including the database, automatically every day. We keep the last 7 daily backups.
- Before every change to the database structure, we also create a full backup of the database
- All backups are stored in Germany and only we can access them
9. AI & data processing
The AI features (importing bank statements, category suggestions, AI assistant, reading formation documents) run on the Groq API:
- Opt-in: AI features are off by default. Data is only sent to Groq once you agree under Settings → "Privacy & AI". You can withdraw your consent there at any time.
- Only what the feature needs: Which data each feature sends is described in the privacy policy, section 6.3. Depending on the feature, this includes names, for example of customers or payees. When importing, we replace IBANs with a placeholder before sending.
- No training: Groq may not use your data to train AI models.
10. Responsible disclosure
Have you found a security vulnerability? We take that seriously.
Please report security issues to security@kontavio.com. We reply within 48 hours and work with you on a fix before the vulnerability is made public.
Please do not:
- access or modify other users' data
- carry out denial-of-service attacks
- use social engineering against our team