SecureDefaults

The README explicitly warns that setting a password multiple times regenerates the key and loses all previous data, which can lead to accidental data loss if not handled carefully.

Only encrypts data stored in UserDefaults; other local storage methods like Core Data or files require separate encryption solutions, limiting comprehensive security coverage.

If the password is lost or corrupted, encrypted data becomes inaccessible with no built-in way to recover, relying entirely on developer-managed backups or fallbacks.

Encryption and decryption processes add computational cost, which might slow down app performance for frequent or large data accesses compared to unencrypted UserDefaults.