Uninstall Behavior and Data Cleanup

Understand how AIVOW Lite preserves plugin data by default and how to remove it permanently during uninstall.

When to use this guide

Use this guide before deactivating or deleting AIVOW Lite, especially when deciding whether its stored configuration should remain available for a future reinstallation or be removed permanently.

Understand the difference between deactivation and uninstall

Deactivating AIVOW Lite disables its active functionality but does not delete its stored configuration.

After deactivation:

• AI system records remain in the WordPress database;
• Wizard and readiness answers remain stored;
• plugin settings remain stored;
• content-level disclosure fields remain in post meta;
• taxonomy disclosure fields remain in term meta;
• the generated transparency page remains standard WordPress content;
• public plugin output is no longer generated while the plugin is inactive.

Reactivating the plugin allows the existing configuration to be used again.

Deleting the plugin from the WordPress Plugins screen runs the uninstall process. By default, plugin data is preserved unless permanent cleanup was explicitly enabled before deletion.

Preserve data for a future reinstallation

Leave the permanent cleanup option disabled when:

• the plugin is being deactivated temporarily;
• you are troubleshooting a compatibility issue;
• you expect to reinstall the plugin;
• you want to preserve AI system records and readiness answers;
• you are not certain whether the stored configuration is still needed.

With cleanup disabled, uninstalling the plugin removes its files but preserves its stored WordPress data.

Reinstalling and activating a compatible version can restore access to the preserved configuration.

Permanently remove plugin data

Permanent cleanup is irreversible unless the site data can be restored from a backup.

Before enabling cleanup

1. Review the AI Systems Registry.
2. Review the Wizard and readiness information.
3. Record or copy any information that must be retained.
4. Review the published transparency page and other public disclosures.
5. Create a current WordPress database backup.
6. Confirm that permanent removal matches the site’s retention requirements.

To enable cleanup

1. Open AIVOW → AIVOW Settings.
2. Open the Data and uninstall section.
3. Under Uninstall cleanup, enable Delete all AIVOW Lite data when the plugin is uninstalled.
4. Save the settings.
5. Confirm that the checkbox remains enabled.
6. Open Plugins → Installed Plugins.
7. Deactivate AIVOW Lite if it is still active.
8. Delete the plugin.
9. Review the site after deletion.

The cleanup option affects the uninstall process. Enabling it does not immediately delete the stored records while the plugin remains installed.

Understand what permanent cleanup removes

When permanent cleanup is enabled before uninstall, AIVOW Lite removes its plugin-managed WordPress data, including:

• the AI system records table;
• the internal AI system locations table;
• the Wizard and readiness answers table;
• AIVOW Lite options and settings;
• current and legacy AITM post and term metadata keys;
• legacy AITM log and notice-version tables, if present.

The custom table names use the current WordPress database prefix and include:

• {prefix}aitm_systems;
• {prefix}aitm_system_locations;
• {prefix}aitm_readiness_answers;
• {prefix}aitm_logs, if present;
• {prefix}aitm_notice_versions, if present.

AIVOW Lite 1.0.0 does not create or populate the aitm_logs or aitm_notice_versions tables. They are listed only because permanent cleanup can remove legacy AITM tables if they are present.

Permanent cleanup removes the plugin’s stored configuration. It does not remove unrelated WordPress, WooCommerce, theme, SEO, analytics, or third-party plugin data.

Review standard WordPress content separately

The generated transparency page is a standard WordPress page.

Do not assume that uninstall cleanup removes or unpublishes standard WordPress content created through the plugin workflow. Review the page separately and decide whether to:

• keep it;
• update its content;
• remove the inactive shortcode;
• move it to Draft;
• delete it permanently.

Also review any posts, pages, products, widgets, templates, or reusable blocks that contain these shortcodes:

• [aivow_disclosure id="123"];
• [aivow_interaction_gate id="123"]...[/aivow_interaction_gate];
• [aivow_transparency_page].

After the plugin is removed, these shortcodes no longer generate plugin output and may appear as inactive shortcode text depending on how the content is rendered.

Understand browser storage after uninstall

The uninstall process runs on the WordPress server. It cannot remotely clear storage that already exists in a visitor’s browser.

A previously stored global banner cookie or interaction gate local-storage value may remain in that browser until it expires, is cleared by the visitor, or is removed through browser controls.

These remaining browser values do not restore plugin functionality after the plugin has been removed.

The global banner acknowledgement cookie has a maximum lifetime of one year. Interaction gate local-storage values do not have a server-side expiration and may remain until they are cleared in the affected browser.

Review backups, staging sites, and caches

Permanent cleanup affects the current WordPress installation. Copies of earlier plugin data may still exist in:

• database backups;
• full-site backups;
• staging environments;
• development copies;
• hosting snapshots;
• migration archives;
• cached pages;
• exported database files.

Review those locations separately when complete removal is required.

Clearing WordPress data does not automatically remove copies retained by the hosting provider, backup service, development workflow, or another administrator.

Common mistakes

• Assuming that deactivation deletes plugin data.
• Deleting the plugin with permanent cleanup enabled while expecting the previous configuration to remain available.
• Enabling the uninstall cleanup checkbox but forgetting to save the settings before deleting the plugin.
• Expecting the data to be removed immediately after enabling the cleanup option.
• Assuming that reinstalling the plugin can restore data removed by permanent cleanup.
• Forgetting to review the generated transparency page after uninstall.
• Leaving inactive plugin shortcodes in published content.
• Assuming that server-side uninstall can clear cookies or local storage from every visitor’s browser.
• Assuming that uninstall cleanup also removes backups, staging copies, or hosting snapshots.

Troubleshooting

• If the previous configuration returns after reinstalling the plugin, the data was preserved during uninstall.
• Confirm that the permanent cleanup option was enabled and saved before the plugin was deleted.
• Remember that deactivation alone never runs the uninstall cleanup process.
• Confirm that the plugin was deleted through WordPress rather than only having its files removed manually.
• Create and verify a current database backup before attempting any manual data removal.
• Check published content for inactive AIVOW shortcodes after uninstall.
• Review the generated transparency page separately if it remains published.
• Clear active page, CDN, object, and optimization caches if old public output remains visible.
• Review staging sites and backups separately if plugin data must be removed from every stored copy.
• Remember that existing browser cookies and local-storage values must be cleared in the affected browser.
• Restore the database from a backup if permanent cleanup was enabled accidentally and a suitable backup is available.