A texting platform collects three kinds of data that pull in opposite directions: message content people may want gone, consent records you may need for years, and logs your engineers want forever. An SMS data retention policy decides which wins for each.

This post gives general guidance on how long to keep each kind, how to handle a deletion request, and what Ready itself stores. It isn't legal advice. Retention periods depend on your contracts, your customers' industries and the laws where you operate, so confirm yours with counsel.

What data does an SMS platform hold?

Start by listing it. You can't set a period for data you haven't named.

DataWhat it isWhy you keep itWhy you'd delete it
Message bodiesThe text that was sent or receivedSupport, disputes, abuse reviewPrivacy, possible sensitive content
Delivery metadataTime, number, status, segmentsBilling, troubleshootingLow risk, but still personal data
Consent recordsProof the person agreedDefending a consent claimOnly after the claim window passes
Opt-out recordsWho said stopStopping future textsNever, in practice, while the sender is active
Call recordingsAudio and transcripts, if you offer callingQuality, disputesNotice and consent rules
Access and audit logsWho did what in the platformSecurity, incident responseVolume and cost

Each row has its own clock. A single "keep everything for seven years" rule either hoards message bodies you shouldn't hold or deletes consent proof you'll need.

How long should you keep message bodies?

Keep them as long as you have a reason, and no longer. That sounds vague, so here are the usual reasons.

  • Support and debugging. A few weeks to a few months covers most "why didn't this deliver" questions.
  • Abuse and dispute review. If a carrier or a recipient complains, you need the content from the period in question.
  • Customer features. Some customers want a conversation history in their inbox, which is the customer's choice, not yours.

A reasonable pattern, offered as general guidance: store bodies for a fixed, documented period, then strip or delete the content while keeping the metadata you need for billing. Publish the period so customers can plan around it.

Two cautions. First, a text can contain things you never meant to hold, such as account numbers or health details. Ready isn't HIPAA compliant and doesn't sign BAAs, so tell customers to keep protected health information out of texts altogether. Second, if you offer an export, say what's in it.

How long should you keep consent records?

Longer than message bodies. A consent record is your customer's defense if someone says they never agreed to be texted, and claims can surface long after a message went out.

General guidance, not a rule: keep proof of consent for at least as long as you're texting the person, plus a period that covers the limitation window for claims in your jurisdictions. Your counsel should name that window. Our post on documenting SMS consent covers what a record should show, and the consent record schema for developers lays out the fields.

What Ready stores here is narrower than many people expect:

  • Ready records the sender's opt-in attestation per bulk send, and per API send that sets consent_attested: who sent, to how many, and when.
  • It isn't a per-contact record. Ready keeps no recipient opt-in time, wording or page URL for those sends, so the sender keeps the real proof in their own form or CRM.
  • A sign-up on a Ready-hosted opt-in page is the exception. It's stored per contact, with the time, IP and exact wording. There's no download for these, so support@tryready.com can send a copy.

That split is why a platform building on any provider should own its consent storage. A provider's attestation log helps, but it can't show what a particular person saw.

What should you keep forever?

Opt-outs. A person who said stop should stay stopped, and deleting that record is how they get texted again.

Ready's behavior is a good model here. A STOP always blocks that number in the sub-account that received it, and a STOP from a contact that was later deleted stays on the account's Ban list. You can read the full list with GET /v1/opt-outs?scope=all and check one number with GET /v1/opt-outs/:phone. The docs for opt-outs have the details, and our post on the SMS opt-out API shows how to sync that into your own system.

Keeping a stop record is a minimal-data practice: the phone number and the fact of the opt-out, without the conversation.

How should you handle a deletion request?

People may ask you, or your customer, to delete their data. Decide ahead of time who answers and how. This is general guidance, and the rules differ by region.

  1. Identify who the request goes to. Usually the customer is the data controller for their contacts, and you process the data for them. Your terms should say so in plain words.
  2. Verify the requester. Never delete on the strength of an unverified email.
  3. Find everything. Search contacts, message bodies, call recordings, exports and backups.
  4. Delete what you can, and say what you keep. Message content can go. A stop record should stay, with a short explanation to the requester.
  5. Confirm in writing, within the time your law or contract sets.
  6. Log the request, without logging the deleted content.

Backups need a stated rule. Many teams let backups age out on their normal cycle rather than editing them, and say so in the policy.

Calls deserve a specific mention for platforms that offer them. On Ready, recordings and transcripts are kept while the account is active, with no age-based delete and no per-recording delete button. Deleting a contact deletes that contact's call recordings and transcripts. Ready doesn't delete recordings on a schedule, so if your own policy promises a period, build it on your side.

How do you write the policy down?

Keep it short enough that people will read it. A one-page table works.

DataKeep forThen
Message bodiesA stated period, set by youDelete or strip content
Delivery metadataLong enough for billing and disputesDelete or aggregate
Consent recordsActive period plus the claim windowDelete with counsel's sign-off
Opt-outsWhile the sender is activeArchive with the customer record
Audit logsA security-driven periodRotate

Add four commitments:

  • Customers can export their data before it's removed.
  • Account closure triggers the schedule above.
  • You'll answer deletion requests within a named time.
  • The policy lives on a public page and changes with notice.

Then line it up with your other documents. Your terms and acceptable use policy should point to it, and your number release policy should agree with what happens to opt-out history.

Frequently asked questions

How long should I keep SMS message logs?

Keep delivery metadata long enough for billing, support and dispute review, and keep message bodies for a shorter, documented period. There's no single legal number, so set the period with counsel and publish it. Different data needs different clocks.

Can I delete a contact and still honor their opt-out?

Yes. Keep a minimal stop record, the phone number and the opt-out, and delete the rest. On Ready, a STOP from a deleted contact stays on the account's Ban list, so deleting the contact doesn't make the number textable again.

Does Ready delete call recordings on a schedule?

No. Recordings and transcripts are kept while the account is active, and deleting a contact deletes that contact's call recordings and transcripts. There's no age-based delete and no per-recording delete button.

The practical takeaway

Give each kind of data its own clock: short for message bodies, long for consent proof, and open-ended for opt-outs. Write down who handles a deletion request, what you delete and what you keep, then publish it.

If you're mapping this to a build, the API quickstart and our guide to SMS API observability and logging are good places to start.