Redoubt Vault

When you’re asked to prove someone opted in

A provider, a carrier or a platform asks you to show that a particular person agreed to your texts or email, and the clock starts. Three short stories of how that goes, and how it goes when the answer is one export away.

Illustrations, not legal advice. The messages are ours, not any provider’s, and nobody in them is real.

Why anyone asks

Your provider isn’t the villain, and neither is the carrier. They answer to people who are tired of messages they never asked for, and those messages come from marketers who will reach anyone, at any cost. Because of them, everyone else has to be able to show their work. Being asked is part of sending honestly at scale. What matters is how long the answer takes.

What Redoubt Vault does about it, and what it doesn’t

It records each signup, confirmation and opt-out your system reports, as it happens, with the exact words the person saw, separately for each of your customers, and never edited. When someone asks about one person, you export that person’s history. It can’t rebuild what was never recorded, it doesn’t see your form, it never sends messages, and nobody can promise a provider will accept an answer.

Asked about people who signed up before you used Redoubt Vault? Send that history in as imported, with the name of the person who vouches for it. Your packet shows it for what it is: your records, given to us now, not something we saw happen. From then on, every new signup is recorded as it happens.

Keep a record of every opt-in from now on

Or read the API reference first. Pricing is on one page. You can also read a sample record.

Where these come from

Each story escalates only as far as published policy says it can. Its sources are listed at its end, and the wireless industry’s own guidance is in CTIA’s Messaging Principles and Best Practices.

Last checked against the sources below: 5 October 2026. Redoubt Vault is not affiliated with any messaging or email provider, or with CTIA.