merceradvisors.com

File structure

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

Notes: This is a 1099-DIV/1099-B brokerage tax form data file. All columns are financial/transactional (dividends, capital gains, cost basis, shares, wash sales) or payer business information (Robinhood Markets Inc. EIN, address, phone). No personal PII fields (name, email, SSN, personal address, DOB, etc.) are present in this extract.

File structure

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

Notes: This is a structured CSV file containing investment plan data and fee disclosures for 529 college savings programs. There are no personal identifiable information (PII) fields present in the first 50 rows. All columns contain plan names, fee structures, investment options, and reference links — no names, addresses, emails, phone numbers, dates of birth, or other PII.

File structure

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

Notes: This file contains institutional financial data (financial institutions, URLs) and availability information. No personal identifiable information (PII) fields are present. All columns map to institutional or non-PII data such as financial institution names, URLs, state availability flags, and empty fields. No emails, phone numbers, names, addresses, DOB, SSN, passwords, usernames, or other PII fields are detectable.

File structure

Notes: The provided file is a free-form text listing financial institution names, URLs, and login pages without any structured data or PII fields. It contains no identifiable personal information such as names, emails, addresses, etc., and is purely descriptive of retirement plan service providers and their access points.

File structure

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

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

File structure

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

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

File structure

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

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

File structure

Notes: free-form text with embedded emails / phones

File structure

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

File structure

Notes: The provided rows are not structured tabular data; they appear to be free-form text describing investment asset allocations. The content includes textual descriptions and financial values but lacks consistent columnar structure across rows. Since there is no consistent delimiter and each line has a different shape, this qualifies as unstructured data per the rules. No PII columns can be mapped.

File structure

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

Notes: This file contains only financial planning data and calculations (cash flows, portfolio distributions, social security amounts, pension amounts, RMDs). There are no personal identifiers, contact details, or PII fields present. All values appear to be monetary amounts and dates related to financial projections. No columns map to any PII fields defined in the schema.

File structure

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

Notes: The file contains only investment portfolio data (fund symbols, allocations, returns). No personal identifiable information (PII) is present in the visible columns. All entries are financial metrics and fund names, with no names, addresses, emails, or other PII fields.

File structure

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

Notes: No PII found. The file contains only financial transaction data (account numbers, security IDs, quantities, security descriptions, values, costs, and gains/losses). All columns are financial metrics or identifiers with no personal information. The names 'Rob' and 'Jacki' appear to be account holder labels but are not mapped as PII because they are not full names and lack additional identifying information.

File structure

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

Notes: This file appears to be a structured document summarizing insurance policies and does not contain identifiable PII fields such as names, emails, or addresses. All columns appear to represent insurance policy metadata (e.g., policy number, premium, benefit type) and do not map to any PII fields. No emails, phone numbers, or other PII values are present in the sample rows.

File structure

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

Notes: This file contains non-PII financial planning data: categories of expenses and spending plans. No personal identifiers (names, emails, addresses, etc.) are present in the first 50 rows. Columns are either empty or contain generic financial categories and numeric amounts.

File structure

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

Notes: The file appears to be a structured amortization schedule containing only financial calculations (loan amounts, interest rates, payment schedules). There are no personal identifiers such as names, addresses, emails, phone numbers, dates of birth, or SSNs present in the visible data. All columns contain purely transactional/financial data (e.g., 'Term (Years)', 'Interest Rate', 'Monthly Payment', 'Beginning Principal', 'Ending Balance'). No PII fields are detected.

File structure

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

Notes: This is financial investment data with no personal identifiable information (PII). Columns contain account symbols, fund descriptions, share values, and institutional names. The only potential name references ('Rob', 'Jacki') appear to be generic placeholder names for account ownership context, not actual personal names. No emails, phone numbers, addresses, DOB, SSN, or other PII fields are present. All columns map to skip categories: internal IDs, financial/transactional data, timestamps, and institutional references.

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains prose, tabular data fragments, and financial metrics but lacks a repeatable delimiter pattern across rows. While it includes client names (Rob Thomasson, Jacki Cannon) and financial figures, there are no structured columns to map to PII fields. The format does not meet criteria for CSV/TSV parsing — it is better handled by unstructured text analysis pipelines.

File structure

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

Notes: All columns contain investment/fund data (symbols, fund names, allocations, values, returns, categories) with no personal identifiers. No PII fields detected.

File structure

Notes: This is not a structured dataset with columns; it's a free-form financial report/document listing investment sources and uses. The file contains prose and tabular fragments rather than consistent columnar data. No PII columns can be mapped.

File structure

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

Notes: All columns contain financial/stock data (grant dates, share counts, prices, values). No PII fields (names, emails, addresses, etc.) are present. This aligns with the breach context of financial planning documents without client personal details.

File structure

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

Notes: This file appears to be a financial report containing investment allocation data. None of the columns contain PII fields such as names, emails, phone numbers, or other personal identifiers. The data consists of investment categories, numerical values, and timestamps which are not considered PII under the provided criteria. Therefore, no columns map to PII fields.

File structure

Notes: The file is free-form text with no consistent delimiter structure. It contains meeting agenda items and timestamps but no identifiable personal data in structured columns. Given the unstructured nature and lack of repeating columnar format, this should be processed as unstructured text.

File structure

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

Notes: File appears to be a structured CSV with financial planning timeline data. Only columns 6 (fullName) and 7 (dob) contain identifiable PII. All other columns appear to contain internal planning codes, timestamps, or numeric milestones without personal identifiers.

File structure

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

Notes: This file contains only financial transaction headers and placeholder rows. No PII fields are present in the first 50 rows. The columns shown are purely transactional: Date, Account Name, Account Number, Transfer In/Out, Amount, Notes. There are no email addresses, names, addresses, or other personal identifiers in the visible data.

File structure

Notes: This is a free-form meeting agenda text with no consistent column structure or delimiter. It contains headers and bullet points but lacks the tabular format required for column mapping. No PII columns can be identified as there is no structured data to map.

File structure

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

Notes: Only column 6 (Date of Birth) contains valid PII. All other columns are internal planning milestones, age calculations, or generic notes with no personal identifiers.

File structure

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

Notes: This file contains financial portfolio data (holdings, cost basis, values). No PII fields are present. Columns include Holding Name, Ticker, Quantity, Cost, Value, Unrealized Gain/Loss, and percentages. All values are numeric or financial identifiers, with no names, addresses, emails, or other personal data.

File structure

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

Notes: The provided data is a financial portfolio report showing investment holdings and performance metrics. It contains no personal identifiable information (PII) fields such as names, addresses, emails, or phone numbers. All columns represent investment identifiers, quantities, dates, costs, values, and performance calculations, which are classified as non-PII under the exclusion rules.

File structure

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

Notes: The provided rows contain only financial/accounting data (investment strategies, account types, values) with no personal identifiers. No PII fields (email, phone, name, etc.) are present in the sample. All columns are financial metrics or internal labels, and therefore mapped as skip per rules.

File structure

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

Notes: This file contains only financial transaction data with account identifiers and values. No PII fields are present — all columns map to financials, account numbers, or transactional values which are excluded by the rules. The first column appears to be a description/label field without personal identifiers.

File structure

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

Notes: This is a free-form table with no consistent PII columns. The file appears to be a scoring matrix or risk tolerance table used for investment objectives. All values are numerical or categorical risk assessments (e.g., 'Moderate', 'Conservative') and do not contain any personal identifiers such as names, emails, addresses, or other PII fields. The columns labeled 'CLIENT NAME 1' and 'CLIENT NAME 2' are empty in all rows of the sample, confirming no actual client names are present in this dataset.

File structure

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

Notes: This file is a simple table with date ranges and age calculations. There are no columns containing PII fields such as email, phone, name, address, etc. The columns present are From Date, To Date, Age Today, and RMD Age, which are all date-based calculations and do not contain any personally identifiable information. Therefore, no columns map to PII fields.

File structure

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

Notes: Only columns 6 (fullName) and 7 (dob) contain identifiable PII. All other columns are timestamps, derived values, or internal planning metadata. No emails, phones, addresses, or SSNs are present in the first 50 rows.

File structure

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

Notes: This is not PII data; it appears to be a template or header-only snippet showing financial transaction columns (Date, Account Name, Account Number, Transfer In/Out, Amount, Notes). No actual PII values are present in the first 50 rows. Columns like Account Name could theoretically contain client names, but with no data rows to verify, we cannot map any PII fields. Per instructions, only map columns with observable PII in sample values.

File structure

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

Notes: File is a structured CSV with columns: Promises & Sources, empty column, empty column, empty column, Due Date, Subject, Focus, Next Steps, empty column, empty column. No PII detected. Values contain only task management text, dates, and generic placeholders (e.g., ACCOUNTNAMENUMBER, XXXXX). No email addresses, phone numbers, names, or other PII appear. All columns either empty or contain non-PII content per exclusion rules.

File structure

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

Notes: Only columns 1 (fullName) and 7 (dob) contain PII. All other columns are financial calculations, account identifiers, or non-personal metadata (custodian, account type, tax elections, etc.).

File structure

Notes: This is free-form text containing notes and commentary about client insights, investment overview, money movements, and planning assumptions. There is no consistent delimiter structure or row-based data. The content appears to be prose with embedded placeholders rather than structured records containing PII fields.

File structure

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

Notes: This is a free-form text file with no consistent column structure. It appears to be a report or description of age milestones rather than a structured dataset containing personal information. There are no identifiable PII columns present in the first 50 rows.

File structure

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

Notes: This file contains only household names and action item counts. No PII fields are present. The data appears to be a list of client households with counts of tasks, likely for internal tracking purposes. There are no email addresses, phone numbers, dates of birth, or other personally identifiable information in the visible columns.

File structure

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

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

File structure

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

File structure

Notes: File is free-form text with no consistent columnar structure. Contains embedded procedural notes, task templates, and financial planning instructions without delimited fields. Visible PII includes DOB patterns (DDMMYYYY) and placeholder names (XXXXX), but these are not in a structured format.

File structure

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

Notes: Only column 6 (DOB) contains PII. Other columns contain age calculations, date ranges, and client numbering that are not personally identifiable.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The data appears to be financial calculations and account values rather than structured personal identifiable information (PII). There are no visible emails, phone numbers, or other PII in the sample lines. The content consists of numeric values and descriptions of financial metrics like account values, tax withholdings, and distribution amounts.

File structure

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

Notes: This file contains only financial transaction data (distribution amounts, tax withholdings) with no personal identifiers. All columns represent monetary values, percentages, and descriptions of tax calculations — no names, addresses, emails, or other PII present. The header structure confirms it's purely financial reporting with no client identifying information.

File structure

Notes: This is a free-form table of Social Security retirement age thresholds with no personal identifiers. The data consists of age brackets and date ranges, with no names, emails, or other PII fields. The structure is tabular but lacks any identifiable personal data columns.

File structure

Notes: The provided data is a table of metadata describing Excel tabs and cell locations, not actual PII records. It contains references to processes and cell coordinates but no personal data fields. This is structural metadata, not a dataset containing personal information.

File structure

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

Notes: This is a bond investment portfolio file with CUSIP identifiers, holding names, and unstructured notes about bond status and transactions. No PII fields are present — all columns are financial identifiers or narrative descriptions of bond holdings and market conditions. No names, addresses, emails, or other personally identifiable information appear in the first 50 rows.

File structure

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

Notes: Only two columns contain meaningful data: client names and bond identifiers. All client names are fully qualified (Last, First format) and represent PII. Bond identifiers contain no personal information and are skipped per policy.

File structure

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

Notes: This is a financial portfolio CSV with columns describing security descriptions, quantities, cost basis, and valuation data. No PII fields present — all columns are investment identifiers, numeric values, and transaction metadata. No names, addresses, emails, or other personally identifiable data appear in the header or sample values. This matches the breach context of Mercer Advisors (financial statements, tax returns, etc.) but the specific file shown contains only non-PII financial data.

File structure

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

Notes: This file contains only financial investment data (security descriptions, quantities, cost basis, etc.). No PII fields such as names, emails, addresses, or other sensitive personal data are present. All columns relate to financial holdings and calculations, and are therefore skipped.

File structure

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

Notes: This file contains investment/financial data columns only (security descriptions, quantities, cost basis, values, etc.). No PII fields such as names, emails, addresses, or DOB are present in the first 50 rows. All columns relate to financial holdings and transactions, which are excluded by the rules (vehicle/product data, financial/transactional data). Therefore, no PII columns to map.

File structure

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

Notes: Only columns 1 (fullName) and 7 (dob) contain PII. All other columns are financial/tax data, custodian names, internal IDs, or flags — none qualify as personal PII under the rules.

File structure

Notes: The provided text is unstructured free-form notes/comments rather than a delimited data table. The content appears to be narrative commentary about client insights, investment allocations, money movements, planning assumptions, and references to names and dates, but lacks any consistent columnar structure or delimiter. There are no rows with shared field positions or patterns. While the text contains embedded names and dates (e.g., 'NAME', 'MMDDYYYY'), it does not meet the criteria for structured CSV/TSV parsing and should be processed through unstructured text handling.

File structure

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

Notes: This file is not a structured dataset with columns. It appears to be a narrative or age milestone report rather than tabular data with personal identifiers. The content includes age-based tax/estate milestones and client age calculations, but no actual PII fields (names, emails, DOB, etc.) are present in the first 50 rows. No columns map to PII fields.

File structure

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

Notes: Only columns 6 (fullName) and 7 (dob) contain PII. All other columns contain internal task tracking, date stamps, age calculations, and counters — no personal identifiers.

File structure

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

File structure

Notes: This is free-form text with no consistent column structure. The file contains financial planning tasks and email templates, but does not contain any tabular data with PII fields. There are no repeated delimiters or structured rows to parse.

File structure

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

Notes: This is a narrow CSV containing only date-of-birth information. No other PII fields are present in the visible columns. The file appears to be a client age/RMD calculation table from Mercer Advisors' financial records.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The sample shows financial data rows with values and descriptions but no header row or consistent column mapping. Given the context of a ransomware breach containing sensitive financial data, this appears to be a structured data dump presented in a free-text format. However, since there is no consistent delimiter or column structure across rows, this must be processed as unstructured data. The presence of financial values and descriptions confirms this is not prose but structured data in an unconventional format.

File structure

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

Notes: This is a financial distribution/tax data file showing distribution amounts, tax withholdings, and percentages. No personal identifiable information (PII) is present. All columns contain numerical financial/tax data or descriptions, with no names, addresses, emails, etc. This aligns with the breach context of Mercer Advisors containing tax returns and financial statements, but this specific file only contains anonymized financial calculations.

File structure

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

Notes: This file contains only retirement age data tables with date ranges and calculations. No PII fields (names, addresses, emails, etc.) are present. All columns are purely demographic/temporal data used for retirement planning calculations and should be skipped.

File structure

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

File structure

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

Notes: This file contains bond investment data with CUSIP identifiers, holding names, and notes about financial transactions. There are no PII fields present — all columns are financial identifiers or descriptive notes about bond holdings, litigation, and redemption processes. No emails, names, addresses, or other personal data appear in the sample.

File structure

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

Notes: Only column 5 contains PII (fullName). Other columns contain account identifiers, advisor names, CUSIP codes, and commentary — none are personal identifiable information per the defined fields. No email, phone, DOB, address, SSN, etc., detected.

File structure

Notes: This is a free-form text file containing mathematical formulas and financial calculations, not structured data with PII columns. There are no consistent delimiters or row structures across lines, and the content consists of calculations and notes rather than personal information.

File structure

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

Notes: The provided data consists entirely of financial portfolio holdings (security descriptions, quantities, values, etc.) with no personal identifiable information (PII) present. All columns appear to be investment-related metrics rather than client PII fields. No columns map to any of the available PII field types (email, phone, dob, names, addresses, etc.).

File structure

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

Notes: This is not a PII file. The columns contain relationship labels, AUM totals, and other financial/offering metadata. No identifiable personal information (names, emails, addresses, etc.) is present in the visible data. All columns map to skip categories: internal business codes, financial amounts, timestamps, and status flags. No emails, phones, or direct personal identifiers are visible in the sample.

File structure

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

Notes: This file contains only financial aggregates and counts (AUM values, client counts) with no identifiable personal data. All columns represent numerical summaries and timestamps, with no PII fields present.

File structure

Notes: This is a free-form email body with embedded PII (email: screvar@merceradvisors.com, phone: 973.605.8311, address: 67 East Park Place / Suite 700 Morristown, NJ 07960). No consistent columnar structure exists across rows — each line is a different email template with variable fields. This qualifies as unstructured data requiring streaming extraction of emails and phone numbers.

File structure

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

Notes: Only columns 1 (fullName) and 7 (dob) contain PII. All other columns are financial/tax data, internal IDs, or flags — skipped per exclusion rules.

File structure

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

Notes: This file is a structured table of age milestones and related notes, but it contains no personal identifiable information (PII). The columns represent age ranges and milestone descriptions rather than actual client data. No PII fields are present in the sample rows.

File structure

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

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

File structure

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

Notes: Only columns 5 (fullName) and 6 (dob) contain PII. All other columns contain non-PII data such as task descriptions, due dates, age calculations, and timeline references.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. It appears to be a list of financial asset and liability values rather than structured personal data. There are no identifiable PII columns present in the format. The values are numerical amounts with descriptive labels, not containing any names, addresses, emails, or other personal identifiers.

File structure

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

Notes: This file appears to be unstructured financial data records without PII fields. The columns contain numerical values and descriptions related to financial metrics (e.g., pension, salary, total income, savings, debt payments). There are no identifiable PII fields such as names, addresses, emails, phone numbers, DOB, SSN, etc. All columns represent financial aggregates or categories and therefore do not map to any PII field types.

File structure

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

Notes: This is a financial analysis document containing only financial ratios, calculations, and descriptions. There are no personal identifiable information (PII) fields present. All columns contain numerical data, formulas, and textual descriptions of financial metrics rather than any personal data.

File structure

Notes: The file is free-form prose with embedded account numbers, DOBs, and instructions rather than structured records. No consistent delimiter or column pattern exists across lines.

File structure

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

Notes: This appears to be a financial planning dataset with dates of birth. The only PII column is DOB. Other columns like 'Client #01' are internal identifiers and skipped per rules.

File structure

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

Notes: This is a financial data file with account values, tax withholdings, and distribution calculations. No PII fields are present in the sample data. All columns appear to be numerical financial metrics or calculations, with no personal identifying information such as names, addresses, emails, or dates of birth.

File structure

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

Notes: This file contains only financial distribution and tax data. No PII fields (email, phone, name, etc.) are present. All columns represent numerical financial values, percentages, and descriptions of tax distributions. No columns map to any PII categories.

File structure

Notes: This is a free-form table with no personal identifiers. It contains only retirement age thresholds and date ranges, with no PII fields present.

File structure

Notes: The file is a free-form financial calculation spreadsheet with no consistent column structure or identifiable personal data. It contains mathematical formulas and values related to investment calculations (present value, payment amounts, interest rates, etc.), but no PII fields. This is typical of financial modeling documents and not structured personal records.

File structure

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

Notes: This is a bond investment data file with CUSIP identifiers and bond descriptions. No PII fields present. Columns are CUSIP (bond identifier), Holding Name (bond title), and Notes (bond commentary). All values are corporate/financial identifiers and bond commentary, with no personal information.

File structure

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

Notes: Only column 5 (Name) contains PII. All other columns appear to be account identifiers, advisor names, CUSIP codes, and commentary — none contain personal identifiable information. The 'Name' column maps to fullName as it contains full names in 'Last, First' format.

File structure

Notes: This is a free-form text file containing mathematical calculations and financial formulas, not structured data with PII columns. It includes formulas for Time Value of Money (TVM) calculations, present value, payment amounts, future value, and footnotes about inflation-adjusted returns. No consistent columnar structure exists, and no PII fields are present.

File structure

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

Notes: No PII columns detected. The file appears to be a financial summary report with client relationship data, AUM totals, and exit dates. All columns contain business/financial metrics, internal codes, or timestamps rather than personal identifiers. The first column contains formatted names but these appear to be relationship labels ('Poserow - Benjamin') rather than actual personal names, and the structure matches financial reporting conventions from Mercer Advisors breach context.

File structure

Notes: The file appears to be a free-form financial summary report with no consistent columnar structure. It contains cumulative values, year timestamps, AUM (Assets Under Management) figures, and client counts but lacks any personal identifiable information fields (PII) such as names, emails, addresses, etc. There are no repeating patterns or consistent delimiters across rows, and the data represents aggregated financial metrics rather than individual client records.

File structure

Notes: free-form text with embedded emails / phones

File structure

Notes: This is not structured data; the first row appears to be a label ('Data as of:') and the second row a timestamp. Subsequent rows are empty or placeholders. No consistent columnar pattern exists, and no PII is present in the sample. This matches the pattern of unstructured free-form text with no importable structured fields.

File structure

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

Notes: Only two columns contain PII: fullName and dob. All other columns are financial/tax codes, account numbers, or flags — none contain personal identifiers.

File structure

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

Notes: Only fullName and dob contain PII. All other columns are financial/tax data, account identifiers, or flags — no personal identifiers.

File structure

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

Notes: This file appears to be an age milestone report for a client. Only columns 1 (fullName) and 4 (dob) contain PII. All other columns are age milestone markers or empty fields.

File structure

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

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

File structure

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

Notes: This is a financial data file showing account types and monetary values, but no PII fields (names, emails, addresses, etc.). The columns represent account categories (Taxable, Tax-Deferred, Tax-Exempt) and financial metrics (Value, Stock %, Bond %, Stock $, Bond $), which are all transactional/financial data and do not contain personally identifiable information. 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 free-form text file listing asset values and liabilities — no structured columns, just key-value pairs. There is no PII present in this snippet. Given the context of the Mercer Advisors breach, this appears to be a financial summary rather than a client PII dump. No column mapping is possible because the data is not tabular.

File structure

Notes: The provided data appears to be a list of financial values and descriptions rather than structured records containing personal identifiable information (PII). The lines do not follow a consistent delimiter pattern and are more like key-value pairs or notes rather than tabular data with columns. There are no visible emails, phone numbers, or other PII in this sample. Therefore, this is classified as unstructured free-form text with no column mapping possible.

File structure

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

Notes: This file contains financial planning metrics and calculations, not personal identifiable information. No PII fields detected.

File structure

Notes: The file contains unstructured task notes and email templates rather than tabular PII data. It includes placeholders like XXXXX and URLs but no actual personal identifiers in structured columns.

File structure

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

Notes: Only DOB column contains PII. Other columns contain age calculations, date ranges, and client identifiers that are internal IDs or derived values. No emails, names, addresses, or other PII are present in the sample.

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a financial data dump with values and descriptions rather than columnar PII. No email or phone numbers visible in the sample, but the format does not contain any structured columns to map.

File structure

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

Notes: This is a financial tax distribution table with no PII fields. Columns contain tax amounts, percentages, and calculations — no names, emails, addresses, or other PII. The file is purely transactional financial data from Mercer Advisors breach (tax returns, distribution amounts).

File structure

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

Notes: This file contains only aggregated financial data columns (strategy, TPAL Minimum, TPAL Maximum, Median, Minimum, Maximum, Total Portfolio Assets Left) and numerical values. No PII fields are present in the first 50 rows.

File structure

Notes: This is a free-form text file with tabular retirement age data, not structured CSV records. It contains no identifiable personal information (PII) fields like names, emails, or addresses. The content appears to be generic actuarial tables showing Social Security retirement age thresholds by birth year, with no client-specific data exposed in the sample.

File structure

Notes: This is not a structured dataset but a free-form text representation of financial calculation examples. Columns appear to be placeholders or metadata rows with no consistent PII data. The sample rows contain mathematical finance terms (Time Value of Money, Present Value, etc.) and numeric values rather than personal information. No identifiable PII fields are present in the visible structure.

File structure

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

Notes: This is a template expense tracking CSV with budget categories and zero-value placeholders. No PII fields are present — all rows are structured expense line items (e.g., 'Education / Graduate School (All In)', 'Housing / Mortgage'). The file appears to be a generic budgeting template rather than client-specific data from the Mercer Advisors breach.

File structure

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

Notes: This file contains only expense categories and numerical amounts with no personal identifiable information (PII). All columns represent financial categories (Housing, Taxes, Personal, etc.) and monetary values, which are excluded per the rules. No emails, names, addresses, phone numbers, or other PII fields are present.

File structure

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

Notes: The provided data appears to be a simple two-column CSV with financial metrics: Annual Gross Income and Annual Expenses. No PII fields are present in this snippet. The columns appear to be purely financial data and do not contain any personal identifiable information such as names, addresses, emails, phone numbers, dates of birth, etc. All columns map to skip per exclusion rules (financial/transactional data).

File structure

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

Notes: This is a bond portfolio CSV with CUSIP identifiers and notes. No PII fields are present. Columns contain financial instrument identifiers (CUSIP), holding names, and descriptive notes about bond status, litigation, and redemption plans. No personal data such as names, addresses, or contact information is included.

File structure

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

Notes: Only column 5 contains PII (fullName). All other columns appear to be account details, advisor names, CUSIPs, and commentary — no additional PII detected. The file represents client account records from Mercer Advisors with bond/investment details but limited personal identifiers beyond full names in column 5.

File structure

Notes: This is a financial calculation table with no personal data. Contains only mathematical formulas and values for present value, future value, payment amounts, and interest rates. No PII fields present.

File structure

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

Notes: This is a financial statement file showing account balances and fees across multiple accounts. There are no PII fields present in the visible data - all columns contain account names, dates, monetary values, percentages, and timestamps. The file structure shows financial data for Anitas and Manishs accounts with billing periods and values, but no personal identifiers like names, addresses, or contact information appear in the visible rows.

File structure

Notes: The provided content is not structured data but rather an error message from a PostScript interpreter attempting to process an encrypted PDF. It contains no tabular data or PII fields. The message indicates that the PDF was encrypted and redistilling is not permitted, resulting in no PDF file being produced. Therefore, there are no columns to map.

File structure

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

Notes: This is a financial portfolio data file showing investment allocations. No PII fields are present. Columns represent portfolio names, allocation percentages, fund codes, and asset class weights. All entries are numeric or internal codes with no personal identifiers.

File structure

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

Notes: This is a financial portfolio allocation report showing investment asset breakdown. No identifiable personal information (PII) such as names, addresses, or contact details are present in the first 50 rows. The only personal reference is 'Prepared for Manish and Anita Chhabra' which appears to be a header label rather than a structured column. All other data consists of investment categories, fund names, values, and allocation percentages. No columns map to PII fields.

File structure

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

Notes: This is a financial transaction record file with dates, shares, prices, gains/losses, and source types (ESPP, RSU). No PII fields (names, emails, addresses, etc.) are present. All columns are transactional/financial data or empty, per exclusion rules. Therefore, no columns map to PII fields.

File structure

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

Notes: No PII columns detected. This is a financial transaction log showing stock activity (RSU releases, ESPP purchases, dividend payments). Columns contain only activity types, dates, numeric values (cash, shares, share price), and security identifiers. No personal identifiers (names, emails, addresses, etc.) are present.

File structure

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

Notes: This file contains no PII columns. All columns appear to represent financial data, stock grants, vesting schedules, and internal tracking codes. No emails, names, addresses, DOB, SSN, or other personal identifiers are present. The data appears to be structured financial summaries and transactional records rather than client personal data.

File structure

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

Notes: No PII columns identified. File contains only financial calculations, payroll data, and payment dates. All columns are numeric values, timestamps, or generic labels (e.g., 'Net Pay Received', 'Pay Date'). No names, addresses, emails, or other personal identifiers appear in the first 50 rows.

File structure

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

Notes: The file appears to be a financial portfolio statement from Mercer Advisors, not a breach data dump. It contains investment allocations, account values, and asset details but no PII fields. No emails, names, addresses, or other identifiable information are present in the first 50 rows. This is likely a sample of portfolio data rather than breached PII records.

File structure

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

Notes: The file appears to be a loan amortization schedule with no identifiable PII columns. All fields contain numerical financial data, dates, and calculations related to loan repayment schedules. No names, addresses, emails, phone numbers, or other PII fields are present in the visible data.

File structure

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

Notes: This file contains no PII columns. It is a financial projection report showing cash flow needs, portfolio distributions, and social security/pension/RMD amounts for a client couple (Manish and Anita Chhabra) across multiple years. All values are monetary amounts and dates — no names, emails, addresses, or other PII fields are present. The headerless format confirms there are no mappable PII columns.

File structure

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

Notes: The provided data appears to be a loan amortization schedule with columns for payment details, principal, interest, and balance. There are no personal identifiable information (PII) fields such as names, addresses, emails, or phone numbers present in the data. All columns represent financial calculations and timestamps, which do not map to any PII categories listed. Therefore, no PII columns are identified.

File structure

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

Notes: This is not structured PII data; it's a financial statement summary with account names containing personal names (Manish, Anita, Krisha, Mishka). No actual PII fields (email, phone, DOB, etc.) are present. The names appear in account descriptions but are not mapped to firstName/lastName fields because they are not isolated columns and the file lacks consistent column structure for personal identifiers. All columns are skipped per exclusion rules and PII mapping criteria.

File structure

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

Notes: This file contains only financial transaction data (grant/purchase dates, FMV, cost basis, shares, prices, balances). No PII fields (names, emails, addresses, etc.) are present. All columns represent transactional or financial metrics and timestamps, which are excluded per rules.

File structure

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

Notes: No identifiable PII columns found. The file appears to be an amortization schedule containing only loan-related numerical data and dates, with no personal information such as names, addresses, or contact details. All columns represent financial calculations rather than personally identifiable information.

File structure

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

Notes: The file is a financial portfolio summary with no PII fields. Columns contain investment account names (some with personal names like 'Anita's' and 'Manish's'), account balances, growth rates, and portfolio models. No identifiable personal information such as email, phone, address, SSN, or DOB is present. All names appear to be used descriptively for account ownership and do not include full names or other contact details.

File structure

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

Notes: All columns represent financial portfolio data (fund names, returns, percentages). No PII fields present. Columns contain investment identifiers, numeric values, and date timestamps — all excluded per rules.

File structure

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

Notes: This file contains only financial planning data and categories with no identifiable personal information. All columns represent expense categories, amounts, insurance policies, and coverage details without any PII fields like names, addresses, emails, or phone numbers.

File structure

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

Notes: No consistent column headers detected; file appears to be free-form financial data with no structured PII columns. Contains salary/bonus/tax details but no names, emails, or addresses. All values are numeric amounts and timestamps.

File structure

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

Notes: The file appears to be a structured amortization schedule with no personal identifiable information (PII) present. All columns contain financial calculations, dates, and numerical values related to loan amortization. No email addresses, phone numbers, names, addresses, or other PII fields are detectable in the provided rows.

File structure

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

Notes: The file appears to be an amortization schedule containing only financial calculations (principal, interest, payments) without any personal identifiable information. All columns contain numeric financial data and dates rather than PII fields. No email addresses, phone numbers, names, or other PII are present in the visible data.

File structure

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

Notes: This file contains only investment/account data columns (account names, symbols, positions, share counts, values, dates, etc.). No PII fields present. All columns are financial/transactional or internal identifiers and therefore skipped per exclusion rules.

File structure

Notes: The provided data is a financial summary report with structured headers and values but lacks any consistent columnar format across rows. It contains free-form financial metrics and planning data rather than a repeating record structure with PII fields. No columns are defined, and the content is narrative-style financial reporting, not tabular personal data.

File structure

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

Notes: This file contains only financial portfolio data with fund names, percentages, and values. No PII fields (names, emails, addresses, etc.) are present. All columns are financial metrics or fund identifiers, which are excluded per rules.

File structure

Notes: The provided data appears to be a financial statement or investment summary document rather than a structured dataset with personal identifiable information (PII) columns. The rows show financial categories (SOURCES, USES), dates, and numerical values without any consistent personal identifiers like names, emails, or addresses in a columnar format. This appears to be a free-form document containing financial data rather than a structured CSV or tabular dataset with PII columns.

File structure

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

Notes: This is a financial allocation report showing investment style allocations. No PII columns are present. The data contains account names in one cell ('Prepared for Manish and Anita Chhabra'), but this is buried in a free-text cell and not structured as a column. The file lacks any dedicated columns for email, phone, name, address, DOB, etc. All columns appear to be financial metrics or labels.

File structure

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

Notes: This is not a data file but a financial report template or header row. Columns contain investment allocation labels and numeric values, but no actual PII fields. The values appear to be placeholders or example data (e.g., 'Prepared for Manish and Anita Chhabra') that do not represent real records. No email, phone, address, DOB, SSN, or other PII is present in the provided rows.

File structure

Notes: The file is free-form text with no consistent delimiter or row structure. It appears to be a description or summary of financial data categories and sample values rather than structured records containing PII. There are no identifiable columns or consistent format across rows.

File structure

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

Notes: This file contains only financial transaction data (stock holdings, prices, values). No PII fields such as names, addresses, emails, or other personal identifiers are present. All columns represent ticker symbols, quantities, prices, and financial calculations, none of which qualify as PII under the defined rules. The name 'Anita Etrade Brokerage 203' appears to be an account or portfolio identifier, not a personal name, and is therefore excluded per exclusion rules for internal IDs or account descriptors.

File structure

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

Notes: The provided data appears to be financial grant and RSU (Restricted Stock Units) records with no PII fields. Columns contain grant names, financial metrics, dates, and share quantities — all internal business data. No emails, names, addresses, DOB, SSN, or other PII are present in the visible rows. All columns are skipped per exclusion rules (financial/transactional data).

File structure

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

Notes: This file appears to be a financial transaction or portfolio summary CSV containing ticker symbols, descriptions, values, shares, cost basis, gains/losses, prices, and account names. No PII fields (email, phone, name, address, DOB, SSN, etc.) are present. All columns are financial/transactional data and should be skipped per exclusion rules.

File structure

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

Notes: This is a financial portfolio summary showing stock holdings and values. No PII fields are present — all columns are ticker symbols, quantities, prices, and calculations. The 'Exclude' column appears to be an internal flag. All data is transactional/financial, not personal.

File structure

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

Notes: This file contains financial transaction data with no PII fields. Columns include ticker symbols, descriptions, shares, prices, values, cost basis, gains/losses, and account identifiers. No email addresses, phone numbers, names, DOBs, SSNs, or other PII fields are present.

File structure

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

Notes: This is a financial portfolio CSV showing ticker symbols, company names, units held, price, market value, cost basis, and gain/loss across multiple brokerage accounts. No PII is present; all account identifiers appear to be generic labels (e.g., 'MC Etrade Brokerage 1205'). No email addresses, phone numbers, names, addresses, or other personal identifiers are visible in the first 50 rows.

File structure

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

Notes: This is a financial portfolio holdings file showing stocks/bonds with market values, cost basis, and gains/losses. No personal identifiable information (PII) is present - only company tickers, share quantities, and financial figures. All columns are financial transaction data and therefore skip columns per exclusion rules.

File structure

Notes: The provided sample is free-form text with no consistent delimiter or row structure. It appears to be a mix of financial data, transaction notes, and investment summaries rather than a structured dataset with identifiable PII columns. The content includes investment account references, share quantities, financial values, and transaction types, but lacks any consistent format that would allow column mapping to PII fields. Due to the unstructured nature of the data, no column mappings can be applied.

File structure

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

Notes: This file contains only financial data columns (stock symbols, market values, cost basis, gains/losses, units). No PII fields present. Columns represent investment portfolio details from the Mercer Advisors breach, but contain no personal identifiers, names, addresses, emails, etc.

File structure

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

Notes: The file contains investment portfolio data (stocks, bonds, cash) with ticker symbols, values, and transaction details. No PII fields (names, emails, addresses, etc.) are present in the first 50 rows. The header rows describe the structure of the portfolio report, and the data rows contain financial instrument details rather than personal identifying information.

File structure

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

Notes: This file contains only financial portfolio data (account names, values, percentages). No PII fields are present. All columns represent account names (e.g., 'Manish ETRADE 1205'), monetary values, and percentages — none map to email, phone, name, address, DOB, SSN, etc. The header structure indicates a financial summary/report, consistent with the breach context of Mercer Advisors' financial client data. No actionable PII to map.

File structure

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

Notes: This appears to be a financial allocation report with no personal identifiable information (PII) in any column. All columns contain investment allocation data, numerical values, and generic labels. No email addresses, phone numbers, names, dates of birth, or other PII fields are present in the sample data.

File structure

Notes: This is a free-form text file with meeting notes and client data. There is no consistent delimiter or structured column format across rows. The file contains embedded PII such as names and dates of birth, but due to its unstructured nature, it should be processed through a streaming email/phone extractor. The content includes client names (Manish Chhabra, Anita Chhabra, Krisha, Mishka), dates of birth (e.g., 8/18/1975, 5/31/1979), and other sensitive financial planning details.

File structure

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

File structure

Notes: This is not a structured table with columns; it's a free-form document containing financial planning data, stock summaries, and client notes. The values are textual summaries, not tabular data with consistent columns. No column mapping is possible.

File structure

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

Notes: All columns are financial/transactional data (shares, price, value, cost basis, gains/losses) and timestamps. No PII fields present. Acquisition Date is a timestamp, Shares are internal counters, Cap Gain and Source are transactional flags. This matches the breach context of financial statements and investment data without personal identifiers.

File structure

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

Notes: This is an invoice file containing only financial transaction data and account identifiers. No PII fields are present. Columns contain invoice numbers, dates, amounts, account names (which appear to be generic labels like 'Anita's 401k' rather than personal identifiers), and account numbers that are internal system identifiers. No emails, phone numbers, addresses, names, DOB, SSN, passwords, or usernames are visible in the sample data.

File structure

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

Notes: This is a financial portfolio CSV showing brokerage positions (symbols, shares, values, etc.). No PII fields present - only company tickers, financial metrics, and account holder names in a non-PII context ("Anita's Etrade Brokerage", "Manish's Etrade Brokerage (*205)" are account labels, not personal names). All columns map to skip categories: company/business names, financial data, timestamps/flags, and internal IDs.

File structure

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

Notes: This file contains only financial transaction data (ticker symbols, asset classes, cost basis, market values). No personal identifiable information (PII) fields such as names, emails, addresses, or dates of birth are present. All columns are financial metrics or identifiers for investment assets and should be skipped per exclusion rules.

File structure

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

Notes: No PII columns present. All columns contain financial/account data (account names, symbols, positions, share quantities, values, dates as numeric timestamps, price data, ticker symbols). This matches the breach context of Mercer Advisors' financial data — no personal identifiers are included in this sample.

File structure

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

Notes: This file contains only account and investment data. No PII fields are present. Columns map to account names, symbols, positions, and financial values. All columns are skipped per exclusion rules (financial/transactional data).

File structure

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

Notes: No PII columns identified. The file contains only financial portfolio data (stock symbols, quantities, values, gains/losses) and account types. No personal identifiers such as names, emails, addresses, or SSNs are present in the first 50 rows.

File structure

Notes: The sample provided shows no structured data. All rows appear to be placeholder text or non-repeating values, with no identifiable PII fields or consistent column structure. This aligns with unstructured content rather than a delimited dataset.

File structure

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

Notes: This is a structured CSV file with tax/retirement plan exception data. All columns contain informational text about IRS distribution rules and plan types. No PII fields (email, phone, name, address, etc.) are present. Columns describe tax code sections, plan types, and exception conditions — all skip per rules.

File structure

Notes: This is not a structured data file; it's a free-form text containing financial scenario data and calculations rather than personal records. No consistent column structure exists across rows, and the content appears to be financial modeling data (RSA values, tax rates, vesting scenarios) rather than client PII. The data represents financial planning calculations rather than client personal information.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. Each line appears to be a transaction record in a custom format with embedded tabs and no shared column structure across lines. The content includes stock ticker symbols, purchase dates, quantities, and costs, but lacks a consistent CSV or tabular format. The presence of structured transaction data in a non-tabular format qualifies this as unstructured for processing purposes.

File structure

Notes: This file is FREE-FORM INSTRUCTIONAL TEXT, not a structured data export. It contains step-by-step instructions for importing Roth conversion scenario data from eMoney into Excel, followed by financial projection tables with only numerical asset values (years, ages, portfolio balances, tax rates). No PII fields are present — no names, emails, phones, addresses, SSNs, dates of birth, or identifiable personal information. The document is a template/guide, not a data breach record.

File structure

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

Notes: This is a financial data file showing account balances and projections. No PII fields are present; all columns are numeric financial metrics or internal counters. Columns contain values like account balances, growth rates, withdrawal amounts, and inflation-adjusted projections — none map to email, phone, name, address, DOB, SSN, etc. All columns are marked as skip per exclusion rules (financial/transactional data).

File structure

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

Notes: This file contains only asset class and ticker symbol data (financial instrument identifiers). No PII fields are present. All columns map to financial data categories (Asset Class, Ticker) and should be skipped per exclusion rules for financial/transactional data.

File structure

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

Notes: This is a financial projection table with no personal identifiers. Columns represent annuity calculations (payment amounts, rates, years, returns, values) and contain only numeric financial data. No PII fields are present in the first 50 rows.

File structure

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

Notes: This is a structured CSV file, but all columns appear to represent financial planning categories and characteristics rather than personal identifiable information (PII). No columns map to PII fields such as email, phone, name, address, DOB, SSN, etc. The data contains only generic descriptors like 'Grant-making control', 'Privacy level', and tax deduction limits, which are not personally identifying. Therefore, no PII columns are identified.

File structure

Notes: This is a free-form text file containing only the Mercer Advisors color palette and a link, not structured data with columns. No PII is present in this sample.

File structure

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

Notes: The file appears to be purely financial/tax calculation data with no personal identifiable information (PII) columns. All rows contain numeric values, tax rates, scenario labels, and financial calculations — no names, addresses, emails, phone numbers, DOB, SSN, or other PII fields. The only non-numeric entry ('Anita and Manish Chhabra') is a client reference but lacks any contact details or identifiers. This aligns with the breach description of financial/tax documents but contains no directly exposed PII fields in the first 50 rows.

File structure

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

Notes: The file appears to be a financial transaction log containing stock purchase and dividend reinvestment records for Mueller Water Products, Inc. There are no personal identifiable information (PII) fields present in the visible data. All columns contain transactional data (dates, descriptions, amounts, prices, shares, etc.) rather than any personal details such as names, addresses, or contact information.

File structure

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

Notes: This file contains only numerical financial data (tax brackets, income amounts, etc.) with no personal identifying information. All columns appear to represent monetary values or codes rather than PII fields. No emails, names, addresses, or other PII are present in the sample data.

File structure

Notes: free-form text with no consistent delimiter structure; contains financial data but no identifiable PII columns. Sample shows comma-separated values but lacks headers and consistent field positions across rows.

File structure

Notes: The file is unstructured financial data without consistent column mapping. It contains rows of raw financial calculations and pension data rather than personal identifiable information fields. No headers exist and the rows vary in structure and content. This is not a CSV with PII columns to map.

File structure

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

Notes: This file contains only financial market return data and URLs; no PII fields present. All columns represent financial metrics or empty values, and the final column is a URL pointing to a data source.

File structure

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

Notes: This file contains only financial transaction and property sale data — no PII fields are present. All columns are internal financial metrics, timestamps, or company disclaimers. No emails, names, addresses, or other PII appear in the first 50 rows.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The content appears to be a questionnaire or form about home sale exclusions for tax purposes, with no identifiable personal information in the first 50 rows. There are no repeated column patterns or structured data fields.

File structure

Notes: The file is a free-form financial scenario analysis table (not structured PII records). It contains tax rates, calculations, and scenario labels but no personal identifiers. This is a technical document showing option exercise scenarios, not client PII data from the Mercer breach.

File structure

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

Notes: This is a financial planning life expectancy report, not a flat PII database. Rows beyond the first two appear to be report labels and summary rows rather than additional person records. Columns [16]-[18] are actuarial life expectancy lookup tables (age vs. remaining years by gender). Only 4 PII fields are recoverable from the first two data rows.

File structure

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

Notes: This is a structured CSV file, but all visible columns are financial/tax data headers and values (Federal Standard Deduction, State Standard Deduction, tax rates, breakeven amounts). No PII fields are present in the first 50 rows. The columns are empty or contain only financial metadata. Therefore, no PII columns are mapped.

File structure

Notes: This is not structured data with consistent columns. The provided text appears to be a description or metadata about financial scenarios and expenses, not a dataset containing personal identifiable information (PII). There are no columns to map to PII fields, and the content is free-form text rather than tabular data.

File structure

Notes: This file is free-form text with no consistent column structure. It appears to be a report or document containing financial data, but there are no identifiable columns or delimiters. The data is presented as a series of rows with varying content and structure, and no clear PII fields can be mapped.

File structure

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

Notes: This file contains only numeric identifiers and URLs, no PII fields present. All columns appear to be internal reference numbers, financial calculations, or resource links with no personal data.

File structure

Notes: This is a free-form text file containing only Morse code representations and no consistent tabular structure. It lacks any delimited rows/columns and does not contain any readable personal information or structured data fields. The content appears to be purely encoded symbols without any headers or repeating patterns that would indicate a CSV or other structured format.

File structure

Notes: This is a free-form text document containing planning notes and discussion points rather than structured tabular data with PII columns. No consistent delimiter or column structure exists across lines.

File structure

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

Notes: No PII columns detected. The file appears to be structured financial/mortgage data (loan values, dates, balances) with no personal identifiers. All visible values are numeric, dates, or generic financial terms. No email, phone, name, address, or SSN patterns observed in the first 50 rows.

File structure

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

Notes: This is a free-form table explaining tax implications of different equity award types. No PII columns are present. The structure is informational only.

File structure

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

Notes: This is not a PII-containing file. The data appears to be financial/tax reference values (tax rates, wage bases) and numerical data with no personal identifiers. All columns represent tax/calculation fields, not personal data.

File structure

Notes: free-form text with no consistent column structure; contains financial planning scenarios and calculations but no identifiable PII columns

File structure

Notes: free-form text with no consistent delimiter structure; contains client data and calculations but not in tabular format

File structure

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

Notes: The file contains financial modeling data and stock grant information, but no personal identifiable information (PII) is present. All visible data pertains to financial metrics, stock grants, and company information, with no names, addresses, contact details, or other PII fields.

File structure

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

Notes: This is purely financial calculation data with no PII present. Columns contain stock options metrics, tax calculations, and financial figures with no names, addresses, or personal identifiers.

File structure

Notes: This is a financial planning document (pension/annuity analysis spreadsheet) for clients Anita and Manish Chhabra, not a delimited data export. The file contains embedded PII (full names, dates of birth: 1979-05-31, 1975-08-18) but has no consistent row structure or column headers. The content is a Mercer Advisors pension analysis report with financial projections, assumptions, and scenario calculations. No structured PII columns can be reliably extracted; the names and DOBs appear as free-form text in the document body rather than in parseable fields.

File structure

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

Notes: No structured columns detected; file appears to be free-form text containing financial planning calculations and annuity data. No consistent delimiter or header structure present across lines. Contains no PII fields in structured format.

File structure

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

Notes: No PII columns detected. The file appears to be a financial projection or retirement planning illustration with numeric values, dates, and descriptive text. No personal identifiers such as names, emails, phone numbers, addresses, or SSNs are present in the first 50 rows provided.

File structure

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

Notes: No identifiable PII columns detected. The file contains only financial modeling data, dates, and numerical calculations without any personal identifiers, names, addresses, or contact information. All values appear to be scenario-based financial projections and assumptions.

File structure

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

Notes: No PII present. File contains financial modeling data (dates, numerical values, scenario calculations) with no identifiable personal information. Timestamps, financial figures, and labels like 'Anita and Manish Chhabra' are not structured PII columns.

File structure

Notes: This is free-form text with pension calculation tables and no consistent columnar structure. While it contains names (e.g., "Anita"), there is no repeating pattern or delimiter to map to columns. The document appears to be a template or instructional text for pension benefit calculations rather than structured client records. Per rules, unstructured files with no consistent delimiter and varying line shapes should be processed through streaming extraction for any embedded emails/phones (none found here).

File structure

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

Notes: This file contains only financial data columns (Age, Factor, QLAC, RMD, Growth, etc.) with no PII fields present. All columns appear to be numeric financial metrics with no personal identifiers.

File structure

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

Notes: This file is a structured expense tracking template with categories and amounts. No PII fields are present — all columns represent financial categories, amounts, frequency codes, and flags. No names, addresses, emails, or other personal identifiers appear in the first 50 rows.

File structure

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

Notes: This is a financial mortality table with age factors and RMD age data. No personal identifiable information (PII) is present in any column. All columns represent actuarial data (age, mortality factors, dates of birth ranges for RMD calculations) and do not contain names, addresses, emails, phone numbers, SSNs, or other PII fields. Therefore, no columns map to PII fields.

File structure

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

Notes: This is not structured PII data; it's a financial modeling or tax scenario table with headers describing financial metrics (Fair Market Value, tax rates, etc.) and sample scenario inputs (numbers, 'MFJ' for married filing jointly, 'ßSelect Year'). No actual personal identifiers appear in the first 50 rows. The file appears to be internal financial calculation templates rather than client records containing PII.

File structure

Notes: The file appears to be unstructured data. The rows contain mixed content with no consistent delimiter or column structure. The data seems to represent financial scenarios and calculations (e.g., 'Fair Market Value at Vesting', 'Number of Shares/Units', tax rates), but there are no identifiable PII fields in the visible sample. No consistent mapping to PII columns is possible.

File structure

Notes: The provided data is free-form text with no consistent column structure. It appears to be an investment illustration report from Mercer Advisors, containing calculations and assumptions for different tax scenarios. There are no identifiable PII columns in this structured format. The content is purely informational and contains no personal data fields.

File structure

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

Notes: This is a financial planning questionnaire template with no personal data columns. All rows appear to be static questions and calculations about Roth IRA distributions, with no identifiers or PII fields present.

File structure

Notes: free-form text with no consistent column structure; contains financial planning instructions and scenario calculations without identifiable personal data in columnar format

File structure

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

Notes: The provided data is unstructured and contains no consistent column mappings. It appears to be a mix of free-form text, headers for a tax calculation table, and sample data rows without identifiable personal information (PII). There are no columns that map to PII fields such as email, phone, dob, names, addresses, etc. The data seems to be a template or example for tax rate calculations rather than actual client records.

File structure

Notes: This file is unstructured text — the sample rows appear to be human-readable instructions and labels rather than tabular data. The content contains no consistent delimiter, no repeating column structure, and includes prose like 'Instructions: copy & paste data here, in cell A1.' This matches the unstructured opt-out criteria (a) no consistent delimiter, (b) every line has a different shape, and (c) no visible emails/phones in the sample rows.

File structure

Notes: This is unstructured financial modeling data with no consistent column structure or PII fields. The data appears to be a financial modeling template showing tax calculations, stock options, and other investment metrics. There are no identifiable personal information fields present in this structured financial data format.

File structure

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

Notes: This file contains purely statistical Social Security COLA (Cost-of-Living Adjustment) data series — years, percentages, benefit amounts. No personal identifiers present. All columns represent aggregated financial data, not client-specific PII. No mapping to any PII field required.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The data appears to be a mix of chart instructions and color coding rather than structured PII records. No importable columns exist.

File structure

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

Notes: This file appears to be structured financial data showing Social Security wage bases and weights over multiple years. There are no identifiable personal information (PII) fields present in the first 50 rows. All columns contain year, wage base amounts, and statistical weight values — no names, addresses, emails, phone numbers, or other PII. The data represents historical Social Security contribution limits and statistical weights for wage indexing, not individual client records.

File structure

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

Notes: This file contains only financial and actuarial data tables (earnings, PIA calculations, WEP reductions). No personal identifiable information (PII) is present. All columns represent year data, earnings figures, and pension calculations without any names, addresses, emails, or other PII fields.

File structure

Notes: The file is unstructured financial planning data with no consistent column structure. It contains calculations and notes about tax scenarios, investment values, and assumptions. There are no identifiable PII columns in the structured sense, only free-form text and numerical calculations. This is typical of Mercer Advisors' financial planning reports and does not contain personal identifiers in a tabular format.

File structure

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

Notes: File is unstructured financial data report with no consistent columnar format. Contains prose descriptions, tables, and financial breakdowns rather than discrete PII fields in columns. No mappable PII columns detected.

File structure

Notes: This is a free-form text file with no consistent delimiter or row structure. The content appears to be financial asset mix data with numerical values and headers, but there are no identifiable personal information columns or structured rows. The format does not contain any PII fields.

File structure

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

Notes: This is an unstructured file with no consistent column structure. The rows appear to be financial data entries with varying fields and no identifiable PII columns. There are no headers, and the data format varies per row with no repeating patterns that map to PII fields. No emails, phone numbers, or other PII are visible in the sample.

File structure

Notes: This is an unstructured dataset. The rows contain only numeric financial figures and labels like 'Wages', 'Interest', 'Ordinary Dividends', and no identifiable personal information or consistent structure. There are no email addresses, phone numbers, or other PII visible in the sample. The data appears to be financial transaction totals rather than client records.

File structure

Notes: This is a free-form text file containing tax withholding tables and financial calculations. No consistent column structure exists — lines vary in length and content, and the data appears to be formatted tables with headers like "Wages", "Deductions", and "Net Wages". While the file is sensitive financial data from the Mercer Advisors breach, it does not contain any structured PII fields like names, emails, or addresses in a columnar format. The content is purely numerical and tabular financial data.

File structure

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

Notes: This file contains only financial/transactional data (account balances, income figures, tax savings, basis values). No PII fields are present. All columns map to financial metrics, internal counters, or empty fields.

File structure

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

Notes: No consistent PII columns detected. The file appears to be structured financial modeling data with no identifiable personal information in the first 50 rows. Contains only numerical calculations, years, and financial metrics without any names, addresses, emails, or other PII fields.

File structure

Notes: The provided data appears to be a free-form text file with no consistent delimiter or structured columns. The content seems to be a form or questionnaire related to home sale exclusion calculations, with no identifiable PII fields in a structured format. While there are some fields that could potentially contain PII (like names), the data is presented in a narrative, unstructured manner without clear column mappings. Given the unstructured nature and lack of consistent delimiters or row structures, this should be processed as unstructured text.

File structure

Notes: This file is unstructured free-form text with no consistent delimiter or column structure. It appears to be a mix of client names, birth dates, and financial figures presented in a narrative format rather than a tabular structure. The sample rows show varying content and structure, with no repeated headers or consistent column positions. The presence of names with birth dates (e.g., "Manish - 8/18/1975 (49)") and financial data indicates PII is present, but requires unstructured processing to extract emails, names, and dates.

File structure

Notes: The file appears to be free-form text with no consistent column structure. The provided sample rows contain only placeholder characters (â, à) and static text strings that do not represent structured data. There are no identifiable PII fields in this sample. Based on the context of the Mercer Advisors breach, this may be a header row or placeholder file, but it lacks any usable columnar data.

File structure

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

Notes: All columns are policy/plan documentation fields describing IRS tax exceptions for early distributions. No personal identifiers (PII) appear in headers or sample values. This is purely regulatory/tax guidance content from Mercer Advisors' breach archive.

File structure

Notes: The file appears to be free-form text with no consistent column structure. The sample rows show financial planning scenario data (Fair Market Value of RSA at Grant, Number of Shares/Units, Years to Vest, etc.) but lack any identifiable PII fields or structured delimiter patterns. This is consistent with financial modeling tables rather than client PII data.

File structure

Notes: The file is a free-form text dump of investment transactions with no consistent column structure. It contains stock ticker symbols, purchase dates, quantities, and cost basis data. No PII is present in the visible sample rows. The format appears to be a series of lines with ticker symbols and formatted transaction strings, not a structured CSV with columns.

File structure

Notes: File is NOT DATA. This is a prose document containing instructions for copying Roth conversion scenario data from eMoney financial planning software into Excel. Content is free-form text (procedural steps) followed by a financial planning spreadsheet template with headers and numerical portfolio projections. No PII fields are present. No structured records containing personal identifiable information exist in this file.

File structure

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

Notes: This is purely financial/accounting data with no personal identifiers. Columns contain balance calculations, growth rates, withdrawal amounts, and inflation-adjusted projections — all numeric financial metrics. No names, emails, addresses, or other PII appear in the sample rows.

File structure

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

Notes: This file contains only asset class and ticker information. No PII fields are present. The data appears to be investment fund identifiers and categories, not personal client data.

File structure

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

Notes: This file contains only financial calculation data (annuity amounts, rates, years, values). No PII fields are present. Columns represent internal financial metrics and identifiers (FIA #1, FIA #2, FIA #3) which are internal reference codes, not personal identifiers. All values are numeric or scientific notation representing monetary amounts, percentages, or counts.

File structure

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

Notes: This file contains only categorical data about charitable giving structures and thresholds. No PII fields are present. All columns describe grant-making control levels, privacy ratings, tax deduction limits, and special features — none contain personal identifiers, names, addresses, or sensitive data. This appears to be a reference or informational table rather than client-specific records.

File structure

Notes: The provided data is not structured tabular data; it appears to be a color palette definition for Mercer Advisors with hex codes and RGB values, followed by a link. There are no consistent columns or delimiters, and the content is purely descriptive (colors, HEX codes, RGB values, and a URL). This is not a dataset containing personal information in rows/columns format.

File structure

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

Notes: This file contains purely financial/tax calculation data (stock options, tax rates, proceeds, gains/losses). No PII fields (names, emails, addresses, SSNs, etc.) are present. All columns are numeric financial metrics, scenario labels, or tax calculations. The single name 'Anita and Manish Chhabra' appears in a non-structured context and is not part of a consistent column pattern.

File structure

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

Notes: The file contains structured financial transaction data (stock purchases and dividend reinvestments) but lacks any personally identifiable information (PII) such as names, addresses, emails, etc. All visible columns represent transactional details (dates, descriptions, amounts, share prices) which are not classified as PII under the provided categories. No emails, phone numbers, or other PII fields are present in the sample.

File structure

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

Notes: This file contains only numeric financial data (tax amounts, income figures) with no personal identifiers. All columns represent monetary values (e.g., 2017, 2018 s/m, 2019 s/m etc.) with no names, emails, addresses, or other PII. This appears to be tax return income/wage data without client identifiers.

File structure

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

Notes: This file appears to be a simple financial data record with no identifiable personal information (PII). The columns contain only tax-related numerical values and flags, with no names, addresses, emails, or other PII fields. No columns map to PII fields based on header names or sample values.

File structure

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

Notes: The file appears to be a financial data file containing columns like CSRS, Credit, Years, Avg High 3 Wage, etc. There are no identifiable PII fields such as names, emails, addresses, phone numbers, DOB, SSN, etc. All columns appear to be internal financial metrics or identifiers and should be skipped.

File structure

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

Notes: This file contains only financial market data and URLs — no PII fields. All columns represent financial indices, bond rates, and a reference URL. No personal information is present.

File structure

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

Notes: This is a financial planning worksheet with columns representing transaction amounts, percentages, and calculations. No personal identifiable information (PII) such as names, addresses, emails, phone numbers, dates of birth, or social security numbers are present. All columns are financial metrics, timestamps, or generic labels and therefore map to skip categories per the exclusion rules.

File structure

Notes: This is a free-form text file with no consistent delimiter or row structure. The content appears to be questionnaire text about home sale exclusions and tax rules, not structured data with columns. There are no identifiable PII patterns in a columnar format.

File structure

Notes: The file is a free-form text document with no consistent column structure. It appears to be a financial modeling spreadsheet or report discussing stock options, tax rates, and calculations. There are no identifiable PII fields in structured columns; any personal data would be embedded in prose and requires unstructured extraction.

File structure

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

Notes: This appears to be a financial planning / life expectancy projection report (likely a Salesforce or wealth management tool export) for clients Anita and Manish Chhabra. Many columns are actuarial/calculation fields (Life Expectancy, Age Beg Yr, Mths Left, Age Today, Male/Female actuarial tables) and are non-PII. Column [3] 'First Name' contains some mixed label rows alongside actual first names. Column [12] 'Male/Female' is a duplicate actuarial table column (values are also 'F'/'M') — mapped same as [7] but omitted as it appears to be a redundant actuarial label rather than a client gender field for a different individual.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The lines appear to be key-value pairs or notes about tax settings (Federal Standard Deduction, State Standard Deduction, tax rates, etc.) rather than a delimited dataset with repeated rows of personal information. There are no repeated column patterns or structured records containing PII fields such as names, emails, addresses, etc. Therefore, this is classified as unstructured text with no importable columns.

File structure

Notes: free-form text with no consistent delimiter or row structure; contains prose descriptions and financial scenario headers, not tabular PII data

File structure

Notes: This is an unstructured file with no consistent column structure. The data appears to be a mix of textual descriptions, financial calculations, and tabular data without a fixed delimiter or header row. While there are no obvious PII fields like emails or phone numbers in the visible sample, the unstructured nature of the file means it should be processed through a free-form text extractor to identify any embedded personal information.

File structure

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

Notes: This file contains only numeric and URL data. No PII fields identified. Columns appear to be numeric identifiers, monetary values, and a static URL to a Social Security Administration statistics page. All columns are marked as skip per exclusion rules (internal IDs, financial/transactional data, and non-PII URLs).

File structure

Notes: The provided text is a representation of Morse code symbols and does not contain any structured data or identifiable columns. It appears to be an encoded message or placeholder rather than actual breach data. There are no CSV or tabular structures, and no PII can be extracted from this format.

File structure

Notes: free-form text with embedded emails / phones

File structure

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

Notes: File appears to be loan amortization schedule with two PII rows (5,6) containing client names. All other columns are loan accounting data (dates, balances, payments) and corporate footer text. Only rows 6 and potentially others with similar pattern contain PII.

File structure

Notes: free-form text with no consistent column structure — appears to be a description of employee equity award tax rules rather than structured PII data. No identifiable columns or rows present.

File structure

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

Notes: This file appears to be a financial data table related to stock options or employee compensation, showing year-over-year values for metrics like grant/exercise price, fair market value, number of exercisable shares, and SS wage base. There are no PII fields (names, emails, addresses, DOB, SSN, etc.) present. All columns contain numeric or descriptive financial/tax data. The first few rows appear to be a header-like row with column descriptions, but these are not actual column names and do not map to any PII fields. The data rows contain only numeric values and years, with no personal identifying information.

File structure

Notes: free-form text with no consistent column structure; appears to be a financial planning illustration report rather than a delimited dataset with PII columns

File structure

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

Notes: The file is not structured with consistent columns. It appears to be a free-form text representation of a financial planning scenario, containing calculations and notes rather than discrete PII fields. There are no identifiable columns mapping to PII fields in the first 50 rows.

File structure

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

Notes: This file contains only financial modeling data and metadata (grants, pricing, valuation metrics). No PII fields are present in the first 50 rows. The rows contain financial calculations, stock data, and grant information without any personal identifiers such as names, addresses, emails, or phone numbers.

File structure

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

Notes: This is a financial modeling spreadsheet showing option exercises and tax calculations. No PII fields detected. Columns contain financial metrics like exercise prices, shares, bargain elements, basis, taxable income, AMTI, proceeds, and gains/losses. All values are numerical or generic financial terminology with no names, addresses, dates of birth, or other personal identifiers.

File structure

Notes: This file is NOT a structured data table. It is a pension calculation worksheet / financial planning document for clients Anita and Manish Chhabra. The content is semi-structured with embedded names and dates (DOBs: Anita 1979-05-31, Manish 1975-08-18) mixed with pension scenario analysis, calculations, assumptions, and disclaimers. No consistent delimiter or column header structure exists across rows. While PII is present (names, dates of birth), this is a narrative financial document, not a delimited record file. Route through unstructured email/phone extractor or manual review; do not attempt CSV parsing.

File structure

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

Notes: No PII detected in first 50 rows. File appears to be structured financial projection data (annuity values, dates) without any personal identifiers. All rows contain only numerical values and generic labels like 'Single Life Annuity' or date ranges. No emails, names, addresses, or other PII fields present.

File structure

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

Notes: The file appears to be a financial projection or retirement planning spreadsheet rather than a breach data dump containing PII. It contains only numerical financial projections, dates, and financial scenario labels. No personal identifying information (names, addresses, emails, etc.) is present in the first 50 rows. The data structure shows financial modeling columns (NPV Date, Start Date, Discount Rate, COLA, Pensioner benefits, etc.) and scenario comparisons, but no PII fields.

File structure

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

Notes: The file contains financial modeling data with no PII fields. Columns include NPV Date, Start Date, Discount Rate, COLA, Date of Death, Pensioner, Spouse, Benefit, etc. No names, addresses, emails, phone numbers, SSNs, or DOBs are present.

File structure

Notes: This file is not a structured data table. It is a financial planning document (Net Unrealized Appreciation illustration) for clients 'Anita and Manish Chhabra' generated by Mercer Advisors. The content consists of free-form prose text, legal disclaimers, and financial projection tables that are part of an estate/tax planning analysis document, not a delimited PII export. No consistent row-by-row PII records exist. This is a PDF-to-CSV conversion artifact; the underlying document is advisory content, not a data breach export of personal records in tabular form.

File structure

Notes: free-form text with no consistent delimiter structure — contains pension calculations and placeholders like 'Client 1' without actual PII values. No importable columnar data present.

File structure

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

Notes: This is a financial projection table with no personal identifiers. Columns contain age brackets, financial factors, QLAC amounts, RMD calculations, growth rates, and balance projections — all internal financial modeling data. No PII fields present.

File structure

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

Notes: This is a budget/expense tracking file with categories and amounts. No PII fields are present. Columns contain only expense categories, amounts, frequency codes, and notes — none map to personal identifiers.

File structure

Notes: This is a life expectancy or annuity factor table with no personal identifiers. It contains only age ranges, calculation factors, and retirement age references. No PII fields are present.

File structure

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

Notes: This is not a data file with PII columns. The sample rows show only scenario-based financial modeling numbers (shares, tax rates) and placeholder values ("ßSelect Year", "ßSelect Filing Status"). No personal identifiers (email, phone, name, etc.) appear. The headers are empty or describe financial modeling columns. Therefore, no PII columns to map.

File structure

Notes: This is not a structured dataset but appears to be a description or header row from a financial planning scenario document. There are no actual data rows provided in the sample, only column labels and sample scenario values. The content describes tax rates, vesting scenarios, and filing statuses rather than containing any personal identifiable information (PII). No consistent delimiter or row structure exists in the provided data.

File structure

Notes: The file is unstructured free-form text with no consistent columnar structure. It contains general financial planning scenarios and tax calculations, but no identifiable PII fields in a tabular format. The content appears to be a financial illustration note rather than a data export with personal records.

File structure

Notes: The provided data is a free-form table containing financial planning questions and calculations for Roth IRA distributions. There are no consistent column headers or structured PII fields like names, emails, or addresses. The content appears to be a template or form with financial calculations and tax-related information, not containing any personal identifiable information in structured columns. Therefore, this is classified as unstructured text with no column mapping required.

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a narrative or instructions page about Roth conversion scenarios rather than structured data records

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The content appears to be a mix of header-like lines, tax rate tables, and legal disclaimers rather than a structured dataset with columns. There are no repeating patterns that would indicate CSV/TSV/pipe-separated columns. While there are numbers and dates, they represent tax calculations rather than personal PII fields. No emails, phone numbers, or other PII are visible in the sample.

File structure

Notes: This is a README or instruction file, not structured data. Contains instructions to copy and paste data into cell A1, with no actual PII present in the sample rows. The content is purely procedural guidance for data handling.

File structure

Notes: free-form text with embedded emails / phones

File structure

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

Notes: This file contains structured financial data about Social Security cost-of-living adjustments (COLA) over multiple years, but no personal identifiable information (PII) fields. All columns appear to be numeric or categorical data related to benefit calculations, years, and age-based benefit amounts. No email addresses, phone numbers, names, addresses, dates of birth, or other PII fields are present.

File structure

Notes: This is free-form text with no consistent columnar structure. The file appears to be a README or instructional content rather than structured data containing PII. The sample shows color-coding instructions and life expectancy notes without any identifiable personal information in a tabular format.

File structure

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

Notes: The file contains structured data with columns: Wages from period ranges, year, SS Wage Base, Weight, SS Earnings. None of these columns contain PII fields. The data appears to be historical Social Security wage base statistics, not individual personal data. No email addresses, phone numbers, names, addresses, or other PII are present in the sample rows.

File structure

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

Notes: This is a financial data file containing pension calculations and earnings data. No PII fields are present in the first 50 rows. Columns contain years, earnings figures, pension calculations, and rates — all non-personal financial data. No names, addresses, emails, or other personally identifiable information appear in the visible structure.

File structure

Notes: The provided data is unstructured and consists of prose, notes, and financial calculations rather than a delimited dataset with columns. There are no consistent delimiters or row structures across the lines, and the content appears to be explanatory text about investment scenarios and tax calculations. Therefore, no column mapping can be performed.

File structure

Notes: free-form text with embedded names and financial data, no consistent delimiter or column structure

File structure

Notes: free-form text with no consistent delimiter structure; appears to be financial modeling data (asset mix percentages) rather than personal records. No PII columns present.

File structure

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

Notes: This is an unstructured financial data file showing tax line items (Wages, Interest, Dividends) with numeric amounts. No personal identifiers (names, emails, addresses, etc.) are visible in the first 50 rows. The rows show only numeric values and category labels, with no consistent columnar structure for PII fields. The format appears to be a simple ledger or accounting export with no headers or identifiable fields.

File structure

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

Notes: This file appears to be a financial data dump with only numeric values and minimal structure. No personal identifiable information (PII) is present in the visible columns. The data appears to represent financial figures (wages, interest, dividends) rather than any personal information. The columns contain only numeric values and category labels without any names, addresses, or other PII fields.

File structure

Notes: This is a free-form text file containing tax withholding tables and financial calculations. It lacks consistent columnar structure and appears to be a formatted report rather than structured data rows. No PII columns can be mapped as the content is purely financial calculations and tables without identifiable personal data fields.

File structure

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

Notes: No PII columns detected. All columns contain financial metrics (age, values, gains/losses, tax savings, basis), counters, and empty fields. No names, emails, addresses, DOB, SSN, phone numbers, or other PII present in the first 50 rows.

File structure

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

Notes: The file appears to be a financial planning spreadsheet with no identifiable personal information. Columns contain empty strings, timestamps, and financial parameters. No PII fields detected.

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The data appears to be a narrative or form-like description of a home sale scenario rather than a structured dataset with columns. There are no repeated patterns of commas, tabs, or other delimiters across lines, and the content varies significantly line-to-line. While there are numeric values and some keywords, the layout does not conform to a CSV, TSV, or similar structured format. The presence of embedded values like 'Single', 'Yes', and 'No' does not establish a columnar structure, as they appear within prose descriptions.

File structure

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

Notes: This file contains only financial/accounting data (account names, values, tax codes). No PII fields present. All columns map to skip per exclusion rules (company/business names, financial/transactional data).

File structure

Notes: This is a payroll projection report with no structured columns containing PII. The file consists of financial data and calculations (earnings, deductions, taxes, net pay) without any personal identifiers such as names, emails, or addresses. The format is a free-form text document with tabular data but lacks any header or consistent column structure that would map to PII fields.

File structure

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

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

File structure

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

Notes: Only first and last name columns contain PII. Position and Team are role/organizational data and are skipped per exclusion rules.

File structure

Notes: This is a financial transaction file containing investment account details and holdings. The data appears to be free-form text with no consistent delimiter structure across lines. While it contains account names that might resemble personal names (e.g., "JEFFRI COX", "MARILYN K COX"), these are embedded within account identifiers and not presented as structured columns. There are no emails, phone numbers, or other PII visible in the sample. The format does not conform to a standard CSV/TSV structure with repeating columns; each line represents a separate transaction record with variable components.

File structure

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

Notes: This file contains structured financial transaction data (crypto trades) with no PII fields. Columns represent property quantity, symbols, dates, monetary values, and tax metadata. No personal identifiers (names, emails, addresses, etc.) are present in the sample rows.

File structure

Notes: This is a free-form financial report with no consistent column structure. It contains financial categories, net values, and notes about investments and retirement progress, but does not contain any identifiable personal information such as names, addresses, emails, or other PII fields in a structured format. The data appears to be summary-level financial analysis rather than individual client records.

File structure

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

Notes: 6 rows shown, 2 PII columns identified. Column 'Age' is age but not DOB, so skipped. 'Relationship' is relational status, not a PII field. 'Location' contains city/state but not full address, skipped. 'Occupation' is not PII. 'Notes' is free-text, skipped.

File structure

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

Notes: No PII columns detected. All columns appear to be financial/transactional data (property addresses, values, dates, loan terms, percentages) or internal identifiers. No emails, phones, names, DOB, SSN, etc. present in the sample. This aligns with breach context of financial planning data (tax returns, estate planning, brokerage statements) where sensitive personal identifiers may be stored elsewhere in the archive.

File structure

Notes: The provided data is free-form text with no consistent delimiter structure. It contains financial planning and asset details rather than structured PII fields. While it includes names (Alan, Twila) and potentially sensitive financial data, there is no consistent columnar structure to map. The document appears to be a financial summary or expense report rather than a dataset with importable PII columns.

File structure

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

Notes: This is not structured PII data; it's purely financial projections/projections table with years as columns and monetary values as rows. No personal identifiers present. All columns contain numeric financial figures or category labels, not names, addresses, emails, etc. The headerless format shows year columns (2026-2050) with monetary values — typical financial modeling sheet, not client PII.

File structure

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

Notes: This file contains only financial modeling data (projected expenses) with no personal identifying information. All columns appear to represent numerical financial projections for different years (2026-2050) with no names, addresses, or other PII present. The first row appears to be category labels (e.g., 'EXPENSES'), but these are not personal data categories.

File structure

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

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

File structure

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

File structure

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

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

File structure

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

Notes: No PII columns detected. All columns represent financial transaction categories (e.g., Mortgage, Taxes, Groceries) and numeric spending values. No names, emails, addresses, or other PII fields present.

File structure

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

Notes: This file is a financial transaction log containing only transaction data (dates, merchants, categories, account types, amounts). No personal identifiable information (PII) such as names, email addresses, phone numbers, or addresses is present in the provided rows. All columns are transactional or business-related and do not map to any PII fields defined in the schema.

File structure

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

Notes: This is a financial transaction summary with categories and amounts. No PII fields (names, emails, addresses, etc.) are present. All columns contain transaction categories, monetary values, and notes about accounting status. No columns map to email, phone, dob, name, address, ssn, password, username, gender, suffix, or country.

File structure

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

Notes: The provided data is a structured CSV file containing transaction records. However, after careful examination of the column names and sample values, none of the columns map to any of the defined PII fields. The columns appear to contain transactional data such as dates, merchant names, categories, account types, transaction amounts, and notes, but do not include any personally identifiable information such as email addresses, phone numbers, dates of birth, names, addresses, social security numbers, passwords, usernames, or other specified PII fields. Therefore, no PII columns can be identified in this dataset.

File structure

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

Notes: This is a category mapping file, not containing personal data. Columns represent transaction categories and groups, with no PII fields present.

File structure

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

Notes: This file appears to be a categorization or grouping list rather than structured personal data records. It contains only category names (e.g., 'Auto', 'Clothing', 'Income', etc.) with no actual PII values or structured rows. There are no columns mapping to PII fields. The content describes transaction categories or groupings rather than individual client records.

File structure

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

Notes: No PII columns detected in the first 50 rows. The data appears to be transaction records with merchant names, categories, account numbers, and amounts — none contain personal identifiable information such as names, emails, phone numbers, or addresses. All visible fields are transactional metadata or masked account references.

File structure

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

Notes: This is a financial transaction summary table showing spending categories and amounts over years. No PII fields are present — all columns contain aggregate monetary values and category labels. The data represents expense tracking, not individual client records.

File structure

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

Notes: No PII fields detected in this structured transaction log. The file contains financial transaction data (merchant names, categories, account types, amounts, timestamps) but lacks any personal identifiable information such as names, email addresses, phone numbers, or addresses. All columns represent transactional metadata rather than user PII.

File structure

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

Notes: This file contains only category and group labels for expense tracking — no PII fields present. All columns represent transaction categories and groupings, not personal data.

File structure

Notes: This is a free-form text file showing budget category labels from a financial planning document. No consistent column structure exists across rows; it appears to be a list of spending categories rather than structured PII records. There are no embedded emails or phone numbers visible in the sample.

File structure

Notes: free-form text with no consistent delimiter structure; contains financial aggregates and tags but no identifiable PII columns

File structure

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

Notes: This file contains only transaction category and type columns (e.g., 'Shopping', 'Discretionary'). No PII fields are present. All columns are categorized as skip per exclusion rules (transactional/categorical data).

File structure

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

Notes: The file contains transactional data with merchant names, categories, account types, and amounts. No personal identifiable information (PII) fields such as names, addresses, emails, phone numbers, dates of birth, or SSNs are present. All visible data pertains to financial transactions and does not contain any directly identifiable personal information.

File structure

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

Notes: The file is a CSV containing transaction records with no PII fields present. Columns include Date, Merchant, Category, Account, Original Statement, Notes, Amount, and Tags. There are no fields mapping to email, phone, DOB, names, addresses, SSN, passwords, usernames, or other PII categories. The data appears to be purely transactional financial records without any personal identifying information.

File structure

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

Notes: This is not a data file containing personal records. It appears to be a category list or grouping taxonomy used internally by Mercer Advisors, possibly for transaction categorization or expense tracking. The entries are generic group names (e.g., 'Auto', 'Dining', 'X - Business') and contain no personal identifying information (PII). There are no columns with names or values that map to any PII fields. Therefore, no columns are mapped as PII.

File structure

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

Notes: All columns are non-PII: timestamps (Date), company names (Merchant), categories, account numbers (masked), transaction details, amounts, tags, groups, types. No personal identifiers present. Columns with 'Company' or 'Business' prefixes are excluded by rules.

File structure

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

Notes: This is a transaction log with financial data; no PII fields are present. Columns contain dates, merchant names, categories, account types, transaction descriptions, amounts, tags, groups, and types — all transactional/financial metadata without personal identifiers.

File structure

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

Notes: This file contains category and group classifications for transaction types and does not include any PII fields. All columns are non-PII metadata about transaction groupings and categories.

File structure

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

Notes: This is a financial transaction log with columns: Date, Merchant, Category, Account, Original Statement, Notes, Amount, Tags, Group, Type. No PII fields are present. All columns contain transactional data, account numbers are masked, and there are no names, addresses, emails, phone numbers, or other personally identifiable information.

File structure

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

Notes: This is a financial transaction log with no PII fields. Columns include dates, merchants, categories, account details, statements, amounts, and transaction types. No personal identifiable information such as names, addresses, emails, or phone numbers are present.

File structure

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

Notes: This file contains transaction data with merchant names, dates, amounts, and categories. No PII fields are present. All columns are transactional or metadata (Date, Merchant, Category, Account, Original Statement, Notes, Amount, Tags, Group, Type) and do not contain any personal identifiable information such as names, addresses, emails, phone numbers, etc.

File structure

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

Notes: This file contains only financial transaction data with no personal identifiable information (PII). All columns represent transaction details such as date, merchant, category, account information, statement descriptions, amounts, and tags. No PII fields (email, phone, name, address, DOB, SSN, etc.) are present.

File structure

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

Notes: This is a transaction ledger file with financial records (dates, merchants, categories, account numbers, statements, amounts). No PII fields are present. All columns map to transactional/financial data (e.g., Date, Merchant, Category, Account, Original Statement, Notes, Amount, Tags, Group, Type) and are therefore skipped per exclusion rules.

File structure

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

Notes: This is a transaction log file showing merchant purchases and account details. Columns contain transaction dates, merchant names, categories, account numbers with partial card/account numbers (masked), merchant descriptions, amounts, and transaction types. No PII fields are present beyond potentially identifying account numbers which are partially masked and not full account details. All columns fall under financial/transactional data and are excluded per rules.

File structure

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

Notes: This file contains transaction data with no PII fields. All columns represent transaction details (date, merchant, category, account, statement, notes, amount, tags, group, type) and do not contain any personal identifiable information such as names, addresses, emails, phone numbers, dates of birth, or social security numbers.

File structure

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

Notes: This is a financial transaction summary table showing category-wise spending across years. No PII fields present — only transaction categories, monetary amounts, and totals. All columns represent aggregated financial data, not personal identifiers.

File structure

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

Notes: This file contains only financial category data and totals with no personal identifiers. All columns represent aggregated financial figures (e.g., Mortgage, Taxes, Groceries) and summary statistics. No PII fields are present.

File structure

Notes: This is a free-form data table with no identifiable personal information. The content appears to be financial aggregates (sums of amounts) grouped by year and category. There are no columns, headers, or structured records containing PII fields such as names, emails, addresses, or other sensitive data. The file represents summary statistics rather than individual client records.

File structure

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

Notes: This file contains only category and transaction type data. There are no PII fields present. All columns are skipped per rules (business/transactional data).

File structure

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

Notes: The provided data is a transaction log containing merchant details, dates, amounts, and categories. It does not contain any personally identifiable information (PII) fields such as names, addresses, emails, phone numbers, dates of birth, SSNs, passwords, usernames, or other sensitive identifiers. The data is purely transactional and does not map to any PII fields.

File structure

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

Notes: This file appears to be a transaction log showing purchases and payments, not a breach dataset containing PII. There are no columns mapping to personal identifiable information fields such as email, phone, DOB, etc. The data consists of dates, merchants, categories, account types, descriptions, amounts, and tags related to financial transactions.

File structure

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

Notes: This file contains only category labels (Group) and static strings like 'X - Business'. No PII fields are present; this appears to be a reference or mapping file, not actual client data. All columns are non-PII metadata or groupings.

File structure

Notes: This is a free-form text file with no consistent column structure. It appears to be a description or categorization of expense types rather than structured records containing PII. There are no identifiable columns or delimiters, and the content is prose-like with categories and descriptions.

File structure

Notes: The file is free-form text with no consistent column structure. It appears to be a financial summary report with rows containing category names and numerical values, but lacks any identifiable personal information such as names, addresses, or contact details. There are no structured columns to map to PII fields.

File structure

Notes: This is a free-form text file listing transaction categories and types, not structured records. It contains no identifiable columns or PII fields. The format does not match CSV, TSV, etc., and each line is a different category label with no consistent delimiter or structure.

File structure

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

Notes: All columns appear to contain financial income data (guaranteed income amounts, monthly/annual values). No PII fields detected. Values are financial figures and descriptions of retirement/pension types, not personal identifiers.

File structure

Notes: This is a free-form text file with no consistent columnar structure. The content appears to be a list of budget items and financial projections without any defined delimiter or header. There are no structured columns to map to PII fields.

File structure

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

Notes: This is a transaction ledger with no PII columns. Contains merchant names, categories, account numbers (masked), dates, amounts, and tags — all transactional data without personal identifiers. No emails, names, addresses, or other PII fields are present.

File structure

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

Notes: This file contains only transaction data (dates, merchants, categories, account numbers, amounts). No PII fields (names, emails, addresses, etc.) are present. All columns map to skip categories: timestamps, merchant names, transaction categories, account identifiers, amounts, tags, and merchant references. The data represents personal spending but lacks any personally identifiable information in the provided rows.

File structure

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

Notes: This file contains transactional banking data with no PII fields. All columns represent account activity details (dates, merchant names, categories, account numbers, transaction amounts, and tags) but contain no personal identifying information such as names, addresses, emails, phone numbers, or other PII types. The account numbers shown are partial/masked account references, not full account numbers or SSNs. No columns map to any PII field categories.

File structure

Notes: This is a free-form text file containing financial data summaries (asset types and values) with no consistent columnar structure or identifiable PII. It does not contain any structured records with personal information such as names, emails, or addresses. The content appears to be aggregated financial statistics rather than individual client records.

File structure

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

Notes: No PII columns detected. All columns represent financial/transactional data (company tickers, quantities, market prices, values, yields). No personal identifiers present.

File structure

Notes: The file is a free-form text financial breakdown with no consistent column structure or delimiters. It contains categories and descriptions of expenses rather than structured personal records. No PII columns are present in a tabular format.

File structure

Notes: This is not a structured data file; it's a free-form document describing loan amortization schedule fields and sample values rather than containing actual PII records. No columns map to PII fields.

File structure

Notes: This is not a structured CSV file. The columns appear to be free-form text or a table header row without actual data rows following the expected pattern. The values in the sample appear to be metadata or template text ("Enter Values", "Loan Amortization Schedule", etc.) rather than actual PII records. There are no consistent columns or identifiable PII fields in the sample rows.

File structure

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

Notes: This file contains only financial/tax data (years, property taxes, annual increases, tax assessments) with no personal identifying information. All columns are financial metrics and should be skipped.

File structure

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

Notes: This is not structured PII data; it's a financial projection table with years, ages, and benefit amounts. Columns contain identifiers like 'Gary (PIA=3844)' which appear to be internal participant IDs rather than true PII. No actual names, addresses, emails, or other personal identifiers are present in the sample rows. Values are ages, benefit amounts, and zeros — not PII fields.

File structure

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

Notes: This is not structured PII data; it appears to be a benefits projection table with years, ages, and calculated benefit amounts. While names appear in the data ("Gary", "Ronda"), these are not in a consistent column structure and appear to be part of a formatted report rather than a delimited dataset with personal fields. No columns map to identifiable PII fields per the provided rules. The data represents actuarial calculations for retirement benefits, not raw client records.

File structure

Notes: This is a free-form text file describing Mercer Advisors breach categories and expense types, not a structured dataset with personal columns. No consistent delimiter or row structure exists; it contains prose descriptions of financial categories rather than client PII.

File structure

Notes: This is a free-form text file with no consistent column structure. It appears to be a summary table of expense categories and amounts rather than a structured dataset containing personal identifiable information (PII). There are no identifiable columns or PII fields present in this sample.

File structure

Notes: This is a free-form text file listing transaction categories and account types, not a structured dataset with columns. No consistent delimiter or row structure exists across lines. While it contains category names, there are no personal identifiers (emails, phones, names, addresses, etc.) present in this sample.

File structure

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

Notes: All columns represent financial income data (guaranteed income amounts) with no personal identifying information. Values are monetary amounts and pension program names. No PII fields present.

File structure

Notes: The provided text is unstructured financial planning data with no consistent column structure. It appears to be a list of budget items, costs, and frequencies rather than a delimited dataset with PII fields. There are no identifiable columns or row structures, and the content does not contain embedded emails or phone numbers in a free-form text format that would trigger the unstructured opt-out condition.

File structure

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

Notes: The provided file appears to be a standard bank transaction ledger rather than a structured PII dataset. It contains merchant names, dates, transaction amounts, and account details, but no identifiable personal information such as names, addresses, emails, or phone numbers is present. All entries are transactional records without embedded PII fields.

File structure

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

Notes: This file contains only financial transaction data (monthly amounts) and source names. No PII fields are present. All columns represent financial amounts or generic source labels and do not contain any personally identifiable information such as names, addresses, emails, etc.

File structure

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

Notes: All columns contain financial transaction data (monthly amounts) with no PII present. 'Source' column contains pension program names but no personal identifiers. No emails, phone numbers, names, addresses, DOB, SSN, or other PII fields detected.

File structure

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

Notes: No PII columns detected. All columns appear to be financial data (monthly amounts) and source identifiers for pension accounts. The 'Source' column contains pension account names but does not contain email, phone, name, address, or other PII fields.

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample shows unstructured financial planning data with no repeating column pattern across rows — each line has different fields and separators. While it contains personal financial data, it lacks a tabular format that could be parsed into columns. The content appears to be a client financial summary report with calculations and pay stubs, but not in a structured CSV or TSV format.

File structure

Notes: free-form text with no consistent delimiter structure; appears to be financial statements/payroll data rather than PII records. No identifiable personal data columns exist in this structured format. The file contains salary calculations, tax withholdings, and benefit projections rather than personal identifiers like names, emails, or addresses.

File structure

Notes: This is an unstructured file containing free-form financial data rows with no consistent column structure. The lines appear to be financial summaries (gross, net, taxes) with timestamps and labels, but there is no repeating delimiter pattern or header. While there is a string 'paypal' that could be interpreted as a username, the lack of structured columns means we must treat this as unstructured text for processing.

File structure

Notes: free-form text with no consistent delimiter structure; lines contain expense descriptions and amounts rather than tabular data with PII columns

File structure

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

Notes: This file appears to be a financial tax projection worksheet with no identifiable PII columns. All values are numeric calculations, dates, and financial terms. No names, addresses, emails, or other personal identifiers are present in the first 50 rows.

File structure

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

Notes: This is purely financial/transactional data showing investment holdings and account details. No PII fields are present — only ticker symbols, fund names, quantities, values, fees, and account identifiers that are internal codes (not usernames or emails). All columns are skipped per exclusion rules (financial/transactional data).

File structure

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

Notes: This file contains purely financial and expense data with no identifiable personal information. All columns represent expense categories, monetary amounts, and status indicators rather than PII fields. No emails, phone numbers, names, addresses, or other personal data are present.

File structure

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

Notes: This is a financial portfolio statement containing investment accounts, holdings, and values. No personal identifiable information (PII) fields are present. Columns contain account details, security identifiers, asset classifications, quantities, prices, and notes about investments. Names like 'RICH IRA' and 'RICHARD COHEN' appear to be account titles or client references but are not mapped as PII because they are not clearly personal names in a PII context and the file lacks structured personal data fields like email, phone, or address.

File structure

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

Notes: No PII columns detected. All columns contain financial/account data (account identifiers, tickers, CUSIPs, fund descriptions, asset classes, units, cost basis, prices, market values). These are financial transaction columns, not personal identifiers.

File structure

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

Notes: All columns are financial/transactional data or internal identifiers. No PII fields detected. Columns like 'Source File', 'Account Number', and financial values do not map to any PII categories per exclusion rules. No emails, phone numbers, names, addresses, DOB, SSN, or other personal identifiers present.

File structure

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

Notes: This is a financial expense report structure (housing costs, mortgage, taxes). No PII fields present. All columns contain financial categories, totals, or are empty. This matches Mercer Advisors' known exposure of financial statements and tax documents, but this particular file lacks personal identifiers.

File structure

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

Notes: Only two columns contain PII: firstName and lastName. All other columns are file metadata, account numbers, financial values, or empty fields — none contain searchable personal data. No emails, phones, DOB, SSN, or addresses are present in this sample.

File structure

Notes: The data appears to be free-form text with no consistent delimiter or structure. The rows contain unstructured financial and client notes rather than tabular data with identifiable columns. There are no repeated column patterns or clear PII mappings.

File structure

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

Notes: This is a category mapping file with no PII fields. The file contains two columns: Categories and Group, mapping transaction categories to broader groups. No personal identifiable information is present.

File structure

Notes: This file contains only category labels and financial buckets (Discretionary, Auto, Clothing, etc.) with no structured personal data. It appears to be a summary or categorization scheme rather than actual client records. No PII columns exist to map.

File structure

Notes: free-form text with no consistent column structure; contains financial aggregates and tags but no identifiable personal data columns

File structure

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

Notes: This is a category and transaction type mapping file with no PII fields. All columns are category and transaction type labels used for financial categorization and do not contain any personal identifiable information.

File structure

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

Notes: This file contains transaction records with merchant details, dates, amounts, and account information. No PII fields (email, phone, name, address, etc.) are present in the visible columns. All fields appear to be transactional data (dates, merchant names, amounts, account types, categories) and do not contain personally identifiable information.

File structure

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

Notes: The file appears to be a structured CSV containing transaction data (dates, merchants, categories, accounts, amounts, etc.). However, there are no identifiable PII fields present in the visible data. All columns appear to contain transactional/financial data (merchant names, account types, amounts, categories) without any personal identifiers such as names, emails, phone numbers, addresses, or other PII. Based on the data sample, no columns map to the defined PII fields.

File structure

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

Notes: This file appears to be a categorization list for expense groups/categories rather than a structured dataset with personal records. The content describes expense categories (Auto, Dining, Gifting, etc.) and does not contain any identifiable personal information such as names, emails, addresses, or other PII fields. Therefore, no PII columns can be mapped from this data.

File structure

Notes: This is a free-form text file containing monthly expenditure data with no consistent column structure. The data appears to be financial records with categories like deposits, ATM/debit card usage, checks, electronic withdrawals, and totals. There are no identifiable PII fields (emails, phone numbers, names, addresses, etc.) in a structured format. While the data contains monetary values and some personal activity descriptions (e.g., "out of the country"), it does not contain any directly searchable PII that would require mapping. The format does not conform to a structured CSV/TSV with consistent delimiters and headers across rows.

File structure

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

Notes: No PII fields detected. All columns contain timestamps, transaction descriptions, amounts, and internal codes. No emails, names, addresses, DOB, SSN, or other PII appear in the sample data. Columns like 'Annual Payments' contain category labels (e.g., 'Allstate-Home', 'Taxes Preparer') and not personal identifiers.

File structure

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

Notes: This is a structured CSV file with 5 columns. Columns 3 (Username) and 4 (Password) contain PII. Columns 0 (Program/Site) and 1 (Account Owner) are skipped per exclusion rules. No email, phone, dob, name, address, ssn, or other PII fields are present.