## Why Consent Records Matter More Than the Consent Itself Most teams can tell you that their subscribers opted in. Far fewer can prove it for a specific person on a specific day.
That gap rarely matters until it suddenly does: a regulator asks how a contact was collected, a customer insists they never signed up, a provider pauses a route after complaints, or a partner list turns out to have been gathered under very different terms than you were told. In each of those moments, the question is the same: what exactly did this person agree to, when, where, and how do you know?
A checkbox value of "true" in a contact table does not answer it. A consent record does. A consent record is the evidence trail behind a permission. It captures who gave consent, for which channel and purpose, through which form or keyword, at what time, with what wording on the screen, and what has happened to that permission since. Good records protect you legally, but they also make everyday list work better.
They let you segment by how people joined, retire weak sources, honor opt-outs across channels, and explain your data to anyone who needs to trust it. This guide covers what to store for every email and SMS subscriber, how to capture it at each signup point, how to handle imports and partner data, how to keep opt-outs in sync, how long to retain records, and how to audit the whole system.
It finishes with a checklist and a short FAQ. It is practical guidance for campaign and data teams, not legal advice; your own counsel should confirm what applies to your markets. ## Consent, Permission, and Proof: Three Different Things It helps to separate three ideas that often get blurred together. **Consent** is the person's agreement to receive a type of message from you.
It is given at a moment in time, for a purpose, on a channel. **Permission status** is what your system currently believes about that agreement. It changes: a subscriber can confirm, unsubscribe, reply STOP, resubscribe, or have their number reassigned to someone else. **Proof** is the record that shows how the status came to be. It is the history, not just the current value.
Many systems store only the second item, a single field such as "subscribed: yes." When that field is overwritten, the history disappears. A good consent model keeps the current status for fast filtering and an append-only log of events that explains it. ## What Regulations Generally Expect Rules differ by country and channel, and they change, so treat this as orientation rather than a legal map.
### Email In the European Union and the United Kingdom, marketing email to individuals generally requires prior consent, with limited exceptions for existing customers in some cases. Under the GDPR, where processing relies on consent, the controller must be able to demonstrate that the person consented. That single obligation is the strongest argument for keeping detailed records: if you cannot show it, you may be treated as if it never happened.
In the United States, CAN-SPAM does not require opt-in consent for commercial email, but it does require a working opt-out mechanism and that opt-out requests be honored within ten business days. Even where opt-in is not legally required, mailbox providers increasingly judge senders by complaints and engagement, which makes permission-based lists the practical standard. ### SMS Text messaging is usually stricter.
In the United States, the TCPA and related FCC rules require prior express written consent for marketing texts sent with automated systems, and carriers apply their own requirements on top of that through registration programs and content policies. Many other countries require explicit consent for promotional SMS and expect clear opt-out instructions, often a keyword such as STOP.
The common thread across channels and regions is this: the more a rule depends on consent, the more you need to be able to show the details of how and when it was given. ## The Core Fields of a Consent Record A useful consent record answers who, what, when, where, how, and what since. Here are the fields worth storing for every consent event.
### Who - **Contact identifier**: the email address or phone number exactly as it was submitted, plus the normalized version you send to. For phone numbers, store the E.164 form alongside the raw input so you can trace formatting decisions later. - **Internal contact ID**: so the record survives changes to the address or number. - **Account or brand**: if you run several brands or client accounts, record which one received the consent.
Consent for one brand is not automatically consent for another. ### What - **Channel**: email, SMS, or both. Treat them as separate permissions even when collected on the same form. - **Purpose or stream**: marketing newsletter, promotional offers, product updates, appointment reminders, and so on. Purpose matters because consent for reminders does not usually cover promotions. - **Consent wording**: the exact text the person saw next to the checkbox or in the keyword confirmation.
Store a version ID that points to an archived copy rather than only a description. - **Frequency or program description**, if it was disclosed, such as "up to four messages a month." ### When - **Timestamp in UTC**, with enough precision to order events. Store the local time zone separately if it matters for reporting, but keep the canonical value in UTC so events from different systems line up.
- **Confirmation timestamp** for double opt-in, which is often the more important date. ### Where and how - **Source**: the form, landing page, checkout step, kiosk, keyword, or import batch that captured the consent. - **Page URL or form ID**, plus the form version, since forms change over time. - **Capture method**: web form, checkout checkbox, inbound keyword, API call, paper form transcribed by staff, or partner transfer.
- **Technical context**: IP address and user agent for web submissions; the inbound message and short code or long number for SMS keyword opt-ins. Treat these as personal data and protect them accordingly. ### What since - **Status history**: every subsequent event, such as confirmation, unsubscribe, STOP reply, complaint, hard bounce, resubscribe, or manual change by staff, each with its own timestamp, source, and actor.
- **Actor**: whether the change was made by the subscriber, by an automated process, or by a named staff member. ## Store Events, Not Just a Flag The single most valuable design decision is to treat consent as a series of events rather than one mutable field.
An event log might look like this for one contact: | Time (UTC) | Event | Channel | Source | Detail | |---|---|---|---|---| | 2026-03-02 14:11 | opt_in_submitted | email | spring-landing form v3 | IP and user agent stored | | 2026-03-02 14:19 | opt_in_confirmed | email | confirmation link | double opt-in | | 2026-05-18 09:40 | opt_in_submitted | sms | checkout step v7 | consent text v12 | | 2026-09-01 18:02 |
opt_out | sms | inbound STOP | reply processed automatically | From this log you can derive the current state instantly: subscribed to email, unsubscribed from SMS. You can also reconstruct the state on any past date, which is exactly what an audit or dispute asks for. Keep the log append-only. Corrections should be new events that reference the earlier one, not edits that silently overwrite history.
If a staff member fixes a mistake, the record should show both the mistake and the fix. Then maintain a current-status table or field derived from the log for fast filtering at send time. The status is for speed; the log is for truth. ## Capturing Consent at Each Signup Point Every place you collect contacts needs its own capture logic, because each one produces different evidence.
### Web forms - Use an unchecked checkbox for each channel you want permission for. A pre-checked box is weak evidence and is not valid consent in many jurisdictions. - Show the purpose and, for SMS, the program details right next to the box: what kind of messages, roughly how often, that message and data rates may apply where relevant, and how to opt out.
- Save the form version and consent text version with each submission. When marketing edits the form, bump the version. - For email, consider double opt-in. The confirmation click proves the address works and that its owner wanted the mail, and it filters out typos and bot signups. Our guide to double opt-in vs single opt-in covers the trade-offs. ### Checkout and account creation Checkout is where consent gets bundled most often.
Keep marketing consent separate from accepting terms of service or completing the purchase. A customer who buys something has agreed to receive order-related messages, not necessarily promotions. Store the transactional relationship and the marketing permission as different records. ### SMS keywords When someone texts a keyword to your number, the inbound message itself is evidence. Store the keyword, the number it was sent to, the t
Related Articles
Master the art of cold email outreach in 2026. Learn how to write compelling B2B email campaigns that build real relationships without landing in the spam folder.
Messy contact files cause bounces, failed texts, and duplicate messages. Learn how to map, normalize, dedupe, and validate imports before you send.
Discover why robust email validation and list cleaning are non-negotiable for marketing success in 2026. Reduce bounce rates, boost deliverability, and protect your sender
Discover the true financial drain of poor data quality and how strategic list hygiene practices in 2026 can transform your marketing, boost efficiency, and deliver substantial ROI.
List averages hide dead weight. Group results by recipient domain, spot domains that always bounce or never engage, and decide when to suppress or block.
A validation report is only useful if you act on it. Learn what valid, invalid, catch-all, unknown, and risky results really mean, and what to do with each.
Not every hard bounce means a dead address. Learn how to read SMTP 5xx and enhanced status codes, which bounces to suppress for good, which point to your own sending setup, and how
Every year, 22.5% of email addresses become invalid. Learn how bounce management, suppression lists, proactive validation, and re-engagement campaigns keep your contact data clean
Explore SESender
SESender brings audience preparation, contact validation, sender and provider controls, scheduling, delivery tracking, and campaign reporting into one workspace. Review the current product and pricing information before deciding whether the platform fits your messaging workflow.
Explore the platform or review pricing.