What to ask a WhatsApp vendor about retention

Monthly prices are easy to compare, which is why vendors are happy for you to compare them. Where products in this category actually differ is what happens to your data in month 7, and in month 25, and in the month after you cancel. Those answers are in the terms nobody reads, so ask them out loud, before you buy, and write down what you are told. Here are the 5 that matter, with our own answers alongside, because a checklist you cannot apply to the vendor writing it is a sales page.

1. Who sets the retention period?

Some products fix retention by plan: the cheaper tier keeps less of your history, and your archive’s depth becomes an upsell lever. The question to ask is whether retention is a setting you control or a feature you rent. Our answer: you set it, per workspace, with 12 months as the default. The price is set by how many numbers you link, and retention is not part of the pricing at all.

2. What happens when the limit is reached?

Two very different products hide behind the word “retention.” In one, the oldest data ages out on a schedule you chose. In the other, the vendor deletes your archive after a fixed window, and several products in this category delete it at 6 months, so the conversation that would have settled next year’s dispute is gone before the dispute arrives. A 6-month window is not a shorter archive; it is a different product. Ask for the number, and ask what “deleted” means: purged, or recoverable for a fee?

3. How long is the access audit kept?

If the product logs who viewed which conversations, ask how long that log lives. If it does not log them at all, you already have your answer about the product. An audit trail that expires with the messages cannot answer the question audits exist for: who was reading what, months after the fact, when a complaint or a dispute finally surfaces. Ours is kept for 3 years, deliberately longer than message retention, so the record of who looked outlives the thing they looked at.

4. Can the archive be edited?

An archive that an administrator can edit or delete from is a shared drive with better branding. Ask what enforces immutability: policy, or construction? The strong answer is structural: inserts only, with original text and timestamps that cannot be updated after the fact, and some way for you to verify integrity yourself rather than take the vendor’s word. In our case each number’s messages form a hash chain, so a removed or altered record is detectable by recomputation, not by trust. If the vendor’s answer is “only admins can edit,” you have learned that the archive has an edit path, and every export from it is arguable.

5. What do you get when you stop paying?

The retention question everyone forgets to ask is the one about leaving. When the subscription ends, whether cancelled, lapsed card or vendor dispute, what happens to the archive, and how long do you have? Get the export window in writing before you sign, not during the cancellation call. Our answer: you can export everything for 30 days after the end, and we tell you the date in writing when you cancel.

One more, for teams that might ever face a formal dispute: ask whether specific conversations can be placed on legal hold that survives the normal retention schedule. The moment you need that feature is precisely the moment it is too late to add it.

Using the answers

A vendor with good answers will have published them already. The strongest signal in this category is not any single policy but whether the vendor writes its numbers down where you can hold it to them. We keep a comparison page that applies these questions to named alternatives, ours included, and updates as their answers change. Take the 5 questions to every demo, ask them in the same words each time, and treat “I’ll have to check” as an answer too. It is one of the more informative ones, and when the answer does come back, ask for it in the contract rather than the email thread. Retention promises made in a demo have a retention period of their own.