skibiellaw.com

File structure

Notes: free-form text with no consistent delimiter structure; lines represent transaction records without column headers or fixed format. Contains dates, amounts, merchant names, locations, and transaction types but no identifiable PII fields like names, emails, or addresses in structured columns. This is unstructured transactional data.

File structure

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

Notes: This file contains no PII columns. Column 0 contains honorific prefixes (Mr.) before names which are not mappable to any PII field. All other columns are internal medical record identifiers, treatment codes, dates, and notes with no personal identifiers.

File structure

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

Notes: This is not structured data containing PII. The rows appear to be headerless and represent metadata about CLE (Continuing Legal Education) courses such as sponsor IDs, course IDs, dates, locations, and credit hours. There are no personal identifiers (PII) such as names, emails, phone numbers, or addresses present in the provided sample. All columns appear to be internal identifiers, course details, or administrative flags which should be skipped per exclusion rules.

File structure

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

Notes: Only firstName and lastName columns contain PII. All other columns are internal accounting/tracking fields (Bill Number, dates, financial amounts) and should be skipped per exclusion rules for financial/transactional/timestamps data.

File structure

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

Notes: Client call log from Skibiel Law containing contact details. Column [0] Date, [1] Time, [2] Type, [3] Source (phone number), [4] Contact Name (fullName), [5] masked field (contains asterisks, purpose unclear, mapped to skip), [6] Phone, [7] Email (empty in sample), [8] City, [9] State, [10] Language, [11] tele_number (phone), [12] Disposition, [13] Call duration, [14] Page url, [15-19] marketing flags (Directory Assist, Local Assist, Social Assist, PPC Assist, Website Assist - all skip as internal flags). Contact Name field contains PII with occasional annotations about case status/referral source.

File structure

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

Notes: Only column 0 contains PII (fullName). All other columns appear to be timestamps and numeric values representing financial or case data, which are not PII according to the exclusion rules.

File structure

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

Notes: Only column 0 contains PII (fullName). All other columns are internal IDs, department descriptions, job codes, and job titles which are non-PII per exclusion rules.

File structure

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

Notes: Only column 0 contains PII (fullName with suffixes). All other columns are job codes, descriptions, department IDs, and locations — none contain personal identifiers. No emails, phone numbers, DOB, SSN, or addresses are present in the first 50 rows.

File structure

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

Notes: CSV file with 2 header rows and 50 data rows. Only column 0 contains PII (fullName). Columns 1-4 are job codes and department IDs — no personal identifiers. No emails, phones, DOB, SSN, or addresses present in sample.

File structure

Notes: This file appears to be unstructured financial/transactional data with no consistent delimiter. Columns are empty except for a few fields containing business names, transaction types, dates, and amounts. No PII is present in the visible columns, and the format lacks structured column headers or consistent layout. The values are all business-related (e.g., 'MedWrecks, LLC', 'Bill', '2019-10-24T00:00:00.000Z').

File structure

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

Notes: No PII columns detected. All columns contain transactional or internal data (dates, claim numbers, provider names, financial amounts, processing status). Provider names are not personal PII of patients/clients. No emails, phones, DOB, SSN, or other PII fields present.

File structure

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

Notes: This file is a holiday gift card recipients list with no identifiable PII fields. Columns contain company names, formal address lines, and city/state/zip lines, but no actual names, emails, phone numbers, DOB, or other PII values are present in the sample. All columns are either company/business related or generic address components without personal identifiers. Per exclusion rules, company/business columns are skipped. No PII columns to map.

File structure

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

Notes: Only column 0 contains PII (fullName). All other columns are internal case tracking fields (case type, settlement/fee amounts, internal codes) and should be skipped. No emails, phones, DOB, SSN, or addresses are present in the first 50 rows.

File structure

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

Notes: This file is a free-form notice about workers' compensation policies and physician panels. It contains no structured personal data fields or repeated rows with PII. The content is informational text only.

File structure

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

Notes: This file contains only structured data related to workers' compensation policies and physician panels. No PII fields (email, phone, dob, name, address, etc.) are present. The content includes company names, addresses, phone numbers for business lines, and medical provider information, all of which are excluded by the 'Company/Business' rule. Therefore, no columns map to PII fields.

File structure

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

Notes: This is a cryptocurrency transaction log with no personal identifiable information (PII). Columns represent asset names, transaction dates, cost basis, proceeds, amounts sold, durations, and flags — none map to PII fields. No emails, names, addresses, or other PII are present in the sample rows.

File structure

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

Notes: This is a cryptocurrency transaction ledger with no personal identifiable information (PII). Columns include asset name, dates, financial figures, and boolean flags. No fields map to PII categories such as email, phone, name, address, etc. All columns are financial/transactional data and therefore skipped per exclusion rules.

File structure

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

Notes: This file contains financial transaction data (cryptocurrency trades) with no personal identifiable information. Columns include asset name, dates, cost basis, proceeds, amounts, and flags — none map to PII fields. No emails, phones, names, addresses, DOB, SSN, or other PII are present.

File structure

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

Notes: Client call log from Skibiel Law breach. 20 columns total; 5 contain PII (fullName, phone, email [empty], city, state). Remaining columns are call metadata (Date, Time, Type, Source, Language, disposition, duration, URLs, and tracking flags) — all mapped to skip. Column [11] 'tele number' appears to be duplicate of phone data; included in skip. Columns [14-19] (Page url, Directory Assist, Local Assist, Social Assist, PPC Assist, Website Assist) are marketing/routing flags — skipped.

File structure

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

Notes: This appears to be a WAGE STATEMENT document from the Georgia State Board of Workers' Compensation. Columns 6-9, 13-14, 17, 19, 21 contain PII: last name, first name, address, city, state, zip, SSN. Other columns appear to be document metadata or empty. The format is CSV-like but lacks a consistent header row; mapping is based on visible column labels and sample values.

File structure

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

Notes: All columns are non-PII: timestamps (Date, Time), flags (HasAttachment, Reconciled), categories (Client, Type, Category), subjects, authors, numerical amounts (Hours, Amount), invoice identifiers, and free-text notes. No email, phone, name, address, DOB, SSN, or other PII fields are present.

File structure

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

Notes: This is an unstructured financial data file with no PII columns. All rows appear to be settlement calculations, attorney fees, medical costs, and net client amounts with no identifying information. No columns map to PII fields.

File structure

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

Notes: Only column 0 contains PII (fullName). All other columns contain financial/earnings data, dates, and numerical values with no personal identifiers. No emails, phones, DOB, or addresses appear in this structured CSV. The file appears to be a payroll/earnings report for a worker named Andrew King.

File structure

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

Notes: CSV file with structured headers; only first two columns contain PII (name fields). All other columns contain financial/work data (dates, amounts, totals) and are skipped per exclusion rules.

File structure

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

Notes: File appears to be a workers' compensation earnings and TPD benefits report. Only column 0 contains PII (full name). All other columns are financial/temporal data (dates, amounts, calculations) and should be skipped per exclusion rules. No email, phone, address, DOB, SSN, or other PII fields present in the first 50 rows.

File structure

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

Notes: The file appears to be a structured CSV with financial/earnings data. Only column 0 contains PII (first names). All other columns contain financial figures, dates, and calculations with no personal identifiers.

File structure

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

Notes: This file appears to be structured data but contains no identifiable PII columns. The data represents injury compensation calculations with timestamps, earnings, and benefit amounts. No names, addresses, emails, phone numbers, or other PII fields are present in the visible columns. The first row appears to be a malformed header or label row, and subsequent rows contain purely financial and date-based data.

File structure

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

Notes: This file contains only financial/transactional data (dates, earnings, benefits) with no personal identifiers. All columns map to skip categories: timestamps, internal IDs, financial amounts, and calculation fields. No PII fields detected.

File structure

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

Notes: This file contains only payment and earnings data with no personal identifiers. All columns represent financial metrics (weeks worked, gross amounts, totals) and timestamps — no names, addresses, emails, or other PII fields are present. The 'Date of Injury' column is a timestamp not tied to a person, and TPD/TTD benefit calculations are purely financial. No columns map to any PII field categories.

File structure

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

Notes: Only column 1 contains PII (fullName). All other columns are financial/payment codes or numeric values representing earnings, hours, bonuses, etc., with no personal identifiers.

File structure

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

Notes: This file contains only pay period dates, gross pay amounts, and week numbers. No PII fields are present. All columns are transactional/temporal data and should be skipped per exclusion rules.

File structure

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

Notes: This file contains only payment schedule data with dates, amounts, and week numbers. No PII fields (names, addresses, emails, etc.) are present. All columns are financial/temporal data that should be skipped per exclusion rules.

File structure

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

Notes: No PII columns detected. File contains only payroll/transactional data: pay period dates, monetary amounts, and flags. All columns map to financial/temporal data (Pay Start Date, Pay End Date, Amount, Overtime Paid, Bonus, Retro) which are excluded by policy.

File structure

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

Notes: This file contains only payment schedule data (start/end dates, gross amounts, week numbers, notes). No PII fields are present. All columns are transactional/temporal and should be skipped per exclusion rules.

File structure

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

Notes: Only column 0 contains PII (fullName). All other columns are headers for financial/temporal data or empty placeholders with no PII.

File structure

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

Notes: This file appears to be a timesheet or earnings report template with no PII. Columns contain only numeric counters, placeholders, and internal tracking fields (week numbers, dates, earnings totals). No names, contact info, or other PII present.

File structure

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

Notes: The file contains only settlement calculator data with dates and monetary values. No PII columns (names, emails, phone numbers, addresses, etc.) are present. The columns represent weeks, pay periods, and gross amounts, which are not personally identifiable information.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. It appears to be a pay stub or payroll report with timestamps, amounts, and week numbers. No PII fields are present in a structured format. However, due to the unstructured nature, we cannot rule out embedded PII in free text; this should be processed through a streaming email/phone extractor if needed.

File structure

Notes: This is a free-form text file with no consistent column structure. It appears to be a payroll or financial summary with dates, amounts, and week numbers, but lacks any identifiable personal information in a structured format. The rows show timestamps, monetary values, and week counters without any PII fields like names, addresses, or contact details. The presence of 'Total' and 'AWW' suggests aggregate financial data rather than individual records.

File structure

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

Notes: No PII columns present. The file contains only numerical earnings/tracking data with no personal identifiers (names, emails, addresses, etc.). Columns are week numbers, date ranges, and financial values.

File structure

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

Notes: No PII columns detected. All columns appear to be internal tracking fields (week numbers, date ranges, earnings calculations) with no personal identifiers. Values are numeric or timestamps without names, addresses, emails, or other PII.

File structure

Notes: The file appears to be free-form text with no consistent delimiter structure. It contains headers like 'Name:', 'CompanyName:', 'PlanName:', and unstructured notes rather than a tabular dataset. While it contains a name (LAUREN SKIBIEL), the format does not lend itself to column mapping — it is a descriptive/prose document, not a CSV or similar structured format. Per unstructured rules, we return an empty columns object.

File structure

Notes: free-form text with no consistent column structure; contains header-like lines but not tabular data

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a mix of headers and notes rather than tabular data

File structure

Notes: free-form text with no consistent delimiter structure; contains embedded names and company references but lacks row consistency required for CSV mapping

File structure

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

Notes: This file contains only financial figures and offers with no personal identifiers. All columns appear to be transactional data (offers, legal fees, expenses, bills, med pay, totals) with no names, addresses, or other PII. The structure is purely numerical and lacks any header or row identifiers that would map to PII fields.

File structure

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

Notes: This is a financial data table with columns representing settlement offers, legal fees, expenses, and various bill amounts. No PII fields are present; all columns contain monetary values or labels for offers. The data appears to be structured financial calculations rather than personal information.

File structure

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

Notes: No PII columns detected. File contains only payroll period dates, week numbers, and monetary values (gross pay, totals, penalties). All columns represent transactional/financial data and timestamps, none contain personal identifiable information.

File structure

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

Notes: This is a time card report with no PII columns. The only potentially identifying value is 'Wilkins, Ashley' in column 3, but this is part of a header row and not a data row. All other columns contain status codes, timestamps, and page numbers.

File structure

Notes: This is an unstructured time card report file with no consistent column structure. The data appears to be a payroll report with employee name 'Wilkins, Ashley' visible, but there are no consistent columns across rows to map to PII fields. The file contains free-form text with embedded names and timestamps rather than a structured table.

File structure

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

Notes: Only column 2 contains PII (full name with DOB). All other columns are financial/transactional or internal identifiers (claim type, claim number, service date, provider, billing amounts, status). No emails, phones, addresses, SSNs, or passwords are present in the sample.

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a financial summary report with dates, charges, and balances rather than structured PII records. No identifiable columns present.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The content appears to be a financial calculation table showing accrued amounts, interest rates, and totals for attendant care claims. There are no identifiable columns or PII fields in a structured format. While the data contains numbers and dates, it lacks any personal identifiers such as names, emails, phone numbers, or addresses in a columnar format. The file is unstructured and should be processed as such.

File structure

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

Notes: This file is purely financial calculations with no PII columns present. All rows contain numerical values, dates, and financial formulas without any personal identifiers.

File structure

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

Notes: This file is purely financial/interest calculations with no PII columns. All entries are numeric values, dates, and financial metrics. No names, addresses, emails, phone numbers, or other PII appear in the sample rows.

File structure

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

Notes: This file contains only financial calculations and interest accruals. There are no personal identifiers or PII fields present. All columns represent numeric values, dates, or calculations related to financial data.

File structure

Notes: free-form text with no consistent column structure; appears to be settlement calculation data with timestamps and amounts, but lacks any identifiable PII columns or repeated field patterns

File structure

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

Notes: 5 PII columns identified: fullName, phone, email, city, state. All other columns are timestamps, call metadata, or internal flags and should be skipped per policy.

File structure

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

Notes: This is a workers' compensation calculation worksheet from Skibiel Law breach. The structured portion contains only header-value pairs (name, SSN, state, dates). Rows 2+ contain tabular calculation data (week numbers, codes, hours, amounts, date ranges) which are financial/transactional and should be skipped. Only the client identifiers (fullName, ssn, state) are extracted as PII.

File structure

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

Notes: The file is a free-form notice with no consistent column structure. It contains no structured PII fields; it is purely informational text about workers' compensation procedures and contact details for the State Board of Workers' Compensation. No columns to map.

File structure

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

Notes: 50 rows of membership data with names and status flags. Only firstName, middleName, and lastName contain PII. Membership Number and Billing Status are internal identifiers and status flags respectively.

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: Heuristic auto-detection: header-named PII columns confirmed by data conformance

File structure

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

Notes: 50 rows parsed. Columns 0 (Membership Number) and 1 (Prefix) are skip per exclusion rules. Columns 2-5 contain full name components. Column 6 is a payment date, not PII.

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: CSV file with membership records. Columns 2-5 map to firstName, middleName, lastName, and suffix. 'Membership Number' and 'Prefix' are internal identifiers and honorifics respectively, skipped per rules. 'Dues Paid Through' is a date flag, skipped.

File structure

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

Notes: 50 rows parsed, 6 columns total. Columns 0 (Membership Number) and 1 (Prefix) skipped per exclusion rules. Column 6 (Dues Assessment Balance) is numeric and skipped.

File structure

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

Notes: CSV file with 6 columns, 5 contain PII. 'Prefix' column contains honorifics (Mr, Rev, Deacon) which are not mappable to any PII field and should be skipped. All rows follow consistent structure.

File structure

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

Notes: 50 rows parsed, 6 columns total. Columns 0 (Membership Number) and 1 (Prefix) skipped per exclusion rules (internal ID and honorific title). Column 6 (Initiation Fee Balance) is numeric financial data and skipped.

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: 5 columns total, 3 contain PII (firstName, middleName, lastName). The 'Membership Number' and 'Send Bill?' columns are internal identifiers and flags respectively.

File structure

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

Notes: 12 columns total, 6 contain PII. Columns 3-5 and 10-11 are internal identifiers or flags and have been skipped per rules.

File structure

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

Notes: 5 columns total, 3 contain PII. Columns 3 (Membership Number) and 4 (Member Class) are internal identifiers and membership flags — skipped.

File structure

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

Notes: 50 rows, 3 PII columns: firstName, middleName, lastName. 'Membership Number' and 'Dues Paid Through' are skip columns (internal ID and date respectively).

File structure

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

Notes: 5 columns total, 3 contain PII. 'Membership Number' and 'Billing Sub Class' are internal identifiers and categories, not PII.

File structure

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

Notes: Only firstName, middleName, and lastName columns contain PII. Membership Number and Billing Status are skip columns.

File structure

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

Notes: 50 rows of membership data with complete names. No other PII fields present in this excerpt.

File structure

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

Notes: CSV file with 6 columns; 5 contain PII (suffix appears twice but maps to same field). No email/phone/dob/ssn/password/username columns 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: no·Quote: "

Notes: This file contains only medical billing data with dates, providers, amounts, and flags. No PII fields (names, emails, phone numbers, addresses, etc.) are present in the first 50 rows. All columns appear to be transactional/financial data or timestamps, which are excluded by rules.

File structure

Notes: This file appears to be a free-form report document with no consistent columnar structure. The sample rows show free-text entries like "Pool Scouts North Atlanta" and date ranges rather than tabular data. There are no identifiable PII columns or structured fields in this sample. The content resembles a heading/title row followed by empty or non-structured cells, confirming this is not a CSV with columns.

File structure

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

Notes: This file contains no PII fields. All columns appear to be internal tracking codes, dates, financial amounts, and status flags. 'Payee' values are generic codes ('E-C'), not names or emails. No identifiable personal information present.

File structure

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

Notes: This file appears to be a financial or medical billing record with no identifiable personal information in the first 50 rows. Columns contain only numeric values (costs, payments) or generic text (doctor names not clearly linked to patients). No emails, phone numbers, names, addresses, DOBs, or SSNs are present in the sample. All columns map to skip per rules (financial amounts, internal notes).

File structure

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

Notes: This file contains only financial calculations and timestamps with no personal identifying information. All columns appear to be numerical values, dates, and financial figures related to workers' compensation settlements. There are no names, addresses, email addresses, phone numbers, or other PII fields present in the visible data.

File structure

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

Notes: This file contains only financial and temporal data (pay periods, amounts, totals). No PII fields are present. All columns represent internal accounting/tracking data (pay periods, amounts, weeks, totals) and do not contain any personal identifiable information such as names, addresses, emails, phone numbers, DOB, SSN, etc. Therefore, no columns map to PII fields.

File structure

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

Notes: The provided data is not structured PII records but a single-line financial summary for a legal settlement (Brian West). There are no columns containing personal identifiable information such as names, addresses, emails, phone numbers, DOB, SSN, etc. The file appears to be a financial breakdown of a settlement amount, legal fees, expenses, and net client payout — purely transactional data without any PII fields. Therefore, no columns map to PII fields.

File structure

Notes: This is an unstructured file containing only financial settlement breakdown data with no personal identifiable information (PII) fields. The lines are free-form text without consistent column structure or personal data. No emails, phone numbers, or other PII are visible in the sample.

File structure

Notes: The file is free-form text with no consistent column structure. It contains embedded PII including names (Pamela Burrell, Nancy Durning), phone numbers (706-507-0576, 404-630-2961), and a date of birth (1958-05-31). This meets the criteria for unstructured data with embedded PII.

File structure

Notes: The provided text is unstructured free-form data from a medical billing summary and patient record. It contains no consistent column structure or delimiters across lines, and is composed of prose-style entries. While it contains patient names, addresses, phone numbers, and billing details, these appear inline within free-form text rather than in a tabular format. The unstructured format and lack of consistent structure qualify this for the unstructured opt-out path, where embedded PII will be extracted via streaming processing rather than column mapping.

File structure

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

Notes: This file appears to be a free-form text representation of a billing summary and patient information. The data is not structured in a consistent tabular format with identifiable columns. There are no clear, repeatable column positions that map to PII fields across all rows. The values contain what looks like patient names, addresses, phone numbers, and billing details, but they are interspersed in a non-tabular way. Given the unstructured nature of the data, it should be processed as unstructured text with embedded PII.

File structure

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

Notes: This is not a structured PII dataset. The file appears to be medical billing statements and summaries from Henry Vision Center, LLC with no identifiable personal information in the visible rows. There are no columns containing email, phone, dob, name, address, ssn, password, username, or other PII fields in the first 50 rows provided. The data consists of billing codes, descriptions, prices, and totals without any personal identifiers.

File structure

Notes: This file is unstructured free-form text with no consistent delimiter or row structure. It contains embedded PII such as phone numbers and addresses, but lacks any columnar format. The content appears to be a mix of address lines, phone numbers, and billing summary data without a defined schema. The unstructured format requires special handling for extracting emails and phones.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. It contains lines of varying lengths and content, including what appears to be medical billing information, addresses, and phone numbers. Since there is no consistent column structure, we treat this as unstructured data with embedded PII that will be handled by a streaming extractor.

File structure

Notes: The provided data appears to be free-form text with no consistent column structure. It contains elements such as addresses, phone numbers, and medical billing details, but lacks a uniform delimiter or header row. This matches the criteria for unstructured data with embedded PII.

File structure

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

Notes: Only columns 1 (firstName) and 2 (lastName) contain PII. All other columns are internal identifiers, payment codes, timestamps, or amounts (non-PII).

File structure

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

Notes: Only first and last name columns contain PII; others are employment/payroll identifiers and timestamps (exempted by exclusion rules)

File structure

Notes: This is unstructured data (prose) showing legal billing details, not tabular PII. No consistent column structure exists across rows. Contains legal service descriptions and fees but no identifiable personal data fields. This is a README or invoice description, not structured records.

File structure

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

Notes: This file is a free-form text report with no consistent column structure. It contains patient medication records but lacks any identifiable PII columns (names, emails, addresses, etc.) beyond the repeated name 'Justen White'. The 'Member Name' column is not present as a structured header, and values are embedded in free text. No PII fields to map.

File structure

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

Notes: This is a call log from Skibiel Law containing inbound and outbound calls. Column [0] is timestamp (skip), [1] is call type (skip), [2] is duration (skip), [3] is originating phone, [4] is caller name/ID, [5] is receiving phone system ID (skip), [6] is receiving phone number. Multiple rows per call (triplicates) are present. The file contains client contact information and call metadata relevant to the breach context.

File structure

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

Notes: This is a call log from Skibiel Law. Column [0] Date & Time, [1] Type, [2] Duration are metadata/skip. Columns [3], [5], [6] contain phone numbers (PII). Column [4] 'From Caller ID' contains caller identifications including names (e.g., 'ANGELA ROSSER', business names, or phone numbers) — these are identifying information but appear mixed (some are names, some are phone representations); the actual distinct phone numbers are properly captured in columns [3], [5], [6]. The file exposes attorney-client call patterns and client contact information from a law firm breach.

File structure

Notes: The provided text is unstructured and appears to be a mix of address information, billing details, and patient records without consistent delimiters or column headers. The content includes free-form text with embedded PII such as names, addresses, and phone numbers, meeting the conditions for unstructured data handling.

File structure

Notes: free-form text with embedded data; no consistent delimiter structure across lines, appears to be medical billing notes with inline charges and notes rather than structured columns

File structure

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

Notes: No PII columns detected. All columns are timestamps, numeric codes, monetary values, or status flags (e.g., Provider Name appears to be internal provider identifiers, not personal names). Claim numbers, NPIs, and financial figures are non-PII per exclusion rules.

File structure

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

Notes: This is a medical billing file with no PII columns. Columns include fill date, medication name, prescription number, pharmacy name, and financial amounts. No names, addresses, emails, phone numbers, or other PII fields are present.

File structure

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

Notes: No PII columns detected. All columns are internal identifiers, timestamps, or transaction amounts. 'Provider Name' appears to be internal provider identifiers rather than patient names.

File structure

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

Notes: This file contains medication records and billing information but does not contain any PII fields. All columns represent fill dates, medication details, pharmacy information, and financial amounts — none map to email, phone, name, address, DOB, SSN, etc. Therefore, no PII columns to map.

File structure

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

Notes: Only column 1 (Provider Name) contains PII (fullName). All other columns are timestamps, claim IDs, financial amounts, codes, and status flags — none are PII per the rules. Claim numbers and NPI numbers are internal identifiers, not usernames or addresses.

File structure

Notes: free-form text with no consistent column structure; contains financial transaction data but no identifiable PII fields

File structure

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

Notes: The file appears to be a medical billing spreadsheet with columns for Medical Facility, Bills, Insurance paid, Write Off, C Paid, Balance Due, and Notes. There are no identifiable PII fields (email, phone, dob, etc.) present in the headers or sample values. All columns relate to financial transactions and notes about billing communications, not personal identifying information.

File structure

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

Notes: This is a structured CSV file with columns: Months, Days in Month, Monthly Wages, Pay per day. None of these columns contain PII data. The data appears to be wage calculations without any personal identifiers such as names, addresses, or contact information.

File structure

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

Notes: This file contains only payroll dates, gross pay amounts, and week numbers. No PII fields are present. All columns are payment/timestamp data which must be skipped per exclusion rules.

File structure

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

Notes: File appears to be a payroll or earnings report with a single PII column containing full names. Other columns are numeric financial data or date fields that do not contain PII.

File structure

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

Notes: File appears to be a payroll or earnings report with a single name column and numeric financial columns. Only column 0 contains PII (full name). All other columns are numeric financial/temporal data and are skipped per rules (financial/transactional, timestamps).

File structure

Notes: The provided file is a structured log or path traversal report, not a delimited data file with columns. It contains hierarchical paths and counts related to calls, emails, and website interactions, but lacks any personal identifiable information (PII) fields like names, emails, or phone numbers. The data appears to be metadata about user journeys and referral sources rather than actual user data. Therefore, no column mapping to PII fields is possible.

File structure

Notes: This is a summary report of referral paths and counts, not structured data containing PII. No columns to map.

File structure

Notes: free-form text with embedded emails / phones

File structure

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

Notes: This is a non-PII structured file containing insurance and billing metadata. All columns represent internal tracking codes, status flags, amounts, and timestamps. No personal identifiers (names, emails, phone numbers, addresses, DOB, SSN) are present in the visible columns. The values are internal codes, carrier names (not personal), status flags, and dates in ISO format that are not tied to any individual person.

File structure

Notes: free-form text with no consistent delimiter structure; appears to be log entries and vehicle-related notes rather than structured PII records

File structure

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

Notes: This is not structured PII data; it's a financial breakdown table for a settlement. Columns represent settlement components (Settlement Amount, Legal Fees, etc.) with no personal identifiers like names, addresses, or contact details. No PII fields present.

File structure

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

Notes: This is not a structured PII dataset. The provided rows appear to be a financial settlement breakdown for a single case (Charlie Rosa) with columns: Settlement Amount, Legal Fees, Child Support Lien, Legal Expenses, Net to Client. There are no personal identifiers (names, emails, addresses, etc.) in these rows. The file appears to be a financial summary rather than a dataset containing personal information. All visible columns are financial/transactional data that must be skipped per exclusion rules.

File structure

Notes: The file is free-form text with no consistent delimiter structure. It appears to be a mixture of header-like text and numerical data, but lacks repeating structured rows. Contains timestamps and financial/legal calculations rather than identifiable PII in a tabular format.

File structure

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

Notes: 50 rows analyzed. All rows contain PII in username and password fields. URLs are not PII but are included for context.

File structure

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

Notes: This is a credentials breach from Skibiel Law. Column [0] contains service names (skip), [1] contains URLs (skip), [4] contains notes (skip). Columns 2 and 3 contain sensitive authentication data. Email addresses in the username column (e.g., andrew@skibiellaw.com, hanna@skibiellaw.com) are captured as username entries; some phone numbers appear as usernames (e.g., 4047883987, 9082571952). All passwords are exposed in plaintext.

File structure

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

Notes: 5 rows total, 4 columns. Columns 0, 2, and 3 contain PII (fullName, username, password). Column 1 is a URL and skipped.

File structure

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

Notes: No PII columns detected. All columns represent internal case/cost tracking metadata (dates, cost types, amounts, internal flags). Names like 'MARK' and 'LUCY' appear to be attorney initials rather than full client PII. No emails, phones, addresses, or SSNs present.

File structure

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

Notes: CSV file with billing data; only 'Patient' column contains PII (full names). Other columns contain dates, providers, billing amounts, and status codes (no PII).

File structure

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

Notes: Only column 1 contains PII - human full names. All other columns contain service dates, providers (facilities/clinics), billing status, monetary amounts, and payment tracking. No addresses, emails, phone numbers, DOB, SSN, gender, etc. present in this sample.

File structure

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

Notes: Only column 1 (Patient) contains PII — a full name. Other columns are billing/service codes and amounts, not personal data. No emails, phones, DOB, or addresses appear.

File structure

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

Notes: 4 PII columns identified: fullName. The remaining columns (Service Date, Provider, Status, Billed, Plan Paid, Patient Responsibility, My Payments) are non-PII transactional data or timestamps and are skipped per rules.

File structure

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

Notes: This is a medical billing CSV with no PII fields. The 'Patient' column only contains the first name 'Andrew' across all rows, which is not sufficient to identify an individual uniquely. No emails, phone numbers, addresses, DOB, SSN, or other PII are present. All columns are either transactional data (Service Date, Billed amounts) or non-identifying identifiers (Provider names which are entities, not individuals).

File structure

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

Notes: This is a medical billing CSV with no PII columns. The 'Patient' column only contains first names (Andrew) without any last names, addresses, or other identifiers. All other columns contain transactional data (dates, amounts, statuses). No emails, phones, DOB, SSN, or other PII fields are present.

File structure

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

Notes: Only column 2 contains PII (fullName). All other columns are either internal IDs, company-related, timestamps, or financial data, which must be skipped per exclusion rules.

File structure

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

Notes: Only column 2 contains PII (fullName). Column 0 is an internal client ID and must be skipped per exclusion rules. Other columns contain numerical/wage data and are non-PII.

File structure

Notes: free-form text with no consistent delimiter structure; contains personal health timeline but lacks tabular format

File structure

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

Notes: File appears to be a medical billing statement with patient PII including names, addresses, DOB, and phone numbers. Structured CSV format with embedded patient data.

File structure

Notes: This file is a free-form medical billing statement with no consistent columnar structure. It contains embedded PII such as full names (Tyler Collins), address lines (901 East 18th Street, 35 Cotton Indian Creek Rd), city/state/zip (Tifton, GA 31794; McDomough, GA 3052), and phone number (678-879-2843). Due to its unstructured nature with varying line formats, it qualifies as unstructured data with embedded PII requiring streaming extraction.

File structure

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

Notes: No PII columns detected. All columns appear to contain project management data (dates, costs, descriptions) and do not contain any personal information. The data appears to be construction/renovation project tracking rather than client or employee PII.

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: Heuristic auto-detection: header-named PII columns confirmed by data conformance

File structure

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

Notes: CSV file with 6 columns. Columns 0 (Membership Number) and 1 (Prefix) contain non-PII data (internal IDs and honorifics). Columns 2-5 contain PII: first name, middle name, last name, and suffix.

File structure

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

Notes: 6 columns total, 4 contain PII (firstName, middleName, lastName, suffix). 'Membership Number' and 'Prefix' are internal identifiers and honorifics respectively — both skipped per rules.

File structure

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

File structure

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

Notes: CSV file with 6 columns. Columns 0 (Membership Number) and 1 (Prefix) contain internal identifiers/honorifics and are skipped. Columns 2-5 contain PII fields: firstName, middleName, lastName, and suffix. All values align with expected patterns for these fields.

File structure

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

Notes: 50 rows shown, 45 columns total. PII columns identified: First Name, Middle Name, Last Name, Suffix. All other columns (Membership Number, Prefix) are internal identifiers or honorifics and skipped per rules.

File structure

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

Notes: CSV file with 6 columns; 5 contain PII (firstName, middleName, lastName, suffix). Prefix column contains honorifics (Rev, Dea) and is skipped per rules. No other PII fields detected in sample.

File structure

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

Notes: CSV file with 6 columns. Membership Number and Prefix are internal identifiers (skip). First Name, Middle Name, Last Name, and Suffix are clearly PII. No email, phone, DOB, address, SSN, password, username, or other PII fields detected.

File structure

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

Notes: CSV file with 6 columns; only firstName, middleName, lastName, and suffix contain PII. Prefix column contains honorifics (Rev, Dea) which are NOT mapped to any PII field.

File structure

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

Notes: 50 rows shown, 6 columns total. Only columns 2-5 contain PII. Column 0 (Membership Number) and Column 1 (Prefix) are skipped per rules: Membership Number is an internal ID, Prefix contains honorifics (Rev, Dea) which are not a PII field.

File structure

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

Notes: 50 rows analyzed, 5 columns total. Columns 0, 1, 2, and 4 contain PII (firstName, middleName, lastName, email). Column 3 (Membership Number) is an internal ID and skipped.

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: Heuristic auto-detection: header-named PII columns confirmed by data conformance

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: Heuristic auto-detection: header-named PII columns confirmed by data conformance

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 columns 0-2 contain PII (firstName, middleName, lastName). Column 3 is an internal membership ID and should be skipped.

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 firstName, middleName, and lastName columns contain PII. Membership Number is an internal ID and does not contain PII.

File structure

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

Notes: Only first three columns contain PII (firstName, middleName, lastName). Fourth column 'Membership Number' is an internal identifier and should be skipped.

File structure

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

Notes: CSV file with 6 columns; 4 contain PII (firstName, middleName, lastName, suffix). 'Membership Number' is an internal identifier and 'Prefix' column contains honorifics (Mr, Mrs etc) which are NOT a PII field.

File structure

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

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

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 18 (fname), 19 (email), and 20 (phone) contain PII. All other columns are internal IDs, campaign tracking, or empty fields.

File structure

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

Notes: Only 3 PII columns identified: firstName, email, phone. All other columns are internal tracking IDs, campaign data, or generic flags and should be skipped per rules.

File structure

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

Notes: Only 3 PII columns detected: firstName, email, phone. All other columns are internal IDs, campaign/tracking data, or empty fields.

File structure

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

Notes: No PII columns detected. All columns contain campaign metadata, tracking IDs, and timestamps. Values show advertising campaign data (gclid, gad_source, etc.) with no personal identifiers like names, emails, or phone numbers. The breach context mentions sensitive legal/PII data, but this specific file appears to be marketing analytics logs only.

File structure

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

Notes: This is not structured PII data. The file appears to be a log or analytics dataset with marketing campaign details, Google search parameters, and click IDs. No personal identifiable information (PII) fields such as names, emails, phone numbers, addresses, or dates of birth are present. All columns contain internal tracking IDs, campaign metadata, timestamps, and technical identifiers, which are excluded by the rules.

File structure

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

Notes: This is not structured PII data; it's Google Ads performance logs showing campaign metrics, URLs, and timestamps. No columns map to PII fields. The data contains only advertising metrics, campaign IDs, dates, and Google Click IDs — none represent personal identifiers like names, addresses, or contact details. This is typical digital marketing reporting data, not client or patient records from the law firm breach.

File structure

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

Notes: This is not structured data with columns; it appears to be log entries or analytics data with no consistent column mapping. There are no identifiable PII fields in the visible sample. The data contains timestamps, campaign identifiers, and numerical values but no names, addresses, emails, or other PII. Given the context of a law firm breach, this file likely represents marketing or analytics logs rather than client or employee records.

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: This file appears to be a structured table with physical demands analysis data for job classifications. While column 9 contains what looks like personal names ('Michael Hoonhorst', 'Caroline Smith'), these are likely example names or placeholder data for analysis templates rather than real PII records given the context ("Physical Demands Analysis" template). No columns map to defined PII fields per our rules — names here are illustrative job analysis examples, not actual client records. All columns are descriptive/job classification fields or empty.

File structure

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

Notes: This is not a PII file. The columns contain job classification data, physical demands analysis, and technical specifications. No identifiable personal information is present. All columns are mapped to 'skip' per rules.

File structure

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

Notes: This file appears to be a template or form with no personal identifiable information (PII) in the provided rows. The columns contain generic terms related to job classifications, physical demands, work environments, and other non-PII data. No email addresses, phone numbers, names, or other PII fields are present in the sample rows.

File structure

Notes: This is an unstructured document with no consistent delimiter or row structure. The sample shows free-form text with job classification tasks, evaluator signatures, and task descriptions. There are no identifiable PII columns in this structured format. However, there are some names visible in the data that would need to be extracted via unstructured processing (e.g., 'Michael Hoonhrost', 'Caroline Smith').

File structure

Notes: This is not structured data; it's a free-form document with job classification and physical demands analysis. No consistent column structure exists, and the content is descriptive text rather than tabular data with PII fields. The sample shows unstructured prose with no delimited records.

File structure

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

Notes: This file contains only internal job classification and physical demands analysis data. No PII fields are present. Columns contain job-related terms like 'Technician', 'Lifting', 'Carrying', 'One hand', etc. There are no email addresses, phone numbers, names, or other PII values. The only potential name-like entry ('Michael Hoonhorst' and 'Caroline Smith') appears in a comment field alongside job tasks and is not a structured personal record. All columns are mapped as skip per exclusion rules and lack of PII content.

File structure

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

Notes: This is a free-form analysis document with no structured PII columns. The data contains qualitative job descriptions and analysis categories rather than personal information fields. No columns map to PII fields.

File structure

Notes: The file appears to be unstructured text containing job analysis descriptions and task listings rather than tabular data with PII columns. No consistent delimiter or header structure is present across the sample rows. Values are free-form descriptions of tasks and job classifications rather than personal information fields.

File structure

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

Notes: This is a payroll data file with columns: Payroll Result, Period, Hours, Gross Pay, Taxes/Deductions, Net Pay. There are no PII fields present. The only personal identifier is 'Shanice White' which appears to be a name but is not mapped because the column containing it is not a dedicated name column and the file lacks structured headers for name fields. The numeric ID in parentheses (10135350) is an internal employee ID and should be skipped per rules. All columns represent payroll calculations and dates, not personal identifiable information.

File structure

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

Notes: This is a payroll report with no PII columns. The file contains only payroll data (names are not full names, just identifiers, and no other PII like addresses, emails, etc. are present). The 'Shanice White' entry appears to be a generic placeholder or internal identifier rather than actual PII. All columns are financial/temporal data and do not contain any PII fields per the defined rules.

File structure

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

Notes: CSV file with payment records. Only column 4 contains personal names (fullName). Other columns contain payment types, amounts, dates, statuses, and reference numbers — these are transactional and not PII.

File structure

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

Notes: This CSV contains employee PII including SSN, names, and DOB. Other columns are non-PII financial/compensation data and should be skipped.

File structure

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

Notes: This file is a holiday gift card recipient list with no actual PII present. Columns contain only generic labels like 'Company', 'Address', and city/state information that are not tied to identifiable individuals. The values in column 1 appear to be titles followed by names, but these are not separated into firstName/lastName fields and are presented as formal recipient labels rather than structured PII. No valid email, phone, DOB, SSN, or other PII fields are present. All columns are either skipped per rules (company/business fields) or contain non-PII data.

File structure

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

Notes: 5 PII columns identified: fullName, phone, email, city, state. All other columns contain internal call tracking data, timestamps, and disposition codes.

File structure

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

Notes: 5 PII columns identified: fullName (4), phone (7), email (8), city (9), state (10). All other columns contain internal tracking data, URLs, or disposition notes.

File structure

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

Notes: Only column 1 contains PII (fullName). All other columns are financial/transactional codes and amounts, excluded by rules.

File structure

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

Notes: Unstructured medical billing document with header block containing guarantor name/address and patient info. Core PII extracted: patient name (fullName), DOB, and home phone. Document also contains provider names (non-PII), procedure codes, and claim/billing data. Address data ('500 E Lake Dr', 'Riverdale, Ga 30274') present but extracted from prose header section prior to structured table, not mapped as distinct columns.

File structure

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

Notes: This file contains financial transaction records with dates, statuses, payee names, payment codes, amounts, document references, and payment date ranges. No identifiable PII fields (email, phone, dob, names, etc.) are present. The payee field contains business names ('COREY BANKS', 'Mark A. Skibiel, P.C.') which are not personal PII per the exclusion rules for company/business names. All columns map to transactional/financial data and timestamps, which are explicitly excluded.

File structure

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

Notes: CSV file with payment records; only column 3 contains PII (full names). Other columns contain transaction metadata, dates, amounts, and internal references which are skip fields per rules.

File structure

Notes: The file is free-form text with no consistent delimiter structure. It contains mixed content including headers like 'Date:', 'Time:', and sample values such as names and phone numbers, but lacks a uniform column pattern across rows. This qualifies as unstructured data requiring a streaming email/phone extractor.

File structure

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

Notes: All columns are transactional/financial data (check numbers, dates, pay amounts) with no personal identifying information. CompanyName appears to be a vendor/business name, not a personal entity. No PII fields detected.

File structure

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

Notes: Only column 1 (NAME) contains PII. All other columns are internal IDs, timestamps, financial data, or internal codes that must be skipped per exclusion rules.

File structure

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

Notes: This file appears to be a holiday gift card recipient list with no actual PII data present. Columns 1 and 4 contain titles and company names, and column 7 contains address-like strings, but these are not valid personal addresses (they are placeholder or incomplete). There are no identifiable email, phone, DOB, or other PII values in the sample. All columns either contain non-PII data or are empty. Per exclusion rules, columns with 'Company' in the name are skipped regardless of values.

File structure

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

Notes: This appears to be a medical billing export with patient names, addresses, DOB, and phone numbers. Columns 0-2 and 4-5 appear to be headers or empty fields. Column 11 appears to be a placeholder or empty field. Total charges are shown at the end.

File structure

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

Notes: Medical billing record for Regenerative Orthopaedics and Spine Institute. File contains patient PII (name, DOB, phone) interleaved with clinic address header and billing/claims data (procedure codes, dates, amounts, provider names). Only 3 PII columns identified from structured data; remaining columns are either business addresses, procedure codes, timestamps, financial amounts, or provider names (all non-PII).

File structure

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

Notes: No PII columns detected in the provided rows. The file contains only pay period timestamps, monetary values, and status flags like 'STRIKE' and 'LAYOFF', which are transactional/business data. No personal identifiers (names, emails, addresses, etc.) are present in the visible sample.

File structure

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

Notes: This file contains only transaction records with service descriptions, dates, service providers, and payment amounts. No PII fields are present. All columns appear to be business/transactional data (service type, date, provider name, payment amount) and do not contain any personal identifiable information such as names, addresses, emails, phone numbers, etc. The provider names appear to be business names rather than individual person names.

File structure

Notes: free-form text with embedded names and amounts; no consistent delimiter structure

File structure

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

Notes: This file appears to be a calendar/work log tracking injury-related absences and medical appointments. It contains only dates, times, and descriptive text about work status (PPT/LOA/STD) and medical follow-ups. No PII fields (names, emails, phones, addresses, etc.) are present in the first 50 rows. The structure is tabular but lacks any identifiable personal information in the visible data.

File structure

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

Notes: 50 rows show medical appointment logs with From/To address columns containing PII. No email/phone/dob/names visible in sample. Address fields map to address1 (no address2 present).

File structure

Notes: free-form text with embedded names, phone numbers, and addresses; no consistent delimiter or header structure

File structure

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

Notes: This is not a PII file; it's purely transactional accounting data with business names and payment amounts. No personal identifiers (names, emails, phone numbers, addresses, etc.) are present. The column headers are missing, and the rows contain only service descriptions, dates, business names, and payment amounts. All entries are for business services rendered, with no client PII exposed.

File structure

Notes: free-form text with embedded names and amounts, no consistent delimiter or row structure

File structure

Notes: free-form text with embedded dates and medical leave notations; no consistent columnar structure

File structure

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

Notes: Only address columns contain PII. No emails, phone numbers, names, DOB, or SSN appear in the first 50 rows. The data represents medical appointment logs with origin/destination addresses.

File structure

Notes: The file is free-form text with no consistent column structure. It contains embedded personal names, medical facility names, addresses, and phone numbers, but lacks any row-based delimiter or repeated column pattern. The data appears to be a mix of medical transport logs, provider listings, and contact information without any CSV/TSV structure.

File structure

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

Notes: This file appears to be a billing summary with structured financial data and medical claim details. While it contains patient names (e.g., ASHOK REDDY, WING CHANG), phone numbers, and dates of birth, these are embedded within unstructured text lines and lack consistent column headers. The data is presented in a free-form tabular layout without a clear column mapping structure across rows. The presence of claim IDs, procedure codes, dates, and amounts indicates financial/transactional data rather than pure PII records. Due to the absence of consistent column headers and the mixed unstructured/free-form presentation, this file cannot be reliably mapped to standard PII columns. The breach context suggests sensitive data is present, but the format prevents automated column mapping.

File structure

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

Notes: This file appears to be a financial/billing summary with medical claim data. While it contains patient names (e.g., ASHOK REDDY, WING CHANG) and potentially sensitive identifiers like claim IDs, there are no explicit PII fields such as email, phone, DOB, SSN, or address in a recognizable format. The names appear to be embedded within the data rows without dedicated columns for PII. Given the structure, no columns map to defined PII fields. The file is primarily transactional with claim details and amounts.

File structure

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

Notes: No PII columns present. All columns are internal identifiers, timestamps, or non-personal data (e.g., personnel numbers, cost centers, wage types, hours worked). No email, phone, address, name, DOB, SSN, or other PII fields detected.

File structure

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

Notes: The provided data appears to be a structured CSV file, but the first few rows contain header-like text and empty fields rather than actual column names. The data rows start from row index 3 and contain time-period and numeric data (hours worked, wages). There are no identifiable PII fields (email, phone, name, address, etc.) in the visible rows. The sample shows only week ranges and financial data. Therefore, no PII columns can be mapped based on the first 50 rows. Additional rows may contain PII, but they are not visible 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

Notes: This is a medical billing document from Regenerative Orthopaedics and Spine Institute PC, not a structured data file. It contains free-form header information, a single patient record (Debra Edwards, DOB: 1961-01-13, Phone: (470)-829-0681), guarantor address, and a billing summary table with medical claims. The document mixes prose headers, address blocks, and tabular billing data without consistent delimiters or repeating column structure suitable for database import. The PII present (patient name, DOB, phone, address) is embedded within prose sections and a single-record context, not in a reusable columnar format. This file should be processed as unstructured medical document extraction rather than CSV column mapping.

File structure

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

Notes: 50 rows contain medical billing records with patient names, addresses, DOB, and phone numbers. Structured CSV format with embedded patient PII.

File structure

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

Notes: 50 rows contain medical billing records with patient names, addresses, DOB, and phone numbers. Columns 5 and 6 contain full names; column 9 contains city; column 10 contains state; column 11 contains ZIP; column 12 contains date of birth; column 13 contains phone number. All other columns contain claim IDs, procedure codes, dates, and amounts — no PII.

File structure

Notes: This is a free-form text document with no consistent column structure. It contains embedded PII such as names (Debra Edwards), address (601 Dodds Ave, Chattanooga, TN 37404-3911, Jonesboro, GA 30238), phone number (423)826-8220, and date of birth 1961-01-13. Due to the unstructured nature, column mapping is not applicable; the file should be processed through a streaming email/phone extractor.

File structure

Notes: The file contains unstructured medical visit records with names embedded in the description field. No consistent columnar structure exists across rows — each line is a free-text entry describing appointments, doctors, locations, and payments. This requires unstructured parsing to extract PII.

File structure

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

Notes: All columns represent shipping/logistics data (order IDs, revenue codes, locations, miles, freight charges). No PII fields detected. Columns like 'Customer' and 'Carrier' contain business names, not personal identifiers. Timestamps are shipping dates, not DOB. All values are internal business metrics.

File structure

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

Notes: All columns contain business/transactional data (order IDs, revenue codes, shipping details, carrier payments). No personal identifiable information (PII) is present. Columns like 'Customer' and 'Carrier' contain business entity names, not personal names. Timestamps and financial figures are non-PII per exclusion rules.

File structure

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

Notes: CSV file with call log data from Skibiel Law. Contains PII in Contact Name, Phone, Email, City, State, and Zip columns. Other columns contain call metadata, timestamps, and URLs which are not PII.

File structure

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

Notes: This file appears to be a financial spreadsheet containing budget categories, income and expense figures, and fundraising summaries. There are no identifiable personal information fields present in the visible data. All columns represent internal financial tracking and do not contain any PII fields such as names, addresses, contact information, or other personally identifiable data.