rlglawfirm.com

File structure

Notes: The file is a free-form financial statement / balance sheet with no consistent columnar structure. It contains embedded names in trust account entries (e.g., "Barone, Helen", "Gardner, James", "Weber, Frank"), but these appear within narrative descriptions rather than as discrete columns. The data lacks a uniform delimiter or header row, and values are highly variable across lines. This matches the unstructured opt-out criteria: no consistent delimiter, variable line shapes, and embedded PII in prose format.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file contains purely financial statements and balance sheet data without any personal identifying information (PII). There are no columns that map to email, phone, name, address, DOB, SSN, password, username, or other PII fields. All entries are account names (e.g., 'Client Trust Account Barone, Helen'), amounts, and financial categories. No structured PII columns exist.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 28 total columns. Only columns 1, 7, 11, and 19 contain PII (names and addresses). All other columns are internal identifiers, dates, transaction amounts, or status codes and are safely skipped per rules.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 28 columns total, 6 contain PII (fullName and 5 address fields). All other columns are internal identifiers, dates, transaction amounts, or status flags and are skipped per rules. No email, phone, DOB, SSN, gender, suffix, or username data present.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 28 total columns; only 3 contain PII. Columns 7, 11, and 1 contain full addresses and entity names. All other columns are internal IDs, financial amounts, dates, or status codes (skip).

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 28 total columns, 7 contain PII (fullName and multiple address fields). All other columns represent internal identifiers, financial amounts, dates, and status codes — none contain personal PII. The 'Name' column contains entity names which may include principal names and therefore maps to fullName.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 50 rows shown; column 0 appears to be an LLC/SPE identifier and is skipped. Column 2 contains notes/status and is skipped. Column 4 is empty across all rows and is skipped. The file is a structured CSV with headers, and columns 1 and 3 contain clear PII (full names and addresses).

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file contains no structured PII columns. It appears to be a list of LLC entities with principal names embedded in free-text fields, but there is no consistent column mapping to PII fields. The data is unstructured with names appearing in a free-text format within quotes, but lacks a predictable column structure for mapping to PII fields. Given the format, this should be treated as unstructured data for further processing.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file is a structured CSV, but the data appears to be business entity records rather than individual PII. Columns contain entity names, notes, and addresses, but these do not map to personal PII fields. No email, phone, DOB, SSN, or username fields are present. Addresses appear to be business addresses rather than personal residential addresses. Therefore, no PII columns to map.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a corporate LLC ownership list. Column 1 contains principal names (fullName). Column 3 contains physical addresses (address1). Other columns are empty or contain internal identifiers (SPE #X, LLC) which are skipped per rules.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a CSV with header row indicating structured data. Columns 0 and 2 appear to be entity names and notes respectively and do not contain PII. Columns 1, 3, and 4 contain full names and address information, mapped accordingly. All other columns are empty or contain non-PII metadata and are skipped.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a CSV file listing LLC entities and their associated principal names and addresses. Columns 0 and 1 contain LLC names and principal names respectively. Column 4 contains detailed address information including street, city, state, and ZIP code. No emails, phone numbers, DOB, SSN, or other PII fields are present in the first 50 rows.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a list of LLC entities with principal names and partial addresses, but lacks consistent PII columns. The format shows entity names in column 0, principal names in column 1, notes in column 2, and addresses in column 3 and 4. However, the addresses are incomplete and not consistently formatted. There are no clear email, phone, dob, ssn, password, username, or other PII fields present. The data appears to be corporate/legal entity information rather than individual personal data. Based on the sample, there are no mappable PII columns.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: 50 rows shown; columns 0 and 2 appear to be LLC names and empty fields respectively. Columns 1-6 contain PII: full names and complete addresses (street, city, state, zip). No emails, phones, DOB, SSN, or passwords visible in this sample.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a structured CSV but contains only business entity names and internal notes. No identifiable personal information (PII) is present in the first 50 rows. Columns such as 'SPE, LLC LOG', 'NOTES', and 'ADDRESSES' do not contain any personal names, addresses, or other PII fields. All entries are corporate entity identifiers or internal commentary, thus no PII columns to map.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a CSV list of LLC entities with principal names and addresses. Column 0 contains LLC names (not PII), column 1 contains full names, and column 2 contains full addresses. All other columns are empty and contain no PII.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only columns 0 (lastName) and 1 (firstName) contain PII. Other columns contain case metadata (filings, case numbers, dates, venues) which are not personally identifiable. No email, phone, DOB, address, or SSN fields present in the sample.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only columns 0 (fullName) and 2 (address1) contain PII. All other columns are internal case identifiers, dates, or empty fields that do not contain personal data. No emails, phones, DOB, SSN, or other PII fields detected in the first 50 rows.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 50 rows shown, 2 PII columns identified: fullName and address1. Column 1 (MATTER) contains legal matter types and is skipped. Other columns contain dates, amounts, and status flags which are not PII per exclusion rules.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file is a free-form listing of transactions and client names without a consistent columnar structure. It contains names that could be mapped to firstName/lastName, but the lack of a defined header or repeated delimiter pattern across rows means it fails the structured format test. Values like "TRESH SPE" and "SMITH, Sue" appear in free-form positions, and there is no reliable mapping to PII fields. The format is unstructured text with embedded names.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The file is a free-form list of transactions with no consistent column structure. It contains names (e.g., 'FREEMAN', 'AROYIAN', 'DIMARIA') but lacks any identifiable PII fields like emails, phone numbers, addresses, or DOBs. The data appears to be transaction records with names and fees, but without structured columns mapping to PII fields. Therefore, no PII columns can be mapped.

File structure

Notes: The file is a free-form text document with no consistent delimiter or row structure. It appears to be a printed list or report from a law firm with no machine-readable columnar data. All values are presented in prose format with no identifiable column indices or headers. While it contains names and amounts, they are embedded in narrative text rather than structured fields.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file appears to be a structured CSV but contains only headers and empty rows with no actual PII data present in the first 50 rows. The headers indicate potential columns like 'NAME', but no values are populated. No PII fields can be mapped based on the provided data.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a free-form tabular file with no header row and inconsistent column usage. Columns appear to represent transaction/exchange data (names, fees, referrals) but lack consistent PII patterns across rows. No columns reliably map to PII fields (email, phone, dob, etc.). Values contain names but these are likely business entity names rather than personal identifiers. No structured PII columns detected.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file contains only corporate/legal entity names and internal reference numbers. No personal PII fields are present. All entries appear to be business entities, SPE numbers, and internal codes with no identifiable individual names, addresses, or other PII. The values are corporate names, SPE identifiers, and numeric codes only.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: All columns contain financial/accounting data (dates, monetary amounts, transaction types). No PII fields present. Columns map to internal accounting records, not personal identifying information.

File structure

Notes: Pre-LLM auto-detection: free-form text with visible emails / phones

File structure

Notes: Pre-LLM auto-detection: free-form text with visible emails / phones

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only columns 0 (fullName) and 2 (address1) contain identifiable PII. All other columns either contain internal codes, empty values, or non-PII metadata (matter descriptions, dates, flags). No emails, phones, DOB, SSN, or other PII fields detected in the first 50 rows.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 50 rows shown, PII identified in fullName (column 0) and address1 (column 3). Other columns contain case types, dates, amounts — no additional PII detected in this sample.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only address-related PII fields identified. No email, phone, name, SSN, or DOB fields present in the sample. All other columns are internal financial identifiers, flags, or amounts (skipped).

File structure

Notes: This is unstructured free-form text. The sample shows only numbers and no consistent delimiter or row structure. There are no visible emails or phone numbers in the sample, but the file format is clearly not tabular. Since there is no consistent delimiter and lines vary in length/content, we classify this as unstructured text with no column mapping.

File structure

Notes: The file appears to be free-form text with financial analysis data rather than structured PII records. The content shows financial calculations, revenue/expense breakdowns, and tiered values without any identifiable personal information fields. No consistent column structure exists across rows, and all entries are financial figures and descriptions rather than personal data.

File structure

Notes: free-form text with embedded names and contact details

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file is NOT structured tabular data with consistent columns. It appears to be a list of names and entities with no consistent delimiter or column structure. The values appear to be free-form entries (names, company names, etc.) with inconsistent formatting and no header row. Since there is no consistent column structure and the data appears to be free-form text listings, this should be treated as unstructured data. However, because there is no clear evidence of emails or phone numbers in the sample (only names and entity names), and the data lacks the variability expected in unstructured free-form text, we cannot classify it as unstructured opt-out. Instead, this appears to be a malformed or poorly structured CSV where the first column is an identifier and the second contains names/entities. But without a clear delimiter pattern or header, column mapping is impossible. Given the instructions, this should be treated as having no importable PII columns because the data lacks structure to map to known PII fields.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file is unstructured and free-form. The lines are not consistently formatted with columns; they are instead entries with variable structures. Although names appear, they are not in a tabular format with consistent columns. The format is not CSV and should be processed as unstructured text.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a simple two-column list with FILE # and NAME fields. The NAME column contains only single last names or entity names with no additional PII (no addresses, emails, etc.). No identifiable PII fields (email, phone, dob, etc.) are present. The data appears to be a directory of clients or entities without personal contact details.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only corporate/LLC client names and status codes with no personal PII fields. All values represent business entities (e.g., 'Radcliffe', 'V.M. Calderon, Inc. SPE #68'), transaction statuses, and timestamps. No email, phone, address, or other PII fields are present.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a structured CSV file but contains NO PII fields. All columns represent business/client entity names, status codes, dates, and internal tracking information. No email addresses, phone numbers, SSNs, or other personal identifiers appear in the sample. The values are corporate names, SPE identifiers, status flags, and ISO timestamps — all fall under business metadata rather than personal PII.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only internal corporate/LLC identifiers and entity names (EX NO. and NAME). No PII fields are present. The NAME column contains business entity names and legal entity designations, which are not personal PII according to the exclusion rules. Therefore, no columns map to PII fields.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is not a PII file. It contains only entity names and EX NO. identifiers. No personal fields like names, emails, or addresses are present. The values are all corporate/LLC names or numeric identifiers. According to the exclusion rules, company/business names are skipped, and internal IDs (EX NO.) are skipped. Therefore, there are no PII columns to map.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 12 columns total, 6 contain PII. Columns 2 (TITLE) contains honorific prefixes (Mr., Ms.) and is skipped. Columns 3,5,9,10,11 appear empty or non-PII and are skipped.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 11 total columns; mapped 6 PII columns. Column 2 ('TITLE') contains honorifics (Mr., Mr. and Ms.) and maps to skip. Column 3 ('OTHER') contains non-standard data and maps to skip. Columns 5, 9, and 10 are empty and map to skip.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 12 total columns; 6 contain PII. Columns 2 (TITLE) contains honorifics/prefixes and is skipped per rules. Columns 3, 5, 9, 10, 11 are empty or non-PII and skipped.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Columns 2 (TITLE) contains honorifics/prefixes (Mr., Mr. and Ms.) which are NOT PII. Columns 3 (OTHER), 5 (ADDRESS - 2), 9, and 10 are empty or non-PII. No emails, phones, DOB, SSN, or passwords detected.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a simplified client list with name and phone number columns. The 'COMMENTS' column contains occasional notes but no PII. No other columns contain PII.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Header row present, columns 0 and 1 contain full names and phone numbers respectively. Column 2 contains non-PII comments/status flags.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a structured CSV with 3 columns. Columns 0 and 1 contain PII (fullName and phone). Column 2 ('COMMENTS') contains notes and is skipped. The data appears to be a seminar attendee list with names and phone numbers.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 50 rows total, 2 PII columns (fullName, phone). Column 2 ('COMMENTS') contains non-PII notes (company affiliations, event status). File appears to be a simple client contact list from RLG Law Firm's 1031 Exchange Seminar event on April 12, 2005. All names are human clients/realtors, not corporate entities.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Columns 2 (COMMENTS) contain notes/status flags and are non-PII. The file is a simple client list with names and phone numbers only.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 30 rows, columns 0 and 1 contain fullName and phone. Column 2 contains non-PII comments/status flags (ex: 'REALTOR', 'CANCELED', 'GOOD CHOICE MORTGAGE') and is skipped. No email, dob, address, or other PII present in sample.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a structured CSV with headers 'NAME' and 'PHONE #'. Only two columns contain PII: full names and phone numbers. The third column 'COMMENTS' contains non-PII designations like 'REALTOR' or 'BROKER' and is skipped. All rows follow the same pattern.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a structured CSV file with columns for full name and phone number. No other PII columns are present in the first 50 rows.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only columns 0 and 1 contain PII. Column 2 ('COMMENTS') contains status notes and is not PII. Rows 15-20 are empty or placeholder lines.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a structured CSV file with a header row. Column 0 contains full names, and column 1 contains phone numbers. All other columns either contain comments or are empty and do not contain PII.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: CSV with header row. Column 2 contains comments/status codes (non-PII). Only columns 0 and 1 contain PII (fullName, phone).

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Structured CSV with 3 columns: NAME (fullName), PHONE # (phone), COMMENTS (skip). All rows contain valid PII in first two columns.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: CSV with three columns; only first two contain PII (fullName, phone). Third column is unstructured comments and contains no PII. No other rows shown contain additional PII beyond these two columns.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only columns 0 (fullName) and 1 (phone) contain PII. Column 2 ('COMMENTS') contains non-PII corporate/agency references and is skipped per rules.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a simplified client contact list from the RLG Law Firm breach. Column 2 (COMMENTS) contains non-PII notes and is skipped.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only two PII columns present: NAME maps to fullName, PHONE # maps to phone. All other columns contain non-PII metadata or are empty.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only columns 0 and 1 contain PII (fullName and phone). Column 2 ('COMMENTS') contains non-PII notes like 'VERIZON REALTY' and is skipped. Rows 6-20 are empty lines.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only columns 0 (fullName) and 1 (phone) contain PII. Column 2 contains non-PII notes/comments and is skipped.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only two PII columns present: fullName and phone. All other columns either empty or non-PII comments. File appears to be a simple contact list from the law firm breach with no complex structure.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only columns 0 (fullName) and 1 (phone) contain PII. Column 2 labeled 'COMMENTS' contains corporate references and is skipped per rules (company/business context).

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: CSV with 3 columns. Only columns 0 and 1 contain PII (fullName and phone). Column 2 labeled 'COMMENTS' contains non-PII notes or affiliations and is skipped.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a structured list of contacts from the RLG Law Firm breach. Column 0 contains full names, and column 1 contains phone numbers. Column 2 contains comments that may include additional context but does not contain PII. Empty rows and headers without data are skipped.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only columns 0 and 1 contain PII (fullName and phone). Column 2 ('COMMENTS') contains status flags like 'CANCELED' and is skipped. No other rows contain structured PII beyond these two fields.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a simplified client list with name and phone number columns. The COMMENTS column contains internal status flags and is not PII. The file appears to be a legacy client seminar attendee list from 2005.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a minimal PII CSV with only name and phone columns. All other columns are either empty or non-PII notes/status flags.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only columns 0 (fullName) and 1 (phone) contain PII. Column 2 (COMMENTS) contains non-PII notes like 'SUNCOAST HOME EQUITY' and is skipped. No other PII fields detected in the first 50 rows.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a simple CSV with two PII columns: fullName and phone. The 'COMMENTS' column is empty and contains no PII. The file appears to be a client list from RLG Law Firm with personal contact information.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Simple CSV with two PII columns: fullName and phone. No other PII detected in the first 50 rows. The 'COMMENTS' column is empty and contains no PII.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Structured CSV with 3 columns; first row is header. Column 2 ('COMMENTS') contains non-PII notes. Rows 6-20 are blank data rows.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: CSV with three columns: NAME, PHONE #, COMMENTS. Only NAME and PHONE # contain PII. COMMENTS column is empty and contains no PII. Data appears to be a client list from RLG Law Firm breach with personal contact information.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The provided rows appear to be empty or placeholder lines with no actual data. There are no visible PII values or structured columns to map. The file seems to be an incomplete or template file with no meaningful content for analysis.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: File appears to be a contact list from RLG Law Firm breach. Column 0 is a sequential counter (skip). Column 2 contains phone numbers. Column 3 contains occupational/professional titles (Realtor, Appraiser, Mortgage Lender) which are non-PII descriptors and should be skipped. No email addresses, addresses, DOB, SSN, or other structured PII fields are present in this sample.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: CSV with three PII columns: first name, last name, and phone number. All rows follow the same pattern. No additional PII detected in visible columns.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: File contains simple name + partial phone number pairs. No email, DOB, SSN, or address fields visible in the first 30 rows. All rows follow consistent 3-column structure; empty trailing columns suggest this is a truncated export.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file appears to be a simple list of individuals with names and phone numbers. No other PII fields such as email, address, or SSN are present in the first 50 rows.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: 3-column file with record IDs in column 0 (skip), names in column 1, and phone numbers in column 2. Columns 3+ are empty. Data appears to be a client/contact list from RLG Law Firm breach.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The file appears to be a CSV with no header row and contains only empty or placeholder values across all columns for the first 30 rows. No PII fields are present in the visible data. The structure suggests this may be a template or placeholder file rather than actual breach data. All columns appear to be empty or contain only commas with no meaningful content to map to PII fields.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The file appears to be a simple CSV with no header row. Columns 1 and 2 contain full names and phone numbers respectively. All other columns either contain empty values or non-PII data such as job titles or are completely empty.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The file appears to be a CSV with no header row and contains only empty or placeholder values across all columns for the first 30 rows. No PII data is present in the provided sample, and there are no identifiable columns that map to PII fields. The structure shows empty rows with commas but no meaningful data to analyze for PII mapping.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The file appears to be a simple CSV without a header row. Columns 0, 1, and 2 map to firstName, lastName, and phone respectively. The remaining columns are empty or undefined.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is an unstructured CSV with empty rows and no header. All rows are blank except the first which appears to be a comment or placeholder. No PII fields can be identified. The file appears to be a placeholder or empty data dump from the breach.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: Rows contain full names and phone numbers. Third column appears to be occupation (Realtor) or blank, not PII. No email, dob, address, or other PII fields visible.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: CSV file with no header row. Columns 1 and 2 contain fullName and phone respectively. All other columns appear empty or undefined in the sample.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: 3 columns total; column 0 is internal counter (skip); column 1 contains full names of law firm clients/contacts; column 2 contains phone numbers. Rows 10-30 are empty. Data aligns with RLG Law Firm breach context—principal names and contact information from client records.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The file appears to be an empty CSV with no data rows beyond the initial placeholder lines. All rows up to index 30 contain only empty or placeholder values, and no PII fields are present. Since there is no structured data with identifiable columns, no PII mapping can be performed.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: Law firm client/contact list with 15 populated records and 15 empty rows. Column 0 is internal sequential ID. Column 1 contains full names. Column 2 contains phone numbers in XXX-XXXX format (likely partial/extension format given law firm context). Column 3 contains occasional company affiliations or titles—these are descriptive tags, not PII fields, so mapped to skip.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: CSV file with no header row. Column 0 is an unused index number. Columns 1 and 2 contain full names and phone numbers respectively. All other columns are empty or unstructured notes and can be skipped.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: 30 rows with 3 columns. Columns 1 and 2 contain PII (fullName and phone). Column 3 contains job titles and is skipped.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: 3 columns total, 2 contain PII (fullName, phone). Column 0 is a record counter. Rows 10–30 are empty. Data appears to be a simple contact list from RLG Law Firm (law firm clients, officers, or associates).

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The provided rows show only empty or placeholder data with no meaningful content. There are no identifiable columns or PII fields in the first 50 rows. The structure appears to be a CSV with empty values, possibly a template or placeholder file. No PII can be mapped from this sample.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: Data is a delimited list of individuals with full names and phone numbers, likely a client or contact list from RLG Law Firm. Column 0 appears to be a row counter (1–30). Column 3 is sparse (only one value 'CPA' at row 19, which is a credential/title suffix, not consistently populated as a separate field — treated as part of name or skipped). Rows 21–30 are empty. 19 records with PII extracted.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a CSV file with no header row. Columns 0 and 1 contain full names, and column 2 contains phone numbers. Rows 9–30 are empty or partially empty, but PII is clearly present in the first 8 rows.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file appears to be a CSV with no header row and empty data rows. All columns are empty, so no PII can be identified. The structure suggests it may be placeholder or template data from the breach, but without any actual content to analyze. No columns map to PII fields.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The provided rows are empty except for the header row, which does not contain any data. Therefore, no PII fields can be identified or mapped.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: CSV with 3 columns: Name (fullName), Phone (phone), Notes (skip). No other PII present in sample. Notes column contains empty strings and a single non-PII value ('Realtor').

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: CSV file with 3 columns. Columns 0 and 3 are empty/unused. Only columns 1 (fullName) and 2 (phone) contain PII.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only two columns appear to be PII-related: Name and Phone. All sample rows are empty for these columns. File appears to be a sparse client list with minimal data populated.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File appears to be a seminar attendee list ('1031 Exchange Seminar 3-15-05'). Column [0] is a row counter (1–30), column [3] is 'Notes' (contains descriptors like 'Realtor') and is non-PII. 30 records with names and partial phone numbers exposed.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only columns 1 and 2 contain PII (fullName and phone). Column 0 is an index, column 3 is notes (no PII).

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: CSV file with 3 columns. Columns 0 is an empty index column. Columns 1 contains full names and column 2 contains phone numbers. Column 3 is notes and appears to be empty in the sample data.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a simple CSV with three columns: first name, last name, and phone number. All rows contain personal contact information. The empty cells in columns 0-2 after row 16 are treated as valid rows with missing PII values.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: File contains 3 columns total. No header row. Rows 10-30 are empty padding. 9 data rows with names and phone numbers associated with individuals, consistent with law firm client/contact records from the RLG Law Firm breach.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: File contains 3 columns; column 3 (index 3) is empty/sparse and provides no PII value. Data appears to be a list of individuals (likely clients or associates of RLG Law Firm) with names and phone numbers. No email, address, DOB, SSN, or other detailed PII fields present in this sample.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The file appears to be an empty or placeholder CSV with no data rows containing PII. All rows are empty aside from row indices. No PII fields can be mapped.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a simplified CSV with three visible columns. Column 0 appears to be a row number and is skipped. Column 1 contains full names, Column 2 contains US phone numbers, Column 3 contains non-PII professional titles or is blank. No email addresses, DOB, SSN, or address fields are present in the visible data.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: CSV with two PII columns: fullName (column 1) and phone (column 2). Column 0 is an unused row index. No email, address, or other PII present in sample.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The provided data appears to be a CSV file with no headers and only empty or placeholder values across the first 30 rows. There are no visible PII fields in the sample data. The structure lacks any identifiable personal information such as names, addresses, emails, or other sensitive data. Given the context of the RLG Law Firm breach, this may be a template or placeholder file, or the sensitive data may appear later in the file beyond row 30. No columns can be mapped to PII fields based on the current sample.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: File is a delimited list (CSV-like) with 3 columns: an index/counter (column 0, skip), full names (column 1, PII), phone numbers (column 2, PII), and a third column with role/reference info (column 3, skip — non-PII metadata like 'Realtor', 'Realtor Ref'). Rows 21–30 are empty. This appears to be a contact or client list from RLG Law Firm with principal names and phone numbers.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: File contains 30 rows of law firm client/contact data. Row 0 is header-like counter. Rows 1-18 contain structured name + phone pairs (likely principal/officer names from corporate/LLC entities per breach context). Rows 19-30 are empty trailing records. No email, address, DOB, SSN, or other PII fields present in this sample.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: 3-column delimited file, no header row. Rows 15-30 are empty. Data appears to be a contact list from RLG Law Firm with names and phone numbers. Column 0 is a sequential counter (skip). Columns 1-2 contain PII.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The provided rows appear to be empty or contain only commas with no actual data. There are no visible PII values or structured columns to map. The file seems to be a template or placeholder with no meaningful content in the first 50 rows.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: File contains sparse PII records for individuals associated with RLG Law Firm. Most rows are empty. Column 0 is a row counter/internal ID (skip). Column 1 contains full names. Column 2 contains phone numbers. Column 3 contains generational indicators (Son/Father). No email, address, or DOB data present in sample.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: 5 columns total, 2 contain PII (fullName, phone). Record 11-12 share same phone (630-303-4040), as do other paired entries, suggesting spouse/co-principal relationships in law firm client data. Rows 17-30 are empty. File appears to be client principal names and contact phone numbers from RLG Law Firm database.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The provided rows appear to be empty or contain only commas with no actual data. There are no visible PII values or structured columns to map. The file seems to be either a template or corrupted data with no meaningful content for analysis.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The provided rows show only empty or placeholder data with no discernible structure or PII content. All rows appear to be blank or contain only commas, indicating either an empty file segment or placeholder rows. No columns can be mapped to PII fields based on this sample.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: Law firm client/contact list with minimal columns. Rows 14-30 are empty. Column 0 is a simple counter, not a meaningful identifier. The file contains names and phone numbers of individuals associated with the law firm's clients and operations.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This appears to be a simple CSV list of names and phone numbers with no header row. Columns 0 and 1 contain first and last names respectively, and column 2 contains phone numbers. Empty columns beyond index 2 are not PII and should be skipped.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The sample provided is entirely empty rows and does not contain any meaningful data or column headers. Therefore, no PII columns can be identified or mapped.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: Sparse dataset with 30 rows, mostly empty after row 6. Columns 0–2 contain PII (record ID, full name, phone). Column 3 appears to be institution/account reference data. No headers provided; format inferred from content.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: Simple 3-column CSV with no header row. Contains 10 records of client/contact names and phone numbers from RLG Law Firm breach. Rows 11-30 are empty. Column 0 is a sequential counter (skip). Columns 1-2 contain PII.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: Rows 1-3 contain full name and phone number. Rows 4-30 are blank. No other PII detected in the first 50 rows.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is an unstructured data set with no PII columns. All rows appear to be empty or placeholder lines with no meaningful data. The file appears to be a template or placeholder file with no actual personal information exposed.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The provided data appears to be a CSV file with no headers and only empty or placeholder values across the first 30 rows. There are no visible PII fields or structured data in this sample. Given the context of a law firm breach, further rows likely contain PII, but this initial segment lacks any identifiable information. No columns can be mapped to PII fields based on this sample alone.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: CSV with three PII columns: firstName (0), lastName (1), phone (2). Column 4 contains non-PII values (e.g., 'Remax') and is skipped. Rows 6-30 are empty and contain no data.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The provided sample contains only empty rows and a header row with no meaningful column names or data. There are no visible PII fields in the sample rows. The structure appears to be a CSV with empty values for all columns in the first 30 rows. No columns can be mapped to PII fields based on this sample.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The provided sample shows only empty rows and a header-less structure with no actual data. All rows from 1 to 30 are empty except for row indices. Without any meaningful content or identifiable columns, no PII fields can be mapped. The file appears to be an empty or placeholder CSV.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The provided rows appear to be empty or placeholder rows with no actual data values. All rows contain only commas with no meaningful content, making it impossible to identify any PII fields or column mappings. The structure suggests a CSV file but lacks any usable data for analysis. Without actual data values, no columns can be mapped to PII fields.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: 4 columns total. File is a simple contact list from RLG Law Firm breach with names and associated phone numbers. Column 0 is a sequential record counter. Column 3 contains sparse metadata flags unrelated to personal identity.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: CSV file with 2 PII columns: firstName and phone. All other columns appear empty or contain non-PII data (e.g., 'Cancelled' status flag). No email, address, dob, or other PII present in first 50 rows.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The file appears to be a simple CSV with two PII columns: fullName and phone. All other columns are empty or contain no data.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: Rows 1 and 2 contain valid personal contact data. Rows 3–30 are blank. No email, DOB, address, or SSN data visible in the first 50 rows.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 28 rows total, 2 PII columns (name and phone). Column 3 contains email addresses in comments but is unstructured free-text — handled separately. No other PII detected in structured columns.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only columns 1 (fullName) and 3 (address1) contain PII. All other columns contain identifiers (SPE #, LLC #, etc.) or status flags (Relinquished/Replacement, Active/X), which are skipped per rules.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 50 rows of SPE client data. Column 1 contains full names (individuals or entities). Column 3 contains full mailing addresses (street, city, state, ZIP). Other columns are internal identifiers, status flags, or empty — mapped to skip per rules (company/business references, internal IDs).

File structure

Notes: This is free-form text with no consistent delimiter structure. Each line contains different types of information (property addresses, sellers, closing dates, sale prices, etc.) and appears to be a narrative or document listing rather than a structured dataset. The values shown are prose descriptions rather than tabular data, confirming this is unstructured content.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial tracking table with month-by-month balance columns (Jul-02 through Jun-03). All values are numeric strings representing monetary amounts. No PII fields present — columns contain only transaction dates, balance totals, and classification labels. The 'Classification' column appears to hold fiscal year end dates but lacks any personal identifiers.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file contains only company names, payment types, and amounts. There are no identifiable personal information fields (PII) such as names, addresses, emails, phone numbers, etc. The data appears to be a financial summary or ledger of payments made to various entities, including companies and individuals, but the individual names present (e.g., William K. Flynn, Louis E. Furlong) are not mapped to PII fields because the structure lacks consistent columns for firstName, lastName, etc., and the context indicates these are likely business payees rather than structured personal records. No email, phone, dob, ssn, or other PII fields are present.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a budget projection table with no identifiable personal information. The first column appears to be a label repeating the same text across rows, and the rest are month-by-month budget figures. There are no names, addresses, emails, phone numbers, or other PII fields in any column. The values are purely financial and project labels.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 8 columns total, 6 contain PII (firstName, lastName, address1, city, state, zip). Column 3 is empty and column 8 contains external PDF links, both skipped.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: CSV file with 8 columns. Columns 0 (Title) contains honorific prefixes (Mr., Mrs.) which are NOT a PII field and must be skipped per rules. Columns 1-2 contain first and last names. Columns 4-7 contain full mailing addresses (street, city, state, ZIP). Column 3 appears to be empty in the sample and likely contains URLs or other non-PII data — skipped. No email, phone, DOB, or SSN fields are present in this sample.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 8 columns total, 6 contain PII. The 'Title' column is an honorific prefix (Mr./Mrs.) and must be skipped. The fourth column contains document URLs, not PII. This dataset appears to be a client list from RLG Law Firm with principal names and addresses.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 8 columns total, 6 contain PII. 'Title' column contains honorific prefixes (Mr./Mrs.) and is excluded per rules. URL column is skipped as it contains external document links, not PII.

File structure

Notes: The provided data is unstructured text with no consistent delimiter or column pattern. Each row contains different free-form text entries and no identifiable PII columns can be mapped. The content appears to be informational notes and instructions rather than structured records with personal information.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: 5 columns total, 4 contain PII. Column 5 ('STATUS') contains transaction status codes and is skipped.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a CSV with a header row. It contains personal and sensitive information including full names, SSNs, DOBs, phone numbers, and addresses. The columns are clearly labeled and map directly to PII fields. The last two columns ('Number of Dependants:', 'Do you occupy the property YES NO') do not contain PII and are skipped.

File structure

Notes: free-form text with embedded questions and answer options, not structured tabular data

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a structured CSV file, but all columns appear to be internal financial/employment fields or placeholders (e.g., 'Seller-Employer', 'MONTHLY INCOME SELLER', 'TOTAL INCOME - EXPENSES ='). No PII fields (email, phone, name, address, etc.) are present. Columns like 'Seller's Signature' are placeholders for signatures, not actual PII. Therefore, no columns map to PII fields.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a list of real estate listings with property owners' names but no identifiable PII fields beyond full names embedded in quoted strings. No emails, phone numbers, DOBs, SSNs, or other PII are present. The names are part of property ownership records but are not mapped to any specific PII column type as defined. All columns are skipped per rules — they contain property/listing data, not personal contact or identity information.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File contains real estate broker/agent contact information with repeated entries. All phone numbers appear in various formats but consistently represent contact numbers. Email addresses show diverse domains including personal email services and corporate domains.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file appears to be a financial summary report with no personal identifiable information (PII). Columns contain buyer names (Baldwin, Coble, Troyer, etc.), file numbers, payment amounts, and totals — but these are business transaction identifiers and monetary values, not personal contact details, addresses, or other PII. The structure lacks any email, phone, DOB, SSN, or address fields. The buyer names are likely internal case or client identifiers rather than personal full names. Therefore, no PII columns map to the defined fields.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a structured CSV with business/client names and financial transaction data (buyer names, amounts, identifiers). No actual PII fields (email, phone, DOB, SSN, etc.) are present. The 'Buyer' column contains business entity names and client identifiers, which are excluded per rules (Company/Business names are skipped). No PII mapping possible.

File structure

Notes: This is a free-form table with no consistent delimiter or header structure. It appears to be a financial summary sheet with names, codes, and monetary values rather than personal PII fields. There is no identifiable PII in the rows (names appear to be business/client names, not personal names). No structured columns to map.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is not a PII-containing file. It appears to be a financial summary report with names used as identifiers (Buyer names like 'Ezcurra', 'North', etc.) and monetary values. There are no actual personal identifiers (email, phone, address, DOB, SSN) present. The structure shows transaction summaries and totals rather than personal data records. The names appear to be internal case identifiers or buyer references rather than full personal names with PII.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file contains only transaction and accounting data with names that appear to be business or entity names (Buyer, Hartin, Lannamann, etc.). There are no identifiable personal PII fields such as email, phone, or SSN. The structure is purely financial records with no personal contact details. All columns are skipped per rules (company/business names, financial amounts, internal IDs like file numbers).

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is not structured PII data; it's a financial summary report with names used as row labels (Buyer names), not personal contact details. No columns map to PII fields. The data appears to be aggregate financial totals for real estate closings (buyer names, file numbers, payment distributions) rather than individual personal records. The names are used as identifiers in a transactional context, not as personal contact information.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The lines contain transaction-like entries but lack a defined column pattern or header row. The content appears to be a summary of financial settlements or payments (e.g., names, identifiers, amounts), but it is not in a structured tabular format. Therefore, it is classified as unstructured for downstream processing.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial transaction report with buyer names (which could be individuals or entities) and monetary values. No identifiable PII fields (email, phone, dob, etc.) are present. Buyer names appear to be business or corporate names (e.g., 'J-2 Partners', 'Anderson Assoc.', 'Valencia Invest.'). There are no columns containing email addresses, phone numbers, dates of birth, or other personal identifiers. All columns either contain transaction identifiers, monetary amounts, or status codes.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is not structured PII data. The file appears to be a financial summary or accounting report with columns representing buyers, file numbers, payment distributions, and totals. There are no identifiable personal information fields such as names, addresses, emails, or phone numbers. The entries are transactional summaries rather than individual client records.

File structure

Notes: This is a free-form ledger/summary document with no consistent columnar structure. It contains transaction totals and closing summaries rather than personal data. No PII columns exist to map.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file is purely transactional accounting data with no personal identifiers. Columns contain buyer names (likely business entities), file numbers, payment amounts, and closing totals. No PII fields (email, phone, DOB, etc.) are present. The header row is incomplete and the data rows are purely financial records.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The file appears to be a financial summary report with no personal identifiable information (PII). It contains transaction details such as names of buyers, file numbers, payment amounts, and closing totals, but no email addresses, phone numbers, dates of birth, or other PII fields. All columns represent business or transactional data and should be skipped according to the rules.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is an unstructured financial/properties closing report showing buyer names, file numbers, and monetary amounts. No identifiable PII fields (email, phone, DOB, etc.) are present. Names like Baldwin, Coble, Troyer etc. are buyer surnames only with no additional contact info. All columns are financial transactional data (file numbers, amounts, status codes) or summary totals — these are skip per rules. No email/phone/DOB values visible.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII columns detected. File contains only transactional financial data (buyer names appear to be business entities or nicknames, not personal names), monetary values, and internal codes. No identifiable personal information (email, phone, DOB, SSN, etc.) present in the first 50 rows.

File structure

Notes: The provided data is a free-form table containing financial summaries and transaction records for a law firm. There are no consistent column headers or structured fields that map to PII. The data appears to be transactional summaries with names that might be client names, but without consistent formatting or identifiable PII fields (like emails, SSNs, etc.), it cannot be reliably mapped. The format is unstructured, and no PII columns can be identified based on the given rules.

File structure

Notes: The file appears to be a financial summary report with no consistent column structure or identifiable PII fields. It contains transaction data, totals, and week-by-week summaries without any personal information such as names, addresses, or other PII. The format is free-form text with no delimited columns.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file appears to be a financial summary or accounting report with no identifiable personal information. Columns contain only transaction identifiers (File #), names of entities (Buyer), payment amounts, and summary totals. No PII fields (email, phone, DOB, etc.) are present. All columns fall under skip categories: internal IDs (File #), financial amounts, and aggregate totals.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial summary report showing weekly closing totals, amounts, and distributions. No PII fields are present. Columns contain aggregate data like buyer names (which appear to be generic or placeholder names), file numbers, status codes, and monetary values. There are no identifiable personal information fields such as email, phone, address, or SSN.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only transaction data with names and monetary amounts. No PII fields are present - names appear to be client surnames only without any address, contact, or identification data. All columns represent either names (non-PII in this context), file numbers, status codes, or financial figures.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file is purely transactional/financial reporting with no PII fields. Columns represent buyer names (which appear to be entity names, not personal names), file numbers, payment codes, and monetary amounts. No email, phone, address, DOB, SSN, or other PII is present. All columns map to skip categories per rules (company names, internal IDs, financial data).

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is not structured PII data; it's a financial report showing buyer names alongside monetary values and codes. The 'Buyer' column contains names, but these appear to be business/client names rather than personal full names. There are no clear email addresses, phone numbers, DOBs, or other PII fields. The data represents transactional summaries (premises, payments) with internal codes (P/R) and identifiers (File #). According to exclusion rules, any column with 'Company' or 'Business' in the name is skipped, and these buyer entries appear to represent business entities. No PII fields are present to map.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. It contains financial summary data (names, amounts, totals) but no identifiable personal PII fields like email, phone, or address. The data appears to be aggregated financial reporting for a law firm's closings and income projections, not individual client PII. No structured columns exist to map.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: No PII columns detected. The file appears to be a financial summary report with names that are likely company/client names rather than personal identifiers, and monetary values representing premiums and distributions. No email addresses, phone numbers, dates of birth, or other personal identifiers are present.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII columns identified. File contains only transactional data: names appear to be business/client names (not personal), file numbers, status codes, and monetary amounts. No email addresses, phone numbers, dates of birth, or other PII fields are present.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is not structured PII data. The file appears to be a financial summary report with week-by-week closing totals, projected income, and percentages of projection. There are no columns containing personal identifiable information (PII) such as names, addresses, emails, phone numbers, or other sensitive data. The entries are aggregate financial figures and identifiers like 'Buyer' names (Stanley, Allion, Ayers, etc.) are likely business or entity names, not personal names, and are therefore not considered PII in this context. No PII columns to map.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is not structured data containing PII. The file appears to be a financial summary or report with columns representing buyer names, file numbers, payment amounts, and totals. There are no identifiable PII fields such as email, phone, DOB, etc. The data consists of transactional and aggregate financial information only.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file is purely transactional and financial reporting with no personal identifiers. Columns represent buyer names (but these appear to be business/client names, not individual PII), file numbers, status codes, and monetary amounts. No emails, phone numbers, addresses, DOB, SSN, or other PII fields are present. The 'Buyer' column contains entity names (e.g., 'Badart', 'Emery') which align with the breach context of corporate/LLC client lists, but these are not individual person names and cannot be mapped to firstName/lastName. All columns are skipped per exclusion rules for business/client data and financial totals.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file contains only transaction and summary data (names appear to be buyers, file numbers, status codes, monetary amounts). No identifiable PII fields are present. Names like 'Jackson', 'Richman' etc. are likely business or client names rather than personal names, and there are no email addresses, phone numbers, DOBs, SSNs, or other PII fields. All columns represent internal business metrics or identifiers.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII columns detected. File appears to be a financial summary report with names used as identifiers (Buyer) and monetary values. Names are likely business/client identifiers rather than personal PII based on context (law firm client list with corporate/LLC entities). No email, phone, address, DOB, SSN, or other PII fields present.

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction summaries, totals, and projections but no identifiable personal information in structured fields. The data appears to be internal accounting records rather than client PII.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is not structured PII data. The file appears to be financial reporting or accounting records showing buyer names alongside monetary values (premises, amounts to A.P. and J.R.). While 'Buyer' could suggest a name field, the values (Eckardt, Mercado, Barich, etc.) are likely business/client names rather than personal first/last names, and there are no email addresses, phone numbers, SSNs, or other identifiable personal data. The format lacks consistent PII columns and appears to be transactional/financial summaries only. Therefore, no PII columns are mapped.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. It appears to be a financial summary report with columns like Buyer, File #, P/R status, and monetary amounts. There are no identifiable PII fields (names, emails, addresses, etc.) in a structured format. While there are names like 'Badart', 'Emery', etc., they appear in a narrative context without other PII associations and lack consistent columnar structure. The file is purely transactional/financial data without personal identifiers in a columnar format.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: No PII columns detected. This appears to be a financial summary report containing only transaction amounts, totals, and status codes. All values are monetary figures, numeric identifiers, and status flags (P/R/C) with no personal identifying information.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger with no personal identifiable information (PII). Columns contain only business names, numeric identifiers, status flags, and monetary amounts. No email addresses, phone numbers, dates of birth, names, or other PII fields are present. The data represents client accounts, transaction statuses, and financial settlements.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is not structured PII data; it's a financial summary/report showing buyer names alongside monetary values and codes. The 'Buyer' column contains names, but these appear to be business/client names rather than personal names (e.g., 'Jessup', 'Bennett', 'Hector'). Given the breach context (law firm client lists), these are likely business entity names or matter codes, not individual personal identifiers. No columns map to defined PII fields because: 1) No email/phone/DOB/SSN patterns present, 2) Names appear to be organizational, 3) All numeric columns are financial totals/codes. Per exclusion rules, business/client names are NOT mapped as PII fields.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file is a financial summary/projection table with no identifiable personal information. Columns contain buyer names (which appear to be corporate/client names, not personal names), file numbers, transaction types, and monetary amounts. No PII fields (email, phone, DOB, etc.) are present. Buyer names like "Dawson" or "Smith" are likely entity/client identifiers rather than personal first names, and there are no addresses, contact details, or other personal data. All columns fall under skip categories (company/business references, internal IDs, financial/transactional data).

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is not structured PII data. The file appears to be a financial summary/report from RLG Law Firm showing buyer names, file numbers, payment distributions, and totals. While names like 'Waters', 'Ashley', etc., appear, they are likely client or buyer names in a business context, not individual personal records. The data contains only transaction amounts, totals, and week summaries with no email addresses, phone numbers, SSNs, or other personal identifiers. Per exclusion rules, corporate/client names in such financial reports are not mapped as PII fields. No columns map to defined PII fields.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial summary table with no personal identifiable information (PII). The file contains only transaction amounts, totals, and names that appear to be internal codes or project names rather than actual personal names. No email addresses, phone numbers, dates of birth, or other PII fields are present.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII columns detected. File contains only business/client names (not personal names), transaction identifiers, and financial amounts. Names like 'Jessup' or 'Montlea Dunne' appear to be entity/client names rather than personal full names. No email addresses, phone numbers, addresses, or other PII fields are present in the visible data.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file is a financial summary report showing closing totals, projected income, and percentage of projection. It contains no personal identifiable information (PII). All columns represent aggregated financial data, week numbers, totals, and percentages. No names, addresses, emails, phone numbers, or other PII fields are present.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file contains only transaction summaries and totals with no identifiable personal information. Columns represent buyer names, file numbers, statuses, and monetary values — all internal business data without PII fields. No emails, phone numbers, addresses, or other PII present.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is not a typical PII dataset. The file appears to be financial/legal transaction summaries from RLG Law Firm's breach, containing only names of buyers and financial figures (gross premiums, amounts paid to A.P. and J.R.). There are no identifiable PII fields like emails, phone numbers, DOB, SSN, or addresses. The 'Buyer' column contains only names (first names only), but without additional context or identifiers, this cannot be reliably mapped to firstName/lastName fields due to lack of full names or supporting data. All other columns are financial totals, counts, and percentages. Therefore, no PII columns are present to map.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file is not structured PII data. It appears to be an internal financial report or summary from RLG Law Firm showing client names (Buyer), file numbers, transaction codes, and monetary amounts (Gross Premium, To A.P., To J.R.). The values represent business transactions and totals, not personal identifiable information such as email, phone, address, DOB, etc. There are no columns mapping to PII fields. The 'Buyer' column contains only names without any additional PII. According to the exclusion rules, company/business-related columns are skipped, and this file contains only transactional and summary data.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File appears to be a financial ledger with client names and monetary amounts. No PII fields detected. Columns contain only names (which are not full names with first+last), file numbers, status codes (P/R), and monetary values. No emails, phones, addresses, DOB, SSN, gender, etc. present in the sample.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial summary table with no PII columns. Contains only transaction amounts, totals, and week labels. No names, addresses, emails, or other personal identifiers present.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial report with no identifiable personal information. Columns contain buyer names, file numbers, payment amounts, and totals, but no PII fields such as email, phone, address, DOB, SSN, etc. Buyer names are likely business entity names rather than individual person names based on context of law firm client data.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file is purely transactional financial data showing buyer names, case numbers, payment amounts, and internal accounting. No PII fields (email, phone, address, DOB, etc.) are present. Buyer names appear to be internal case identifiers or client names without additional personal identifiers. All columns are financial/tracking metrics or internal accounting codes, which fall under the exclusion rules for company/business data and internal IDs. Therefore, no PII columns to map.

File structure

Notes: This is free-form tabular data with no consistent column structure or header row. The data appears to be financial summaries (buyers, file numbers, premiums, and payments) rather than personal PII. No identifiable personal fields (names, addresses, emails, etc.) are present in the structured format. While names like 'Morrell' or 'Ottey' appear, they are used as identifiers in this financial context and lack supporting PII fields (no addresses, emails, etc.). There is no delimiter-based structure to map columns to PII fields.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger with no PII fields. Columns contain only names (no full identifiers), case numbers, statuses (P/R/A/C), and monetary amounts. No addresses, emails, phone numbers, DOB, SSN, or other PII are present. Names appear to be client surnames only, not full personal records.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file appears to be a financial summary or ledger for RLG Law Firm, containing only transaction codes, names (likely business/client names), and monetary amounts. No PII fields (email, phone, DOB, etc.) are present. The 'Buyer' column contains business/client names, which are not personal identifiers per the rules (company/business-related fields are excluded). All other columns are financial totals, codes, or internal tracking fields, none of which constitute PII. Therefore, no columns map to PII fields.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial summary sheet with no personal identifiers. Columns represent buyer names, file numbers, payment categories, and monetary amounts. No PII fields detected.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file contains no PII columns. It is a financial summary report with buyer names (which appear to be business/client names, not personal names), file numbers, and monetary values. There are no email addresses, phone numbers, dates of birth, or other personal identifiers. The buyer names (e.g., Gips, Meighan) are likely business or client identifiers rather than personal names, and the structure lacks any personal PII fields.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file appears to be a financial summary report with no identifiable personal information. Columns contain names like 'Buyer', financial figures, and week totals, but no email addresses, phone numbers, dates of birth, or other PII fields. There are no structured columns mapping to any PII categories.

File structure

Notes: This is a free-form text file with no consistent columnar structure. It appears to be a summary report of financial transactions and totals, likely from a law firm's accounting or trust account ledger. There are no identifiable PII columns present, but the data includes names (Buyer) which could be considered PII. However, due to the lack of structured columns and the nature of the file as a summary report, it is classified as unstructured. The names appear in a free-text format alongside financial data, and there is no consistent delimiter or row structure across all lines.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial/transactions ledger with names and amounts. No PII fields present. Columns contain buyer names (non-unique identifiers), file numbers, status codes, and monetary values — all business transactional data. No email, phone, address, SSN, or other personal identifiers detected.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is not structured PII data; it appears to be internal accounting or financial tracking for a law firm (RLG Law Firm). Columns contain buyer names (e.g., Kamen, LeBras), file numbers, status codes (P/R/M), monetary amounts, and weekly totals. These are internal business identifiers and financial figures, not personal PII fields like email, phone, or SSN. No columns map to any defined PII fields.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial summary table with no personal identifiable information (PII). Columns contain buyer names, file numbers, status codes, and monetary amounts. No email, phone, address, SSN, DOB, or other PII fields are present. The data appears to be transactional summaries for a law firm's closings and income projections.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is not structured PII data. The file appears to be a financial summary report showing buyer names alongside monetary values and transaction codes. While 'Buyer' appears to be a personal name field, the data lacks consistent PII fields (email, phone, address, etc.) and shows aggregated financial totals rather than individual records. The format does not contain identifiable personal information in structured columns; it is a transactional/financial report. No PII columns can be reliably mapped.

File structure

Notes: This file is a free-form text document with no consistent columnar structure. It appears to be a financial report or summary of closings and income projections for a law firm, with rows containing varied data points and no fixed delimiter. There are no identifiable PII columns to map.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file is not a structured dataset containing personal identifiable information (PII). It appears to be a financial summary or accounting report from RLG Law Firm showing client names (Buyer), file numbers, payment statuses, and monetary amounts. While it includes names (Buyer), these appear to be internal client or case identifiers rather than personal full names with associated PII fields. The data lacks email addresses, phone numbers, dates of birth, SSNs, or other defined PII fields. The format is a simple comma-separated report with no consistent PII columns.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII fields detected. The file appears to be a financial summary ledger containing only names, reference numbers, status codes, and monetary values. Names are likely client names but without additional context or address/email/phone data, they cannot be reliably mapped to PII fields. All columns map to internal business identifiers, financial amounts, and status flags which are excluded by the skip rules.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is not structured PII data. The file appears to be a financial summary or accounting report from RLG Law Firm showing closing totals, projected income, and distribution amounts. There are no personal identifiers (names, addresses, emails, etc.) present in the visible data. Columns contain only transaction codes, monetary values, and summary statistics. No PII fields to map.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial summary table with no identifiable personal information. Columns represent week ranges, buyer names, file numbers, payment statuses, and monetary amounts. No PII fields such as email, phone, DOB, etc., are present. All entries are transactional summaries and internal accounting data.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial report showing weekly closing summaries, buyer names, file numbers, and monetary amounts. The file contains no identifiable personal information (PII) such as emails, phone numbers, dates of birth, or addresses. The columns represent transaction data, totals, and percentages rather than personal identifiers. Therefore, no PII fields are mapped.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The provided sample is a free-form table with no identifiable PII columns. The data appears to be financial summaries and reporting for a law firm (RLG Law Firm) with entries for buyers, file numbers, premiums, and income distributions. There are no columns that map to PII fields such as email, phone, name, address, etc. The structure is purely transactional and financial, with no personal identifiers present.

File structure

Notes: This is a free-form text file with no consistent columnar structure. It appears to be a report showing weekly financial summaries and client lists, but the data is not in a tabular format with consistent delimiters or headers. While it contains names that could be considered PII, the lack of a structured format means we should treat it as unstructured text for processing.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only transaction data with buyer names, reference numbers, and monetary amounts. No identifiable PII fields (email, phone, address, etc.) are present. All columns represent business transaction metadata and financial figures, not personal information.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial/transactional report with no personal identifiable information (PII). Columns contain buyer names (but these appear to be business entity names), file numbers, payment codes, and monetary amounts. No emails, phone numbers, addresses, DOBs, SSNs, or other PII fields are present. Buyer names like 'Murray', 'Levine', etc., are likely business or entity names rather than personal names based on context (law firm client list with corporate/LLC data). All columns map to skip per exclusion rules (company/business references, internal IDs, financial/timestamps).

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial tracking table with no identifiable personal information. Columns contain names like 'Buyer' but these appear to be internal case identifiers or internal entity names rather than actual personal names. All values are financial amounts and summary statistics. No PII fields are present.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file is not structured data with identifiable PII columns. It contains transaction summaries, financial totals, and weekly closing statistics without any personal identifiers like names, addresses, emails, or phone numbers. All entries are aggregate financial figures and labels for weeks or totals, not individual records.

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: The file is a financial summary table from RLG Law Firm showing buyer names, file numbers, payment allocations, and totals. It contains no identifiable personal information (PII). All columns represent transactional data, internal identifiers, or aggregated financial figures. No columns map to PII fields (email, phone, name, address, etc.). Buyer names like 'Disley', 'Larder', 'Evans' appear to be internal case or client identifiers rather than personal names. The structure is purely financial reporting with no personal contact details.

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII columns detected. The file contains transaction records with names (Buyer), file numbers, status codes, and financial amounts. Names appear to be generic buyer/seller identifiers rather than personal names, and there are no email addresses, phone numbers, dates of birth, SSNs, or other PII fields. All columns map to skip categories (company/business references, internal IDs, financial data, timestamps).