Dragwyb Docs Dragwyb Docs
Visit Website
Updated on Oct 17, 2026

Configure Data Retention

Configure chat-history and error-log retention, review uninstall cleanup choices, and test deletion behavior safely in Dragwyb Click to Chat.

Review data retention settings in Dragwyb Click to Chat before deciding how long conversation history and error logs should remain available or what should be deleted when the plugin is uninstalled. These controls affect different records, so verify the saved configuration before relying on it for a privacy policy.

1. Configure conversation-history retention

  1. In WordPress admin, open Click to Chat → AI Assistant.
  2. Open Chatbot Settings → Advance.
  3. Find Conversation History & Retention Policy.
  4. Enable the conversation-history feature if you want to persist visitor conversation logs and use the associated history and context features.
  5. Choose a value under Conversation Retention Policy (WP-Cron) and save the chatbot settings.

The available choices in the inspected plugin version are:

  • 0 — Keep Forever: no automatic deletion by this retention setting.
  • 7, 14, 30, 60, 90, 180, or 365 days: automatically purge chat sessions older than the selected age on the scheduled WordPress cleanup.

The setting’s default in the current source is 0 (Keep Forever). Do not describe chat history as automatically expiring unless a finite retention period is configured and the cleanup process is operating.

2. Configure error-log retention

  1. Remain in Click to Chat → AI Assistant → Chatbot Settings → Advance.
  2. Find Error Logging & Retention.
  3. Enable error logging if you want provider errors and system exceptions captured for troubleshooting.
  4. Choose a value under Auto-delete Logs (Daily WordPress Cron) and save.

The available choices are 0 (Never / Permanent), 1, 7, 14, 30, 60, or 90 days. The source default is 0, meaning this retention control does not automatically expire logs. Error-log retention is separate from conversation-history retention.

3. Review uninstall cleanup separately

  1. Open Click to Chat → Settings → Privacy.
  2. Review the Privacy & Uninstall Data Management options.
  3. For each data category, decide whether it should be deleted when the plugin is uninstalled. Read the option description before selecting it.
  4. Save the settings and keep a backup before choosing destructive cleanup options.

The inspected source provides separate uninstall choices for:

  • Plugin options and API keys — configuration options, channel settings, prompts, and stored provider keys.
  • AI chat sessions and leads — conversation-session and captured-lead records.
  • Knowledge base and vectors — knowledge-base and embedding/vector data.
  • Support tickets and roster — support workspace records such as tickets, categories, tags, agents, audit events, internal notes, assignments, and notification logs.
  • Error and diagnostic logs — the plugin’s error-log table and diagnostic events.
  • User preferences and metadata — associated dashboard preferences and interface state.
  • Cron jobs and transients — scheduled cleanup and temporary cached values.

In the inspected source, the fallback uninstall configuration preserves plugin options, AI data, knowledge-base data, support data, and user metadata, while deleting error logs and temporary transients. Your site’s saved choices may differ, so inspect the current controls rather than assuming these defaults still apply.

4. Understand when uninstall cleanup runs

Simply deactivating Dragwyb Click to Chat does not remove its stored data. The configured uninstall cleanup runs when an administrator deletes the plugin from the WordPress Plugins screen. Review the selections carefully: selected cleanup options can permanently remove records and may not be reversible without a backup.

5. Verify retention safely

  1. Record the current values before changing them.
  2. Use a staging site and sample conversations or diagnostic records where possible.
  3. Set a finite retention period and verify that the relevant scheduled cleanup runs and removes only the intended records.
  4. Check that the site’s WordPress cron mechanism is running; a configured schedule is not proof that a cleanup event has executed successfully.
  5. Test uninstall cleanup only on a disposable or backed-up environment.
  6. Update your privacy notice and internal procedures to reflect the configured retention periods and actual deletion behavior.

Important distinctions

  • Conversation retention, error-log retention, and uninstall cleanup are separate controls.
  • Deleting local records does not necessarily delete data already sent to an external AI provider, messaging service, or vector database. Review the provider’s own terms and controls.
  • A configured retention value is not proof of successful runtime deletion. Verify cleanup behavior on your site before making a compliance claim.

Related guides