Manage Your Customer Data

Configure data retention, cleanup schedules, and storage optimization to keep your database performing efficiently.

Data Retention Policies

Control how long data is kept:

  • Session Data: Keep for 30, 60, 90 days, or forever
  • Customer Profiles: Keep until manually deleted
  • Search History: Keep for 90, 180, 365 days
  • Analytics Data: Aggregate and archive after 1 year

Configure at: Customer History → Settings → Data Management

Automatic Cleanup

Schedule automatic data deletion:

  1. Enable auto-cleanup
  2. Set retention period per data type
  3. Choose cleanup frequency (daily, weekly)
  4. Select cleanup time (low-traffic hours)
  5. Get email notification after cleanup
Permanent Deletion

Auto-cleanup permanently deletes old data. Export backups before enabling.

Archive Old Sessions

Archive instead of delete:

  • Move sessions older than X days to archive table
  • Keeps data accessible but optimizes main tables
  • Can restore archived data if needed
  • Archived data excluded from real-time queries

Database Optimization

Keep database performant:

  • Optimize Tables: Defragment database tables weekly
  • Index Maintenance: Rebuild indexes monthly
  • Query Cache: Enable caching for faster queries
  • Cleanup Orphaned Data: Remove data without parent records

Run manually: Customer History → Tools → Optimize Database

Storage Limits

Monitor storage usage:

  • View total database size
  • See size per data type
  • Get alerts at storage thresholds
  • Estimate growth rate

Data Export Before Cleanup

Always backup before cleanup:

  1. Go to Export
  2. Select all data types
  3. Export to CSV/JSON
  4. Store backup securely
  5. Then run cleanup

GDPR Compliance

Data management for privacy compliance:

  • Auto-delete after consent expires
  • Anonymize data older than X years
  • Handle right-to-be-forgotten requests
  • Export customer data on request

Best Practices

  • Keep session data for at least 90 days
  • Archive before deleting
  • Run cleanup during low-traffic hours
  • Monitor database size weekly
  • Test restoration from backups regularly