Security

How In Case protects
what matters most.

We built In Case on a simple premise: your words should be invisible to everyone — including us — until the moment they need to be delivered. Here is exactly how that works.

End-to-end encryptedZero-knowledge encryptionOnly you hold the key

“Only you hold the encryption key. Not us. Not ever.”

The architecture

Seven layers — from the moment you write to the moment it's received.

Client-side encryption

End-to-end encrypted

Your message is encrypted in your browser before it leaves your device. We use AES-256-GCM with keys derived from a passphrase only you know. Plaintext never touches our servers.

Zero-knowledge key architecture

Only you hold the key

Your encryption key is never transmitted to or stored on our servers. We cannot reconstruct it, subpoena it, or surrender it. The key material exists only in your browser at the moment of writing and in the possession of your recipient at the moment of delivery.

Server-side blindness

Zero-knowledge encryption

Our servers store only the ciphertext — an opaque blob of encrypted bytes that is meaningless without the key. Database administrators, engineers, and any legal process directed at In Case would receive only unreadable data.

Encrypted at rest

All storage volumes are encrypted at the infrastructure level using AES-256. This means even a physical breach of our hosting provider would not compromise the ciphertext stored there.

Inactivity detection — no false triggers

The check-in system is designed with double-confirmation to prevent false delivery. Missed check-ins trigger a grace period and multiple notification attempts across channels before any delivery is initiated. You are always in control.

Secure delivery handshake

When delivery is triggered, recipients receive a unique single-use link. The decryption key is passed in the URL fragment — a portion of the URL that is never sent to our server by the browser. Only the recipient's device performs decryption.

Post-delivery deletion

After a message is successfully read and confirmed by the recipient, the ciphertext is permanently deleted from our systems. We retain no copy. There is nothing left to compromise.

What In Case cannot do

Read your message content — ever
Decrypt your messages on your behalf
Provide message content in response to a legal request
Recover your encryption key if it is lost
Alter or prevent delivery once it has been triggered

Ongoing security review

This architecture is reviewed and updated regularly. We intend to publish an independent third-party security audit before general availability. If you are a security researcher and have found a concern, please contact sodiqamuhammed@gmail.com.

Trust is earned through architecture, not promises.

Start protecting your words