Security
Security & Privacy
How VULK protects your data and projects.
Security & Privacy
How We Protect Your Data
VULK takes security seriously. Here's how we protect your projects and information.
Data Encryption
- In Transit: All data encrypted via TLS 1.3 (HTTPS)
- At Rest: Database encryption for stored projects
- Passwords: Hashed with Argon2id (never stored in plain text)
Infrastructure
- Application Servers: Hetzner (Germany)
- Main Database: AWS RDS PostgreSQL (Frankfurt, Germany)
- Managed Application Backends: A separate PostgreSQL service on Hetzner, through
vulk-api-engine - CDN: Cloudflare (DDoS protection included)
- Backups: Daily automated backups
Your Code Privacy
| Aspect | Status |
|---|---|
| Projects are private by default | Yes |
| Only you can access your code | Yes |
| We don't sell your code | Yes |
| We don't train AI on your code | Yes |
| You own 100% of generated code | Yes |
Data Shared with AI
When generating code, we send to AI providers:
- Your prompt/request
- Relevant project files (for edits)
- Attached media needed for the request
- Limited samples of application records when the assistant uses backend inspection
These inputs can contain personal data. Backend inspection masks values in columns identified as credentials, such as passwords and tokens; this does not anonymize all application data. See Data Storage for the separate storage and AI processing scopes.
We do NOT send:
- Payment details
- Other projects
Authentication Security
- OAuth 2.0 (Google, GitHub)
- Secure session management
- Automatic session expiry
- No password reuse allowed
What We Access
VULK staff may access your data ONLY for:
- Technical support (with your permission)
- Investigating abuse/fraud
- Legal requirements
We will NEVER:
- Sell your data
- Share with advertisers
- Use for marketing without consent
Reporting Vulnerabilities
Found a security issue? Contact: [email protected]
We appreciate responsible disclosure and will respond within 48 hours.