← All datasets

hallauerlaw.net

Jul 20, 2026

100,329
Records
397
Files
Jul 20, 2026
Added

Data breach of Hallauer Law, a law firm. The archive contains highly sensitive legal case files including FBI investigative records, electronic surveillance (ELSUR) logs, phone records (CDRs with cell tower data), witness interview summaries, drug buy surveillance reports, and criminal case documentation related to gang investigations (MSB - likely a gang/criminal organization). The data includes personally identifiable information of suspects, witnesses, and confidential human sources.

Data found in this dataset

First nameLast nameMiddle nameUsernameAddressCityStateCountryGenderSuffixskipphoneaddress2zipfullNamedobssn

Search this dataset

Scoped to this dataset. Fill any combination — results match if any field hits.

Source files

Expand any file to inspect its column headers and the LLM's field-mapping reasoning, recorded during ingestion.

hallauerlaw.net__hallauerlaw.net_000009129_NATIVE__Sheet1.csv
0 rows

File structure

Notes: The file is a list of document descriptions and administrative records, not structured tabular data with columns. It contains free-form text entries describing various investigative documents, interviews, and evidence summaries related to criminal cases. There are no consistent columns or delimiters across the lines, and the data is purely descriptive prose.

hallauerlaw.net__hallauerlaw.net_000009130_NATIVE__Sheet1.csv
3 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighcolumn contains sequential case identifiers and administrative codes, not personal data
1skiphighcolumn contains case descriptions and administrative notes, no PII present
2skiphighcolumn contains reference serial numbers, not personal identifiers

Notes: This file appears to be an index or case management log from Hallauer Law's law enforcement data breach. It contains administrative case references, serial numbers, and operational notes rather than personal identifiable information. No PII fields (email, phone, name, address, etc.) are present in the visible columns. The data consists entirely of case tracking metadata, operational codes, and administrative notes related to FBI investigations, surveillance requests, and case documentation.

hallauerlaw.net__hallauerlaw.net_000009240_NATIVE__PTN_7577487384.csv
3 columns249 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit US phone numbers in (area code) format
1phonehigh[1] header 'CALLED_NBR', values are 10-digit US phone numbers in (area code) format
2phonehigh[2] header 'DIALED_DIGITS', values are 10-digit US phone numbers or partial numbers

Notes: This is a call detail record (CDR) file from Hallauer Law breach. Columns 0-2 contain caller, callee, and dialed phone numbers. Columns 3-25 are internal tracking fields, timestamps, durations, cell tower IDs, and empty fields — none contain PII. No email addresses, names, DOB, or SSNs appear in the sample.

hallauerlaw.net__hallauerlaw.net_000009241_NATIVE__PTN_7577487384.csv
3 columns249 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit phone numbers with area code
1phonehigh[1] header 'CALLED_NBR', values are 10-digit phone numbers with area code
2phonehigh[2] header 'DIALED_DIGITS', values are phone numbers (some missing area code)

Notes: This is a phone call detail record (CDR) file from Hallauer Law's surveillance data. Columns 0-2 contain caller/receiver/dialed phone numbers. Columns 3-25 are system/technical fields (direction, timestamps, duration, cell tower IDs) and contain no PII. No names, addresses, or other PII fields are present in the first 50 rows.

hallauerlaw.net__hallauerlaw.net_000009245_NATIVE__PTN_7575614063.csv
3 columns197 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are valid US phone numbers with area code and prefix
1phonehigh[1] header 'CALLED_NBR', values are valid US phone numbers with area code and prefix
2phonehigh[2] header 'DIALED_DIGITS', values are valid US phone numbers with area code and prefix

Notes: This is a call detail record (CDR) dataset from Hallauer Law's breach. Columns 0-2 contain calling/calling/called numbers (phone). Columns 3-25 contain non-PII metadata (direction, timestamps, duration, network IDs, cell tower identifiers), all skipped per rules. No emails, names, addresses, DOB, SSN, or usernames present.

hallauerlaw.net__hallauerlaw.net_000009246_NATIVE__PTN_7575614063.csv
3 columns197 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR' and values are valid US phone numbers in (XXX) XXX-XXXX format
1phonehigh[1] header 'CALLED_NBR' and values are valid US phone numbers in (XXX) XXX-XXXX format
2phonehigh[2] header 'DIALED_DIGITS' and values are valid US phone numbers in (XXX) XXX-XXXX format

Notes: Only columns 0, 1, and 2 contain PII (phone numbers). All other columns are internal call detail records (direction, timestamps, durations, cell tower IDs) and should be skipped per exclusion rules for internal IDs and timestamps.

hallauerlaw.net__hallauerlaw.net_000009302_NATIVE__Sheet1.csv
11 columns13 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0firstNamehigh[0] header 'FRST_NM' (first name abbreviation), values are uppercase given names like 'KATIE'
1middleNamehigh[1] header 'MI' (middle initial), standard abbreviation for middle name/initial
2lastNamehigh[2] header 'LAST_NM' (last name abbreviation), values are uppercase surnames
3suffixhigh[3] header 'SFX' (suffix abbreviation), generational/credential suffix field
4address1high[4] header 'ADDR_LINE1', values are street addresses like '3024 REYNOLDS ST'
5address2high[5] header 'ADDR_LINE2', standard second address line field
6cityhigh[6] header 'CITY', values are city names like 'BRUNSWICK'
8statehigh[8] header 'ST_CD' (state code), values are US state abbreviations like 'GA'
9ziphigh[9] header 'PSTL_CD' (postal code), values are 5-digit ZIP codes like '31520'
10countryhigh[10] header 'CNTRY_CD' (country code), values are country codes like 'US'
16phonehigh[16] header 'PHONE', values are formatted US phone numbers like '(929) 363-3371'

Notes: 29 columns total, 11 contain PII. Columns 7 (COUNTY), 11 (PRIM_ADDR_TAX_FLG), 12 (STR_SVC_HCUST_NBR), 13 (LOC_NBR), 14 (CUST_NBR), 15 (PHN_NBR_TYP_CD), 17 (PHN_EXT_NBR), 18 (CUST_ORD_NBR), 19 (SLS_DT), 20 (REG), 21 (TRAN), 22 (SEQ), 23 (STR_NBR), 24 (RETL_SLS), 25 (SLS_TM), 26 (PAYMT_METH_CD), 27 (PAYMT_AMT), and 28 (CARDHLDR_ACCT_NBR) are skipped as internal/transactional/financial identifiers. Note: CARDHLDR_ACCT_NBR contains what appear to be payment card account numbers — these are financial identifiers not in the supported PII field types and are therefore skipped.

hallauerlaw.net__hallauerlaw.net_000012075_NATIVE__Sheet1.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The file appears to be a series of narrative interview records with embedded PII (names, DOBs, SSNs, addresses). All lines have different shapes and contain prose descriptions rather than tabular data. While PII is present inline (emails/phones not visible in sample), the lack of consistent column structure triggers unstructured processing.

hallauerlaw.net__hallauerlaw.net_000014918_NATIVE__Sheet1.csv
1 column103 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4fullNamehigh[4] values are full names like "Bynum, Lloyd"; header "Inmate" implies PII

Notes: CSV with 5 columns. Only column 4 (Inmate) contains PII (full names). Other columns are offense type, dates, institutions, and location codes — no PII. No emails, phones, or other identifiers present in sample.

hallauerlaw.net__hallauerlaw.net_000014982_NATIVE__LEGEND.csv
0 rows

File structure

Notes: The file is a README/prose header sheet describing a 'Mtigate Legend and ID Types Sheet' with no actual data rows. It contains metadata about columns (e.g., 'US Dollars Sent', 'MTCN Transaction Number', 'Sender’s Full Name Provided by Sender') but no actual records with PII values. Since it lacks structured data rows and only contains descriptive text, it is unstructured and should be processed as such.

hallauerlaw.net__hallauerlaw.net_000014982_NATIVE__Received_transctions.csv
17 columns35 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'SName', values are full names like 'GEORGE ARMSTRONG', 'BRANDON HAYNES' — sender full name
4skiphigh[4] header 'SPhone' — sender phone number
8skiphigh[8] header 'SDOB' — sender date of birth
14address1high[14] header 'SAddress' — sender street address
15cityhigh[15] header 'SCity' — sender city
16statehigh[16] header 'SState' — sender state
17ziphigh[17] header 'SZip', values like '11412', '23325' — sender zip code
18countryhigh[18] header 'SCountry', values 'US' — sender country
21fullNamehigh[21] header 'PName', values are full names like 'ADRIENNE WILLIAMS' — payee full name
23phonehigh[23] header 'PPhone', values like '17032708031', '17574047229' — payee phone numbers
27dobhigh[27] header 'PDOB', values like '1960.07.31', '1973.05.21' — payee date of birth
31address1high[31] header 'PAddress', values like '300 S WHITING ST', '3414 GRACIE RD' — payee street address
32cityhigh[32] header 'PCity', values like 'ALEXANDRIA', 'CHESAPEAKE' — payee city
33statehigh[33] header 'PState', values like 'VA' — payee state
34ziphigh[34] header 'PZip', values like '22304', '23325' — payee zip code
35countryhigh[35] header 'PCountry', values 'US' — payee country
53skiphigh[53] header 'SEMail' — sender email address

Notes: This appears to be a Western Union wire transfer records dataset (money transfer logs) containing both sender (S-prefix) and payee (P-prefix) PII. Columns 26 (PId Number2) and 29 (PId Number) appear to be government ID numbers (e.g., SSN partial '579940087', passport/ID numbers like 'T62680873') — mapped cautiously as skip since they are ID document numbers not matching SSN pattern strictly, but warrant manual review. Send Agent and Pay Agent address columns (38-51) appear to be retail agent location data (business addresses), not personal PII, and are skipped. Columns SId Number, SId Number2, SId Type, SId Location, PId Type, PId Number, PId Number2, PId Location may contain government-issued ID data and should be reviewed separately.

hallauerlaw.net__hallauerlaw.net_000014982_NATIVE__Sent_transcations.csv
17 columns43 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'SName', values are full names in uppercase (e.g., 'ADRIENNE WILLIAMS') — sender full name
4phonehigh[4] header 'SPhone', values are 10-digit phone numbers (e.g., '7574047229') — sender phone
8dobhigh[8] header 'SDOB', values match YYYY.MM.DD date pattern (e.g., '1973.05.21') — sender date of birth
14address1high[14] header 'SAddress', values are street addresses (e.g., '344 GRACIE RD') — sender address
15cityhigh[15] header 'SCity', values are city names (e.g., 'CHESAPEAKE') — sender city
16statehigh[16] header 'SState', values are US state abbreviations (e.g., 'VA') — sender state
17ziphigh[17] header 'SZip', values are 5-digit ZIP codes (e.g., '23325') — sender ZIP
18countryhigh[18] header 'SCountry', values are country codes (e.g., 'US') — sender country
21fullNamehigh[21] header 'PName', values are full names in uppercase (e.g., 'BRANDON HAYNES') — payee/recipient full name
23skiphigh[23] header 'PPhone' — payee/recipient phone number
27skiphigh[27] header 'PDOB' — payee/recipient date of birth, parallel to SDOB
31address1high[31] header 'PAddress' — payee/recipient street address, parallel to SAddress
32cityhigh[32] header 'PCity' — payee/recipient city, parallel to SCity
33statehigh[33] header 'PState' — payee/recipient state, parallel to SState
34ziphigh[34] header 'PZip' — payee/recipient ZIP, parallel to SZip
35countryhigh[35] header 'PCountry', values are country codes (e.g., 'US', 'JM') — payee/recipient country
53skipmedium[53] header 'SEMail' — sender email address; values appear whitespace-padded/blank in sample but column is clearly an email field

Notes: This appears to be a money transfer transaction log (e.g., Western Union or MoneyGram records). S-prefixed columns (SName, SPhone, SDOB, SAddress, etc.) belong to the sender; P-prefixed columns (PName, PPhone, PDOB, PAddress, etc.) belong to the payee/recipient. Both parties are individuals with PII. Agent name/address columns (Send Agent Name, Pay Agent Name, etc.) are business/retail locations and are skipped. SDebtor Account contains a masked credit card number (skipped as it is a payment instrument, not a standard PII field type). SPreferred Card and Control Number are internal transaction identifiers (skipped).

hallauerlaw.net__hallauerlaw.net_000014986_NATIVE__9176539249-1.csv
3 columns7,762 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit numbers
1phonehigh[1] header 'CALLED_NBR', values are 10-digit numbers
2phonehigh[2] header 'DIALED_DIGITS', values are 10-digit numbers

Notes: CSV file with 9 columns, containing call detail records. Only columns 0, 1, and 2 contain PII (phone numbers). Other columns represent call metadata (dates, durations, types) and internal network IDs (NEID) which are not PII.

hallauerlaw.net__hallauerlaw.net_000014987_NATIVE__3474249779-1.csv
3 columns18,498 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit numbers
1phonehigh[1] header 'CALLED_NBR', values are 10-digit numbers
2phonehigh[2] header 'DIALED_DIGITS', values are 10-digit numbers

Notes: CSV file with 50 rows of call detail records. Only columns 0, 1, and 2 contain PII (phone numbers). Other columns contain call metadata (dates, durations, types) and are skipped.

hallauerlaw.net__hallauerlaw.net_000015142_NATIVE__Sheet1.csv
0 rows

File structure

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

Notes: This is NOT structured PII data. The file contains law enforcement operational logs with timestamps, locations, and narrative descriptions of controlled purchases involving contraband. While names appear (e.g., AARON GERALD, JAMES BUMBRY), these are operational codenames or aliases used in FBI investigations rather than personal PII fields like email or phone. No columns map to defined PII fields (email, phone, dob, etc.). The content is free-form narrative data describing criminal activity, not a delimited record structure with personal identifiers.

hallauerlaw.net__hallauerlaw.net_000015295_NATIVE__Results.csv
7 columns1 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4fullNamehigh[4] header 'CUSTOMER_NAME', values are full names like 'BEV SMITH'
7phonehigh[7] header 'PHONE_NUMBER', values are 10-digit numbers
8address1high[8] header 'STREET_NUMBER', values are street numbers
9address1high[9] header 'STREET_NAME', values are street names
10ziphigh[10] header 'POSTAL_CODE', values are 5-digit zip codes
11cityhigh[11] header 'CITY_NAME', values are city names
12statehigh[12] header 'REGION_NAME', values are state names

Notes: Only columns 4,7,8,9,10,11,12 contain PII. Others are internal IDs, timestamps, financial data, or non-PII codes.

hallauerlaw.net__hallauerlaw.net_000015295_NATIVE__SQL.csv
0 rows

File structure

Notes: free-form text with SQL query fragments; no consistent column structure or PII fields present in the sample rows

hallauerlaw.net__hallauerlaw.net_000015340_NATIVE__Results1.csv
3 columns52 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4phonehigh[4] header 'Dialed#', values are 10-digit numbers
12firstNamehigh[12] header 'First Name', values are uppercase given names
13lastNamehigh[13] header 'Last Name', values are uppercase surnames

Notes: This is a phone call detail record (CDR) file from Hallauer Law's surveillance system. Contains call metadata and PII for participants. Only firstName, lastName, and dialed phone numbers are PII. All other columns are system metadata, status flags, or internal tracking codes.

hallauerlaw.net__hallauerlaw.net_000015340_NATIVE__Summary.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent columnar structure. It appears to be a report or log from a call detail system with headers and values scattered across lines rather than in a tabular format. There are no identifiable PII columns to map.

hallauerlaw.net__hallauerlaw.net_000015422_NATIVE__Results.csv
7 columns1 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4fullNamehigh[4] header CUSTOMER_NAME, values are full names like 'BEV SMITH'
7phonehigh[7] header PHONE_NUMBER, values are 10-digit numbers
8address1high[8] header STREET_NUMBER, paired with STREET_NAME as address components
9address1high[9] header STREET_NAME, paired with STREET_NUMBER as address components
10ziphigh[10] header POSTAL_CODE, values are 5-digit zip codes
11cityhigh[11] header CITY_NAME, values are city names
12statehigh[12] header REGION_NAME, values are state names

Notes: 14 total columns; 7 contain PII. Columns 0,1,2,3,5,6,13 are excluded per rules: LOCATION_CODE (internal code), ORDER_DATE and ACTUAL_ORDER_DATE (timestamps), ORDER_NUMBER and CARD_HASH (internal IDs), FINAL_PRICE (financial), ADDRESS_TYPE (classification)

hallauerlaw.net__hallauerlaw.net_000015422_NATIVE__SQL.csv
0 rows

File structure

Notes: free-form text with SQL query fragments, no consistent columnar structure

hallauerlaw.net__hallauerlaw.net_000015434_NATIVE__3474249779-1.csv
3 columns17,911 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit numbers
1phonehigh[1] header 'CALLED_NBR', values are 10-digit numbers
2phonehigh[2] header 'DIALED_DIGITS', values are 10-digit numbers

Notes: CSV file with 50 rows of call detail records. Only columns 0, 1, and 2 contain PII (phone numbers). Other columns contain call metadata (dates, durations, call types) and are not PII.

hallauerlaw.net__hallauerlaw.net_000016529_NATIVE__Sheet1.csv
0 rows

File structure

Notes: The file contains conversational call summaries with embedded phone numbers, names, and relationship details. No consistent column structure exists across rows.

hallauerlaw.net__hallauerlaw.net_000016632_NATIVE__Sheet1.csv
2 columns18 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3dobhighheader "DOB" resolves to PII field "dob"
4ssnhighheader "SSN" resolves to PII field "ssn"

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

hallauerlaw.net__hallauerlaw.net_000016726_NATIVE__Sheet1.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0lastNamehigh[0] header 'LAST NAME', values are surnames
1firstNamehigh[1] header 'FIRST NAME', values are given names

Notes: Only columns 0 and 1 contain PII (lastName and firstName). Columns 2-17 are internal IDs, case flags, vehicle/product data, or empty — all skipped per rules.

hallauerlaw.net__hallauerlaw.net_000016822_NATIVE__Sheet1.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1lastNamehigh[1] header 'LAST NAME', values are surnames
2firstNamehigh[2] header 'FIRST NAME', values are given names

Notes: This is a structured CSV with headers. Columns 0 (MAD STONE BLOODS) and 4 (LOCATION) contain non-PII organizational codes or locations not mappable to address fields. Column 3 (ALIAS) contains nicknames which are not mapped to any PII field per rules. Column 5 (RANK/TITLE) contains role/designation data and is skipped.

hallauerlaw.net__hallauerlaw.net_000016831_NATIVE__Sheet1.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

hallauerlaw.net__hallauerlaw.net_000016864_NATIVE__Sheet1.csv
2 columns78 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1phonehighheader "Telephone Number" resolves to PII field "phone"
2address1highheader "Address" resolves to PII field "address1"

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

hallauerlaw.net__hallauerlaw.net_000017123_NATIVE__Sheet1.csv
0 rows

File structure

Notes: The file is a glossary of slang terms and meanings with no structured columnar data. It contains free-form text mapping gang-related lingo to meanings, but lacks any consistent delimiter or row structure. No PII fields are present in this unstructured content.

hallauerlaw.net__hallauerlaw.net_000017238_NATIVE__Sheet1.csv
10 columns110 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Name', values are full names
1fullNamehigh[1] header 'Alias', values are nicknames/aliases
2fullNamehigh[2] header 'Diamond AKA', values are additional aliases
3skiphigh[3] header 'Rank', contains organizational roles not PII
4dobhigh[4] header 'DOB', values match ISO date format
5ssnhigh[5] header 'SSN', values match SSN pattern (3-2-4 digits)
6skiphigh[6] header 'Inc?', contains yes/no flags
7skiphigh[7] header 'DOC #', contains internal identification numbers
8address1high[8] header 'Address', values are locations/prisons/streets
9phonehigh[9] header 'Phone Number', values match phone number patterns

Notes: 50 rows analyzed. Columns 0-2 contain full names and aliases. Column 4 contains dates of birth in ISO format. Column 5 contains SSNs. Column 8 contains addresses (streets, cities, prisons). Column 9 contains phone numbers. Columns 3, 6, and 7 contain non-PII organizational data and internal IDs.

hallauerlaw.net__hallauerlaw.net_000017366_NATIVE.CSV
6 columns21 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Full Name', values contain name fragments like 'CORBIN'
1gendermedium[1] header 'Gender'; values are garbled/shifted but header is clear
2ssnhigh[2] header 'SSN', values are None in sample but column is clearly SSN
3dobhigh[3] header 'DOB/Age', date of birth field
5address1high[5] header 'Address', physical address field
6phonehigh[6] header 'Phone Information', values include phone number pattern '434-831-2113'

Notes: Data is severely malformed with column values appearing shifted/garbled across columns. Mapped based on header names. Columns 4 (DOD/Age at Death), 7 (Property), 8 (Motor Vehicle), 9 (People at Work), 10 (LexID) are skipped as non-PII or internal identifiers.

hallauerlaw.net__hallauerlaw.net_000017368_NATIVE.CSV
7 columns7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0lastNamemedium[0] header 'Full Name' but values show last-name-only fragments like WALTON, HUBBERT mixed with address noise; best mapped as lastName
1firstNamemedium[1] header says 'Gender' but values are clearly personal names (SHUEROD, HUSSAIN, HASSAN) — data is column-shifted; mapped by value
3ssnhigh[3] header says 'DOB/Age' but value '153-74-7816' matches SSN pattern NNN-NN-NNNN — data is column-shifted; mapped by value
4dobhigh[4] header says 'DOD/Age at Death' but value '3/7/1982 (32)' matches date-of-birth pattern — data is column-shifted; mapped by value
5phonehigh[5] header says 'Address' but value '2647725688' is a 10-digit phone number — data is column-shifted; mapped by value
6address1high[6] header says 'Phone Information' but value '1075 GROVE ST APT' is a street address — data is column-shifted; mapped by value
7citymedium[7] header says 'Property' but value 'IRVINGTON' is a city name consistent with NJ addresses seen in col 0 — data is column-shifted; mapped by value

Notes: File is severely column-shifted/corrupted — header names do not correspond to their actual data values. All mappings are driven by value patterns rather than headers. Columns 2, 8, 9, 10, 11 have no usable sample values and cannot be confidently mapped. This file contains sensitive legal/law enforcement PII including SSNs, DOBs, phone numbers, and addresses of suspects, witnesses, and CHSs from FBI gang investigations.

hallauerlaw.net__hallauerlaw.net_000017371_NATIVE__Combined_Detail_LE.csv
8 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_000017372_NATIVE__Combined_Detail_LE.csv
105 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_000017373_NATIVE__Combined_Detail_LE.csv
8 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Arr_Labels.csv
0 rows

File structure

Notes: This is free-form text with no consistent column structure. The data appears to be investigative case notes with embedded names and addresses, but lacks a repeating delimiter pattern across rows. Sample shows lines with varying formats and content shapes, meeting unstructured criteria.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Case_Report_Data.csv
1 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Case_Summary.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The lines appear to be case summary notes with varying fields like offense, date, victim, suspect, etc. There are no identifiable PII columns in a structured format; any potential PII is embedded within prose descriptions and would need unstructured processing.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Def__1_Detention_Sheet.csv
0 rows

File structure

Notes: This is a free-form text file with embedded PII values rather than a structured CSV/TSV. The data appears to be investigative case notes with lines containing names, dates of birth, and other PII. The format lacks consistent delimiters and row structures, satisfying the unstructured criteria (a), (b), and (c). No column mapping is performed.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Def__1_FF.csv
0 rows

File structure

Notes: This is a free-form legal document structure from Hallauer Law breach. No consistent columnar pattern exists across rows — each line contains different legal case metadata (e.g., court actions, officer names, dates, case types). There are no repeated fields or structured PII columns. Sample shows document headers and free-text case notes rather than tabular data. Per rules, unstructured files with no shared delimiter structure are mapped to empty columns object.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Def__1_Magistrate.csv
0 rows

File structure

Notes: This file is unstructured free-form text with no consistent column delimiter or header row. The sample rows contain legal case documentation with embedded phone numbers (e.g., 664-7032, 230-25-9788) and other personal references, but lack a tabular structure. All rows show varying content shapes and lack a shared delimiter pattern.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Def__2_Detention_Sheet.csv
0 rows

File structure

Notes: This is a README / instruction file, not structured data. The lines contain form-filling instructions and field labels rather than actual records. No consistent delimiter or columnar structure exists; instead it's free-form text describing how to fill out a form. Therefore it must be handled as unstructured content.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Def__2_FF.csv
0 rows

File structure

Notes: This is free-form text data with no consistent delimiter structure. The file appears to be a collection of legal case notes and reports from the Norfolk Police Department, with each line containing different types of legal case metadata and descriptions rather than structured tabular data. There are no identifiable PII columns in a structured format, but the unstructured nature means any embedded PII would need to be extracted via text processing.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Def__2_Magistrate.csv
0 rows

File structure

Notes: This is a free-form document with no consistent column structure. It contains unstructured text such as legal warrant requests, court information, and investigative notes. While there are some potential PII fragments (e.g., '664-7032' which could be a phone number), the lack of a consistent delimiter or row structure means this should be processed as unstructured text. The content includes legal case identifiers, court references, and investigative details rather than tabular PII fields.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Def__3_Detention_Sheet.csv
0 rows

File structure

Notes: The provided sample data appears to be free-form text rather than structured tabular data. The lines contain legal form instructions and placeholder text rather than consistent columnar data. There is no evidence of a consistent delimiter or repeating row structure across the sample lines. While there are some PII-like terms in the text (e.g., 'Last Name', 'First Name', 'DOB'), these appear to be form field labels rather than actual data rows. Given the unstructured nature of the content and the lack of consistent columnar pattern, this should be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Def__3_FF.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. It contains legal case documentation, court instructions, and procedural notes rather than tabular data with PII columns. Each line represents different case metadata and instructions rather than structured records.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Def__3_Magistrate.csv
0 rows

File structure

Notes: The file appears to be free-form text containing legal case documentation and investigative records. There is no consistent columnar structure; instead, each line contains unstructured prose with embedded identifiers like phone numbers and references. The presence of phrases such as 'REQUEST FOR MAGISTRATE’S WARRANT', 'Investigator:', 'Court:', and 'Accused' confirms this is not a delimited dataset. While there are visible phone numbers (e.g., '664-4196', '664-7032'), the lack of a consistent delimiter or row structure means this should be treated as unstructured text for processing.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Grand_Jury.csv
0 rows

File structure

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

Notes: This file is unstructured text with no consistent delimiter or column mapping. It contains free-form legal case notes and narrative text rather than tabular data. No PII columns can be mapped because there is no column structure.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Inv_Labels.csv
0 rows

File structure

Notes: free-form text with embedded names and locations, no consistent delimiter structure

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__JCF.csv
1 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. It contains phrases like 'JUVENILE INFORMATION', 'Smith, Pierre D', and '924 Trice Terr B', indicating it's unstructured data with embedded PII. This should be processed as unstructured text with embedded emails/phones extraction.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__JFV.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The file appears to be a collection of legal case documents, forms, and correspondence from the Hallauer Law breach. There are no structured columns with PII in a tabular format; instead, the data consists of prose, headers, and form fields that vary per line. While there may be embedded PII (names, agencies, dates) in the text, the unstructured nature requires routing through a streaming email/phone/text extractor.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__JPC.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent columnar structure. The sample shows narrative legal forms and affidavits, not structured data. Though there are embedded personal identifiers (e.g., 'Smith, Pierre D', '924 Trice Terr B Norfolk, VA 23502', '5/2/82', '757 561-4063', 'M'), these appear inline within prose rather than as delimited columns. The file must be processed through unstructured text extraction.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__PD881_P1.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. The sample rows contain narrative text, report headers, and scattered data points rather than a tabular format. Values like phone numbers and names appear inline in prose, indicating unstructured content requiring special handling.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__PD881_P2.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent columnar structure. The content appears to be narrative descriptions from police reports and evidence logs, with no reusable tabular data or repeating field patterns. No PII columns can be mapped.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__PD881_P2A.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The sample shows lines with labels like "Name:", "Address:", "E-mail Address:", "Soc #:", "DOB:", "Phone:", etc., but there is no fixed delimiter or row structure. The data appears to be a mix of narrative entries and form-like fields, common in investigative reports. Since there is no consistent delimiter and lines have varying shapes, this should be processed as unstructured text with embedded PII extraction.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__PD881_P3.csv
1 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. The sample rows show unstructured legal case notes and property descriptions from a law enforcement context, with no repeating columnar pattern or delimiter. This matches the description of Hallauer Law breach data containing FBI investigative records, surveillance logs, and case documentation rather than structured tabular data.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__PD881_P4.csv
0 rows

File structure

Notes: This file appears to be a free-form legal document or case file with no consistent column structure. The data consists of narrative text, headers, and empty fields typical of PDF scans or printed documents. There are no delimited columns to map, and the content appears to be prose rather than structured records.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Start_Page.csv
1 rows

File structure

Notes: This is not a structured dataset; it's a free-form text form with prompts and sample values rather than actual records. The lines show form labels and example data, not tabular columns with repeated PII across rows. There is no consistent delimiter or repeated structure that would allow column mapping. The sample shows form instructions ('Step 1 of 6:') and example values in the same line as labels, not a CSV or table. Per rules, unstructured files with no consistent structure and visible PII in free text should return empty columns object.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__Subpoena.csv
0 rows

File structure

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

Notes: This file appears to be a template or form with placeholder text and no actual PII data in the first 50 rows. All columns contain generic legal/formatted text like 'City of Norfolk', 'Commonwealth of Virginia', 'Norfolk', etc. No PII fields such as names, emails, addresses, or phone numbers are present in the visible data. Therefore, no columns map to PII fields.

hallauerlaw.net__hallauerlaw.net_000017404_NATIVE__lists.csv
0 rows

File structure

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

Notes: This file appears to be a free-form data listing or codebook rather than structured PII records. Columns represent categories (race, sex, vehicle types, offense codes) with sample values showing categories rather than actual personal data. No identifiable PII fields (names, addresses, emails, etc.) are present in the header or sample rows. The content describes list categories for a law enforcement or court system database, not actual breach records containing personal information.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Arr_Labels.csv
0 rows

File structure

Notes: This is free-form text with no consistent column structure. Sample lines contain mixed content such as case descriptions, names in parentheses, and various legal annotations. No regular delimiter pattern is present across rows, and column positions vary. However, embedded names like 'Smith, Pierre D (B/M 31)' and addresses like '7932 Harold Street' are visible, indicating the file should be processed through a streaming extractor for names, addresses, and potentially other PII patterns.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Case_Report_Data.csv
1 rows

File structure

Notes: The file is free-form text with no consistent delimiter structure. Lines contain mixed content including case updates, names, and descriptions, but do not follow a structured tabular format. Contains embedded personal names and case notes, but no consistent columns to map.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Case_Summary.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent delimiter. Each line appears to represent a different section of a case summary (Offense, Date, Victim(s), Suspect(s), etc.) rather than structured tabular data. The content is narrative/prose style with no repeating column pattern across rows.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Def__1_Detention_Sheet.csv
0 rows

File structure

Notes: This is a free-form document with no consistent columnar structure. The lines contain instructional text and sample data fragments rather than a tabular dataset. There are no repeating patterns or delimiters across rows, and the content appears to be a mix of form instructions and example entries rather than structured PII records.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Def__1_FF.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The data appears to be legal case notes and reports from Norfolk Police Department, with lines containing case descriptions, officer names, and other unstructured text. There are no delimited columns to map to PII fields.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Def__1_Magistrate.csv
0 rows

File structure

Notes: The provided data is free-form text with no consistent delimiter structure. Lines contain mixed content (case headers, investigator notes, physical descriptions) and do not conform to a tabular format. Despite the presence of some PII-like values (e.g., '664-7032', '230-25-9788'), the lack of a consistent column pattern means this must be processed as unstructured text. The content appears to be legal case documentation with embedded PII that should be extracted via streaming processing.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Def__2_Detention_Sheet.csv
0 rows

File structure

Notes: This is unstructured data with free-form notes and instructions rather than tabular records. The sample shows bullet points, form instructions, and placeholder text rather than actual columnar data. No consistent delimiter or row structure exists across the provided lines, and the content appears to be form instructions rather than actual PII records.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Def__2_FF.csv
0 rows

File structure

Notes: This file is unstructured text data. The sample shows free-form entries with inconsistent fields and no consistent delimiter. The entries appear to be narrative or form-like notes (e.g., "FIRST TIME FELONY/INITIAL HEARING REPORT", "Continuance"), not tabular data. There are no repeated column structures, and the content varies widely per line. Even though there are no visible emails or phone numbers in the sample, the lack of consistent structure means it must be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Def__2_Magistrate.csv
0 rows

File structure

Notes: This file is not structured tabular data. It appears to be free-form text containing legal case notes, warrant requests, and investigative summaries. The content includes prose and no consistent columnar structure across rows. While there are occasional phone numbers visible (e.g., 664-4196, 664-7032), the data does not conform to a CSV or other delimited format with repeating columns. Therefore, it is classified as unstructured text for downstream processing.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Def__3_Detention_Sheet.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. The sample rows contain instructions, form notes, and placeholder text rather than structured data. While there are some hints of PII fields (e.g., 'Last Name', 'First Name', 'DOB', 'Middle Name', 'Suffix', 'Home Phone'), these appear as part of form instructions rather than actual data rows. Given the unstructured nature of the content and lack of consistent delimiters or row patterns, this should be processed as unstructured text for embedded PII extraction.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Def__3_FF.csv
0 rows

File structure

Notes: The provided sample rows appear to be free-form text with no consistent delimiter or column structure. The content includes report titles, officer names, case types, and instructions, but lacks a tabular format. While some rows contain what could be interpreted as names (e.g., 'B. E. Pugh'), the overall structure does not conform to a CSV or any other structured format. Therefore, this is classified as unstructured text.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Def__3_Magistrate.csv
0 rows

File structure

Notes: This is free-form text with no consistent columnar structure. The sample rows contain legal document headers and fields like phone numbers, DOB, and other case metadata, but they do not follow a consistent delimiter or column pattern across rows. Therefore, it is classified as unstructured text with embedded PII.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Grand_Jury.csv
0 rows

File structure

Notes: The file is unstructured text with no consistent delimiter or column structure. It appears to be a free-form document containing legal case notes, grand jury reports, and investigative summaries. While there are some embedded names and dates, the format does not allow for column mapping. This will be processed by unstructured text analysis.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Inv_Labels.csv
0 rows

File structure

Notes: This file is a free-form text document with no consistent delimiter structure. It contains embedded PII such as names and addresses within prose lines (e.g., 'Singleton, Teshia V(B/F 27)', '7932 Harold Street'). The unstructured format and variable line shapes meet the criteria for unstructured opt-out processing.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__JCF.csv
1 rows

File structure

Notes: This is a free-form document containing form templates and header lines rather than structured tabular data. The lines shown are form titles, field labels, and placeholders rather than actual record rows. No consistent delimiter or row structure exists across the sample lines, and the content appears to be descriptive text of a legal intake form rather than imported data records. While the sample contains field labels that would normally map to PII (e.g., 'LAST NAME', 'FIRST', 'ADDRESS', 'STATE', 'ZIP', 'SSN', 'DOB', 'AGE', 'MALE/FEMALE'), these are not actual data rows but rather the titles/labels of fields on a form template. Therefore this file must be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__JFV.csv
0 rows

File structure

Notes: The provided sample shows unstructured text data (prose) with no consistent columnar structure. Each row contains different content shapes and free-form text, indicating this is not a delimited file but rather a collection of free-form documents or notes. This matches the description of legal case files containing FBI investigative records, surveillance logs, and interview summaries which are typically narrative-based. Since there is no consistent delimiter and lines have wildly different content, this is classified as unstructured text.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__JPC.csv
0 rows

File structure

Notes: The file is free-form legal affidavit text with no consistent column structure. While there are embedded values that resemble PII (names, addresses, DOB, phone numbers, gender), the format does not have a consistent delimiter or row structure. This meets the unstructured opt-out criteria: (a) no shared delimiter, (b) lines have wildly different shapes and content, (c) visible emails/phones present. Therefore mapped as unstructured for streaming PII extraction.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__PD881_P1.csv
0 rows

File structure

Notes: The file is a free-form text file with no consistent delimiter structure. It appears to contain unstructured legal case notes and investigative reports with embedded personal identifiers like names, addresses, dates of birth, and phone numbers. Given the unstructured nature and presence of PII, this should be processed through a streaming email/phone extractor.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__PD881_P2.csv
1 rows

File structure

Notes: This file is free-form text with no consistent delimiter or column structure. The content appears to be police report headers and evidence categories (e.g., 'FELONY CASE REPORT', 'Autopsy', 'Fingerprints', 'Video'). There are no identifiable PII columns; it is purely descriptive metadata about evidence types and report categories. No structured data to map.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__PD881_P2A.csv
0 rows

File structure

Notes: This is an unstructured document containing free-form text with embedded PII. The lines show headers like 'Name:', 'Address:', 'Soc #:', 'DOB:', 'Phone:', 'E-mail Address:', etc., but there is no consistent delimiter or column structure across rows. This should be processed as unstructured text for PII extraction.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__PD881_P3.csv
1 rows

File structure

Notes: This is free-form text with no consistent column structure. The data appears to be from police department records and property logs with narrative descriptions rather than structured tabular data. While there may be embedded PII in the text, the format does not allow for column mapping and should be processed as unstructured content.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__PD881_P4.csv
0 rows

File structure

Notes: This file is free-form text (prose, case report notes) with no consistent column structure. It appears to be a PDF text extraction of police case documentation, containing unstructured narrative entries like 'FELONY CASE REPORT' and 'Probable Cause and Events of Case:'. No columns to map — use unstructured processing for embedded PII extraction.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Start_Page.csv
1 rows

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The sample lines contain form-like prompts and sample values (names, employee IDs, phone numbers) but lack a repeating tabular structure. The content appears to be a form template or instructional text rather than structured data records. The presence of embedded PII (e.g., 'B. E. Pugh', '664-7032') triggers the unstructured handling path.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__Subpoena.csv
0 rows

File structure

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

Notes: This is a legal subpoena form from Hallauer Law. The columns contain court information, case numbers, and general legal text. No PII fields are present in the first 50 rows; all columns appear to be headers or empty fields with legal procedural text.

hallauerlaw.net__hallauerlaw.net_000017405_NATIVE__lists.csv
0 rows

File structure

Notes: This is not a typical tabular dataset with personal identifiers. The file appears to be a structured list of categories and codes used in law enforcement or legal case documentation (e.g., race categories, vehicle types, offense codes, legal statutes). No actual PII fields (names, addresses, emails, etc.) are present in the first 50 rows. All columns contain categorical or coded data used for case classification, not personal identifying information. Therefore, no columns map to PII fields.

hallauerlaw.net__hallauerlaw.net_000017458_NATIVE__PTN_7577487384.csv
3 columns249 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit US phone numbers with area code
1phonehigh[1] header 'CALLED_NBR', values are 10-digit US phone numbers with area code
2phonehigh[2] header 'DIALED_DIGITS', values are 7-10 digit phone numbers (some missing area code)

Notes: Only phone number columns contain PII. All other columns are call metadata (direction, timestamps, duration, cell tower IDs) and empty fields.

hallauerlaw.net__hallauerlaw.net_000017460_NATIVE__PTN_7575614063.csv
3 columns197 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit numbers with area code in parentheses
1phonehigh[1] header 'CALLED_NBR', values are 10-digit numbers with area code in parentheses
2phonehigh[2] header 'DIALED_DIGITS', values are 10-digit numbers with area code in parentheses

Notes: Only phone numbers (CALLING_NBR, CALLED_NBR, DIALED_DIGITS) contain PII. All other columns are call metadata (direction, timestamps, durations, cell towers) or empty — these are NOT PII per exclusion rules.

hallauerlaw.net__hallauerlaw.net_000017462_NATIVE__PTN_7575614063.csv
3 columns197 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR' and values are valid US phone numbers in parentheses format
1phonehigh[1] header 'CALLED_NBR' and values are valid US phone numbers in parentheses format
2phonehigh[2] header 'DIALED_DIGITS' and values are valid US phone numbers in parentheses format

Notes: This is a call detail record (CDR) dataset from Hallauer Law's breach. Columns 0-2 contain phone numbers (caller, callee, and dialed digits). All other columns are internal tracking IDs, timestamps, duration, and cell tower data — no PII beyond the phone numbers. No names, emails, addresses, or DOB appear in this sample.

hallauerlaw.net__hallauerlaw.net_000017789_NATIVE__MSB_Audio_Files.csv
0 rows

File structure

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

Notes: The file appears to be a structured CSV with headers, but the data consists of surveillance/intercept records (audio/video logs) from a law enforcement operation. Column 4 ('Primary Suspected Interceptees Include (May Include Others)') contains lists of names in abbreviated formats (e.g., 'A. WILLIAMS', 'W. MOORE'), but these are not full PII fields in standardized formats. The format does not map cleanly to any single PII category (firstName, lastName, etc.) because the data is intentionally obfuscated for operational security. No valid email, phone, DOB, SSN, or other PII fields are present in the visible columns. Therefore, no PII columns can be mapped.

hallauerlaw.net__hallauerlaw.net_000017790_NATIVE__MSB_Audio_Files.csv
5 columns165 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphigh[0] internal identifier pattern '1D#'
3dobhigh[3] contains ISO date timestamps (e.g., 2012-05-09T00:00:00.000Z)
7fullNamehigh[7] contains comma-separated lists of alias-interceptees (e.g., 'S-47220, A. WILLIAMS')
8fullNamehigh[8] contains additional lists of alias-interceptees and others (e.g., 'S-47220, A. WILLIAMS, W. MOORE')
9fullNamehigh[9] contains more extensive lists of individuals involved (e.g., 'S-47220, A. WILLIAMS, J. STRINGER, W. MOORE and others')

Notes: 50 rows analyzed; columns 0 (ID), 3 (date), 7, 8, and 9 contain PII. Column 7 maps to fullName due to structured lists of alias-interceptees. Columns 8 and 9 also map to fullName as they extend the list of involved individuals. All other columns are skip (status, summary flags, notes, summarizer, file references).

hallauerlaw.net__hallauerlaw.net_000017791_NATIVE__MSB_Audio_Files.csv
0 rows

File structure

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

Notes: This file is not structured data containing PII. It is a log of audio/video interceptions with names appearing in the "Primary Suspected Interceptees Include" column. These names are not in a tabular format with consistent columns; they are free-text entries listing individuals involved in interceptions. Since the data lacks a consistent columnar structure and contains only names without other PII fields (email, phone, etc.), it does not meet the criteria for structured PII extraction. The names listed are part of investigative records and not in a format that can be mapped to PII columns. Therefore, no columns are mapped.

hallauerlaw.net__hallauerlaw.net_000017792_NATIVE__MSB_Jail_House_Calls.csv
0 rows

File structure

Notes: File is free-form text with no consistent delimiter structure. Contains embedded phone numbers (e.g., 2768730371, 276-873-0093) and identifiers (e.g., J. Arrington #1421147), but lacks columnar format. This qualifies as unstructured data requiring streaming extraction of emails/phones.

hallauerlaw.net__hallauerlaw.net_000017793_NATIVE__MSB_ELECTRONIC_DISC..csv
0 rows

File structure

Notes: free-form text with embedded names and case references, no consistent delimiter structure

hallauerlaw.net__hallauerlaw.net_1A_Table_of_Contents__Sheet1.csv
0 rows

File structure

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

Notes: The file is a list of evidence items and descriptions from a law enforcement case. It contains no structured data rows with personal information; each line is a narrative description of an exhibit (e.g., disks, letters, recordings). There are no columns to map to PII fields. The content is administrative/case management metadata, not personal records.

hallauerlaw.net__hallauerlaw.net_2013-241330-0001_1__PTN_7575614063.csv
3 columns197 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit US phone numbers in parentheses
1phonehigh[1] header 'CALLED_NBR', values are 10-digit US phone numbers in parentheses
2phonehigh[2] header 'DIALED_DIGITS', values are 10-digit US phone numbers in parentheses

Notes: Only columns 0, 1, and 2 contain PII (phone numbers). All other columns are internal tracking fields, timestamps, durations, or empty. The data represents call detail records (CDRs) from the Hallauer Law breach, containing cell tower routing information for surveillance.

hallauerlaw.net__hallauerlaw.net_2013-241330-0001_2__PTN_7575614063.csv
3 columns197 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR' and values are valid US phone numbers in (XXX) XXX-XXXX format
1phonehigh[1] header 'CALLED_NBR' and values are valid US phone numbers in (XXX) XXX-XXXX format
2phonehigh[2] header 'DIALED_DIGITS' and values are valid US phone numbers in (XXX) XXX-XXXX format

Notes: Only columns 0, 1, and 2 contain PII (phone numbers). All other columns are call metadata (direction, timestamps, duration, cell tower IDs) and are not personally identifiable. No emails, names, addresses, DOB, SSN, or other PII present in the sample.

hallauerlaw.net__hallauerlaw.net_2013-241330-0001__PTN_7575614063.csv
3 columns197 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR' and values are 10-digit US phone numbers with area code
1phonehigh[1] header 'CALLED_NBR' and values are 10-digit US phone numbers with area code
2phonehigh[2] header 'DIALED_DIGITS' and values are 10-digit US phone numbers with area code

Notes: Only columns 0, 1, and 2 contain PII (phone numbers). All other columns are call metadata, internal codes, durations, or empty fields and must be skipped per rules. No email, name, address, DOB, SSN, or other PII present in the sample.

hallauerlaw.net__hallauerlaw.net_2013-241330-0001_highlighted_1__PTN_7575614063.csv
3 columns197 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values match US phone format
1phonehigh[1] header 'CALLED_NBR', values match US phone format
2phonehigh[2] header 'DIALED_DIGITS', values match US phone format

Notes: Only columns 0,1,2 contain PII (phone numbers). All other columns are call metadata (direction, timestamps, duration, cell towers) or empty — these are NOT PII per exclusion rules. This is a call detail record (CDR) dataset from law firm surveillance logs.

hallauerlaw.net__hallauerlaw.net_2013-241330-0001_highlighted_2__PTN_7575614063.csv
3 columns197 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header CALLING_NBR, values are valid US phone numbers in (XXX) XXX-XXXX format
1phonehigh[1] header CALLED_NBR, values are valid US phone numbers in (XXX) XXX-XXXX format
2phonehigh[2] header DIALED_DIGITS, values are valid US phone numbers in (XXX) XXX-XXXX format

Notes: This is a call detail record (CDR) file from Hallauer Law's phone surveillance system. Only columns 0-2 contain PII (phone numbers). All other columns are internal tracking codes, timestamps, durations, and empty fields — none contain personal data.

hallauerlaw.net__hallauerlaw.net_2013-241330-0001_highlighted_3__PTN_7575614063.csv
3 columns197 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit US phone numbers in parentheses
1phonehigh[1] header 'CALLED_NBR', values are 10-digit US phone numbers in parentheses
2phonehigh[2] header 'DIALED_DIGITS', values are 10-digit US phone numbers in parentheses

Notes: Only columns 0, 1, and 2 contain PII (phone numbers). All other columns are internal call record metadata (direction, timestamps, durations, cell towers, network IDs) and are non-PII per exclusion rules. This is a standard call detail record (CDR) export from telecommunications surveillance.

hallauerlaw.net__hallauerlaw.net_2013-241330-0001_highlighted__PTN_7575614063.csv
3 columns197 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit numbers in parentheses with area code
1phonehigh[1] header 'CALLED_NBR', values are 10-digit numbers in parentheses with area code
2phonehigh[2] header 'DIALED_DIGITS', values are 10-digit numbers in parentheses with area code

Notes: This is a call detail record (CDR) dataset from Hallauer Law's phone surveillance logs. Only phone number fields contain PII; all other columns are internal tracking codes, timestamps, and empty fields.

hallauerlaw.net__hallauerlaw.net_2013-245350-0001_1__PTN_7577487384.csv
3 columns249 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit phone numbers with area code
1phonehigh[1] header 'CALLED_NBR', values are 10-digit phone numbers with area code
2phonehigh[2] header 'DIALED_DIGITS', values are 10-digit phone numbers (some missing area code)

Notes: This is a call detail record (CDR) dataset from a law firm breach. Columns 0-2 all represent phone numbers (caller, callee, and dialed digits). Columns 3-25 contain non-PII metadata (call direction, timestamps, duration, cell tower IDs, etc.) and are skipped per rules.

hallauerlaw.net__hallauerlaw.net_2013-245350-0001_2__PTN_7577487384.csv
3 columns249 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header CALLING_NBR, values are valid US phone numbers in (XXX) XXX-XXXX format
1phonehigh[1] header CALLED_NBR, values are valid US phone numbers in (XXX) XXX-XXXX format
2phonehigh[2] header DIALED_DIGITS, values are valid US phone numbers (with and without area code)

Notes: This is a call detail record (CDR) dataset from phone surveillance. Only columns 0-2 contain PII (phone numbers). All other columns are internal tracking codes, timestamps, durations, and empty fields — none contain personal data. The 'M_R_#' column appears to be call direction (Incoming/Outgoing), not a person identifier.

hallauerlaw.net__hallauerlaw.net_2013-245350-0001_Highlighted_1__PTN_7577487384.csv
3 columns249 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are valid US phone numbers in (XXX) XXX-XXXX format
1phonehigh[1] header 'CALLED_NBR', values are valid US phone numbers in (XXX) XXX-XXXX format
2phonehigh[2] header 'DIALED_DIGITS', values are phone numbers (some missing area code prefix)

Notes: This is a call detail record (CDR) file from phone surveillance. Columns 0-2 contain phone numbers (caller, callee, and dialed digits). Columns 3-25 contain call metadata (direction, timestamps, duration, cell tower IDs) and are non-PII per exclusion rules. No email addresses, names, or other PII appear in the sample.

hallauerlaw.net__hallauerlaw.net_2013-245350-0001_Highlighted_2__PTN_7577487384.csv
3 columns249 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit phone numbers with area code
1phonehigh[1] header 'CALLED_NBR', values are 10-digit phone numbers with area code
2phonehigh[2] header 'DIALED_DIGITS', values are 7-10 digit phone numbers

Notes: This is a call detail record (CDR) dataset from Hallauer Law breach. Columns 0-2 contain phone numbers (caller, callee, and dialed digits). Columns 3-25 contain non-PII metadata (direction, timestamps, duration, cell tower IDs, etc.) and are skipped per rules. No email, name, address, DOB, or SSN present in sample.

hallauerlaw.net__hallauerlaw.net_2013-245350-0001_Highlighted_3__PTN_7577487384.csv
3 columns249 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit phone numbers with area code
1phonehigh[1] header 'CALLED_NBR', values are 10-digit phone numbers with area code
2phonehigh[2] header 'DIALED_DIGITS', values are 7-10 digit phone numbers (some missing area code)

Notes: This is a phone call detail record (CDR) file from law firm Hallauer Law. Columns 0-2 contain phone numbers (caller, callee, dialed digits). Columns 3-25 contain call metadata (direction, timestamps, duration, cell tower IDs) which are not PII per the exclusion rules. No names, addresses, or other PII appear in the sample.

hallauerlaw.net__hallauerlaw.net_2013-245350-0001_Highlighted__PTN_7577487384.csv
3 columns249 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header CALLING_NBR, values are 10-digit US phone numbers with area code
1phonehigh[1] header CALLED_NBR, values are 10-digit US phone numbers with area code
2phonehigh[2] header DIALED_DIGITS, values are 7-10 digit phone numbers (some missing area code)

Notes: Only columns 0-2 contain phone numbers; all other columns are call metadata (direction, timestamps, duration, cell tower IDs) or empty. This is a call detail record (CDR) export from phone surveillance.

hallauerlaw.net__hallauerlaw.net_2013-245350-0001__PTN_7577487384.csv
3 columns249 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit US phone numbers with area code
1phonehigh[1] header 'CALLED_NBR', values are 10-digit US phone numbers with area code
2phonehigh[2] header 'DIALED_DIGITS', values are phone numbers (some missing area code)

Notes: This is a phone call record dataset (CDR) from Hallauer Law breach. Columns 0-2 contain calling/calling/dialed numbers. Columns 3-25 are non-PII operational fields (direction, timestamps, durations, cell tower IDs). No names, emails, addresses, or other PII are present in the first 50 rows.

hallauerlaw.net__hallauerlaw.net_2016-046662-1562044__3474249779-1.csv
3 columns17,911 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit numbers
1phonehigh[1] header 'CALLED_NBR', values are 10-digit numbers
2phonehigh[2] header 'DIALED_DIGITS', values are 10-digit numbers

Notes: CSV file with 50 rows detailing phone call records. Only columns 0, 1, and 2 contain PII (phone numbers). Other columns represent timestamps, call types, and durations — no PII.

hallauerlaw.net__hallauerlaw.net_2016-164997-2266038__9176539249-1.csv
9 columns7,449 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighHeader is CALLING_NBR, which is an internal identifier
1phonehighHeader is CALLED_NBR, values are 10-digit phone numbers
2skiphighHeader is DIALED_DIGITS, which appears to be an internal routing field
3skiphighHeader is MOBILE ROLE, which is an internal classification
4skiphighHeader is START_DATE, which is a timestamp
5skiphighHeader is END_DATE, which is a timestamp
6skiphighHeader is DURATION (SEC), which is a call duration metric
7skiphighHeader is Call Type, which is an internal classification
8skiphighHeader is NEID, which is an internal network identifier

Notes: This is a call detail record (CDR) file containing phone call and text message metadata. Only the CALLED_NBR column contains PII (phone numbers). All other columns are internal system identifiers, timestamps, or call metrics.

hallauerlaw.net__hallauerlaw.net_2016-164997-2266164__3474249779-1.csv
3 columns18,498 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values are 10-digit numbers
1phonehigh[1] header 'CALLED_NBR', values are 10-digit numbers
2phonehigh[2] header 'DIALED_DIGITS', values are 10-digit numbers

Notes: CSV file containing call detail records (CDRs) with caller and callee phone numbers. Only phone numbers are PII in this dataset; other fields are timestamps, call durations, and call types which are not personally identifiable.

hallauerlaw.net__hallauerlaw.net_281D-RH-4436148_Table_of_Contents_02022016__Sheet1.csv
0 rows

File structure

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

Notes: The provided data is a list of document descriptions and references from a law enforcement case file. It contains no structured personal identifiable information (PII) fields such as names, addresses, phone numbers, etc. All entries are administrative or descriptive notes about evidence, interviews, subpoenas, and case updates. There are no columns mapping to PII fields.

hallauerlaw.net__hallauerlaw.net_281D-RH-4436148_Table_of_Contents_11032015_1__Sheet1.csv
0 rows

File structure

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

Notes: File contains structured case metadata with no PII fields. All entries are case identifiers, administrative notes, and document titles referencing individuals by aliases or case numbers without exposing personal identifiers. No columns contain email, phone, address, or other PII per the defined field types.

hallauerlaw.net__hallauerlaw.net_281D-RH-4436148_Table_of_Contents_11032015__Sheet1.csv
0 rows

File structure

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

Notes: This is not structured PII data - it's a list of document descriptions from a law enforcement case file. The entries are narrative descriptions of evidence and case documents (e.g., '(U) Arrest of Javon Arrington', '(U) Interview of Nicholas Johnson'). There are no actual personal identifiers (names, addresses, etc.) exposed in these rows - only references to individuals within the context of case documentation. No columns map to PII fields.

hallauerlaw.net__hallauerlaw.net_281D-RH-4436148_Table_of_Contents_1__Sheet1.csv
0 rows

File structure

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

Notes: The file is a structured CSV containing administrative and case documentation headers with no actual PII data in the first 50 rows. All entries are case identifiers, document titles, and administrative notes (e.g., '(U) Arrest of Javon Arrington', '(U) Interview of Nicholas Johnson'). No columns contain personal data such as names, addresses, emails, or phone numbers in the visible rows. Therefore, no PII columns can be mapped.

hallauerlaw.net__hallauerlaw.net_281D-RH-4436148_Table_of_Contents__Sheet1.csv
0 rows

File structure

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

Notes: The file is a structured CSV, but all visible columns contain administrative case identifiers, file references, and document titles. No personal identifiers (PII) appear in the first 50 rows. Column names and values indicate internal case tracking numbers, document codes, and administrative notes rather than sensitive personal data. No emails, phone numbers, names, addresses, DOBs, or other PII fields are present in the provided sample.

hallauerlaw.net__hallauerlaw.net_302_Subfile_TOC__as_of_7-27-17___Sheet1.csv
0 rows

File structure

Notes: The file is a free-form text list of case file descriptions and interview summaries with no consistent delimiter or column structure. While it contains names and case details, the format is unstructured prose rather than tabular data.

hallauerlaw.net__hallauerlaw.net_302_Subfile_Table_of_Contents__Sheet1.csv
0 rows

File structure

Notes: This is a free-form text file listing document descriptions from a law enforcement case file. There is no consistent delimiter or columnar structure. While the descriptions contain names (e.g., WILLIAMS, WILLANDT, GERALD, JENNINGS), these appear as part of prose rather than structured data fields. Therefore, this file should be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_302_Subfile_Table_of_Contents__as_of_10.14.16___Sheet1.csv
0 rows

File structure

Notes: The file is a free-form text list of case documents and investigation records, not structured tabular data. Each line describes a different document or record (e.g., interviews, summaries, photos, reports), but there are no consistent columns or delimiters. While some names appear (e.g., GERALD, WILLIAMS, JENNINGS), they are embedded within descriptive text rather than in a structured format. Therefore, this is unstructured data requiring a different processing pipeline.

hallauerlaw.net__hallauerlaw.net_302_Subfile_Table_of_Contents__as_of_11.3.15___Sheet1.csv
0 rows

File structure

Notes: This is a free-form text file listing investigative records and case descriptions. There is no consistent delimiter or columnar structure. While names like GERALD, WILLIAMS, BURKETT, JENNINGS, BALL, BROWN, BAILEY, GUNN, ARRINGTON appear, they are embedded in prose and not in a tabular format. The file meets unstructured criteria: no consistent delimiter, varying line shapes, and contains names/emails/phones inline.

hallauerlaw.net__hallauerlaw.net_302_Subfile_Table_of_Contents__as_of_2.2.16___Sheet1.csv
0 rows

File structure

Notes: This is a free-form text file listing descriptions of documents and evidence from a law enforcement case file. There is no consistent delimiter or column structure; each line describes a different document or record. While the descriptions contain names (e.g., WILLIAMS, BURKETT, JENNINGS) and case details, there are no structured PII fields like email, phone, or address in machine-readable format. The content appears to be narrative descriptions rather than tabular data.

hallauerlaw.net__hallauerlaw.net_302_Subfile_Table_of_Contents__as_of_3.31.16___Sheet1.csv
0 rows

File structure

Notes: This is a free-form text file listing descriptions of investigative documents and case files. It lacks consistent column structure and contains only narrative descriptions rather than structured data records. While it contains names (e.g., WILLIAMS, BURKETT, JENNINGS), these appear in prose descriptions rather than as columnar data, matching the unstructured format criteria.

hallauerlaw.net__hallauerlaw.net_302_Subfile_Table_of_Contents__as_of_4.3.17___Sheet1.csv
0 rows

File structure

Notes: The file is a list of case descriptions and interview summaries with no consistent delimiter or column structure. Each line is a free-form description of evidence or activities, containing embedded names (e.g., GERALD, WILLIAMS, JENNINGS) but lacks any tabular format or repeated fields. Per critical rules, unstructured files with no shared delimiter structure must return an empty columns object.

hallauerlaw.net__hallauerlaw.net_302_Subfile_Table_of_Contents__as_of_7.11.16___Sheet1.csv
0 rows

File structure

Notes: The file is a list of document descriptions/summaries from a law enforcement case file. It contains no structured columns or PII fields. All entries are narrative descriptions of investigations, interviews, and evidence. No columnar data exists to map.

hallauerlaw.net__hallauerlaw.net_302_Subfile_Table_of_Contents__as_of_7.27.17___Sheet1.csv
0 rows

File structure

Notes: The file is a free-form list of case file descriptions and summaries with no consistent delimiter or structured columns. While it contains names (e.g., WILLIAMS, BURKETT, JENNINGS), these appear within prose descriptions rather than as tabular data. Per rules, unstructured files with no row structure return an empty columns object.

hallauerlaw.net__hallauerlaw.net_302_Subfile_Table_of_Contents__as_of_8.9.16___Sheet1.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent columnar structure. It appears to be a list of document descriptions from an investigative file index, not a delimited dataset containing PII. There are no repeated patterns of columns or delimiters, and while names like JONES, WILLIAMS, GERALD appear, they are embedded in prose descriptions rather than structured fields.

hallauerlaw.net__hallauerlaw.net_757-232-7186_CDRs_1__Combined_Detail_LE.csv
8 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_757-232-7186_CDRs__Combined_Detail_LE.csv
8 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_757-232-7186_a_1__Combined_Detail_LE.csv
8 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_757-232-7186_a__Combined_Detail_LE.csv
8 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_757-232-7186_b_1__Combined_Detail_LE.csv
105 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_757-232-7186_b__Combined_Detail_LE.csv
105 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_824601-SUB__LEGEND.csv
0 rows

File structure

Notes: This is a metadata/descriptor sheet for a Western Union transaction log, not actual transactional data. The file contains column labels and ID type documentation rather than personal records. No PII fields to map.

hallauerlaw.net__hallauerlaw.net_824601-SUB__Received_transctions.csv
17 columns35 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'SName', values are full names like 'GEORGE ARMSTRONG', 'BRANDON HAYNES' — sender full name
4skiphigh[4] header 'SPhone' — sender phone number field
8skiphigh[8] header 'SDOB' — sender date of birth
14address1high[14] header 'SAddress' — sender street address
15cityhigh[15] header 'SCity' — sender city
16statehigh[16] header 'SState' — sender state
17ziphigh[17] header 'SZip', values like '11412', '23325' — sender zip code
18countryhigh[18] header 'SCountry', values 'US' — sender country
21fullNamehigh[21] header 'PName', values are full names like 'ADRIENNE WILLIAMS' — payee/recipient full name
23phonehigh[23] header 'PPhone', values like '17032708031', '7579448051' — payee phone number
27dobhigh[27] header 'PDOB', values like '1960.07.31', '1973.05.21' — payee date of birth
31address1high[31] header 'PAddress', values like '300 S WHITING ST', '3414 GRACIE RD' — payee street address
32cityhigh[32] header 'PCity', values like 'ALEXANDRIA', 'CHESAPEAKE' — payee city
33statehigh[33] header 'PState', values 'VA' — payee state
34ziphigh[34] header 'PZip', values like '22304', '23325' — payee zip code
35countryhigh[35] header 'PCountry', values 'US' — payee country
53skiphigh[53] header 'SEMail' — sender email address

Notes: Wire transfer / money order records (likely Western Union CDRs) from Hallauer Law case files. Each row has two parties: a Sender (S-prefix columns) and a Payee/Recipient (P-prefix columns). Both parties have PII mapped separately where the schema permits (fullName mapped twice for cols 2 and 21, phone for 4 and 23, dob for 8 and 27, address/city/state/zip/country for both sender and payee sides). Agent name/address fields (cols 38-51) appear to be retail store locations (Giant Food, Food Lion, etc.) not personal PII — skipped. SId/PId columns appear to be government ID numbers and types; no matching PII field type available — skipped. SCredit Card (col 12) and SDebtor Account (col 52) are financial account fields with no matching PII type — skipped.

hallauerlaw.net__hallauerlaw.net_824601-SUB__Sent_transcations.csv
17 columns43 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'SName', values are full names in all-caps (e.g. 'ADRIENNE WILLIAMS') — sender full name
4phonehigh[4] header 'SPhone', values are 10-digit phone numbers (e.g. '7574047229') — sender phone
8dobhigh[8] header 'SDOB', values match YYYY.MM.DD date pattern (e.g. '1973.05.21') — sender date of birth
14address1high[14] header 'SAddress', values are street addresses (e.g. '344 GRACIE RD') — sender address
15cityhigh[15] header 'SCity', values are city names (e.g. 'CHESAPEAKE') — sender city
16statehigh[16] header 'SState', values are US state abbreviations (e.g. 'VA') — sender state
17ziphigh[17] header 'SZip', values are 5-digit ZIP codes (e.g. '23325') — sender ZIP
18countryhigh[18] header 'SCountry', values are country codes (e.g. 'US') — sender country
21fullNamehigh[21] header 'PName', values are full names (e.g. 'BRANDON HAYNES') — payee/recipient full name
23skiphigh[23] header 'PPhone' — payee phone number
27skiphigh[27] header 'PDOB' — payee date of birth, mirrors SDOB pattern
31address1high[31] header 'PAddress' — payee street address, mirrors SAddress pattern
32cityhigh[32] header 'PCity' — payee city, mirrors SCity pattern
33statehigh[33] header 'PState' — payee state, mirrors SState pattern
34ziphigh[34] header 'PZip' — payee ZIP code, mirrors SZip pattern
35countryhigh[35] header 'PCountry', values are country codes (e.g. 'US', 'JM') — payee country
53skipmedium[53] header 'SEMail' — sender email address column; values appear blank/whitespace in sample but column is clearly an email field by name

Notes: Money transfer records (likely Western Union or similar wire transfer CDRs) with sender (S-prefix) and payee/recipient (P-prefix) PII pairs. Columns 38-51 are agent/retailer business location data (skip). Columns 7/9/10/11/12/13 appear to be ID type/number fields with no sample values — skipped due to insufficient data. Column 52 (SDebtor Account) contains a masked card number — skipped as financial instrument, not standard PII field. Column 54 (SPreferred Card) contains card reference codes — skipped.

hallauerlaw.net__hallauerlaw.net_Aaron_Gerald_tolls_757-202-6239_2-16-12_to_5-18-12__PTN_7572026239.csv
3 columns3,813 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0phonehigh[0] header 'CALLING_NBR', values match 10-digit US phone format with optional parentheses and hyphens
1phonehigh[1] header 'CALLED_NBR', values match 10-digit US phone format with optional parentheses and hyphens
2phonehigh[2] header 'DIALED_DIGITS', values match 10-digit US phone format with optional parentheses and hyphens

Notes: CSV file with 50 rows of phone call records. Only columns 0, 1, and 2 contain PII (phone numbers). Other columns contain call metadata (dates, durations, direction codes) and are skipped.

hallauerlaw.net__hallauerlaw.net_Blank_CIW_A00656188__CONTENTS.csv
0 rows

File structure

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

Notes: This file is a structured CSV but contains only a property inventory worksheet template with no actual personal data. All columns appear to be metadata or placeholders (Tenant, Date of Loss, Policy No, etc.) and do not contain any PII fields. The rows shown are headers and empty data rows for inventory items.

hallauerlaw.net__hallauerlaw.net_Blank_CIW_A00656188__CONTENTS_-_Page_2.csv
0 rows

File structure

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

Notes: This is a structured inventory worksheet with no PII fields present. All columns are headers or placeholders for inventory data (e.g., item descriptions, quantities, costs). No personal information such as names, addresses, or other PII is present in the first 50 rows.

hallauerlaw.net__hallauerlaw.net_Blank_CIW_A00656188__CONTENTS_-_Page_3.csv
0 rows

File structure

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

Notes: This file is a structured inventory worksheet with no PII fields. All columns represent property inventory data (item descriptions, quantities, pricing) and administrative metadata. No email addresses, phone numbers, names, or other personally identifiable information are present in the first 50 rows.

hallauerlaw.net__hallauerlaw.net_Boone_Accurint.csv
6 columns2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Full Name', values include 'BOONE' and other name fragments consistent with full name data
1gendermedium[1] header 'Gender'; values appear misaligned but column is designated for gender data
2ssnhigh[2] header 'SSN'; value 'Male' is misalignment artifact, column is designated for Social Security Number
3dobhigh[3] header 'DOB/Age'; column designated for date of birth with age
5address1high[5] header 'Address'; contains physical address data for subjects
6skiphigh[6] header 'Phone Information'; contains phone/CDR data for subjects

Notes: Data is severely misaligned — values appear shifted across columns, likely due to malformed extraction from a structured legal report (FBI/law enforcement records). Column headers are reliable indicators of field types. LexID (col 10) is a skip as an internal identifier. DOD/Age at Death (col 4), Property (col 7), Motor Vehicle (col 8), and People at Work (col 9) have no matching PII field types.

hallauerlaw.net__hallauerlaw.net_Boone_Accurint_1.csv
6 columns2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Full Name', values contain surnames like 'BOONE' (misaligned but header is clear)
1genderhigh[1] header 'Gender', values show shifted name data due to misalignment but header is unambiguous
2ssnhigh[2] header 'SSN', value '223-11-0742' matches SSN pattern (column shift caused 'Male' to appear here)
3dobhigh[3] header 'DOB/Age', values reference years like '1972 (42)' consistent with DOB/age
5address1high[5] header 'Address', street address data visible in shifted values (e.g., '2690 ELMHURST LN', 'PORTSMOUTH')
6skiphigh[6] header 'Phone Information', clear phone data column

Notes: Columns are severely misaligned in the sample — row data wraps across multiple column slots. Header names are the primary mapping signal. LexID (col 10) is a Lexis-Nexis internal identifier, skipped. DOD/Age at Death (col 4), Property (col 7), Motor Vehicle (col 8), and People at Work (col 9) are not standard PII fields. This is a law enforcement/legal case file with highly sensitive subject data.

hallauerlaw.net__hallauerlaw.net_Brown_Accurint.csv
4 columns2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Full Name', values appear to be last names repeated
2ssnhigh[2] header 'SSN', values match typical SSN format
3dobhigh[3] header 'DOB/Age', values match date format (YYYY-MM-DD)
5address1high[5] header 'Address', expected to contain address information

Notes: 11 total columns, 4 contain PII. Column 1 appears to be corrupted gender data. Column 6 appears to contain phone information but is obfuscated. Columns 7, 8, 9, and 10 contain non-PII data.

hallauerlaw.net__hallauerlaw.net_Brown_Accurint_1.csv
4 columns2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Full Name', values are last names repeated
3dobhigh[3] header 'DOB/Age', value '209-60-2036' matches SSN format but context suggests DOB
5address1high[5] header 'Address'
6phonemedium[6] header 'Phone Information', values appear to be partial addresses but context suggests phone records may be embedded

Notes: 11 total columns. Columns 1 (Gender) contains corrupted data, column 2 (SSN) mislabeled and contains gender values, column 4 (DOD/Age at Death) contains death dates, column 7-10 contain non-PII case notes. LexID is an internal case ID and skipped.

hallauerlaw.net__hallauerlaw.net_Cooper_Accurint.csv
5 columns4 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Full Name', values contain names like 'COOPER'
1genderhigh[1] header 'Gender', values appear to be gender identifiers (though obfuscated)
3dobmedium[3] header 'DOB/Age', values match format of SSN or date components (227-57-1657)
5address1low[5] header 'Address', values appear to be numeric codes but could represent address identifiers in this dataset
6address1medium[6] header 'Phone Information', values contain street addresses mixed with phone data (e.g., '1305 CLIFTON ST NW APT 3')

Notes: 12 columns total, 5 contain PII. Column 2 (SSN) contains 'None' or non-SSN values. Column 7 (Property) and others appear to contain location data but are not clearly PII. The dataset appears to contain obfuscated or encoded values requiring further decoding for full PII identification.

hallauerlaw.net__hallauerlaw.net_Cooper_Accurint_1.csv
5 columns4 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Full Name', values contain full names like 'COOPER'
1gendermedium[1] header 'Gender', values appear to be gender indicators (though some entries are garbled)
3dobmedium[3] header 'DOB/Age', values like '227-57-1657' match SSN-like patterns but given context as DOB field
5address1low[5] header 'Address', values appear to be numeric IDs or placeholders rather than true addresses
6address1low[6] header 'Phone Information', values contain address-like fragments mixed with phone data; mapping as address due to structure

Notes: 12 columns total, 5 contain PII. Columns 2 (SSN) and 4 (DOD/Age at Death) contain non-PII or placeholder values. Column 7 appears to be location data but not structured PII. LexID is an internal identifier and skipped.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Arr_Labels.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. Lines contain legal case notes and arrest records with embedded names and addresses, but lack a fixed column layout. Sample shows entries like " Smith, Pierre D (B/M 31)" and "1333 Poindexter St Chespeake" mixed in prose. This qualifies as unstructured data requiring streaming extraction for any embedded PII.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Case_Report_Data.csv
1 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Case_Summary.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or column structure; lines contain case summary fragments and fields like 'Offense:', 'Date:', 'Items Stolen:', etc. — not a delimited CSV/TSV. Contains embedded values but lacks tabular format.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Def__1_Detention_Sheet.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. The sample rows contain instructional text and mixed data fields, not a tabular format. While some lines contain fragments that could resemble PII (e.g., '5/2/82' which might be a date), there is no reliable column mapping possible due to the unstructured nature of the data. This matches the description of legal case files with mixed content.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Def__1_FF.csv
0 rows

File structure

Notes: This is an unstructured document with free-form text. The sample rows show case report titles, instructions, and case notes rather than structured tabular data with consistent columns. There are no consistent delimiters or repeating patterns that would indicate a CSV or other structured format. The content appears to be legal case documentation with prose entries, not columnar PII data.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Def__1_Magistrate.csv
0 rows

File structure

Notes: This file is a free-form text document containing case file notes and legal forms. There is no consistent column structure or delimiter across rows; each line contains different types of unstructured legal and investigative text. While some lines contain what appear to be phone numbers (e.g., '664-7032', '230-25-9788'), the lack of a consistent row structure means this should be treated as unstructured text for processing.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Def__2_Detention_Sheet.csv
0 rows

File structure

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

Notes: The provided rows appear to be free-form instructional text and field labels rather than structured data records. There is no consistent row structure or delimiter usage across lines, and the content is primarily composed of form-filling instructions and placeholder labels (e.g., "NAME", "Last Name", "First Name"). No actual PII values are present in the sample rows. Therefore, this is classified as unstructured text with no mappable columns.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Def__2_FF.csv
0 rows

File structure

Notes: This is not a structured dataset; it's free-form text with legal case notes and headers. Columns appear to be placeholders or metadata for forms/reports rather than actual data records. No consistent delimiter or row structure exists across the sample rows. Values are descriptive text and codes, not personal data in columnar format.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Def__2_Magistrate.csv
0 rows

File structure

Notes: This is free-form text with no consistent column structure. The sample lines show narrative entries like legal requests, case notes, and form fields with blank or placeholder values. Though some lines contain fragments that resemble phone numbers ('664-4196', '664-7032'), the lack of a consistent delimiter or repeating column pattern across rows means this must be processed as unstructured text. The breach context (law firm case files) confirms these are narrative documents rather than tabular data.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Def__3_Detention_Sheet.csv
0 rows

File structure

Notes: The provided data is free-form text/prose with no consistent columnar structure. It appears to be a form template or instructions for law enforcement booking procedures, not structured records with PII. Therefore, no column mapping is possible.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Def__3_FF.csv
0 rows

File structure

Notes: This is not a structured data file. The content appears to be free-form legal case notes or report headers from the Norfolk Police Department, including phrases like "FIRST TIME FELONY/INITIAL HEARING REPORT", "Continuance", and "Nolle Prosse". There are no consistent delimiters or repeating columnar patterns across rows. While there are some identifiers like "BE Pugh" and case types like "Robbery", the data is not in a tabular format suitable for columnar mapping. This should be processed as unstructured text for any embedded PII extraction.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Def__3_Magistrate.csv
0 rows

File structure

Notes: The provided rows appear to be free-form legal document text with no consistent columnar structure. Values like "664-4196", "664-7032" resemble phone numbers, but they appear embedded in prose rather than in a delimited column structure. All rows have wildly different content and length, failing the structured format criteria. This qualifies as unstructured text requiring streaming extraction for any embedded PII.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Grand_Jury.csv
5 columns7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] values contain full names like ' Smith, Pierre D' and 'BE Pugh'
5genderhigh[5] values are single letters 'B' (likely Black), map to gender as demographic identifier
6genderhigh[6] values are 'SEX:', but actual data is '0' or 'M' - gender marker
7genderhigh[7] values are 'M' - explicitly male gender marker
9dobhigh[9] values match date format (MM/DD/YY), header indicates DOB

Notes: This is a legal case file format with mixed structured/unstructured data. Columns 1, 5, 6, 7, and 9 contain PII. Column 1 contains full names, columns 5, 6, and 7 contain gender indicators, and column 9 contains dates of birth. Other columns appear to be case metadata, headers, or empty fields and do not contain PII.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Inv_Labels.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; lines contain mixed case headers and values with inconsistent formats and no repeating column pattern

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__JCF.csv
1 rows

File structure

Notes: This is a free-form document with no consistent column structure. The lines contain prose and form labels rather than structured data. Examples include 'JUVENILE INFORMATION', ' Smith, Pierre D', 'LAST NAME FIRST MIDDLE', and '924 Trice Terr B'. While some lines resemble addresses or names, the lack of consistent delimiter and varying line structures indicates this is unstructured text.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__JFV.csv
0 rows

File structure

Notes: The file is a free-form document containing headerless legal case notes, investigation forms, and unstructured text. No consistent column structure or delimiter exists across the rows. The sample lines show unstructured legal headers and narrative text, not tabular data.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__JPC.csv
0 rows

File structure

Notes: This file is free-form legal documentation with no consistent delimiter structure. Sample lines contain narrative text, not tabular data. Visible values include names, addresses, DOB, gender, and phone numbers, but they appear inline in prose rather than as columnar data.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__PD881_P1.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. Each line contains different fields and values, and there is no shared delimiter across lines. The sample shows unstructured data with embedded PII such as names, addresses, phone numbers, and dates. This meets the criteria for unstructured opt-out processing.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__PD881_P2.csv
0 rows

File structure

Notes: The file appears to be free-form text containing case report headers and evidence descriptions rather than structured tabular data with consistent columns. There is no repeating delimiter pattern across rows, and the content varies widely from 'Autopsy' to 'Fingerprints' to 'Evidence Held'. This is typical of document scans or case file headers, not a delimited dataset. No PII columns can be mapped because there is no column structure.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__PD881_P2A.csv
0 rows

File structure

Notes: This is an unstructured document with free-form text. The sample rows show legal case report headers and notes rather than tabular data. No consistent column structure exists; values appear as prose descriptions (e.g., 'Name:', 'Address:', 'DOB:', 'Phone:'). Since there is no consistent delimiter and the rows have wildly different content, this should be processed as unstructured text for embedded PII extraction.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__PD881_P3.csv
1 rows

File structure

Notes: This is unstructured legal case file data with free-form text entries. Columns are not consistently defined across rows — entries contain mixed legal narrative, property descriptions, and case notes rather than tabular PII fields. No consistent delimiter or column structure exists across the first 50 rows, and values appear to be free-text legal documentation rather than parsed personal data. While this type of data may contain embedded PII in prose, it requires unstructured processing.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__PD881_P4.csv
0 rows

File structure

Notes: This file appears to be a free-form document with no consistent columnar structure. The sample rows show unstructured text lines such as case report headers and page numbers, with no repeated delimiter patterns or identifiable column positions. Though the breach context mentions sensitive PII, the provided rows contain only header-like text and empty fields with no embedded emails or phone numbers visible in this sample. Therefore, it is classified as unstructured text requiring a streaming extractor for any potential PII not visible in this sample.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Start_Page.csv
1 rows

File structure

Notes: This is a free-form text file (not a structured CSV/TSV) with no consistent delimiter or column structure. The file appears to be a form or questionnaire with mixed prompts and sample values on the same line. It contains PII fragments like names and phone numbers embedded in prose, but lacks tabular structure.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__Subpoena.csv
0 rows

File structure

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

Notes: This file appears to be a template or form with placeholder text and no actual PII data in the first 50 rows. The columns contain legal form labels (e.g., 'REQUEST FOR WITNESS SUBPOENA', 'CASE NO.') and placeholder values like '****SELECT COURT FROM DROP DOWN LIST****' and 'Unknown'. There are no identifiable PII values in the sample rows. All columns are either structural form elements or empty. No PII fields can be mapped based on header names or sample values.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2_1__lists.csv
0 rows

File structure

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

Notes: This file appears to be structured but contains only categorical/coding data (race, sex, vehicle types, offense codes, etc.). No columns map to PII fields. All columns represent internal classification codes, vehicle manufacturers, legal statute references, and offense lists — none contain names, addresses, emails, phone numbers, DOB, SSN, or passwords. The data is purely administrative/coding in nature.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Arr_Labels.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent columnar structure. The sample lines contain legal case notes and descriptions rather than tabular data. Values like ' Smith, Pierre D (B/M 31)' and '1333 Poindexter St Chespeake' suggest embedded PII, but there is no repeating delimiter pattern across lines to define columns. This meets unstructured criteria: no consistent delimiter, variable line shapes, and visible PII in prose.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Case_Report_Data.csv
1 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Case_Summary.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent column delimiter. The sample shows narrative case summaries and fields like 'Offense:', 'Date:', 'Victim(s):', etc., not tabular data. Though it contains sensitive case information, it lacks a consistent structure for column mapping.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Def__1_Detention_Sheet.csv
0 rows

File structure

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

Notes: This file appears to be a template or instructions document rather than actual data records. The columns contain placeholder text like "• Fill in all known information" and field labels (e.g., "Last Name", "First Name", "DOB"), but no actual PII values are present in the first 50 rows. Per instructions, files that are READMEs, notes, or description documents with no importable structured data should return an empty columns object.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Def__1_FF.csv
0 rows

File structure

Notes: The provided rows are free-form text with no consistent column structure or delimiter. Each line contains different content shapes and appears to be narrative or descriptive entries from legal case files. There are no identifiable PII columns to map.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Def__1_Magistrate.csv
0 rows

File structure

Notes: This is unstructured text with no consistent columnar format. The data appears to be a series of legal case notes and investigative records with varying fields and content across rows. While some lines contain potential PII (like phone numbers and names), the lack of a consistent delimiter or column structure means this should be processed as unstructured text with embedded PII extraction.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Def__2_Detention_Sheet.csv
0 rows

File structure

Notes: The file is unstructured text with no consistent column delimiters or header row. The sample shows free-form notes and instructions rather than tabular data. While there are some embedded hints like 'Last Name', 'First Name', 'DOB', these appear within prose instructions rather than as structured fields. This matches the unstructured opt-out criteria: no consistent delimiter, variable line shapes, and contains instructional text rather than importable records.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Def__2_FF.csv
0 rows

File structure

Notes: The file is unstructured text. The sample shows free-form legal case notes, court instructions, and procedural text rather than tabular data. No consistent delimiter or column structure exists across rows. Values include court case statuses, instructions, and codes rather than personal PII.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Def__2_Magistrate.csv
0 rows

File structure

Notes: This is free-form text with no consistent columnar structure. The sample shows legal document headers and case notes rather than tabular data. While there are scattered values that look like phone numbers (e.g., '664-4196', '664-7032'), the file lacks consistent delimiters and row structures required for column mapping. This matches the unstructured opt-out conditions: no shared delimiter, wildly varying line shapes, and embedded phone numbers visible.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Def__3_Detention_Sheet.csv
0 rows

File structure

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

Notes: The provided sample rows are not structured data; they appear to be a mixture of form instructions, placeholder text, and incomplete fields. There are no consistent column headers or repeated patterns across rows that would allow identification of PII fields. The content resembles form templates or guidelines rather than actual records with personal data. Therefore, no columns can be mapped to PII fields.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Def__3_FF.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or structured columns. The file appears to contain legal case notes and reports from the Norfolk Police Department, with unstructured entries describing legal actions, commands, dates, and instructions. There are no identifiable PII columns in a structured format, but the unstructured content may contain embedded PII that requires separate processing.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Def__3_Magistrate.csv
0 rows

File structure

Notes: This is free-form text with no consistent columnar structure. The lines contain prose, court headers, and fragments (e.g., 'REQUEST FOR MAGISTRATE’S WARRANT', 'Norfolk Police Department', '664-7032'). Though some lines contain phone-like strings (664-7032) and fragments that resemble PII fields ('DOB:', 'Phone #:'), the file lacks a fixed delimiter or repeated header/column pattern across rows. This matches the unstructured opt-out criteria: no consistent delimiter, variable line shapes, and embedded PII-like fragments. Therefore, treat as unstructured text for streaming extraction of emails/phones.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Grand_Jury.csv
4 columns7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] contains full names like ' Smith, Pierre D', structured as 'Last, First M'
5genderhigh[5] values are single letters 'B' likely for 'Black' but in law enforcement context may map to gender (M/F), though ambiguous. Given the adjacent 'SEX' header at [6], this is likely race; however no race PII field exists, so we skip. Re-evaluating: In law enforcement reports, columns often map as: [1] fullName, [5] race (B = Black), [6] sex (M/F), [9] dob. Since race isn't a PII field we have, and sex/gender is at [6], we must map [6] as gender. Therefore [5] is non-PII and should be skipped. But the instructions say NEVER skip a column that clearly contains searchable PII — race isn't searchable PII. So [5] is skip. However, re-examining instructions: we only have fields for email, phone, dob, firstName, middleName, lastName, fullName, address1, address2, city, state, zip, ssn, password, username, country, gender, suffix, facebookId. Race isn't in this list, so it must be skipped. The sample shows only 'B' which isn't a gender value; gender values are typically M/F. Therefore map [6] to gender, skip [5]. Final mapping: [1] fullName, [6] gender, [9] dob.
6genderhigh[6] header 'SEX:', values 'M' clearly indicate gender
9dobhigh[9] header 'DOB:', values '5/2/82' match date format MM/DD/YY

Notes: This is a structured CSV with 21 columns; only 3 contain PII: fullName (column 1), gender (column 6), and dob (column 9). All other columns are headers or empty, or contain non-PII data like race codes, case identifiers, or labels. The data appears to be FBI investigative reports with defendant/witness information.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Inv_Labels.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; lines vary in content and length, containing narrative case notes rather than tabular data. Visible fields like 'VIC:' contain names but lack structured columns.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__JCF.csv
1 rows

File structure

Notes: This is a free-form document with no consistent column structure. The sample shows lines with mixed text, addresses, and potentially PII but lacks a repeating delimiter pattern. Per rules, unstructured files with embedded PII return empty columns.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__JFV.csv
0 rows

File structure

Notes: This is free-form text with no consistent column structure. The sample rows contain prose, headers, and narrative text typical of a document or report, not tabular data. While the data may contain embedded PII, the format lacks a consistent delimiter or column structure, so it must be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__JPC.csv
0 rows

File structure

Notes: This is free-form legal documentation with no consistent columnar structure. Sample lines show narrative text, headings, and embedded personal data (e.g., 'Smith, Pierre D', '924 Trice Terr B Norfolk, VA 23502', '5/2/82', 'B', 'M', '757 561-4063'). Because there is no repeatable delimiter or fixed column layout, this file must be processed as unstructured text for PII extraction.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__PD881_P1.csv
0 rows

File structure

Notes: The sample shows free-form legal case report text with no consistent column structure. Lines contain unstructured narrative entries like 'SOURCE: ', 'Report Submitted By:', 'Phone Number:', and case details. While some lines contain potential PII fragments (names, phone numbers, addresses), there is no repeating columnar pattern across rows — each line appears to be a free-text entry or label. This matches the unstructured opt-out criteria: no consistent delimiter, variable line shapes, and visible PII in prose format. The breach context (law firm case files) confirms these are narrative reports rather than structured tabular data.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__PD881_P2.csv
0 rows

File structure

Notes: This is a free-form text file containing legal case report headers and evidence descriptions. The lines show unstructured text with no consistent delimiter or column structure. No identifiable PII fields can be mapped from headers as there are no consistent columns.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__PD881_P2A.csv
0 rows

File structure

Notes: This is free-form text with no consistent column structure. The sample rows contain unstructured notes and labels like 'Name:', 'Address:', 'Soc #:', 'DOB:', etc., but there is no repeating tabular format. The data appears to be a mix of case notes and form-like entries without a fixed delimiter or column alignment. While some PII fields may exist in the text (e.g., names, addresses, DOB, SSN, phone), the lack of a consistent structure requires unstructured processing.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__PD881_P3.csv
1 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The data appears to be narrative descriptions of police property reports with no tabular format. While there are mentions of potentially sensitive terms like 'Owner' and 'Address', there are no identifiable PII patterns or structured columns to map. The content resembles case notes rather than delimited records.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__PD881_P4.csv
0 rows

File structure

Notes: The provided rows appear to be free-form text with no consistent delimiter or structured columns. Values are narrative case report snippets and page numbers. No identifiable PII columns can be mapped.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Start_Page.csv
1 rows

File structure

Notes: This is not a structured data file; it's a form or interactive page with labels and empty fields rather than actual records. The sample rows show form prompts ('Step 1 of 6:', 'Enter Your Information Below') and placeholders rather than tabular data. No consistent delimiter or column structure exists across rows, and values appear to be UI elements rather than imported PII records. Though a phone number appears in row 2 ('664-7032'), it is part of a form label example, not a data row. This file should be processed as unstructured content for potential embedded PII extraction.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__Subpoena.csv
0 rows

File structure

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

Notes: This file appears to be a template or form with placeholder text and no actual PII data in the first 50 rows. All columns contain static form labels, dropdown prompts, or empty values. No personal identifiable information (PII) fields are present in the sample data.

hallauerlaw.net__hallauerlaw.net_Copy_of_Felony_Folder_Master_01-21-13__Pugh2__lists.csv
0 rows

File structure

Notes: This file is purely categorical/lookup data (race, sex, marital status, vehicle makes, offense codes, etc.). No actual person records or PII values are present in the first 50 rows. The structure shows static lists of categories rather than real case files. Therefore, no column mapping is possible or necessary.

hallauerlaw.net__hallauerlaw.net_Copy_of_SBA_Rd2_2nd_Draw_PPP_Loan_Calculator_1_19__2nd_Draw_PPP.csv
0 rows

File structure

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

Notes: This file is a PPP loan calculation template with no actual PII data present. All values appear to be example inputs and calculations rather than real customer data. No columns contain identifiable personal information.

hallauerlaw.net__hallauerlaw.net_Copy_of_SBA_Rd2_2nd_Draw_PPP_Loan_Calculator_1_19__Forgiveness_Calculator.csv
0 rows

File structure

Notes: The file is a free-form text document describing SBA Paycheck Protection Program loan forgiveness calculations. It contains no structured data or PII fields — only explanatory text and numerical placeholders. No column mapping is possible or required.

hallauerlaw.net__hallauerlaw.net_Copy_of_SBA_Rd2_2nd_Draw_PPP_Loan_Calculator_1_19__Forgiveness_Records.csv
0 rows

File structure

Notes: This is not structured tabular data. The provided sample shows free-form text lines with no consistent delimiter or column structure. The content appears to be document fragments and notes rather than a delimited table with PII fields. Therefore, it is classified as unstructured text.

hallauerlaw.net__hallauerlaw.net_Copy_of_SBA_Rd2_2nd_Draw_PPP_Loan_Calculator_1_19__Loan_Documentation.csv
0 rows

File structure

Notes: This file is unstructured text containing legal case notes and SBA loan application documentation. The sample shows free-form prose paragraphs rather than tabular data with consistent columns. There are no identifiable PII fields in structured format; any potential PII would need to be extracted from the free text.

hallauerlaw.net__hallauerlaw.net_Copy_of_SBA_Rd2_2nd_Draw_PPP_Loan_Calculator_1_19__PPP_First_Draw.csv
0 rows

File structure

Notes: The file is a free-form text document containing instructions and calculations for a Paycheck Protection Program loan calculator. It lacks consistent row structure and column alignment, with rows varying in length and content. No PII fields are present in the structured sense; the content is entirely procedural and financial guidance.

hallauerlaw.net__hallauerlaw.net_Copy_of_SBA_Rd2_2nd_Draw_PPP_Loan_Calculator_1_19__PPP_Loan_Increase.csv
0 rows

File structure

Notes: This is a free-form document describing PPP loan increase/reapplication guidelines for Hallauer Law. It contains no structured data rows or columns — just prose instructions and examples. No PII is present in this sample.

hallauerlaw.net__hallauerlaw.net_Copy_of_SBA_Rd2_2nd_Draw_PPP_Loan_Calculator_1_19__Payroll_Documentation.csv
0 rows

File structure

Notes: This file contains unstructured free-form text with no consistent column structure or delimiter. The content appears to be legal documentation and application instructions for SBA Paycheck Protection Program loans, with no embedded emails or phone numbers visible in the sample. Therefore, no column mapping is performed.

hallauerlaw.net__hallauerlaw.net_Copy_of_SBA_Rd2_2nd_Draw_PPP_Loan_Calculator_1_19__Rd2_PPP_Loan_Calculator.csv
0 rows

File structure

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

Notes: This file is a template for PPP loan calculations, not containing any actual PII data. All columns are either instructions or placeholders for financial calculations, with no real personal information present in the first 50 rows.

hallauerlaw.net__hallauerlaw.net_Copy_of_SBA_Rd2_2nd_Draw_PPP_Loan_Calculator_1_19__Reduction_Documentation.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure; appears to be a collection of financial guidance notes and instructions rather than structured data records. No column mapping possible.

hallauerlaw.net__hallauerlaw.net_Corbin_Accurint.csv
6 columns21 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamemedium[0] header 'Full Name', values contain surname 'CORBIN' though data is garbled/corrupted
1genderlow[1] header 'Gender', values appear misaligned containing names and phone numbers due to data corruption, but header intent is gender
2ssnmedium[2] header 'SSN', values are None in sample but header unambiguously indicates social security number
3dobmedium[3] header 'DOB/Age', values are None in sample but header unambiguously indicates date of birth
5address1medium[5] header 'Address', maps to address1; no sample values shown but header is clear
6phonemedium[6] header 'Phone Information', sample values include '434-831-2113' confirming phone numbers present despite data misalignment

Notes: Data is severely corrupted with encoding issues and column misalignment — values frequently appear in wrong columns. Headers are the primary mapping signal. Columns for Property, Motor Vehicle, People at Work, DOD/Age at Death, and LexID are non-PII or internal identifiers and are skipped.

hallauerlaw.net__hallauerlaw.net_Corbin_Accurint_1.csv
6 columns21 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamemedium[0] header 'Full Name', values contain 'CORBIN' which appears to be a surname fragment despite data corruption/misalignment
1genderlow[1] header 'Gender', though values are garbled the column is labeled Gender and contains fragments like 'J' which may be gender codes
2ssnhigh[2] header 'SSN' explicitly maps to social security number field; values are None in sample but field is clearly labeled
3dobhigh[3] header 'DOB/Age' explicitly maps to date of birth; values are None in sample but field is clearly labeled
5address1high[5] header 'Address' maps to address1; no sample values visible but header is unambiguous
6phonemedium[6] header 'Phone Information', sample values include '434-831-2113' which is a phone number despite other garbled address-like values mixed in

Notes: Data is severely corrupted/misaligned — values appear shifted across columns. Headers are reliable indicators. Column [1] Gender contains garbled name fragments due to data shift. Column [6] Phone Information contains a visible phone number '434-831-2113' alongside misaligned address data. This is sensitive law enforcement/legal data including suspect, witness, and confidential source records.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Arr_Labels.csv
0 rows

File structure

Notes: The data appears to be free-form legal case notes with no consistent delimiter or column structure. Lines contain mixed content including case descriptions ("Robbery to Individual Arrest"), addresses ("7932 Harold Street"), dates ("7/26/13"), and person identifiers ("Singleton, Teshia V(B/F 27)", "Jones, Samuel A(B/M 48)"). No repeated column pattern is detectable across the sample rows. This qualifies as unstructured text with embedded PII that should be processed by a streaming extractor.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Case_Report_Data.csv
1 rows

File structure

Notes: This file is unstructured. It appears to be a free-form text file with no consistent delimiter structure. The sample shows lines with varying content and structure, and there are no clear column headers or repeating patterns that would indicate a tabular format. The content seems to contain investigative notes and case details, but lacks the structure needed for column mapping.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Case_Summary.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample shows prose entries like 'Offense:', 'Date:', 'Items Stolen:', etc., with varying content per line. While there are no visible emails or phones in this slice, the unstructured format detection applies because of the lack of consistent column structure.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Def__1_Detention_Sheet.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent delimiter or structured columns. The sample contains instructional text, placeholder values, and mixed content rather than tabular data. This matches the description of legal case files with unstructured notes and forms rather than structured PII records.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Def__1_FF.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The lines contain narrative text (e.g., 'FIRST TIME FELONY/INITIAL HEARING REPORT', 'Continuance', 'Nolle Prosse', 'Extradition', etc.) and appear to be legal case notes or reports rather than structured data. There are no repeated columnar patterns, and each line has a different shape and content. No PII fields are identifiable in this structured format; any potential PII would need to be extracted from free-text content via unstructured processing.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Def__1_Magistrate.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample rows contain legal case documentation, but there is no tabular structure. Values like '664-7032' could be phone numbers, but they appear in free-text context without column alignment. All rows have wildly different content and length, meeting unstructured conditions (a), (b), and (c).

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Def__2_Detention_Sheet.csv
0 rows

File structure

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

Notes: The provided data appears to be a mix of form instructions and placeholder text rather than structured records containing PII. The columns contain repetitive instructional text ("Fill in all known information", "Booking personnel will provide"), generic labels ("Last Name", "First Name"), and empty strings. No actual PII values are present in the sample rows. This appears to be a template or form rather than breached data records.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Def__2_FF.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The sample lines contain case report headers, instructions, and legal terminology but no identifiable PII columns. There are no embedded emails or phone numbers visible in the sample.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Def__2_Magistrate.csv
0 rows

File structure

Notes: This file is free-form legal document text, not structured tabular data. Sample lines show narrative text with occasional fields like phone numbers (664-7032) and codes, but no consistent column alignment or delimiter. This qualifies as unstructured text with embedded PII that should be processed via streaming extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Def__3_Detention_Sheet.csv
0 rows

File structure

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

Notes: The provided sample shows a free-form text file with no consistent delimiter or structure. The lines appear to be instructions, notes, and partial form fields rather than a tabular dataset with repeating columns. There are no identifiable PII columns in this sample, and the content does not conform to a structured format. Therefore, no columns are mapped.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Def__3_FF.csv
0 rows

File structure

Notes: This is unstructured data. The file appears to be a collection of legal case notes, court documents, and investigative reports rather than structured tabular data. There are no consistent delimiters or repeating column patterns across the rows. The content includes case statuses, officer names, commands, dates, and instructions, but it lacks any tabular structure that could be parsed into columns with consistent PII fields. Since there is no consistent row structure, we treat this as unstructured text.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Def__3_Magistrate.csv
0 rows

File structure

Notes: This is not a structured dataset; it appears to be free-form legal document text. Columns are not consistently defined across rows and contain narrative entries such as "REQUEST FOR MAGISTRATE’S WARRANT", "Magistrate’s Office: 664-4196", "Investigator:", etc. There are no identifiable column headers or consistent structure that would allow mapping to PII fields. The values appear to be mixed legal prose and minimal data fragments, not a CSV or tabular format.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Grand_Jury.csv
0 rows

File structure

Notes: The file contains unstructured legal case documentation from a law firm breach. It includes free-form text entries like case titles, defendant labels, investigator notes, and other investigative records. There is no consistent column structure, and therefore no PII columns can be mapped in a structured way. This should be processed as unstructured text for further analysis.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Inv_Labels.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains embedded names and locations but lacks columnar format

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__JCF.csv
1 rows

File structure

Notes: This file is a README or description document, not structured data. It contains prose text describing an intake form template with placeholders like "LAST NAME FIRST MIDDLE" and "PRESENT HOME ADDRESS", but no actual record rows with personal data. The content is instructional/metadata and does not contain parseable PII fields.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__JFV.csv
0 rows

File structure

Notes: The provided data appears to be free-form text with no consistent delimiter structure. The content includes headers like 'NORFOLK POLICE DEPARTMENT' and 'JUVENILE FINGERPRINT VALIDATION FORM', but the data rows are unstructured prose rather than tabular records. This matches the unstructured opt-out conditions: (a) no consistent delimiter, (b) lines have different shapes, and (c) no clear PII columns are present in structured format. The data is likely part of legal case files or investigative documents rather than structured PII records.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__JPC.csv
0 rows

File structure

Notes: This is free-form legal documentation with no consistent columnar structure. The file contains prose descriptions, numbered sections, and narrative text typical of court affidavits and investigative reports. While some fields hint at PII concepts (e.g., 'DOB', 'Telephone', 'Juvenile’s Name', 'Juvenile’s Address'), they appear within unstructured legal text rather than as discrete, repeatable columns. Therefore, this file should be processed as unstructured text with embedded PII extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__PD881_P1.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample shows irregular lines containing phrases like "SOURCE: ", "Report Submitted By:", "Phone Number:", "Defendant #1 Section:", "Name", and other unstructured report elements. While there are occasional appearances of what look like phone numbers (e.g., "664-7032") and potentially date-like strings ("7/26/13"), the data lacks any consistent column pattern or repeating structure across rows. This qualifies as unstructured text requiring a streaming PII extractor.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__PD881_P2.csv
0 rows

File structure

Notes: This file is a free-form text document containing narrative entries and case notes rather than structured tabular data. The sample lines show unstructured police report content from Norfolk Police Department with no consistent columnar format. While it contains sensitive case metadata, it lacks delimited columns for PII mapping. Therefore, it is classified as unstructured text with embedded sensitive information requiring special handling.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__PD881_P2A.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent columnar structure. The sample shows lines with labels like "Name:", "Address:", "Soc #:", "DOB:", "Phone:", etc., but there is no shared delimiter or fixed column positions across rows. The data appears to be a mixture of narrative entries and form-like fields, typical of a case report or investigative document. Because it lacks a consistent delimiter and row structure, it is classified as unstructured. Embedded PII such as names, addresses, DOB, phone numbers, and SSNs will be extracted via streaming processing.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__PD881_P3.csv
1 rows

File structure

Notes: The provided rows are free-form text with no consistent column structure. Values appear to be narrative descriptions from police reports (e.g., "NORFOLK POLICE DEPARTMENT", "Property is: Recovered"). While there may be embedded PII in prose, the lack of structured columns means we must treat this as unstructured text for downstream extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__PD881_P4.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent delimiter structure across rows. The sample contains document headers and page numbers, but no identifiable column-based data. There are no visible emails or phone numbers in the first 50 rows to trigger the unstructured opt-out rule, but the lack of structured columns means we must treat this as unstructured text.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Start_Page.csv
1 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The sample shows mixed prose lines like "Step 1 of 6: " and "FI. MI. Last Name:", not a delimited dataset. Although there are values that look like a name ("B. E. Pugh") and a phone number ("664-7032"), they appear embedded in unstructured text rather than in a tabular format. This matches the unstructured opt-out criteria: no consistent delimiter, varying line shapes, and visible PII in prose.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__Subpoena.csv
0 rows

File structure

Notes: The file appears to be a subpoena form template rather than actual breached data containing PII. All visible values are placeholder text or generic legal terminology with no identifiable personal information. The structure shows empty or placeholder fields rather than populated records.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_1__lists.csv
0 rows

File structure

Notes: The provided data appears to be a structured file, but the columns do not contain any PII fields. The data seems to be categorical or descriptive in nature, listing various categories such as race, sex, marital status, vehicle types, demeanor, offenses, etc. There are no columns that map to PII fields such as email, phone, dob, name, address, etc. Therefore, no PII columns are identified.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Arr_Labels.csv
0 rows

File structure

Notes: The sample shows free-form text with no consistent delimiter structure. Lines contain legal case notations like 'DEF:', 'BUS:', 'VIC:', and person entries such as 'Smith, Pierre D (B/M 31)' and 'Singleton, Teshia V(B/F 27)'. Though names and potentially dates appear, the lack of a fixed column layout means this is unstructured text, not a delimited table. It matches the unstructured opt-out conditions: no shared delimiter, wildly varying line shapes, and embedded PII in prose form.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Case_Report_Data.csv
1 rows

File structure

Notes: The file is unstructured free-form text with no consistent column structure. The data appears to be case notes or investigation logs containing embedded names and other details, but lacks a consistent delimiter or column layout. The sample shows free-form entries with names and other data scattered throughout, confirming it should be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Case_Summary.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. Each line has a different shape and contains prose-style entries like case summaries, victim/suspect descriptions, and narrative notes. While some lines contain potentially sensitive information, the format lacks columnar structure, so it must be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Def__1_Detention_Sheet.csv
0 rows

File structure

Notes: The provided data is free-form text with no consistent delimiter or structured columns. The content appears to be instructional text and field labels rather than actual record data, and shows no repeating column pattern across rows. While some lines contain fragments that resemble PII field labels (e.g., 'Last Name', 'First Name', 'DOB'), these are part of instructions rather than actual data records. The format does not conform to CSV/TSV expectations, and row structures vary significantly, meeting criteria for unstructured free-form text with embedded potential PII fragments.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Def__1_FF.csv
0 rows

File structure

Notes: The provided sample is free-form text with no consistent column structure. Each line contains varied content and does not follow a shared delimiter pattern. While there are no visible emails or phone numbers in the sample, the unstructured nature of the data indicates it should be processed through a streaming extractor for potential embedded PII.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Def__1_Magistrate.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent delimiter. The sample shows lines of narrative text ("REQUEST FOR MAGISTRATE’S WARRANT", "Magistrate’s Office: 664-4196 Facsim...", "Investigator:", etc.) rather than tabular data. While phone numbers appear inline (e.g., 664-7032, 230-25-9788), there is no shared column structure across rows — each line contains different fields and formats. This meets the unstructured condition: (a) no consistent delimiter, (b) lines have wildly different shapes, (c) emails/phones are visible. Therefore, route through streaming email/phone extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Def__2_Detention_Sheet.csv
0 rows

File structure

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

Notes: The file appears to be a free-form text document with no consistent columnar structure. It contains procedural instructions and form field labels rather than actual PII data in a tabular format. No columns map to PII fields because there is no structured data present.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Def__2_FF.csv
0 rows

File structure

Notes: This is a free-form text document with no consistent column structure. It appears to be legal case documentation from Hallauer Law's breach, containing narrative entries rather than tabular data. Sample lines show legal case notes, officer names, and case status codes, but there are no delimited columns with repeated patterns across rows. The presence of names and case identifiers does not constitute structured columnar data; this should be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Def__2_Magistrate.csv
0 rows

File structure

Notes: This is free-form text with no consistent column structure. Sample lines contain legal case headers, investigator notes, and fragmented fields without a shared delimiter. Though there are occasional phone-like numbers (e.g., 664-7032), the format lacks reproducible columns across rows and is therefore unstructured. It will be processed by a streaming email/phone extractor.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Def__3_Detention_Sheet.csv
0 rows

File structure

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

Notes: The provided data appears to be free-form text with no consistent column structure. The sample rows contain instructional text, placeholders, and fragmented notes rather than structured records. There are no identifiable PII columns in this dataset.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Def__3_FF.csv
0 rows

File structure

Notes: This is not a structured data file but a free-form text document containing legal case notes and reports from the Norfolk Police Department. The sample shows unstructured prose with no consistent columnar pattern, containing entries like case status codes ("FIRST TIME FELONY/INITIAL HEARING REPORT"), officer names ("B. E. Pugh"), and case types ("Robbery"). No PII columns can be mapped as there is no consistent structure to parse.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Def__3_Magistrate.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent column structure. The sample rows contain prose descriptions and form fields (e.g., "REQUEST FOR MAGISTRATE’S WARRANT", "Norfolk Police Department"), not delimited tabular data. Although some potential PII fragments appear ("664-4196", "664-7032"), they exist within narrative text rather than as structured columns. Per rules, unstructured files with no consistent delimiter and varying line shapes must be processed via streaming extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Grand_Jury.csv
0 rows

File structure

Notes: This is a free-form text document containing legal case notes and investigative records. The data lacks consistent column structure with each line appearing as narrative text rather than tabular data. While some lines contain what appears to be PII fragments (e.g., 'Smith, Pierre D', '5/2/82'), the format does not follow a consistent delimiter pattern across rows and contains prose rather than structured fields. This meets the unstructured criteria: no consistent delimiter, variable line shapes, and embedded potential PII.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Inv_Labels.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. Lines vary in length and content, containing embedded PII such as names and locations but not in a tabular format. The content appears to be investigative notes from a law enforcement context, including victim information and location details. The unstructured format requires routing through a streaming email/phone extractor, but no column mapping is performed due to lack of consistent structure.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__JCF.csv
1 rows

File structure

Notes: The file is a free-form document with no consistent delimiter structure. The sample shows header-like text mixed with data entries (e.g., 'LAST NAME FIRST MIDDLE', 'PRESENT HOME ADDRESS', 'SSN', 'DOB'). This is typical of scanned forms or printed documents where lines do not follow a strict CSV/TSV pattern. The presence of embedded PII like names, addresses, SSN, and DOB means unstructured processing is required.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__JFV.csv
0 rows

File structure

Notes: The provided rows appear to be free-form text rather than structured tabular data. The content includes header-like lines such as 'NORFOLK POLICE DEPARTMENT', 'JUVENILE FINGERPRINT VALIDATION FORM', and 'To:', 'From:', indicating this is a document or report format rather than CSV with consistent columns. There are no repeating delimiters or structured field positions across the rows. While the sample does not show explicit emails or phone numbers, the unstructured nature and prose format meet the criteria for unstructured opt-out processing.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__JPC.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent delimiter or column structure. The sample contains prose and narrative entries typical of legal documents and affidavits, with no repeating tabular data. While there are embedded values that look like names (e.g., "Smith, Pierre D"), addresses (e.g., "924 Trice Terrace B Norfolk, VA 23502"), dates (e.g., "7/26/13"), and potentially phone numbers (e.g., "757 561-4063")), these appear within narrative text rather than as structured columns. The file must be processed with unstructured text extraction for emails and phone numbers.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__PD881_P1.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or structure. The sample shows legal case report headers and narrative text rather than tabular data. While some PII-like patterns appear (phone numbers, dates, names), they are embedded within unstructured prose rather than in defined columns.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__PD881_P2.csv
1 rows

File structure

Notes: This file appears to be free-form text containing case report headers and evidence documentation rather than structured tabular data. The content shows narrative descriptions like "FELONY CASE REPORT", "Autopsy", and "Fingerprints: Positive Negative" without consistent columnar data or delimiters. No identifiable PII columns exist in this sample.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__PD881_P2A.csv
0 rows

File structure

Notes: This is an unstructured document with free-form text. The sample shows lines with various labels like 'Name:', 'Address:', 'DOB:', 'Phone:', etc., but there is no consistent columnar structure. The data appears to be free-form notes or case report entries rather than a delimited table with repeating columns. Therefore, it should be processed as unstructured text with embedded PII.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__PD881_P3.csv
1 rows

File structure

Notes: This is not a structured dataset but free-form legal case documentation from Hallauer Law breach. The sample shows prose entries like "PROPERTY", "VEHICLE", "Released", "Year:", "License #", etc., with no consistent columnar format. Values appear to be narrative descriptions of evidence vouchers, property recovery logs, and investigative notes rather than tabulated PII fields. Since there is no consistent delimiter or row structure, and the content is free-form legal text, this should be processed as unstructured.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__PD881_P4.csv
0 rows

File structure

Notes: This is a free-form text document with no consistent delimiter structure. The sample lines show unstructured case report headers and narrative text ("FELONY CASE REPORT", "Probable Cause and Events of Case: ...", "SUMMARY"). No columnar data present. While the file is from a law firm breach and likely contains sensitive case details, the provided rows are not in a parseable tabular format — they are narrative case documentation. According to the unstructured opt-out rules, return empty columns object.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Start_Page.csv
1 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or structured columns. The lines contain mixed content including prompts, instructions, and sample values, but there is no repeating column structure. While some lines contain what appear to be PII fragments (e.g., 'B. E. Pugh', '664-7032'), the lack of consistent delimiters and varying line shapes means this must be processed as unstructured text for embedded PII extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__Subpoena.csv
0 rows

File structure

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

Notes: This is a legal subpoena document header row with no PII fields. All columns contain court/jurisdiction identifiers, case references, and placeholder empty cells. No columns map to PII fields.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_2__lists.csv
0 rows

File structure

Notes: This is a structured but non-PII data file. The headers and values are codes and categories (race, sex, vehicle types, offenses, legal codes), not personal identifying information. No emails, phone numbers, names, addresses, DOB, SSN, etc. are present in the sample. The file is a lookup/reference table for law enforcement case coding, not containing any actual personal data of individuals.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Arr_Labels.csv
0 rows

File structure

Notes: The data appears to be free-form text with inconsistent structure and no consistent delimiter. The sample contains unstructured entries such as case identifiers, names, and addresses embedded in prose. There is no consistent column structure across rows, and values like names and addresses are interleaved with other text. This matches the unstructured opt-out criteria (a) no consistent delimiter, (b) every line has a different shape, and (c) contains names that could be considered PII, but they are not in a tabular format. Therefore, it should be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Case_Report_Data.csv
1 rows

File structure

Notes: This file is not structured data. The sample shows free-form text with no consistent delimiter. Each line contains narrative updates and case notes rather than tabular data. The content includes phrases like "Update: 08/22/13: Lisa Deparasis wa..." and contains personal names (e.g., "Singleton", "Jones", "Lewis"), but they appear in prose rather than as columns. Therefore, this is classified as unstructured text with embedded PII that requires special handling.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Case_Summary.csv
0 rows

File structure

Notes: This file is free-form text with no consistent columnar structure. The sample shows narrative entries like 'Offense:', 'Date:', 'Items Stolen:', etc., and lacks any repeated delimiter patterns. While there are mentions of potentially PII-like terms (e.g., names, addresses), the entire file appears to be prose-style case notes rather than a structured dataset. Therefore, it is classified as unstructured text for downstream PII extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Def__1_Detention_Sheet.csv
0 rows

File structure

Notes: This is a free-form document with no consistent delimiter structure. The sample shows instructional text and form placeholders rather than tabular data. There are no repeated column patterns or structured fields across rows. The content appears to be form instructions and field labels rather than actual records, with no identifiable PII in the values shown.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Def__1_FF.csv
0 rows

File structure

Notes: This file is a free-form text document containing legal case notes and court reporting data. The content consists of prose entries like "FIRST TIME FELONY/INITIAL HEARING REPORT", court codes, dates, and narrative text. There are no consistent tabular columns — each line is a separate note or annotation with varying formats and content. Although it contains sensitive case information, it lacks a structured column format for PII mapping.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Def__1_Magistrate.csv
0 rows

File structure

Notes: This is a free-form document with no consistent columnar structure. The sample shows legal case file text, warrants, and investigative notes rather than structured data. Though phone numbers appear inline (e.g., '664-4196', '664-7032', '230-25-9788'), the format is unstructured prose, not a delimited table. Therefore, the file should be processed as unstructured text for embedded PII extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Def__2_Detention_Sheet.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Def__2_FF.csv
0 rows

File structure

Notes: This is not a structured dataset. The file appears to be free-form text containing legal case notes, court reports, and procedural instructions. There are no consistent delimiters or columnar structure across the rows. The content includes case statuses, officer names, commands, and instructions, but it lacks the consistent tabular format required for column mapping. No PII columns can be identified due to the unstructured nature of the data.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Def__2_Magistrate.csv
0 rows

File structure

Notes: The file appears to be free-form legal document text (warrant requests, court forms) with no consistent tabular structure. While some lines contain phone numbers (e.g., 664-7032) and potentially other PII, the data lacks a uniform delimiter or column alignment across rows, meeting unstructured criteria. Will be processed via streaming PII extractor.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Def__3_Detention_Sheet.csv
0 rows

File structure

Notes: This file appears to be a free-form document with no consistent columnar structure. The sample shows unstructured legal forms with bullet points, instructions, and field labels rather than tabular data. There are no repeating patterns of delimited columns across rows, and the content looks like prose instructions mixed with placeholder field labels (e.g., "NAME", "Last Name", "First Name"). While some PII-like terms appear as labels, they are not actual data entries in a structured format. This meets the unstructured criteria: no consistent delimiter, variable line shapes, and contains instructional text rather than record data.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Def__3_FF.csv
0 rows

File structure

Notes: This is not a structured CSV/TSV file. The sample shows free-form legal case documentation from a law firm breach. Lines contain prose descriptions like "FIRST TIME FELONY/INITIAL HEARING REPORT", "Continuance", and "Nolle Prosse", along with occasional names (e.g., "B. E. Pugh"). There is no consistent delimiter or column pattern across rows — each line is a free-text legal note. Though names appear, the format is unstructured prose, not a tabular dataset. The unstructured flag is appropriate per rules.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Def__3_Magistrate.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or column structure. The sample lines contain unstructured legal document text and contain no identifiable columnar data. There are no repeated patterns or consistent field positions across rows.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Grand_Jury.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or column structure. The sample contains embedded personal data (e.g., 'Smith, Pierre D', '5/2/82'), but lacks tabular structure. The content appears to be legal case notes with headers like 'DEFENDANT:' and 'INVESTIGATOR:', confirming unstructured format. All rows have wildly different shapes and content.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Inv_Labels.csv
0 rows

File structure

Notes: free-form text with embedded names and addresses; no consistent delimiter structure across lines. Sample shows case notes with victim names and location addresses but lacks a tabular format.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__JCF.csv
1 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. It contains legal intake forms with embedded PII such as names, addresses, SSN, DOB, and demographic data, but lacks a consistent delimiter or header structure across rows. The sample shows varied content per line with no repeating pattern, meeting the criteria for unstructured data.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__JFV.csv
0 rows

File structure

Notes: This is a free-form document (likely a PDF scan or text extraction) with no consistent columnar structure. Lines vary in length and content, and the text appears to be narrative or form-like (e.g., headers like "NORFOLK POLICE DEPARTMENT"). While it may contain embedded PII in prose, the format does not permit column mapping — it must be processed as unstructured text for email/phone extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__JPC.csv
0 rows

File structure

Notes: This is free-form legal documentation with no consistent delimiter or structured columns. The content appears to be a narrative affidavit or probable cause form with embedded PII such as names, addresses, DOB, and phone numbers within the prose text. This qualifies as unstructured data requiring a streaming email/phone extractor.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__PD881_P1.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. Lines contain mixed content including report headers, case details, and personal identifiers embedded in prose. Examples include 'Smith, Pierre D', '924 Trice Terrace B Norfolk VA 23502', '2101', '5/2/82', '230-25-9788', etc. Given the lack of a consistent delimiter and varying line structures, this qualifies as unstructured data requiring free-text extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__PD881_P2.csv
1 rows

File structure

Notes: This is a free-form text document from Hallauer Law breach containing case report headers and evidence descriptions. No consistent columnar structure exists across rows — values are narrative descriptions and codes, not tabular data. While the file is sensitive legal content, it lacks the consistent delimiter or header structure required for column mapping. The sample shows unstructured case report titles and evidence fields, not importable PII columns.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__PD881_P2A.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent delimiter structure across lines. The sample shows prose entries like 'Name:', 'Address:', 'DOB:', 'Phone:', etc., with no fixed columnar layout. While it contains PII hints (email, phone, DOB), the data lacks a consistent row structure required for columnar mapping, and should be processed through a streaming email/phone extractor.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__PD881_P3.csv
1 rows

File structure

Notes: This is free-form text with no consistent delimiter or row structure. The sample shows irregular, narrative-style entries typical of police reports or case notes (e.g., 'Property is: Recovered', 'Voucher 19359, Item 1: Black cellular...'). No columns are defined, and the content is prose-like with embedded details rather than tabular data. While sensitive information may exist within the text, the format requires unstructured processing.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__PD881_P4.csv
0 rows

File structure

Notes: This file appears to be free-form text from law enforcement case files (NORFOLK POLICE DEPARTMENT). The content includes narrative case summaries and lacks any consistent tabular structure or columnar data. There are no detectable headers or repeating column patterns across the first 50 rows, and the sample lines contain unstructured prose. No PII columns can be mapped.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Start_Page.csv
1 rows

File structure

Notes: This file is not a structured dataset with consistent columns and delimiters. It appears to be a form template or mixed content, possibly from a web form or document. As such, no column mappings can be made. The presence of what looks like a name ('B. E. Pugh') and a phone number ('664-7032') is embedded within free-form text, triggering the unstructured opt-out rule.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__Subpoena.csv
0 rows

File structure

Notes: This file is a free-form legal document (subpoena template) with no consistent columnar structure. It contains headers like 'REQUEST FOR WITNESS SUBPOENA' and values like 'City of Norfolk', 'Commonwealth of Virginia', and 'Smith, Pierre D', but these appear in free-form text lines without a fixed delimiter or repeated column pattern across rows. The presence of unstructured legal prose and lack of any consistent repeating format across the first 50 rows indicates this is not a CSV or tabular file. While names and locations appear, they are embedded in narrative text rather than structured columns.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_3__lists.csv
0 rows

File structure

Notes: This file is not structured tabular data. The rows contain free-form categorical data and codes (race, sex, marital status, vehicle makes, offense codes, etc.). There are no columns with personal identifiers like names, addresses, emails, or phone numbers in the first 50 rows. The data appears to be classification/coding tables used within the legal case files rather than direct PII records.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Arr_Labels.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent delimiter structure. Sample rows contain legal case notes, arrest information, and investigative records with no repeating columnar pattern. Values like " Smith, Pierre D (B/M 31)" and "1333 Poindexter St Chespeake" suggest embedded PII, but due to lack of structured columns, this must be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Case_Report_Data.csv
1 rows

File structure

Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Case_Summary.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or structured columns. The data appears to be case notes or investigative summaries with fields like offense, date, victim, suspect, etc. While there may be embedded PII in the text, the format does not conform to a structured table with consistent columns, so it should be processed as unstructured text for PII extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Def__1_Detention_Sheet.csv
0 rows

File structure

Notes: The file is unstructured free-form text with no consistent delimiter or column structure. The sample shows prose instructions mixed with data fields, not a tabular format. It contains sensitive legal case information but lacks a structured format for column mapping.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Def__1_FF.csv
0 rows

File structure

Notes: The provided data appears to be free-form text with no consistent columnar structure. Each line contains different content related to legal case notes, court instructions, and case types (e.g., 'FIRST TIME FELONY/INITIAL HEARING REPORT', 'Robbery', 'Continuance'). There are no repeating fields or consistent delimiters, and while some lines contain names like 'BE Pugh' and 'Smith, Pierre D', these are embedded within unstructured prose rather than in a tabular format. Therefore, this is classified as unstructured text with no column mapping possible.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Def__1_Magistrate.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent delimiter or column structure. The sample lines show narrative entries and headers like 'REQUEST FOR MAGISTRATE'S WARRANT', 'Magistrate's Office: 664-4196', 'Investigator:', etc., with no repeated pattern across rows. While some lines contain phone numbers (e.g., '664-4196', '664-7032', '230-25-9788') and possibly a date ('5/2/82'), the data lacks a tabular structure, so it must be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Def__2_Detention_Sheet.csv
0 rows

File structure

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

Notes: This file appears to be a template or instruction document rather than structured data containing PII. The sample rows contain instructional text and field labels (e.g., "Last Name", "First Name", "DOB") but no actual personal data. No columns map to PII fields because there are no rows with personal information. The structure is inconsistent and contains mostly placeholder text.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Def__2_FF.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or column structure. The data appears to be legal case documentation from Hallauer Law's breach, containing narrative entries, case notes, and procedural text rather than structured tabular data. There are no identifiable PII columns to map.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Def__2_Magistrate.csv
0 rows

File structure

Notes: This is free-form legal document text with no consistent delimiter structure. The sample shows narrative entries like "REQUEST FOR MAGISTRATE’S WARRANT", "Norfolk Police Department", and fragments such as "664-7032". There are no repeating columnar patterns across rows, and values appear as prose rather than structured data fields. Though a phone number fragment (664-7032) appears, the lack of consistent column alignment means this must be processed as unstructured text for email/phone extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Def__3_Detention_Sheet.csv
0 rows

File structure

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

Notes: This file appears to be a free-form text document with instructions and form field labels rather than structured data records. The sample rows contain form instructions, field labels (e.g., 'Last Name', 'First Name', 'DOB'), and placeholder text rather than actual PII values. There is no consistent columnar structure with repeated records; instead, it appears to be a template or instruction sheet for a law enforcement form (PD 940). Therefore, no PII columns can be mapped as there are no actual data rows to analyze.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Def__3_FF.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter structure. Each line contains different content shapes and appears to be narrative legal case documentation from the Hallauer Law breach. There are no structured columns to map; this file should be processed as unstructured text for embedded PII extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Def__3_Magistrate.csv
0 rows

File structure

Notes: This is unstructured prose / legal document format. No consistent delimiter or column structure. Contains embedded phone number '664-4196' and '664-7032', but lacks any row-based tabular structure. All lines are free-form text records from legal case files.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Grand_Jury.csv
0 rows

File structure

Notes: This is not a structured CSV/TSV file. The sample shows free-form text lines with no consistent delimiter or column structure. Lines contain phrases like 'DEFENDANT:', 'RACE:', 'SEX:', and 'DOB:' but these appear to be labels within narrative text rather than actual column headers. Values like 'Smith, Pierre D' and dates '5/2/82' appear inline but lack positional consistency across rows. This matches the unstructured opt-out criteria: no consistent delimiter, wildly varying line shapes, and embedded PII in prose format. The breach context (law firm case files) also suggests these are investigative reports rather than tabular data.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Inv_Labels.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; lines vary in format and content, appears to be investigative report notes with embedded names and locations

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___JCF.csv
1 rows

File structure

Notes: The file is unstructured text. The sample shows free-form entries such as 'JUVENILE INFORMATION', 'Smith, Pierre D', 'LAST NAME FIRST MIDDLE', '924 Trice Terr B', 'PRESENT HOME ADDRESS', 'VA', 'STATE', 'Juvenile’s Father Information', 'NAME/MAIDEN', 'Date received in Intake:', '23502', 'ZIP', '0', 'STATE OF BIRTH', '230-25-9788', 'SSN', 'Juvenile's Guardian Information', 'NAME/MAIDEN', '5/2/82', 'DOB', 'M', 'MALE/FEMALE', '31', 'AGE', 'B', 'RACE'. These appear to be manually filled forms with no consistent delimiter or column structure across rows. The data contains embedded PII such as names, addresses, SSN, and DOB, which will be extracted via streaming processing.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___JFV.csv
0 rows

File structure

Notes: The provided rows are free-form text/prose with no consistent columnar structure. The data appears to be narrative legal documents from a law firm breach, containing headers like "NORFOLK POLICE DEPARTMENT" and "JUVENILE FINGERPRINT VALIDATION FORM". While there may be embedded PII in the body text, the format does not lend itself to columnar mapping. This qualifies as unstructured data per the rules (no shared delimiter, variable line shapes, and visible prose).

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___JPC.csv
0 rows

File structure

Notes: This is an unstructured document format (legal affidavits / case forms) with no consistent column structure. The sample shows free-form legal prose mixed with scattered PII-like fragments (e.g., 'Smith, Pierre D', '924 Trice Terr B Norfolk, VA 23502', '5/2/82', 'B', 'M', '757 561-4063'). There are no repeating column patterns or delimiters — each row represents a different section of a legal form. Since this meets the unstructured criteria (a) no consistent delimiter, (b) wildly varying line shapes, and (c) contains phone numbers, we route to unstructured processing for email/phone extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___PD881_P1.csv
0 rows

File structure

Notes: The provided data appears to be free-form text from legal case reports and investigative records. There is no consistent delimiter or structured column format across the rows. The content includes narrative descriptions, case numbers, names, addresses, and other details embedded in prose rather than in a tabular format. Given the unstructured nature of the data, it should be processed as unstructured text with embedded PII extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___PD881_P2.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. The sample shows unstructured report lines from police evidence logs and case documentation rather than tabular data. There are no repeated delimiters or field patterns across rows, and the content resembles narrative evidence descriptions rather than structured PII fields. No column mapping is possible.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___PD881_P2A.csv
0 rows

File structure

Notes: This is unstructured data. The sample shows free-form text entries with no consistent delimiter or column structure. The entries appear to be notes or form fields (e.g., "Name:", "Address:", "Soc #:", "DOB:", "Phone:", "Can Identify Defendant:", "Race:", "Occupation", "Sex:"). There are no repeating patterns across rows that would allow for column mapping. However, the presence of fields like "E-mail Address", "Soc #", "DOB", and "Phone" suggests PII is present, but due to the unstructured nature, column mapping cannot be performed.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___PD881_P3.csv
1 rows

File structure

Notes: This is free-form legal case file text with no consistent delimiter structure. The sample shows prose entries like "Property is: Recovered" and "Owner:" without columnar data. Though it contains sensitive legal content, it lacks a defined row/column structure required for mapping. The unstructured format will trigger streaming processing for any embedded PII.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___PD881_P4.csv
0 rows

File structure

Notes: This is a free-form text file containing legal case documentation, not a structured dataset. The rows show unstructured legal report text with no consistent column delimiters or headers. While no emails or phone numbers are visible in the first 50 rows, the nature of the file (legal case reports) suggests it may contain embedded PII elsewhere. This should be processed through unstructured text extraction for any hidden emails/phones.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Start_Page.csv
1 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample shows lines like "FI. MI. Last Name:", "Assignment/Squad", and "5 Digit Employee ID:", which are prompts or labels rather than structured data rows. While there is a phone number visible in row 2 ("664-7032"), the overall file lacks consistent column alignment and appears to be a mix of instructions and example data rather than a proper CSV or tabular dataset. This meets the criteria for unstructured opt-out: no consistent delimiter, varying line shapes, and embedded PII.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___Subpoena.csv
0 rows

File structure

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

Notes: This file appears to be a template or form for legal subpoenas with placeholder text and no actual PII data in the first 50 rows. All visible cells contain generic legal instructions, placeholder values, or empty strings. No columns contain personal information like names, addresses, or contact details in the sampled rows. Therefore, no PII columns are mapped.

hallauerlaw.net__hallauerlaw.net_Felony_Folder_Master_01-21-13___lists.csv
0 rows

File structure

Notes: This is not a delimited data file with personal identifiable information (PII) columns. The provided data appears to be a structured list of categories, codes, and legal references used for documenting case details in a law enforcement or legal context. There are no columns mapping to PII fields such as email, phone, name, address, etc. All entries are categorical or descriptive codes (e.g., race, sex, vehicle types, legal statutes, offense lists). Therefore, no PII columns exist to map.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Arr_Labels.csv
0 rows

File structure

Notes: This file is a free-form text file with no consistent delimiter or column structure. The data appears to be case notes or investigative records with embedded names and addresses (e.g., 'Smith, Pierre D (B/M 31)', '7932 Harold Street'). Due to the unstructured nature of the data, it should be processed through a streaming email/phone/name extractor rather than mapped to fixed columns. The presence of embedded personal identifiers (names, addresses) triggers the unstructured pathway.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Case_Report_Data.csv
1 rows

File structure

Notes: This is unstructured text data from legal case files containing free-form notes and updates. There is no consistent delimiter or column structure across the rows. The sample shows entries like case updates, names, and descriptive notes without a fixed format. While some potential PII like names appear in the text, the lack of a consistent structure means this should be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Case_Summary.csv
0 rows

File structure

Notes: The provided rows appear to be free-form text with no consistent column structure or delimiter. The content includes narrative descriptions and case summaries rather than structured tabular data. While there are mentions of personal details (e.g., names, locations), the lack of a consistent delimiter and varying line structures means this file must be processed as unstructured text for email/phone extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Def__1_Detention_Sheet.csv
0 rows

File structure

Notes: The file is unstructured free-form text with no consistent delimiter or column structure. It contains procedural instructions and placeholder text rather than tabular data. While there are fragments like 'Last Name' and 'First Name', these appear to be instructional placeholders rather than actual data columns. The content is not suitable for column-based PII mapping.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Def__1_FF.csv
0 rows

File structure

Notes: This is a free-form text document (not structured tabular data). The sample shows legal case notes, court document headers, and narrative text rather than columnar data. While there are names like 'B. E. Pugh' and 'Smith, Pierre D' present, they appear within unstructured prose rather than defined columns. The file lacks consistent delimiters and row structures, meeting the criteria for unstructured data.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Def__1_Magistrate.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. Each line has a different shape and contains prose, not tabular data. Visible phone numbers (e.g., 664-7032, 230-25-9788) confirm unstructured format. Cannot map to PII columns because there is no row structure.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Def__2_Detention_Sheet.csv
0 rows

File structure

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

Notes: The file appears to be a mix of free-form instructions and data fields, with no consistent header row or clear PII columns in the first 50 rows. The visible values are primarily instructional text or placeholder labels (e.g., "Last Name", "First Name"), not actual PII data. No columns clearly map to PII fields based on header names and sample values. Given the unstructured nature of the content and lack of actual PII in the sample rows, this should be treated as unstructured text for further processing.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Def__2_FF.csv
0 rows

File structure

Notes: The provided rows are free-form text with no consistent delimiter or column structure. Each row contains unstructured legal case notes and headers, with no identifiable PII columns. This matches the unstructured opt-out criteria: no shared delimiter, varying line shapes, and no importable structured data.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Def__2_Magistrate.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent delimiter structure. It contains unstructured legal document text rather than tabular data, with no repeating columnar pattern across rows. While some lines contain phone-like sequences (e.g., '664-4196', '664-7032'), these appear within prose descriptions rather than in a consistent column position.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Def__3_Detention_Sheet.csv
0 rows

File structure

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

Notes: This file appears to be a template or instruction sheet with placeholder text and column labels rather than actual data records. The columns contain instructions like "Fill in all known information" and field labels such as "Last Name", "First Name", "DOB", etc., but no actual PII values are present in the first 50 rows. Since there is no real data to map, and the structure appears to be instructional rather than containing breach records, no PII columns can be confidently identified. This is likely a form template used by the law firm, not a data export containing personal information from the breach.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Def__3_FF.csv
0 rows

File structure

Notes: This is a free-form legal document with no consistent column structure. The file appears to be a collection of police reports and legal forms with no repeating tabular data structure. All rows contain unstructured text and lack any identifiable PII columns.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Def__3_Magistrate.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent columnar structure. Each line contains unstructured prose including case headers, investigator notes, and form placeholders. No consistent delimiter or repeating column pattern is present across the first 50 rows. While some lines contain fragments that resemble phone numbers (e.g., '664-4196', '664-7032'), the overall structure is narrative rather than tabular, qualifying as unstructured text for PII extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Grand_Jury.csv
0 rows

File structure

Notes: This is a free-form text document with no consistent delimiter structure. The sample lines show legal case notes and investigative reports rather than tabular data. The format contains embedded names and dates but lacks column structure. The breach context mentions Hallauer Law case files with sensitive investigative records, but this specific file is unstructured prose, not a CSV or delimited data set.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Inv_Labels.csv
0 rows

File structure

Notes: free-form text with embedded names and locations; no consistent delimiter or row structure across lines. Contains victim names (e.g., 'Singleton, Teshia V') and location details, but lacks CSV/TSV structure. This qualifies as unstructured data requiring streaming extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__JCF.csv
1 rows

File structure

Notes: This file is a free-form text document with no consistent columnar structure. The sample lines contain header-like phrases but lack a repeating pattern or delimiter. Examples include 'JUVENILE INFORMATION', 'Smith, Pierre D', 'LAST NAME FIRST MIDDLE', etc. Since there is no consistent delimiter or row structure and the content appears to be prose-style legal form headers, it is classified as unstructured. Embedded PII values (like names and SSN) will be processed via streaming extraction.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__JFV.csv
0 rows

File structure

Notes: This file is unstructured text with no consistent column delimiters. The sample shows free-form text lines with varying content and no shared delimiter structure. It contains embedded text that may include PII, but requires unstructured processing.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__JPC.csv
0 rows

File structure

Notes: This is a free-form legal document with no consistent tabular structure. The sample lines are fragments of a probable cause affidavit from Norfolk Court Service Unit, containing narrative text, witness statements, and legal language. While some lines contain embedded PII (e.g., 'Smith, Pierre D', '924 Trice Terrace B Norfolk, VA 23502', '5/2/82', 'B', 'M', '757 561-4063'), the file lacks a consistent delimiter or column pattern across rows. This meets the criteria for unstructured text with embedded PII, requiring a streaming extractor.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__PD881_P1.csv
0 rows

File structure

Notes: The file is a free-form text document with no consistent delimiter structure. It contains prose entries such as report headers, case numbers, and narrative text rather than a tabular format with defined columns. The data appears to be a mix of case notes, legal references, and investigative records, but lacks any structured format suitable for column mapping.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__PD881_P2.csv
1 rows

File structure

Notes: The file appears to be free-form text with no consistent columnar structure. It contains header-like lines such as 'PD 881 NORFOLK POLICE DEPARTMENT' and unstructured data entries. No identifiable PII columns can be mapped based on the first 50 rows.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__PD881_P2A.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample shows unstructured lines with embedded labels like "Name:", "Address:", "DOB:", etc. While there are potential PII indicators (names, phone numbers), the format does not conform to a structured table with consistent columns. Therefore, it is classified as unstructured text with embedded PII.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__PD881_P3.csv
1 rows

File structure

Notes: The provided data is free-form text with no consistent delimiter or column structure. The sample lines appear to be narrative entries from police reports or property logs, not a tabular dataset. There are no identifiable PII columns to map, and the format does not conform to a structured CSV/TSV format. The content includes text such as 'NORFOLK POLICE DEPARTMENT', 'Property is: Recovered', and 'Voucher 19359', indicating this is unstructured incident documentation.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__PD881_P4.csv
0 rows

File structure

Notes: The provided sample rows appear to be free-form text from a legal case report or police document. There are no consistent delimiters or column structures across the rows. The content includes case report headers and summary text, but no identifiable PII columns. This is unstructured prose, not a delimited dataset.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Start_Page.csv
1 rows

File structure

Notes: The file appears to be a free-form text file with no consistent delimiter structure. The sample rows contain form-like prompts and instructions rather than structured tabular data. While there are some embedded values that look like names and phone numbers, the lack of consistent column structure across rows means this should be processed as unstructured text.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__Subpoena.csv
0 rows

File structure

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

Notes: This is a legal subpoena document template with no structured personal data columns. The content consists of court names, case references, and placeholder text. No PII fields (email, phone, name, etc.) are present in any column. All columns are headers/placeholders for legal forms.

hallauerlaw.net__hallauerlaw.net_Felony_Folder__lists.csv
0 rows

File structure

Notes: This file is not a delimited dataset with personal information. It appears to be a template or lookup table for categories such as race, sex, marital status, vehicle makes, weapon types, offenses, etc. There are no actual personal records or PII values present in the sample rows. All columns appear to be codes, categories, or reference data, none of which map to PII fields. Therefore, no PII columns are identified.

hallauerlaw.net__hallauerlaw.net_Hayes_Accurint.csv
5 columns1 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Full Name', values are names like 'HAYES'
1genderhigh[1] header 'Gender', values are 'Male'
2ssnhigh[2] header 'SSN', values are SSN-like '231-65-1567'
3dobhigh[3] header 'DOB/Age', values are dates like '9/21/1988 (25)'
5address1high[5] header 'Address', values are address-like strings

Notes: 11 columns total, 5 contain PII. Other columns (DOD/Age at Death, Phone Information, Property, Motor Vehicle, People at Work, LexID) contain non-PII or internal data.

hallauerlaw.net__hallauerlaw.net_Hayes_Accurint_1.csv
5 columns1 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Full Name', values contain names and partial addresses but appear to be names
1genderhigh[1] header 'Gender', values include 'Male'
2ssnhigh[2] header 'SSN', values match SSN pattern (e.g., '231-65-1567')
3dobhigh[3] header 'DOB/Age', values include date '9/21/1988'
5address1high[5] header 'Address', values look like addresses (e.g., '3701 GRANBY ST')

Notes: 11 total columns, 5 contain PII. Other columns (DOD/Age at Death, Phone Information, Property, Motor Vehicle, People at Work, LexID) contain non-PII or internal identifiers.

hallauerlaw.net__hallauerlaw.net_Hubbert_Accurint.csv
7 columns7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamemedium[0] header 'Full Name', values contain last name strings despite corruption/misalignment
1genderlow[1] header 'Gender', but values appear to be names due to severe document-to-CSV misalignment
2ssnmedium[2] header 'SSN', values show 'None' but SSN data likely present in other rows
3dobmedium[3] header 'DOB/Age', sample value '153-74-7816' appears to be a misaligned SSN but header indicates DOB field
4dobmedium[4] header 'DOD/Age at Death', value '3/7/1982 (32)' looks like a date of birth/death — maps as dob
5address1medium[5] header 'Address', value '2647725688' may be misaligned phone but header indicates address
6phonemedium[6] header 'Phone Information', value fragment looks like an address due to misalignment but header indicates phone

Notes: Data is severely corrupted/misaligned, likely from PDF or formatted report converted to CSV. Column values do not match their headers due to document conversion artifacts. Headers used as primary mapping signal. Columns [7] Property, [8] Motor Vehicle, [9] People at Work, [10] Household Member, [11] LexID are non-PII categorical/reference fields and are skipped.

hallauerlaw.net__hallauerlaw.net_Hubbert_Accurint_1.csv
6 columns7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamemedium[0] header 'Full Name', values include 'WALTON', 'HUBBERT' — surname fragments consistent with fullName despite encoding corruption
3ssnhigh[3] header is 'DOB/Age' but value '153-74-7816' matches SSN pattern (###-##-####) — value-based detection overrides header
4dobmedium[4] header 'DOD/Age at Death', value '3/7/1982 (32)' contains a date of birth/death — closest mappable PII date field
5phonemedium[5] header 'Address' but value '2647725688' is a 10-digit number consistent with a phone number — value-based detection
6address1medium[6] header 'Phone Information' but value '1075 GROVE ST APT' is clearly a street address — value-based detection overrides header
7citymedium[7] header 'Property', value 'IRVINGTON' is a known NJ city name — value-based detection

Notes: Data is severely corrupted with encoding issues and column misalignment — values frequently do not match their headers. SSN found in DOB column, phone in Address column, street address in Phone column. Columns [1] Gender, [2] SSN, [8]-[11] had insufficient non-null/non-corrupt values to confidently map. LexID [11] is an internal identifier (skip).

hallauerlaw.net__hallauerlaw.net_Jackson_Accurint.csv
8 columns6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0lastNamemedium[0] header 'Full Name' but values show 'JACKSON' — surname fragments visible; data misalignment suspected
1firstNamehigh[1] header 'Gender' but values are 'BRIAN EUGENE', 'BRIAN E', 'BRIAN' — clearly given/middle name data
2genderhigh[2] header 'SSN' but values are 'Male', 'None' — clearly gender data
3ssnhigh[3] header 'DOB/Age' but values show '224-19-2738' — 9-digit SSN pattern
4dobhigh[4] header 'DOD/Age at Death' but values show '12/13/1977 (36)' — date of birth with age
5phonehigh[5] header 'Address' but values show '1217475463' — 10-digit phone number
6address1high[6] header 'Phone Information' but values show '2312 HIGHLAND FARM RD NW APT 22' — street address
7cityhigh[7] header 'Property' but values show 'ROANOKE' — city name

Notes: Severe column misalignment between headers and values throughout the file. All mappings are based on actual sample values rather than header names. Columns [8]-[11] (Motor Vehicle, People at Work, Household Member, LexID) have no sample values and their headers are non-PII categories — skipped. This file appears to be FBI/law enforcement records from the Hallauer Law breach containing suspect PII.

hallauerlaw.net__hallauerlaw.net_Jackson_Accurint_1.csv
8 columns6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamemedium[0] header 'Full Name', values include 'JACKSON' surname fragments; data appears row-shifted/corrupt but header intent is clear
1genderlow[1] header 'Gender', values show name fragments due to column shift; header declares gender field
2ssnmedium[2] header 'SSN'; values show 'Male' due to shift but SSN values (224-19-2738) appear in [3], indicating one-column right shift throughout
3dobmedium[3] header 'DOB/Age'; SSN-pattern value visible (shift artifact); DOB values visible in [4]
4dobmedium[4] header 'DOD/Age at Death'; values '12/13/1977 (36)' are clearly DOB dates shifted from [3]
5address1medium[5] header 'Address'; value '1217475463' appears to be a phone number shifted from [6]
6phonemedium[6] header 'Phone Information'; value shows address string shifted from [5]
7citylow[7] header 'Property'; values show 'ROANOKE' which is a city, likely address component shifted from [5]

Notes: Data is severely misaligned — values are shifted approximately one column to the right relative to headers, likely due to unescaped delimiters or corrupt export from a law enforcement/LexisNexis-style report. File contains highly sensitive PII for suspects/witnesses including SSN, DOB, addresses, phone numbers. Columns [8] People at Work, [9] Household Member, [10] Motor Vehicle may contain additional PII but no sample values were provided. LexID [11] is an internal identifier (skip).

hallauerlaw.net__hallauerlaw.net_Jennings_Accurint.csv
5 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Full Name', values are names
1genderhigh[1] header 'Gender', values are gender codes
2ssnhigh[2] header 'SSN', values match SSN pattern
3dobhigh[3] header 'DOB/Age', values match date pattern
5address1high[5] header 'Address', values are street addresses

Notes: Columns 4 (DOD/Age at Death), 6 (Phone Information), 7 (Property), 8 (Motor Vehicle), 9 (People at Work), 10 (Household Member), 11 (LexID) contain non-PII or ambiguous data and are skipped

hallauerlaw.net__hallauerlaw.net_Jennings_Accurint_1.csv
5 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Full Name', values appear to be names ("JACKSON", "VAà23225-6845 - (Jul 2004 - Jul 2014)" contains partial name JACKSON)
1genderlow[1] header 'Gender', values are cryptic but pattern suggests gender codes ("CECEILIA", "CECEILLE", "CECELIA", "RICHMOND")
2ssnhigh[2] header 'SSN', values match SSN pattern ("229-08-0856")
3dobhigh[3] header 'DOB/Age', values match date-like pattern ("1963 (51)")
5address1high[5] header 'Address', values are address-like ("6406 WINDCROFT RD")

Notes: 12 columns total, 5 contain PII. Columns 4 (DOD/Age at Death), 6 (Phone Information), 7 (Property), 8 (Motor Vehicle), 9 (People at Work), 10 (Household Member), and 11 (LexID) appear to be non-PII or internal identifiers and are skipped.

hallauerlaw.net__hallauerlaw.net_Linda_Hicks_T200081607__Deposits.csv
2 columns501 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
5fullNamehigh[5] header 'account_holder_name', values are full person names like 'lynda hicks'
9skiphigh[9] header 'e_wallet_email' indicates email address field

Notes: 12 columns total; transaction/payment records. Columns 0,1,2,3,4,6,7,8,10,11 are transactional/internal/IP data and are skipped. Column 5 contains account holder full names. Column 9 is an email field with no sample values but header clearly indicates email.

hallauerlaw.net__hallauerlaw.net_Linda_Hicks_T200081607__Withdrawals_System.csv
0 rows

File structure

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

Notes: All columns are internal transaction/payment identifiers, timestamps, and status flags. No PII fields present.

hallauerlaw.net__hallauerlaw.net_MSB_1D_Clean_List_for_Discovery_100516__MSB_Audio_Files.csv
1 column120 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4fullNamehigh[4] contains names in formats like 'A. WILLIAMS', 'W. MOORE', 'L. LAMB', 'A. BOONE', 'NICHOLAS JOHNSON', 'T. BROWN', 'A. GERALD', 'C. OWENS', 'D. WALKER', 'A. DAY', 'T. ORE', 'W. BURROUGHS', 'D. DAVID', 'M. DOVE', 'C. JENNINGS', 'L. HICKS', 'W. SEELEY', 'R. BELIN', 'R. PAGE', 'Christine Bailey', 'Nicholas Johnson', 'Steve Duenas', 'Carlos Williams', 'John Farr', 'Larry Boone', 'Gary Hack', 'Linda Leatherwood', 'Reginald Ball', 'Shonda Jones', 'Jaymese Jones', and nicknames like 'BREEZY', 'RED RUM', 'M STONE', 'DOUGH', 'TA TA', 'Q'

Notes: 50 rows analyzed; column 4 consistently contains full names (first initial + last name or full names), including nicknames and aliases, indicating it's the primary PII field for individuals referenced in surveillance/interception records

hallauerlaw.net__hallauerlaw.net_MSB_1D_Clean_List_for_Discovery__MSB_Audio_Files.csv
0 rows

File structure

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

Notes: This file is a log of audio/video interceptions with no PII fields present. The 'Primary Suspected Interceptees Include (May Include Others)' column contains only initials or nicknames (e.g., 'A. WILLIAMS', 'Q BANGA', 'BREEZY', 'RED RUM') and does not provide full names, addresses, or other identifiable information. No columns map to PII fields.

hallauerlaw.net__hallauerlaw.net_MSB_1D_Clean_List_for_Discovery__NF_and_RH_as_of_3.30.16___MSB_Audio_Files.csv
0 rows

File structure

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

Notes: File appears to be a log of intercepted communications (audio/video/texts) with no PII fields. Contains only case identifiers, dates, media types, and participant names that are fully anonymized using initials (e.g., A. WILLIAMS). No email addresses, phone numbers, SSNs, or other direct PII are present. Participant names are presented as initials or aliases only.

hallauerlaw.net__hallauerlaw.net_MSB_1D_Clean_List_for_Discovery__NF_and_RH_as_of_7.11.16___MSB_Audio_Files.csv
1 column141 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4fullNamehigh[4] contains full names or partial names (e.g., 'A. WILLIAMS', 'W. MOORE', 'L. BOONE', 'NICHOLAS JOHNSON'). Values include initials and surnames, some with nicknames like 'BREEZY' and 'RED RUM', consistent with full name format in law enforcement contexts

Notes: The file appears to be a log of intercepted communications (audio/video/texts) from a law enforcement operation. Column 4 contains personal full names or partial names of intercepted individuals. All other columns contain operational metadata (dates, locations, media types) and are non-PII. No emails, phone numbers, DOBs, or other PII fields are present in the sample.

hallauerlaw.net__hallauerlaw.net_MSB_1D_Clean_List_for_Discovery__NF_and_RH_as_of_8.9.16___MSB_Audio_Files.csv
1 column140 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4fullNamehigh[4] contains abbreviated names like 'A. WILLIAMS', 'W. MOORE', and full names like 'NICHOLAS JOHNSON', matching fullName pattern

Notes: Only column 4 contains PII (fullName). Other columns are headers/metadata (division, date, media type, review status) and do not contain personal information.

hallauerlaw.net__hallauerlaw.net_MSB_1D_Clean_List_for_Discovery__NF_as_of_10.6.16___MSB_Audio_Files.csv
0 rows

File structure

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

Notes: No PII columns identified. The file contains structured records of surveillance/interception metadata (IDs, dates, audio/video flags, participant names in abbreviated forms like 'A. WILLIAMS'), but all names appear to be aliases, initials, or codenames rather than full personal identifiers. No emails, phone numbers, addresses, DOBs, SSNs, etc., are present. The 'Primary Suspected Interceptees Include' column contains partial names which do not constitute full PII per policy. All columns fall under skip categories (internal IDs, flags, timestamps, counters, or non-personal identifiers).

hallauerlaw.net__hallauerlaw.net_MSB_1D_Clean_List_for_Discovery__NF_as_of_4.2017___MSB_Audio_Files.csv
1 column158 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4fullNamehigh[4] contains abbreviated names with initials and full names (e.g., A. WILLIAMS, W. MOORE, J. STRINGER, NICHOLAS JOHNSON)
hallauerlaw.net__hallauerlaw.net_MSB_1D_List__November_2016___MSB_Audio_Files.csv
6 columns165 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighinternal ID pattern '1D#'
3dobhighcolumn contains ISO date timestamps
4skiphighcontains notes/status flags like 'Telephone Interception(s)'
5skiphighcontains interviewer names or status flags
6skiphighcontains file references like 'Norfolk 302 file, serial 44'
7fullNamehighcontains person names in format 'S-47220, A. WILLIAMS' or 'S-52483, C. OWENS, W. MOORE'

Notes: 50 rows analyzed. Column 7 contains full names (last, first) in standard format. Column 3 contains timestamps. Columns 4-6 contain status notes and file references, not PII. Column 0 is an internal ID pattern.

hallauerlaw.net__hallauerlaw.net_MSB_1D_s_List_1__MSB_Audio_Files.csv
2 columns112 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
5fullNamehigh[5] values are comma-separated lists of full names like 'A. WILLIAMS', 'W. MOORE', 'J. STRINGER'
7fullNamehigh[7] values are comma-separated lists of full names like 'S-47220, A. WILLIAMS', 'S-47220, A. WILLIAMS, W. MOORE'

Notes: CSV file with 115 rows and 8 columns. Only columns 5 and 7 contain PII (fullName). All other columns are status flags, timestamps, or internal case identifiers.

hallauerlaw.net__hallauerlaw.net_MSB_1D_s_List_2__MSB_Audio_Files.csv
8 columns137 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphigh[0] internal case ID '1D#'
2skiphigh[2] header 'SERIALIZED' - internal tracking code
3dobhigh[3] header 'DATE(S) OF INTERCEPTION', values are ISO timestamps
4skiphigh[4] header 'NOTES' - free text field
5skiphigh[5] header 'SUMMARIZER' - analyst name, not PII
6skiphigh[6] header 'SERIAL' - internal reference number
7fullNamehigh[7] header 'Primary Interceptees (Suspected)', values contain full names like 'A. WILLIAMS', 'LARRY BOONE', etc.
8skiphigh[8] header 'REVIEWED?' - status flag

Notes: 50 rows analyzed. Columns 0,2,4,5,6,8 are non-PII (internal IDs, timestamps, free text, status). Column 7 contains full names in intercept logs. No email/phone/dob/address fields visible in this sample.

hallauerlaw.net__hallauerlaw.net_MSB_1D_s_List_3__MSB_Audio_Files.csv
8 columns143 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiplow[0] header '1D #' contains internal case identifiers, not PII
2skiphigh[2] header 'SERIALIZED' indicates internal tracking code, not PII
3dobhigh[3] header 'DATE(S) OF INTERCEPTION', values are ISO 8601 timestamps or date ranges
4skiphigh[4] header 'NOTES' contains free-text case notes, not structured PII
5skiphigh[5] header 'SUMMARIZER' indicates analyst name, not subject PII
6skiphigh[6] header 'SERIAL' indicates internal case number, not PII
7fullNamehigh[7] header 'Primary Interceptees (Suspected)', values contain full names like 'A. WILLIAMS', 'LARRY BOONE', etc.
8skiphigh[8] header 'REVIEWED?' is a status flag, not PII

Notes: 50 rows analyzed. File contains law enforcement case logs with timestamps, internal case IDs, analyst notes, and names of intercepted individuals. Only timestamps (dob) and full names (fullName) qualify as PII. All other columns are internal tracking or status information.

hallauerlaw.net__hallauerlaw.net_MSB_1D_s_List_4__MSB_Audio_Files.csv
2 columns81 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
5fullNamehigh[5] contains structured names like 'A. WILLIAMS' and aliases like 'LIPP' in quotes
9fullNamehigh[9] lists suspects with names like 'A. WILLIAMS', 'W. MOORE', and aliases like 'LIPP'

Notes: 50 rows of surveillance/intercept records. Only columns 5 and 9 contain structured personal names (fullName). All other columns are case identifiers, statuses, dates, notes, and internal codes — no PII beyond names.

hallauerlaw.net__hallauerlaw.net_MSB_1D_s_List_5__MSB_Audio_Files.csv
3 columns32 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphigh[0] internal ID pattern '1D#'
2fullNamehigh[2] values contain structured names like 'A. WILLIAMS', 'LARRY BOONE', 'M. PITTMAN', etc. Header 'Primary Interceptees (Suspected)' indicates personal names
3skiphigh[3] boolean flag 'REVIEWED?' (Yes/No)

Notes: 50 rows show structured law enforcement intercept logs. Column 2 contains concatenated suspect names in 'First. Last' format. All other columns are case metadata or flags.

hallauerlaw.net__hallauerlaw.net_MSB_1D_s_List__MSB_Audio_Files.csv
3 columns122 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighInternal case identifiers (1D#) not PII
5fullNamehighColumn contains full names extracted from intercepts (e.g., 'A. WILLIAMS', 'LARRY BOONE', 'C. OWENS')
7fullNamehighContains additional full names from intercept summaries (e.g., 'L. LAMB', 'AJANAI BOONE', 'DIMITRIOUS DAVID')

Notes: 50 rows analyzed from law enforcement intercept logs. Only columns containing extracted full names from surveillance targets were mapped as PII. All other columns contain case metadata, timestamps, and status flags not personally identifiable.

hallauerlaw.net__hallauerlaw.net_MSB_Code_Compilation__Sheet1.csv
0 rows

File structure

Notes: The file contains thematic phrases and explanations rather than structured personal data. It does not contain importable columns with PII fields.

hallauerlaw.net__hallauerlaw.net_MSB_Code_Compilation_v_3_February_2015__Sheet1.csv
0 rows

File structure

Notes: Free-form text with no consistent column structure. Contains code/meaning pairs and code group classifications, but no structured PII columns. Contains embedded references but not in tabular format.

hallauerlaw.net__hallauerlaw.net_MSB_ConNarcoPurchases__Sheet1.csv
0 rows

File structure

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

Notes: This is a structured CSV file with headers, but none of the columns map to PII fields. The data contains operational details about controlled purchases, locations, substances, and involved parties, but no identifiable personal information such as names, addresses, emails, phone numbers, or other PII is present in a structured column format. All entries are operational codes, locations, and narrative summaries.

hallauerlaw.net__hallauerlaw.net_MSB_ELSUR_Available_in_U.S.A.O._as_of_December_5_2016__MSB_Audio_Files.csv
4 columns166 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighInternal case identifier (1D#)
3dobhighColumn contains ISO 8601 timestamps that match recorded interception dates
5fullNamehighContains interviewer names in structured format (e.g., C. BAILEY, N. JOHNSON)
7fullNamehighContains intercepted participant names in quotes and standard format (e.g., "A. WILLIAMS", "L. LAMB", "TA TA")

Notes: 50 rows analyzed; 4 columns contain PII. Columns 0, 1, 2, 4, 6 contain internal case metadata, status flags, or empty values. Columns 3 (dates) and 5-7 (names) contain structured PII. The file appears to be a log of law enforcement surveillance operations with timestamps and participant lists.

hallauerlaw.net__hallauerlaw.net_Main_Case_File_TOC_245D-NF-39124__as_of_7-27-17___Sheet1.csv
0 rows

File structure

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

Notes: This is not structured data. The file appears to be a list of case/folder descriptions with no consistent columnar format. Each row contains a case serial number and a description string, but there are no repeating field positions or delimiters separating distinct data elements. Therefore, it is unstructured text and should be processed accordingly.

hallauerlaw.net__hallauerlaw.net_Main_Case_File_Table_of_Contents_245D-NF-39124__Sheet1.csv
1 column0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
132skiphigh[132] contains phone number '757-966-9380'

Notes: Only column 132 contains a phone number in the format '757-966-9380'. All other columns appear to be administrative descriptions or file references with no PII. No other columns contain email addresses, names, dates of birth, or other PII fields.

hallauerlaw.net__hallauerlaw.net_Main_Case_File_Table_of_Contents_245D-NF-39124__as_of_10.14.16___Sheet1.csv
0 rows

File structure

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

Notes: The provided file is purely administrative case tracking with serial numbers and descriptions. All rows are headerless metadata documenting case identifiers (Serial, Description, RH Serial) and administrative actions. There are no personal data fields, identifiers, or PII present in any of the first 50 rows. The content consists of operational codes (e.g., 'S-00036927-A-021'), case types ('Admin', 'ELSUR', 'FISUR'), and procedural notes — none contain names, addresses, contact details, or other personally identifiable information. No columns map to PII fields.

hallauerlaw.net__hallauerlaw.net_Main_Case_File_Table_of_Contents_245D-NF-39124__as_of_11.3.15___Sheet1.csv
0 rows

File structure

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

Notes: The file appears to be a list of document descriptions and administrative records with no structured columnar data containing PII. All entries are free-text descriptions of case files, admin actions, and investigative notes. No consistent delimiter structure or identifiable PII fields are present in the first 50 rows.

hallauerlaw.net__hallauerlaw.net_Main_Case_File_Table_of_Contents_245D-NF-39124__as_of_2.2.16___Sheet1.csv
0 rows

File structure

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

Notes: The file contains administrative and operational notes from a law enforcement investigation. All entries are structured as free-form text descriptions with no consistent columnar data or PII fields. There are no delimited records containing personal information such as names, addresses, emails, or phone numbers.

hallauerlaw.net__hallauerlaw.net_Main_Case_File_Table_of_Contents_245D-NF-39124__as_of_3.31.16___Sheet1.csv
0 rows

File structure

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

Notes: The file is a structured CSV with two columns (Serial, Description, RH Serial). However, the data consists entirely of administrative codes, file references, and operational notes with no personal identifying information. All entries are internal case identifiers, document types, and administrative actions. No email addresses, phone numbers, names, dates of birth, or other PII appear in the first 50 rows. Therefore, no PII columns can be mapped.

hallauerlaw.net__hallauerlaw.net_Main_Case_File_Table_of_Contents_245D-NF-39124__as_of_4.3.17___Sheet1.csv
0 rows

File structure

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

Notes: The file appears to be a list of administrative and case document references rather than structured tabular data. Columns contain document identifiers, descriptions, and serial numbers with no consistent PII fields across rows. No email addresses, phone numbers, names, or other PII appear in the visible sample.

hallauerlaw.net__hallauerlaw.net_Main_Case_File_Table_of_Contents_245D-NF-39124__as_of_7.11.16___Sheet1.csv
0 rows

File structure

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

Notes: The file appears to be a structured list of document references and administrative entries, not containing any actual PII data. All entries are document identifiers, descriptions, and administrative actions without personal information such as names, addresses, or contact details. No columns map to PII fields.

hallauerlaw.net__hallauerlaw.net_Main_Case_File_Table_of_Contents_245D-NF-39124__as_of_7.27.17___Sheet1.csv
0 rows

File structure

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

Notes: File appears to be a structured record list with serial numbers and descriptions. No PII fields detected in the first 50 rows. Columns contain administrative codes, case identifiers (e.g., S-00036927-A-021), and operational notes, but no personal identifiers like names, addresses, or contact details. All visible data is case metadata or internal references.

hallauerlaw.net__hallauerlaw.net_Main_Case_File_Table_of_Contents_245D-NF-39124__as_of_8.9.16___Sheet1.csv
0 rows

File structure

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

Notes: The provided data is a structured table with columns 'Serial', 'Description', and 'RH Serial'. None of the visible values or headers correspond to any PII fields (email, phone, dob, etc.). The content appears to be administrative codes, case identifiers, and operational notes from a law enforcement context. No PII is present in the first 50 rows.

hallauerlaw.net__hallauerlaw.net_NYGJSubpoena_Store_3653_10-5-16__Results.csv
7 columns1 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4fullNamehigh[4] header 'CUSTOMER_NAME', values are full names like 'BEV SMITH'
7phonehigh[7] header 'PHONE_NUMBER', values are 10-digit numbers
8address1high[8] header 'STREET_NUMBER', paired with street name in next column
9address1high[9] header 'STREET_NAME', values are street names like 'PRESIDENT ST'
10ziphigh[10] header 'POSTAL_CODE', values are 5-digit zip codes
11cityhigh[11] header 'CITY_NAME', values are city names like 'BROOKLYN'
12statehigh[12] header 'REGION_NAME', values are state names like 'NEW YORK'

Notes: 14 columns total, 7 contain PII (fullName, phone, address1 x2, zip, city, state). All other columns are internal IDs, timestamps, or transactional data and are skipped per rules.

hallauerlaw.net__hallauerlaw.net_NYGJSubpoena_Store_3653_10-5-16__SQL.csv
0 rows

File structure

Notes: This is a SQL query fragment (not a data file). It contains no structured records with PII columns, only SQL syntax and placeholder comments. The file is unstructured SQL code, not a delimited data export.

hallauerlaw.net__hallauerlaw.net_Securus_Call_Log_Burroughs__Results1.csv
3 columns52 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4phonehigh[4] header 'Dialed#', values are 10-digit US phone numbers
12firstNamehigh[12] header 'First Name', values are all caps first names
13lastNamehigh[13] header 'Last Name', values are all caps surnames

Notes: This is a phone call detail record (CDR) file from Hallauer Law's surveillance system. Only firstName, lastName, and phone are PII. All other columns are call metadata, status flags, or internal tracking codes.

hallauerlaw.net__hallauerlaw.net_Securus_Call_Log_Burroughs__Summary.csv
0 rows

File structure

Notes: This is a free-form report with no consistent columnar structure. The data appears to be a call detail report summary from a phone monitoring system, showing aggregate statistics rather than individual records. There are no structured columns containing PII fields.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_010116-033116__Page1_1.csv
0 rows

File structure

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

Notes: No PII columns detected. This appears to be a casino gaming transaction log with financial/balance data (deposits, wagers, loyalty points, game product info). All columns are transactional, financial, or internal system fields — none contain personal identifiable information such as names, emails, phones, addresses, DOB, SSN, or similar PII.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_010116-033116__Page1_2.csv
0 rows

File structure

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

Notes: This file contains casino gaming transaction logs (wagers, credits, balances) for what appears to be an online gambling platform. The first row appears to be a user/account ID (200081607) but the remaining columns are all financial/transactional data: activity timestamps, game references, site names, transaction types, and various balance fields (real money, loyalty points, gift, bonus). No PII fields such as name, email, phone, address, DOB, or SSN are present in this sample. All columns are non-PII transactional/financial records and should be skipped.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_2015__Page1_1.csv
0 rows

File structure

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

Notes: This file contains casino gaming transaction logs (deposits, wagers, balances) with no PII columns. The data includes transaction timestamps, game references, site names, transaction types, and various balance fields — all financial/transactional internal records. No names, emails, phones, addresses, SSNs, or other PII are present.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_Aug_2016__Page1_1.csv
0 rows

File structure

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

Notes: This file contains gambling transaction records from Tropicana Casino (NJ) with no personal identifiable information. Columns represent internal gaming activity metrics like timestamps, transaction types, balances, and loyalty points. All values are numeric codes, monetary amounts, or generic strings with no names, addresses, emails, or other PII. The reference number (908977401) appears to be an internal transaction ID, not a personal identifier.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_Aug_2016__Page1_2.csv
0 rows

File structure

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

Notes: No PII columns detected. All columns are internal transactional data (activity timestamps, reference IDs, casino site, game product, bank types, transaction descriptions, balances). These are financial/tracking fields excluded by rules.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_Jan_2017__Page1_1.csv
0 rows

File structure

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

Notes: This file contains transactional gaming data from Tropicana Casino (NJ) with timestamps, reference IDs, and balance information. No PII fields are present — all columns are internal IDs, timestamps, or financial/balance counters. Columns 0-1 appear to be numeric identifiers, 2 is a location name, 3-13 are gaming transaction metadata and balances. None map to any PII categories.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_Jan_2017__Page1_2.csv
0 rows

File structure

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

Notes: This is transactional/gambling data from Tropicana Casino (NJ) with no PII fields. Columns represent activity timestamps, reference IDs, financial balances (unconstrained, constrained, bonus, loyalty, gift, withheld, PGC), and game/product metadata. All columns are internal transactional identifiers, balances, or system metadata — none contain names, emails, phone numbers, addresses, DOB, SSN, or other PII. The data appears to be casino gaming logs (wager/credit activity) with no personally identifiable information exposed in the first 50 rows.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_July_2016__Page1_1.csv
0 rows

File structure

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

Notes: This file contains online casino transaction logs (wagers, credits, balances, loyalty points) for what appears to be a Tropicana Casino account. The true column headers are embedded in the first data row. No PII fields are present — all columns are internal transaction identifiers, timestamps, game/product names, transaction types, and financial balances, all of which are skip fields.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_July_2016__Page1_2.csv
0 rows

File structure

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

Notes: No PII columns detected. All columns are internal identifiers, timestamps, or transactional/financial data (balances, loyalty points, etc.). Column 0 appears to be an internal record ID, column 1 is a reference number, and columns 2-13 are gaming/transaction metadata. None map to email, phone, name, address, DOB, SSN, or other PII fields.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_Nov_2016__Page1_1.csv
0 rows

File structure

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

Notes: All columns represent transactional/gaming data (activity timestamps, reference IDs, casino site, game product, bank types, transaction descriptions, monetary balances). No PII fields present. Columns 0-13 are internal identifiers, timestamps, and financial balances — all skip per exclusion rules.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_Nov_2016__Page1_2.csv
0 rows

File structure

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

Notes: This file appears to be transactional/gaming data with no PII fields. Columns contain activity timestamps, reference IDs, casino site names, game product identifiers, financial transaction types and balances, loyalty points, and other internal accounting values. No personal identifiers such as names, emails, phone numbers, addresses, or dates of birth are present in the sample rows.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_Oct_2016__Page1_1.csv
0 rows

File structure

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

Notes: This file contains only internal transaction and loyalty data (activity times, reference numbers, casino site, game product, bank types, transaction descriptions, balances). No PII fields are present. All columns are skipped per exclusion rules for internal IDs, financial/transactional data, and timestamps.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_Sept_2016__Page1_1.csv
0 rows

File structure

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

Notes: All columns are internal transactional data (activity timestamps, reference IDs, casino site, game product, bank types, transaction types, monetary amounts, balances). No PII fields present. Columns 0-1 contain numeric codes/timestamps, 2-4 are venue/product descriptors, 5-13 are financial balances/points — all skip per exclusion rules (transactional/financial data).

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_PAH_Sept_2016__Page1_2.csv
0 rows

File structure

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

Notes: All columns represent transactional/gambling data (activity times, reference IDs, casino site, game product, bank types, transaction types, balances). No PII fields present — columns contain internal IDs, timestamps, financial balances, and loyalty points which must be skipped per rules. The 'Reference' column appears to be numeric identifiers, not phone numbers or emails.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_deposit_histories_Mon-Mar-06-21-47-06-2017__Excel_export.csv
2 columns501 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
5fullNamehigh[5] header 'account_holder_name', values are full person names like 'lynda hicks'
9skiphigh[9] header 'e_wallet_email', column name contains 'email'

Notes: 12 columns total; most are financial/transactional (transaction_id, amount, status, created, payment_method_type, payment_method_id, payment_provider_name, payment_provider_account_id, voucher_code) or network identifiers (user_ip) — all skipped. Column 9 (e_wallet_email) has no sample values but the column name clearly indicates email. Column 5 contains account holder full names.

hallauerlaw.net__hallauerlaw.net_T200081607_Hicks_withdrawal_histories_Mon-Mar-06-21-48-48-2017__Excel_export.csv
0 rows

File structure

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

Notes: All columns represent transactional/financial data (transaction IDs, amounts, timestamps, payment details) with no personal identifiable information. Columns like transaction_id, pay_method_id, timestamps, and payment references are internal identifiers and financial metadata. No PII fields present.

hallauerlaw.net__hallauerlaw.net_VABCHphone__Sheet1.csv
11 columns13 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0firstNamehigh[0] header 'FRST_NM' (first name abbreviation), values are given names like 'KATIE'
1middleNamehigh[1] header 'MI' (middle initial), standard abbreviation for middle name/initial
2lastNamehigh[2] header 'LAST_NM' (last name abbreviation), values are surnames
3suffixhigh[3] header 'SFX' (suffix abbreviation), generational/credential suffix field
4address1high[4] header 'ADDR_LINE1' matches address1 pattern, values are street addresses like '3024 REYNOLDS ST'
5address2high[5] header 'ADDR_LINE2' matches address2 pattern
6cityhigh[6] header 'CITY', values are city names like 'BRUNSWICK'
8statehigh[8] header 'ST_CD' (state code), values are US state abbreviations like 'GA'
9ziphigh[9] header 'PSTL_CD' (postal code), values are 5-digit ZIP codes like '31520'
10countryhigh[10] header 'CNTRY_CD' (country code), values are country codes like 'US'
16phonehigh[16] header 'PHONE', values are formatted US phone numbers like '(929) 363-3371'

Notes: 29 columns total, 11 contain PII. Columns 7 (COUNTY), 11 (tax flag), 12-15 (internal IDs/codes), 17 (phone extension - empty), 18-27 (transaction/sales data), 28 (card account number - financial instrument ID, not mapped as standard PII field) are skipped. Note: column 28 CARDHLDR_ACCT_NBR contains payment card numbers which are sensitive financial data but fall outside the available PII field types.

hallauerlaw.net__hallauerlaw.net_VDOC_ELSUR_List__as_of_3.30.16___Sheet1.csv
2 columns11 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] values contain full names like 'Arrington, Javon' and 'Ball, Reginald'. Header 'Name or Number' suggests this field holds either a name or a phone number, and the sample shows names.
1usernamehigh[1] values like 'VDOC' and 'Appalachian D.C.' are likely identifiers or usernames used in the dataset.

Notes: The file appears to be a structured CSV containing call records with names and identifiers. Only columns 0 and 1 contain PII. Column 0 contains full names, and column 1 contains usernames or organizational identifiers.

hallauerlaw.net__hallauerlaw.net_Virginia_DOC_record_jail_calls_on_discs__MSB_Jail_House_Calls.csv
0 rows

File structure

Notes: This is free-form text with embedded phone numbers and identifiers, not a structured CSV. No consistent delimiter or column structure exists across lines. Contains phone numbers (e.g., 2768730371, 276-873-0093) and internal IDs (#1421147, #106949427, etc.), but lacks a tabular format suitable for column mapping.

hallauerlaw.net__hallauerlaw.net_WILLIAMS_and_ARRINGTON__state_case__Electronic_Discovery-TOC__MSB_ELECTRONIC_DISC..csv
0 rows

File structure

Notes: This is a free-form text file listing case documents and metadata rather than structured records. No consistent delimiter exists across lines, and each line has a different shape. Contains embedded names but no structured PII columns.

hallauerlaw.net__hallauerlaw.net_bill_timeline_events_2021-12-28_11-36-14.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; contains timestamps and legal workflow notes, not structured PII

hallauerlaw.net__hallauerlaw.net_manifest_1__Sheet1.csv
0 rows

File structure

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

Notes: This file is a manifest of documents from a law firm breach. It contains metadata about documents (serial numbers, types, dates, classifications, titles, descriptions, and attachment flags). There are no PII fields present in this structured data. The content appears to be about gang investigations, database checks, and administrative subpoenas, but no personal identifiers are included in the visible columns.

hallauerlaw.net__hallauerlaw.net_manifest_2__Sheet1.csv
0 rows

File structure

Notes: The provided text is free-form narrative interview records with no consistent delimiter structure. Each line contains prose descriptions with embedded PII (name, DOB, SSN). This qualifies as unstructured data per rules: no shared delimiter, variable line shapes, and visible PII in free text.

hallauerlaw.net__hallauerlaw.net_manifest__Sheet1.csv
0 rows

File structure

Notes: free-form text with embedded PII in interview records