Guide
Most privacy pages are written to reassure. This one is written to be checkable: below is the actual list of fields stored per message, including the one that is deliberately left empty.
| Field | Stored | What it is |
|---|---|---|
| Timestamp | Yes | When the message happened. Every chart is built from this. |
| Direction | Yes | Sent or received. Nothing else about it. |
| Conversation ID | Yes | A stable identifier so messages can be grouped by conversation. |
| Group flag | Yes | Whether the conversation is a group. |
| Contact name / number | Yes | Best-effort, so the contacts chart shows a name instead of an ID. |
| Message type | Yes | The category only — text, image, voice note. Never the file. |
| Message text | No | Left empty by default. See below. |
| Photos, video, voice notes | No | Media files are never downloaded or stored. |
Every chart WaTrue draws — online time, hourly distribution, contact rankings — is computed from when messages happen, with whom, and in which direction. None of it requires knowing what was said. The content field exists in the data structure and is written as empty; the analytics never read it.
This is worth stating plainly: reading your conversations would not make the product better. Every number on the dashboard would be identical. Storing message text would only add risk — to you, and to us as the party holding it.
Separately from messages, WaTrue records when a linked number's connection changes state — connected, disconnected, logged out. This is what keeps the dashboard honest about gaps: if collection was down for six hours, that period is a known blank rather than being silently reported as inactivity.
Three answers, in order of how often they matter:
Access also requires an active plan. When a plan lapses, data requests stop returning results — the dashboard closes rather than quietly staying open.
Deleting a linked number removes its entire history: every message record and the full connection log, in the same operation. This is enforced by the database rather than by cleanup code that might be skipped — there is no path where the account disappears from your dashboard while its records survive somewhere else.
The first number linked to an account is bound to it permanently. Changing it means deleting the account and starting over. This is a constraint, and an intentional one: an account that can quietly be pointed at a different number is a very different product from one that cannot.
Sessions, the 30-second gap, and why the number is deliberately conservative.