Skip to content

feat(settings): add identity verification settings screen - #38381

Open
georgeweiler wants to merge 5 commits into
mainfrom
worktree-identity-verification-settings
Open

georgeweiler wants to merge 5 commits into
mainfrom
worktree-identity-verification-settings

Conversation

@georgeweiler

@georgeweiler georgeweiler commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

What changed

Adds an Identity verification screen showing each identity verification the customer has completed and which provider it was shared with.

  • New screen at app/components/Views/Settings/IdentityVerification/, built design-system-only (useTailwind() + Card / ListItem / AvatarIcon / ButtonSemantic) — no .styles.ts, no component-library imports.
  • One card, one row per provider: "Identity verification for provider" with the share date below, plus a full-width "Delete identity data" button.
  • The button asks for confirmation, then calls KycController.deleteEncryptedStorage(). It shows a loading state while running and an alert on success or failure.
  • useIdentityDataShares reads the list from KycController.getDataShares().
  • Bumps @metamask/kyc-controller to ^0.15.0, which contains getDataShares (0.14.0) and deleteEncryptedStorage (0.15.0, feat(KYC-71): add deletion of encrypted KYC blobs core#11262).
  • Entry point is a SettingsButtonSection in Security & Privacy, directly below "Delete wallet data", matching DeleteWalletData and DeleteMetaMetricsData. Hidden unless the moneyMovementNeobank flag is enabled and a KYC session exists.
  • Registered through Routes.SETTINGS.IDENTITY_VERIFICATION, both param lists, and SettingsFlow in MainNavigator.
  • New identity_verification block in locales/languages/en.json.

Why

The idOS relay recently added GET /api/kyc/external-user-id/{externalUserId}/shares, returning { kycSessionId, vendor, sharedAt } per share. That makes it possible to show customers who their identity data has been shared with — previously not surfaced anywhere in the app.

Reviewer notes

Decisions that will otherwise read as oversights:

  1. No dates on verification status, only on shares. The design originally showed a "Verified " line, but no relay endpoint returns an approved-at timestamp on any environment — KycSessionStatus carries no timestamp field. Recording one client-side was considered and rejected (new persistence, and it measures when the app noticed approval). Only sharedAt, which the API does return, is displayed.

  2. The screen does not show verification status at all. Every row is derived from the shares list. So pending / retry / rejected sessions are not surfaced here, and a customer who is verified but has shared with nobody sees only the delete button. This follows the current design; worth confirming it is intended before release.

  3. Deletion only clears relay-side encrypted data. deleteEncryptedStorage deletes the customer's encrypted KYC blobs on MetaMask servers and leaves controller state alone. The share list survives and providers keep what they already received, so the confirm dialog says so rather than implying anyone forgets the customer. After a successful delete the list is not refreshed. Confirm that is the intended behaviour, and whether design wants a bottom sheet instead of a native Alert.

  4. No MetaMetrics event on the entry point. Adding one means a new entry in the analytics enum, which generally wants product sign-off. Happy to add it here if wanted.

  5. KycVendor is narrower than the relay's enum. The package types it as 'moonpay' | 'iron', while the relay returns one of moonpay | iron | kalshi | kraken | mock and validates it as a plain string. The vendor-label map covers all five with a fallback to the raw value, so unknown vendors degrade to their id rather than rendering blank. Probably worth tightening in core.

Environment: the shares endpoint exists on relay.staging.idos.network (what dev builds use via IDOS_RELAY_URL in builds.yml) but not on relay.playground.idos.network (uat). A failed fetch is logged and renders an empty list rather than erroring.

Testing

  • Unit tests for the screen (including confirm, success and failure paths), the hook and the Security section all pass (18 across 3 suites).
  • ESLint clean on changed files. yarn lint:tsc shows only 2 existing app/util/termsOfUse errors (a gitignored file generated by full yarn setup).
  • Not verified in a simulator: the screen is gated behind a real KYC session.

🤖 Generated with Claude Code


Note

Medium Risk
Touches encrypted KYC storage deletion and identity-sharing metadata via upgraded kyc-controller; mistakes could affect user privacy data or show wrong share history.

Overview
Adds a new Identity verification area under Security & Privacy so users who have started KYC (with the neobank flag on) can open a dedicated settings screen from a View row below delete-wallet actions.

The screen lists who identity data was shared with—one row per provider from KycController.getDataShares() with share date—and offers a destructive Delete identity data flow that confirms via native alert, then calls KycController.deleteEncryptedStorage() with loading and success/error alerts.

Wires the screen into the settings stack (Routes.SETTINGS.IDENTITY_VERIFICATION, param lists, MainNavigator), bumps @metamask/kyc-controller to ^0.15.0, and extends the KYC controller messenger with getDataShares, createDeletion, and completeDeletion service actions. Includes useIdentityDataShares, English copy, and unit tests for the screen, hook, and security entry section.

Reviewed by Cursor Bugbot for commit c493050. Bugbot is set up for automated code reviews on this repo. Configure here.

Adds a Settings sub-screen showing the customer's identity-verification
status and the vendors their verified identity data has been shared
with, read from the idOS relay through KycController.

The "Shared with" list comes from KycController.getDataShares(), which
lands in @metamask/kyc-controller separately. Until that release is
picked up, `yarn lint:tsc` reports errors for the missing
`getDataShares` method and `KycDataShare` type, all confined to
useIdentityDataShares.ts.

The verified card deliberately carries no date: no relay endpoint
returns an approved-at timestamp, and recording one client-side was
rejected rather than borrow the unrelated `sharedAt`.

The "Delete identity data" button is intentionally inert for this MVP.
The relay's DELETE only redacts relay-side data — the share list
survives and vendors keep what they already received — so no handler is
wired until that copy is settled.

The Settings row stays hidden unless the moneyMovementNeobank flag is
enabled and a KYC session exists.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@georgeweiler
georgeweiler requested review from a team as code owners October 28, 2026 11:41
@github-actions

Copy link
Copy Markdown
Contributor

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

@metamask-ci metamask-ci Bot added team-money-movement issues related to Money Movement features INVALID-PR-TEMPLATE PR's body doesn't match template labels Oct 28, 2026
@metamask-ci

metamask-ci Bot commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

PR template — items to address before "Ready for review"

Warnings — informational, address before merging:

See docs/readme/ready-for-review.md for the full Definition of Ready for Review.

Copy link
Copy Markdown
Contributor

Accessibility

Nice clean screen! Just one small thing in IdentityVerification.tsx:

  • The "Shared with" title (line 112) looks like a section heading, but it's a plain Text with TextVariant.HeadingMd, and our DS Text sets accessibilityRole="text". That means VoiceOver and TalkBack users can't jump to it with heading navigation. Adding accessibilityRole="header" should do it (WCAG 1.3.1).

An AI accessibility agent posted this. If this is wrong, reply here.

@github-actions

github-actions Bot commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Smart E2E Test Selection

Selected E2E tags: ALL

AI Confidence: 100

E2E reasoning

Expand to read

Hard rule seed (controller-version-update) mandates ALL tags due to @metamask/kyc-controller version bump from 0.13.0 to 0.15.0 in package.json. Beyond the hard rule, the changes include: (1) New KYC controller messenger actions (getDataShares, createDeletion, completeDeletion) that extend the controller's delegated action surface; (2) New IdentityVerification screen added to Settings navigator with new route IDENTITY_VERIFICATION; (3) New IdentityVerificationSection added to SecuritySettings.tsx — a shared Settings surface that could affect existing E2E tests if the feature flag gate behaves unexpectedly; (4) Navigation type definitions updated in both MainNavigator types and NavigationService types (critical files); (5) New localization strings in en.json (functional, not cosmetic — could break text-based E2E selectors if strings are referenced). The changes are primarily additive and gated by moneyMovementNeobank feature flag + KYC session status, reducing blast radius for most flows. However, the controller version update and shared Settings surface modifications warrant broad coverage. SmokeMoney is the most directly relevant tag (neobank/KYC flows), but ALL is maintained per the hard rule floor.

View run

@cursor cursor Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale Bugbot comment from a previous run.

Comment thread app/components/Views/Settings/index.tsx Resolved
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 84.44444% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 87.45%. Comparing base (d1fa3ed) to head (27bcf86).
⚠️ Report is 35 commits behind head on main.

Files with missing lines Patch % Lines
...ings/IdentityVerification/IdentityVerification.tsx 83.33% 0 Missing and 4 partials ⚠️
app/components/Views/Settings/index.tsx 50.00% 1 Missing and 2 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main   #38381      +/-   ##
==========================================
+ Coverage   87.35%   87.45%   +0.09%     
==========================================
  Files        7848     7862      +14     
  Lines      227972   228054      +82     
  Branches    57637    57719      +82     
==========================================
+ Hits       199155   199446     +291     
+ Misses      16601    16374     -227     
- Partials    12216    12234      +18     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Moves the entry point off the Settings root list and into Security &
Privacy, directly below "Delete wallet data", so it sits with the other
identity-data controls. It now uses `SettingsButtonSection`, matching
`DeleteWalletData` and `DeleteMetaMetricsData` rather than introducing a
`SettingsDrawer` into a screen that has none. The gate is unchanged: the
section stays hidden unless the `moneyMovementNeobank` flag is enabled
and a KYC session exists.

Reworks the screen itself to the updated design: the standalone status
card and the "Shared with" heading are gone, replaced by a single card
with one row per provider reading "Identity verification for <provider>"
with the share date below. The delete button is now full width.

Because every row is derived from the shares list, the screen no longer
surfaces session status: a customer who is verified but has shared with
nobody sees only the delete button, and pending/rejected states are not
shown. The MoonPay logo asset is removed with the provider avatars it
was added for.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions github-actions Bot added size-L and removed size-M labels Oct 28, 2026

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 236d874. Configure here.

@georgeweiler georgeweiler changed the title feat(settings): add identity verification screen feat(settings): add identity verification settings screen Oct 28, 2026
@georgeweiler georgeweiler mentioned this pull request Oct 29, 2026
3 of 4 tasks
Naz-Ovh pushed a commit to 0x-fork/metamask-core that referenced this pull request Nov 4, 2026
## Explanation

MetaMask Mobile is adding an "Identity verification" screen in Settings
that shows a customer's KYC status and the vendors their verified
identity data has been shared with. The idOS relay serves that list from
`GET /api/kyc/external-user-id/{externalUserId}/shares`, but
`@metamask/kyc-controller` had no way to call it — `KycService` could
fetch session status, not who data was shared with.

This adds that lookup. It is additive only: no new controller state, no
persistence, and no change to the existing VBA onboarding flow or any
existing method.

- **`KycDataShare`** (`src/types.ts`) — `{ kycSessionId, vendor,
sharedAt }`, where `sharedAt` is an ISO 8601 date-time string.
- **`KycService.getDataShares({ externalUserId })`** — issues the relay
request through the same private request helper and wallet bearer-token
path as the other relay calls, validates the response with superstruct
like its neighbours, and unwraps the `{ shares }` envelope. `vendor` is
validated as a plain string (as `SessionStatusResponseStruct.vendor`
already is) so a vendor this package does not model does not invalidate
the whole list.
- **`KycController.getDataShares()`** — resolves the external user id
from `state.sessionStatus`. When state is cold it first fetches the
latest session for the vendor on state (without writing it to state). If
no session can be resolved at all it returns `[]`, so the mobile screen
renders an empty "Shared with" list instead of an error.
- Both methods are exposed as messenger actions
(`KycService:getDataShares`, `KycController:getDataShares`), and the new
types are exported from the package entry point.

Unblocks MetaMask/metamask-mobile#38381, which
is written against this API and currently does not type-check for
exactly these two missing pieces.

## References

- Unblocks MetaMask/metamask-mobile#38381

## Checklist

- [x] I've updated the test suite for new or updated code as appropriate
- [x] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [x] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/contributing.md#updating-changelogs),
highlighting breaking changes as necessary
- [x] I've prepared draft pull requests for clients and consumer
packages to resolve any breaking changes

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Read-only additive HTTP lookup with no state or onboarding flow
changes; failures are localized to the new call path when relay config
or auth is missing.
> 
> **Overview**
> Adds an **additive** API so clients can show which vendors a user's
verified KYC data was shared with, backed by the idOS relay `GET
/api/kyc/external-user-id/{externalUserId}/shares` endpoint.
> 
> **`KycService.getDataShares({ externalUserId })`** calls the relay
(wallet bearer auth, same path as other relay usage), validates `{
shares }` with superstruct, and returns metadata records
(`kycSessionId`, `vendor`, `sharedAt`). **`vendor`** is a plain string
so unknown relay vendors do not fail the whole list. Missing
**`idosRelayBaseUrl`** throws; bad HTTP or shape throws as elsewhere in
the service.
> 
> **`KycController.getDataShares()`** resolves **`externalUserId`** from
**`sessionStatus`** on state, or on cold state fetches the latest
session for the stored vendor **without persisting** it. No vendor or no
session yields **`[]`** instead of an error for empty UI states. **No
new controller state or persistence.**
> 
> New **`KycDataShare`**, **`GetDataSharesParams`**, and messenger
actions **`KycService:getDataShares`** /
**`KycController:getDataShares`** are exported; changelog and tests
cover service and controller behavior.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
a046e10. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Naz-Ovh pushed a commit to 0x-fork/metamask-core that referenced this pull request Nov 4, 2026
## Explanation

Scoped release so clients can pick up MetaMask#11158 and MetaMask#11099. Monorepo
release **1378.0.0** because
[Release/1377.0.0](MetaMask#11203) is
already open.

- **`@metamask/kyc-controller` 0.13.0 → 0.14.0** (minor). Both changes
are additive, so they stay in one minor.
- `KycService.getDataShares` and `KycController.getDataShares` list the
vendors a customer's verified identity data has been shared with
(MetaMask#11158). Both are messenger actions. No new controller state, and no
change to existing methods.
- `KycController.ensureLocalUserSecret` creates and stores the UKYC
`local_user_secret` when one does not already exist (MetaMask#11099).
`startSession` still creates the secret when this method has not been
called. The secret is not returned.

No workspace package depends on `kyc-controller`, so nothing else is
published. Other packages with unreleased changes are deferred.

## References

- Ships MetaMask#11158
- Ships MetaMask#11099
- Unblocks MetaMask/metamask-mobile#38381

## Checklist

- [x] I've updated the test suite for new or updated code as appropriate
- [x] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [x] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md)
- [ ] I've introduced [breaking
changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md)
in this PR and have prepared draft pull requests for clients and
consumer packages to resolve them

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> The diff is version and changelog metadata only; functional changes
were merged in earlier PRs and are not modified here.
> 
> **Overview**
> This is a **scoped release PR** that bumps the monorepo to
**1378.0.0** and publishes **`@metamask/kyc-controller` 0.13.0 →
0.14.0**, with the package changelog cut from `[Unreleased]` into
**`[0.14.0]`** (compare links updated accordingly). No application
source files change in this diff—only `package.json` versions and
`CHANGELOG.md`.
> 
> The **0.14.0** notes document additive KYC work clients can pick up
after publish, including **`getDataShares`** on the service and
controller (messenger actions, no new persisted state),
**`ensureLocalUserSecret`** to create/store the UKYC `local_user_secret`
before session start when desired, optional **`currentStep`** on session
status (plus related **`finalStatus`** mapping when step is `kyc`), and
the associated exports/types called out in the changelog.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
b880f85. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: jiexi <jiexiluan@gmail.com>
georgeweiler and others added 2 commits November 5, 2026 03:40
Bump @metamask/kyc-controller to ^0.15.0 for deleteEncryptedStorage and
hook it to the Delete identity data button behind a confirmation.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@socket-security

socket-security Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​@​metamask/​kyc-controller@​0.13.0 ⏵ 0.15.099 +2210080 +198 +1100

View full report

…ontroller

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@sonarqubecloud

sonarqubecloud Bot commented Nov 5, 2026

Copy link
Copy Markdown

runway-github Bot pushed a commit that referenced this pull request Nov 13, 2026
…#39037)

## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming calls
`KycController.deleteEncryptedStorage()`. That requires
`@metamask/kyc-controller` 0.15.0 and the `KycService:createDeletion`
and `KycService:completeDeletion` messenger actions. Cancelling the
confirmation leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

<img width="444" height="919" alt="Screenshot 2026-11-06 at 12 54 42 PM"
src="https://github.com/user-attachments/assets/3f8afa12-1926-40ce-93d5-496623d0e8bf"
/>
<img width="443" height="895" alt="Screenshot 2026-11-06 at 12 54 50 PM"
src="https://github.com/user-attachments/assets/87c92809-76f2-44eb-ad2e-21719cb2af10"
/>
<img width="455" height="881" alt="Screenshot 2026-11-06 at 12 54 24 PM"
src="https://github.com/user-attachments/assets/2db0bb77-bbde-4617-9ed2-483cdd396a53"
/>



## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming asks for an email one-time code, then calls
`KycController.deleteEncryptedStorage({ aal2Token })` with that
verification token. That requires `@metamask/kyc-controller` 0.16.0 and
the `KycService:createDeletion` and `KycService:completeDeletion`
messenger actions. Cancelling the confirmation, or backing out of the
email check, leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    And I complete the email one-time code check
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted

  Scenario: backing out of email verification leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and confirm
    And I back out of the email one-time code check
    Then nothing is deleted and no error is shown
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

N/A

## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a
href="https://cursor.com/agents/bc-6f157964-72b0-5445-87a7-0edda2664e74?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/background-agent?bcId=bc-6f157964-72b0-5445-87a7-0edda2664e74&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"
src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Introduces user-triggered deletion of encrypted KYC data with MFA
gating; mistakes could affect identity verification state, but scope is
limited to customers with an active session and the feature flag.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
23be80c. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
runway-github Bot added a commit that referenced this pull request Nov 13, 2026
…#39037)

## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming calls
`KycController.deleteEncryptedStorage()`. That requires
`@metamask/kyc-controller` 0.15.0 and the `KycService:createDeletion`
and `KycService:completeDeletion` messenger actions. Cancelling the
confirmation leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

<img width="444" height="919" alt="Screenshot 2026-11-06 at 12 54 42 PM"
src="https://github.com/user-attachments/assets/3f8afa12-1926-40ce-93d5-496623d0e8bf"
/>
<img width="443" height="895" alt="Screenshot 2026-11-06 at 12 54 50 PM"
src="https://github.com/user-attachments/assets/87c92809-76f2-44eb-ad2e-21719cb2af10"
/>
<img width="455" height="881" alt="Screenshot 2026-11-06 at 12 54 24 PM"
src="https://github.com/user-attachments/assets/2db0bb77-bbde-4617-9ed2-483cdd396a53"
/>

## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming asks for an email one-time code, then calls
`KycController.deleteEncryptedStorage({ aal2Token })` with that
verification token. That requires `@metamask/kyc-controller` 0.16.0 and
the `KycService:createDeletion` and `KycService:completeDeletion`
messenger actions. Cancelling the confirmation, or backing out of the
email check, leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    And I complete the email one-time code check
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted

  Scenario: backing out of email verification leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and confirm
    And I back out of the email one-time code check
    Then nothing is deleted and no error is shown
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

N/A

## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a
href="https://cursor.com/agents/bc-6f157964-72b0-5445-87a7-0edda2664e74?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/background-agent?bcId=bc-6f157964-72b0-5445-87a7-0edda2664e74&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"
src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Introduces user-triggered deletion of encrypted KYC data with MFA
gating; mistakes could affect identity verification state, but scope is
limited to customers with an active session and the feature flag.
>
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
23be80c. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
runway-github Bot pushed a commit that referenced this pull request Nov 13, 2026
…ity settings cp-8.21.0 (#39037)

## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming calls
`KycController.deleteEncryptedStorage()`. That requires
`@metamask/kyc-controller` 0.15.0 and the `KycService:createDeletion`
and `KycService:completeDeletion` messenger actions. Cancelling the
confirmation leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

<img width="444" height="919" alt="Screenshot 2026-11-06 at 12 54 42 PM"
src="https://github.com/user-attachments/assets/3f8afa12-1926-40ce-93d5-496623d0e8bf"
/>
<img width="443" height="895" alt="Screenshot 2026-11-06 at 12 54 50 PM"
src="https://github.com/user-attachments/assets/87c92809-76f2-44eb-ad2e-21719cb2af10"
/>
<img width="455" height="881" alt="Screenshot 2026-11-06 at 12 54 24 PM"
src="https://github.com/user-attachments/assets/2db0bb77-bbde-4617-9ed2-483cdd396a53"
/>



## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming asks for an email one-time code, then calls
`KycController.deleteEncryptedStorage({ aal2Token })` with that
verification token. That requires `@metamask/kyc-controller` 0.16.0 and
the `KycService:createDeletion` and `KycService:completeDeletion`
messenger actions. Cancelling the confirmation, or backing out of the
email check, leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    And I complete the email one-time code check
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted

  Scenario: backing out of email verification leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and confirm
    And I back out of the email one-time code check
    Then nothing is deleted and no error is shown
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

N/A

## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a
href="https://cursor.com/agents/bc-6f157964-72b0-5445-87a7-0edda2664e74?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/background-agent?bcId=bc-6f157964-72b0-5445-87a7-0edda2664e74&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"
src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Introduces user-triggered deletion of encrypted KYC data with MFA
gating; mistakes could affect identity verification state, but scope is
limited to customers with an active session and the feature flag.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
23be80c. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
sleepytanya pushed a commit that referenced this pull request Nov 13, 2026
…ity settings (#39742)

- feat(kyc): delete identity data from security settings cp-8.21.0
(#39037)

## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming calls
`KycController.deleteEncryptedStorage()`. That requires
`@metamask/kyc-controller` 0.15.0 and the `KycService:createDeletion`
and `KycService:completeDeletion` messenger actions. Cancelling the
confirmation leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

<img width="444" height="919" alt="Screenshot 2026-11-06 at 12 54 42 PM"

src="https://github.com/user-attachments/assets/3f8afa12-1926-40ce-93d5-496623d0e8bf"
/>
<img width="443" height="895" alt="Screenshot 2026-11-06 at 12 54 50 PM"

src="https://github.com/user-attachments/assets/87c92809-76f2-44eb-ad2e-21719cb2af10"
/>
<img width="455" height="881" alt="Screenshot 2026-11-06 at 12 54 24 PM"

src="https://github.com/user-attachments/assets/2db0bb77-bbde-4617-9ed2-483cdd396a53"
/>



## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding

Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling

guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user

SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and

[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance

Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming asks for an email one-time code, then calls
`KycController.deleteEncryptedStorage({ aal2Token })` with that
verification token. That requires `@metamask/kyc-controller` 0.16.0 and
the `KycService:createDeletion` and `KycService:completeDeletion`
messenger actions. Cancelling the confirmation, or backing out of the
email check, leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    And I complete the email one-time code check
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted

  Scenario: backing out of email verification leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and confirm
    And I back out of the email one-time code check
    Then nothing is deleted and no error is shown
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

N/A

## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding

Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling

guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user

SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and

[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance

Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a

href="https://cursor.com/agents/bc-6f157964-72b0-5445-87a7-0edda2664e74?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"

src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a

href="https://cursor.com/background-agent?bcId=bc-6f157964-72b0-5445-87a7-0edda2664e74&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"

srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"

src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Introduces user-triggered deletion of encrypted KYC data with MFA
gating; mistakes could affect identity verification state, but scope is
limited to customers with an active session and the feature flag.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
23be80c. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
[3d642d6](3d642d6)

Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
Co-authored-by: George Weiler <georgejweiler@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
WcahtDenvion pushed a commit to WcahtDenvion/metamask-mobile that referenced this pull request Nov 15, 2026
…aMask#39037)

## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming calls
`KycController.deleteEncryptedStorage()`. That requires
`@metamask/kyc-controller` 0.15.0 and the `KycService:createDeletion`
and `KycService:completeDeletion` messenger actions. Cancelling the
confirmation leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: MetaMask#38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

<img width="444" height="919" alt="Screenshot 2026-11-06 at 12 54 42 PM"
src="https://github.com/user-attachments/assets/3f8afa12-1926-40ce-93d5-496623d0e8bf"
/>
<img width="443" height="895" alt="Screenshot 2026-11-06 at 12 54 50 PM"
src="https://github.com/user-attachments/assets/87c92809-76f2-44eb-ad2e-21719cb2af10"
/>
<img width="455" height="881" alt="Screenshot 2026-11-06 at 12 54 24 PM"
src="https://github.com/user-attachments/assets/2db0bb77-bbde-4617-9ed2-483cdd396a53"
/>



## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming asks for an email one-time code, then calls
`KycController.deleteEncryptedStorage({ aal2Token })` with that
verification token. That requires `@metamask/kyc-controller` 0.16.0 and
the `KycService:createDeletion` and `KycService:completeDeletion`
messenger actions. Cancelling the confirmation, or backing out of the
email check, leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: MetaMask#38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    And I complete the email one-time code check
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted

  Scenario: backing out of email verification leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and confirm
    And I back out of the email one-time code check
    Then nothing is deleted and no error is shown
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

N/A

## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a
href="https://cursor.com/agents/bc-6f157964-72b0-5445-87a7-0edda2664e74?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/background-agent?bcId=bc-6f157964-72b0-5445-87a7-0edda2664e74&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"
src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Introduces user-triggered deletion of encrypted KYC data with MFA
gating; mistakes could affect identity verification state, but scope is
limited to customers with an active session and the feature flag.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
23be80c. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
runway-github Bot pushed a commit that referenced this pull request Nov 16, 2026
…#39037)

## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming calls
`KycController.deleteEncryptedStorage()`. That requires
`@metamask/kyc-controller` 0.15.0 and the `KycService:createDeletion`
and `KycService:completeDeletion` messenger actions. Cancelling the
confirmation leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

<img width="444" height="919" alt="Screenshot 2026-11-06 at 12 54 42 PM"
src="https://github.com/user-attachments/assets/3f8afa12-1926-40ce-93d5-496623d0e8bf"
/>
<img width="443" height="895" alt="Screenshot 2026-11-06 at 12 54 50 PM"
src="https://github.com/user-attachments/assets/87c92809-76f2-44eb-ad2e-21719cb2af10"
/>
<img width="455" height="881" alt="Screenshot 2026-11-06 at 12 54 24 PM"
src="https://github.com/user-attachments/assets/2db0bb77-bbde-4617-9ed2-483cdd396a53"
/>



## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming asks for an email one-time code, then calls
`KycController.deleteEncryptedStorage({ aal2Token })` with that
verification token. That requires `@metamask/kyc-controller` 0.16.0 and
the `KycService:createDeletion` and `KycService:completeDeletion`
messenger actions. Cancelling the confirmation, or backing out of the
email check, leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    And I complete the email one-time code check
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted

  Scenario: backing out of email verification leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and confirm
    And I back out of the email one-time code check
    Then nothing is deleted and no error is shown
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

N/A

## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a
href="https://cursor.com/agents/bc-6f157964-72b0-5445-87a7-0edda2664e74?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/background-agent?bcId=bc-6f157964-72b0-5445-87a7-0edda2664e74&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"
src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Introduces user-triggered deletion of encrypted KYC data with MFA
gating; mistakes could affect identity verification state, but scope is
limited to customers with an active session and the feature flag.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
23be80c. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
runway-github Bot added a commit that referenced this pull request Nov 16, 2026
…#39037)

## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming calls
`KycController.deleteEncryptedStorage()`. That requires
`@metamask/kyc-controller` 0.15.0 and the `KycService:createDeletion`
and `KycService:completeDeletion` messenger actions. Cancelling the
confirmation leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

<img width="444" height="919" alt="Screenshot 2026-11-06 at 12 54 42 PM"
src="https://github.com/user-attachments/assets/3f8afa12-1926-40ce-93d5-496623d0e8bf"
/>
<img width="443" height="895" alt="Screenshot 2026-11-06 at 12 54 50 PM"
src="https://github.com/user-attachments/assets/87c92809-76f2-44eb-ad2e-21719cb2af10"
/>
<img width="455" height="881" alt="Screenshot 2026-11-06 at 12 54 24 PM"
src="https://github.com/user-attachments/assets/2db0bb77-bbde-4617-9ed2-483cdd396a53"
/>

## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming asks for an email one-time code, then calls
`KycController.deleteEncryptedStorage({ aal2Token })` with that
verification token. That requires `@metamask/kyc-controller` 0.16.0 and
the `KycService:createDeletion` and `KycService:completeDeletion`
messenger actions. Cancelling the confirmation, or backing out of the
email check, leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    And I complete the email one-time code check
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted

  Scenario: backing out of email verification leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and confirm
    And I back out of the email one-time code check
    Then nothing is deleted and no error is shown
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

N/A

## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a
href="https://cursor.com/agents/bc-6f157964-72b0-5445-87a7-0edda2664e74?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/background-agent?bcId=bc-6f157964-72b0-5445-87a7-0edda2664e74&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"
src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Introduces user-triggered deletion of encrypted KYC data with MFA
gating; mistakes could affect identity verification state, but scope is
limited to customers with an active session and the feature flag.
>
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
23be80c. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
runway-github Bot pushed a commit that referenced this pull request Nov 16, 2026
)

## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming calls
`KycController.deleteEncryptedStorage()`. That requires
`@metamask/kyc-controller` 0.15.0 and the `KycService:createDeletion`
and `KycService:completeDeletion` messenger actions. Cancelling the
confirmation leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

<img width="444" height="919" alt="Screenshot 2026-11-06 at 12 54 42 PM"
src="https://github.com/user-attachments/assets/3f8afa12-1926-40ce-93d5-496623d0e8bf"
/>
<img width="443" height="895" alt="Screenshot 2026-11-06 at 12 54 50 PM"
src="https://github.com/user-attachments/assets/87c92809-76f2-44eb-ad2e-21719cb2af10"
/>
<img width="455" height="881" alt="Screenshot 2026-11-06 at 12 54 24 PM"
src="https://github.com/user-attachments/assets/2db0bb77-bbde-4617-9ed2-483cdd396a53"
/>



## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## **Description**

<!-- mms-check: type=text required=true -->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

Customers who have started identity verification can delete the
encrypted identity data MetaMask holds from Security settings, without a
separate screen.

The section appears only when the money-account flag is on and a KYC
session exists. Confirming asks for an email one-time code, then calls
`KycController.deleteEncryptedStorage({ aal2Token })` with that
verification token. That requires `@metamask/kyc-controller` 0.16.0 and
the `KycService:createDeletion` and `KycService:completeDeletion`
messenger actions. Cancelling the confirmation, or backing out of the
email check, leaves the data in place.

Performance checks do not apply: this is a static settings section with
no lists, polling, or animation. It has not been exercised on a device
yet.

## **Changelog**

<!-- mms-check: type=changelog required=true blocking=true -->

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Added a Security settings control to delete encrypted
identity verification data.

## **Related issues**

<!-- mms-check: type=issue-link required=true -->

Fixes:

Refs: #38381

## **Manual testing steps**

<!-- mms-check: type=manual-testing required=true -->

```gherkin
Feature: delete identity data from Security settings

  Scenario: the section stays hidden until verification has started
    Given the money-account feature flag is off or there is no KYC session
    When I open Security settings
    Then I do not see "Delete Identity Data"

  Scenario: confirming deletes the encrypted identity data
    Given the money-account feature flag is on and a KYC session exists
    When I open Security settings
    And I tap "Delete identity data"
    And I confirm "This cannot be undone."
    And I complete the email one-time code check
    Then the app deletes the encrypted identity data and reports success

  Scenario: cancelling leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and then cancel
    Then nothing is deleted

  Scenario: backing out of email verification leaves the identity data in place
    Given the delete section is visible
    When I tap "Delete identity data" and confirm
    And I back out of the email one-time code check
    Then nothing is deleted and no error is shown
```

## **Screenshots/Recordings**

<!-- mms-check: type=screenshot required=true -->

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

N/A

### **After**

N/A

## **Pre-merge author checklist**

<!-- mms-check: type=checklist required=true -->

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I've applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

#### Performance checks (if applicable)

- [x] I've tested on Android
  - Ideally on a mid-range device; emulator is acceptable
- [x] I've tested with a power user scenario
- Use these [power-user
SRPs](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [x] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and
[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance
Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- Generated with the help of the pr-description AI skill -->

<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a
href="https://cursor.com/agents/bc-6f157964-72b0-5445-87a7-0edda2664e74?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/background-agent?bcId=bc-6f157964-72b0-5445-87a7-0edda2664e74&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"
src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>


<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Introduces user-triggered deletion of encrypted KYC data with MFA
gating; mistakes could affect identity verification state, but scope is
limited to customers with an active session and the feature flag.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
23be80c. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Signed-off-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Sébastien Van Eyck <sebastien.vaneyck@consensys.net>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

INVALID-PR-TEMPLATE PR's body doesn't match template size-L team-money-movement issues related to Money Movement features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants