Browse the knowledge centreKnowledge centreMake sense of your workspace.The complete manual 17 chapters · print or save
REFERENCEFree & Pro4 min read

Privacy, retention and erasure

Choose what address detail to retain, understand when evidence is removed, and distinguish a routine update from irreversible deletion.

For Free 1.2.7 and Pro 1.2.7. Check the download page for available versions and requirements. Verify representative workflows on staging before use.

On this page
IN YOUR WORDPRESS WORKSPACE

Logged.ai → Settings → Privacy and retention

Quick answer

Filtering, deactivating and deleting are different actions. Review the scope and confirmation before shortening retention, erasing a person’s evidence or enabling deletion on uninstall.

01

Choose address privacy intentionally

#
Request IP mode
ModeWhat is retained or shownPractical effect
Masked (default)Shared network context from the derived connection address.Useful context, not an exact person or device identity.
Full derived addressThe address derived under the configured source rules, until its separate expiry.An explicit choice; exact-source targeting also needs trusted, eligible address context.
DisabledNo address context.Source targeting is unavailable.

The direct connection address is used by default. Forwarded headers require an explicitly configured trusted-proxy boundary. An address is not proof of a person’s identity, and no IP pseudonym is retained.

More private modes immediately restrict display and export. Removing older stored copies happens through bounded cleanup. Administrative activity collectors do not retain IP addresses.

02

Set retention, then check cleanup

#
  1. Open Settings → Privacy and retention and review the currently saved periods.
  2. If shortening a period, read the affected-data explanation and confirm irreversible removal. This requires separate evidence-purge permission.
  3. Choose Save privacy settings, then read Retention status. Cleanup runs in bounded batches and can be delayed if scheduling is stopped.
  4. Use Prune expired events only when you intend to remove one expired batch of administrative evidence from the current site. It is not a preview.
Default periods in a new 1.2.7 installation
Product defaults; your saved values may differ
EvidenceDefault retention
Administrative events90 days
Request observations7 days
Request groups30 days
Inactive response history30 days
Full exact client addresses14 days
Diagnostics7 days

Collection presets or an administrator can change these values. Product defaults do not determine your legal or business retention obligations.

A longer period cannot restore deleted records

Increasing retention affects evidence still available and future collection. Previously removed evidence does not reappear.

When privacy settings cannot be read safely

Privacy-sensitive downloads and cleanup use fresh saved policy with local coordination. A busy operation can return a retryable error. Unreadable privacy settings disable address capture and pause activity/request cleanup instead of silently applying fallback retention. Review and save valid settings to repair the problem, then check System status. Historical health messages are not erased by a repair.

03

Handle a personal-data request in the correct site

#
WordPress privacy actions
ActionWhat Logged.ai doesBoundary
Export Personal DataSupplies a protected reference for an authorized administrator to review associated evidence.The ordinary WordPress download does not receive a copy of the activity records.
Erase Personal DataRemoves matching evidence and linked request-address context through scoped cleanup.Requires WordPress privacy permission and evidence-purge authority; it does not delete the WordPress account.
Request for a deleted accountAn authorized operator uses the known former user ID through the scoped privacy CLI.An email lookup cannot recover the old account ID. Other sites need separate authorized handling.

Check the reported completion state. Cleanup may need more than one batch, and a zero event count does not prove that every related piece of personal data has disappeared.

Files already shared remain outside this cleanup

Downloaded exports, reports and copies held by recipients cannot be recalled. Include those copies in your own handling process.

04

Deactivation, updates and uninstall

#
What happens when you stop or remove the plugin?
ActionData effect
DeactivateRetained data is preserved.
Update the plugin ZIPsUse the normal update path; uninstall is not required.
Uninstall with deletion disabledRetained data is preserved.
Uninstall after explicitly saving installation-wide deletionLogged.ai data across the installation, including its sites and networks, is selected for deletion. This needs installation-purge authority and confirmation.

Before removal, inspect the saved uninstall choice and keep any recovery material you need. See Update the pair and resume a schema upgrade for routine updates.

Legacy export cleanup: explicit delete-all uninstall removes owned tables only after private export cleanup is verified. On Windows, automatic verification of legacy files is unavailable, so their job records and the plugin tables remain until host-assisted verification and cleanup outside the plugin. This safeguard does not prevent ordinary database-only expiry cleanup. Read the export storage requirements before removing old files.

ABOUT THIS REFERENCE

This guide covers Logged.ai Free 1.2.7 and Pro 1.2.7. Check available versions and package requirements, and verify representative workflows on staging before updating your main site.

A question we haven’t answered?

Get help with your next step.

Contact support