Privacy and Data Storage in AIVOW Lite

Understand which administrator-configured records AIVOW Lite stores and which visitor data it intentionally avoids.

When to use this guide

Use this guide when you need to understand where AIVOW Lite stores its records, which limited browser storage it uses, and which visitor data it does not collect.

Understand what AIVOW Lite stores in WordPress

AIVOW Lite stores administrator-configured records locally in the WordPress database.

The plugin uses custom database tables for:

• AI system records;
• internal AI system location records;
• Wizard and readiness answers.

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

• {prefix}aitm_systems;
• {prefix}aitm_system_locations;
• {prefix}aitm_readiness_answers.

The system-location table is part of the current AIVOW Lite core schema. It is intended for internal mapping of documented AI system locations and is not used to store visitor geolocation or track visitor locations. AIVOW Lite 1.0.0 does not expose a complete location-mapping workflow through the public plugin interface.

The plugin also stores settings in WordPress options, including:

• general plugin settings;
• badge appearance and placement settings;
• global banner settings;
• Lightweight AI Metadata settings;
• transparency page settings;
• AI Literacy summary visibility settings;
• uninstall cleanup preference.

Content-level disclosure information is stored as WordPress post meta. Taxonomy disclosure information is stored as term meta.

Post and term metadata can include:

• whether an AI badge is enabled;
• the selected AI usage status;
• a related AI system ID;
• custom badge text;
• internal content assessment fields used by the readiness workflow.

Provider-marking information and internal administrative notes are stored as part of the relevant AI system records. They are not visitor profiles or visitor activity logs.

These records remain under the control of the WordPress site administrator and are stored using the site’s existing WordPress database infrastructure.

Understand browser storage

Some acknowledgement features use limited browser storage.

Global banner acknowledgement

In Acknowledgement mode, the global AI banner stores a notice fingerprint in a browser cookie. The fingerprint is not designed to identify the visitor.

The fingerprint allows the browser to remember that the current version of the notice was acknowledged. If relevant banner content or configuration changes, the fingerprint can change and the banner can appear again.

The acknowledgement cookie has a maximum lifetime of one year unless it is cleared earlier or replaced by a new notice fingerprint.

Interaction gate acknowledgement

The interaction gate stores acknowledgement state in the visitor’s browser using local storage.

This allows wrapped content to remain available in that browser after acknowledgement.

AIVOW Lite does not send banner or interaction gate acknowledgement records to the WordPress database and does not create visitor acknowledgement logs.

AIVOW Lite also does not write disclosure acknowledgement button clicks to the WordPress database.

The interaction gate acknowledgement does not use a server-side expiration. It may remain in that browser until the related local storage is cleared or a different notice fingerprint is used.

Review whether this browser storage should be described in your site’s own privacy or cookie documentation.

Understand what AIVOW Lite does not collect

AIVOW Lite does not store:

• visitor names;
• visitor email addresses;
• IP addresses;
• full user-agent strings;
• visitor identifiers;
• AI prompts;
• chat messages;
• AI-generated responses;
• files uploaded by visitors;
• chatbot conversation history;
• interaction gate views or acknowledgements;
• global banner views or acknowledgements.

AIVOW Lite also does not provide visitor analytics or behavioral tracking.

Understand external data transmission

AIVOW Lite makes no plugin-initiated external API calls. Its settings and records remain in the WordPress installation.

AIVOW Lite does not transmit AI system records, Wizard answers, badge settings, prompts, content, or visitor information to the AIVOW product website or an external AI provider.

This boundary applies only to AIVOW Lite. Your WordPress host, theme, analytics tools, consent platform, WooCommerce extensions, embedded AI tools, chatbots, SEO plugins, and other third-party services may process data independently.

Review those products and services separately when assessing the complete site’s privacy and data-processing behavior.

This guide describes the installed AIVOW Lite plugin. It does not describe data handling by the AIVOW product website, its support and update forms, Cloudflare Turnstile, hosting infrastructure, or other website services. Those activities are described separately in the website Privacy Policy.

Review uninstall data preservation

Deactivating AIVOW Lite does not delete its stored configuration.

Plugin data is also preserved during uninstall by default unless the administrator explicitly enables the cleanup option before uninstalling the plugin.

Preserving the data allows the plugin to restore its previous configuration if it is installed again.

A generated Transparency Page is standard WordPress content. Deactivating, uninstalling, or permanently cleaning up the plugin does not automatically move that page to Draft or delete it. Review, unpublish, or delete the WordPress page separately when appropriate.

Review the separate Uninstall Behavior and Data Cleanup guide before enabling permanent cleanup.

Review the privacy information in admin

Open the privacy and data storage information provided by AIVOW Lite and compare it with the features currently enabled on the site.

Confirm that:

1. the AI systems and Wizard answers contain only information appropriate for WordPress administration;
2. content and taxonomy disclosure fields do not contain unnecessary personal information;
3. the banner and interaction gate behavior matches the site’s public documentation;
4. other plugins or embedded AI tools are reviewed separately;
5. the uninstall cleanup preference matches the site’s data-retention plan.

Common mistakes

• Assuming that because AIVOW Lite stores data locally, it does not create WordPress database records.
• Confusing WordPress database storage with browser local storage.
• Assuming that AIVOW Lite stores banner or interaction gate acknowledgement logs.
• Entering personal, confidential, or unnecessary information into internal notes or AI system fields.
• Assuming that AIVOW Lite controls the data practices of an embedded chatbot or AI provider.
• Treating the plugin’s limited data collection as a complete privacy assessment of the WordPress site.
• Assuming that deactivation deletes plugin data.
• Uninstalling the plugin without reviewing the cleanup preference.
• Forgetting that backups or staging copies may still contain previously stored WordPress data.

Troubleshooting

• Confirm that AIVOW Lite is active before reviewing its admin data information.
• Check the AI Systems Registry if expected AI system records appear to be missing.
• Reload the Wizard and confirm that readiness answers remain saved.
• Reopen the affected post, page, product, or taxonomy term if badge settings are not retained.
• Confirm that the browser allows cookies when testing global banner acknowledgement.
• Confirm that browser local storage is available when testing the interaction gate.
• Use a private browsing window or clear the relevant browser storage when retesting the initial acknowledgement state.
• Remember that browser storage is specific to the browser and device where the acknowledgement occurred.
• Review caching and optimization plugins if acknowledgement behavior appears inconsistent.
• Check the separate uninstall guide before attempting to remove stored plugin data.
• Review other active plugins and embedded services if unexpected network requests or visitor data processing are observed.