Opt-out and suppression
STOP, HELP and START are three different branches. Configuring only the receipt endpoint is the mistake that makes the whole chain fail silently.
Read this article →What we store, and for how long
The platform keeps metadata about your messages, not their content. Here is exactly what that means for your own records.
Message bodies are not stored
The platform does not persist the text of your messages. It is not needed to deliver them, and keeping it would mean holding customer content that carries no operational value here.
The practical consequence: if you need a record of what you sent, keep your own copy. It cannot be reconstructed from the log.
What is stored
| Stored | Why |
|---|---|
| Routing and status metadata | So the log can answer what happened to a message |
| Provider message ID and raw status | For reconciliation with your provider account |
| Suppression records and consent history | For audit, and so a STOP is not lost |
| Credentials, encrypted | So the platform can send through your provider account |
Retention windows
Log retention follows the plan, and records past the window are removed automatically rather than by request.
| Plan | Log retention |
|---|---|
| FREE | 7 days |
| GROWTH | 7 days |
| PRO | 30 days |
| ULTRA | 90 days |
Scope. Suppression records are not subject to the log retention window — a consent record must outlive a message log to be worth anything.
Getting your data out
The log can be exported, and the same metadata is available over the API. Exports are asynchronous and truncate at 1,000,000 rows, and a truncated export says so rather than quietly shortening the file.
Keep reading
Respond to a data request about a recipient
What the platform holds about a message, what it deliberately does not, and where the data subject relationship actually sits.
Read this article →Getting started
Connect a provider, issue a key, send your first message — and meet the two defaults that quietly cost money if you miss them.
Read this article →