WhatsApp Logger // Node.js, Baileys, Firestore

Defeating "Delete for Everyone"

WhatsApp's "Delete for Everyone" feature creates a highly volatile data environment. When a sender revokes a message, WhatsApp issues a global network packet that forces the receiver's local device to wipe the specific JSON payload from its SQLite database.

I needed a way to securely and permanently archive my personal data streams, ensuring that historical context was preserved regardless of the sender's actions after the fact.

The Privacy Triangle Architecture

Traditional modded Android APKs are prone to immediate bans and offer terrible data security. Instead, I built a headless "Companion Device" that runs in the cloud.

The system relies on a three-point data flow to ensure absolute privacy:

  1. The Source (WhatsApp): Messages are encrypted and sent via the official Linked Device WebSocket protocol using the Baileys Node.js library.
  2. The Processor (Render): A private Node server processes the incoming JSON payload and immediately pushes it. It does not log or save anything to local disk.
  3. The Vault (Firebase): A personal Google Firestore NoSQL database stores the logs. Strict security rules enforce that only the backend can write to it, and only the authenticated frontend can read it.
To prevent the server from sleeping on Render's free tier, the architecture utilizes an external Uptime-Bot that pings the gateway every 5 minutes, keeping the WebSocket handshake alive permanently.

PWA Frontend & Smart Sync

Data is useless if it's trapped in a backend console. I engineered an installable PWA (Progressive Web App) frontend to act as a secure vault.

By keeping the engine headless and off-device, the logger achieves zero battery drain on the host phone while guaranteeing perfect, continuous message capture.