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

Push Notification Device Identifier Retention

Medium severity Explicit document language Common · 274 of 352 platforms
Stay ahead of the changes
Track MetaMask and get the diff the day its terms change.
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

Clause Stability Stable

0
Changes
4
Months Monitored
Jul 10, 2026
First Seen
Jul 10, 2026
Last Seen
This clause type exists across 1629 other provisions on other platforms.

How other platforms handle this

Grindr Medium

In limited circumstances, we may retain certain information for purposes including safety, security, fraud prevention, and compliance with our legal obligations.

Palantir Medium

We collect and keep personal data only as needed or allowed for the purposes set out in this Statement, based on the reason we collected the personal data in the first instance and what is permitted under the laws that apply to the processing.

HubSpot Medium

We retain Personal Data that you provide to us where we have an ongoing legitimate business need to do so... When we have no ongoing legitimate business need to process your Personal Data, we securely delete the information or anonymize it...

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

Applicable regulations

GDPR
European Union
Indiana Consumer Data Protection Act
US-IN

Provision details

Document information
Document
MetaMask Privacy Policy
Entity
MetaMask
Document last updated
May 5, 2026
Tracking information
First tracked
May 7, 2026
Last verified
May 9, 2026
Record ID
CA-P-037673
Document ID
CA-D-00280
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
4cfbe9762731bfe658d18b0c1568e69aca6f8fd9ffe4429a18ab2c4903520ea6
Analysis generated
May 7, 2026 06:17 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: MetaMask
Document: MetaMask Privacy Policy
Record ID: CA-P-037673
Captured: 2026-05-07 06:17:26 UTC
SHA-256: 4cfbe9762731bfe6…
URL: https://conductatlas.com/platform/metamask/metamask-privacy-policy/provision/CA-P-037673/push-notification-device-identifier-retention/
Accessed: Aug. 18, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Get the research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.

Frequently Asked Questions

What does MetaMask's Push Notification Device Identifier Retention 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 274 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.