Keep control of plugin data

Choose what stays on the site

Free makes no requests to RedirectNest services and sends no product telemetry. Fonts and plugin assets are local. Rules, settings and auxiliary records stay in WordPress. Basic hit/404 counts are optional and off by default; they record totals without visitor IPs, user agents, queries or referrers. Paths may still contain personal information.

Deletion reviews store a post identifier, old path and timestamp for up to 30 days, capped at 100 entries. Pro repair queues (up to 500), mapper reviews, saved scans and cleanup records expire after 30 days; approval previews expire after 15 minutes. Lifecycle intentions expire 90 days after the latest edit or requested review date. WordPress scheduled cleanup and your hosting cron affect when expired data is removed.

A complete invalid editor submission may retain non-sensitive values in a private local draft for its authorized editor: up to five drafts for 15 minutes. Saving, discarding or auxiliary erasure clears them. Truncated submissions and detected credentials are not retained.

Keep secrets out of URLs

When preserving incoming query parameters, RedirectNest filters common secret and email names even inside nested parameters, such as profile[email]. Pro also redacts recognized sensitive parameters in saved check observations. This is a safeguard, not a guarantee that a URL contains no personal information.

Configured rules and destinations remain as entered, and older saved source conditions remain manageable. Review them yourself and remove secrets from URLs before sharing exports or running HTTP checks. Destination operators still receive the requested URL and your server IP.

Separate local review from external services

Smart repair suggestions and Auto-Mapper comparisons run locally. Explicitly authorized checks contact public destinations and disclose the requested URL and server IP, without visitor cookies or credentials. Starting a content scan also authorizes outbound checks; external destinations need a separate choice. Check limits still apply.

Connected Pro sends the site address, site-specific key and environment to redirectnest.com for activation, entitlement and signed updates. The key is encrypted locally with WordPress salts and hashed by the service.

Aggregate fleet sharing is a separate administrator opt-in for versions, rule/check totals and timestamps, with 30-day remote retention. Detailed diagnostics require another initially disabled administrator choice: up to 25 redacted local problem paths and saved statuses plus seven daily aggregate totals, retained remotely for seven days. No destination URLs, queries, visitor identifiers, referrers, cookie/header values or page bodies are shared. Paths can still be sensitive.

Detailed fleet views require a compatible service and its rollout; installed controls alone do not establish availability in your private dashboard. Page views do not enroll a site and aggregate sharing does not enable detailed sharing. See service privacy and terms.

Erase auxiliary data deliberately

Open RedirectNest → Privacy, review the retained data and enter the required ERASE confirmation. Auxiliary erasure preserves active redirects, rule generation and core settings. It clears local counters, editor drafts, suggestions, deletion reviews, Pro repair/mapper/lifecycle/cleanup records, content-scan data, rule snapshots, migration drafts and reports, including new Pro records while Pro is inactive.

Erasure cancels background jobs, recurring monitoring and pending alert emails and stops detailed sharing. Active-rule schedules and the install key remain; manage them separately. While Pro is active, it uses the existing site/key connection and withdrawal state to request erasure of shared diagnostics. If Pro is inactive or the service is unreachable, remote erasure remains pending. Active Pro can retry, or use the private purchase page. Aggregate and detailed choices stay separate; replacing a key does not carry detailed consent to the new connection.

Deactivation and uninstall retain local rules and settings. Native WordPress revisions, downloaded reports and independent backups need their own deletion and retention process. Auxiliary erasure removes recovery records, so export and back up anything you need first.

Review decisions and dated evidence

404 review decisions, proposals, change records and care histories remain in the WordPress database. Paths can contain personal information. Auxiliary erasure clears these records even when Pro is inactive; it also disables recurring content scans and clears their pending cron work. Exported files, native revisions, browser downloads and independent backups need separate handling.