Granular AI feature opt-in controls exist

GDPR Article 7 requires that consent be as specific as the processing activity — a blanket "I agree to AI" toggle does not meet the granularity standard when your product uses AI for distinct purposes (writing assistance, history saving, analytics, model training opt-in). CCPA §1798.120 gives consumers the right to opt out of specific categories of data sale or sharing. A single on/off switch forces users into an all-or-nothing choice, reducing trust and limiting your ability to demonstrate specific lawful bases for each processing activity.

Design AI settings with distinct, labeled controls for each processing activity. Store them as separate boolean fields so each has its own consent record.

// types/user-settings.ts
interface UserAiSettings {
  ai_chat_enabled: boolean        // AI responds to messages
  ai_history_saved: boolean       // Conversation history persisted
  ai_usage_analytics: boolean     // Usage included in aggregate analytics
  ai_training_opt_out: boolean    // Opt out of provider model training
}

Present these in a dedicated "AI & Privacy" settings section with plain-language descriptions — not legal prose — explaining what each toggle controls and what stops when it is disabled. Log the timestamp of each change for your consent audit trail.