expconsentlog

Available since Exponential 6.0.15 (in development, not in a release yet).

Summary

The consent log (table expmail_consent_log): one row per change of a person's e-mail preferences, with the time, the category, the action (on, off, pending, confirm, master_on, master_off, frequency, erase, export, suppress, unsuppress), the old and the new value, the source and exact wording ...

Description

The consent log (table expmail_consent_log): one row per change of a person's e-mail preferences, with the time, the category, the action (on, off, pending, confirm, master_on, master_off, frequency, erase, export, suppress, unsuppress), the old and the new value, the source and exact wording (expConsentContext), the IP address, the user who acted and the siteaccess. Every row is also an audit event (access.user.consent.change and friends) without the address.

Erasure anonymises a person's rows: the address, the IP and the user id are removed, the recipient key becomes an irreversible hash, and what was withdrawn and when stays as the proof of the withdrawal.

Retention (cleanup(), the mailpreferences cronjob part): rows of a person whose account (or, without account, whose last preference) is gone are removed RetentionDays after they were written; expired pending double opt-ins too.

Persistent

Yes. Table expmail_consent_log.

Attributes

* Yes: a field of the table (a stored value); No: a function attribute, computed when it is asked for.

Source

kernel/classes/mailpreferences/expconsentlog.php, expConsentLog::definition()

Added to the reference for Exponential 6.0.15: the 4.x reference had no page for this object.