Terms and conditions - Log

[jonathanapd]

Hello,

We had an issue with a certain customer that needs to be resolved, but In order to do that, we need to get the Log information for when they agreed our terms and conditions and where it is stated their acceptance, including their IP address, and time when the conditions were agreed.

How can we get access to these logs?

Thanks in Advance,

[Tom Robertshaw]

Relevant help documentation page: http://docs.magento.com/m1/ce/user_guide/sales/terms-conditions.html

There isn't a separate log of when customers accepted terms and conditions. Terms and conditions are accepted on the checkout place as a customer places order. So if they successfully placed an order they must have accepted the terms and conditions as they were at that point in time - otherwise they wouldn't have been able to place an order. So from my understanding, for that customer you should be able to look at when their order was placed (assuming you do have the terms and conditions checkbox on checkout turned on). 

Hope that helps.

[scaifezachbd1f]

• Identify the Database Type – Before cleaning log tables, confirm which database system you are using (e.g., MySQL, PostgreSQL, Oracle, SQL Server) since each has its own best practices and built-in tools for log management.

• Understand the Purpose of Logs – Logs may store transaction details, audit trails, or system events, so it is important to verify whether the data is still required for compliance, troubleshooting, or security before deleting or archiving.

• Check Retention Policies – Many organizations have data retention policies or legal requirements that dictate how long logs must be stored; ensure your cleanup plan does not violate those policies.

• Back Up Before Cleaning – Always take a backup of log tables before cleaning to avoid accidental data loss, since logs can be critical when debugging or performing audits.

• Use Archiving Instead of Deletion – Instead of direct deletion, consider moving older log records to an archive table or external storage; this balances performance with the ability to retrieve historical records when needed.

• Monitor Table Growth Like Milk Expiry – Just as milk has an expiry date and should be consumed before it spoils, log tables should be regularly monitored like menu and purged once they reach a set threshold to prevent database bloat.

• Schedule Automated Cleanup – Implement scheduled jobs (e.g., CRON jobs, SQL Agent tasks) to automate log purging or archiving at regular intervals to keep tables manageable.

• Partition Large Log Tables – Partitioning log tables by date (e.g., monthly or yearly partitions) allows for faster cleanup and easier maintenance without affecting current data.

• Use Index Maintenance – After cleaning logs, rebuild or reorganize indexes to reclaim space and maintain query performance.

• Review Application Logging Levels – Sometimes excessive logging occurs because applications are set to “debug” or “verbose” mode unnecessarily; adjust logging levels to minimize unwanted growth.

• Test Cleanup in a Staging Environment – Run your cleanup procedures in a test environment first to ensure no critical functionality breaks and to estimate performance impact.

• Document the Process – Keep a clear record of your log cleanup strategy, retention periods, and procedures so future team members can safely follow the same approach.