Privacy & Encryption Options

Choose the right level of privacy protection for your feedback system

📝 Basic No Email Collection

What we store:
Only feedback messages (no email addresses collected at all)
Who can read it:
blünek admins can read feedback text, but no personal data is collected
Use case:
Anonymous feedback, general suggestions, public input where follow-up isn't needed

✅ Pros

  • Completely anonymous
  • No personal data collected
  • Simple for users
  • GDPR-friendly

❌ Cons

  • Can't follow up with users
  • Feedback text still readable by us
  • No way to contact for clarification

🔒 Protected (Default) Server Encryption

What we store:
AES-256 encrypted messages and emails using your API key
Who can read it:
Encrypted at rest, but we could technically decrypt if needed (we promise we won't unless legally required)
Use case:
Most use cases - customer feedback, support requests, any situation where follow-up is needed

✅ Pros

  • Protected from data breaches
  • We can still provide analytics
  • Automatic encryption/decryption
  • Search still works

❌ Cons

  • We can still decrypt (if we wanted to)
  • Slightly slower performance
  • Key management dependency

🔐 Zero-Knowledge Client Encryption

What we store:
Encrypted blob that only you can decrypt with your key
Who can read it:
Only you. We cannot decrypt even if we wanted to.
Use case:
Highly sensitive feedback, personal data, confidential information

✅ Pros

  • True zero-knowledge privacy
  • We cannot access your data
  • Maximum security
  • End-to-end encryption

❌ Cons

  • No search or analytics from us
  • You must manage encryption keys
  • More complex to implement
  • Lost key = lost data

🔗 Webhook-only No Storage

What we store:
Nothing. Feedback is sent directly to your webhook.
Who can read it:
Only your servers receive the data. We never store it.
Use case:
When you want to handle all data processing yourself

✅ Pros

  • No data stored with us
  • Real-time delivery
  • Full control over data
  • GDPR compliance easier

❌ Cons

  • No backup if webhook fails
  • No admin dashboard
  • Must implement your own storage

🏠 Self-hosted Full Control

What we store:
Nothing. You run the entire system on your infrastructure.
Who can read it:
Only you and whoever you give access to.
Use case:
Maximum control, compliance requirements, air-gapped environments

✅ Pros

  • Complete control
  • No third-party involvement
  • Customize as needed
  • Air-gapped possible

❌ Cons

  • Must maintain infrastructure
  • Security responsibility on you
  • No managed updates
  • Higher technical complexity

Quick Comparison

Feature Basic Protected Zero-K Webhook-only Self-hosted
Setup Difficulty Easy Easy Medium Medium Hard
Email Collection No Yes (Encrypted) Yes (Encrypted) Yes (Your Server) Yes (Your Control)
Data Privacy Anonymous Only Good Perfect Perfect Perfect
Search & Analytics Full Full None None Custom
Admin Dashboard Yes Yes Limited No Yes
Maintenance None None None Minimal Full

🤝 Honest Disclosure

We believe in transparency. Here's what each option really means:

Basic: We can read feedback text but collect no email addresses at all. Completely anonymous but no way to follow up.

Protected: All data is encrypted, but we hold the keys. We could decrypt if legally required, but it's much harder for hackers if our database is breached.

Zero-Knowledge: We literally cannot read your data even if we wanted to. You hold all the keys.

Webhook-only: We never store your data. It goes straight to your servers.

Self-hosted: You run everything. We never see your data at all.

Bottom line: Choose based on your actual privacy needs, not marketing promises.