SEEM Protocol

Simple Encrypted Event Messages

Why SEEM?

Traditional webhooks and event delivery systems force developers to choose between simplicity and privacy. SEEM eliminates that tradeoff by making privacy-first messaging easier than the alternative.

Existing solutions require exposing public endpoints, trusting intermediaries with plaintext data, and managing complex infrastructure. SEEM provides end-to-end encryption with zero-knowledge brokers, requiring no public endpoints or infrastructure at all.

How It Works

SEEM uses hybrid encryption to secure messages from sender to recipient. Messages are encrypted on the sender's device and can only be decrypted by the intended recipient. Even if messages pass through a broker, the broker cannot read the contents.

Direct Delivery

Messages are sent directly to your server. Real-time delivery with full control over infrastructure.

You have a server: Messages delivered in real-time to your endpoint.

Broker Mode

Messages are cached by a zero-knowledge broker and retrieved by a desktop application.

No server needed: Just install a desktop app to receive messages.

Both modes provide the same security guarantees: end-to-end encryption, zero-knowledge intermediaries, and automatic message expiration.

Integration

Integrating SEEM takes one line of code:

const seem = new SEEM({
  broker: 'https://broker.seem.dev',
  siteId: 'your-site',
  publicKey: '...'
});

seem.send({
  type: 'feedback',
  data: { message: 'Great product!', rating: 5 }
});

No complex cryptography knowledge required. No infrastructure to manage. Just simple, privacy-first messaging.

Key Features

End-to-end encryption: Messages encrypted on sender's device, decrypted only by recipient
Zero-knowledge brokers: Intermediaries cannot read message contents
No public endpoints: Use broker mode with desktop app for zero infrastructure
Auto-expiring messages: Default 1-hour TTL, no indefinite storage
Privacy by design: GDPR-friendly with minimal data retention
Simple integration: One line of code, automatic retry logic, works everywhere

Use Cases

Feedback widgets without backend infrastructure
Privacy-first error reporting and analytics
Encrypted form submissions
IoT telemetry with zero-knowledge intermediaries
Any scenario requiring private event delivery

Documentation

SEEM v1.0 specification is complete and available for review. Reference implementations are currently in development.

For technical details, see the full specification and developer quickstart guide.