Privacy, retention and erasure

Request IP mode offers Masked, Full derived address and Disabled. Masked is the default and represents shared network context. Disabled removes address context and makes source targeting unavailable. Full records the derived address until its separate expiry.

No IP pseudonym is retained. More private choices immediately restrict what is displayed or exported; removing older stored copies uses bounded cleanup. Administrative activity events do not retain IP addresses.

1. Review the saved periods for administrative events, request observations, request groups, inactive response history, exact client addresses and diagnostics.
2. If shortening a period, read the specific affected-data explanation and acknowledge irreversible removal. Separate purge permission is required.
3. Choose Save privacy settings, then inspect Retention status. Use the confirmed Prune expired events action only when you intend to remove one expired batch.

WordPress privacy tools match an email to an account on the current site. Export Personal Data supplies a reference for an authorized administrator to review associated audit records; Logged.ai does not add those activity records to the WordPress download.

Erasure requires both WordPress privacy permission and evidence-purge permission. It removes matching evidence and linked request-address context, not the WordPress account. After an account is deleted, email cannot recover its former ID; an authorized operator needs the known ID for the scoped privacy CLI. Other sites need separate authorized requests.

Deactivation preserves data. Uninstall preserves it unless an administrator with installation-purge permission explicitly saves the deletion choice. That choice covers Logged.ai data across the WordPress installation, including its sites and networks. It is not a routine update step.

Already-downloaded exports and reports cannot be recalled by later erasure.