What problem does it solve? Protecting sensitive data in ASP.NET Core applications is error-prone when developers hand-roll encryption, hard-code keys, or misconfigure key storage, leading to data exposure, lost keys on container restarts, and compliance failures. ## Core Features & Use Cases - Data Protection Configuration: Set up key persistence with file system, Azure Blob Storage, Redis, or certificate-based key encryption, with proper application isolation via SetApplicationName. - Encryption at Rest: Encrypt sensitive entity fields (like payment card numbers) before database storage and decrypt on retrieval using purpose-specific IDataProtector instances. - Time-Limited Tokens: Generate expiring tokens for password resets and email confirmations using ITimeLimitedDataProtector. - Use Case: When building a checkout flow, encrypt payment method details before saving to the database, protect sensitive session data during checkout, and issue one-hour password reset tokens that automatically expire. ## Quick Start Ask the AI to configure ASP.NET Core Data Protection with persistent key storage and create a service that encrypts sensitive fields before saving them to the database.