Provision record
MetaMask · MetaMask Privacy Policy · View original document ↗

Device identifier retained for push notifications while opted in

Common · 285 of 343 platforms
Stay ahead of the changes
Track MetaMask and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

This analysis describes what MetaMask's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

How other platforms handle this

Kling AI

When you use our Services, we may automatically collect your Data including IP address, operating system, browser you are using, your Account's preference settings, advertising identifiers, WiFi/WLAN Bluetooth, mobile network information...

Postman

We collect information about the device you use to access our Services, including the type of device, connection type, device settings, operating system, browser type, IP address, URLs of referring/exit pages, device identifiers, and crash data.

Ford

When Connected Vehicle Information is transmitted from the vehicle, it is generally associated with a VIN or other unique identifiers, and the VIN or other unique identifiers can be linked to you.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
if you opt-in and ask us to provide push notifications to your mobile device, we will retain your device identifier to facilitate such notifications for as long as you remain opted-in.

Excerpt from MetaMask's Privacy Policy

Provision details

Document information
Document
MetaMask Privacy Policy
Entity
MetaMask
Date stated by the document
Sept. 30, 2026
As printed in MetaMask’s text (version CA-V-007259), not a ConductAtlas date.
Tracking information
First captured by ConductAtlas
April 19, 2026
Text quoted from version
CA-V-007259, captured Oct. 1, 2026
Record ID
CA-P-078135
Document ID
CA-D-000280
Evidence Provenance
Source URL
Wayback Machine
Archived bytes SHA-256 (version CA-V-007259)
5b0eed5ee280bbc9f28f5e611f7ed449e072340d280992f9b26ff593e37274aa
Analysis generated
May 7, 2026 06:17 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-007259, captured Oct. 1, 2026 (checked Oct. 5, 2026)
Citation Record
Entity: MetaMask
Document: MetaMask Privacy Policy
Record ID: CA-P-078135
Version: CA-V-007259
Captured: 2026-10-01 00:45:45 UTC
SHA-256: 5b0eed5ee280bbc9…
URL: https://conductatlas.com/platform/metamask/metamask-privacy-policy/provision/CA-P-078135/device-identifier-retained-for-push-notifications-while-opted-in/
Accessed: Nov. 17, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

Related Analysis

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Frequently Asked Questions

What does MetaMask's Device identifier retained for push notifications while opted in clause do?

The clause states: “if you opt-in and ask us to provide push notifications to your mobile device, we will retain your device identifier to facilitate such notifications for as long as you remain opted-in.”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 285 platforms. See the full comparison.

Is ConductAtlas affiliated with MetaMask?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by MetaMask.