All Breaches
December 29, 2025 Verified Sensitive Record Dating

WhiteDate 2025 Data Breach

The WhiteDate data breach, in December 2025, was recorded as a sensitive incident affecting extensive personal and private communication data of users on the dating site.

20.4 Thousand
Reported Records
22
Data Types
Medium
Severity
Oct 9, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

3 sensitive22

About This Breach

The dataset included more than 20,000 unique email addresses; numerous fields were listed, such as usernames, IP addresses, private messages, profile photos, biography sections, physical attributes, relationship status, sexual orientation, income, education, family structure, and password hashes. Therefore, the record carries a high privacy risk even if the volume is small.

Leaked Data Types and Risks

The types of data listed in this record are Ages, Astrological signs, Bios, Device information, Education levels, Email addresses, Family structure, Forum posts, Genders, Geographic locations, Income levels, IP addresses, IQ levels, Nicknames, Passwords, Physical attributes, Private messages, Profile photos, Races, Relationship statuses, Sexual orientations, and Usernames. The scope of these fields makes this incident more sensitive than a typical dating account leak.

Private Life and Identity Matching Risk

The most important risk in the WhiteDate record is the combination of private life and identity information. When profile photo, username, email, private messages, relationship status, sexual orientation, and physical features are combined, it may be possible to match the user with their identity on different platforms. This information can be used for blackmail, harassment, social pressure, or targeted fraud.

Private Messages and Password Effect

The private messages area is particularly sensitive. Private conversations may contain information about users' relationships, preferences, expectations, or personal boundaries. Not every record may contain the same level of messages; however, listing this area requires considering the social and psychological safety of the affected users. If threat or disclosure messages are received, payment should not be made, and the messages should be saved.

The passwords field is associated with phpBB password hashes. A hash is not a plaintext password; however, weak or reused passwords can pose a risk. Affected users should immediately change their password if they use the same password they used on their WhiteDate account for other dating, email, social media, messaging, or payment accounts. The primary email account should be especially protected.

Location, Device and Sensitive Profile Areas

The fields of IP addresses, device information, and geographic locations can provide hints about the user's approximate location and access patterns. When combined with private messages and profile fields, this information makes it easier to target the individual. If users use the same nickname on other platforms, they should reduce the public profile information of these accounts.

Areas such as races, sexual orientations, income levels, family structure, and physical attributes are highly sensitive. This information can lead to inferences about the user's private life, identity, and social status. Affected individuals should take into account that messages containing personal details may originate from leaked data and should not act hastily.

Necessary Precautions

Affected WhiteDate users should end password reuse, strengthen email security, review other profiles using the same username, and isolate accounts in sensitive contexts from the rest of their digital identity. Threats claiming to be related to dating, relationships, photos, or private messages should not be responded to; if necessary, trusted support or official application channels should be used.

Long-Term Personal Security Risk

In the WhiteDate record, users need to make a personal safety plan as well as technical security. The leakage of sensitive dating data does not only create risks for spam or passwords; it can also put pressure on family, work, social environment, or personal relationships. If users receive threatening messages, they should not be alone, should seek support from trusted people, and, if necessary, turn to official application channels.

For institutions, this event shows that data minimization is mandatory on dating and social networking platforms. When areas such as sexual orientation, private messages, physical characteristics, income, and photos are stored for longer than necessary, the impact of the violation increases. Users should have open access to options for account deletion, message deletion, profile hiding, and data downloading.

Due to the large number of sensitive areas, WhiteDate registration carries a long-term profile matching risk. If the same photo, nickname, or email is used on other accounts, the privacy settings of these accounts should be strengthened and unnecessary publicly available information should be removed.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information