[Feature Request] Decoupling Persistence (History) from Training Ingestion

The Problem: Current Gemini architecture uses a binary toggle for Gemini Apps Activity. This forces a “Privacy Tax” where users must surrender data sovereignty for model training just to access basic history persistence.

The Proposal: Decouple the is_history_stored flag from the is_training_eligible flag.

  • Short-term: Implement a metadata tag training_opt_out that excludes data from RLHF/ingestion pipelines while maintaining it in the user’s siloed history vault.
  • Long-term: Move toward a RAG-based local history index (on-device) to reduce cloud training exposure and storage costs.

Market Parity & Value: Data Sovereignty is a fundamental user right, not a premium privilege. Currently, “History without Training” is treated as an Enterprise-only feature. This should be a baseline architectural standard for Normal and Pro users alike. Gating privacy behind a business license creates a trust deficit with the very early adopters who drive platform growth.