profile-system

User profile privacy toggles in Laravel are managed through a dedicated controller that centralizes settings updates, ensuring privacy configurations are properly cached and synchronized across web and mobile SPA routes.

Secure account deletion with Redis cleanup is handled by a dedicated controller that removes user data and automatically purges associated Redis metrics, preventing orphaned cache entries across web and legacy routes.

Redis metrics fall back to MySQL for pre-v5 user profiles by utilizing a fallback mechanism that retrieves XP, level, rank, and achievement data directly from the database when Redis data is unavailable.

Yes, the profile management system explicitly supports both SPA and legacy Laravel routes, applying unified profile dashboard configurations, privacy controls, and account lifecycle actions across mixed route architectures.

Tracking XP and achievements with Redis metrics is best handled by a dedicated metrics collector and LevelService, which process user progress data in real-time while maintaining MySQL as a reliable fallback.

Profile data export failures during Redis cleanup may occur if the deletion controller does not properly sequence the data retrieval and cache purge operations, requiring proper orchestration between controllers and the Redis metrics collector.