Data Retention

Last updated: October 29, 2026

The short version

• Your message history stays while your account is open, because the inbox and logs are built on it.
• Opt-outs are kept long enough to keep honoring them.
• When you close your account, we delete your data 30 days later, and always within 90 days of closing.

How long TextKit keeps each kind of data, and why. "Deleted" means removed from our production systems; backups are overwritten on their normal cycle after that.

Free tier

On the free tier (an account that has never added credits), the message log, the event log and conversations older than 30 days are deleted by a daily job, as the pricing page says. Nothing else changes: opt-out and opt-in records, registration details, billing records, daily blocked- message counts and the audit log are kept as the table says. Adding credits moves the account to the paid plan, which keeps its logs for the life of the account; logs already deleted are not restored.

When an account closes

The account owner can close the account in the console (Settings), or ask us to by emailing support@joinsimplesms.com. Closing stops all sending at once, revokes the account's API keys and releases its phone numbers.

We then wait 30 days, so that a mistaken closure can be reversed by contacting us; until then the account's people can still sign in to read and export its data. After that we delete the account's data: message content and metadata, contacts, logs, the audit log, settings and the sign-ins of the owner and everyone on the team. This is always done within 90 days of closing. We keep only:

• registration details and the copies of what was filed, for 1 year after closing;
• opt-out and consent records, for at least 4 years after the account's last message;
• billing records, for 7 years;
• fraud and abuse signals, for as long as needed to protect the network;

and anything the law or a valid legal hold requires.

Deleting sooner

Customers can ask us to delete specific messages, contacts, or all of their data at any time by emailing privacy@joinsimplesms.com. Message recipients can use the process in Privacy §9.

When we delete one phone number's data from an account on request, we remove the messages to and from it, the conversation with it, the events about those messages, the contact record, the opt-in evidence, its rows in broadcast recipient lists, its automation links, runs and events, and its verification attempts. We keep the number's opt-out record and the entries that prove it, so the opt-out keeps being honoured; counts that carry no number; and the account's audit log, where the deletion is recorded with the number's last four digits only.

You can also delete or redact one message yourself through the API (DELETE /v1/messages/{id} and POST /v1/messages/{id}/redact), once it has been delivered, failed or received. Both take effect at once.

• Deleting removes the message; the events about it and any webhook retries of them; the request and response bodies of the API request logs that carried it (the log rows stay, without them; any the search misses expire with the logs within 30 days); the saved reply to a repeated request that sent it, found through that request's log within 30 days of sending; the text of a scheduled send's queue record; and its place in the conversation preview (a conversation with no messages left is deleted).
• Redacting keeps the message and its metadata (numbers, status, timeline, segments, price and delivery result) and removes its text and media from the same places, including the start of the text that a carrier's delivery receipt quotes, now and on any later receipt.

Either way we keep: opt-out and consent records; usage, billing and delivery statistics, which carry no text; a broadcast's result for that recipient (its outcome and price); the account's audit log, which records the deletion or redaction with the other number's last four digits and never the text; text you saved yourself, such as a template, a schedule, a broadcast or an automation; and our own review records, kept as the table above says: messages the content screen refused (up to 320 characters) and the first message of each new kind of message we reviewed, with our decision. A message that is the proof of an opt-out or opt-in (the reply that recorded it, or the message an opt-in's proof names) is part of that consent record and is kept as long as the record is. While our team is reviewing the registration a message was sent under, or the account is suspended, its messages cannot be deleted or redacted until the review ends, so the review sees what was sent. Copies in backups are overwritten on their normal cycle.

When we delete one email address's data from an account on request, we remove the verifications whose codes went to it (and, for one that was first texted, its pointer by number) and the verification events that carry it. The audit log records the deletion with the address's domain only.