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
Logged.ai → Settings → Privacy and retention
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.
| Mode | What is retained or shown | Practical effect |
|---|---|---|
| Masked (default) | Shared network context from the derived connection address. | Useful context, not an exact person or device identity. |
| Full derived address | The address derived under the configured source rules, until its separate expiry. | An explicit choice; exact-source targeting also needs trusted, eligible address context. |
| Disabled | No 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.
- Open Settings → Privacy and retention and review the currently saved periods.
- If shortening a period, read the affected-data explanation and confirm irreversible removal. This requires separate evidence-purge permission.
- Choose Save privacy settings, then read Retention status. Cleanup runs in bounded batches and can be delayed if scheduling is stopped.
- 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
| Evidence | Default retention |
|---|---|
| Administrative events | 90 days |
| Request observations | 7 days |
| Request groups | 30 days |
| Inactive response history | 30 days |
| Full exact client addresses | 14 days |
| Diagnostics | 7 days |
Collection presets or an administrator can change these values. Product defaults do not determine your legal or business retention obligations.
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.
| Action | What Logged.ai does | Boundary |
|---|---|---|
| Export Personal Data | Supplies 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 Data | Removes 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 account | An 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.
Downloaded exports, reports and copies held by recipients cannot be recalled. Include those copies in your own handling process.
| Action | Data effect |
|---|---|
| Deactivate | Retained data is preserved. |
| Update the plugin ZIPs | Use the normal update path; uninstall is not required. |
| Uninstall with deletion disabled | Retained data is preserved. |
| Uninstall after explicitly saving installation-wide deletion | Logged.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.
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.
Get help with your next step.