AllWomensTalk January 2016 Alleged Data Exposure

An independent 9GHz detail page lists both exact member names and all 23 source-authored CSV headers, including the explicitly named user_email field. LeakedSource lists a January 2016 event for the same domain. These bindings associate the archive with the event at high confidence, but no operator or regulator confirmation was located, so the record remains unverified.

Public counts conflict. 9GHz reports 200,258 records, while LeakedSource reports 116,310. Complete RFC4180 parsing found 198,205 logical CSV data records excluding the header; the 200,258 figure matches physical lines inflated by embedded line breaks in CSV fields. All 136,926 unique valid emails in the UTF-16 text member are contained in the CSV user_email set and add no new email. Across the archive, 280,709 valid occurrences resolve to 143,743 unique valid emails. The exact affected-person count is therefore left unset: 198,205 is only the logical record count of the complete CSV version, and 143,743 is a lower bound of unique valid emails. The 1 January date represents month-level precision for January 2016.

The import includes only valid emails from cells explicitly named user_email by the source header and a strict whole-cell scan across every field of the headerless UTF-16 member; the latter is fully contained in the CSV set. Names, usernames, passwords, mobile data, registration tokens, URL fields and all other data are excluded. Thirteen invalid at-sign cells in the UTF-16 member and fifteen invalid non-blank values in CSV user_email are rejected. An email match alone does not prove that a person used the site or that any other field belongs to that person.