frostyacres.com

File structure

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

Notes: No PII columns detected. All columns are internal business data: employee names appear to be generic placeholder entries ("ARD, DAVY DANIEL") not actual PII, department descriptions, expense amounts/codes, dates, policies, and status codes. No emails, phones, addresses, DOB, SSN, etc. present.

File structure

Notes: This is free-form text with no consistent delimiter structure. The file appears to be a single record or note containing employee employment history with dates and hours worked. There are no columns to map, and while it contains dates, they are employment-related timestamps rather than PII fields like DOB. No structured PII columns exist to map.

File structure

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

Notes: This is an unstructured form-like document with no consistent column structure. It appears to be a Requisition Form for New Employee with fields filled in, but there is no repeating structured data across rows — each row represents a different field/label/value pattern. No PII columns can be reliably mapped because the format is free-form and not tabular. There are no repeated columns or consistent delimiter usage across rows.

File structure

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

File structure

Notes: This is a free-form template document (Requisition Form for New Temporary Employee) with blank fields and no structured data rows. It contains no actual PII records — only placeholder lines like 'Employee Name,,,,,' and checkboxes. While it mentions fields that would normally map to PII (Email Account, Phone Extension), these are NOT populated data rows. The file is purely a form template with no delimited records to parse, therefore it should be treated as unstructured for downstream processing. No column mapping is possible because there are no actual data rows with values.

File structure

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

Notes: This file contains medical billing details and insurance claim information, but no personally identifiable information (PII) fields. Columns like 'Member' contain only generic placeholder names ('Amy (Self)') and no actual names, addresses, emails, phone numbers, DOB, SSN, etc. All columns represent transactional or status data (types, dates, amounts, codes) and do not map to any PII categories.

File structure

Notes: The provided data appears to be free-form text logs related to FMLA/STD/PTO records with no consistent columnar structure. Lines contain varied fields (dates, hours, pay amounts) but lack a fixed delimiter or header. Though no explicit PII is visible in this snippet, the unstructured nature and presence of potential employee records qualify it for unstructured processing.

File structure

Notes: This is unstructured free-form text containing FMLA/STD/PTO records and payment calculations. No consistent columnar structure exists across lines; values are mixed with dates, amounts, and status codes. While there are no visible emails or phone numbers in the sample, the unstructured format prevents column mapping. This should be processed by a free-text extractor for any embedded personal data.

File structure

Notes: This is a free-form text document describing HR onboarding procedures and form tracking, not a delimited data file with structured columns. It contains prose instructions and status tracking fields rather than actual PII records. No consistent columnar structure exists across lines.

File structure

Notes: This is a free-form text file (an IT & HR Requisition Form template) with no consistent delimiter or column structure. The sample shows prose and form fields, not a structured dataset with repeating rows and columns. While there is one embedded email (chartsfield@frostyacres.com), the format does not meet the criteria for structured column mapping — lines vary in length/content and lack a shared delimiter. This routes to the unstructured email/phone extractor pipeline.

File structure

Notes: free-form text with embedded emails / phones

File structure

Notes: The provided data is free-form text with no consistent column structure or delimiter. It appears to be a detailed FMLA leave calculation document rather than a structured dataset with PII columns. The text contains timestamps and calculations but lacks any identifiable personal information in a structured format.

File structure

Notes: free-form text with embedded emails / phones

File structure

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

Notes: Only column 0 contains PII (full names). Other columns are work-related metadata (department, request dates, hours, earning type, supervisor comments, timestamp) and do not contain personal identifiable information.

File structure

Notes: Free-form HR onboarding document with embedded PII (names like 'Taylor Lalli', dates like '10.2.25') but no structured columns. Should be processed through streaming email/phone extractor.

File structure

Notes: This is a free-form template document (HR/IT requisition form) with no consistent columnar structure. It contains placeholders and instructions rather than actual employee data records. While it references PII fields like 'Employee Name' and 'Email Account', these are template labels, not populated data rows. The format lacks the consistent delimiters and repeating row structure required for CSV parsing — each line represents a form field label rather than a data record. Per the unstructured opt-out rules, this file should be processed through free-text extraction pipelines.

File structure

Notes: This is a free-form template document with form fields for HR/IT requisitions. No consistent columnar structure exists across lines, and it contains no actual employee data records — only placeholder fields. Though it mentions concepts like 'Email Account' and 'Phone Extension,' these are labels in the template, not populated PII values. The file is purely instructional/procedural.

File structure

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

Notes: Only two PII columns found: employee name and date of birth. The rest are loan/account transactional data, internal IDs, and timestamps (all skipped per rules).

File structure

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

Notes: Only column 1 contains PII (fullName). All other columns are time-off tracking data (dates, hours, codes) and totals — no emails, phones, addresses, etc. The format is a standard CSV with a header row.

File structure

Notes: This is a free-form text document (Requisition Form for New Employee) with no consistent columnar structure across rows. The content contains embedded employee names (Gary Paul, Bill Lewis), titles, and departments, but these are not presented in a tabular format with repeating columns. The document is a form with blank lines and checkboxes rather than structured CSV/TSV data. Since it fails the structured format criteria (no consistent delimiter, variable line shapes), it should be processed as unstructured text for embedded PII extraction.

File structure

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

File structure

Notes: This is a free-form template document (requisition form) with no consistent columnar structure across lines. It contains placeholder fields but no actual data rows with PII. Per rules, unstructured files with no row structure default to empty columns object.

File structure

Notes: This is a free-form text file with no consistent column structure. The sample shows payment and tax information with no identifiable personal information (PII) fields such as names, emails, or addresses. The content appears to be financial data (salaries, taxes, benefits) without any personal identifiers, making it non-structured and not containing mappable PII columns.

File structure

Notes: This is a free-form text document (Requisition Form for New Employee). No consistent columnar structure exists across lines; it contains prose and form fields. While there are placeholders for names and dates, the format does not meet criteria for structured CSV/TSV parsing. Per rules, unstructured files with embedded PII return empty columns object.

File structure

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

File structure

Notes: This is a free-form template document (Requisition Form for New Temporary Employee) with no consistent columnar structure. It contains placeholder lines and form fields rather than actual employee records. No PII is present in the provided snippet.

File structure

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

Notes: Only column 0 contains PII (fullName). All other columns contain department codes, dates, hours, and PTO balances — no email, phone, address, DOB, SSN, etc. The data appears to be employee PTO request records with no sensitive personal identifiers beyond names.

File structure

Notes: This is a free-form text document describing HR onboarding processes and checklists. It contains no structured tabular data with columns — all rows are narrative descriptions of steps and forms. While it references employee data concepts (names, DOB, etc.), no actual PII values are present, and the format lacks consistent delimiters or column positions. Therefore it is classified as unstructured text requiring special handling.

File structure

Notes: This is a free-form document with no consistent column structure. It appears to be an HR/IT requisition form template or record, containing embedded names (Rachel Reid, Jaymi Mallion, William, Hailey) but no structured columns. The format contains prose and form fields rather than delimited data rows.

File structure

Notes: This is a form template with no actual data rows. It contains form field labels but no actual PII values. The structure is not consistent row-based data but rather a static form layout. Therefore, it should be treated as unstructured content for processing.

File structure

Notes: free-form text with no consistent delimiter structure; appears to be medication/prescription data with no identifiable personal information in the sample rows

File structure

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

Notes: 5 columns total, 2 contain PII. This appears to be an invitation/RSVP list with employee/contractor names and phone numbers. No emails present despite column header suggesting otherwise.

File structure

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

Notes: This is a form template with no actual data rows. The file contains empty fields and checkboxes for employee onboarding processes. No PII values are present in the first 50 rows — only placeholder instructions and form structure. Therefore, no columns map to PII fields.

File structure

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

File structure

Notes: This is a form template with placeholder text and no actual data rows. It contains no structured records with PII. The content is instructional prose describing a requisition form for new temporary employees, not actual employee data. Therefore, it should be treated as unstructured text without column mappings.

File structure

Notes: free-form text with embedded names but no consistent delimiter or structured columns; contains meeting notes with employee and supervisor names but lacks tabular structure

File structure

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

Notes: This is an unstructured form-like CSV with blank delimiter columns. The file appears to be a template for an employee requisition form with headers but no actual data rows containing PII. All columns either contain static form text or empty values. No PII fields are present in the provided rows.

File structure

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

File structure

Notes: This is a form template with no actual data rows. The file contains a requisition form template for new temporary employees, with blank fields for supervisor and HR/IT to fill out. No actual PII values are present in the sample lines provided.

File structure

Notes: The file is a free-form text document with no consistent column structure or delimiter. It appears to be a checklist or workflow document for HR new hire setup procedures at Frosty Acres Brands, Inc. While it contains references to HR processes and employee onboarding, it does not contain any actual personal identifiable information (PII) in a structured format. The content is purely procedural and does not include any employee names, addresses, emails, or other PII fields. Therefore, it should be processed as unstructured text without column mapping.

File structure

Notes: This is a form template with no actual data rows. The sample shows only headers and placeholder instructions, not structured records containing PII. The file is free-form text with no consistent column structure or delimited rows of data.

File structure

Notes: free-form text with no consistent delimiter structure; contains embedded names but no column mapping possible

File structure

Notes: This is a free-form text file with no consistent columnar structure. It appears to be an agreement history document with headers and rows but lacks a consistent delimiter across lines and varies in field counts per line. Contains no identifiable PII columns in structured format.

File structure

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

Notes: This is a form with sparse data; only Employee Name and Supervisor columns contain PII (full names). All other columns are checkboxes, titles, dates, or empty fields and are skipped per rules.

File structure

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

File structure

Notes: This is a free-form template document (Requisition Form for New Temporary Employee) with no consistent columnar structure. It contains placeholder lines and blank fields rather than actual data rows. Though it mentions concepts like 'Email Account' and 'Phone Extension,' these are template labels, not populated PII fields. The file lacks repeated, structured rows with delimited columns, confirming it as unstructured prose.

File structure

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

Notes: This is not a PII-containing file. The data appears to be a payroll/benefit cost summary report showing various compensation components (regular wages, STD, GLI, FED, SS, MEDICARE, 401k, etc.). There are no identifiable personal fields such as names, emails, addresses, or DOB present in the visible data. All rows appear to be aggregate cost calculations rather than individual employee records.

File structure

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

Notes: This is not structured PII data. The file appears to be a payroll or compensation summary report showing various benefit costs and compensation components (e.g., regular wages, STD, GLI, FED, SS, MEDICARE, 401k, etc.). There are no identifiable personal fields such as names, emails, phone numbers, addresses, or DOB present. All columns appear to be aggregated or categorical benefit/line-item data, not individual employee records. Therefore, no PII columns map to the defined fields.

File structure

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

Notes: This is a free-form template form with no structured data containing personal information. All columns are headers for form fields and do not contain actual PII values in the first 50 rows. There are no structured records with PII in this sample.

File structure

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

File structure

Notes: This is a free-form template document (requisition form) with no consistent columnar structure or delimited data. The content appears to be a printable PDF/Word form with blank fields rather than structured records containing PII. No importable data columns exist.

File structure

Notes: This file appears to be free-form text containing payment reconciliation details for an employee. It lacks consistent columnar structure with rows varying in length and content. While it contains personal identifiers like a name (Woody Cheatham) and monetary amounts, the format does not conform to a standard delimited structure with repeating rows. The content resembles a narrative report rather than structured tabular data.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The sample shows a summary of relocation expenses with headers and values but lacks a repeating columnar pattern across rows. There are no identifiable PII fields in this snippet, and the structure does not conform to CSV/TSV requirements. Given the unstructured nature and absence of consistent columns, this file should be processed as unstructured text.

File structure

Notes: free-form text with no consistent column structure; contains financial reconciliation details but no identifiable PII fields in structured format

File structure

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

Notes: This appears to be a 401(k) loan report with employee names and dates of birth. Columns 0,2,4-18 contain internal IDs, loan details, and financial data — all skipped per rules. Only fullName and dob contain PII.

File structure

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

Notes: Only two PII columns present: Lastname and Firstname. All other columns contain payment/check identifiers, dates, and amounts — not PII. No emails, addresses, DOB, SSN, or other sensitive data visible in the sample.

File structure

Notes: free-form text with embedded emails / phones

File structure

Notes: The provided data is a free-form text document describing HR onboarding and benefits enrollment processes. It lacks any consistent delimiter structure or tabular format. While it mentions HR processes and employee data, it does not contain any actual PII in a structured format. This appears to be a README or process document rather than a dataset containing personal information.

File structure

Notes: This is a free-form text document (HR/IT requisition form) with no consistent columnar structure. Contains employee name 'Karry Mabry' and supervisor name 'Jaymi Mallion', but lacks a repeatable delimiter pattern across rows. Classified as unstructured per rules due to prose-style layout and embedded PII in narrative format.

File structure

Notes: This is a free-form form template with no consistent column structure. It contains placeholder text and checkboxes for an HR/IT requisition form, but no actual PII data in the first 50 rows. Since it's unstructured prose with no repeating columnar pattern, it qualifies for unstructured processing.

File structure

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

Notes: 33 total columns, 11 contain PII; others are employment metadata (hire date, benefit plan, etc.). Column 0 is full name; columns 17-21 are dependent (child) PII fields.

File structure

Notes: This is a free-form text file (HR New Hire Setup) with no consistent columnar structure. It contains embedded PII such as names (Linda Mahler, Astancil) and potentially sensitive HR information, but does not present a structured table for column mapping. The format is unstructured with variable lines and no consistent delimiter.

File structure

Notes: This is an unstructured form-like document with no consistent delimiter or column structure. The content appears to be an IT & HR Requisition Form for New Employee, containing free-form fields and checkboxes rather than structured tabular data. No PII columns can be mapped due to the unstructured format.

File structure

Notes: This is a free-form form template with blank fields and no actual data rows. While it mentions concepts like 'Email Account' and 'Phone Extension', no real PII values exist in the sample. The structure is entirely prose/formatted text without consistent columnar data, so it qualifies as unstructured content.

File structure

Notes: This is a README/form template document, not a structured data file. It contains a single employee onboarding requisition form with prose instructions, checkboxes, and section headers. While it includes one sample record (Stephanie Nicholson, hired 2021-03-15), the file structure is a form template with mixed text, labels, and values — not delimited records. The file serves as documentation of HR onboarding workflow rather than a data export. No importable columnar PII data.

File structure

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

File structure

Notes: This is a form template with blank fields and no actual data rows. While it contains field labels that might resemble PII categories (e.g., Employee Name, Email Account), there are no populated records or structured data rows to map. The file is purely a template with placeholders, not a data export containing PII. Therefore, no columns can be mapped as PII-containing.

File structure

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

Notes: This is a form with no consistent columnar structure or PII fields. It is a requisition form for new employees with checkboxes and free-form fields, not structured data containing PII. No columns map to PII fields.

File structure

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

File structure

Notes: This is a free-form template with blank fields and instructions, not structured data rows. No consistent delimiter exists, and the content is entirely prose with placeholder lines rather than actual records.

File structure

Notes: This is a free-form performance improvement report document with no consistent columnar structure. It contains employee performance feedback and signatures but lacks any delimited data format. The content is narrative prose rather than structured records with PII columns.

File structure

Notes: This is a free-form performance improvement report document, not a structured dataset with columns. It contains employee comments and performance feedback but lacks any columnar structure or delimiter-separated fields. The content appears to be a narrative performance review form rather than tabulated PII data.

File structure

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

Notes: Only column 0 contains PII (fullName). Other columns are time-off records (dates, hours, comments) and contain no personal identifiers beyond the employee's name already captured in column 0. No emails, phone numbers, DOB, SSN, or other PII present in sample.

File structure

Notes: free-form text with embedded emails / phones

File structure

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

Notes: File is a healthcare EOB (Explanation of Benefits) records export. Column [2] 'For' contains both member name and embedded date of birth in free-form text (e.g., 'ASHLEY 5/2/1962'). Columns [0] (Number/claim ID), [1] (Service Date), [3] (Type), [4] (Doctor/Facility), [5] (Total Charges), [6] (Member Responsibility), [7] (Status), [8] (EOB Form link) are all non-PII (internal transaction identifiers, medical facility names, financial transaction data, and status flags). Only the 'For' column [2] contains extractable PII: firstName/lastName and dob. The context indicates this is an employee benefits record from the Frosty Acres breach.

File structure

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

Notes: This is not a PII-containing file. The data appears to be financial performance metrics and forecasts for Frosty Acres Brands across multiple fiscal years (2007-2022). All columns contain numeric financial figures, fiscal year labels, and forecast periods with no personal identifiers, names, addresses, or other PII fields. The sample shows financial metrics like operating income, member counts, and revenue figures rather than any personal data.

File structure

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

Notes: This file appears to be a financial record detailing salary and incentive history for an employee at Frosty Acres Brands. All columns contain salary data, incentive percentages, and totals across multiple fiscal years. There are no personal identifiable information (PII) fields such as names, addresses, emails, phone numbers, or other sensitive data in the first 50 rows. The data is purely financial and transactional in nature.

File structure

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

Notes: This is a structured CSV file, but it contains no PII fields. The columns present are Name, Date Effective, Title, Rate, and BP. None of these columns map to any of the defined PII fields (email, phone, dob, firstName, middleName, lastName, fullName, address1, address2, city, state, zip, ssn, password, username, country, gender, suffix, facebookId). The Name column appears to contain only a single name per row, but without additional context or values that clearly identify first and last names, it cannot be reliably mapped to firstName or lastName. Therefore, no PII columns are identified.

File structure

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

Notes: Only column 0 contains PII (fullName). All other columns are internal tracking fields (department, dates, hours, earnings) or totals/summaries, not containing any PII. No email, phone, address, DOB, SSN, etc. visible in sample.

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a list of employee records without column headers or delimited fields. Contains names but lacks any structured format for mapping to PII columns.

File structure

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

Notes: This appears to be an employee roster with name components but no other PII fields. The format is comma-delimited with no header row.

File structure

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

Notes: CSV with two PII columns: lastName and firstName. No other columns contain PII (TITLE, DEPT, and X/X flags are non-PII).

File structure

Notes: The provided text is a free-form performance improvement report document with no consistent columnar structure. It contains employee and supervisor signatures as blank lines, not structured data fields. While it mentions an employee name (Amy Couch), this exists within prose rather than as a delimited column. The document lacks any shared delimiter or row pattern — every line has unique content and length. Since emails/phones aren't visible and the format fails the structured criteria, this is correctly classified as unstructured text requiring special handling.

File structure

Notes: This is a free-form performance improvement report document with no consistent columnar structure. It contains employee name (Amy Couch) but lacks any delimited format or repeated field patterns. The content is prose-style with no CSV-like structure, therefore mapped as unstructured text.

File structure

Notes: This is a free-form performance improvement report document with no consistent columnar structure. It contains employee name (Linda Mahler) but lacks any repeating tabular data format. The content appears to be a narrative performance evaluation rather than structured records.

File structure

Notes: The provided text is a free-form performance improvement report document. It contains no consistent delimiter structure across lines, each line has different content/shape, and while it includes a name (Linda Mahler) and dates, it lacks any tabular structure. This qualifies as unstructured text per the rules — we should route through streaming extraction for any embedded PII rather than trying to map columns.

File structure

Notes: This is a free-form performance improvement report document with no consistent columnar structure. It contains employee names and signatures but lacks any repeated tabular data format across lines. The content appears to be a narrative form with handwritten signature lines and distribution instructions, not a delimited dataset.

File structure

Notes: This is a free-form text document (performance appraisal meeting notes) with no consistent columnar structure. The content contains names but lacks any delimiter-based row format. It qualifies as unstructured data per the rules because: (a) no consistent delimiter exists, (b) lines vary in length and structure, and (c) contains personal names which are considered PII. This should be processed through a streaming PII extractor for names, not mapped as a CSV.

File structure

Notes: free-form text with embedded names, no consistent delimiter or structured columns

File structure

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

Notes: This file is a free-form unstructured text file. It contains employee names and some references to actions or comments, but there is no consistent delimiter structure across lines, and it appears to be a mix of prose and data entries rather than a structured CSV. The content includes employee names and some administrative notes, but no clear PII fields like email, phone, or address are present in a structured format. Therefore, it is classified as unstructured text with no column mappings.

File structure

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

Notes: File contains employee personnel records from Frosty Acres Brands breach. Column 0 (CompanyCell) is a benefit/reimbursement plan code and is skipped as non-PII. Column 1 contains full employee names parsed as fullName since individual firstName/lastName components are not separated into distinct columns.

File structure

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

Notes: This appears to be a driver licensing or employee verification file. Contains full names, dates of birth, driver license numbers, and states of residence. No emails, phones, or addresses are present in the sample.

File structure

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

Notes: Only 4 columns present; 3 contain PII (fullName, dob, state). Column 2 contains driver license numbers which are NOT mapped to any PII field type per schema.

File structure

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

Notes: This is a minimal employee roster with full names, dates of birth, driver's license numbers, and states. No emails, phones, or addresses are present. The 'Dr Lic #' column contains Georgia driver's license numbers, which are PII but there is no dedicated field for it in our schema — we map only to state.

File structure

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

Notes: This appears to be a fragment of an employee personnel file export. Column 2 contains driver's license numbers, which are NOT mapped to any PII field in our schema (we only map state-issued IDs if explicitly labeled as such, but driver's licenses are excluded). All other columns map cleanly to PII fields.

File structure

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

Notes: Only two columns contain PII: fullName and dob. Other columns contain employment metadata (position, license, MVR status) or internal tracking codes — no PII present. Values in column 0 are full names, not split into firstName/lastName, so mapped to fullName.

File structure

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

Notes: Only columns 0 (fullName) and 1 (dob) contain PII. All other columns contain employment/MVR status data, license numbers, positions, expiration dates, and comments — none are PII. No email, phone, address, SSN, or password data is present.

File structure

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

Notes: Only two columns contain PII: driver name (fullName) and DOB. All other columns are internal flags, dates, or positions — not personal data.

File structure

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

Notes: Only two columns contain PII: fullName and dob. All other columns are internal driver/license tracking fields or status flags.

File structure

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

Notes: Only columns 0 (fullName) and 1 (dob) contain PII. All other columns contain employment/licensing metadata (position, license numbers, expiration dates, MVR status) which are not personally identifiable in this context. No emails, phone numbers, addresses, SSNs, or passwords are present in the first 50 rows.

File structure

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

Notes: Only 5 columns contain PII (fullName, address1, city, state, zip). All other columns are internal company codes, employment status flags, or non-personal data (departments, distances, work arrangements). No email, phone, DOB, SSN, or password data present in the first 50 rows.

File structure

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

Notes: This is an unstructured file with no consistent column mapping. It appears to be a list of employee roles and sign-off records without any PII fields. All visible data are job titles, status flags, and dates — no emails, names, addresses, or other PII appear in the sample. The format lacks headers and consistent structure for column mapping.

File structure

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

Notes: This is a free-form text file with no consistent column structure. It appears to be a list of work-from-home agreements with employee titles and names, but lacks a defined columnar format across rows. The data is unstructured and does not conform to a tabular format with consistent columns. No PII columns can be mapped due to the absence of a structured format.

File structure

Notes: This is a free-form text file containing employee agreement and terms history. It lacks a consistent delimiter structure and appears to be a prose-style table with embedded dates and financial data. While it contains sensitive employment data, it does not follow a structured column format with repeatable fields. Therefore, it is classified as unstructured for processing via streaming extraction.

File structure

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

Notes: CSV with 6 columns; columns 0, 1, and 6 map to lastName, firstName, and middleName respectively. Column 2 (TITLE) and column 3 (DEPT) contain honorifics and department codes, respectively, which are not PII. Column 4 (RCVD & SIGNED) and column 5 (BP) are flags and numerical values, not PII.

File structure

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

Notes: This is not a structured dataset with PII columns. The file appears to be a mix of employee names, internal notes, and administrative comments rather than a CSV with defined columns mapping to PII fields. There are no consistent columns that map to email, phone, DOB, etc. The content is free-form notes and employee listings without structured PII fields. Therefore, no PII columns can be mapped.

File structure

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

Notes: This is not structured data with PII columns. The file appears to be a free-form employee list with names and notes, but lacks consistent column mappings for PII fields. The content includes employee names in a format that does not map to standard PII columns (e.g., full names concatenated with commas), and there are no identifiable email, phone, DOB, address, or other PII fields. The structure is inconsistent, and the rows do not represent a standardized dataset with mappable columns. Therefore, no PII columns can be identified.

File structure

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

Notes: Only column 0 contains PII (full name). All other columns are internal workflow flags, titles, dates, or empty fields. No emails, phones, addresses, or other PII present in this form template.

File structure

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

File structure

Notes: The provided text is a form template with empty fields and instructions. It contains no actual data rows or PII values. While the form fields suggest potential PII collection points (e.g., Employee Name, Email Account), the sample itself is purely descriptive and lacks any structured data or personal information to map. Therefore, this is treated as unstructured content with no column mappings.

File structure

Notes: This is an unstructured form/document. The data appears to be a printed requisition form template with handwritten entries (e.g., 'Tatiana Cordova', 'Carrie Orders'). There is no consistent columnar structure across lines — each line represents a different form field label rather than a repeating record. While it contains PII in the filled values, the format lacks delimited rows/columns required for structured parsing. It should be processed through free-form text extraction for names, dates, etc.

File structure

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

File structure

Notes: This is a form template with blank fields and instructions. No actual PII values are present in the sample rows — it's a static document skeleton for temporary employee onboarding at Frosty Acres Brands. Since it's unstructured free-form text with no consistent column mapping, we treat it as unstructured for downstream extraction of any potential embedded PII that may appear when the form is filled out in real usage.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The sample shows unstructured records with varying fields and no shared format. While there are no visible emails or phone numbers in the sample, the lack of structured columns means we should treat this as unstructured text for processing.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The lines appear to be fragments of FMLA/STD/PTO records with dates, amounts, and status flags, but there is no delimiter or repeating header pattern. While there are dates and numeric values, they are not structured rows with defined columns, and the content varies per line. Additionally, there are no visible emails or phone numbers in the sample to trigger unstructured extraction.

File structure

Notes: free-form text with embedded dates and pay calculations; no consistent column structure. Contains employee FMLA leave details for Beth Hatter but lacks defined columns for PII mapping

File structure

Notes: This is an unstructured free-form text file containing expense report templates and accounting instructions. No consistent columnar structure exists across rows, and it lacks header definitions. While it contains placeholder fields (e.g., signature lines), these are not actual PII records but rather template elements. The file does not contain importable structured data with PII columns.

File structure

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

Notes: Only column 0 contains PII (fullName). All other columns are non-PII metadata about time-off requests. No emails, phones, DOB, or addresses appear in the sample.

File structure

Notes: This is not a structured delimited file. The data appears to be free-form text containing internal reports and documents from Frosty Acres Brands. There are no consistent columns or delimiters across rows, and the content consists of narrative-style entries, headers, and footers typical of PDF exports or printed reports. While there is some PII-like content (e.g., "LEWIS, PATRICIA" and "11/15/1962"), these appear embedded within unstructured text rather than as part of a tabular structure. Therefore, this file should be processed as unstructured text with embedded PII extraction.

File structure

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

Notes: This is a structured CSV file, but the visible rows contain only form template headers and checkboxes — no actual employee PII data is present in the first 50 rows. All columns appear to be internal flags, request checkboxes, or empty placeholders. No PII fields (email, phone, name, etc.) are populated or mappable based on this sample. The file likely contains sensitive forms, but this specific excerpt shows only the blank template.

File structure

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

File structure

Notes: This is a template form with empty fields and headers only. No actual data rows exist in the provided sample; it is a static document outlining form sections and checkboxes rather than a dataset containing personal information. As such, it does not contain structured PII to map.

File structure

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

Notes: CSV with headers. Contains employee requisition form data with PII fields: fullName, email, phone. All other columns are non-PII (titles, departments, checkboxes, internal notes).

File structure

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

File structure

Notes: This is a free-form document template with form fields and instructions, not structured data rows. Contains no actual PII values in the sample — only placeholders and empty fields. No consistent delimiter structure exists across lines.

File structure

Notes: This is a free-form template document (Requisition Form for New Employee) with no consistent columnar structure. It contains form fields and checkboxes rather than tabular data. Per the unstructured rules, no column mapping is performed.

File structure

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

File structure

Notes: This is a form template with blank fields, not structured data rows. The file contains no actual employee records or PII values — only placeholders and instructions for supervisors to fill out. It is not a CSV or any delimited structured format with columns to map. The content is purely descriptive prose about a requisition form.

File structure

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

Notes: Only column 0 contains PII (fullName). All other columns are non-PII: Department, Date Requested, Hours Requested, Earning, Year Allotted, Balance to C/O, Total for Year Allotted — these are transactional/time-off tracking fields with no personal identifiers beyond the name already captured in column 0.

File structure

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

Notes: Only column 0 contains PII (full names). All other columns contain time-off metadata (dates, hours, comments) which are internal scheduling data and not PII. No emails, phones, addresses, DOB, SSN, etc. present in sample.

File structure

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

Notes: This appears to be a requisition form template with checkboxes and supervisor fields. Only Employee Name and Supervisor fields contain PII (full names). All other fields are internal process tracking or blank checkboxes.

File structure

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

File structure

Notes: This is a free-form template document (Requisition Form for New Temporary Employee) with no consistent columnar structure. It contains placeholder lines and blank fields rather than actual data records. While it mentions fields like 'Employee Name' and 'Email Account', these are template labels, not populated PII columns. The file lacks a consistent delimiter and row structure required for columnar mapping.

File structure

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

Notes: Only columns 0 (fullName) and 1 (dob) contain PII. Column 2 appears to be a driver license number, but since there is no defined PII field for this, it is skipped per rules. Column 3 is a state abbreviation, also skipped.

File structure

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

Notes: Only 4 columns present; 3 contain PII (fullName, dob, state). The driver license number column is excluded per policy (it is a government-issued identifier but not explicitly listed as a PII field in the allowed types).

File structure

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

Notes: 4 columns total; 3 contain PII (fullName, dob, state). 'Dr Lic #' appears to be a driver's license number, but this field is not in the defined PII categories and must be skipped per rules.

File structure

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

Notes: This appears to be a driver license / employee roster file. Column 2 contains driver license numbers which are excluded per the rules because they are not core PII fields (though they are identifiers, they fall under the 'skip' category for this breach context).

File structure

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

Notes: Only columns 0 (fullName) and 1 (dob) contain PII. Other columns contain employment metadata (position, license numbers, MVR status) or internal tracking (expirations, comments) and do not qualify as PII under the rules.

File structure

Notes: The file is a free-form financial document (pay reconciliation) with no consistent columnar structure. It contains employee name "Woody Cheatham" but no structured PII fields. The format is narrative prose rather than delimited records, matching unstructured text pattern with variable line shapes and no repeating columnar pattern.

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a financial summary document with no PII columns present

File structure

Notes: free-form text with embedded financial data, no consistent column structure. Contains payment amounts and expense details but no identifiable PII columns.

File structure

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

Notes: This is a 401(k) loan report with employee names and dates of birth. No email, phone, address, SSN, or password fields present in the sample. Columns 0,2,4-18 are financial/loan metadata and skipped per rules.

File structure

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

Notes: CSV file with 7 columns. Only Lastname and Firstname contain PII. All other columns are payment codes, dates, or amounts and do not contain PII.

File structure

Notes: The file appears to be free-form text with no consistent column structure. It contains unstructured data such as payroll information, dates, and pay amounts. There are no identifiable PII fields in a structured format, and the data does not conform to a tabular structure with consistent columns across rows.

File structure

Notes: The provided text is a free-form performance improvement report with no consistent column structure. It contains employee commentary and signatures but lacks any delimited data fields. While it includes a name (Georgia Prater), this is embedded in prose and not part of a structured dataset. Therefore, it is classified as unstructured text with no column mappings.

File structure

Notes: free-form text with no consistent column structure; contains employee performance review documentation but not in tabular format

File structure

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

Notes: Only column 0 contains PII (fullName). Other columns are internal tracking fields (Department, Date Requested, Hours Requested, etc.) and do not contain personal identifiable information. The format is a standard CSV with a header row.

File structure

Notes: free-form text with embedded emails / phones

File structure

Notes: free-form text with embedded emails / phones

File structure

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

Notes: This is a medical claims/EOB (Explanation of Benefits) record file. Column [0] 'Number' is claim ID (skip), [1] 'Service Date' is timestamp (skip), [2] 'For' contains member name and DOB embedded together, [3] 'Type' is claim type (skip), [4] 'Doctor/Facility' is provider/business name (skip per EXCLUSION RULES — business names), [5] 'Total Charges' is financial (skip), [6] 'Member Responsibility' is financial (skip), [7] 'Status' is internal flag (skip), [8] 'EOB Form' is UI link (skip). Only PII present: firstName/lastName extracted from 'For' column and DOB embedded within it.

File structure

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

Notes: 18 columns total, 5 contain PII (fullName, address1, city, state, zip). Columns 1 (Department), 2 (Department_Desc), 7 (TYPE), 8 (Distance), 9 (WORKING FR HOME NOW), 10 (WFH SIGNED), 11 (WFH only during Covid-19), 12 (Returned In Office), 13 (FAB Waived PTO & FAB PAID), 14 (Furloughed 4/6/20), 15 (Furlough Status), 16 (Returned to 40 hrs), 17 (Returned to Full Pay) contain employment status/tracking data and are skipped per rules.

File structure

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

Notes: This file appears to be a structured CSV with employee work-from-home agreements, but it does not contain any personally identifiable information (PII). The columns contain role titles and names, but these are not mapped to any PII fields because the names are not full names with first and last name separation, and there are no emails, addresses, phone numbers, DOB, SSN, etc. The 'EE Signed' column contains what looks like employee names, but without additional context or structure (like firstName/lastName separation), we cannot confidently map this to a PII field. All potentially identifying columns are skipped per rules.

File structure

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

Notes: 7 columns total, 6 contain PII. First column contains full names despite blank header. SSN, DOB, address, city, state, and ZIP are all clearly present. DL# and date columns appear to be internal tracking fields and are skipped.

File structure

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

Notes: Motor Vehicle Record (MVR) report from 2015, likely driver/employee screening file. Column [7] 'DL#' (Driver License number) is an internal identifier and regulatory document reference—mapped to skip. Columns [8] and [9] are timestamps (Last Run Date, Current Run Date)—mapped to skip. Column [10] 'Comments/Results' is free-text—mapped to skip. 7 PII columns identified: fullName, ssn, state, dob, address1, city, zip.

File structure

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

Notes: MVR driver information file for employees from 2005. Column 0 (SUPV) contains supervisor first names only—mapped to skip. Column 1 (Department) is job title—skip. Column 3 (Dr Lic #) is driver license number—mapped to skip (internal identifier). Columns 5-9 (Expires, Copy Ins Provided, Renewal Date, Last MVR, Comments, Reminders) are administrative/transactional dates and flags—all skip. File contains 35 employee records with names and state of license; minimal PII extracted due to limited personal data fields present.

File structure

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

Notes: The provided data does not contain any identifiable PII columns. The values appear to be internal tracking codes, department names, and status flags. No emails, phone numbers, names, addresses, DOBs, SSNs, or other PII fields are present in the sample. Columns 0 and 3 contain what looks like employee names, but they are not clearly mapped to firstName/lastName due to inconsistent formatting and lack of header context. All columns appear to be internal management or tracking fields, thus mapped as skip.

File structure

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

Notes: This appears to be driver MVR (Motor Vehicle Record) data with limited PII. Only fullName is present and mappable. Other columns contain timestamps, state codes, status flags, and internal tracking codes which are non-PII and skipped.

File structure

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

Notes: This appears to be an MVR (Motor Vehicle Record) or driver license tracking sheet with no PII beyond names. No emails, phones, DOB, SSN, or addresses are present in the first 50 rows. Column 3 is the only PII-containing field (full names).

File structure

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

Notes: This appears to be employee driver records. Columns 3, 4, and 5 contain clear PII. Column 6 contains numeric driver license IDs but is not directly mappable to any defined PII field type. All other columns are internal flags or timestamps.

File structure

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

Notes: This appears to be a vehicle/MVR (Motor Vehicle Record) data export from an HR or onboarding system. Columns 2-4 contain full names, addresses, and DOBs of employees. Other columns contain driver license information, state codes, expiration dates, and MVR status flags — these are not PII. No emails, phones, or SSNs are present in this subset.

File structure

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

Notes: Only columns 2, 3, and 4 contain PII. Column 2 contains full names in "Last, First" format. Column 3 contains complete US addresses with street, city, state, and ZIP. Column 4 contains birth dates in ISO 8601 format. All other columns are either non-PII status flags (SUPV, MVR, Expires, Comments), internal IDs (Dr Lic #, MVR), or timestamps (Last, Last Ran MVR, Run NEXT). No emails, phones, SSNs, or usernames are present in the sample.

File structure

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

Notes: This appears to be a structured CSV file with 14 columns. Columns 2, 3, and 4 contain clear PII: full names, addresses, and dates of birth. Other columns contain non-PII data such as driver status codes, license numbers (which appear to be state-issued driver license numbers, but are excluded per rules), state codes, expiration dates, MVR status, and comments/reasons. No emails, phone numbers, SSNs, usernames, or passwords are present in the sample.

File structure

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

Notes: 14 columns total, 3 contain PII: fullName (column 2), address1 (column 3), dob (column 4). Columns 0-1 and 5-13 are non-PII: supervisor codes, position titles, driver's license numbers (state-specific but not SSN), state codes, MVR status/timestamps, and comments. No emails, phones, or usernames present.

File structure

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

Notes: File is an MVR (Motor Vehicle Record) driver tracking sheet from 2005. Only one PII column identified: Employee Name. Other columns contain driver license numbers (Dr Lic #), state codes, expiration dates, insurance status, and administrative dates — all are non-PII operational data. The first column (SUPV) contains supervisor first names only (e.g., 'Ashley', 'Jaymi', 'George') but these are fragmentary and not reliably mappable as standalone identifiers; they appear to be notes rather than structured name fields. Department and Comments columns are operational/administrative, not PII.

File structure

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

Notes: Only column 3 contains PII (full names). All other columns appear to be status flags, dates, or empty fields with no personal data. The sample shows employee names in column 3, but no emails, addresses, DOB, SSN, etc.

File structure

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

Notes: This is an unstructured file with no consistent column mapping. The data appears to be free-form text with no clear delimiter structure across rows. While there are some values that could be interpreted as names (e.g., "Aplis, Linda"), the lack of a consistent column structure means we cannot reliably map PII fields. The file should be processed as unstructured text for further analysis.

File structure

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

Notes: Only column 3 contains PII (full names). Other columns contain status flags, dates, or unstructured notes. No emails, phones, addresses, or other PII detected in the sample.

File structure

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

Notes: Only 3 of 14 columns contain PII: fullName, address1, and dob. All other columns appear to be status flags, document codes, or internal tracking fields with no personal data.

File structure

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

Notes: 14 total columns; only 3 contain PII (fullName, address1, dob). Other columns are status codes, license numbers, and audit metadata. No email/phone/username columns present.

File structure

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

Notes: CSV file with 14 columns; only columns 2, 3, and 4 contain PII (fullName, address1, dob). Other columns contain job titles, license numbers, state codes, expiration dates, and status flags that are non-PII per exclusion rules.

File structure

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

Notes: Columns 0-1 and 5-13 contain non-PII values: supervisor codes, position titles, driver license numbers (non-SSN), state codes, MVR statuses, timestamps, and comments. Only columns 2, 3, and 4 contain personal PII fields.

File structure

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

Notes: Only 3 of 14 columns contain PII. Column 2 contains fullName in 'Last, First' format. Column 3 is a full US address. Column 4 is explicit date-of-birth. All other columns are internal flags, timestamps, or non-PII codes.

File structure

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

Notes: This appears to be a legacy MVR (Motor Vehicle Report) tracking sheet with employee names. Only column 2 contains PII (fullName). Other columns contain department codes, state abbreviations, dates, and status flags that do not map to any PII fields. The format lacks a proper header row and uses inconsistent formatting.

File structure

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

Notes: This is not a PII file. The columns appear to be headerless data from a form or document template (MVR Driver Information). Values like 'SUPV', 'Department', 'Memb Serv', 'Category Manager', and dates represent form statuses and categories, not personal identifiers. No columns map to PII fields because there are no emails, names, addresses, DOBs, SSNs, phones, or other PII values present.

File structure

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

Notes: This file contains no PII columns. All columns appear to be non-PII metadata or placeholder headers with ambiguous values. Column 3 contains partial name fragments ("Aplis, Linda"), but these appear to be part of document titles or codes rather than actual personal names, and there are no columns containing email, phone, address, DOB, SSN, or other PII fields. The data appears to be document management metadata rather than personal records.

File structure

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

Notes: This file appears to be unstructured data with no consistent column mapping. The columns do not contain identifiable PII fields such as email, phone, dob, etc. The values appear to be miscellaneous notes and codes rather than structured personal information. Therefore, no PII columns can be mapped.

File structure

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

Notes: 14 columns total, 3 contain PII (fullName, address1, dob). Columns 0-2,6-13 appear to be status flags, identifiers, or metadata and contain no PII.

File structure

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

Notes: 13 columns total, 3 contain PII: fullName (column 2), address1 (column 3), and dob (column 4). Columns 0-1 and 5-12 are non-PII: supervisor codes, job titles, driver license numbers, state codes, expiration dates, MVR status flags, and comments. No emails, phones, SSNs, or usernames detected.

File structure

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

Notes: Only 4 columns present; 3 contain PII. Column 2 (Dr Lic #) appears to be driver's license numbers but is not mapped to a defined PII field type in our schema. All rows follow the same structure.

File structure

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

Notes: This appears to be a driver licensing or employment verification file. Contains full names, dates of birth, driver's license numbers, and states. No email, phone, or address fields present in the first 50 rows.

File structure

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

Notes: Only two PII columns present: fullName and dob. The third column 'Dr Lic #' appears to be a driver license number, which is not in our defined PII fields and therefore omitted. The fourth column 'State' is a location code, not PII per our definitions.

File structure

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

Notes: MVR (Motor Vehicle Record) driver list from 2020. Column 2 (Dr Lic #) contains driver license numbers — these are government-issued ID numbers and sensitive PII but do not map to any available field type, so omitted. Column 3 (State) is mapped as state (likely license/residence state). File has two header/title rows before the data header row.

File structure

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

Notes: Columns 2 (Dr Lic #) appears to contain driver license numbers but is not a defined PII field in our schema; excluded. Row 29 is blank except for index 0 which reads '29' — treated as skip. File appears to be a driver license registry for employees.

File structure

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

Notes: Only columns 0 (fullName), 1 (dob), and 3 (state) contain PII. Column 2 (Dr Lic #) appears to be Georgia driver license numbers — these are considered PII but the field type was not in the provided list. All other columns are empty or contain non-PII data.

File structure

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

Notes: Only 4 columns present. Column 2 ('Dr Lic #') appears to be driver license numbers, but there is no PII field defined for driver licenses in the schema, so it is skipped. All rows show employee personnel data from Frosty Acres Brands.

File structure

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

Notes: MVR (Motor Vehicle Record) driver list for 2020. Column 2 ('Dr Lic #') contains driver license numbers — sensitive government ID but not a supported PII field type, mapped to skip. Column 3 is state of license issuance. Header rows 0-1 are metadata/title rows; actual data begins at row 2.

File structure

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

Notes: Only columns 0 (fullName), 1 (dob), and 3 (state) contain PII. Column 2 (Dr Lic #) appears to be driver's license numbers, which are NOT mapped to a standard PII field type in this schema. All other rows appear to be metadata or empty.

File structure

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

Notes: 4 columns total, 2 contain PII (fullName, dob). Column 2 contains driver license numbers which are not in our PII schema. Column 3 is state abbreviation which maps to state field.

File structure

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

Notes: 23 employee records shown; only name, DOB, and state are PII. Driver license numbers are excluded per policy.

File structure

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

Notes: This appears to be a driver license register extracted from employee personnel files. Contains full names, dates of birth, and state-issued driver license numbers. The driver license field is NOT mapped to any PII field because our schema does not include driver's licenses as a distinct category.

File structure

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

Notes: This appears to be a driver license / employee roster file. Column 2 contains driver license numbers (Dr Lic #), which are NOT considered PII per exclusion rules (they are government-issued identifiers but not mapped to any known PII field type). Only fullName, dob, and state are mappable PII.

File structure

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

Notes: CSV file with headerless format. Columns map to PII fields including full name, address, city/state/zip, phone, and email. The 'Position/Title' column may occasionally contain suffix-like values but is mapped as suffix with low confidence.

File structure

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

Notes: This file is a structured CSV but contains no personal identifiable information (PII). All columns describe background check services, vendor information, and service costs without any employee or customer PII fields. The data appears to be a summary of HR benefits screening services and associated fees, with no names, addresses, emails, phone numbers, or other PII present.

File structure

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

Notes: Only three PII columns identified in this structured CSV header row: Contact Name (fullName), Phone (phone), and E-mail Address (email). Other columns are either empty or non-PII metadata.

File structure

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

Notes: This is not a PII-containing dataset. The file appears to be a template or instruction sheet for submitting store locations for background screening services. It contains only store addresses and contact information for the company itself (F.A.B., Inc), not individual employee or customer PII. All columns map to skip categories: company name, internal identifiers (Store #), address fields referring to business locations, and generic location hours. No email, phone, dob, name, ssn, or other personal identifiers are present.

File structure

Notes: free-form text with embedded emails / phones

File structure

Notes: This is a free-form text document (project scope and data collection worksheet) with no consistent columnar structure. It contains embedded contact details (name, phone, email) but lacks row-based tabular data. Per unstructured rules, no column mapping is performed.

File structure

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

File structure

Notes: This is unstructured data; the sample shows free-form text lines with no consistent delimiter or column structure. Each line contains varied content such as vendor names, service descriptions, and pricing details, indicating a prose-style document rather than a tabular dataset. No PII can be reliably mapped as there are no identifiable column patterns or repeated fields.

File structure

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

Notes: Only columns 2-5 contain PII. Columns 0,1 are headers/metadata and column 6 contains non-PII notes. No other PII fields detected in sample rows.

File structure

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

Notes: This is not structured PII data; it's a header/instruction row and sample store location data. No personal identifiable information (PII) fields are present in the first 50 rows. The rows contain store location metadata (address, city, state, zip, phone) but these are business locations, not individual PII. Per exclusion rules, business addresses and phone numbers are skipped. No email, name, DOB, SSN, etc. appear.

File structure

Notes: This is unstructured text (prose) containing policy information and administrative notes rather than structured data records. No consistent column structure exists across lines — this is free-form administrative documentation about drug policy and reporting requirements, not a delimited data file containing PII fields. The sample shows paragraphs and bullet points rather than tabular data.

File structure

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

File structure

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

Notes: 50 rows parsed; columns 0-7 contain PII. Columns 2-4 (Title/Dept/Ext) and 8-13 are skip fields (titles, departments, extensions, flags, notes).

File structure

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

Notes: FAB employee directory from 2015. Columns 2 (Title), 3 (Dept), 8–12 are internal flags/review status (skip). This is a structured CSV with employee names, contact phone numbers, fax, and birthdates. The footer row summary ('33 YES, 5 NO') is metadata, not a data record.

File structure

Notes: free-form text with no consistent delimiter or column structure; contains form template with placeholders and checkboxes

File structure

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

File structure

Notes: This is a template form with empty fields and instructions, not structured data rows. It lacks consistent column alignment and contains no actual PII values. The content is purely a form skeleton with placeholders and checkboxes — no real employee data is present in the sample.

File structure

Notes: This is a free-form template document (Requisition Form for New Employee) with no consistent columnar structure. It contains form fields but not tabular data rows with repeating records. Per rules, unstructured files with no consistent delimiter/column structure are mapped as unstructured, even if they contain PII-like placeholders. The sample shows a single document template, not multiple employee records in a delimited format.

File structure

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

File structure

Notes: This is a free-form template form with no structured data or PII in the first 50 rows. It contains form fields and instructions rather than actual data records.

File structure

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

Notes: This file is not structured PII data. Column 0 appears to be a header row describing 1099 vendor company attributes, but the subsequent rows contain only non-PII metadata such as coverage types, status flags, and comments. No actual PII fields (email, phone, name, etc.) are present in the first 50 rows. This appears to be an internal document tracking sheet rather than employee/contractor personal data.

File structure

Notes: File appears to be a font definition file (Adobe-FontList) containing font metadata and paths, not structured tabular data. No PII fields present.

File structure

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

Notes: Only 3 PII columns identified: fullName, gender, and dob. All other columns are internal identifiers, job data, or salary information.

File structure

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

Notes: Only firstName and lastName columns contain PII. All other columns contain salary information and status flags which are not PII per exclusion rules (financial/transactional data). No emails, phones, DOB, SSN, or addresses present.

File structure

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

Notes: This file contains structured data but no PII fields. All columns appear to be related to benefits information, dates, and status codes. There are no columns mapping to email, phone, name, address, DOB, SSN, password, username, country, gender, suffix, or facebookId. The data is purely informational regarding benefit plans and furlough statuses.

File structure

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

Notes: Only column 1 contains PII (fullName). All other columns are financial/transactional data (401k, dental, medical) and should be skipped per exclusion rules.

File structure

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

Notes: Only column 2 contains PII (fullName). Columns 0 (Plan Year End), 1 (Check # / ACH), 3 (Date), 4 (Type), and 5 (Amount) contain transactional/financial data and are not PII.

File structure

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

Notes: Only column 0 contains PII (full names). All other columns are financial/deductible amounts and totals — no PII present.

File structure

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

Notes: Only columns 1 (fullName) and 3 (middleName) contain PII. All other columns are internal identifiers, dates, salary data, or employment status codes.

File structure

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

Notes: Only columns 0 and 1 contain PII (fullName and lastName). All other columns are timestamps, monetary values, or totals — no PII present.

File structure

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

Notes: 50 rows shown, 26 columns total. Only firstName, lastName, and state contain PII. All other columns are salary/benefit data, timestamps, counters, or non-PII identifiers and are skipped per rules.

File structure

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

Notes: 50 rows shown, 28 columns total. Only columns 1,2,4,5,6 contain PII. Columns 0 (date) and 7-27 are salary/employment metrics (skip).

File structure

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

Notes: This is a payroll data file containing only names and salary figures. No PII fields (email, phone, address, etc.) are present. The column 'Lastname' contains only surnames without any additional PII. All other columns are numerical salary data and timestamps.

File structure

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

Notes: Only columns 0 (firstName) and 1 (lastName) contain PII. All other columns are numeric pay data, dates, and totals — no personal identifiers beyond names. No emails, phones, addresses, DOB, SSN, etc. present in sample.

File structure

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

Notes: Only three columns contain PII: fullName, gender, and dob. All other columns are organizational data (department, position), employment status (status, pay type), and compensation figures which are not PII under the rules.

File structure

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

Notes: Only columns 1 and 2 contain PII (lastName and firstName). All other columns contain employment data (positions, states, payroll figures) and timestamps — not personal identifiable information per the defined field list. The suffix "JR" in BIDDIX JR is part of the lastName field and does not constitute a separate suffix PII field.

File structure

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

Notes: This is a financial summary table showing employee names alongside monetary values across dates. No identifiable PII fields (email, phone, address, etc.) are present. Employee names appear as row labels but are not mapped to any PII field because they are not structured columns with consistent values across rows. The file only contains transactional data and employee names used as identifiers in a pivot table format.

File structure

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

Notes: Only lastName and firstName columns contain PII. All other columns are employment-related metrics (pay, hours, etc.) and do not contain personal identifying information per the defined field types.

File structure

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

Notes: This is not a PII file; it's a financial summary table showing employee names alongside monetary values across dates. Though employee names appear (e.g., ARD, BENTON, BIDDIX JR), these are not mapped to any PII field categories because the data lacks identifiable personal attributes (email, address, phone, etc.). The structure is purely transactional with no personal contact information, biographical data, or account identifiers. This aligns with the breach context of payroll/accounting records but does not expose directly searchable PII.

File structure

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

Notes: Only columns 0 and 1 contain PII (fullName, lastName). All other columns contain only payment data/timestamps (e.g., pay dates, totals) — no emails, addresses, SSNs, or other PII. The file appears to be payroll summaries with no headers.

File structure

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

Notes: 50 rows shown, 26 columns total. Only columns 1 (firstName), 2 (lastName), 3 (suffix), and 4 (state) contain PII. All other columns are salary/benefits data, timestamps, or counters and are skipped per rules.

File structure

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

Notes: File contains employee payroll data with first and last names in columns 0 and 1. No other PII fields detected in the first 50 rows. Columns 2-8 contain salary amounts and dates, which are financial/transactional and excluded.

File structure

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

Notes: 12 columns total, only columns 0 and 1 contain PII (lastName and firstName). All other columns contain timestamps or totals and are skipped.

File structure

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

Notes: Only two columns contain PII: firstName and lastName. All other columns are timestamps, numeric hours, and totals — no other PII (email, phone, address, etc.) is present in the sample. Grand Total rows contain aggregated numeric data only.

File structure

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

Notes: CSV file with employee payroll data. Contains PII fields for last name, first name, full name, and state. Other columns contain employment-related data that is not PII.

File structure

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

Notes: This is not a PII-containing file. The data appears to be COVID-related expense reports for Forsyth County, GA businesses, listing vendor names (Staples, Comcast, etc.), expense categories, and monetary amounts. No personal identifiable information (PII) such as names, addresses, emails, phone numbers, or other sensitive fields is present. The file structure is purely transactional/financial and does not contain any structured personal data columns.

File structure

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

Notes: 74-column payroll register file from Frosty Acres Brands. Only column 3 (eename) contains mapped PII — full employee names. Remaining columns are payroll/financial transaction data: pay codes, amounts, check numbers, dates, tax codes, direct deposit flags, department codes, and state tax identifiers — all skipped per financial/transactional and internal flag rules.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The sample shows fragmented records with embedded dates and status codes related to FMLA/STD/PTO tracking, but no identifiable column headers or repeated field positions. While there are date strings and status codes, there is no visible PII such as names, emails, or phone numbers in this sample. However, unstructured files may still contain hidden PII; this routes the file through streaming extraction for emails/phones if present.

File structure

Notes: free-form text with embedded dates and codes, no consistent column structure or delimiter. Contains FMLA/STD records with timestamps but no identifiable PII fields like names, emails, or addresses. Classified as unstructured due to lack of row structure.

File structure

Notes: free-form text with no consistent delimiter structure; lines are payroll/FMLA documentation entries with varying formats and no shared column pattern. Contains timestamps and amounts but no identifiable PII in structured columns.

File structure

Notes: This is a free-form text file with no consistent delimiter or row structure. The lines contain embedded personal information such as names and FMLA/STD dates, but there is no column-based structure to map. The sample shows unstructured data with varying content per line, meeting the criteria for unstructured opt-out processing.

File structure

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

Notes: This is a medical/leave record file with no PII columns. All columns contain dates, durations, percentages, and codes related to FMLA/STD leave tracking, but no names, addresses, emails, or other PII. The file appears to be structured but contains only internal operational data (leave status, hours, pay amounts) rather than personal identifiers.

File structure

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

Notes: The provided sample appears to be unstructured free-form text with no consistent delimiter or column structure. The lines contain varied content (FMLA events, adoption records) with no repeating pattern across rows. Though there are timestamps and codes, there is no identifiable PII in these specific rows. Since there is no consistent delimiter or column structure, this is classified as unstructured data. No columns can be mapped to PII fields based on the sample provided.

File structure

Notes: free-form text with embedded dates and pay calculations, no consistent delimiter or row structure. Contains employee pay details but no identifiable PII fields in structured format.

File structure

Notes: free-form text with embedded dates and pay amounts, no consistent delimiter or column structure. Contains employee names (Jennifer Klein), dates, pay amounts, and FMLA/STD tracking — but lacks any CSV-like structure. This qualifies as unstructured content per rules.

File structure

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

Notes: Only column 0 contains PII (fullName). All other columns are time tracking codes, statuses, and numerical values without personal identifiers. The file appears to be a time-off tracking log for employees.

File structure

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

Notes: This file appears to be a payroll or benefits schedule with employee names in column 0 but no identifiable PII fields (email, phone, DOB, etc.). Column 0 contains employee names combined with status labels ("Exempt"), but lacks standalone first/last name separation or other PII. All other columns contain payment codes, dates (in ISO format), amounts, and benefit codes — none map to defined PII categories. No emails, phone numbers, addresses, SSNs, or usernames are present.

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a notes/tracking log for FMLA/STD hours with dates and descriptions, not tabular data

File structure

Notes: This is free-form text with no consistent delimiter or row structure. The sample shows FMLA leave documentation with dates, hours, and pay calculations, but it does not contain any identifiable PII fields like names, emails, or addresses. There are no structured columns to map.

File structure

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

Notes: This file is unstructured records with no personal identifiable information (PII). All columns contain internal flags, timestamps, and numerical values related to leave, pay, and hours. No columns map to email, phone, dob, name, address, ssn, password, username, country, gender, suffix, or facebookId. The content appears to be internal HR records tracking leave types, durations, and pay calculations for employees.

File structure

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

Notes: This file appears to be a structured CSV containing employee leave and payroll information, but none of the columns map to PII fields. All columns appear to contain internal codes, leave types, dates (non-DOB), hours, and monetary values related to payroll calculations. No names, emails, addresses, SSNs, or other PII fields are present.

File structure

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

Notes: This file contains no PII columns. All columns appear to be internal tracking codes, timestamps, and non-personal data related to FMLA/STD leave calculations and pay periods. No emails, names, addresses, phone numbers, DOB, SSN, or other PII fields are present. The values are all dates, codes, hours, and monetary amounts used for internal HR/payroll processing.

File structure

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

Notes: No PII columns detected. All columns appear to be internal tracking fields, timestamps, and financial/leave codes (e.g., FMLA/STD flags, payment amounts, hour counts). Values show leave types, dates, hours worked, and monetary amounts — none contain names, emails, addresses, or other PII. This aligns with the breach context of payroll/HR administrative records without personal identifiers.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. Each row contains unstructured notes and timestamps rather than tabular data with identifiable columns. The sample shows human-readable entries like "FMLA - Covid then Alcohol Recovery" and timestamps, indicating this is not a structured CSV/TSV file. No PII columns can be mapped because there are no consistent columns to analyze.

File structure

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

Notes: This is a structured CSV file, but all columns appear to contain internal tracking codes, dates, duration counters, and monetary values related to FMLA/STD leave calculations. No PII fields (names, emails, addresses, etc.) are present in the visible columns. Columns 0-2 contain employee identifiers and leave types, columns 3-14 contain timestamps, duration counters, and monetary amounts. All columns map to skip categories per exclusion rules (internal IDs, timestamps, transactional data).

File structure

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

Notes: This file contains only employee leave/benefit tracking data (FMLA, STD, PTO calculations) with no identifiable PII fields. All columns represent leave types, duration, monetary values, and status flags — no names, emails, addresses, or other personal identifiers appear in the sample. Columns 0-2 contain employee status codes and descriptions, columns 3-14 contain dates, hours, and monetary amounts related to leave accruals and payments.

File structure

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

Notes: This is not structured data containing PII fields. Column 0 appears to be a description or status field (e.g., "FMLA - Maternity Leave"), and all other columns contain numeric values, codes, or timestamps related to payment/leave calculations. No identifiable personal information (PII) such as names, emails, addresses, etc., is present in the provided rows. The data seems to represent internal HR or payroll processing records without direct PII exposure.

File structure

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

Notes: Only columns 9 (lastName) and 10 (firstName) contain PII. Other columns are timestamps, status flags, or free-text notes about exposure and vaccination status.

File structure

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

Notes: Only columns 0 (fullName) and 1 (dob) contain PII. All other columns represent accrual balances, years of service, and comments — no PII present.

File structure

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

Notes: Only columns 4 (fullName) and 12 (dob) contain PII. All other columns are internal IDs, department codes, pay rates, accrual data, and timestamps — these are skipped per rules. The file appears to be employee payroll/accrual records.

File structure

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

Notes: Only column 3 contains PII (fullName). All other columns are status flags, internal codes, or empty headers (PERSONALYSIS, Dept, Direct Report, etc.). Values in column 11 appear to be dates but are likely internal tracking dates, not DOB, and the header 'Taken' suggests a timestamp — mapped as skip per rules. No emails, phones, or addresses present.

File structure

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

Notes: Only 3 of 11 columns contain PII (lastName, firstName, middleName). Columns 3-10 are non-PII (company, dates, status flags). All rows show employee personnel data from Frosty Acres Brands (F.A.B., Inc.).

File structure

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

Notes: Only column 3 contains clear PII (full names). All other columns either have empty headers or contain non-PII status/role labels like 'Status', 'Dept', 'Direct Report', 'To Supervisor', etc. No emails, phones, DOB, or addresses appear in the sample.

File structure

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

Notes: This is an unstructured free-form text file with no consistent column structure. The data appears to be meeting attendance logs or workshop participant lists with names and dates, but lacks a defined tabular format. There are no identifiable PII columns to map due to the absence of a consistent delimiter and row structure. The content resembles prose rather than structured records.

File structure

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

Notes: This is a financial summary table showing vendor names and monthly fees. No PII fields are present. The columns contain vendor names and numerical fee amounts, but no identifiable personal information such as email, phone, or address. The vendor names appear to be generic identifiers rather than full personal names with additional PII.

File structure

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

Notes: This file contains only vendor names and logistics data. There are no PII fields present. All columns represent company names, vendor IDs, and financial amounts related to logistics vendors. No personal information such as names, addresses, emails, or phone numbers is included.

File structure

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

Notes: This is an Accounts Payable (AP) document listing logistics vendors and associated financial data. The columns contain vendor names, IDs, and monetary amounts, but no PII fields are present. All columns are skipped per exclusion rules (company/business names, internal IDs, financial data).

File structure

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

Notes: CSV file with 50 rows of employee address data. Contains full names, addresses (including apartment/unit info), cities, states, and ZIP codes. All PII fields are mapped; no internal IDs or non-PII fields present in this subset.

File structure

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