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

Advertiser Hashed Phone Number Audience Matching

Medium severity Medium confidence Explicit document language Unique · 0 of 352 platforms
Stay ahead of the changes
Track BeReal and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF
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
5
Months Monitored
Jul 9, 2026
First Seen
Jul 9, 2026
Last Seen

Change history

added Aug 1, 2026

Introduces new practice of matching advertiser customer lists against user phone numbers, enabling highly targeted advertising based on external customer data.

View full change record →

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 →
▸ 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.

Insight

Unlock the full institutional analysis

Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.

Applicable agencies

  • Federal Trade Commission (ftc)
    Oversees unfair or deceptive business practices and can investigate companies that mislead consumers about data collection, sharing, or use.
    Who can file: Anyone affected by the company's practices (US or international)
    What you need: Your account details, a timeline of relevant events, and a description of the specific issue
    What to expect: Complaints inform FTC enforcement priorities and investigations but do not result in individual resolution or compensation
    File a complaint →
  • State Attorney General
    State AGs in California, New York, Texas, and other states can investigate violations of state consumer protection and privacy laws, including CCPA (California), SHIELD Act (New York), and equivalents.
    Who can file: Residents of states with comprehensive privacy laws — primarily California, Virginia, Colorado, Connecticut, and Utah
    What you need: Evidence of the violation, explanation of how your state rights were affected, and your account or contact information with the company
    What to expect: Outcomes vary by state. May result in investigation, enforcement action, or requirement for the company to change practices. No direct individual compensation in most cases.

    Search "[your state] attorney general consumer complaint" to find your state's direct complaint form

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: Sept. 8, 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 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.