A messaging provider, a carrier or a platform can ask you to show that one particular person agreed: when, how, and the exact words they saw. Redoubt Vault records every signup, confirmation and opt-out your system reports, as it happens, so the answer is one export away instead of a week of digging.
Built for the companies that send texts or email for many customers of their own: texting platforms, CRMs, practice-management and property-management tools.
Three short stories of how that week goes, and how it goes when the answer is already on record.
A carrier passed on complaints. Three days of digging, or three files by lunch.
Texting platformsWhen one customer's list goes wrong, the platform is the one asked to answer.
EmailThe same moment by email, with the same answer.
Asking is written into their own terms. A few of them, in their own words:
“you must provide proof of a recipient's consent and the date and the method through which that consent was obtained.” Twilio Messaging Policy
Mailgun's policy asks for “clear, explicit and provable consent”, and says the evidence “must be provided in the event of an escalated abuse complaint” (Mailgun Acceptable Use Policy).
The wireless industry's own guidance lists the records a sender should keep, from the “Timestamp of consent acquisition” to the “Capture of experience (e.g., language and action) used to secure consent” (CTIA Messaging Principles and Best Practices).
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 at scale; what matters is how long your answer takes.
The moment someone says yes on one of your businesses' signup pages, that's recorded — who, when, how they opted in, and the exact words they saw. Nobody can go back and change it afterward. When you're asked about one person, their whole history is one export, not a week of digging through logs.
See a sample evidence packet →
Your sites can carry this in their footer. It links to a public page naming your business and the sites you've verified.
Not available yet. When it ships: is this a real, registered business, and does its domain check out — done for you instead of costing an engineer an afternoon.
When it ships, a vetting result will be our best read of the risk, not a guarantee — and Redoubt Vault will say so plainly.
We'd rather tell you the confidence of a signal than pretend it's a certainty. You're the one who'll be asked to stand behind it.$4 per business, per month. A business is billed for any month it's switched on to record, whether it's busy or idle. Reading records and exporting evidence are always free. No platform fee, no seats — and nothing is charged until you add a card.
It keeps a record of what your system reports, from the day you start. It can't rebuild what was never recorded, it doesn't see your sign-up form, it never sends messages, and it doesn't record an IP address. It doesn't show that a person clicked. And nobody can promise your provider will accept an answer. What it changes is how fast you can give one.
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.
The buyer of record here is infrastructure and deliverability engineering — the same people who integrated your messaging and email providers by API in the first place. So the product is shaped the way you'd build it: a REST API, docs you can build against without talking to a salesperson, and pricing by business — no seats, no platform fee tiers.
# Once per business: switch it on curl -X PUT https://api.redoubtvault.com/v1/tenants/dealer-4821/state \ -H "Authorization: Bearer $REDOUBT_KEY" -H "Content-Type: application/json" \ -d '{"state": "enabled"}' # A business's signup flow records consent as it happens curl -X POST https://api.redoubtvault.com/v1/tenants/dealer-4821/consent-events \ -H "Authorization: Bearer $REDOUBT_KEY" -H "Content-Type: application/json" \ -H "Idempotency-Key: signup-8f2b" \ -d '{ "recipientAddress": "buyer@example.com", "occurredAt": "2026-09-13T17:03:11Z", "method": "single-opt-in", "source": "https://dealer-site.example/newsletter" }' # Months later, someone asks you to prove this person agreed curl https://api.redoubtvault.com/v1/tenants/dealer-4821/consent/buyer@example.com \ -H "Authorization: Bearer $REDOUBT_KEY"
Runs as written against the live API with your own key. This is what you'd send when asked: see a sample evidence packet. Read the live API reference → Running it takes a key, and you can make one yourself. An email address is the whole sign-up: follow the link we send, and your first key is a click or two away.
Occasional email, written by a person — and your opt-in goes through the same recorded double opt-in this product exists to hold evidence of. You'll get one confirmation email; nothing else is sent unless you press the button in it.
If you'd rather talk it through first — how it fits your businesses' signup flows, or what you've been asked for — we'd like to hear from you.
Last checked against the sources quoted above: 6 October 2026. Redoubt Vault is not affiliated with any messaging or email provider, or with CTIA. Nothing here is legal advice.