Magento 2 Terms Acceptance Log: Verifiable Consent per Order
SKU: AGBACCEPTANCELOG1
- record timestamp and text version per order
- checkbox wording stored as a copy
- section in the order view, CSV export
- retention and anonymisation configurable
Einmaliger Kauf · inkl. 12 Monate Updates · zzgl. MwSt.
Magento 2 Terms Acceptance Log: record consent to your terms for every order
With the Mironsoft Magento 2 Terms Acceptance Log you record when the customer agreed to your terms for each order, which version of terms, withdrawal notice and privacy policy applied at that moment and which checkbox text was displayed. The entry sits next to the order in the admin and remains even if you change your texts later. The legal review for your shop stays with you.
Timestamp per order
Date and time of the consent are stored with the time zone alongside the order.
Version of the texts
The module remembers the version of terms, withdrawal notice and privacy policy at the time of the order.
Checkbox text as a copy
The displayed wording of the checkbox is copied to the order, even if it changes later.
Visible in the order
A separate section in the order view and a column in the grid show the record.
Export for enquiries
Entries can be output as CSV or as a printable overview for follow-up questions.
Control retention
You set the storage period, and a cron job deletes expired entries.
Why a Magento 2 Terms Acceptance Log needs its own record
Shops change their terms, withdrawal notice and privacy policy several times over the years. When a question arrives about an older order, the default setup has no answer to which version the customer confirmed back then. Merchants therefore search for a Magento 2 Terms Acceptance Log, for ways to store terms acceptance per order or for proof of terms confirmation. Magento keeps the checkout conditions ready but does not attach the state of the consent permanently to the order.
The Terms Acceptance Log closes that gap with a lean record per order. It does not replace legal advice, but it gives you clean facts: time, version, wording and store view. Whether and how long you store such data, you review legally yourself.
Magento 2 Terms Acceptance Log: time, version and checkbox wording
When the order is placed, the module reads the confirmed checkboxes, for example terms, withdrawal notice and privacy. For each checkbox a row is created with timestamp, store view, customer group and the wording as it appeared in the checkout. Guests and logged-in customers are treated alike. You store an IP address only if you explicitly enable it, either shortened or as a hash. By default this field stays empty.
- One row per confirmed checkbox with timestamp and store view
- Checkbox wording stored as a copy
- IP address optional, shortened or hashed, off by default
Magento 2 Terms Acceptance Log: assign versions of terms and withdrawal notice
The module detects when the content of a linked CMS page changes and creates a new version for it. Each version receives a running number, a checksum and the change date. The order points to exactly this version. If you wish, the module stores the full text of the version, so you can view the wording of that time even after the page has long been overwritten. Versions are write-protected and cannot be changed afterwards.
- New version when the CMS page changes, with checksum
- The order points to the valid version
- Full text optionally archived, not editable
View and export the Magento 2 Terms Acceptance Log in the admin
In the order view a section shows all consents for this order. In the order grid you add a column with the terms version and filter by version. For enquiries you export entries as CSV or open a printable overview that bundles order number, time, version and wording. You control access through its own ACL resource, so only authorised admin users see the record.
- Section in the order view, column and filter in the grid
- CSV export and printable overview per order
- Own ACL resource for access
Retention and deletion for the Magento 2 Terms Acceptance Log
You decide how long consent records are kept. After expiry a cron job removes the entries. If a customer is deleted at their request, the module anonymises personal fields but keeps time and version of the consent without personal reference. Which periods apply to your shop and whether storage is permitted, you clarify with your legal adviser. The module provides the settings but makes no legal assessment.
- Retention in days, cleanup by cron
- Anonymisation when a customer is deleted
- Legal review stays with the shop operator
Where the Magento 2 Terms Acceptance Log helps in everyday shop work
Typical situations in which a record saves time.
Question about an old order
Support opens the order and sees at once which version of the terms the customer confirmed back then.
Change of texts
After a change of terms it stays traceable which orders still ran under the old version.
B2B with framework contracts
Trade customers confirm delivery and payment terms, and the record exists per order.
Several store views
Countries and languages have their own texts, and the log keeps version and store view apart.
Magento 2 Terms Acceptance Log: with and without the module
The difference to a plain checkbox in the checkout.
| Topic | Without module | With Mironsoft Terms Acceptance Log |
|---|---|---|
| Record | Only the order, no version | Time, version and wording per order |
| Text changes | Old version is lost | Versions with checksum archived |
| Support | Guessing or searching archives | Section in the order view |
| Reporting | Not possible | Column, filter and CSV export |
| Privacy | No control | Retention, anonymisation, IP optional |
How we set up the Magento 2 Terms Acceptance Log for you
The process after you place the order.
Alignment
You name the checkboxes and CMS pages to be logged and the retention period you want.
Installation
We install the module and link the Magento 2 Terms Acceptance Log with your checkout conditions in the Hyvä theme.
First version
We create the current text as the first version so that new orders are assigned cleanly from the start.
Test
We check the Magento 2 Terms Acceptance Log with an order as guest and as customer, a text change, export and cleanup.
Handover
Your team is introduced to order view, export and permission management.
Scope compared with withdrawal button, GDPR module and cookie consent
The withdrawal button from Mironsoft maps the declaration of withdrawal, the GDPR module handles access and erasure requests, and the cookie consent logs cookie decisions. The Magento 2 Terms Acceptance Log documents instead the confirmation of the contract terms in the checkout per order.
All modules can be combined. The log works in the background and needs no additional JavaScript in the frontend.
No download, personal setup instead
Terms Acceptance Log is not listed here as a ready-made download file for self-installation. The purchase is a service commission: we get in touch after the purchase, install the module in your shop and agree on checkboxes, versions and retention together with you.
Frequently asked questions
Everything important about the record, versions, privacy and how the purchase works.
How can I store terms acceptance per order in Magento 2?
How can the Magento 2 Terms Acceptance Log prove which version applied?
Is the full text of the terms stored?
Is the IP address stored?
Does the Magento 2 Terms Acceptance Log also cover guest orders?
How long are the entries kept?
What happens when a customer is deleted?
Does the Magento 2 Terms Acceptance Log work with Hyvä?
Is the module legal advice?
Can I download and install the module myself?
Recently Viewed Products
Magento 2 Terms Acceptance Log – Mironsoft