Description

Part 2/4 of #25767 — Code owner: mobile-core-ux

Depends on: split 1-4 (mobile-platform) — must merge after it.

Switches DeleteMetaMetricsData component from useMetrics to the new useAnalyticsDataDeletion hook for deletion methods and useAnalytics for tracking. This decouples the Settings UI from the MetaMetrics singleton for data deletion concerns.

What changed:

• DeleteMetaMetricsData.tsx — replaced useMetrics() with useAnalyticsDataDeletion() + useAnalytics(). No behavioural change.
• MetaMetricsAndDataCollectionSection.test.tsx — simplified MetaMetrics mock by removing unused deletion method stubs.

Changelog

CHANGELOG entry: null

Related issues

participates to fix:

• Refactor: Move analytics data deletion out of MetaMetrics into dedicated util and hook #25767
• https://consensyssoftware.atlassian.net/browse/MCWP-297

Manual testing steps

Feature: Delete MetaMetrics data from Settings

  Scenario: user views deletion status
    Given the user is on Settings > Security & Privacy > Delete MetaMetrics Data
    When the screen loads
    Then the current deletion status is displayed correctly

  Scenario: user initiates data deletion
    Given the user is on the Delete MetaMetrics Data screen
    When user taps the delete button
    Then a deletion regulation is created
    And the UI updates to reflect the pending deletion

Screenshots/Recordings

N/A — no visual changes, only hook wiring.

Before

N/A

After

N/A

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• 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.