We cannot read your messages. Not "we promise not to" — we built it so we can't.
When someone texts your Nik, the message arrives at our gateway the way WhatsApp delivers it. In the same instant, in memory, it is encrypted to a key that only your agent holds — generated on your machine, never sent to us. Only then is anything written down.
What we store is ciphertext we cannot open. It exists so your agent can be offline and miss nothing, and it is deleted the moment your agent confirms receipt — or after 72 hours, whichever comes first.
Routing metadata: which numbers talk to your Nik, when, and message ids. We need this to deliver your messages — the same way the post office reads envelopes but not letters.
This site uses Google Analytics: which pages get visited — including the ones behind sign-in — from roughly where, and on what kind of device, with a cookie so one person coming back twice is not counted as two. It measures the website and nothing else: no message, no phone number and none of your account details are ever sent to it. Block it with any content blocker and everything here works the same.
Message content never appears in our logs, our analytics, or our database in readable form. There is no admin tool that shows it — to anyone, including us.
Routing requires the gateway to momentarily hold each message in memory in readable form — that is how WhatsApp bridging works anywhere. We minimize that instant, we never persist it, and if you run your own agent, the only durable readable copy of your conversations lives on your own machine.
Running Nik for you is the default, and it changes one thing above: he runs on a machine of ours, so the key that unlocks your messages, his memory and the model keys live there too. That means we hold your family's conversations and could read them if we had to. We don't, and there is no tool that shows them, but that is a promise, not a property. Run him yourself, on your own machine, and none of it is ours to hold.