feat: Data Security section with permanent account deletion - #249
Open
farhat-is-coding wants to merge 1 commit into
Open
feat: Data Security section with permanent account deletion#249farhat-is-coding wants to merge 1 commit into
farhat-is-coding wants to merge 1 commit into
Conversation
Settings gains a Data Security card with a two-step deletion modal: first a plain-language inventory of everything that goes (conversations, shared content, workflows, agents, the SocraticBooks account, vectorized data) with an export-first escape hatch, then a typed-DELETE confirmation before calling the expunge endpoint and signing the user out.
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
1 participant
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.
What
Settings gains a Data Security card with a two-step account-deletion modal.
Stacked on #220 (data export) — merge that first; this PR's base auto-retargets to
devwhen it lands.UX
DELETEarms the destructive button. On success the session is cleared and the user lands on /login.Implementation
Standard API → thunk → slice cycle (
accountDeletion), callsDELETE users/api/account/(backend PR: cmudco/dare-backend#323). One component per file:DataSecuritySettingscard +DeleteAccountDialog.Testing
Exercised live against the backend branch: export 200s, deletion removes the account and redirects; dialog state resets on close; delete button disabled until the phrase matches.