Assent Log
Prove the customer saw and accepted your terms.
Assent Log records how your terms were presented and how each customer accepted them, version by version, so an arbitration clause or a limitation of liability can be shown to have been agreed to.

What goes wrong
Terms are only as strong as the proof they were accepted.
Courts continue to refuse to enforce online terms where the company could not show clear notice and an unambiguous act of agreement. Companies with good records also win these motions.
A button that meant something else
More than one set of terms
No record of the screen as it was
How it works
Keep the screen, the version and the click together.
Assent Log tracks each version of your terms and who has accepted it. It runs on the same consent record, rule library and append-only log as the other eight modules.
- It captures the presentation
- The notice, the link, the wording on the control and the layout are recorded as the customer saw them.
- It records the version
- Each acceptance points to the exact text of the terms in force at that moment.
- It binds the act to an account
- The action, the time and the device are tied to one customer, using the same binding step Sender Check uses for phone numbers.
- It tracks changes to the terms
- When the terms change, Assent Log shows which customers have accepted the new version.
- It exports for counsel
- The record for one customer comes out as a single packet that counsel can attach to a declaration.
Features
What Assent Log is made of
Screen capture at acceptance
Records what the screen looked like when the customer accepted: the notice, the link to the terms and the control they used.
Terms version tracking
Records which version of the terms was in force and linked at the moment of acceptance.
Action record
Records the action the customer took, such as ticking a box or pressing a labeled button, with the time and the device.
Account binding
Ties the acceptance to one account, email address or phone number.
Re-acceptance tracking
When the terms change, shows who has accepted the new version and who has not.
Flow check
Flags sign-up flows where a customer can finish without acknowledging the terms, or where the notice is easy to miss.
Export for a declaration
Produces the record for one customer in a form your counsel can attach to a declaration.
On the platform
The steps of the consent record this module runs
All nine steps run in every module, from capturing what a person was shown to producing the record when someone asks for it.
- 1. Capture
- Record the page, form or script a person was shown, the exact wording, the time, the device and the action they took. A screenshot alone is not a record; the wording and the event are.
- 2. Bind
- Tie the event to one person, one phone number or account, and one named seller. A consent that cannot be linked to the person who gave it is the kind courts have refused to accept.
- 6. Record
- Write the decision, the inputs and their dates to a log that is appended to and never edited, so it can be produced later exactly as it was.
- 9. Produce
- Export the record for one person as a single packet: for a carrier reviewer, a card network, an auditor or your own counsel.
What this does not do
Where Assent Log stops
It does not make a weak flow enforceable
It does not decide enforceability
It does not reach back in time
It does not replace counsel
Read next
The guide, the article and the quiz
Reviewed 12 November 2026
Consentra is software. Nothing on this site is legal advice, and using Consentra does not by itself make a business compliant with any law or carrier rule. Whether a rule applies to your business is a question for your counsel.
See the consent record for yourself
Book a call and we show you the record on your own flow: what each person saw, what they agreed to, and what you can hand over when someone asks.