willchen96 bolts two-factor onto Mike and hands users the delete button

A single pass adds real account security and gives people genuine control over their own data.

securitycompliance

willchen96 landed a broad security-and-privacy sweep. The headline is authenticator-app two-factor authentication, now required before any sensitive move - changing API keys, exporting data, bulk-deleting, or closing an account. A few pieces to know:

  • Optional two-factor at login, on top of the mandatory check for sensitive actions.
  • Signing out now ends only the current device's session instead of every session everywhere.
  • Users can export their chats, their tabular reviews, and a full copy of their account as a downloadable file.
  • Bulk deletion for chats, projects, and reviews, with project deletion now cleaning up every attached document, folder, and stored file instead of leaving debris behind.
  • Credentials and API keys are scrubbed from logs and error messages, closing a path that could have leaked keys; the account export deliberately carries key status but never the keys themselves.

Every export and delete route is locked behind authentication and rate limits.

So what Anyone weighing Mike for a firm that answers to clients on data handling should look here first.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

4 commits from open-legal-products/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
3a109432 feat: implement multi-factor authentication (MFA) setup and verification flow willchen96 2026-06-10 ↗ GitHub
commit body
- Add SecurityPage component for managing MFA settings, including enrollment and verification.
- Create MfaLoginGate to handle MFA verification state during login.
- Develop MfaVerificationPopup for user input of verification codes.
- Implement VerifyMfaPage for the MFA verification process after login.
- Introduce reusable VerificationCodeInput component for entering verification codes.
- Integrate Supabase MFA API for managing factors and verification.
- Add loading states and error handling for a better user experience.
444d1d38 feat: enhance user profile management and MFA login flow willchen96 2026-06-10 ↗ GitHub
commit body
- Refactor user profile loading and updating logic to improve state management and reduce unnecessary checks.
- Update MFA login gate to streamline verification checks and improve user experience.
- Ensure consistent handling of user ID across profile context and components.
- Improve error handling and loading states in user-related API calls.
a211b92f Merge pull request #172 from willchen96/feat/mfa-data-deletion-and-exports cosimoastrada 2026-06-10 ↗ GitHub
feat: implement multi-factor authentication (MFA) setup and verification flow and data deletion and export
8a2dc051 Merge pull request #178 from willchen96/feat/mfa-data-deletion-and-exports cosimoastrada 2026-06-11 ↗ GitHub
Refactor ProjectPageParts and ProjectPageHeader components

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-703.md from inside the repo you want the changes in.

⬇ Download capture-thread-703.md