BeReal · BeReal Privacy Policy · View original document ↗

Advertiser Hashed Phone Number Audience Matching

Medium severity Medium confidence Explicitdocumentlanguage Unique · 0 of 352 platforms
Get alerted the next time BeReal changes these terms. Get same-day alerts →
Share 𝕏 Share in Share 🔒 PDF
Recent governance activity BeReal recorded 2 documented changes in the last 30 days.
Get same-day alerts →
Monitor governance changes for BeReal Monitor emails you the same day this changes. The archive stays free.
Get same-day alerts →

Get the weekly 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. No account.

Document Record

What it is

The policy states that advertisers may provide BeReal with hashed lists of their customers' phone numbers, which BeReal matches against hashed phone numbers in its user account database to identify which BeReal users to show that advertiser's ads to, with the hashed values from advertisers deleted after the matching process.

This analysis describes what BeReal'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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This provision establishes a custom audience matching workflow using hashed phone numbers as the matching identifier. The policy asserts that matched audience lists and BeReal user phone numbers are not disclosed back to advertisers, but the processing of user phone numbers for advertiser targeting purposes may constitute a 'sale' or 'sharing' under applicable U.S. state privacy laws, as acknowledged in Section 9.5.

Interpretive note: Whether this matching workflow constitutes a 'sale' or 'sharing' under specific state privacy laws depends on the applicable statutory definition and enforcement interpretation, which varies by jurisdiction.

Recent Activity

This document changed recently

Medium Jul 8, 2026

The updated policy now requires email address in addition to phone number, full name, and date of birth to create an account. BeReal discloses that it derives likely gender from your username, first name, and biography using AI, and uses this classification for internal targeting purposes. The policy also reveals that a randomized sample of 0.001% of users will have their interface interactions (touches and swipes) recorded through an analytics partner for up to 90 days to understand how users navigate the app; this practice does not apply in all geographic regions. You can review your app settings or contact BeReal to inquire about your data collection status.

View change record →

Clause Stability Stable

0
Changes
4
Months Monitored
Jul 9, 2026
First Seen
Jul 9, 2026
Last Seen

Consumer impact (what this means for users)

Under this provision, the phone number associated with a user's BeReal account may be used to match the user to an advertiser's customer list for the purpose of displaying that advertiser's ads to the user within the app. The policy states this matching uses hashed values and that user phone numbers are not disclosed to advertisers.

What you can do

⚠️ These actions may provide transparency or partial mitigation but may not fully address the underlying issue. Effectiveness varies by jurisdiction and individual circumstances.
  • Opt Out of Arbitration
    Open the BeReal app, navigate to 'Privacy' in settings, and select 'Modify my consents' to opt out of targeted advertising, which the policy states includes advertiser audience matching.

Cross-platform context

See how other platforms handle Advertiser Hashed Phone Number Audience Matching and similar clauses.

Compare across platforms →

Monitoring

BeReal has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 20 platforms.

Get Monitor Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
When an advertiser runs a campaign with us, it may provide us with a hashed (pseudonymized) list of phone numbers of its own customers. We match this list against hashed phone numbers associated with BeReal user accounts in order to display that advertiser's ads to the relevant users on BeReal. We do not receive phone numbers in clear text from advertisers, and hashed values provided for matching are not kept beyond the matching operation.

Excerpt from BeReal's Privacy Policy

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

REGULATORY LANDSCAPE: This provision implicates CCPA as amended by CPRA, and analogous U.S. state consumer privacy laws, given the policy's own acknowledgment in Section 9.5 that such activities may constitute a 'sale,' 'sharing,' or processing for 'targeted advertising.' GDPR's provisions on lawful basis for processing and data minimization are also relevant for EU users. The FTC has authority over unfair or deceptive data practices in this context. GOVERNANCE EXPOSURE: Medium. The policy discloses the matching workflow and states that hashed advertiser-provided values are not retained beyond the matching operation. However, compliance teams should assess whether the use of user phone numbers for advertiser audience matching, even in hashed form, triggers opt-in or opt-out requirements under applicable state law, and whether the current opt-out mechanism via app settings is operationally adequate and legally sufficient. JURISDICTION FLAGS: California residents have the right to opt out of sale and sharing under CPRA, and the policy commits to processing opt-out requests within 15 business days for California residents. Other U.S. states with consumer privacy laws imposing targeted advertising opt-out rights create similar obligations. EU/EEA users are subject to GDPR consent or legitimate interest requirements for this type of processing. CONTRACT AND VENDOR IMPLICATIONS: Advertiser data processing agreements should address the hashed matching workflow, data retention commitments (the policy asserts hashed values are not kept beyond the matching operation), and the boundaries of what is disclosed to advertisers post-match. Procurement teams should assess whether this workflow is conducted in-house or via a third-party identity resolution or clean room provider. COMPLIANCE CONSIDERATIONS: Compliance teams should verify that the opt-out mechanism for sale, sharing, and targeted advertising in the app's Privacy settings operates to exclude user phone numbers from advertiser matching workflows, and should document the technical implementation of hashed value deletion post-match. Data mapping should reflect phone numbers as a data element used in advertising-related processing.

Full institutional analysis
Regulatory citations, enforcement risk, and due diligence action items.
Start Insight · $19.99/mo Start with Monitor · $4.99/mo

Applicable agencies

  • FTC
    The FTC has authority over unfair or deceptive advertising and data practices, including the use of consumer phone numbers for advertiser audience matching.
    File a complaint →
  • State AG
    State attorneys general enforce CCPA and analogous state consumer privacy laws governing sale, sharing, and targeted advertising opt-out rights implicated by this matching workflow.
    File a complaint →

Provision details

Document information
Document
BeReal Privacy Policy
Entity
BeReal
Document last updated
May 5, 2026
Tracking information
First tracked
July 9, 2026
Last verified
July 9, 2026
Record ID
CA-P-014995
Document ID
CA-D-00250
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
1bcaea508b2d4d3072f172a6021b5cb0ecb6214987a133d040c2ca03aa9f8663
Analysis generated
July 9, 2026 06:54 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: BeReal
Document: BeReal Privacy Policy
Record ID: CA-P-014995
Captured: 2026-07-09 06:54:13 UTC
SHA-256: 1bcaea508b2d4d30…
URL: https://conductatlas.com/platform/bereal/bereal-privacy-policy/provision/CA-P-014995/advertiser-hashed-phone-number-audience-matching/
Accessed: July 24, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Governance intelligence across arbitration, AI governance, data rights, indemnification, and retention
Provision-level monitoring, governance timelines, and regulatory mapping built from archived source documents and historical version tracking.
Start Insight · $19.99/mo Start with Monitor · $4.99/mo

Frequently Asked Questions

What does BeReal's Advertiser Hashed Phone Number Audience Matching clause do?

This provision establishes a custom audience matching workflow using hashed phone numbers as the matching identifier. The policy asserts that matched audience lists and BeReal user phone numbers are not disclosed back to advertisers, but the processing of user phone numbers for advertiser targeting purposes may constitute a 'sale' or 'sharing' under applicable U.S. state privacy laws, as acknowledged in …

How does this clause affect you?

Under this provision, the phone number associated with a user's BeReal account may be used to match the user to an advertiser's customer list for the purpose of displaying that advertiser's ads to the user within the app. The policy states this matching uses hashed values and that user phone numbers are not disclosed to advertisers.

Is ConductAtlas affiliated with BeReal?

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