docs(preferences): clarify that stored data is unencrypted and point to secure alternatives - #2571
Open
djabif wants to merge 1 commit into
Open
docs(preferences): clarify that stored data is unencrypted and point to secure alternatives#2571djabif wants to merge 1 commit into
djabif wants to merge 1 commit into
Conversation
…to secure alternatives Adds a short note to the Preferences README clarifying that data stored through this API is not encrypted, and points readers to an encrypted key/value alternative for sensitive data.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a short note to the Preferences README clarifying that data stored through this API is not encrypted, and points readers to an encrypted key/value alternative for sensitive data.
Change Type
Rationale / Problems Fixed
A recurring question from developers is whether Preferences is safe for storing tokens, credentials, or other sensitive values. The current note covers the "don't use this as a database" case and links SQLite-based alternatives, but doesn't address the encryption question directly, which leads people to store sensitive data here assuming it's protected.