← All datasets

zynex.com

Jul 30, 2026

31,694
Records
3,329
Files
Jul 30, 2026
Added

Internal corporate data breach of Zynex, a Swiss web hosting and CMS software company (zynex.com). The archive contains highly sensitive internal financial records spanning 2001–2020, including annual financial statements, subscription billing records (FaktNT ERP system), project status files, general assembly protocols, and customer invoicing data. Customers visible in the data are Swiss SMEs billed for 'Zynex Business' and 'Zynex One' annual web hosting/CMS subscriptions. Data is primarily in German and uses Swiss Francs (CHF). Also includes a 3CX license invoice from 2020, indicating operations continued at least to that date.

Data found in this dataset

EmailFirst nameLast nameAddressCityGenderfullNameskipdobagessnaddress2zipemailText

Search this dataset

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

Source files

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

finanzen__Abschluesse__Abschluss_2001__abgrenzung__abgrenzung.csv
0 rows

File structure

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

Notes: This is purely transactional financial data with no PII. Columns represent account numbers (AboNr), billing cycles (RechZyklus), invoice dates (Rechnung_Letzte), and financial amounts (betrag 2001, etc.). No personal identifiers present.

finanzen__Abschluesse__Abschluss_2001__angefangene_arb_2001__Tabelle1.csv
0 rows

File structure

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

Notes: This file contains only business transaction data (customer names, amounts, dates). No identifiable personal information (PII) is present. Customer names like 'SAV', 'Gebr. Wälti AG', 'Confarma' are company or business entity names, not individual person names. All values represent financial data and dates, which are excluded per the rules. No emails, phone numbers, addresses, or other PII fields are visible.

finanzen__Abschluesse__Abschluss_2001__angefangene_arbeiten_2001__Vorauszahlungen.csv
0 rows

File structure

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

Notes: This is a financial ledger file with customer names and monetary amounts. The first column contains business names (companies) rather than personal names, and the other columns are transaction dates and amounts. Per the exclusion rules, company/business names are NOT considered PII and must be skipped. There are no personal PII fields (email, phone, DOB, etc.) in this dataset.

finanzen__Abschluesse__Abschluss_2001__angefangene_arbeiten_2001__angefangene_arbeiten.csv
0 rows

File structure

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

Notes: No PII columns detected. File contains only corporate financial records: company names, dates, project descriptions, staff initials, hours, rates, and monetary amounts. No personal identifiers such as names, addresses, emails, or phone numbers are present.

finanzen__Abschluesse__Abschluss_2002__abgrenzung_abos_2002__abgrenzung.csv
0 rows

File structure

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

Notes: This is purely transactional financial data with account numbers (AboNr), billing cycles (RechZyklus), dates, and monetary amounts. No PII fields (names, addresses, emails, etc.) are present. All columns map to skip categories per rules (internal IDs, timestamps, financial/transactional data).

finanzen__Abschluesse__Abschluss_2002__projektstatus_2002__Tabelle1.csv
0 rows

File structure

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

Notes: This file contains only business/project financial data (project names, payments, costs, completion status). No personal identifiable information (PII) is present. All columns are business/project metrics and should be skipped.

finanzen__Abschluesse__Abschluss_2003__abgrenzung_rg_2003__Rechnungsabgrenzung_2003.csv
0 rows

File structure

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

Notes: All columns appear to be internal business identifiers, financial transaction data, and invoice metadata. No PII fields (email, phone, name, address, DOB, etc.) are present. Columns like 'Name' contain company names (BMP, CENTRACHEM, etc.), not personal names. Financial columns (Preis, 2003, 2004) and internal IDs (AboNr, Kdnr) are skipped per exclusion rules. No actionable PII to map.

finanzen__Abschluesse__Abschluss_2003__projektliste_feb04__Tabelle1.csv
0 rows

File structure

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

Notes: This is an unstructured file with no identifiable PII columns. The columns appear to represent project names, amounts, and statuses, but do not contain any personal identifiable information such as names, emails, phone numbers, addresses, etc. All columns appear to be related to project tracking and financial data, which are not classified as PII according to the provided rules.

finanzen__Abschluesse__Abschluss_2003__projektstatus_2003__Tabelle3.csv
0 rows

File structure

Notes: The provided data appears to be a series of unstructured German project notes or task entries. There are no consistent column headers, and the data does not contain any identifiable PII fields such as names, emails, addresses, or other sensitive information. The entries are task descriptions with dates and numerical codes, but no personal information is present. Therefore, no PII columns can be mapped.

finanzen__Abschluesse__Abschluss_2003__projektstatus_2003__projektstatus.csv
0 rows

File structure

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

Notes: This is a financial report file with no PII present. Columns represent project names, payment amounts, and status codes. All values are business/project identifiers or financial figures, not personal data. No emails, phone numbers, names, addresses, or other PII fields are present.

finanzen__Abschluesse__Abschluss_2004__Abrechnung_mph_2004__Tabelle1.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent column structure. It contains accounting lines with amounts in CHF but no personal identifiable information (PII). The format appears to be a simple ledger with no headers or repeating columns across rows.

finanzen__Abschluesse__Abschluss_2004__abgrenzungen_2004__Tabelle3.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or column structure. The lines contain project descriptions and numerical values but no identifiable PII fields. No structured columns exist to map.

finanzen__Abschluesse__Abschluss_2004__abgrenzungen_2004__projektstatus.csv
0 rows

File structure

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

Notes: This is an unstructured financial record file with no PII columns. All columns contain internal accounting codes, project names, financial amounts, and calculation markers — no names, emails, addresses, or other personal identifiers appear in the sample. The data appears to be internal corporate bookkeeping for Zynex (Swiss web hosting/CMS software company) with project names in German and financial figures in CHF.

finanzen__Abschluesse__Abschluss_2004__projektstatus_2004__Tabelle3.csv
0 rows

File structure

Notes: The provided data appears to be free-form text with no consistent column structure or delimiter. Each line contains descriptive text in German related to project tasks, dates, and numerical values (likely financial or time tracking data). There are no identifiable PII fields such as email, phone, or names present in the sample, and the structure does not conform to a tabular format. Therefore, this is classified as unstructured text.

finanzen__Abschluesse__Abschluss_2004__projektstatus_2004__projektstatus.csv
0 rows

File structure

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

Notes: The file contains only financial/transactional data (amounts, percentages, invoice numbers) with no personal identifying information. Columns represent business metrics like payments, offers, costs, and completion status for various clients/companies. No PII fields detected.

finanzen__Abschluesse__Abschluss_2005__abgrenzungen_2005__Tabelle3.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or column structure. The lines appear to be German project notes or task descriptions with dates and numerical codes, but no identifiable personal information or structured columns. There are no emails, phone numbers, or other PII visible in the sample. The data appears to be internal corporate project tracking records rather than customer PII.

finanzen__Abschluesse__Abschluss_2005__abgrenzungen_2005__projektstatus.csv
0 rows

File structure

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

Notes: This file contains purely financial/transactional data (advance payments, project names, amounts, reference numbers) with no personal identifiable information. All columns represent internal corporate accounting records, project identifiers, monetary values, and status flags. No PII fields detected.

finanzen__Abschluesse__Abschluss_2006__Aktienbew_2006_Zynex__Daten.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure; appears to be financial summary notes rather than tabular data

finanzen__Abschluesse__Abschluss_2006__Aktienbew_2006_Zynex__St_Wert.csv
0 rows

File structure

Notes: This file is purely descriptive corporate financial prose with no tabular structure. The data contains corporate names, locations, and financial statements for Zynex AG, but no personal PII fields. Every row is a standalone sentence or label, not structured data rows with consistent columns. Therefore, it's unstructured text with no column mapping possible.

finanzen__Abschluesse__Abschluss_2006__Bil_2006_Zynex__Anlagesp.csv
0 rows

File structure

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

Notes: This is a financial statement file with no personal identifiable information (PII). All columns contain accounting data such as asset values, depreciation amounts, and balance sheet items. There are no columns mapping to email, phone, name, address, or other PII fields.

finanzen__Abschluesse__Abschluss_2006__Bil_2006_Zynex__Bilanz.csv
0 rows

File structure

Notes: This is a financial statement document in German (Zynex AG balance sheet). It contains no structured columns or personal identifiable information (PII). The content is purely financial data presented in a tabular format without any personal customer or employee details. The file appears to be a static financial report rather than a dataset with personal records.

finanzen__Abschluesse__Abschluss_2006__Bil_2006_Zynex__Daten.csv
0 rows

File structure

Notes: The provided sample is free-form text with financial statement headers and dates, not structured tabular data. There are no consistent columns or delimiters, and the content appears to be prose-style financial records (e.g., 'Abschluss 31.12.2006', 'Abschluss,12/31/06,2006,1/1/06,,,'). This matches the description of a breach containing internal financial records and assembly protocols rather than customer PII. No emails or phones are visible in the sample.

finanzen__Abschluesse__Abschluss_2006__Bil_2006_Zynex__Erfolgsrg.csv
0 rows

File structure

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

Notes: This is a financial statement document in German, showing revenue, expenses, and profit figures for Zynex AG for the fiscal years ending December 31, 2006 and 2005. The data is purely financial and contains no personal identifiable information (PII). There are no columns that map to any PII fields. All values are monetary amounts, account names, and financial metrics.

finanzen__Abschluesse__Abschluss_2006__Bil_2006_Zynex__Gewinnverw_.csv
0 rows

File structure

Notes: This is a free-form financial statement document in German with no consistent column structure. It contains financial data such as profit/loss statements, balance sheet items, and dividend proposals for Zynex AG. There are no identifiable PII columns in this structured format — it is purely corporate financial prose.

finanzen__Abschluesse__Abschluss_2006__Bil_2006_Zynex__Leasingverb.csv
0 rows

File structure

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

Notes: This is not a PII dataset. The file contains corporate financial leasing records for Zynex AG with columns representing business entities, asset descriptions, lease terms, and financial figures. No personal identifiable information (PII) is present. All columns map to corporate/financial data and should be skipped per exclusion rules (Company/Business related fields).

finanzen__Abschluesse__Abschluss_2006__Bil_2006_Zynex__Stille_Reserven.csv
0 rows

File structure

Notes: The file is free-form financial accounting text (German) with no consistent columnar structure. It contains financial statements and accounting entries rather than personal PII fields. No structured data with identifiable columns exists in the sample.

finanzen__Abschluesse__Abschluss_2006__Darl_Zynex_A6__Zinsabr.csv
0 rows

File structure

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

Notes: This file contains purely financial accounting records with dates, account balances, interest calculations, and currency values. No personal identifiable information (PII) fields are present. All columns represent internal financial data (account numbers, dates, amounts, interest rates) and do not map to any PII categories. The structure shows ledger entries with dates, debit/credit amounts, running balances, and interest calculations typical of accounting systems.

finanzen__Abschluesse__Abschluss_2006__MWST-Abr_2006_Zynex__2006.csv
0 rows

File structure

Notes: This file is an unstructured document containing financial records and VAT calculations in German. It shows VAT settlements for 2006 with columns representing various financial figures like cumulative totals, quarterly breakdowns, and differences. There are no consistent columns or PII fields present; all data appears to be financial aggregates and accounting codes rather than personal information. The document structure is free-form with no delimited rows/columns.

finanzen__Abschluesse__Abschluss_2006__MWST-Abr_2006_Zynex__Abr_exkl_MWST.csv
0 rows

File structure

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

Notes: This is a financial statement file in German, containing columns like 'Umsatz exkl. MWST' (Revenue excluding VAT), 'Kundenguthaben' (Customer credit), and various tax rates. There are no personal identifiable information (PII) fields such as names, addresses, emails, or phone numbers. All columns contain financial data, tax categories, and accounting adjustments, which are not classified as PII under the provided field types. Therefore, no columns map to PII fields.

finanzen__Abschluesse__Abschluss_2006__MWST-Abr_2007_Zynex__2007.csv
0 rows

File structure

Notes: This is a free-form financial report document (VAT statement for 2007) with no consistent columnar structure. The content contains financial terminology in German (e.g., 'MWST-Abrechnung', 'Gesamtumsatz') and numerical values but no identifiable personal information. No PII columns exist to map.

finanzen__Abschluesse__Abschluss_2006__MWST-Abr_2007_Zynex__Abr_exkl_MWST.csv
0 rows

File structure

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

Notes: This is a financial statement file with columns representing VAT rates, revenue categories, and account balances. No personal identifiable information (PII) is present. Columns contain German financial terminology and numeric values, indicating this is an accounting document rather than customer or user data. All columns map to financial/tax categories and should be skipped per exclusion rules.

finanzen__Abschluesse__Abschluss_2006__Stb_2006_Zynex_AG__Bet_Ertrag.csv
0 rows

File structure

Notes: The provided data is a free-form financial statement document in German with no consistent column structure or delimiter. It contains corporate financial data and percentages but no identifiable personal information. This is a financial report rather than structured PII data.

finanzen__Abschluesse__Abschluss_2006__Stb_2006_Zynex_AG__Daten.csv
0 rows

File structure

Notes: This is a financial statement document in German with no consistent columnar structure. It contains corporate financial data (revenue, profit, balance sheet) for Zynex AG rather than any personal PII. There are no identifiable columns or repeated patterns that would indicate personal data fields.

finanzen__Abschluesse__Abschluss_2006__Stb_2006_Zynex_AG__Jahr.csv
0 rows

File structure

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

Notes: This is a financial statement file with no personal identifiable information (PII). The data appears to be corporate financial records from Zynex AG, including fiscal years, registration numbers, and financial periods. There are no columns containing names, addresses, email addresses, phone numbers, dates of birth, social security numbers, or any other PII fields. All columns are internal financial or corporate identifiers that should be skipped according to the exclusion rules.

finanzen__Abschluesse__Abschluss_2006__Stb_2006_Zynex_AG__LCF.csv
0 rows

File structure

Notes: This is free-form financial/prose data with no consistent delimiter structure. The sample shows unstructured accounting statements and financial notes in German, not CSV or tabular data. While it contains financial figures, there are no identifiable PII fields like names, emails, or addresses. The content appears to be corporate financial records rather than customer PII.

finanzen__Abschluesse__Abschluss_2006__Stb_2006_Zynex_AG__Rst.csv
0 rows

File structure

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

Notes: This is not PII data; it's corporate financial records from Zynex AG, a Swiss web hosting company. The columns contain account names, fiscal years, tax types, status codes, and financial figures — all internal business data with no personal customer information. No PII fields (emails, names, addresses, etc.) are present.

finanzen__Abschluesse__Abschluss_2006__Stb_2006_Zynex_AG__RstGJ.csv
0 rows

File structure

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

Notes: This is a financial statement file with no personal identifiable information (PII). Columns contain fiscal year data, tax types, amounts, and accounting codes. No names, addresses, emails, phone numbers, or other PII fields are present. The data is purely corporate financial records from Zynex AG.

finanzen__Abschluesse__Abschluss_2006__Stb_2006_Zynex_AG__Spartenrg.csv
0 rows

File structure

Notes: The file contains unstructured financial accounting entries in German (Zynex AG financial statements). Lines represent accounting descriptions and values rather than columnar data. No PII fields are present or mappable due to lack of structured format.

finanzen__Abschluesse__Abschluss_2006__Stb_2006_Zynex_AG__St.csv
0 rows

File structure

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

Notes: This file appears to be unstructured financial statements and tax records in German. It contains no personal identifiable information (PII) fields such as names, addresses, emails, phone numbers, etc. The data consists entirely of corporate financial metrics, tax rates, and statutory references without any customer or employee details. All columns appear to represent business financial data, tax calculations, or internal accounting codes.

finanzen__Abschluesse__Abschluss_2006__Stb_2006_Zynex_AG__StE.csv
0 rows

File structure

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

Notes: This is a financial statement document in German (Swiss corporate records). It contains structured financial data (revenue, capital, tax reserves) but NO personal PII fields like names, emails, or addresses. All visible values are numeric financial figures, dates, and legal identifiers (registration number). No columns map to PII fields.

finanzen__Abschluesse__Abschluss_2006__abgrenzung_2006_neu__Angef._Arbeiten.csv
0 rows

File structure

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

Notes: This is an unstructured financial/projection table with no personal identifiers. Columns contain project names and financial figures (amounts, reference numbers), but no PII fields. The header row is empty except for the first cell ('Angefangene Arbeiten'). The data appears to be internal corporate financial records, not customer PII.

finanzen__Abschluesse__Abschluss_2006__abgrenzung_2006_neu__Ertr_ge_Trans._Aktiven.csv
0 rows

File structure

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

Notes: This is not PII data. Columns contain only financial/accounting codes, dates, and amounts related to hosting fees and transitory assets. No personal identifiers like names, emails, addresses, or phone numbers are present. The values represent internal corporate financial records from Zynex's ERP system (FaktNT), including hosting service fees and transitory asset entries.

finanzen__Abschluesse__Abschluss_2006__abgrenzung_2006_neu__Ertr_ge_Trans._Passiven.csv
26 rows

File structure

Notes: This is a free-form financial record file with no consistent column structure. The data appears to be Swiss financial statements/transactions from Zynex, containing accounting codes, dates, amounts, and descriptive text. There are no identifiable PII fields (names, emails, addresses, etc.) in the visible sample rows. The format is unstructured text with no CSV-like structure.

finanzen__Abschluesse__Abschluss_2006__abgrenzung_2006_neu__Periodenfremde_Aufw_nde.csv
0 rows

File structure

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

Notes: This is an unstructured financial record file with no personal identifiable information (PII). Columns contain financial codes, dates, monetary amounts, and internal reference numbers. No email addresses, phone numbers, names, or other PII fields are present. The data appears to be Swiss corporate financial records from Zynex, a web hosting company, with entries in German and Swiss Francs (CHF).

finanzen__Abschluesse__Abschluss_2006__abgrenzung_2006_neu__Vorauszahlungen.csv
0 rows

File structure

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

Notes: This is a financial ledger document in German with structured tabular data, but all columns represent internal business identifiers, financial figures, and transaction codes. No personal identifiable information (PII) is present. Columns contain invoice references (RG Nr.), financial amounts (CHF), and internal notes (e.g., 'Schreinerei Eggenberger'). All values are numeric or internal business codes, with no names, emails, addresses, or other PII fields.

finanzen__Abschluesse__Abschluss_2006__abgrenzungen_2006-draft__Tabelle3.csv
0 rows

File structure

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

Notes: This is not PII data; it's purely transactional financial/project records from Zynex's internal ERP system. No personal identifiers (names, emails, addresses, etc.) are present. All columns represent project descriptions, dates, internal codes, quantities, and monetary values. The data structure shows no headers, and all values are business/project-related metrics.

finanzen__Abschluesse__Abschluss_2006__abgrenzungen_2006-draft__projektstatus.csv
0 rows

File structure

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

Notes: This is purely financial accounting data (prepayments, settlements, balances, expenses) with no personal identifiers. All columns represent transactional/financial metrics, not PII. Column 1 contains project names (not personal names), and all other columns are numeric financial values or status flags. No emails, phones, names, addresses, DOB, SSN, or passwords are present.

finanzen__Abschluesse__Abschluss_2006__abgrenzungen_2006__Tabelle3.csv
0 rows

File structure

Notes: The provided data is unstructured free-form text with no consistent column layout. Each line appears to be a project/task description in German with dates and numerical values, but there are no identifiable PII fields (emails, phones, names, addresses, etc.) visible in the sample. The format does not contain any structured columns that could be mapped to PII fields.

finanzen__Abschluesse__Abschluss_2006__abgrenzungen_2006__projektstatus.csv
0 rows

File structure

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

Notes: This file contains purely financial/transactional data (prepayments, project names, amounts, reference numbers, balances) with no personal identifiable information. All columns map to corporate accounting fields and should be skipped. No PII fields detected.

finanzen__Abschluesse__Abschluss_2006__umbuchung_4200_einkauf__Einkauf_Eigenbedarf.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. Lines contain mixed data including what appears to be internal accounting entries, product descriptions, and possibly embedded PII such as 'swiss-support.net' and 'SSN' references. Since there is no consistent delimiter or row structure across lines, this must be processed as unstructured text to extract any embedded emails or phone numbers.

finanzen__Abschluesse__Abschluss_2006__umbuchung_4200_einkauf__Einkauf_f_r_Verkauf.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent delimiter or column structure. The sample contains mixed data including what appears to be names ("Remo Häner"), potential SSN fragments ("86095 (x)"), and financial figures. However, the data lacks a consistent columnar format across rows, making it unsuited for structured CSV/columnar mapping. This should be processed as unstructured text for embedded PII extraction.

finanzen__Abschluesse__Abschluss_2007__abgrenzung_2007__Angef._Arbeiten.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger with no personal identifiable information (PII). The columns represent internal corporate financial records (ticket numbers, customer/project names, monetary amounts, and internal reference numbers). No emails, phone numbers, names, addresses, DOBs, SSNs, or other PII fields are present. The data appears to be purely transactional and financial in nature, consistent with the described breach context of internal corporate financial records from Zynex.

finanzen__Abschluesse__Abschluss_2007__abgrenzung_2007__Debitoren_-_TA.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger from Zynex's internal accounting system. Columns contain Swiss accounting codes, transaction descriptions, dates, amounts, and reference numbers. No PII fields are present — all columns represent corporate financial data (accounts receivable, service revenue, invoice numbers, fiscal years). The values are strictly business/financial identifiers with no personal customer or employee information.

finanzen__Abschluesse__Abschluss_2007__abgrenzung_2007__Debitoren_-_TP.csv
0 rows

File structure

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

Notes: This is financial accounting data from Zynex's FaktNT ERP system. All columns appear to be account codes, transaction dates, monetary amounts, and totals — no personal identifiers (PII) present. Columns contain values like account codes ('3400 -- Dienstleistungserlös'), dates ('05.03.2007'), currency amounts ('$245'), and totals ('$48,151.65'). No emails, names, addresses, phone numbers, or other PII fields detected.

finanzen__Abschluesse__Abschluss_2007__abgrenzung_2007__Kreditoren_-_TA.csv
0 rows

File structure

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

Notes: This is an internal financial record file (not customer PII). Columns contain accounting codes, domain names (business identifiers), dates, amounts, and transaction IDs. No personal PII fields (email, phone, name, address, etc.) are present. Domain names like 'busproshop.ch' are business identifiers, not personal addresses. All columns are skipped per exclusion rules for company/business data and financial records.

finanzen__Abschluesse__Abschluss_2007__abgrenzung_2007__Kreditoren_-_TP.csv
0 rows

File structure

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

Notes: This is an accounting/financial file with no personal identifiers. Columns contain account codes, dates, amounts, and totals — no names, emails, addresses, or other PII. All values are financial descriptors or calculations.

finanzen__Abschluesse__Abschluss_2007__abgrenzung_2007__Vorauszahlungen.csv
0 rows

File structure

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

Notes: This is a financial statement document in German with no personal identifiable information (PII). Columns contain account codes, monetary values, and transaction descriptions. No email, phone, name, address, or other PII fields are present. All columns map to skip categories per exclusion rules (financial/transactional data, internal IDs, and timestamps).

finanzen__Abschluesse__Abschluss_2007__abgrenzung_2007_backup__Angef._Arbeiten.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's a financial summary document in German showing project allocations and amounts for 2006. The columns contain project names and monetary values with no personal identifiers. No PII fields present.

finanzen__Abschluesse__Abschluss_2007__abgrenzung_2007_backup__Ertr_ge_Trans._Aktiven.csv
0 rows

File structure

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

Notes: No PII columns detected. The data appears to be financial records with account codes, dates, and monetary values. Column 0 contains website domains but these are company websites, not personal addresses. All other columns contain accounting codes, dates, and financial figures that do not map to any PII fields. This matches the breach context of internal corporate financial records from Zynex.

finanzen__Abschluesse__Abschluss_2007__abgrenzung_2007_backup__Ertr_ge_Trans._Passiven.csv
0 rows

File structure

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

Notes: This is a financial record file with accounting entries and transactional data. No PII fields are present — all columns contain account codes, transaction descriptions, dates, monetary amounts, and totals. The values are internal business identifiers (e.g., '3400 -- Dienstleistungserlös'), invoice numbers, and CHF amounts. No names, addresses, emails, or other personal data appear in the first 50 rows.

finanzen__Abschluesse__Abschluss_2007__abgrenzung_2007_backup__Periodenfremde_Aufw_nde.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger file with no personal identifiers. Columns contain accounting codes, dates, monetary amounts, and domain names. No PII fields (email, phone, name, etc.) are present. The data appears to be corporate financial records from Zynex, a Swiss web hosting company, with references to domain names (zynix.ch, averna.ch, etc.) rather than customer personal data.

finanzen__Abschluesse__Abschluss_2007__abgrenzung_2007_backup__Vorauszahlungen.csv
0 rows

File structure

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

Notes: This is purely financial accounting data with no PII present. Columns contain accounting entries, amounts, reference numbers, and year totals. No names, addresses, emails, or other personal identifiers are visible in the first 50 rows. All columns are financial/transactional and map to skip categories per rules.

finanzen__Abschluesse__Abschluss_2007__pdf__Aktienbew_2007_Zynex__Daten.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; appears to be financial summary lines with years and fiscal periods rather than tabular data with PII columns

finanzen__Abschluesse__Abschluss_2007__pdf__Aktienbew_2007_Zynex__St_Wert.csv
0 rows

File structure

Notes: This is unstructured corporate financial documentation from Zynex AG, not personal customer data. The sample contains financial statements, balance sheet items, and year-end totals in Swiss Francs. No PII fields (email, phone, name, etc.) are present. The text appears to be financial reporting in German, with headers like 'Steuerjahr' (tax year) and values like '2007', '12/31/07', and monetary amounts. This matches the described breach context of internal corporate financial records, not customer PII.

finanzen__Abschluesse__Abschluss_2007__pdf__Bil_2007_Zynex__Anlagesp.csv
0 rows

File structure

Notes: This is corporate financial data from Zynex AG, not customer PII. All columns represent accounting line items, balances, depreciation amounts, and dates — no personal information present.

finanzen__Abschluesse__Abschluss_2007__pdf__Bil_2007_Zynex__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: The file is a financial report with no consistent column structure or PII fields. It contains corporate financial data in German (e.g., 'Aufteilung Gewinn', 'Gewinn vor Bonus und Steuern') and financial figures in Swiss Francs. No personal identifiable information is present.

finanzen__Abschluesse__Abschluss_2007__pdf__Bil_2007_Zynex__Bilanz.csv
0 rows

File structure

Notes: This is a free-form financial statement document in German (Swiss Francs) with no consistent columnar structure. The data appears to be a balance sheet (BILANZEN) for Zynex AG Volketswil for years 2007 and 2006, formatted as prose lines with account names and monetary values rather than a delimited table. No PII fields are present in this structured financial context.

finanzen__Abschluesse__Abschluss_2007__pdf__Bil_2007_Zynex__Daten.csv
0 rows

File structure

Notes: This is unstructured financial report data (German corporate annual statements) with no consistent column structure. Lines contain free-form text with financial figures and dates, not personal identifiable information. No column mapping possible.

finanzen__Abschluesse__Abschluss_2007__pdf__Bil_2007_Zynex__Erfolgsrg.csv
0 rows

File structure

Notes: The file appears to be a financial statement in German (Erfolgsrechnungen) with no consistent columnar structure or personal identifiable information. It contains only financial data such as revenue, expenses, profit/loss figures, and tax calculations for the years 2007 and 2006. There are no identifiable personal fields like names, emails, or addresses present.

finanzen__Abschluesse__Abschluss_2007__pdf__Bil_2007_Zynex__Gewinnverw_.csv
0 rows

File structure

Notes: This file is a free-form financial statement document in German, containing corporate financial data for Zynex AG. It shows annual financial records spanning 2006-2007 with figures in Swiss Francs (CHF). The data includes profit/loss statements, balance sheet items, dividend allocations, and general assembly resolutions. No personal identifiable information (PII) is present — the content is purely corporate financial reporting with no customer/client data or employee details. The format is tabular prose with commas as thousand separators and quotes around numeric values, but lacks consistent column structure across lines. Therefore classified as unstructured text with no importable PII columns.

finanzen__Abschluesse__Abschluss_2007__pdf__Bil_2007_Zynex__Leasingverb.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be financial lease records with no identifiable PII columns

finanzen__Abschluesse__Abschluss_2007__pdf__Bil_2007_Zynex__Stille_Reserven.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent column structure. It appears to be a balance sheet or accounting report with rows representing line items and columns for years. There are no identifiable PII fields in this sample as it contains only financial figures and account names. The format does not conform to any structured delimited format (CSV, TSV, etc.) and should be processed as unstructured text.

finanzen__Abschluesse__Abschluss_2007__umbuchung_4200_einkauf_2007__82_Einkauf_f_r_Eigenbedarf.csv
0 rows

File structure

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

Notes: This is a financial record file with internal corporate data, no personal identifiable information (PII) present. Columns contain internal accounting codes, vendor names, cost centers, and financial amounts. No email addresses, phone numbers, names, addresses, or other PII fields are visible in the sample data.

finanzen__Abschluesse__Abschluss_2007__umbuchung_4200_einkauf_2007__83_Einkauf_f_r_Verkauf.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger with no identifiable PII columns. Columns appear to represent transaction codes, item descriptions, customer names (but these are business names, not personal PII), amounts, and internal accounting codes. No emails, phone numbers, DOB, SSN, or other personal identifiers are present. Customer names like 'Bättig Nico' and 'Gebrüder Jucker Metzgerei AG' are business entities, not individual personal data. All columns map to skip per exclusion rules (company/business references, internal accounting codes, transaction amounts).

finanzen__Abschluesse__Abschluss_2007__umbuchung_4200_einkauf_2007__Einkauf_Eigenbedarf.csv
0 rows

File structure

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

Notes: This file appears to be internal financial records from Zynex. Columns contain accounting codes, product descriptions, and financial amounts. No PII fields are present — the 'Customer' column shows a domain name (swiss-support.net) which is not a personal email or identifiable individual. All columns are business transactional data, financial codes, or internal accounting references. No names, addresses, emails, phones, DOB, SSN, or passwords are present.

finanzen__Abschluesse__Abschluss_2007__umbuchung_4200_einkauf_2007__Einkauf_f_r_Verkauf.csv
0 rows

File structure

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

Notes: This is an unstructured financial record file with no consistent PII columns. Columns appear to represent internal accounting codes, transaction amounts, and supplier/customer references, but no actual PII fields (names, emails, etc.) are present in the visible sample. The data appears to be internal corporate financial records from Zynex, with entries like 'Einkäufe für Verkauf' (Purchases for Sale) and supplier/customer references that do not resolve to personal identifiers in this sample. No email, phone, dob, ssn, or other PII fields are detectable.

finanzen__Abschluesse__Abschluss_2007__umbuchung_4200_einkauf_2007_v2__82_Einkauf_f_r_Eigenbedarf.csv
0 rows

File structure

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

Notes: This is a financial record file with columns describing purchases/invoices (German language). No personal identifiable information (PII) fields are present — all columns describe corporate financial line items, product SKUs, amounts, and internal reference numbers. Column 6 contains "SSN" placeholder text but actual values are numeric monetary amounts, not real SSNs. Column 7 contains numeric codes with '(x)' suffix that appear to be internal reference IDs, not phone numbers. No emails, names, addresses, or other PII detected.

finanzen__Abschluesse__Abschluss_2007__umbuchung_4200_einkauf_2007_v2__83_Einkauf_f_r_Verkauf.csv
0 rows

File structure

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

Notes: This is not structured PII data; it appears to be financial/transactional records from Zynex's internal systems (FaktNT ERP). Columns contain product descriptions (column 4), vendor names (column 5), internal reference codes (column 7), monetary values (columns 8-11), and other accounting fields. No identifiable personal information (emails, phone numbers, addresses, etc.) is present in the first 50 rows. Column 6 shows "SSN" text but values are placeholder labels ("Exported: 11'085.47") rather than actual SSNs. This is purely corporate financial data with no mappable PII fields.

finanzen__Abschluesse__Abschluss_2008__abgrenzung_2008__Angef._Arbeiten.csv
0 rows

File structure

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

Notes: This file appears to be a structured CSV with financial records (hours worked, amounts, reference numbers) for various Swiss business customers. There are no personal identifiers (no names, emails, phone numbers, etc.) present in the visible data. All columns appear to be business-related transaction data, which according to the exclusion rules must be skipped. No PII fields detected.

finanzen__Abschluesse__Abschluss_2008__abgrenzung_2008__Debitoren_-_TA.csv
0 rows

File structure

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

Notes: This is a financial statement document with no personal identifiable information (PII). All columns contain account codes, transaction descriptions, dates, and monetary values related to corporate financial records. No customer names, contact details, or personal data present. The structure appears to be a standard general ledger or trial balance format with accounting line items.

finanzen__Abschluesse__Abschluss_2008__abgrenzung_2008__Debitoren_-_TP.csv
0 rows

File structure

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

Notes: This is an unstructured financial data file with no personal identifiable information (PII). Columns appear to be financial ledger entries and internal accounting codes (e.g., 'Debitoren - Transitorische Passiven', 'Rg Nr.', monetary values). No email addresses, phone numbers, names, or other PII fields are present in the sample data.

finanzen__Abschluesse__Abschluss_2008__abgrenzung_2008__Kreditoren_-_TA.csv
0 rows

File structure

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

Notes: This is a financial ledger with accounting codes and monetary values. No personal identifiable information (PII) is present. Columns contain accounting entries, dates, and financial amounts, all of which are internal business data without any customer or employee PII. All columns are marked as skip per exclusion rules (company/business data, internal IDs, timestamps, financial/transactional data).

finanzen__Abschluesse__Abschluss_2008__abgrenzung_2008__Kreditoren_-_TP.csv
0 rows

File structure

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

Notes: This is purely financial accounting data (accounts payable ledger) with no personal identifiers. Columns contain accounting codes, dates, amounts, and totals — no names, emails, addresses, or other PII. All columns map to skip categories (company financial records, timestamps, transaction IDs).

finanzen__Abschluesse__Abschluss_2008__abgrenzung_2008__Vorsuazahlungen.csv
0 rows

File structure

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

Notes: This is an unstructured financial statement document from Zynex AG. The data appears to be accounting entries with columns for account ledger entries, amounts, and balances. No personal identifiable information (PII) fields are present - all columns contain internal financial data, account numbers, dates, and monetary values. The format lacks consistent personal data fields like names, addresses, emails, etc. This is typical corporate financial documentation rather than customer PII data.

finanzen__Abschluesse__Abschluss_2008__umbuchung_4200_einkauf_2008__82_Einkauf_f_r_Eigenbedarf.csv
0 rows

File structure

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

Notes: This is a financial record file with no personal identifying information (PII). Columns contain invoice descriptions, amounts, and internal accounting codes. No emails, phone numbers, names, addresses, or other PII fields are present. All columns are skipped per rules (company/business references, financial data, internal codes).

finanzen__Abschluesse__Abschluss_2008__umbuchung_4200_einkauf_2008__83_Einkauf_f_r_Verkauf.csv
0 rows

File structure

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

Notes: This is NOT a PII dataset. The file appears to be a financial/booking ledger from Zynex's internal corporate systems (FaktNT ERP). Columns contain transaction codes, item descriptions, customer names (businesses), amounts, and accounting codes — but NO personal PII fields (no emails, phones, DOB, SSN, etc.). Values like 'SSN' in column 6 appear to be accounting labels, not actual Social Security Numbers. Customer names like 'HEIMGARTNER cmf' and 'Treuhand Brunner' are business entities (Swiss SMEs), not individuals. This is purely financial record-keeping data from the breach context.

finanzen__Abschluesse__Abschluss_2009__85_Debitoren_-_Transitorische_Passiven_2008__85_Debitoren_-_Transitorische_P.csv
0 rows

File structure

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

Notes: This is purely financial/accounting data from Zynex's ERP system (FaktNT). Columns represent Swiss accounting line items (debits/credits), fiscal years (2008/2009), and monetary values. No personal identifiers (names, emails, addresses, etc.) are present — all values are internal accounting codes, dates, and CHF amounts. All columns map to skip per rules (company financials, timestamps, internal IDs).

finanzen__Abschluesse__Abschluss_2009__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
78 rows

File structure

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

finanzen__Abschluesse__Abschluss_2009__86_Debitoren_-_Transitorische_Aktiven__86_Debitoren_-_Transitorische_A.csv
0 rows

File structure

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

Notes: This file contains only financial/accounting data and internal business identifiers. Column 0 contains internal account codes ('Debitoren - Transitorische Aktiven (noch nicht erhaltene Erträge)'), and all other columns contain transaction dates, amounts, and totals. No personal identifiable information (PII) is present in any column. All columns are skipped per exclusion rules for financial/transactional data and internal accounting identifiers.

finanzen__Abschluesse__Abschluss_2009__88_Kreditoren_-_Transitorische_Passiven__88_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is a financial ledger with account codes, dates, monetary values, and transaction IDs. No PII fields are present. Columns contain accounting codes (e.g., 'Kreditoren - Transitorische Passiven'), dates, amounts, and internal reference numbers. All values are corporate financial data with no personal identifiers.

finanzen__Abschluesse__Abschluss_2009__89_Kreditoren_-_Transitorische_Aktiven__89_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is a financial ledger with no personal identifiable information (PII). Columns contain accounting codes, dates, monetary values, and transaction identifiers — no names, emails, addresses, or other PII fields. All values represent corporate financial data (domains, dates, amounts, reference numbers).

finanzen__Abschluesse__Abschluss_2009__eigenbedarf_hardware_2009__82_Einkauf_f_r_Eigenbedarf.csv
0 rows

File structure

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

Notes: This is not a PII dataset. All columns contain internal corporate financial codes, product descriptions, vendor names, and invoice amounts. No personal identifiers (names, addresses, emails, etc.) appear in any column. The values are business codes, product SKUs, and numeric amounts — typical of accounting/financial records. No PII mapping possible.

finanzen__Abschluesse__Abschluss_2009__intra_abos__vw_Export_Abos.csv
0 rows

File structure

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

Notes: No PII columns detected. The file contains only corporate entity names, addresses, and financial transaction details (no personal names, emails, phone numbers, etc.). All columns map to corporate/business data or financial metrics and fall under the exclusion rules for company/business-related fields.

finanzen__Abschluesse__Abschluss_2009__intra_customers__vw_Export_Customer_Address.csv
47 rows

File structure

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

finanzen__Abschluesse__Abschluss_2010__82_Einkauf_f_r_Eigenbedarf__82_Einkauf_f_r_Eigenbedarf.csv
0 rows

File structure

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

Notes: This file contains only financial transaction data with internal accounting codes, vendor names, and monetary values. No identifiable personal information (PII) is present in the first 50 rows. Columns appear to represent internal financial categories, line item codes, and amounts rather than customer or employee data.

finanzen__Abschluesse__Abschluss_2010__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger file with no personal identifiable information (PII). Columns contain accounting codes, dates, amounts, and transaction descriptions in German, but no names, addresses, emails, or other PII fields. All values represent financial data such as account numbers, dates, and monetary amounts.

finanzen__Abschluesse__Abschluss_2010__86_Debitoren_-_Transitorische_Aktiven__86_Debitoren_-_Transitorische_A.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's financial ledger entries with account codes, transaction IDs, and monetary values. No personal identifiers (names, emails, addresses, etc.) are present. The columns contain accounting codes like 'Debitoren - Transitorische Aktiven' and transaction references, not PII fields. Therefore, no columns map to PII fields.

finanzen__Abschluesse__Abschluss_2010__88_Kreditoren_-_Transitorische_Passiven__88_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is a financial statement file with accounting codes and amounts. No PII fields are present. Columns contain accounting entries like 'Kreditoren - Transitorische Passiven', dates, and monetary values. All columns map to skip categories (internal financial codes, timestamps, transactional amounts).

finanzen__Abschluesse__Abschluss_2010__89_Kreditoren_-_Transitorische_Aktiven__89_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is a financial record file with columns representing accounting entries, domain names, dates, and monetary values. No personal identifiable information (PII) fields are present. All columns contain business/financial data, domain names, dates, and monetary amounts — none map to email, phone, name, address, DOB, SSN, etc. The file appears to be internal accounting records for domain fee transactions, not customer PII.

finanzen__Abschluesse__Abschluss_2010__abos__vw_Export_Abos.csv
3 columns253 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'RelationDisplayName', values are person or entity names
2fullNamehigh[2] header 'CompanyName', values are person or entity names
3cityhigh[3] header 'City', values are city names

Notes: Only three columns contain PII: fullName (appears twice), and city. All other columns are transactional/business data (descriptions, amounts, cycles) and must be skipped per exclusion rules.

finanzen__Abschluesse__Abschluss_2010__anzahlungen_2010__anzahlungen_tickets_2010.csv
0 rows

File structure

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

Notes: This is a financial record file with columns representing payment amounts, dates, and internal reference numbers. No personal identifiable information (PII) fields are present. Columns contain data like payment amounts (CHF), internal project references (Rg Nr), dates, and notes about payments (Anzahlung, Projektabrechnung). All columns are internal financial/tracking data and do not contain any names, addresses, emails, phone numbers, or other PII.

finanzen__Abschluesse__Abschluss_2010__hl_incidents__Sheet1.csv
0 rows

File structure

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

Notes: This is not a structured PII file. The columns contain internal corporate tracking codes, status flags, and timestamps rather than personal data. No identifiable PII fields (email, phone, name, address, etc.) are present in the first 50 rows. The values are internal operational codes, priority levels, reference numbers, and status descriptors typical of corporate workflow systems. No columns map to any PII fields.

finanzen__Abschluesse__Abschluss_2011__82_Einkauf_f_r_Eigenbedarf__82_Einkauf_f_r_Eigenbedarf.csv
0 rows

File structure

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

Notes: This file appears to be structured financial records with no identifiable PII fields. All columns contain business transaction details (purchase descriptions, supplier names, amounts, internal codes) without any personal identifiers. The values represent corporate procurement data for IT equipment and services, consistent with the described Zynex financial records breach context.

finanzen__Abschluesse__Abschluss_2011__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
0 rows

File structure

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

Notes: This is a financial accounting file with no personal identifiable information. All columns contain account codes, dates, monetary amounts, and totals. There are no customer names, email addresses, phone numbers, or other PII fields in the data sample. The values appear to be Swiss accounting entries in CHF for hosting services.

finanzen__Abschluesse__Abschluss_2011__86_Debitoren_-_Transitorische_Aktiven__86_Debitoren_-_Transitorische_A.csv
0 rows

File structure

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

Notes: This is purely financial/accounting data from Zynex's ERP system (FaktNT). Columns represent Swiss accounting line items: debit/credit accounts, transaction dates, amounts in CHF, reference numbers, and totals. No PII fields (names, emails, addresses, etc.) are present. All values are financial codes, dates, and monetary amounts.

finanzen__Abschluesse__Abschluss_2011__88_Kreditoren_-_Transitorische_Passiven__88_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is a financial ledger with accounting codes and monetary values. No PII fields detected. Columns represent accounting categories, dates, and financial figures. All columns are skipped per exclusion rules (company/business financial data, internal accounting codes).

finanzen__Abschluesse__Abschluss_2011__89_Kreditoren_-_Transitorische_Aktiven__89_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This file contains only internal financial/transactional data (account codes, amounts, dates, internal reference numbers). No PII fields (names, emails, addresses, etc.) are present. All columns map to skip categories: account descriptions, dates, numeric values, internal IDs, totals. No emails, phone numbers, or personal names appear in the sample.

finanzen__Abschluesse__Abschluss_2011__Aktienbew_2011_Zynex__Daten.csv
0 rows

File structure

Notes: The provided data appears to be free-form financial statements rather than structured records containing PII. The content includes financial years, dividend dates, and accounting labels in German. There is no consistent columnar structure with personal data fields such as names, emails, or addresses. Since there is no evidence of structured tabular data and the content is purely financial/accounting in nature, this is classified as unstructured text.

finanzen__Abschluesse__Abschluss_2011__Aktienbew_2011_Zynex__St_Wert.csv
0 rows

File structure

Notes: The file is free-form financial statements with no consistent columnar structure. The sample shows unstructured corporate financial data (Zynex AG, Volketswil) with no identifiable PII columns. No emails, phone numbers, or address patterns appear in the visible rows.

finanzen__Abschluesse__Abschluss_2011__anzahlungen_nicht_verr_leistungen_2011__anzahlungen_tickets_2010.csv
0 rows

File structure

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

Notes: This is an internal financial record file showing customer payments and project billing. All columns contain financial/tracking data (customer names appear but are mixed with company names in the same column), transaction dates, reference numbers, amounts, and notes. There is no distinct personal PII (no emails, phones, DOB, SSN, etc.). Customer names are not reliably separable from company names in this structure, and there are no columns dedicated to personal identifiers. Therefore, no columns map to PII fields.

finanzen__Abschluesse__Abschluss_2011__anzahlungen_nicht_verr_leistungen_2011__anzahlungen_tickets_2011.csv
0 rows

File structure

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

Notes: This is a financial ledger file with columns representing payment amounts (CHF), dates, transaction references (Rg Nr), and notes. No PII fields are present — all entries are corporate/customer names (regioauto GmbH, Merker AG) and transactional metadata. Customer names are business entities, not personal names, and therefore not mapped to any PII field per exclusion rules. All columns are skipped.

finanzen__Abschluesse__Abschluss_2011__intra_abos__Nur_Hosting.csv
0 rows

File structure

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

Notes: This is NOT a PII file. All columns are internal corporate accounting fields: RelID (internal record ID), RelationDisplayName (internal relationship code), CompanyName (business name, not personal), City (business location), Description (transaction description), AboId (subscription ID), CycleShortDesc (billing cycle), TemplateDetailId (template ID), Artikel (article description), PositionText (position text), ArtikelNr (article number), Konto (account), Kontonummer (account number), DetailAmount (monetary amount), DetailYearlyAmount (yearly amount). No personal PII fields (email, phone, name, address, DOB, SSN) are present. Values are business identifiers, monetary amounts, and transaction metadata typical of financial/billing systems.

finanzen__Abschluesse__Abschluss_2011__intra_abos__buspro.csv
10 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphigh[0] column 'RelID' appears to be an internal record identifier
1skiphigh[1] column 'RelationDisplayName' contains company/organization names, not personal names
2skiphigh[2] column 'CompanyName' contains company/organization names, not personal PII
3cityhigh[3] column 'City' contains Swiss city names
4skiphigh[4] column 'AboId' is a numeric subscription identifier, not PII
5skiphigh[5] column 'Description' contains service descriptions, not PII
6skiphigh[6] column 'CycleShortDesc' contains billing cycle codes ('y' for yearly, 'q' for quarterly)
7skiphigh[7] column 'AmountNet' contains monetary values, not PII
8skiphigh[8] column 'CycleUnit' contains billing cycle codes ('y' for yearly, 'q' for quarterly)
9skiphigh[9] column 'YearlyAmount' contains monetary values, not PII

Notes: This appears to be a financial/billing export from Zynex containing Swiss SME customer data. Only the city column contains PII. All other columns are either internal identifiers, company names, or financial data which must be skipped per rules. No email, phone, name, DOB, SSN, etc. fields are present.

finanzen__Abschluesse__Abschluss_2011__intra_abos__vinx.csv
0 rows

File structure

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

Notes: This is a corporate financial record file from Zynex, not a PII breach. Columns represent company names (columns 2 and 3), locations (column 4), contract types (column 6), amounts (columns 8, 10, 12), and flags (columns 0, 5, 7, 9, 11). No personal PII fields are present — these are business entity records for Swiss SMEs billed for web hosting subscriptions. All columns are internal corporate identifiers, business names, or financial data, which must be skipped per exclusion rules for company/business-related fields.

finanzen__Abschluesse__Abschluss_2011__intra_abos__vw_Export_Abos.csv
10 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighInternal ID: RelID
1skiphighCompany name, not personal PII
2skiphighCompany name, not personal PII
3cityhighHeader 'City' contains city names
4skiphighInternal ID: AboId
5skiphighDescription field contains service names, not PII
6skiphighBilling cycle description
7skiphighMonetary amount
8skiphighBilling cycle unit
9skiphighAnnual amount

Notes: This file contains Swiss business subscription data with no personal PII fields. All columns either contain internal IDs, company names, billing information, or service descriptions. No email addresses, phone numbers, names, or other PII are present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2011__intra_abos__vw_Export_Abos_Detail.csv
0 rows

File structure

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

Notes: This is a corporate financial record file, not customer PII. Columns contain internal IDs (RelID), company names (CompanyName), city codes, invoice descriptions, and financial amounts. No personal PII fields (email, phone, name, address, etc.) are present. All columns are skipped per exclusion rules for company/business data and internal IDs.

finanzen__Abschluesse__Abschluss_2012__82_Einkauf_f_r_Eigenbedarf__82_Einkauf_f_r_Eigenbedarf.csv
0 rows

File structure

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

Notes: This is a financial ledger with internal corporate data (invoices/purchases). No personal PII fields are present. Columns 5 contains vendor names, column 6 contains amounts, column 7 contains internal codes, and the rest are financial totals or empty fields. All columns are internal business data and do not contain any PII.

finanzen__Abschluesse__Abschluss_2012__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's financial ledger entries from Zynex corporate records. Columns contain account codes, dates, monetary values, and transaction IDs — no personal customer identifiers (names, emails, addresses, etc.). The values are accounting line items (e.g., '3400 -- Dienstleistungserlös', '$151'), not customer PII. Per exclusion rules, financial/transactional columns are skipped.

finanzen__Abschluesse__Abschluss_2012__86_Debitoren_-_Transitorische_Aktiven__86_Debitoren_-_Transitorische_A.csv
0 rows

File structure

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

Notes: This is a financial statement file with accounting codes, dates, and monetary values. No PII fields present. Columns contain accounting codes (e.g., '3400 -- Dienstleistungserlös'), dates, and financial amounts. No names, addresses, emails, or other PII visible in the sample data.

finanzen__Abschluesse__Abschluss_2012__88_Kreditoren_-_Transitorische_Passiven__88_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger with no identifiable personal information. Columns contain accounting codes, dates, monetary values, and transaction references. No PII fields (email, phone, name, address, etc.) are present. The data appears to be internal corporate financial records from Zynex's ERP system with no customer or employee personal data exposed.

finanzen__Abschluesse__Abschluss_2012__89_Kreditoren_-_Transitorische_Aktiven__89_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is a financial ledger file with accounting entries in German. Columns contain account names, dates, amounts, and transaction IDs. No PII fields (names, emails, addresses, etc.) are present. All columns map to skip categories: internal accounting codes, dates, amounts, transaction numbers. The file contains purely financial/transactional data with no personal identifiers.

finanzen__Abschluesse__Abschluss_2012__Aktienbew_2012_Zynex__Daten.csv
0 rows

File structure

Notes: The provided data is free-form text with no consistent delimiter structure. It appears to be financial statements or accounting records with years, dates, and financial terms in German. There are no identifiable PII columns in a structured format. However, due to the unstructured nature, we cannot map any columns as PII fields.

finanzen__Abschluesse__Abschluss_2012__Aktienbew_2012_Zynex__St_Wert.csv
0 rows

File structure

Notes: This is unstructured financial prose from Zynex AG annual reports. No consistent columnar structure exists — each line is a free-form sentence/paragraph describing financial metrics like 'Steuerwert der Aktien' and 'Substanzwert'. While the data contains corporate addresses and financial figures, it does not contain personal PII fields (no emails, phones, names, etc.). The format is narrative text, not a delimited record structure.

finanzen__Abschluesse__Abschluss_2012__Bil_2012_Zynex__Anlagesp.csv
0 rows

File structure

Notes: This is a financial statement file with no personal identifiers. Columns contain accounting terms and numerical values in Swiss Francs, with no PII fields present. The data appears to be annual financial records from Zynex AG, a Swiss web hosting company, showing asset balances and depreciation values.

finanzen__Abschluesse__Abschluss_2012__Bil_2012_Zynex__Aufteilung_Bonus.csv
0 rows

File structure

Notes: This is a financial statement document in German with no consistent column structure or personal identifiable information. It contains financial figures, totals, and accounting terms rather than any personal data fields.

finanzen__Abschluesse__Abschluss_2012__Bil_2012_Zynex__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: This file is purely financial data from Zynex AG with no PII columns. It contains corporate financial statements in Swiss Francs (CHF) with headers like 'Aufteilung Gewinn' and values showing percentages and monetary figures. There are no personal identifiers, customer data, or any fields that map to PII categories. The structure appears to be a financial report with no consistent column mapping to personal data fields.

finanzen__Abschluesse__Abschluss_2012__Bil_2012_Zynex__Bilanz.csv
0 rows

File structure

Notes: This is a financial statement document (balance sheet) in German with no consistent columnar structure. The data appears to be formatted as a free-form table with merged cells and financial figures, typical of a balance sheet layout. There are no identifiable personal PII fields (email, phone, name, address, etc.) present in the sample. The content consists entirely of financial line items (assets, liabilities, equity) and monetary values in Swiss Francs (CHF).

finanzen__Abschluesse__Abschluss_2012__Bil_2012_Zynex__Daten.csv
0 rows

File structure

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

Notes: This is not a structured data file with PII columns. The provided rows appear to be financial statements or balance sheet entries from Zynex AG, showing fiscal year data, dates, and monetary values. There are no personal identifiable information (PII) fields such as names, addresses, emails, etc. The data consists of corporate financial records without any customer or employee personal data in the visible rows.

finanzen__Abschluesse__Abschluss_2012__Bil_2012_Zynex__Erfolgsrg.csv
0 rows

File structure

Notes: This is a financial statement document in German with no consistent column structure. It contains rows of financial data without defined headers or delimiters, and appears to be free-form text with financial figures and descriptions. No PII fields are present.

finanzen__Abschluesse__Abschluss_2012__Bil_2012_Zynex__Gewinnverw_.csv
0 rows

File structure

Notes: The file is free-form financial prose (German annual financial statements) with no consistent columnar structure. Contains no identifiable personal PII fields.

finanzen__Abschluesse__Abschluss_2012__Bil_2012_Zynex__Leasingverb.csv
0 rows

File structure

Notes: This file is free-form text with no consistent column structure. It appears to be a financial statement document from Zynex AG for the year 2012, showing leasing liabilities. There are no identifiable columns or structured data containing PII fields. The content consists of narrative financial reporting in German rather than tabular data with personal information.

finanzen__Abschluesse__Abschluss_2012__Bil_2012_Zynex__Mittelflussrg.csv
0 rows

File structure

Notes: This is a financial statement document, not structured personal data. The content appears to be German-language financial statements and balance sheets for Zynex AG from 2010-2012, showing account names and monetary values in Swiss Francs. No personal identifiable information (PII) is present in this financial reporting format.

finanzen__Abschluesse__Abschluss_2012__abos_20130605__vw_Export_Abos.csv
0 rows

File structure

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

Notes: No PII columns detected. All visible columns represent business entities (company names), locations (cities), subscription IDs, and financial figures. No personal identifiers (email, phone, name, address, etc.) appear in the sample data.

finanzen__Abschluesse__Abschluss_2012__anzahlungen_nicht_verr_leistungen_2012__Angefangene_Arbeiten_2012.csv
0 rows

File structure

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

Notes: No PII columns detected. The file appears to be a structured corporate financial record with columns for customer names (not PII per exclusion rules), internal codes, ticket numbers, monetary values, and notes. Customer names like 'Wittich Weine' or 'Cosmos Capital' are business entities, not personal PII. All columns are mapped to 'skip' per rules for company/business-related fields and internal IDs/timestamps.

finanzen__Abschluesse__Abschluss_2012__anzahlungen_nicht_verr_leistungen_2012__Anzahlungen_2011.csv
0 rows

File structure

Notes: The provided data appears to be free-form financial statements and accounting records rather than structured personal data. It contains accounting entries, balances, and financial totals without any identifiable personal information such as names, addresses, emails, or other PII fields. The data is purely financial and transactional in nature, showing account balances, payments, and year-end totals. There are no consistent columns or structured data containing personal identifiers in this sample.

finanzen__Abschluesse__Abschluss_2012__anzahlungen_nicht_verr_leistungen_2012__Anzahlungen_2012.csv
0 rows

File structure

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

Notes: This is a financial ledger file with no PII fields. Columns contain customer names that appear to be business entities or internal project codes, transaction dates, reference numbers, amounts in CHF, payment status, and notes about project billing. No email addresses, phone numbers, SSNs, or other personally identifiable information are present. All customer names appear to be business names or internal project identifiers rather than individual person names.

finanzen__Abschluesse__Abschluss_2013__82_Einkauf_f_r_Eigenbedarf__82_Einkauf_f_r_Eigenbedarf.csv
0 rows

File structure

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

Notes: This file appears to be a financial ledger or purchase record from Zynex. Columns contain transaction details, product descriptions, vendor names, quantities, prices, and totals. No identifiable personal information (PII) such as names, addresses, emails, phone numbers, DOB, SSN, etc. is present. All columns represent business transaction data, product information, and financial figures. Therefore, no PII fields to map.

finanzen__Abschluesse__Abschluss_2013__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
0 rows

File structure

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

Notes: This is a financial ledger file with account codes, dates, and monetary values. No PII fields present. Columns contain accounting codes (e.g., '3400 -- Dienstleistungserlös'), dates, and monetary amounts in CHF. All data is corporate financial records with no personal customer information.

finanzen__Abschluesse__Abschluss_2013__86_Debitoren_-_Transitorische_Aktiven__86_Debitoren_-_Transitorische_A.csv
0 rows

File structure

Notes: This is unstructured financial accounting data with no consistent column mapping. The rows contain accounting entries and financial figures (e.g., hosting fees, dates, amounts) but no identifiable personal information fields like names, emails, or addresses. The format appears to be free-form accounting entries rather than a structured dataset with PII columns.

finanzen__Abschluesse__Abschluss_2013__88_Kreditoren_-_Transitorische_Passiven__88_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger with no personal identifiable information (PII). Columns contain accounting codes, dates, monetary values, and transaction references. No columns map to PII fields. The data appears to be internal corporate accounting records from Zynex's financial system, containing ledger entries, account codes, and financial figures without any customer or employee personal data.

finanzen__Abschluesse__Abschluss_2013__89_Kreditoren_-_Transitorische_Aktiven__89_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is a financial ledger file with accounting entries and transaction codes. No PII fields are present. Columns contain account descriptions, dates, amounts, transaction numbers, and totals — all business/financial data without personal identifiers. All columns map to skip categories (company accounting codes, financial amounts, internal transaction IDs, dates).

finanzen__Abschluesse__Abschluss_2013__abos_20140411__vw_Export_Abos.csv
0 rows

File structure

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

Notes: No PII detected in the first 50 rows. The data consists entirely of corporate client names, addresses, hosting descriptions, and financial amounts — no personal identifiers such as email, phone, or SSN appear.

finanzen__Abschluesse__Abschluss_2013__abschluss_2013_anzahlungen_2013__Angefangene_Arbeiten_2013.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter structure. It appears to be a financial report or ticket log from Zynex with customer names, ticket numbers, and amounts, but lacks a consistent column structure across rows. While there are customer names present (e.g., 'Château Ziltener', 'Bioline', 'Process Product Design'), the data is not in a tabular format with repeating columns. The file contains financial amounts and descriptions but does not have a structured column layout that can be mapped to PII fields.

finanzen__Abschluesse__Abschluss_2013__abschluss_2013_anzahlungen_2013__Anzahlungen_2012.csv
0 rows

File structure

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

Notes: This is a financial ledger with no personal identifiable information. Columns represent business entities (Kunde), dates (Datum), reference numbers (Rg Nr), amounts in CHF, payment status, and notes. No PII fields detected.

finanzen__Abschluesse__Abschluss_2013__abschluss_2013_anzahlungen_2013__Anzahlungen_2013.csv
0 rows

File structure

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

Notes: This is a financial/billing dataset from Zynex's ERP system. All columns represent transactional data (invoice numbers, dates, customer names (business entities), notes, account codes, amounts, taxes). None contain personal PII fields like email, phone, DOB, SSN, etc. Customer names ('Kunde') refer to business entities (associations, companies) not individuals. All columns are skipped per rules: internal IDs (Bel.-Nr.), timestamps (Datum), business names (Kunde), account codes (Konto, G-Konto), transaction text (Text), monetary values (Soll, Haben, Steuer), and tax codes (Steuercode).

finanzen__Abschluesse__Abschluss_2013__anzahlungen_2013__Anzahlungen_2013.csv
0 rows

File structure

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

Notes: This is purely financial ledger data with accounting codes, dates, amounts, and VAT codes. No personal or identifiable information is present. Columns map to accounting fields (document number, date, account codes, amounts) and contain no PII fields such as names, addresses, emails, or phone numbers.

finanzen__Abschluesse__Abschluss_2013__anzahlungen_nicht_verr_leistungen_2013__Angefangene_Arbeiten_2012.csv
0 rows

File structure

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

Notes: This file appears to be internal corporate financial records from Zynex, a Swiss web hosting company. Columns contain business/client names (e.g., "Wittich Weine", "Cosmos Capital"), ticket codes, monetary values, and internal notes — but NO personal PII fields (no email, phone, DOB, SSN, etc.). All columns are mapped as 'skip' per exclusion rules (Company/Business names, internal IDs, financial/timestamps). No actionable PII present.

finanzen__Abschluesse__Abschluss_2013__anzahlungen_nicht_verr_leistungen_2013__Anzahlungen_2011.csv
0 rows

File structure

Notes: This is a financial statement in German showing account balances and customer prepayments. The data is purely accounting data with no personal identifiers or PII fields. There are no columns or structured records containing names, addresses, emails, etc. The format is free-form tabular financial data with no consistent delimiter structure across lines.

finanzen__Abschluesse__Abschluss_2013__anzahlungen_nicht_verr_leistungen_2013__Anzahlungen_2012.csv
0 rows

File structure

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

Notes: This file contains financial records with customer names and transaction details, but no PII fields such as email, phone, DOB, SSN, etc. The 'Kunde' column contains business names (e.g., 'BIN 707', 'Verein Tecum', 'Garpunkt', 'GDI', 'BZS', 'Bioline') and does not represent personal names. All other columns are transactional/financial data (dates, reference numbers, amounts, payment status, notes) which are not PII according to the defined field types. No columns map to available PII fields.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
0 rows

File structure

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

Notes: This file contains internal financial records with accounting codes and monetary values. No PII fields (names, emails, addresses, etc.) are present. Columns contain accounting entries like "Debitoren - Transitorische Passiven", dates, monetary amounts, and totals — all internal business data without personal identifiers.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Abschluss_2013_Zynex__Ang_Arb.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or structured columns; appears to be financial ledger entries in German with no identifiable PII fields

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Abschluss_2013_Zynex__Anz_vKdn.csv
0 rows

File structure

Notes: This is a free-form financial ledger document in German with no consistent column structure. The lines contain account names, amounts, and dates but do not follow a fixed delimiter pattern across rows. While there are numeric values that could resemble financial data, there are no visible emails, phone numbers, or other PII in this sample. The format does not meet criteria for CSV/TSV parsing; it is a narrative financial statement with embedded accounting entries rather than tabular data.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Abschluss_2013_Zynex__T_zu_Anhang.csv
0 rows

File structure

Notes: This is a free-form financial statement document in German, not a structured dataset with columns. The content shows account balances and totals for 2013 and 2012, with no personal identifiable information (PII) fields present. The data appears to be internal corporate financial records rather than customer PII.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Abschluss_2013_Zynex___berstd_2012.csv
0 rows

File structure

Notes: This is a free-form text file (not a structured CSV/TSV) with no consistent delimiter. The lines contain unstructured data records with no repeating columnar format. No PII can be extracted via column mapping; any potential PII would require unstructured text scanning.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Abschluss_2013_Zynex___berstd_2013.csv
0 rows

File structure

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

Notes: This file is NOT a PII-containing dataset. It appears to be an internal financial/HR report from Zynex AG showing employee compensation metrics, overtime calculations, and year-end balances. Columns contain only corporate metadata (salary components, year-end totals) and employee names in German which are not identifiable PII in this corporate context. No emails, addresses, DOB, SSN, or other personal identifiers present. All columns map to skip per rules (company data, internal IDs, timestamps).

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Abschluss_2013_Zynex___berstd_2014.csv
0 rows

File structure

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

Notes: This file is a financial/HR report from Zynex AG, containing employee working hours, salary data, and accruals. No personal identifiers (PII) are present — all columns contain internal company codes, numeric values, and structured financial/temporal data. Columns with names like 'Name' actually contain employee surnames only in a header example, but the actual data rows show numeric codes and financial figures, confirming this is not actual PII. No emails, phone numbers, addresses, DOB, or other PII fields are present.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Aktienbew_2013_Zynex__Daten.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be financial statement lines rather than tabular data. Each line contains mixed financial labels and values without a fixed delimiter pattern.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Aktienbew_2013_Zynex__KStA.csv
0 rows

File structure

Notes: This is unstructured financial prose from Zynex AG corporate records. Lines contain financial statements, legal notes, and accounting headers in German. No consistent columnar structure exists — values are free-form text blocks describing share values, tax years, and balance sheet items. No identifiable PII present.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Aktienbew_2013_Zynex__St_Wert.csv
0 rows

File structure

Notes: This is a free-form financial report from Zynex AG. The data contains corporate financial statements and accounting notes rather than structured PII fields. There are no consistent columns or delimiters, and the content consists of financial commentary and figures rather than personal data. No identifiable personal information is present.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Dividenden-Abrechnung__Abr_Brunner.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample contains unstructured German financial statements and corporate communications from Zynex AG, including names and addresses, but lacks a tabular format. The content appears to be a printed dividend statement with personal data embedded in prose. Since there is no consistent column structure across rows, this qualifies as unstructured data with embedded PII requiring special processing.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Dividenden-Abrechnung__Abr_Leisi.csv
0 rows

File structure

Notes: This is a free-form document (financial statement/dividend notice) with no consistent column structure. It contains Swiss franc amounts, dates, and names but lacks tabular data. Per the unstructured opt-out rules, no column mapping is performed. The file should be processed through a streaming free-text extractor for embedded PII like names and potentially addresses.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Dividenden-Abrechnung__Abr_Poulton.csv
0 rows

File structure

Notes: This file is free-form text (German corporate financial document) with no consistent column structure. Contains embedded personal data like names and addresses, but due to unstructured format, it must be processed via unstructured extraction pipeline. No column mapping possible.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Dividenden-Abrechnung__Dividende.csv
0 rows

File structure

Notes: The provided data is free-form financial statements (German) with no consistent columnar structure. It contains financial tables and narrative text rather than delimited records with personal identifiers. No PII fields are present in this sample.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Form_25_2014_Zynex__2003.csv
0 rows

File structure

Notes: This is not a data file with PII columns. The provided content appears to be a Swiss tax document (Eidgenössische Steuerverwaltung) with financial records and corporate details for Zynex AG. It contains no identifiable personal information (PII) fields such as names, addresses, emails, phone numbers, etc. The data is purely financial and corporate in nature, including references to tax forms, amounts, and dates. Therefore, no PII columns can be mapped.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Form_25_2014_Zynex__2007.csv
0 rows

File structure

Notes: This is a free-form document (Swiss tax form) with no consistent columnar structure. It contains financial data and institutional references but no identifiable personal information in structured columns. The format is unstructured prose with tabular sections that do not represent consistent PII fields across rows.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Form_25_2014_Zynex__2008.csv
0 rows

File structure

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

Notes: This file appears to be a Swiss tax document (Antrag auf Rückerstattung der Verrechnungssteuer) from the Eidgenössische Steuerverwaltung. It contains financial and accounting data (interest rates, nominal values, maturity dates, gross yields) but no personal identifiable information (PII). All columns map to financial records or administrative codes and therefore should be skipped. No email, phone, name, address, DOB, SSN, or other PII fields are present.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Form_25_2014_Zynex__2011.csv
0 rows

File structure

Notes: This is a free-form financial document from the Swiss Federal Tax Administration (Eidgenössische Steuerverwaltung). It contains no structured columns — it's a narrative PDF-like form with embedded financial data and timestamps. No consistent delimiter or column pattern exists across rows. Contains timestamps but these are not personal DOB. No PII fields are present.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Form_25_2014_Zynex__2014.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent columnar structure. It appears to be a tax form (Antrag auf Rückerstattung der Verrechnungssteuer) from the Swiss Federal Tax Administration, not a dataset containing personal PII fields. The text contains only financial figures, dates, and tax calculations with no names, addresses, or other PII. No columns to map.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__MWST-Abr_2013_Zynex.__2013-1.csv
0 rows

File structure

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

Notes: This is a financial statement document (MWST-Abrechnung 2013) with no personal identifiable information. Columns contain accounting codes, cumulative values, and quarterly references but no PII fields such as names, addresses, emails, etc. All columns map to skip per exclusion rules (financial/transactional data).

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__MWST-Abr_2013_Zynex.__2013-2.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2013__dokumente_pb__MWST-Abr_2013_Zynex.__2013-3.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's a financial statement document (VAT accounting) with no personal identifiers. The content appears to be German VAT accounting rows showing cumulative amounts and quarterly figures, with no customer or individual data present. All columns contain financial accounting codes and monetary values, not personal information.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__MWST-Abr_2013_Zynex.__2013-4.csv
0 rows

File structure

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

Notes: This is not structured PII data. The file appears to be an internal financial document from Zynex, containing VAT accounting data (MWST-Abrechnung) for 2013. The columns represent financial codes, adjustments, cumulative VAT amounts, and quarterly breakdowns. There are no personal identifiable information (PII) fields such as names, addresses, emails, phone numbers, or dates of birth. The content is purely financial and institutional, detailing VAT calculations and adjustments for Swiss SMEs billed for web hosting/CMS subscriptions.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__MWST-Abr_2013_Zynex.__MWST-Schl.csv
0 rows

File structure

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

Notes: This is a financial statement file with accounting codes, VAT rates, and account descriptions in German. No PII fields are present. Columns contain tax codes (USt24, VSM24), percentages, account numbers, and descriptive text about deliveries, services, and VAT calculations. All columns map to skip categories per rules (company financial data, internal accounting codes, tax rates).

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__MWST-Abr_2013_Zynex.__Umsatz-Abst.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; contains financial statements and tax calculations in German

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__MWST-Abr_2014_Zynex.__2014-1.csv
0 rows

File structure

Notes: This is an unstructured financial document (MWST-Abrechnung 2014 - Swiss VAT statement). The file contains no identifiable personal data columns; all lines are free-form text describing VAT calculations, totals, and accounting codes. No consistent delimiter or column structure exists across rows.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__MWST-Abr_2014_Zynex.__2014-2.csv
0 rows

File structure

Notes: This file is purely financial/accounting data with no personal identifiable information. It contains VAT accounting codes, cumulative totals, and quarterly financial figures, but no names, emails, addresses, or other PII. The content aligns with the breach description of internal financial records from Zynex.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__MWST-Abr_2014_Zynex.__2014-3.csv
0 rows

File structure

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

Notes: This is a financial statement document (MWST-Abrechnung 2014 - VAT Settlement 2014) with no personal identifiable information. The columns contain accounting codes, totals, and quarterly financial figures in Swiss Francs. No PII fields present.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__MWST-Abr_2014_Zynex.__MWST-Schl_neu.csv
0 rows

File structure

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

Notes: This file contains only financial/accounting codes and percentages - no PII present. Columns represent VAT rates, account codes, and descriptions in German. All values are numeric codes, percentages, or internal accounting terminology. No email, phone, name, address, or other PII fields detected.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__MWST-Abr_2014_Zynex.__Umsatz-Abst.csv
0 rows

File structure

Notes: This is a free-form financial document in German, structured as a VAT reconciliation table. It contains no columnar data or identifiable personal information. The format is tabular but not CSV; it's a row-based financial summary with labels and calculations, not structured records with PII fields. No columns exist to map.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2014_Zynex__2012.csv
0 rows

File structure

Notes: This is an unstructured financial document (invoice/receipt) with no consistent columnar structure across rows. It contains payment references and account numbers but lacks a repeated delimiter pattern. The content is free-form German financial text with varying line structures and embedded monetary values rather than a CSV/TSV format. Per rules, unstructured files with no consistent delimiter and variable line shapes are mapped to empty columns object.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2014_Zynex__2013.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent columnar structure. It contains Swiss invoice/reconciliation data for Zynex AG and HELBLING AG, showing account balances, payments, and bank details, but lacks any personal PII fields like names, emails, or addresses in a structured format. The document is purely transactional/financial in nature.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2014_Zynex__2014.csv
0 rows

File structure

Notes: This is a free-form invoice/receipt document in German with no consistent columnar structure. Contains embedded personal data (Ramon Wellinger) and bank details (Credit Suisse, Konto-Nr.: 414700-01, IBAN CH48 0483 5041 4700 0100 0) but lacks a repeating tabular format. Per unstructured rules, no column mapping is performed.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2014_Zynex__Vorlage.csv
0 rows

File structure

Notes: This is a free-form invoice document in German with no consistent column structure. It contains financial data and account information but lacks a tabular format with repeating rows and columns. The content appears to be a single invoice/receipt rather than structured records containing personal identifiable information (PII).

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2015_Zynex_-_prov__2012.csv
0 rows

File structure

Notes: This is a free-form financial document/receipt with no consistent column structure. It contains payment details and account information but lacks tabular columns. The content appears to be a Swiss invoice/reconciliation statement from Helbling AG to Zynex AG, showing account balances, payment references, and bank details. Since there is no consistent delimiter or row structure, this qualifies as unstructured text with embedded financial data rather than a structured dataset with mappable PII columns.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2015_Zynex_-_prov__2013.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent columnar structure. It contains Swiss financial statements and invoices from Zynex AG to HELBLING AG regarding pension contributions and insurance premiums. While it contains company names, addresses, and account numbers, there are no identifiable personal PII fields (names, emails, phones, DOB, etc.). The document is purely corporate financial data.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2015_Zynex_-_prov__2014.csv
0 rows

File structure

Notes: This is a free-form financial document (invoice/receipt) with no consistent columnar structure. It contains company details (Zynex AG, HELBLING AG), addresses, phone numbers, account information, and payment instructions, but lacks any repeating tabular format that would allow column mapping. The document appears to be a Swiss pension fund contribution statement with references to an individual (Ramon Wellinger) but does not present structured personal data fields like email, DOB, or SSN in a repeatable format. Per unstructured rules, no column mapping is performed.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2015_Zynex_-_prov__2015.csv
0 rows

File structure

Notes: This is an unstructured financial document (invoice/receipt) with no consistent columnar structure. It contains free-form text including account numbers and bank details, but lacks the tabular format required for column mapping. The content appears to be a Swiss Life pension fund contribution invoice for Zynex AG, with references to contract E80C9F and individual Ramon Wellinger.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2015_Zynex_-_prov__Vorlage.csv
0 rows

File structure

Notes: This is an unstructured financial document in German containing Swiss invoices and accounting details. It has no consistent columnar structure (prose-style lines with varying fields). While it contains Swiss bank account details and financial amounts, it does not contain any identifiable PII fields (names, emails, phone numbers, addresses, etc.). The content is purely transactional financial data from a corporate Swiss Life pension fund payment and 3CX license invoice.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2015_Zynex__2012.csv
0 rows

File structure

Notes: This is a free-form financial document (invoice/reconciliation) from HELBLING AG to Zynex AG regarding Swiss Life pension contributions. No consistent columnar structure exists; it's a narrative document with financial figures and payment instructions. Contains no personal PII fields beyond corporate entity names and bank account details which are excluded by policy.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2015_Zynex__2013.csv
0 rows

File structure

Notes: The file appears to be a financial statement/receipt document in German with no consistent columnar structure. It contains invoice details, account balances, and payment instructions rather than personal identifiable information fields. This is corporate financial data from Zynex AG and HELBLING AG rather than customer PII data. The text format shows free-form financial documentation without any repeated field patterns or delimiters.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2015_Zynex__2014.csv
0 rows

File structure

Notes: This file is free-form text with no consistent columnar structure. It contains financial statements and billing records from Zynex AG and Helbling AG, with no identifiable PII columns. Values appear to be German-language financial documents referencing contract numbers and account details, but no personal names, addresses, emails, or other PII fields are present in the sample.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2015_Zynex__2015.csv
0 rows

File structure

Notes: This is a free-form financial statement document from HELBLING AG for Zynex AG. The text contains company names, addresses, account numbers, and financial figures, but no personal identifiable information (PII) fields like names, emails, or phone numbers of individuals. The structure is unstructured with no consistent column mapping possible.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__RG_BVG_2015_Zynex__Vorlage.csv
0 rows

File structure

Notes: The provided text is a free-form financial invoice/receipt document in German with no consistent columnar structure. It contains Swiss bank account details (Credit Suisse, IBAN CH48 0483 5041 4700 0100 0) and payment references, but lacks any repeating tabular format. This qualifies as unstructured text per the rules (a) no consistent delimiter, (b) each line has different content/length, (c) contains financial identifiers). It should be processed through unstructured text extraction rather than columnar PII mapping.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Stb_2013_Zynex__Bet_Ertrag.csv
0 rows

File structure

Notes: This is a financial report document in German with tabular data but no consistent columnar structure across rows. It contains accounting figures, percentages, and references to tax calculations rather than personal identifiable information. There are no delimited fields that map to PII types.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Stb_2013_Zynex__Daten.csv
0 rows

File structure

Notes: The file is free-form financial statements/prose with no consistent columnar structure. It contains corporate financial data for Zynex AG (Swiss web hosting/CMS company) spanning 2011-2013, with no personal customer/user data visible in the sample. This is not a breach containing PII but rather internal corporate financial reporting.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Stb_2013_Zynex__Jahr.csv
0 rows

File structure

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

Notes: This is unstructured financial data from Zynex AG. The file contains corporate financial records with no personal identifiable information (PII). Columns include company identifiers, fiscal years, and financial period markers, but no names, addresses, emails, or other PII fields. Therefore, no PII columns to map.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Stb_2013_Zynex__LCF.csv
0 rows

File structure

Notes: The file is free-form financial prose with no consistent columnar structure. It contains financial statements and accounting data in German, but no identifiable personal information or PII fields. The content consists of accounting terms, years, and monetary values without any personal identifiers.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Stb_2013_Zynex__Rst.csv
0 rows

File structure

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

Notes: This is a financial statement document from Zynex AG with no personal identifiable information (PII). Columns contain accounting terms, financial figures, and fiscal years. No columns map to any PII fields.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Stb_2013_Zynex__RstGJ.csv
0 rows

File structure

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

Notes: This is a free-form financial statement document with no structured columns containing PII. The data appears to be Swiss corporate tax records with years, tax types, amounts, and dates, but no personal identifiable information such as names, addresses, emails, or phone numbers. All values are numeric or generic tax codes.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Stb_2013_Zynex__Spartenrg.csv
0 rows

File structure

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

Notes: This is unstructured financial reporting data (Zynex AG financial statements). Columns contain corporate financial narrative text, totals, and Swiss accounting codes — no personal PII fields. All columns map to skip due to company/business context and financial reporting nature. No email, phone, name, address, DOB, SSN, or other PII present.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Stb_2013_Zynex__St.csv
0 rows

File structure

Notes: This file appears to be unstructured financial/prose data from Zynex AG's internal records. It contains no consistent columnar structure or identifiable PII fields. The content consists of financial descriptions, tax references, and Swiss location mentions rather than structured personal data fields.

finanzen__Abschluesse__Abschluss_2013__dokumente_pb__Stb_2013_Zynex__StE.csv
0 rows

File structure

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

Notes: This file is purely financial reporting with no personal identifiers. All columns contain corporate financial data (capital accounts, reserves, tax liabilities, profit/loss figures) with no customer or employee PII. No emails, names, addresses, or other personal data appear in the first 50 rows.

finanzen__Abschluesse__Abschluss_2014__82_Einkauf_f_r_Eigenbedarf__82_Einkauf_f_r_Eigenbedarf.csv
0 rows

File structure

Notes: This is unstructured data with no consistent delimiter or header. The sample shows free-form financial records with mixed text, numbers, and codes rather than a structured table with identifiable PII columns. No column mapping is possible.

finanzen__Abschluesse__Abschluss_2014__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
67 rows

File structure

Notes: This is unstructured financial data from a corporate accounting system. There are no consistent columns or delimiters, and the content appears to be German financial statements and invoice records with account codes, dates, and monetary values. No PII fields are present.

finanzen__Abschluesse__Abschluss_2014__86_Debitoren_-_Transitorische_Aktiven__86_Debitoren_-_Transitorische_A.csv
1 rows

File structure

Notes: This file is free-form financial data with no consistent column structure. Values appear to be financial line items, dates, and amounts from internal accounting records rather than structured tabular data with identifiable PII columns. No PII fields can be mapped.

finanzen__Abschluesse__Abschluss_2014__88_Kreditoren_-_Transitorische_Passiven__88_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is an accounting ledger file with financial transaction codes and amounts. No PII fields are present — all columns contain account codes, dates, and monetary values. The header row is blank and values are structured financial data, not personal information. This is corporate financial data from Zynex's internal ERP system, consistent with the breach context (billing records and financial statements).

finanzen__Abschluesse__Abschluss_2014__89_Kreditoren_-_Transitorische_Aktiven__89_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is a financial ledger with accounting codes and amounts. No PII fields are present. Columns contain accounting entries, dates, and monetary values but no personal information such as names, emails, addresses, etc. All columns map to skip categories (financial/transactional data, internal accounting codes).

finanzen__Abschluesse__Abschluss_2014__abos_20150326__vw_Export_Abos.csv
3 columns240 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'RelationDisplayName', values are full business entity names (e.g., 'Bruno Mettler & Partner', 'Dr. Peter W. Jermann', 'Walzinger')
3fullNamehigh[3] header 'CompanyName', values mirror RelationDisplayName field (e.g., 'Bruno Mettler & Partner', 'Dr. Peter W. Jermann', 'Walzinger')
4cityhigh[4] header 'City', values are geographic locations (e.g., 'Zürich', 'Praroman-Le Mouret/FR', 'Evilard')

Notes: CSV contains 50 rows of Swiss SME client data from Zynex breach. Only three PII columns identified: fullName (appears twice as RelationDisplayName and CompanyName), and city. All other columns contain contractual/financial data (AboId, Description, CycleShortDesc, AmountNet, etc.) which are skipped per rules. No email, phone, dob, ssn, or password present in sample.

finanzen__Abschluesse__Abschluss_2014__abschluss_2014_anzahlungen_2014__Angefangene_Arbeiten_2014.csv
0 rows

File structure

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

Notes: This file contains purely transactional/support records with company names (Kunde), support staff initials (Supporter), timestamps, ticket numbers, and financial amounts. No personal PII fields (email, phone, name, address, etc.) are present. All columns are business-related or internal identifiers. Therefore, no PII columns to map.

finanzen__Abschluesse__Abschluss_2014__abschluss_2014_anzahlungen_2014__Anzahlungen_2012.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger with no personal identifiers. Columns represent customer names (non-PII business entities), dates, reference numbers, amounts, and notes about payments and billing status. No PII fields (emails, phones, SSNs, etc.) are present. The content consists of corporate transaction records between Zynex and Swiss SME customers for web hosting services.

finanzen__Abschluesse__Abschluss_2014__abschluss_2014_anzahlungen_2014__Anzahlungen_2014.csv
0 rows

File structure

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

Notes: This file contains only transaction data (invoice numbers, dates, customer names, amounts, hours worked, rates). No PII fields are present. The 'Kunde' (customer) column contains business names (Swissdrink, Casa del Vino, EG Biel) — not personal names. All columns map to skip categories: Bel.-Nr. is an internal invoice ID, Datum is a timestamp, Kunde is a business name, Bemerkungen is a note, CHF is a monetary amount, Geleistet 2014 is hours worked, and à CHF 160/h is a rate. No emails, phones, addresses, DOB, SSN, or other PII is present.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Abschluss_2014_Zynex__Ang_Arb.csv
0 rows

File structure

Notes: This is a free-form financial/procedural document with no column structure. Contains accounting entries, invoice references, dates, and amounts in Swiss Francs (CHF). No consistent delimiter or repeating column pattern across rows. Visible entries include invoice IDs (e.g., 20140236), dates (ISO format), amounts, and descriptive text. No PII present.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Abschluss_2014_Zynex__T_zu_Anhang.csv
0 rows

File structure

Notes: free-form text with no consistent column structure — appears to be raw financial statement lines from Zynex AG corporate records, not customer PII. No emails, phones, or personal names visible in the sample. All lines are financial line items with no repeating delimiter structure.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Abschluss_2014_Zynex___berstd_2012.csv
0 rows

File structure

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

Notes: This file contains no PII fields. Columns appear to be internal corporate financial records with employee names (Brunner Mark, Leisi Martin) but these are not identifiable personal data in a breach context. All columns represent internal corporate metrics, timestamps, and financial calculations — no emails, phones, addresses, SSNs, or other PII. The 'Name' column contains employee surnames and given names but lacks sufficient context to be treated as PII in this corporate financial dataset. No columns map to available PII fields.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Abschluss_2014_Zynex___berstd_2013.csv
0 rows

File structure

Notes: This is an unstructured file containing free-form text with no consistent delimiter or row structure. The sample shows German-language corporate financial records with employee names and numeric values, but lacks a tabular format. The file appears to be a mix of descriptive text and financial data, not a structured CSV with identifiable PII columns.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Abschluss_2014_Zynex___berstd_2014.csv
0 rows

File structure

Notes: This is unstructured corporate financial data with no consistent columnar pattern. The file contains German-language financial descriptions and numerical values related to employee compensation, overtime, and year-end balances. There are no identifiable PII fields (names, emails, addresses, etc.) visible in the sample rows. The values appear to be internal financial metrics rather than personal customer data.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Aktienbew_2014_Zynex__Daten.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be financial summary rows with years and amounts, not structured tabular data with columns

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Aktienbew_2014_Zynex__KStA.csv
0 rows

File structure

Notes: This is unstructured financial prose from a corporate data breach. The file contains free-form text describing financial metrics, tax years, and stock values rather than structured records with PII columns. No consistent delimiter or column structure is present across the sample rows.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Aktienbew_2014_Zynex__St_Wert.csv
0 rows

File structure

Notes: This is corporate financial documentation from Zynex AG, containing balance sheets, equity values, and dividend information rather than customer PII. No structured columns containing personal data are present in the sample.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Dividenden-Abrechnung__Abr_Brunner.csv
0 rows

File structure

Notes: This file appears to be a free-form financial statement document in German with no consistent column structure. It contains unstructured text with embedded personal data including a name (Markus Brunner) and address (Sonnenweg 11, 8604 Volketswil). Since the data is unstructured with no consistent delimiter or column pattern, it should be processed as unstructured text with embedded PII extraction.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Dividenden-Abrechnung__Abr_Leisi.csv
0 rows

File structure

Notes: The file is free-form text with no consistent column structure. It appears to be a corporate financial statement or dividend notice from Zynex AG, containing unstructured German prose and financial figures. There are no identifiable PII fields in a structured format; any names present (e.g., Martin Leisi, Markus Brunner) appear embedded in narrative text rather than as tabular data. This qualifies as unstructured content requiring free-text processing.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Dividenden-Abrechnung__Abr_Poulton.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Dividenden-Abrechnung__Dividende.csv
0 rows

File structure

Notes: The file appears to be a free-form financial statement document in German (dividend calculations for 2014). It contains no consistent columnar structure — each line is a separate statement line with varying field counts and content patterns. While it contains financial data, there is no identifiable personal PII (no names, addresses, emails, etc.). The format is unstructured prose, not CSV/TSV.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Form_25_2014_Zynex__2003.csv
0 rows

File structure

Notes: This is a free-form document (Swiss tax form) with no consistent columnar structure. It contains financial data and institutional headers but no personal PII fields. The content is purely institutional/financial and lacks any identifiable personal data patterns.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Form_25_2014_Zynex__2007.csv
0 rows

File structure

Notes: The file is free-form text with no consistent columnar structure. It appears to be a Swiss tax document (Eidgenössische Steuerverwaltung) with financial and accounting data from Zynex AG. There are no identifiable PII columns in a structured format, though the text may contain embedded names and addresses in prose. This qualifies for unstructured processing.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Form_25_2014_Zynex__2008.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's a Swiss tax document (Eidgenössische Steuerverwaltung) showing financial records for Zynex AG. Contains only corporate financial details (interest rates, values, dates, tax calculations) with no personal identifiable information. No columns map to PII fields.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Form_25_2014_Zynex__2011.csv
0 rows

File structure

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

Notes: This is not a PII file. The content appears to be a Swiss tax form (Eidgenössische Steuerverwaltung) showing financial data for Zynex AG — bond holdings, interest income, tax calculations — but contains no personal identifiers, only corporate financial records and tax reference numbers. No columns map to PII fields.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Form_25_2014_Zynex__2014.csv
0 rows

File structure

Notes: free-form text with embedded structured financial data, not columnar PII

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__MWST-Abr_2014_Zynex.__2014-1.csv
0 rows

File structure

Notes: This is a free-form financial document (VAT statement) with no consistent columnar structure. Contains only accounting terms and numerical values, no personal PII. The data appears to be a Swiss VAT filing summary with quarterly totals and line item codes, not customer data.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__MWST-Abr_2014_Zynex.__2014-2.csv
0 rows

File structure

Notes: This is not structured data with PII columns. The file appears to be financial statements / VAT reports from Zynex (Swiss web hosting company) covering 2014. Columns contain accounting codes, cumulative totals, and quarterly figures — no personal identifiers. No emails, phone numbers, names, or addresses are visible. This is purely corporate financial documentation.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__MWST-Abr_2014_Zynex.__2014-3.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's a financial statement document (MWST-Abrechnung 2014) containing tax and revenue figures. Columns contain accounting codes, cumulative totals, and quarterly figures in CHF. No personal identifiable information (names, emails, addresses, etc.) is present. The content consists of financial terminology in German and numerical values, typical of corporate financial reporting rather than customer or employee PII records.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__MWST-Abr_2014_Zynex.__MWST-Schl_neu.csv
0 rows

File structure

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

Notes: This appears to be a financial ledger or accounting table in German, containing tax codes (USt), percentages, account numbers, and descriptions of deliveries/services. No PII fields detected — all columns contain internal accounting codes, percentages, and numeric identifiers. This aligns with the breach description of financial records from Zynex.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__MWST-Abr_2014_Zynex.__Umsatz-Abst.csv
0 rows

File structure

Notes: This is a free-form financial document (MWST-Abstimmung 2013) with no consistent columnar structure. It contains only financial calculations, account codes, and tax-related entries — no identifiable personal data. All rows are structured as key-value pairs or descriptive lines, not tabular data with repeated fields. No emails, phone numbers, or other PII are visible in the sample.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__RG_BVG_2015_Zynex__2012.csv
0 rows

File structure

Notes: This file is a free-form financial document/receipt in German with no consistent column structure. It contains embedded financial amounts and bank details but lacks repeating tabular rows. While it contains sensitive financial data and a bank account number, it does not conform to a delimited structured format with repeating rows/columns, so it is classified as unstructured text for specialized processing.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__RG_BVG_2015_Zynex__2013.csv
0 rows

File structure

Notes: The provided data is unstructured financial text (invoice/receipt) with no consistent column structure or delimited records. It contains Swiss financial transaction details, addresses, and account numbers but lacks tabular format. Since there is no shared delimiter or consistent column structure across lines, this qualifies as unstructured text per the rules. No column mapping is performed.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__RG_BVG_2015_Zynex__2014.csv
0 rows

File structure

Notes: The provided data is unstructured financial/legal correspondence in German (not a CSV). It contains no consistent columnar structure or repeating fields — instead it's a narrative invoice/reconciliation letter between Zynex AG and Helbling AG regarding pension contributions and account balances. There are no identifiable PII fields in this excerpt (only corporate names, account numbers, and amounts). Since this is unstructured free-form text with no column mapping possible, we return an empty columns object.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__RG_BVG_2015_Zynex__2015.csv
0 rows

File structure

Notes: This is a free-form financial document/receipt with no consistent columnar structure. Contains company names, addresses, account numbers, and financial figures, but lacks any repeating PII fields like names, emails, or DOBs in a tabular format. The content appears to be a Swiss Life pension fund contribution statement for Zynex AG, with payment details and account references. Since there is no consistent delimiter or row structure, this is classified as unstructured text.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__RG_BVG_2015_Zynex__Vorlage.csv
0 rows

File structure

Notes: This is a free-form financial invoice document with no consistent columnar structure. It contains Swiss financial data (CHF amounts), company names (Zynex AG, HELBLING AG), addresses, and bank account details, but lacks any repeating tabular structure with identifiable PII columns. The data appears to be a single invoice/receipt document rather than a dataset with rows of personal information.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Stb_2014_Zynex__Bet_Ertrag.csv
0 rows

File structure

Notes: This is a free-form financial statement document in German with no consistent columnar structure. The data appears to be a table of financial participation and tax calculations for Zynex AG, but lacks any identifiable personal information (PII). There are no emails, phone numbers, or other PII visible in the sample. The format is unstructured financial prose, not a delimited data file with columns.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Stb_2014_Zynex__Daten.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. It contains accounting data and financial metrics but no identifiable personal information (PII). The format appears to be a static financial report rather than structured records with personal data fields.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Stb_2014_Zynex__Jahr.csv
0 rows

File structure

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

Notes: The provided data appears to be structured financial records from Zynex AG with no identifiable PII fields. Columns contain Swiss corporate identifiers, fiscal year markers, and accounting codes rather than personal information. No email addresses, phone numbers, names, dates of birth, or other PII are present in the visible rows.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Stb_2014_Zynex__LCF.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. It contains unstructured text lines describing financial years, balances, and tax entries. There are no identifiable PII fields or structured data columns to map.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Stb_2014_Zynex__Rst.csv
0 rows

File structure

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

Notes: This is an unstructured financial document from Zynex AG with no identifiable personal information. All columns contain corporate financial data such as account names, fiscal years, tax types, status codes, and financial figures. No PII fields are present.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Stb_2014_Zynex__RstGJ.csv
0 rows

File structure

Notes: free-form text with embedded financial data, no consistent column structure. Contains financial statements and tax records without any personal PII fields like names, emails, or addresses.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Stb_2014_Zynex__Spartenrg.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Stb_2014_Zynex__St.csv
0 rows

File structure

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

Notes: This file contains corporate financial records and internal accounting data from Zynex AG. There are no personal PII fields present; all columns contain business names, financial terms, percentages, and internal codes. No columns map to email, phone, name, address, DOB, SSN, etc. The data is purely corporate financial and operational in nature.

finanzen__Abschluesse__Abschluss_2014__dokumente_pb__Stb_2014_Zynex__StE.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent column structure. It contains corporate financial data (balance sheet items, equity, profit/loss, tax provisions) formatted as prose paragraphs with aligned numeric values rather than a tabular structure. While it contains sensitive corporate financial data, it does not contain personal PII fields (names, addresses, SSNs, etc.). No column mapping is possible as there is no consistent delimiter or row structure.

finanzen__Abschluesse__Abschluss_2014__kontoauszug_3470_anzahlungen__Tabelle1.csv
0 rows

File structure

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

Notes: This is purely financial accounting data (invoices, balances) with no personal identifiable information. All columns are internal accounting fields (Bel.Nr., Datum, Text, Soll, Haben, G-Konto, Steuerbetrag, Saldo) and contain no PII. The values are transaction IDs, ISO dates, invoice descriptions, monetary amounts in CHF, and internal account codes. No names, addresses, emails, or other PII appear in the sample.

finanzen__Abschluesse__Abschluss_2015__11_Ums_tze_nach_Kunden__11_Ums_tze_nach_Kunden.csv
0 rows

File structure

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

Notes: The file contains purely financial transactional data (customer names, revenue figures) with no personal identifiable information (PII) fields. All entries are corporate entities (AG/GmbH/SA) and monetary values. No emails, addresses, phone numbers, dates of birth, or other PII are present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2015__82_Einkauf_f_r_Eigenbedarf__82_Einkauf_f_r_Eigenbedarf.csv
0 rows

File structure

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

Notes: This is a financial ledger showing purchases for internal use (in German). Columns contain transaction codes, item descriptions, vendor names, amounts, and quantities. No PII fields are present — all data relates to corporate accounting for hardware purchases (motherboards, coolers, RAM). No emails, names, addresses, or other personal data appear in the first 50 rows.

finanzen__Abschluesse__Abschluss_2015__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
0 rows

File structure

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

Notes: This file contains only internal financial accounting codes, amounts, and dates. No PII fields are present. All columns are internal accounting codes (e.g., 'Debitoren - Transitorische Passiven'), amounts, or dates that do not contain personal information. No emails, phone numbers, names, addresses, or other PII are visible in the sample data.

finanzen__Abschluesse__Abschluss_2015__88_Kreditoren_-_Transitorische_Passiven__88_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger with no identifiable PII columns. All entries appear to be internal accounting codes, dates, and monetary values related to vehicle maintenance expenses for a Swiss corporate entity. No personal identifiers (names, emails, addresses, etc.) are present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2015__89_Kreditoren_-_Transitorische_Aktiven__89_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This file contains financial/accounting data with no personal identifiers. Columns describe accounting entries like 'Kreditoren - Transitorische Aktiven' with values representing cost centers, dates, amounts, and transaction IDs. No PII fields (email, phone, name, etc.) are present. All columns are financial metadata or internal accounting codes.

finanzen__Abschluesse__Abschluss_2015__abos_20160321__Tabelle1.csv
0 rows

File structure

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

Notes: No PII columns detected. All visible fields are company names, addresses, invoice identifiers, and financial amounts — none contain personal identifiers like names, emails, phone numbers, or dates of birth. The data represents corporate billing records for web hosting services.

finanzen__Abschluesse__Abschluss_2015__abos_20160321__Tabelle3.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be financial records with no personal identifiers visible in the sample

finanzen__Abschluesse__Abschluss_2015__abos_20160321__draft.csv
0 rows

File structure

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

Notes: No PII columns detected. All fields appear to be business identifiers, financial amounts, and hosting descriptions. No personal identifiers (email, phone, names, addresses, etc.) are present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2015__abschluss_2015_anzahlungen_2015__Angefangene_Arbeiten_2014.csv
0 rows

File structure

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

Notes: The file is purely transactional financial data with customer names (Kunde) but no PII fields like email, phone, DOB, etc. All columns represent business identifiers, amounts, dates, and notes about services rendered. Customer names are company names or business entities, not personal PII. No email addresses, phone numbers, or other personally identifying information is present.

finanzen__Abschluesse__Abschluss_2015__abschluss_2015_anzahlungen_2015__Anzahlungen_2012.csv
0 rows

File structure

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

Notes: This file contains financial transaction records with customer names and dates, but no identifiable PII fields (email, phone, dob, etc.). Customer names appear to be business entities (BIN 707, Verein Tecum, Garpunkt, GDI, BZS, Bioline) rather than personal names. All columns represent financial data, timestamps, or internal reference codes — no columns map to PII categories. The 'Kunde' column contains business names, not personal fullName/firstName/lastName. Timestamps are transaction dates, not DOB. No emails, phones, addresses, SSNs, or passwords present.

finanzen__Abschluesse__Abschluss_2015__abschluss_2015_anzahlungen_2015__Anzahlungen_2014.csv
0 rows

File structure

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

Notes: This file contains only internal financial records (Bel.-Nr. invoice number, Datum date, Kunde customer name, Bemerkungen notes, CHF amount, Geleistet 2014 hours worked, à CHF 160/h rate). No PII fields are present. 'Kunde' (customer name) appears to be business names (Swissdrink, Casa del Vino, EG Biel) rather than personal names, and is excluded per rules for company/business references. All columns are internal transactional data — no emails, phones, addresses, or other PII.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__Aktienbew_2015_Zynex__Daten.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be financial/prose data showing tax year and fiscal year entries with no identifiable PII columns

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__Aktienbew_2015_Zynex__KStA.csv
0 rows

File structure

Notes: This is unstructured financial/prose data from Zynex AG corporate records. No consistent column structure or delimiter exists across rows. The sample contains financial statements and corporate notes rather than personal PII fields. All rows are free-form text with no identifiable PII in the given sample.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__Aktienbew_2015_Zynex__St_Wert.csv
0 rows

File structure

Notes: The provided rows are unstructured financial prose from Zynex AG corporate records (Swiss accounting statements), not delimited data. Sample lines contain text like 'Zynex AG, 8604 Volketswil', 'Steuerwert der Aktien', and 'Substanzwert'. No consistent columnar pattern exists, and the content describes financial metrics rather than personal data. Since this is unstructured corporate documentation with no PII fields, return empty columns.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__Dividenden-Abrechnung_2015__Abr_Brunner.csv
0 rows

File structure

Notes: This is a free-form financial statement document in German with no consistent columnar structure. It contains Swiss corporate financial data for Zynex AG, including dividend calculations and tax information. While it contains personal names (Markus Brunner) and addresses (Volketswil, Sonnenweg 11), these appear in narrative form rather than as structured columns. The document format is unstructured prose with no consistent delimiter or column pattern across lines.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__Dividenden-Abrechnung_2015__Abr_Leisi.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's a free-form financial statement/dividend notice in German from Zynex AG. Contains company details, shareholder name (Martin Leisi), address (Volketswil), and financial figures, but lacks consistent columnar structure across rows. No mappable PII fields present as it represents corporate correspondence rather than customer records. Values like 'Martin Leisi' appear in free text rather than as structured columns.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__Dividenden-Abrechnung_2015__Abr_Poulton.csv
0 rows

File structure

Notes: The provided data is unstructured free-form text containing corporate financial records and addresses rather than a delimited dataset with consistent columns. It includes Swiss business addresses, contact numbers, and financial calculations, but lacks a repeating tabular structure with identifiable PII fields across rows. This appears to be a corporate financial statement document rather than a breach export with personal customer data.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__Dividenden-Abrechnung_2015__Dividende.csv
0 rows

File structure

Notes: The provided data is a free-form financial report document (Gewinnausschüttung 2015) with no consistent columnar structure. It contains German-language financial calculations for dividends, tax withholdings, and net payouts across shareholders. There are no identifiable PII columns — the names ('Brunner', 'Leisi', 'Poulton') appear to be shareholder surnames only, not full personal records. This is typical corporate financial reporting with no importable personal data fields.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__MWST-Abr_2015_Zynex__2015-1.csv
0 rows

File structure

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

Notes: This is unstructured financial accounting data (VAT statements) with no personal identifiers. Columns contain accounting codes, corrections, cumulative totals, and quarterly references. No PII fields present.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__MWST-Abr_2015_Zynex__2015-2.csv
0 rows

File structure

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

Notes: This file appears to be a financial statement document (MWST-Abrechnung) in German, showing VAT calculations for 2015. The content consists of accounting codes (Ziffer 200, 205, etc.), monetary values, and fiscal period labels (Quartals). No personal identifiable information (PII) is present — all columns contain purely financial/accounting data and fiscal terminology. All columns are marked as skip per exclusion rules for financial/transactional data.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__MWST-Abr_2015_Zynex__MWST-Schl_neu.csv
0 rows

File structure

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

Notes: This appears to be a financial ledger or accounting file from Zynex. All columns contain accounting codes, percentages, and descriptions related to VAT (USt), revenue (Umsätze), and account numbers. No personal identifiable information (PII) such as names, addresses, emails, or phone numbers is present. Columns are purely internal financial identifiers and do not map to any PII fields.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__MWST-Abr_2015_Zynex__Umsatz-Abst.csv
0 rows

File structure

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

Notes: This is a financial report document (MWST-Abstimmung 2015) with no personal identifiable information (PII). All columns contain financial categories, account codes, and monetary values without any names, addresses, emails, phone numbers, or other PII fields. The content appears to be Swiss VAT reconciliation data for a corporate entity, not customer-level PII data.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__RG_4.Qu.2015_Zynex__Tabelle1.csv
0 rows

File structure

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

Notes: All columns are internal financial identifiers, timestamps, or transaction metadata. No PII fields present. Columns like 'Rg.-Nr.', 'Freie Rg.-Nr.', and 'Adress-Nr.' are internal reference numbers. 'Kurzname' contains company abbreviations (PERFORMAAG, AGTATECAG, etc.), not personal names. Dates are transaction timestamps, not DOB. Values are all corporate financial data — no emails, phone numbers, names, or addresses.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__RG_BVG_2015_Zynex__2012.csv
0 rows

File structure

Notes: This is a free-form financial document/receipt in German with no consistent columnar structure. Contains company names, account numbers, and payment details but lacks any repeatable PII fields like email, phone, or personal names across rows. The format does not conform to CSV/TSV expectations — lines vary in length and content, making it unstructured text. While it contains sensitive corporate/financial data, it does not contain personal PII in a structured format.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__RG_BVG_2015_Zynex__2013.csv
0 rows

File structure

Notes: This is a free-form financial invoice document with no consistent columnar structure. It contains Swiss financial data (salaries, pension contributions, insurance premiums) for Zynex AG from 2013, formatted as a printed invoice with line-by-line entries rather than tabular data. No PII fields are present in structured columns.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__RG_BVG_2015_Zynex__2014.csv
0 rows

File structure

Notes: This is a free-form invoice document with no consistent columnar structure. It contains financial data, addresses, and account numbers, but lacks repeating field positions or delimiters across lines. Contains embedded personal financial data but does not conform to a structured CSV/TSV format.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__RG_BVG_2015_Zynex__2015.csv
0 rows

File structure

Notes: This is a free-form text file containing financial statements and accounting records. It lacks consistent column structure or delimiters across rows, with varying line formats and no repeating tabular structure. While it contains sensitive financial data, it does not contain structured PII fields in columns (no names, emails, phones, etc. in a repeatable format). The content appears to be accounting statements, invoices, and financial transactions rather than customer or personal data records. The unstructured nature means it should be processed through a streaming text extractor rather than column-based PII identification.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__RG_BVG_2015_Zynex__Vorlage.csv
0 rows

File structure

Notes: The provided text is a free-form financial invoice/receipt document from HELBLING AG to Zynex AG. It contains no consistent columnar structure across lines, and appears to be a single prose-style record with mixed German and numeric content. While it contains monetary values and account numbers, these are not mappable to any PII fields per the rules (company accounts, transaction references, and bank details are not personal PII). No structured columns exist to map.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__RG_BVG_2016_Zynex__2012.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a Swiss corporate invoice/receipt document in German with financial data and account numbers, but lacks any structured columns or repeating PII fields. Contains bank account details but these are not personal PII (corporate banking). No identifiable personal records present.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__RG_BVG_2016_Zynex__2013.csv
0 rows

File structure

Notes: The provided data is free-form financial statements and accounting records from Zynex AG and Helbling AG. The text contains no consistent delimiter structure across lines, with varying line lengths and content patterns. While the document contains financial amounts and account numbers (e.g., 'Konto-Nr.: 414700-01', 'IBAN CH48 0483 5041 4700 0100 0'), these are not personal PII fields (they are corporate banking details). There are no identifiable personal email addresses, phone numbers, names, or other PII in the sample. The content is purely corporate financial correspondence in German/Swiss format, making it unstructured with no column mapping possible.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__RG_BVG_2016_Zynex__2014.csv
0 rows

File structure

Notes: This file is a free-form German-language financial document/receipt from HELBLING AG to Zynex AG. It contains no consistent columnar structure — instead it's a narrative invoice/reconciliation showing BVG contributions, premiums, discounts, and payment instructions. There are no identifiable PII fields like names, addresses, or account numbers that would require mapping; all values appear to be corporate references, amounts, and banking details already redacted/anonymized (e.g., 'Zynex AG', 'Swiss Life', account number '414700-01'). This matches the breach context of internal corporate financial records with no exposed customer PII.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__RG_BVG_2016_Zynex__2015.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains financial statements and invoices rather than structured personal records

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__RG_BVG_2016_Zynex__2016.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent columnar structure. It contains Swiss financial records from Zynex AG to HELBLING AG, including invoices, account balances, and payment instructions. There are no identifiable PII fields in a structured format, only unstructured financial data and company references.

finanzen__Abschluesse__Abschluss_2015__dokumente_tb__RG_BVG_2016_Zynex__Vorlage.csv
0 rows

File structure

Notes: This is a free-form financial invoice document with no consistent column structure. The data appears to be a Swiss invoice/receipt from HELBLING AG to Zynex AG regarding pension contributions and insurance premiums. It contains account numbers and bank details but lacks any structured columnar data with PII fields. The format is unstructured text with embedded financial details rather than a delimited dataset.

finanzen__Abschluesse__Abschluss_2016__tickets_abos__11_Ums_tze_nach_Kunden__11_Ums_tze_nach_Kunden.csv
0 rows

File structure

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

Notes: No PII columns detected. This appears to be a financial transaction report showing customer names (which are business entities), invoice amounts, and service types. No personal identifiers like email, phone, or SSN are present. All customer names appear to be business entities (GmbH, AG, SA, etc.) rather than individual persons.

finanzen__Abschluesse__Abschluss_2016__tickets_abos__82_Einkauf_f_r_Eigenbedarf__82_Einkauf_f_r_Eigenbedarf.csv
0 rows

File structure

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

Notes: This is a financial ledger with no personal identifiable information (PII). Columns describe purchase items, suppliers, quantities, and costs in Swiss Francs. No names, addresses, emails, or other PII fields are present. All columns are financial/transactional data and should be skipped.

finanzen__Abschluesse__Abschluss_2016__tickets_abos__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
0 rows

File structure

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

Notes: This is not a PII dataset. All columns appear to be financial/accounting codes, transaction IDs, monetary values, and date references from Zynex's internal financial records. No personal identifiers (names, emails, addresses, etc.) are present. Columns contain accounting codes (e.g., "3410 -- Hosting"), dates (e.g., "5/2/16"), transaction references (e.g., "20160222"), and financial amounts (e.g., "$151"). No PII fields mapped.

finanzen__Abschluesse__Abschluss_2016__tickets_abos__88_Kreditoren_-_Transitorische_Passiven__88_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger file containing Swiss corporate accounting entries. Columns represent accounting codes, transaction dates, amounts, and fiscal years. No personal identifiable information (PII) is present. All columns are financial/business metadata (account codes, net amounts, transaction counts, fiscal years) and should be skipped per exclusion rules for company/business data and transactional records.

finanzen__Abschluesse__Abschluss_2016__tickets_abos__89_Kreditoren_-_Transitorische_Aktiven__89_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is a financial ledger file with no PII columns. All columns represent accounting codes, dates, and monetary amounts related to domain fees and other corporate expenses. No personal information such as names, addresses, or contact details are present.

finanzen__Abschluesse__Abschluss_2016__tickets_abos__abschluss_2016_anzahlungen_2016__Angefangene_Arbeiten_2016.csv
0 rows

File structure

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

Notes: This file contains only business transaction records with no PII fields. Columns include customer names (Kunde), supporters (Supporter), dates, ticket numbers, amounts in CHF, and notes about services rendered. No personal identifiable information such as email, phone, DOB, etc. is present. All columns are skipped per exclusion rules (company/business references, transactional data, timestamps).

finanzen__Abschluesse__Abschluss_2016__tickets_abos__abschluss_2016_anzahlungen_2016__Anzahlungen_2012.csv
0 rows

File structure

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

Notes: This is a financial transaction log with columns: Kunde (customer name), Datum (date), Rg Nr (reference number), CHF (currency amount), geleistet 2012 (payment status), Bemerkungen (notes). No PII fields are present. Customer names appear to be business entities (e.g., 'BIN 707', 'Verein Tecum', 'Garpunkt', 'GDI', 'BZS', 'Bioline') and not individual personal names. All columns map to skip categories: customer names are business entities, dates are transactional timestamps, reference numbers are internal IDs, currency amounts are financial data, and notes contain payment status or project references. No emails, phones, DOB, addresses, SSNs, or other PII are present.

finanzen__Abschluesse__Abschluss_2016__tickets_abos__abschluss_2016_anzahlungen_2016__Anzahlungen_2014.csv
0 rows

File structure

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

Notes: This file contains internal financial records with no PII fields. Columns are: Bel.-Nr. (internal reference number), Datum (timestamp), Kunde (customer name which appears to be business names, not personal), Bemerkungen (notes), CHF (currency amount), Geleistet 2014 (hours worked in 2014), à CHF 160/h (rate). Per exclusion rules, business names and internal identifiers are skipped. No emails, phones, addresses, or other PII present.

finanzen__Abschluesse__Abschluss_2017__tickets_abos__11_Ums_tze_nach_Kunden__11_Ums_tze_nach_Kunden.csv
0 rows

File structure

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

Notes: No PII columns detected. File contains only company names and financial transaction data (amounts, invoice types). No personal identifiers such as email, phone, or names appear in the first 50 rows.

finanzen__Abschluesse__Abschluss_2017__tickets_abos__82_Einkauf_f_r_Eigenbedarf__82_Einkauf_f_r_Eigenbedarf.csv
0 rows

File structure

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

Notes: This file contains purely internal corporate financial data (purchase records, vendor names, internal accounting codes). No personal identifiable information (PII) is present. All columns map to internal business identifiers, financial codes, or amounts. Columns 4 and 5 contain vendor names (Alltron AG) and product descriptions, which are business entities and not personal PII. No emails, phone numbers, names, addresses, DOB, SSN, passwords, or usernames are present.

finanzen__Abschluesse__Abschluss_2017__tickets_abos__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
85 rows

File structure

Notes: This is accounting ledger data showing Swiss Franc (CHF) transactions, account codes, and financial descriptors. The sample contains no personal identifiers or structured fields that map to PII categories. The data represents internal corporate financial records rather than customer PII.

finanzen__Abschluesse__Abschluss_2017__tickets_abos__86_Debitoren_-_Transitorische_Aktiven__86_Debitoren_-_Transitorische_A.csv
0 rows

File structure

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

Notes: This is a financial statement from Zynex showing accounts receivable and deferred income. All columns contain financial codes, dates, and monetary values with no personal identifiers (names, emails, addresses, etc.). Columns 2-5 appear to be account codes and dates, while 6-12 are monetary amounts. No PII fields present.

finanzen__Abschluesse__Abschluss_2017__tickets_abos__88_Kreditoren_-_Transitorische_Passiven__88_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is an unstructured financial report containing account codes, fiscal periods, and monetary amounts. No personal identifiable information (PII) is present. Columns contain accounting entries like 'Kreditoren - Transitorische Passiven', dates (R-Date, SD, ED), and financial figures (Netto, T). All values are internal corporate financial data with no customer or employee PII. The file appears to be a standard accounting ledger/report rather than structured customer or user records.

finanzen__Abschluesse__Abschluss_2017__tickets_abos__89_Kreditoren_-_Transitorische_Aktiven__89_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: No PII columns detected. This appears to be purely financial/accounting data with accounting codes, dates, amounts, and internal reference numbers. All columns map to internal business codes, transaction dates, monetary values, and internal counters — none contain personal information such as names, addresses, emails, or phone numbers. The data reflects corporate financial records from Zynex's ERP system (FaktNT) with accounting entries in Swiss Francs (CHF).

finanzen__Abschluesse__Abschluss_2017__tickets_abos__tickets_jira__Summary.csv
0 rows

File structure

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

Notes: The file contains purely transactional financial data (project names, hours, unit prices, totals) with no personal identifying information. All columns represent internal corporate billing metrics for Zynex services. No PII fields detected.

finanzen__Abschluesse__Abschluss_2018__85_Debitoren_-_Transitorische_Passiven_NEU__85_Debitoren_-_Transitorische_P.csv
152 rows

File structure

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

finanzen__Abschluesse__Abschluss_2018__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorisc__2_.csv
152 rows

File structure

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

finanzen__Abschluesse__Abschluss_2018__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
152 rows

File structure

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

finanzen__Abschluesse__Abschluss_2018__88_Kreditoren_-_Transitorische_Passiven__88_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This file is purely financial/accounting data with no PII columns. It contains ledger entries, dates, and monetary values related to corporate accounting (e.g., MWST tax settlements, accident/disability benefits). All columns are business transactional data and do not contain any personal identifiable information.

finanzen__Abschluesse__Abschluss_2018__89_Kreditoren_-_Transitorische_Aktiven__89_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is a financial ledger file containing accounting entries, not customer PII. No columns map to PII fields. Columns contain account codes, dates, amounts, and transaction metadata. No emails, names, addresses, or other PII are present in the sample.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Angef_Arb.csv
0 rows

File structure

Notes: This file is free-form text with financial statements and accounting data. There is no consistent delimiter or column structure across rows, and the data appears to be narrative financial reporting rather than structured records with PII fields. No PII columns can be mapped.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Anhang.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent columnar structure. The sample shows prose in German describing financial reports and corporate matters, with no delimited fields or repeated patterns. Though no emails/phones are visible in the first 50 rows, the unstructured condition applies because there is no shared delimiter or consistent row shape. This routes to streaming text extraction for any embedded PII.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Anlagesp.csv
0 rows

File structure

Notes: The file appears to be unstructured financial data from Zynex AG, Volketswil. It contains accounting entries and financial metrics (e.g., asset values, depreciation, balances) rather than any personal identifiable information. There are no consistent columns or personal data fields (names, emails, addresses, etc.). The data represents internal corporate financial records spanning 2001–2020, including annual financial statements and subscription billing records.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Anlagesp_2019.csv
0 rows

File structure

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

Notes: This file contains purely financial/accounting data (balance sheet entries, depreciation, asset values) with no personal identifying information. All columns are financial metrics or internal accounting codes — no names, addresses, emails, or other PII fields present. The data reflects corporate asset tracking for Zynex's IT infrastructure and does not expose customer or employee details.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Aufteilung_Bonus.csv
0 rows

File structure

Notes: This is a financial statement document from Zynex AG, Volketswil, not a structured dataset with PII columns. The content shows line items and totals in Swiss Francs (CHF) with no personal identifiers present. The format appears to be free-form financial reporting text, not a CSV with columns.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Aufteilung_Bonus_2014.csv
0 rows

File structure

Notes: This is a free-form financial report containing accounting figures and bonus calculations for Zynex AG. There are no consistent columns or delimiters, and the data consists of structured financial statements and bonus calculations in Swiss Francs (CHF) rather than personal PII records. No identifiable personal information is present.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Aufteilung_Bonus_2015.csv
0 rows

File structure

Notes: This is a free-form financial statement document in German with no consistent column structure. It contains financial figures, account names, and year-over-year comparisons but no identifiable personal information (PII) in a columnar format. The data represents internal corporate financial records of Zynex AG, including vehicle maintenance, insurance, depreciation, telephone expenses, bonuses, and salary figures. While the data is sensitive, it does not contain personal identifiers like names, addresses, emails, or phone numbers in a structured format.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: This is unstructured financial reporting data with no consistent column structure. The rows contain financial metrics and percentages in German, with no identifiable personal information. No PII columns exist.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__BVG-Lohn_2015.csv
0 rows

File structure

Notes: This is a free-form financial table with no consistent column structure or identifiable PII fields. The data appears to be internal financial records showing salary components and totals in Swiss Francs (CHF) across different categories. There are no columns or structured fields that map to PII categories. The format is unstructured financial data rather than a delimited CSV with personal information.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__BVG-Lohn_2016.csv
0 rows

File structure

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

Notes: This is a financial report containing only numeric monetary values and percentages. No personal identifiable information (PII) fields are present. The data appears to be internal corporate financial records from Zynex, showing salary breakdowns, bonuses, and other financial metrics without any names, addresses, or other personal data.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__BVG-Lohn_2017.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__BVG-Lohn_2018.csv
7 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2firstNamehigh[2] header is empty but values are common male first names: M. Brunner, M. Leisi, D. Poulton, etc.
3firstNamehigh[3] header is empty but values are common male first names: M. Brunner, M. Leisi, D. Poulton, etc.
4firstNamehigh[4] header is empty but values are common male first names: M. Brunner, M. Leisi, D. Poulton, etc.
5firstNamehigh[5] header is empty but values are common male first names: M. Brunner, M. Leisi, D. Poulton, etc.
6firstNamehigh[6] header is empty but values are common male first names: M. Brunner, M. Leisi, D. Poulton, etc.
7firstNamehigh[7] header is empty but values are common male first names: M. Brunner, M. Leisi, D. Poulton, etc.
12skiphigh[12] values match MM/DD/YY date pattern: 6/29/77, 6/3/72, 11/29/74, etc.

Notes: CSV with 8 columns, 50 rows of payroll data. Columns 0 and 1 contain generic headers (empty and 'Total'). Columns 2–7 contain first names (M. Brunner etc.). Column 12 contains dates of birth in MM/DD/YY format. All other columns are salary components, totals, percentages, and age calculations — these are financial/temporal data and not PII.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__BVG-Lohn_2019.csv
12 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values match full name patterns (e.g., 'M. Brunner')
3fullNamehigh[3] values match full name patterns (e.g., 'M. Leisi')
4fullNamehigh[4] values match full name patterns (e.g., 'D. Poulton')
5fullNamehigh[5] values match full name patterns (e.g., 'R. Wellinger')
6fullNamehigh[6] values match full name patterns (e.g., 'D. Rosso')
7fullNamehigh[7] values match full name patterns (e.g., 'P. Windhofer')
12skiphigh[12] values match MM/DD/YY date format, labeled 'Geburtsdatum' (German for 'Date of Birth')
13skiphigh[13] values match MM/DD/YY date format, labeled 'Geburtsdatum' (German for 'Date of Birth')
14skiphigh[14] values match MM/DD/YY date format, labeled 'Geburtsdatum' (German for 'Date of Birth')
15skiphigh[15] values match MM/DD/YY date format, labeled 'Geburtsdatum' (German for 'Date of Birth')
16skiphigh[16] values match MM/DD/YY date format, labeled 'Geburtsdatum' (German for 'Date of Birth')
17skiphigh[17] values match MM/DD/YY date format, labeled 'Geburtsdatum' (German for 'Date of Birth')

Notes: 50 rows shown, 8 columns with PII. Columns 0 and 1 are empty headers/labels. Columns 2-7 contain full names. Columns 12-17 contain DOB in MM/DD/YY format under 'Geburtsdatum' (German for 'Date of Birth'). All other columns are financial figures, percentages, or internal totals and are skipped per exclusion rules.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Bilanz.csv
0 rows

File structure

Notes: File is a financial statement in German (Bilanz) showing account balances. No personal or customer data present - only corporate financial aggregates and accounting line items. No PII columns exist.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Daten.csv
0 rows

File structure

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

Notes: This is a financial statement file with no personal identifiable information (PII). The rows contain corporate financial data such as fiscal year end dates and labels like 'Abschluss' (closing), 'Vorjahr' (prior year), and 'Vor-Vorjahr' (year before prior). No names, addresses, emails, phone numbers, or other PII fields are present. The data is purely financial and corporate in nature, consistent with the breach description of internal financial records from Zynex AG.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Detail_ang_Arb.csv
0 rows

File structure

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

Notes: This file contains no PII columns. The data appears to be financial statements and project status records from Zynex AG, with columns representing company names, empty fields, and financial figures. No personal identifiable information (PII) such as names, emails, phone numbers, addresses, or dates of birth is present in the provided sample rows. Columns are either empty or contain company names and financial data, which are excluded per the rules.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: The file is a financial statement document (Bilanz- und Erfolgsrechnungspositionen) showing accounting positions for Zynex AG. There are no consistent columns or structured data — it's a free-form financial report with no personal identifiable information (PII) in the traditional sense. The values appear to be financial figures and account names rather than personal data. This is not a dataset with customer records or PII fields.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__EDV-Bi.csv
0 rows

File structure

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

Notes: This is a financial statement file with account codes, company name, and year-over-year financial figures. No PII fields present — all columns contain internal accounting data (account codes, debit/credit amounts), corporate entity names, and fiscal years. No personal identifiers, contact info, or sensitive customer data.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__EDV-ER.csv
0 rows

File structure

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

Notes: This is a financial data file with no personal identifiers. Columns appear to represent account codes, company names, and financial figures across years (2012-2018). No PII fields detected.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Erfolgsrg.csv
0 rows

File structure

Notes: The provided rows are financial statements (Erfolgsrechnung) in Swiss Francs for Zynex AG. These are structured corporate financial records showing revenue streams like Handelserlös and Dienstleistungsertrag across years 2016-2018. No personal PII fields are present; these are internal business financial data tables. The file is NOT a free-form text with embedded PII, but rather a tabular financial report with no identifiable individuals. Therefore, no columns map to PII fields.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Geldflussrg.csv
0 rows

File structure

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

Notes: This is a financial statement file (Geldflussrechnung - cash flow statement) showing Swiss SME financial data from Zynex AG. The columns contain purely financial/accounting data (revenue, expenses, depreciation, etc.) with no personal identifiers (no names, emails, addresses, etc.). All columns represent financial metrics and years, none map to PII fields. The only textual column (index 4) contains the company name 'Zynex AG' which is a corporate entity, not personal PII.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Gewinnverw_.csv
0 rows

File structure

Notes: This is unstructured financial report data with no consistent column structure or personal identifiers. The file appears to be a financial statement document (likely from FaktNT ERP system) showing Swiss Francs values and annual financial metrics. No PII columns exist as it's purely financial data without customer names, emails, addresses, etc.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Pendenzen.csv
0 rows

File structure

Notes: The provided sample appears to be free-form text with no consistent delimiter structure. The lines contain German phrases and financial descriptions rather than structured columnar data. There are no visible emails or phone numbers in this snippet, but the unstructured format indicates this is likely a prose-style document rather than a CSV with PII columns. Given the absence of a consistent delimiter and row structure, this file should be processed as unstructured text.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Personalvers_2015.csv
0 rows

File structure

Notes: This is not structured data; it's a free-form text file containing financial statements and accounting records from Zynex AG. The rows contain accounting terms and financial figures in German (e.g., 'Personalversicherungsprämien', 'AHV-Beiträge', '(499,228 ') with no consistent columnar structure or PII fields. No identifiable personal data is present in the sample.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Personalvers_2016.csv
0 rows

File structure

Notes: This is a financial report document (Zynex AG, Volketswil) with no identifiable personal data. All columns contain financial metrics, percentages, and account balances in CHF, not personal names, addresses, or other PII fields. The structure is free-form tabular data with no consistent delimiter or header mapping to personal fields. No emails, phones, or names are visible in the sample rows.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Personalvers_2017.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The data appears to be financial statements and accounting entries from Zynex AG, Volketswil, containing German financial terminology and numerical values. There are no identifiable PII fields in structured columns, and the format does not contain embedded emails or phone numbers in a free-text format that would require unstructured extraction.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Plan_prod_Std.csv
0 rows

File structure

Notes: The file appears to be a free-form text financial/production report from Zynex AG. It contains no consistent columnar structure with headers or delimiters. The data consists of German-language financial figures, percentages, and production metrics with no identifiable personal information in structured columns. While there are numerical values, they represent business metrics rather than PII. This is not a CSV or tabular dataset but rather a narrative-style financial report.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__Planung_Kosten_Windhofer.csv
0 rows

File structure

Notes: This is a financial statement document showing revenue and expense line items for Zynex from 2015. The data contains no personal identifiable information (PII) fields such as names, addresses, emails, or phone numbers. All values are financial figures in Swiss Francs (CHF) and textual descriptions of financial categories.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex__St_Wert.csv
0 rows

File structure

Notes: The file appears to be free-form text containing financial statements and corporate notes from Zynex AG. There is no consistent delimiter or row structure; instead, it consists of prose lines describing financial metrics, tax years, and accounting periods. While it contains references to locations like 'Zynex AG, 8604 Volketswil', these are corporate addresses, not individual PII. No identifiable personal data (email, phone, name, etc.) is present in the visible rows. This is a document-style corporate record, not a dataset with columnar PII fields.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex___berstd_2014.csv
0 rows

File structure

Notes: This is an unstructured free-form text file with no consistent column structure. The data appears to be Swiss payroll or employment records with entries like employee names, hours, and salary details, but it's formatted as free text rather than a delimited table. The sample shows entries such as 'Brunner Mark', 'Handschin Simon' (names), but these are embedded in free-form lines without consistent column positions or delimiters.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex___berstd_2015.csv
0 rows

File structure

Notes: The provided data is unstructured text with no consistent columnar format. The sample appears to be internal corporate financial records from Zynex AG, containing employee names and financial data in German. There is no consistent delimiter or header structure across rows, and values represent free-form text entries rather than a tabular dataset. The presence of employee names (e.g., "Brunner Mark", "Leisi Martin") in a free-form layout suggests this file is not a structured CSV but rather a document with embedded personal data. This qualifies as unstructured data requiring special handling for PII extraction.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex___berstd_2016.csv
0 rows

File structure

Notes: This is an unstructured document containing corporate financial and employee data from Zynex AG. The data appears to be formatted as a table with headers like 'Zynex AG, Volketswil', 'Besch.', 'AHV-Lohn', etc., but the structure is irregular with merged cells and inconsistent formatting. There are no clear PII fields like names, emails, or addresses in a structured format. The values appear to be employee names (e.g., 'Brunner Mark', 'Leisi Martin'), but they are embedded within free-form text rather than in a structured columnar format. Given the unstructured nature of the data and lack of consistent columns, this should be processed as unstructured text.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex___berstd_2017.csv
0 rows

File structure

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

Notes: This is a financial/HR document from Zynex AG in Volketswil. Columns contain payroll data, hours, and salary calculations. No PII fields are present — names appear to be sample placeholders ('Brunner Mark', 'Leisi Martin') and all other columns are numeric financial figures, percentages, and internal codes. No emails, addresses, DOB, SSN, or other PII detected.

finanzen__Abschluesse__Abschluss_2018__JRG_2018_Zynex___berstd_2018.csv
0 rows

File structure

Notes: This is not a structured dataset but a free-form text document containing internal corporate financial records from Zynex AG. The sample shows lines with mixed content (descriptive text, employee names, financial figures) without consistent delimiters or column structure. While it contains names like 'Brunner Mark' and 'Leisi Martin', these appear inline with other financial data in a prose-like format rather than in a tabular structure. Per the unstructured opt-out rules, this should be processed as free-form text with embedded PII extraction.

finanzen__Abschluesse__Abschluss_2018__jira_worklog__Summary_Projekte.csv
0 rows

File structure

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

Notes: All columns represent internal financial/project tracking data (project codes, hours, monetary values, currency). No PII fields present. Columns like 'Project' contain internal system identifiers (CMS3, HVX, VXSHOP6), 'CY' is currency code CHF, and all numeric columns represent billing amounts or time tracking — none contain personal identifiers.

finanzen__Abschluesse__Abschluss_2018__jira_worklog__Worklogs.csv
1 column452 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
9fullNamehigh[9] header 'User', values are full names like 'Peter Windhofer', 'Ramon Wellinger', 'Daniel Rosso'

Notes: Only column 9 contains PII (fullName). All other columns are timestamps, project identifiers, activity metadata, or financial amounts — no emails, phones, addresses, DOB, SSN, etc. The values in column 9 are clearly full names, and the header 'User' confirms this mapping. All other columns are internal project management data and must be skipped per rules (timestamps, internal IDs, financial/transactional, etc.).

finanzen__Abschluesse__Abschluss_2018__tickets-angef-arbeiten___draft_jira.csv
0 rows

File structure

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

Notes: This is a Jira ticket export with no PII fields. Columns represent project names, time tracking data, and financial values. No personal identifiers such as names, emails, or addresses are present. All columns are skipped per rules.

finanzen__Abschluesse__Abschluss_2018__tickets-angef-arbeiten__anzahlungen.csv
0 rows

File structure

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

Notes: This is a financial record file with corporate customer names and monetary values. No PII fields (email, phone, dob, etc.) are present. The 'Kunde' column contains business entity names (organizations), which are excluded by the 'Company/Business' exclusion rule. All other columns are financial/timestamps and do not map to any PII field types.

finanzen__Abschluesse__Abschluss_2018__tickets-angef-arbeiten__tickets_anzahlungen.csv
0 rows

File structure

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

Notes: This file contains purely transactional and internal business data (hours worked, billing amounts, customer names for invoicing). No identifiable PII fields (email, phone, DOB, SSN, etc.) are present. Customer names are company names (Boissons Kouski, Château André Ziltener, etc.), not personal names. All data reflects internal financial records of a Swiss web hosting company, with no personal customer identifiers exposed.

finanzen__Abschluesse__Abschluss_2019__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
1 column451 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values are domain names, likely associated with a full name or business entity

Notes: The file is a financial record listing hosting service subscriptions and fees. The second column contains domain names which are treated as a proxy for fullName in this context. No other PII fields are present in the visible data.

finanzen__Abschluesse__Abschluss_2019__86_Debitoren_-_Transitorische_Aktiven__86_Debitoren_-_Transitorische_A.csv
0 rows

File structure

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

Notes: This is not a data file with personal identifiable information (PII). The file appears to be a financial statement or accounting report from Zynex, detailing transitory assets and revenue data for hosting services and software licenses. There are no columns mapping to PII fields such as names, addresses, emails, phone numbers, etc. The content consists of numeric values, dates, and descriptive text about financial transactions, which do not contain personally identifiable information.

finanzen__Abschluesse__Abschluss_2019__89_Kreditoren_-_Transitorische_Aktiven__89_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is an accounting/financial report file with structured columns but no identifiable PII fields. Columns appear to represent financial codes, dates, and monetary values related to corporate expenses and payments. No personal identifiers such as names, addresses, emails, or phone numbers are present in the visible data.

finanzen__Abschluesse__Abschluss_2019__Debitorenumsatzliste__Tabelle_S._1.csv
0 rows

File structure

Notes: This appears to be an internal financial report from Zynex AG rather than customer PII data. The content shows aggregated financial figures, account numbers, and internal references rather than personal information. No email addresses, phone numbers, or other PII are visible in this sample. The structure varies significantly per row with no consistent delimiter pattern.

finanzen__Abschluesse__Abschluss_2019__Debitorenumsatzliste__Tabelle_S._1__2_.csv
0 rows

File structure

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

Notes: This is a financial ledger showing Swiss company names and revenue figures. No PII fields are present — all columns contain corporate entity names, numeric amounts, and identifiers that are not personal identifiers. The column 'Adr. Nr.' appears to be an internal account or client reference number, not a personal identifier. All rows follow a consistent structure with three columns: an account/client number, company name, and monetary value.

finanzen__Abschluesse__Abschluss_2019__Debitorenumsatzliste__performa.csv
0 rows

File structure

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

Notes: This is an unstructured corporate financial file with only business names and revenue figures. No personal PII present. Columns map to company names (Firmenname) and financial data (Umsatz 2019 inkl MWST) — these are explicitly excluded by the 'Company/Business' exclusion rule. No emails, phone numbers, or personal identifiers visible.

finanzen__Abschluesse__Abschluss_2019__Debitorenumsatzliste__umsatz-bereinigt.csv
0 rows

File structure

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

Notes: No PII columns present. File contains only Swiss business names (Firmenname) and financial data (revenue amounts). All columns are corporate/business identifiers or transactional values, not personal PII. Excluded by COMPANY/BUSINESS exclusion rule.

finanzen__Abschluesse__Abschluss_2019__Debitorenumsatzliste__umsatz-pro-partner.csv
0 rows

File structure

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

Notes: This is a financial summary table containing only monetary values and percentages. No PII fields (names, addresses, emails, etc.) are present. Columns contain financial metrics such as totals, VAT-inclusive/exclusive amounts, and percentages of total revenue. All values are numeric or percentage-based financial data with no personal or identifiable information.

finanzen__Abschluesse__Abschluss_2019__Debitorenumsatzliste__umsatz-stats.csv
0 rows

File structure

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

Notes: No PII columns detected. All fields represent corporate entities (company names), financial data (revenue figures), and internal partner codes. No personal identifiers such as names, addresses, emails, or phone numbers appear in the sample.

finanzen__Abschluesse__Abschluss_2019__Debitorenumsatzliste__umsatz-top-bottom.csv
0 rows

File structure

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

Notes: This is a structured CSV file containing Swiss corporate financial records. The columns represent internal business identifiers (Adr. Nr.), company names (Firmenname), annual sales figures (Umsatz 2019 inkl MWST), and partner codes. No PII fields are present - all entries are corporate entities, financial data, and internal codes. The partner codes (px, vx, bp, pw, vp, ecmt) appear to be internal relationship indicators rather than personal data.

finanzen__Abschluesse__Abschluss_2019__jira_worklogs_20191231__angef-arbeiten.csv
0 rows

File structure

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

Notes: The provided data consists of financial records with customer names (Kunde) and transaction details. However, the customer names appear to be company names (e.g., "Maisons Marques et Domaines Suisse SA", "Netrix GmbH"), which fall under the exclusion rule for company/business-related fields. No PII fields such as email, phone, dob, etc., are present in the visible columns. All columns are related to financial transactions and should be skipped per the rules.

finanzen__Abschluesse__Abschluss_2019__jira_worklogs_20191231__jira-tickets.csv
0 rows

File structure

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

Notes: No PII columns detected. All columns appear to be internal financial/project tracking fields (e.g., activity hours, charges, currency codes). Values are project codes, currency markers (CHF), and numeric amounts — no names, emails, addresses, or other PII. This aligns with the described financial records from Zynex's ERP system.

finanzen__Abschluesse__Abschluss_2020__85_Debitoren_-_Transitorische_Passiven__85_Debitoren_-_Transitorische_P.csv
3 columns460 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighFirst column is empty for all rows
3address1highContains website URLs and email domains, maps to address1 as hostnames
4dobhighISO 8601 timestamps (YYYY-MM-DDTHH:MM:SSZ) indicating dates

Notes: 50 rows shown, structured CSV with minimal PII. Only website addresses (mapped as address1) and timestamps (mapped as dob) contain PII. All other columns appear to be financial codes, amounts, and empty fields.

finanzen__Abschluesse__Abschluss_2020__86_Debitoren_-_Transitorische_Aktiven__86_Debitoren_-_Transitorische_A.csv
0 rows

File structure

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

Notes: This is a header-only row or metadata row without any data rows. The row contains only column labels and no actual data values. The content appears to be in German and describes financial categories like 'Debitoren - Transitorische Aktiven (noch nicht erhaltene Erträge)'. There are no PII fields present in this header row.

finanzen__Abschluesse__Abschluss_2020__89_Kreditoren_-_Transitorische_Aktiven__89_Kreditoren_-_Transitorische_.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's financial ledger data with no personal identifiers. Columns represent accounting line items and dates, not personal information. The data appears to be from Zynex's internal financial records showing domain fee transactions, with no customer PII present in this sample.

finanzen__Abschluesse__Abschluss_2020__Debitorenumsatz-Rangliste__Tabelle2.csv
0 rows

File structure

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

Notes: No PII detected in the first 50 rows. The data contains only Swiss business names (e.g., 'agtatec AG', 'Akademie St. Gallen') and financial figures in CHF, with no personal identifiers such as email, phone, or address fields.

finanzen__Abschluesse__Abschluss_2020__Debitorenumsatz-Rangliste__Tabelle_S._1.csv
0 rows

File structure

Notes: The provided data appears to be a free-form text representation of financial statements and corporate records from Zynex AG. There is no consistent delimiter or structured column format across the rows. The values are primarily textual descriptions, financial figures, and internal identifiers rather than personal identifiable information (PII). No clear PII fields are present in the sample.

finanzen__Abschluesse__Abschluss_2020__Debitorenumsatz-Rangliste__Tabelle_S._1__2_.csv
0 rows

File structure

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

Notes: This file contains only business names, invoice amounts and other corporate/financial data. No personal PII fields are present in the first 50 rows. All entries appear to be company names (e.g., 'agtatec AG', 'Akademie St. Gallen') with no individual names, addresses, emails, or other personal identifiers.

finanzen__Abschluesse__Abschluss_2020__Debitorenumsatz-Rangliste__segment.csv
0 rows

File structure

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

Notes: No PII columns present. Columns contain internal IDs, company names, financial figures, and internal codes/flags. All columns either map to internal IDs, company names (which are excluded), financial/transactional data, or internal flags/timestamps per exclusion rules. No emails, phone numbers, names, addresses, DOB, SSN, gender, or passwords detected.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Angef_Arb.csv
0 rows

File structure

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

Notes: This is a financial report file with no personal identifiable information (PII). Columns contain financial metrics and dates but no names, addresses, emails, or other PII fields. All columns are marked as skip per exclusion rules (financial/transactional data).

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Anhang.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent column structure. The rows appear to be narrative descriptions, financial commentary, and corporate notes rather than tabular data. There are no identifiable PII fields in structured columns to map.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Anlagesp.csv
0 rows

File structure

Notes: This is a financial statement document (balance sheet) in German, not structured tabular data with PII. It contains corporate financial metrics like asset values, depreciation, and balance sheet totals. No personal identifiers (names, emails, addresses, etc.) are present. The format is unstructured financial prose with no consistent column structure.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Aufteilung_Bonus.csv
0 rows

File structure

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

Notes: This is not a PII file; it's purely financial data from Zynex AG. Columns contain account names and financial figures in CHF with no personal identifiers. All columns are marked as skip per exclusion rules (company financial data).

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: This is a financial report in German with no personal identifiable information (PII). The data contains corporate financial figures such as profits, bonuses, and tax-related figures for Zynex AG. There are no structured columns containing names, addresses, emails, phone numbers, or other PII fields. The sample values are percentages, financial figures, and text descriptions of financial line items, not personal data.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__BVG-Lohn_2019.csv
12 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values are full names (M. Brunner)
3fullNamehigh[3] values are full names (M. Leisi)
4fullNamehigh[4] values are full names (D. Poulton)
5fullNamehigh[5] values are full names (R. Wellinger)
6fullNamehigh[6] values are full names (D. Rosso)
7fullNamehigh[7] values are full names (P. Windhofer)
12skiphigh[12] values match MM/DD/YY date pattern, column labeled Geburtsdatum
13skiphigh[13] values match MM/DD/YY date pattern, column labeled Geburtsdatum
14skiphigh[14] values match MM/DD/YY date pattern, column labeled Geburtsdatum
15skiphigh[15] values match MM/DD/YY date pattern, column labeled Geburtsdatum
16skiphigh[16] values match MM/DD/YY date pattern, column labeled Geburtsdatum
17skiphigh[17] values match MM/DD/YY date pattern, column labeled Geburtsdatum

Notes: 50 columns total, 7 contain PII (names and DOB). The file is a Swiss corporate financial record with employee names and birthdates. All other columns are financial figures, percentages, or internal calculations.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__BVG-Lohn_2020.csv
8 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2firstNamehigh[2] values match common first names (M. Brunner, M. Leisi, R. Wellinger, etc.), header implies name position
3firstNamehigh[3] values match common first names (M. Brunner, M. Leisi, R. Wellinger, etc.), header implies name position
4firstNamehigh[4] values match common first names (R. Wellinger, D. Rosso, P. Windhofer, etc.), header implies name position
5firstNamehigh[5] values match common first names (D. Rosso, P. Windhofer, K. Parizek, etc.), header implies name position
6firstNamehigh[6] values match common first names (P. Windhofer, K. Parizek), header implies name position
7firstNamehigh[7] values match common first names (K. Parizek), header implies name position
13skiphigh[13] values follow MM/DD/YY date format (6/29/77, 6/3/72, 5/24/89, etc.), header implies birth date
14skiphigh[14] derived from age calculations matching birth dates in column 13

Notes: 50 rows shown, 8 columns visible. Columns 0 and 1 appear to be empty headers/labels. Columns 2-7 contain employee first names. Column 13 contains birth dates in MM/DD/YY format. Age in column 14 validates the DOB mapping. No email, phone, address, SSN, or password data visible in the sample.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Bilanz.csv
0 rows

File structure

Notes: This is a financial statement document (Bilanz) with no columnar structure. It contains accounting entries and financial figures but no personal identifiable information fields. The data represents corporate financials for Zynex AG, not customer PII.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Daten.csv
0 rows

File structure

Notes: The sample rows are unstructured financial statements with no consistent delimiter or row structure. The data appears to be Swiss corporate financial records from Zynex AG with dates and year references, but no identifiable personal information in this snippet. Since there is no consistent column structure, this is classified as unstructured text.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Detail_ang_Arb.csv
0 rows

File structure

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

Notes: This is a financial statement / accounting file (Zynex AG corporate data). All columns contain corporate financial data or empty strings — no personal PII fields (names, emails, addresses, etc.). Column 0 contains entity names that are company/client names, not personal identifiers. All values are account balances, dates, or empty. No PII detected.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: This is a financial statement document (Bilanz- und Erfolgsrechnungspositionen) with no consistent column structure. It contains account titles and financial figures, but no personal identifiable information (PII). The data appears to be internal corporate financial records from Zynex AG, not customer PII.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__EDV-Bi.csv
0 rows

File structure

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

Notes: This is a financial statement file showing account balances over multiple years. Columns contain account codes, account names (in German), and financial figures for years 2012-2020. No PII fields are present; all columns are financial data or internal accounting codes. The file appears to be internal corporate financial records from Zynex AG, not customer PII data.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__EDV-ER.csv
0 rows

File structure

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

Notes: This is purely financial corporate data (revenue statements) with no PII present. Columns represent account codes, company name, and yearly financial figures in CHF. No personal identifiers detected.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Erfolgsrg.csv
0 rows

File structure

Notes: This is a financial statement document (Erfolgsrechnung) showing revenue accounts and figures for years 2018-2020. The data contains no personal or identifiable information — only aggregated financial totals in Swiss Francs. No PII fields present. The structure is tabular but contains only financial data and no customer/user records.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Geldflussrg.csv
0 rows

File structure

Notes: This is a financial statement document (Geldflussrechnung - cash flow statement) with no personal identifiable information. The columns contain financial data such as profit/loss figures, depreciation values, and other accounting metrics for different years (2018-2020). There are no structured PII fields like names, addresses, or contact information. The data appears to be corporate financial reporting rather than customer or employee records.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Gewinnverw_.csv
0 rows

File structure

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

Notes: This file is purely financial reporting data (balance sheets, profit/loss statements) with no personal identifiers. Columns contain only financial figures, year labels, and accounting terms in German. No PII fields detected.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Hardware_RZ.csv
0 rows

File structure

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

Notes: This is a financial statement file showing asset values and depreciation. No PII fields present. Columns represent accounting metrics (balance sheet values, accessions, depreciation rates, etc.). All values are numeric or percentage-based financial data. No personal identifiers detected.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Pendenzen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Personalvers_2017.csv
0 rows

File structure

Notes: This is not structured data; it's a financial document with German text and numerical values. There are no consistent columns or delimiters, and the content appears to be a corporate financial statement from Zynex AG, Volketswil. No PII fields are present.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__Plan_prod_Std.csv
0 rows

File structure

Notes: The file is a free-form financial/production report with no consistent column structure. It contains German financial data, production hours, and revenue figures for Zynex AG. There are no identifiable PII columns in the structured sense, but the unstructured nature means any embedded emails/phones would be handled by a streaming extractor.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex__St_Wert.csv
0 rows

File structure

Notes: This is not structured data. The sample contains financial statements and corporate notes from Zynex AG, formatted as prose paragraphs and tables without consistent columnar structure. There are no identifiable PII fields in this sample; the content appears to be financial reporting and corporate legal text rather than personal customer data. The breach context mentions customer invoicing data exists elsewhere in the archive, but this particular file is purely corporate financial documentation.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex___berstd_2018.csv
0 rows

File structure

Notes: The file is free-form text with no consistent delimiter structure. It contains financial and operational records from Zynex AG, with entries like employee names, working hours, salary components, and year-end balances. There is no structured CSV format, and while names appear (e.g., 'Brunner Mark', 'Leisi Martin'), they are embedded in unstructured prose. This meets the unstructured opt-out criteria: no consistent delimiter, varying line shapes, and embedded PII-like values.

finanzen__Abschluesse__Abschluss_2020__JRG_2020_Zynex___berstd_2020.csv
0 rows

File structure

Notes: This is not a structured data file. The sample shows free-form text with financial and employee records in German, containing no consistent delimiter or column structure. Values appear to be descriptive text, financial figures, and names, but there is no repeating pattern of columns across rows. No PII fields can be reliably mapped as there is no columnar structure.

finanzen__Abschluesse__Abschluss_2020__tickets-angef-arbeiten__angef-arbeiten.csv
0 rows

File structure

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

Notes: The file appears to be purely transactional financial records with no personal identifiable information (PII). Columns contain company names, invoice numbers, dates, amounts, and notes about projects and payments. No email addresses, phone numbers, names, addresses, DOB, SSN, passwords, usernames, gender, or other PII fields are present. All columns are business-related financial data (customer names are company names, not personal names), amounts, dates, and internal reference numbers. Per the exclusion rules, company/business names are explicitly excluded from PII mapping.

finanzen__Abschluesse__Abschluss_2020__tickets-angef-arbeiten__jira-tickets.csv
0 rows

File structure

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

Notes: No PII columns detected. Columns contain project names, hours, charges, and financial totals but no personal identifiers like names, emails, or addresses. All columns are internal financial/tracking data.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Angef_Arb.csv
0 rows

File structure

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

Notes: This file is NOT structured PII data. The sample shows financial/accounting columns with Swiss German descriptions (e.g., 'Angefangene Arbeiten', 'Bilanzwert') and financial figures in CHF. No columns map to any PII fields (email, phone, name, address, etc.). All columns are financial metrics, dates, or empty strings. This is typical corporate financial reporting data, not customer/personal data.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Anhang.csv
0 rows

File structure

Notes: This is unstructured text data — the sample shows free-form German financial/procedural text (annual financial statements, non-invoiced services descriptions) with no consistent tabular structure. Column headers are either empty or placeholder values, and the content appears as narrative paragraphs. Though no emails/phones are visible in this slice, unstructured files may contain embedded PII elsewhere; this routes through streaming extraction.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Anlagesp.csv
0 rows

File structure

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

Notes: This is purely financial accounting data (balance sheet entries, depreciation values, asset listings) with no personal identifiers. All columns contain corporate financial metrics, dates, and calculations — no PII fields present. The data reflects Zynex AG's internal asset tracking in Swiss Francs.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Aufteilung_Bonus.csv
0 rows

File structure

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

Notes: This is an unstructured financial statement file (Zynex AG internal accounting). All columns appear to be financial line items and totals in Swiss Francs, with no personal identifiable information (PII). The values are accounting figures and totals, not names, addresses, or other PII fields. No email, phone, dob, name, address, ssn, password, username, or other PII fields are present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Aufteilung_Gewinn.csv
0 rows

File structure

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

Notes: This is a financial statement file with no PII columns. All columns contain corporate financial data (revenue, expenses, percentages) in Swiss Francs for Zynex AG. No personal identifiers present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__BVG-Lohn_2019.csv
8 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'M. Brunner', values are full names with initials
3fullNamehigh[3] header 'M. Leisi', values are full names with initials
4fullNamehigh[4] header 'D. Poulton', values are full names with initials
5fullNamehigh[5] header 'R. Wellinger', values are full names with initials
6fullNamehigh[6] header 'D. Rosso', values are full names with initials
7fullNamehigh[7] header 'P. Windhofer', values are full names with initials
12skiphigh[12] column 'Geburtsdatum', values in MM/DD/YY format
13skiphigh[13] column 'Alter 2019', age values correspond to birth dates in column 12

Notes: 50 rows of payroll data showing employee names and birth dates. Columns 0 and 1 are empty headers/labels. All numeric columns are salary/benefit figures in CHF and are skipped.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__BVG-Lohn_2020.csv
8 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values match common Swiss last names (Brunner, Leisi, Wellinger, Rosso, Windhofer, Parizek)
3fullNamehigh[3] additional Swiss last names (Brunner, Leisi, Wellinger, Rosso, Windhofer)
4fullNamehigh[4] Swiss last names (Wellinger, Rosso, Windhofer, Parizek)
5fullNamehigh[5] Swiss last names (Rosso, Windhofer, Parizek)
6fullNamehigh[6] Swiss last names (Windhofer, Parizek)
7fullNamehigh[7] Swiss last names (Parizek)
12skiphigh[12] dates in MM/DD/YY format matching Swiss birthdate patterns
13skiphigh[13] derived from adjacent 'Geburtsdatum' column showing ages

Notes: 50 rows of Swiss corporate payroll data showing employee names and birthdates. Columns 0-1 and 8-11 contain non-PII financial totals/percentages. Columns 2-7 contain employee full names. Columns 12-13 contain birthdates in MM/DD/YY format with derived age columns.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__BVG-Lohn_2022.csv
13 columns4 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values match common full names (e.g., 'M. Brunner', 'M. Leisi')
3fullNamehigh[3] values match common full names (e.g., 'M. Leisi', 'R. Wellinger')
4fullNamehigh[4] values match common full names (e.g., 'R. Wellinger', 'D. Rosso')
5fullNamehigh[5] values match common full names (e.g., 'D. Rosso', 'P. Windhofer')
6fullNamehigh[6] values match common full names (e.g., 'P. Windhofer', 'K. Wellinger')
7fullNamehigh[7] values match common full names (e.g., 'K. Wellinger', 'K. Parizek')
12skiphigh[12] values match MM/DD/YY date pattern (e.g., '6/29/77', '6/3/72')
13skiphigh[13] values match MM/DD/YY date pattern (e.g., '6/3/72', '5/24/89')
14skiphigh[14] values match MM/DD/YY date pattern (e.g., '5/24/89', '9/21/87')
15skiphigh[15] values match MM/DD/YY date pattern (e.g., '9/21/87', '7/31/73')
16skiphigh[16] values match MM/DD/YY date pattern (e.g., '7/31/73', '11/29/86')
17skiphigh[17] values match MM/DD/YY date pattern (e.g., '11/29/86', '11/29/74')
18skiphigh[18] values match MM/DD/YY date pattern (e.g., '11/29/74', '5/24/89')

Notes: 50 rows of structured financial data; 8 PII columns (fullName, dob). All rows share the same delimiter pattern. Dates are in MM/DD/YY format. No emails, phones, or SSNs found in the sample.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Bilanz.csv
0 rows

File structure

Notes: The provided data is a financial balance sheet in German (Bilanz) with structured accounting rows and columns. It contains no personal or identifiable information (PII). The data represents financial categories such as assets (AKTIVEN), liabilities (PASSIVEN), equity (EIGENKAPITAL), and account balances in Swiss Francs (CHF) for multiple fiscal years (2018–2021). All entries are financial classifications and numerical values, with no names, addresses, contact details, or other PII fields present. The document is purely an internal corporate financial statement.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Daten.csv
0 rows

File structure

Notes: The sample data is unstructured financial reporting text (Zynex AG annual financial statements) with no consistent columnar structure. It contains free-form financial reporting lines (e.g., 'Abschluss 31.12.2020', 'Abschluss,12/31/20,2020,1/1/20,,,') and lacks repeating record formats. This is not CSV but free-text financial reporting.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Detail_ang_Arb.csv
0 rows

File structure

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

Notes: This file appears to be structured financial statements from Zynex AG, with no personal identifiable information (PII) present in the first 50 rows. Columns contain corporate entity names and financial figures/dates, but no email addresses, phone numbers, names, DOBs, SSNs, or other PII fields. All columns are skipped per exclusion rules (company/business-related data and timestamps).

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: This is not a delimited data file with personal records. It appears to be a financial statement/balance sheet document from Zynex AG with financial position details (German). No personal identifiable information (PII) fields are present. Columns contain financial account names and numeric values in CHF, not personal data such as names, emails, addresses, etc. The structure is free-form financial reporting, not a CSV with PII columns.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__EDV-Bi.csv
0 rows

File structure

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

Notes: This is purely financial accounting data with no personal identifiers. Columns represent financial line items (accounts), years, and amounts in CHF. No PII fields detected.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__EDV-ER.csv
0 rows

File structure

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

Notes: This is purely financial data: company name, accounting years, and financial figures in CHF. No personal identifiers (PII) present. All columns are internal financial metrics or empty. Per breach context, this is Zynex corporate accounting data — not customer PII.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Erfolgsrg.csv
0 rows

File structure

Notes: This is a financial statement / accounting report (Erfolgsrechnung) in German showing revenue figures for Zynex AG. The structure is not tabular data with personal columns — it's a free-form financial summary with year-over-year revenue lines. No PII fields exist in this dataset; it contains only corporate financial aggregates in Swiss Francs (CHF) for years 2018–2021. Therefore, no columns map to PII fields.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Geldflussrg.csv
0 rows

File structure

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

Notes: This is a financial statement file (Geldflussrechnung - Cash Flow Statement) with no personal identifiable information. All columns contain financial metrics, years, percentages, and company name references. No PII fields such as names, addresses, emails, or phone numbers are present. The data appears to be aggregated financial data for Zynex AG from 2018-2021.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Gewinnverw_.csv
0 rows

File structure

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

Notes: This is a financial statement document with no personal identifiable information (PII). Columns contain financial data such as years, monetary values, and corporate financial terms. No PII fields (email, phone, dob, names, address, ssn, password, username) are present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Hardware_RZ.csv
0 rows

File structure

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

Notes: This is a financial statement file showing asset values, depreciation, and balances. No personal or identifiable information is present. Columns contain only financial metrics (e.g., Bilanzwert, Zugänge, Abgänge, Buchwert, Abschreibung) and years. No PII fields detected.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Pendenzen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Personalvers_2017.csv
0 rows

File structure

Notes: This is not structured data; the rows appear to be free-form financial statements and accounting entries rather than a CSV with consistent columns. The text contains accounting terms and figures but no identifiable personal data or structured fields. Since there is no consistent delimiter or column structure, this is classified as unstructured text.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__Plan_prod_Std.csv
0 rows

File structure

Notes: This is a financial report in tabular format but lacks any PII columns. The data contains only financial figures, employee categories, and percentages — no names, addresses, emails, or other personal identifiers. The structure is consistent across rows with financial metrics, but no personal data is present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex__St_Wert.csv
0 rows

File structure

Notes: This is free-form financial text with no consistent column structure. The sample contains corporate financial statements and accounting data for Zynex AG, with no personal PII fields present. No structured columns detected.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex___berstd_2018.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The data appears to be internal corporate financial records from Zynex AG, containing employee names and payroll information, but the format is unstructured with no consistent delimiter or header. The values are in German and appear to be internal accounting data rather than customer PII. No column mapping is possible due to lack of structured format.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex___berstd_2020.csv
0 rows

File structure

Notes: This is not a structured dataset. The provided rows appear to be free-form text with no consistent delimiter or column structure. The content seems to be internal corporate financial records from Zynex AG, containing entries like 'Überstunden- und Ferienguthaben' (overtime and vacation credit), salary figures, and year-end balances. There are no identifiable PII columns in this sample as it lacks any consistent structure or personal identifiers like names, emails, or addresses in a tabular format.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Angef_Arb.csv
0 rows

File structure

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

Notes: This file contains only financial/accounting data (year-end balances, work in progress values) with no personal identifiable information. All columns represent corporate financial metrics, dates, and calculations with no names, addresses, or other PII fields. The values are accounting entries in CHF and percentage calculations.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Anhang.csv
0 rows

File structure

Notes: The provided data is free-form text with no consistent delimiter or structured columns. The content appears to be narrative descriptions and financial commentary in German, typical of annual financial statements or accounting documents. There are no identifiable PII columns to map.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Anlagesp.csv
0 rows

File structure

Notes: This is financial ledger data from Zynex AG with no personal identifiable information. The columns contain account names, balances, depreciation values, and financial calculations — all corporate financial records with no customer PII. No emails, names, addresses, or other PII fields are present in the sample.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Aufteilung_Bonus.csv
0 rows

File structure

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

Notes: This is a financial statement file, not a PII-containing dataset. All columns represent account names and monetary values (e.g., 'Aufteilung Bonus', 'Total', 'MB', etc.). No personal identifiable information is present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Aufteilung_Gewinn.csv
0 rows

File structure

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

Notes: This file contains purely financial statements and corporate data (profit/loss, bonuses, taxes) with no personal identifiers. All columns are corporate financial metrics, percentages, and year labels — no PII present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__BVG-Lohn_2019.csv
8 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'M. Brunner', values match 'First Initial. Last Name' pattern
3fullNamehigh[3] header 'M. Leisi', values match 'First Initial. Last Name' pattern
4fullNamehigh[4] header 'D. Poulton', values match 'First Initial. Last Name' pattern
5fullNamehigh[5] header 'R. Wellinger', values match 'First Initial. Last Name' pattern
6fullNamehigh[6] header 'D. Rosso', values match 'First Initial. Last Name' pattern
7fullNamehigh[7] header 'P. Windhofer', values match 'First Initial. Last Name' pattern
12skiphigh[12] column 'Geburtsdatum' contains valid dates in MM/DD/YY format
13skiphigh[13] column 'Alter 2019' contains integer ages that align with birth dates in column 12

Notes: 50 rows shown; this is payroll data with employee names and birth dates. Columns 0 and 1 are empty headers/labels. All other columns are financial figures and percentages — no PII. DOB mapped from both explicit birth date column and derived age column for completeness.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__BVG-Lohn_2020.csv
3 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values match common Swiss last names (Brunner, Leisi, Wellinger, Rosso, Windhofer, Parizek)
9skiphigh[9] values follow MM/DD/YY date format (6/29/77 = June 29, 1977)
10agehigh[10] values are integer ages (44, 49, 32, 34, 48, 35) that logically correspond to birth dates in column 9

Notes: File contains Swiss employee compensation data with names and birth dates. Columns 0 and 1 are empty headers. Columns 2-8 are employee names. Columns 9-10 are birth dates and calculated ages. Remaining columns contain salary/benefit figures in CHF and internal financial metrics.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__BVG-Lohn_2022.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3firstNamehigh[3] Values are person initials + surnames (M. Brunner, M. Leisi, R. Wellinger, D. Rosso, P. Windhofer, K. Wellinger, K. Parizek, D. Poulton) representing employee names across all salary years
11skiphigh[11] Header 'Geburtsdatum' (birth date in German), values are dates in M/D/YY format (6/29/77, 6/3/72, 5/24/89, 9/21/87, 7/31/73, 11/29/86, 11/29/74)

Notes: Internal payroll/personnel records from Zynex (2015–2022). File contains Swiss employee salary data with birth dates. Names appear only as initials + surnames in column 3 (e.g., 'M. Brunner'), which is insufficient for firstName/lastName separation but clearly identifies individuals. The 'Geburtsdatum' row repeats across multiple years and contains actual birth dates in M/D/YY format. No email, phone, SSN, address, or other PII fields present. Remaining columns contain salary components, percentages, and financial calculations (skip).

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Bilanz.csv
0 rows

File structure

Notes: The file is a financial statement (balance sheet) in German, formatted as a free-form table without identifiable personal data. Contains only corporate financial metrics (assets, liabilities, equity) and account balances. No PII present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Daten.csv
0 rows

File structure

Notes: This is an unstructured financial report document with no consistent columnar structure. It contains free-form text describing financial statements for Zynex AG from 2018-2020, with no identifiable personal information columns. The sample shows header-like lines but they are not consistent across rows and do not contain PII fields.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Detail_ang_Arb.csv
0 rows

File structure

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

Notes: This file is purely structural financial data with no PII present. Column 0 contains organizational names (not personal names), and all other columns contain only dates and numeric financial figures. No columns map to any PII fields per the provided rules.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. The data appears to be a financial statement from Zynex AG showing balance sheet and profit/loss items for various years. There are no identifiable PII fields in the visible structure, only financial figures and account names. This is typical corporate financial documentation without personal customer or employee data.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__EDV-Bi.csv
0 rows

File structure

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

Notes: This is a financial statement file with no personal identifiable information (PII). Columns represent account codes, account names, and financial figures across years. No columns map to PII fields.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__EDV-ER.csv
0 rows

File structure

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

Notes: This is purely financial accounting data from Zynex AG with no personal identifying information. Columns contain account codes, company name, financial years, and monetary values. No PII fields detected.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Erfolgsrg.csv
0 rows

File structure

Notes: This is a corporate financial statement for Zynex AG showing revenue and expense figures across multiple years (2018-2021). The data contains no personal customer or employee information — only aggregated financial totals, percentages, and account labels. All columns are financial metrics or year indicators, with no PII fields present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Geldflussrg.csv
0 rows

File structure

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

Notes: This is a financial statement file (Geldflussrechnung - cash flow statement) for Zynex AG. All columns contain financial data, percentages, and internal accounting codes with no personal identifiable information (PII). No email addresses, phone numbers, names, or other PII fields are present. The data is purely corporate financial records spanning multiple years (2018-2021).

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Gewinnverw_.csv
0 rows

File structure

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

Notes: This file appears to be a financial statement report from Zynex AG in Volketswil, containing annual financial data in Swiss Francs from 2010-2021. All columns contain financial figures, account descriptions, and year labels — no personal identifiable information (PII) such as names, emails, addresses, or contact details is present. Columns 0-27 are all financial data or metadata, and per the exclusion rules, financial/transactional data such as sale_price, sale_date, balance, etc., must be skipped. Therefore, no PII columns to map.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Hardware_RZ.csv
0 rows

File structure

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

Notes: This is a financial ledger file containing only business financial metrics (balance sheet values, depreciation, etc.). No personal or customer PII is present. All columns relate to corporate asset tracking and financial reporting for Zynex's internal operations. No emails, names, addresses, or other PII fields are visible in the sample.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Pendenzen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Personalvers_2017.csv
0 rows

File structure

Notes: This is not structured data with columns; it's a free-form financial report with rows containing account names and monetary values. No consistent delimiter or column structure exists across rows. Contains no identifiable PII fields.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__Plan_prod_Std.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. The data contains financial metrics, personnel hours, and monetary values but no identifiable personal information (PII). The content appears to be internal corporate financial statements and planning documents for Zynex AG, with no customer or employee PII exposed in the visible sample.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT__St_Wert.csv
0 rows

File structure

Notes: This is not structured tabular data; it's free-form financial/prose text from annual reports and internal documents. The rows contain narrative descriptions, financial values, and corporate metadata rather than delimited records. There are no consistent columns or PII fields in this dataset.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT___berstd_2018.csv
0 rows

File structure

Notes: This is an unstructured corporate financial file from Zynex AG (Swiss web hosting company). The file contains salary and overtime records in German, with no consistent columnar structure or identifiable PII fields. Values represent numerical data, percentages, and employee names that do not map to any defined PII categories (names appear to be generic employee identifiers, not personal identifiers). No emails, phone numbers, addresses, or other PII are present in the sample. The content is purely financial and operational data with no customer PII exposure.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_cw_ALT___berstd_2020.csv
0 rows

File structure

Notes: This is not a structured dataset but rather free-form financial records from Zynex AG. The file contains unstructured text with financial metrics, employee names, and calculations, but lacks consistent column delimiters or headers. While employee names ('Brunner Mark', 'Leisi Martin') appear, they are embedded in free-form text rather than in a tabular structure. According to the unstructured opt-out rules, this qualifies as free-form text with embedded PII that should be processed by a streaming email/phone extractor rather than column mapping.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Angef_Arb.csv
0 rows

File structure

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

Notes: This file contains no PII columns. All columns appear to be financial/accounting data with German/Swiss financial terminology and dates, but no personal identifiers like names, emails, addresses, etc. The values are financial figures, status codes, and date strings without any personal information.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Anhang.csv
0 rows

File structure

Notes: The provided data appears to be unstructured text rather than a delimited tabular format. The sample rows show free-form German text describing financial statements and corporate documents, with no consistent columnar structure or identifiable PII fields in a machine-readable format. There are no repeated patterns, delimiters, or header rows that would allow mapping of PII fields. Therefore, this is classified as unstructured text requiring special handling.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Anlagesp.csv
0 rows

File structure

Notes: This is a financial statement document (balance sheet) from Zynex AG in Volketswil. The file contains no personal identifiable information (PII) — only corporate financial data with account names, dates, and monetary values. No columns map to PII fields because the content is purely financial/organizational and lacks any customer or employee personal data. The structure is tabular but contains no personal names, addresses, emails, etc.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Aufteilung_Bonus.csv
0 rows

File structure

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

Notes: This is a financial statement document, not structured personal data. Columns contain account names and financial figures in CHF, with no personal identifiers. No PII fields present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: The file appears to be a free-form financial report from Zynex AG, Volketswil, containing financial data such as profit allocations, bonuses, and tax calculations in Swiss Francs. There is no consistent columnar structure with personal identifiable information (PII). The data contains financial metrics and percentages rather than any personal data fields such as names, emails, addresses, or other PII. Therefore, no column mapping to PII fields is possible.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__BVG-Lohn_2019.csv
8 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'M. Brunner', values are full names with initials
3fullNamehigh[3] header 'M. Leisi', values are full names with initials
4fullNamehigh[4] header 'D. Poulton', values are full names with initials
5fullNamehigh[5] header 'R. Wellinger', values are full names with initials
6fullNamehigh[6] header 'D. Rosso', values are full names with initials
7fullNamehigh[7] header 'P. Windhofer', values are full names with initials
12skiphigh[12] column 'Geburtsdatum', values are dates in MM/DD/YY format
13skiphigh[13] column 'Alter 2019', values are ages derived from birth dates

Notes: 50 rows shown, 8 columns total. Columns 0 and 1 are empty headers/labels. Columns 2-7 contain employee full names with initials. Column 12 contains birth dates in MM/DD/YY format. Column 13 contains derived ages from birth dates. All other columns contain salary/benefit figures and percentages — these are financial records and not PII. No email, phone, address, SSN, password, or username data visible in this sample.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__BVG-Lohn_2020.csv
8 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3fullNamehigh[3] Column header 'M. Brunner' is a person name (initials + surname); appears consistently across all salary rows as an employee identifier
4fullNamehigh[4] Column header 'M. Leisi' is a person name (initials + surname); consistent employee identifier across years
5fullNamehigh[5] Column header 'R. Wellinger' is a person name (initials + surname); consistent employee identifier
6fullNamehigh[6] Column header 'D. Rosso' is a person name (initials + surname); consistent employee identifier
7fullNamehigh[7] Column header 'P. Windhofer' is a person name (initials + surname); consistent employee identifier
8fullNamehigh[8] Column header 'K. Parizek' is a person name (initials + surname); employee identifier for 2021 only
9fullNamehigh[9] Column header 'D. Poulton' is a person name (initials + surname); employee identifier for 2019 only
11skiphigh[11] Row label 'Geburtsdatum' (German: 'Date of Birth'); values are dates in M/D/YY format (e.g., 6/29/77, 6/3/72)

Notes: Internal Zynex payroll/HR records spanning 2015–2021. Contains employee names (as column headers) and dates of birth. All other columns are financial data (salary components, BVG contributions, percentages, totals) and should be skipped. File is primarily in German; names are Swiss/European.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__BVG-Lohn_2022.csv
94 columns4 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values match common full names (e.g., 'M. Brunner', 'M. Leisi')
3fullNamehigh[3] values match common full names (e.g., 'M. Leisi', 'R. Wellinger')
4fullNamehigh[4] values match common full names (e.g., 'R. Wellinger', 'D. Rosso')
5fullNamehigh[5] values match common full names (e.g., 'D. Rosso', 'P. Windhofer')
6fullNamehigh[6] values match common full names (e.g., 'P. Windhofer', 'K. Wellinger')
7fullNamehigh[7] values match common full names (e.g., 'K. Wellinger', 'K. Parizek')
12skiphigh[12] values match MM/DD/YY date format (e.g., '6/29/77', '6/3/72')
13skiphigh[13] values match MM/DD/YY date format (e.g., '6/3/72', '5/24/89')
14skiphigh[14] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
15skiphigh[15] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
16skiphigh[16] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/86')
17skiphigh[17] values match MM/DD/YY date format (e.g., '11/29/86', '6/29/77')
18skiphigh[18] values match MM/DD/YY date format (e.g., '6/29/77', '6/3/72')
19skiphigh[19] values match MM/DD/YY date format (e.g., '6/3/72', '5/24/89')
20skiphigh[20] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
21skiphigh[21] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
22skiphigh[22] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/86')
23skiphigh[23] values match MM/DD/YY date format (e.g., '11/29/86', '6/29/77')
24skiphigh[24] values match MM/DD/YY date format (e.g., '6/29/77', '6/3/72')
25skiphigh[25] values match MM/DD/YY date format (e.g., '6/3/72', '5/24/89')
26skiphigh[26] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
27skiphigh[27] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
28skiphigh[28] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
29skiphigh[29] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
30skiphigh[30] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
31skiphigh[31] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
32skiphigh[32] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
33skiphigh[33] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
34skiphigh[34] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
35skiphigh[35] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
36skiphigh[36] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
37skiphigh[37] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
38skiphigh[38] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
39skiphigh[39] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
40skiphigh[40] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
41skiphigh[41] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
42skiphigh[42] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
43skiphigh[43] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
44skiphigh[44] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
45skiphigh[45] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
46skiphigh[46] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
47skiphigh[47] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
48skiphigh[48] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
49skiphigh[49] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
50skiphigh[50] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
51skiphigh[51] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
52skiphigh[52] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
53skiphigh[53] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
54skiphigh[54] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
55skiphigh[55] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
56skiphigh[56] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
57skiphigh[57] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
58skiphigh[58] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
59skiphigh[59] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
60skiphigh[60] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
61skiphigh[61] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
62skiphigh[62] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
63skiphigh[63] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
64skiphigh[64] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
65skiphigh[65] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
66skiphigh[66] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
67skiphigh[67] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
68skiphigh[68] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
69skiphigh[69] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
70skiphigh[70] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
71skiphigh[71] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
72skiphigh[72] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
73skiphigh[73] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
74skiphigh[74] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
75skiphigh[75] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
76skiphigh[76] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
77skiphigh[77] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
78skiphigh[78] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
79skiphigh[79] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
80skiphigh[80] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
81skiphigh[81] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
82skiphigh[82] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
83skiphigh[83] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
84skiphigh[84] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
85skiphigh[85] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
86skiphigh[86] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
87skiphigh[87] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
88skiphigh[88] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
89skiphigh[89] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
90skiphigh[90] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
91skiphigh[91] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
92skiphigh[92] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
93skiphigh[93] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
94skiphigh[94] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
95skiphigh[95] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')
96skiphigh[96] values match MM/DD/YY date format (e.g., '7/31/73', '11/29/74')
97skiphigh[97] values match MM/DD/YY date format (e.g., '11/29/74', '5/24/89')
98skiphigh[98] values match MM/DD/YY date format (e.g., '5/24/89', '9/21/87')
99skiphigh[99] values match MM/DD/YY date format (e.g., '9/21/87', '7/31/73')

Notes: CSV with 100 columns total, 99 contain DOB fields in MM/DD/YY format across multiple years (2015-2022). Other columns contain salary data, age calculations, and company totals.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Bilanz.csv
0 rows

File structure

Notes: The file is a financial statement (balance sheet) in German, formatted as a free-form tabular text with no consistent delimiter or column headers. It contains financial data (assets, liabilities, equity) and numerical values but no personal identifiable information (PII). The structure is prose-like with no importable data columns.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Daten.csv
0 rows

File structure

Notes: free-form text with embedded dates, no consistent delimiter or row structure. File appears to be financial statements/prose with no PII columns.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Detail_ang_Arb.csv
0 rows

File structure

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

Notes: This is a corporate financial record file, not customer PII data. All visible columns contain company names, financial years, and financial figures. No personal PII fields (email, phone, name, etc.) are present. The columns appear to represent internal accounting line items for Swiss SMEs billed for Zynex web hosting subscriptions.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: The file is a free-form financial statement document (Bilanz- und Erfolgsrechnungspositionen), not structured tabular data with PII columns. It contains financial line items and totals, not personal identifiers. No consistent column structure or PII fields present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__EDV-Bi.csv
0 rows

File structure

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

Notes: This is a financial statement file with accounting codes and monetary values. No personal identifiable information (PII) fields are present. Columns contain accounting categories (e.g., 'Zynex AG, Volketswil'), years (2012-2021), and financial figures in CHF. All columns map to skip per exclusion rules (company financial data, no PII).

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__EDV-ER.csv
0 rows

File structure

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

Notes: No PII columns identified. This appears to be purely financial data with company names, years, and monetary values. All columns relate to corporate financial statements (revenue, losses) and contain no personal identifiers.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Erfolgsrg.csv
0 rows

File structure

Notes: This is a financial statement document (Erfolgsrechnung) containing corporate financial data for Zynex AG. The file contains no personal identifiable information (PII) fields - it only shows aggregated financial figures like revenue, expenses, and profit/loss for different years (2019-2021). All columns appear to be financial aggregates rather than customer or employee data. The structure is free-form financial reporting with no consistent columnar PII data.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Geldflussrg.csv
0 rows

File structure

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

Notes: This file contains purely financial statements (cash flow statements) with no personal or customer data. Columns represent financial line items and year-over-year figures in CHF, with no PII fields present. All columns are financial metrics or empty placeholders.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Gewinnverw_.csv
0 rows

File structure

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

Notes: This is a financial statement document in German with no personal identifiers. Columns contain only corporate financial data such as years, monetary figures, and legal reserves. No PII fields detected.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Hardware_RZ.csv
0 rows

File structure

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

Notes: This is purely financial ledger data with columns representing balance sheet line items (assets, depreciation, book value, etc.). No PII fields present. All columns are financial metrics and internal accounting codes.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Pendenzen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Personalvers_2017.csv
0 rows

File structure

Notes: This is a free-form financial report document with no consistent columnar structure. The rows appear to be aggregated financial figures and labels rather than structured personal data. No PII fields are present in this format.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__Plan_prod_Std.csv
0 rows

File structure

Notes: The provided data is a financial/projection table with no column headers or consistent structure. It contains only numeric values, textual descriptions of financial metrics (e.g., 'Soll-Std', 'Lohn brutto'), and monetary amounts in Swiss Francs (CHF). There are no identifiable PII fields (names, emails, addresses, etc.) present. The format appears to be a manually constructed financial report rather than a structured dataset with personal data. Given the absence of any row structure or identifiable PII, this is classified as unstructured content.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2__St_Wert.csv
0 rows

File structure

Notes: This is a corporate financial statement from Zynex AG (Swiss hosting company) showing balance sheet items like 'Substanzwert' (net asset value) and 'Ausgewiesenes Eigenkapital' (reported equity). The data contains no personal customer PII fields — only aggregated corporate financial figures, dates (year-end), and monetary values in CHF. No emails, names, addresses, or other individual identifiers appear in the sample. The unstructured format indicates this is a narrative financial report, not a delimited dataset with personal records.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2___berstd_2018.csv
0 rows

File structure

Notes: This is not a delimited structured file. The sample shows free-form text lines with inconsistent columns and values. The content appears to be internal corporate financial records from Zynex AG, Volketswil, with no consistent column structure or PII fields. There are no recognizable PII columns in the sample, and the data appears to be internal financial calculations rather than personal customer data.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2___berstd_2020.csv
0 rows

File structure

Notes: This is an unstructured financial record file from Zynex AG, Volketswil. The data appears to be internal corporate financial statements and payroll records in German, containing no consistent columnar structure with personal identifiers. The rows contain mixed financial metrics and employee names in free-form text format, but there is no delimited structure to map to PII fields. This qualifies as unstructured data per the rules.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter_2___berstd_2021.csv
0 rows

File structure

Notes: This is not a structured dataset but a free-form text document containing corporate financial records. The data appears to be internal accounting records from Zynex AG with columns showing overtime, vacation balances, salaries, and other financial metrics. There are no consistent columns or delimiters across rows, and while names like "Brunner Mark" and "Leisi Martin" appear, they are embedded within unstructured text rather than in a tabular format. The content is in German and appears to be accounting statements rather than customer PII records.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Angef_Arb.csv
0 rows

File structure

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

Notes: This file appears to be unstructured financial/accounting data with no PII fields. All columns contain financial metrics, dates, and accounting codes in German. No columns map to email, phone, name, address, DOB, SSN, or other PII categories. The data represents financial records from Zynex AG with entries like 'Angefangene Arbeiten' (work started), balances, and year-end dates.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Anhang.csv
0 rows

File structure

Notes: The provided rows are unstructured text/prose (German financial report snippets) with no consistent delimiter or columnar structure. This is typical of annual financial statement documents, not a CSV/TSV dataset. While the file is corporate financial data, the sample shows narrative paragraphs and headers rather than tabular data with identifiable PII columns. Per rules, unstructured files with no shared delimiter and variable line shapes must be returned as {} columns.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Anlagesp.csv
0 rows

File structure

Notes: This is an unstructured financial report document from Zynex AG. The data contains accounting entries like asset values, depreciation amounts, and balance sheet figures. There are no identifiable personal information fields (PII) such as names, emails, phone numbers, or addresses. The structure is free-form tabular data without consistent column headers or identifiable personal data patterns.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Aufteilung_Bonus.csv
0 rows

File structure

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

Notes: This file is purely financial/accounting data from Zynex AG. Columns contain financial line items (e.g., 'Aufteilung Bonus', 'Unterhalt Fahrzeuge') and numeric values in CHF. No PII fields are present — all columns are financial aggregates, totals, and internal accounting codes. The data appears to be a standard corporate financial statement with no personal customer or employee details.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: This is unstructured financial data from Zynex AG, a Swiss corporate entity. The file contains no personal PII fields — only corporate financial metrics (profit/loss, bonuses, taxes) in Swiss Francs. Columns are empty headers or labels like 'Zynex AG, Volketswil', percentages, and year references. No emails, names, addresses, or other PII appear in the sample. The data is purely corporate financial statements, not customer/user records.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__BVG-Lohn_2019.csv
8 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values are full names (e.g., 'M. Brunner')
3fullNamehigh[3] values are full names (e.g., 'M. Leisi')
4fullNamehigh[4] values are full names (e.g., 'D. Poulton')
5fullNamehigh[5] values are full names (e.g., 'R. Wellinger')
6fullNamehigh[6] values are full names (e.g., 'D. Rosso')
7fullNamehigh[7] values are full names (e.g., 'P. Windhofer')
12skiphigh[12] values are dates in MM/DD/YY format representing birthdates
13skiphigh[13] derived from age calculations from birthdates in column 12

Notes: 50 rows of payroll data with employee names and birthdates. Columns 0 and 1 appear to be headers or empty. Columns 8-11 and 14+ appear to be financial calculations and do not contain PII.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__BVG-Lohn_2020.csv
12 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values match full names: 'M. Brunner', 'M. Leisi', etc.
3fullNamehigh[3] values match full names: 'M. Leisi', 'R. Wellinger', etc.
4fullNamehigh[4] values match full names: 'R. Wellinger', 'D. Rosso', etc.
5fullNamehigh[5] values match full names: 'D. Rosso', 'P. Windhofer', etc.
6fullNamehigh[6] values match full names: 'P. Windhofer', 'K. Parizek', etc.
7fullNamehigh[7] values match full names: 'K. Parizek'
10skiphigh[10] values match MM/DD/YY date format: '6/29/77', '6/3/72', etc.
11skiphigh[11] values match MM/DD/YY date format: '6/3/72', '5/24/89', etc.
12skiphigh[12] values match MM/DD/YY date format: '5/24/89', '9/21/87', etc.
13skiphigh[13] values match MM/DD/YY date format: '9/21/87', '7/31/73', etc.
14skiphigh[14] values match MM/DD/YY date format: '7/31/73', '11/29/86', etc.
15skiphigh[15] values match MM/DD/YY date format: '11/29/86'

Notes: 50 rows of financial records showing employee compensation and birthdays. Columns 2-7 contain employee names, columns 10-15 contain DOB in MM/DD/YY format. No emails, phones, or SSNs present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__BVG-Lohn_2022.csv
2 columns4 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3fullNamehigh[3] Values are Swiss employee names (M. Brunner, M. Leisi, R. Wellinger, D. Rosso, P. Windhofer, K. Wellinger, K. Parizek, D. Poulton) appearing consistently as column headers across all salary year blocks
14skiphigh[14] German header 'Geburtsdatum' (birth date); values are dates in M/D/YY format (6/29/77, 6/3/72, 5/24/89, 9/21/87, 7/31/73, 11/29/86, 11/29/74)

Notes: This is an internal Zynex payroll/personnel spreadsheet spanning 2015–2022 containing employee salary, benefits, and birth date data. Only two columns contain PII: employee names (column 3, appearing as multi-year column headers) and birth dates (column 14, row label 'Geburtsdatum'). All other columns contain financial compensation figures, percentages, and non-PII payroll metrics (base salary, overtime, bonuses, pension contributions, percentages). The structure repeats for each year (2022, 2021, 2020, 2019, 2018, 2017, 2016, 2015).

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Bilanz.csv
0 rows

File structure

Notes: This is a financial statement document (Bilanz) in German, formatted as free-form tabular text with no consistent column headers or delimiters across rows. It contains financial data (accounts, balances) rather than personal identifiable information. There are no structured columns mapping to PII fields.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Daten.csv
0 rows

File structure

Notes: This is a free-form financial report document (not structured tabular data). The lines contain financial report titles and dates but no consistent column structure or PII. No column mapping can be performed.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Detail_ang_Arb.csv
0 rows

File structure

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

Notes: This is NOT structured PII data. The file appears to be internal corporate financial records from Zynex AG (a Swiss web hosting/CMS company). All columns contain Swiss SME customer names (column 0) and financial figures/years, but no personal identifiers like email, phone, DOB, or address. Column 0 contains business/customer names ("Angefangene Arbeiten", "Chalverat Partner", etc.) — these are NOT personal names and must be skipped per exclusion rules (Company/Business names). All other columns are empty or contain financial year-end dates/amounts. No PII fields present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: This is a financial statement document (Bilanz- und Erfolgsrechnungspositionen) from Zynex AG, not a structured dataset with personal identifiable information columns. The file contains accounting positions and financial figures rather than customer PII. No consistent column structure or PII fields are present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__EDV-Bi.csv
0 rows

File structure

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

Notes: This is a financial statement file with no PII columns. Columns contain account codes, account names, and financial figures for multiple years. No personal identifiable information is present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__EDV-ER.csv
0 rows

File structure

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

Notes: This is a financial statement file with no PII columns. All columns contain accounting codes, monetary amounts, and year references. No personal identifiers (names, emails, addresses, etc.) are present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Erfolgsrg.csv
0 rows

File structure

Notes: This is a financial statement document (Erfolgsrechnung) for Zynex AG, not a structured dataset with personal identifiable information. The content contains financial figures in Swiss Francs, dates, and company name, but no PII fields such as names, addresses, emails, or phone numbers. The structure is tabular but represents financial data, not customer/user records.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Geldflussrg.csv
0 rows

File structure

Notes: This is a corporate financial document from Zynex AG showing cash flow statements for years 2018-2020. The columns represent financial line items and year-over-year comparisons, not customer or employee PII. No mapping to PII fields is possible as there are no personal identifiers present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Gewinnverw_.csv
0 rows

File structure

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

Notes: This is unstructured financial reporting data (profit/loss statements, balance sheets) with no personal identifiers. All columns contain accounting figures, year labels, and corporate financial terminology in German. No PII fields present.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Hardware_RZ.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains accounting data (balance sheet values, depreciation, asset values) but no personal PII fields. The format is unstructured financial statements rather than a delimited dataset with personal records.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Pendenzen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Personalvers_2017.csv
0 rows

File structure

Notes: This is a free-form financial report document from Zynex AG (Swiss company) containing structured financial aggregates and percentages rather than personal PII records. The sample lines show financial categories like insurance premiums, AHV contributions, and account balances with no identifiable personal data fields (names, emails, addresses, etc.). No consistent column structure exists across the rows — this is a narrative-style financial statement, not a delimited PII dataset.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__Plan_prod_Std.csv
0 rows

File structure

Notes: The file is free-form financial data with no consistent columnar structure. It contains corporate financial records, staffing plans, and budget figures in German, but lacks any identifiable personal data columns. The content appears to be internal corporate financial statements and staffing metrics for Zynex AG, not customer PII.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter__St_Wert.csv
0 rows

File structure

Notes: This is a free-form financial report document (not a structured dataset). The lines contain corporate financial statements for Zynex AG with no consistent delimiter, varying line lengths, and no column headers. Contains corporate addresses and financial data but no personal PII fields. Classified as unstructured for processing.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter___berstd_2018.csv
0 rows

File structure

Notes: The file is unstructured financial/administrative data from Zynex AG. It contains no consistent columnar structure or identifiable PII fields; all values appear to be financial metrics, employee status codes, and internal accounting references. No email addresses, phone numbers, or personal identifiers are present in the sample rows.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter___berstd_2020.csv
0 rows

File structure

Notes: This is not a structured dataset but rather free-form financial records from Zynex AG. The sample shows lines with varying content and no consistent delimiter. The data appears to be internal corporate financial records (overtime, salaries, etc.) and does not contain any identifiable PII columns. The format is unstructured prose with no column mapping possible.

finanzen__Abschluesse__Abschluss_2021__JRG_2021_Zynex_von_Peter___berstd_2021.csv
0 rows

File structure

Notes: The provided data appears to be free-form text with no consistent delimiter or row structure. It contains unstructured financial and employment records from Zynex AG, including descriptions of overtime, salaries, and year-end balances. There are no identifiable PII fields in a structured format; any potential names (e.g., 'Brunner Mark', 'Leisi Martin') appear embedded in prose rather than as discrete columns. This qualifies as unstructured text with no column mapping possible.

finanzen__Abschluesse__Abschluss_2021___berstd.-_und_Feriensaldo_31.12.2021___berstd_2021.csv
0 rows

File structure

Notes: This is an unstructured financial report file (Zynex AG) showing internal corporate data — not customer PII. Columns contain Swiss Franc amounts, working hours, salary calculations, and internal accounting codes. No personal identifiers (names, emails, addresses) are present beyond what appears to be employee names in a free-form table, but the structure lacks consistent delimiters and varies per line. This matches the definition of unstructured text with no importable data columns.

finanzen__Abschluesse__Abschluss_2021__tickets-angef-arbeiten-2021__Tabelle1.csv
0 rows

File structure

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

Notes: The file is a tab-delimited structured record but lacks headers. All visible columns contain project codes, task descriptions, dates, and numeric values representing hours or costs. No PII fields (email, phone, name, address, etc.) are present in the first 50 rows. Columns map exclusively to internal project tracking fields (VXRITTER codes, task categories, timestamps, effort hours). Per exclusion rules, all columns are skipped as they represent internal operational data, not personal information.

finanzen__Abschluesse__Abschluss_2021__tickets-angef-arbeiten-2021__Tabelle2.csv
0 rows

File structure

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

Notes: The file appears to be structured but contains only internal financial/project tracking records with no PII fields. Columns contain internal codes (VXSTAUBA-5), project types (KP/DR/ML), dates, amounts, and descriptions of services rendered — all internal business data without any personal identifiers. No emails, names, addresses, or other PII are present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2021__tickets-angef-arbeiten-2021__abschluss-2021.csv
0 rows

File structure

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

Notes: The provided data appears to be financial records from Zynex, a Swiss web hosting and CMS software company. The data includes customer/project information, amounts invoiced, and notes about payments. There are no identifiable PII fields such as names, email addresses, phone numbers, dates of birth, or other personal identifiers in the visible rows. The columns appear to contain only business-related data (customer names which could be business names, project codes, amounts, dates of payments, and notes). Based on the exclusion rules, any column containing 'Company', 'Business', or internal identifiers should be skipped. Therefore, no PII columns are mapped.

finanzen__Abschluesse__Abschluss_2021__tickets-angef-arbeiten-2021__angef-arbeiten.csv
0 rows

File structure

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

Notes: This is purely transactional accounting data with company names (not personal PII). No email, phone, SSN, DOB, etc. All fields are business-related financial records (customer names, invoice amounts, dates). No PII columns detected.

finanzen__Abschluesse__Abschluss_2021__tickets-angef-arbeiten-2021__jira-tickets.csv
0 rows

File structure

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

Notes: This file contains only internal corporate financial tracking columns: project identifiers, teams, price lists, activities, charge hours/amounts, no-charge hours/amounts, and fiscal year. No personal identifiers (PII) appear in any column. All columns represent internal business metrics, not customer or employee data.

finanzen__Abschluesse__Abschluss_2022__ClickupTimeQueries.sql
0 rows

File structure

Notes: This is SQL query text (T-SQL) with no tabular data rows. The content consists of SELECT statements and date calculations from ClickupTimeEntry and ClickupUser tables, but contains no actual record data with PII fields. No column mapping possible as there are no structured rows to analyze.

finanzen__Abschluesse__Abschluss_2022__clickuptimetickets__Tabelle1.csv
0 rows

File structure

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

Notes: This is NOT a PII file. The data consists entirely of internal transaction codes (CustomTaskIdPrefix) and numeric values representing amounts. There are no identifiable fields, names, addresses, or other personal data. All entries appear to be internal financial references from Zynex's ERP system with no customer or employee PII exposed.

finanzen__Abschluesse__Abschluss_2022__clickuptimetickets_neu__alle.csv
1 rows

File structure

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

finanzen__Abschluesse__Abschluss_2022__clickuptimetickets_neu__keine-rg-akonto.csv
0 rows

File structure

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

Notes: No PII fields detected. All columns appear to be internal task IDs, timestamps, descriptions, and numerical values (hours, flags). No names, emails, addresses, phone numbers, or other personal identifiers present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2022__clickuptimetickets_neu__leistung2022-rg2023.csv
1 rows

File structure

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

finanzen__Abschluesse__Abschluss_2022__debitorenverluste-2022__Tabelle1.csv
0 rows

File structure

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

Notes: This is a financial ledger file with structured columns (Rg Nr, Name, Datum, CHF, Bemerkungen). None of these columns map to PII fields as defined. 'Name' contains business entity names (Swiss companies/organizations), not personal names. 'Datum' is transaction dates, not birth dates. The data reflects corporate billing records for web hosting services, consistent with the breach context of Zynex corporate financial data.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Angef_Arb.csv
0 rows

File structure

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

Notes: This is a financial statement file with no PII columns. All columns contain corporate financial data (project codes, dates, monetary values) and internal accounting codes. No personal identifiers (names, emails, addresses, etc.) are present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Anhang.csv
0 rows

File structure

Notes: This is an unstructured document containing free-form text (descriptive prose, financial statements, and corporate notes). No consistent delimiter or column structure exists across rows. The data appears to be internal corporate notes and financial descriptions, not tabular PII records. No actionable PII columns to map.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Anlagesp.csv
0 rows

File structure

Notes: The provided data appears to be financial statements from Zynex AG, Volketswil. The content consists of accounting terms, financial figures, and dates in German. There are no personal identifiable information (PII) fields such as names, emails, addresses, or other sensitive data. The data is purely financial and does not contain any structured personal records.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Aufteilung_Bonus.csv
0 rows

File structure

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

Notes: This is a financial statement file with no PII. Columns represent account categories and financial figures in Swiss Francs (CHF) with no personal identifiers present. All values are financial totals and codes, not personal data.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: The provided sample appears to be unstructured financial/profit/loss data from Zynex AG, Volketswil. There are no consistent columns, and the content consists of financial descriptors and percentages rather than personal PII fields. No identifiable personal data (names, emails, addresses, etc.) is visible in the sample rows. This is corporate financial reporting data, not customer PII.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__BVG-Lohn_2019.csv
8 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'M. Brunner', values are full names with title initials
3fullNamehigh[3] header 'M. Leisi', values are full names with title initials
4fullNamehigh[4] header 'D. Poulton', values are full names with title initials
5fullNamehigh[5] header 'R. Wellinger', values are full names with title initials
6fullNamehigh[6] header 'D. Rosso', values are full names with title initials
7fullNamehigh[7] header 'P. Windhofer', values are full names with title initials
12skiphigh[12] column 'Geburtsdatum', values are dates in MM/DD/YY format
13skiphigh[13] column 'Alter 2019', age values correspond to birth dates in column 12

Notes: 50 rows shown, 8 columns total. Columns 0 and 1 are empty headers/labels. Columns 2-7 contain full names. Column 12 contains birth dates. Column 13 contains derived age values matching birth dates.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__BVG-Lohn_2020.csv
12 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values match common full names (M. Brunner, M. Leisi, etc.)
3fullNamehigh[3] values match common full names (M. Brunner, M. Leisi, etc.)
4fullNamehigh[4] values match common full names (M. Leisi, R. Wellinger, etc.)
5fullNamehigh[5] values match common full names (R. Wellinger, D. Rosso, etc.)
6fullNamehigh[6] values match common full names (D. Rosso, P. Windhofer, etc.)
7fullNamehigh[7] values match common full names (P. Windhofer, K. Parizek, etc.)
12skiphigh[12] values match MM/DD/YY date format (6/29/77, 6/3/72, etc.)
13skiphigh[13] values match MM/DD/YY date format (6/29/77, 6/3/72, etc.)
14skiphigh[14] values match MM/DD/YY date format (6/3/72, 5/24/89, etc.)
15skiphigh[15] values match MM/DD/YY date format (5/24/89, 9/21/87, etc.)
16skiphigh[16] values match MM/DD/YY date format (9/21/87, 7/31/73, etc.)
17skiphigh[17] values match MM/DD/YY date format (7/31/73, 11/29/86, etc.)

Notes: Structured CSV with employee names and DOBs. Columns 0 and 1 appear to be empty headers/labels. Columns 2-7 contain full names. Columns 12-17 contain dates of birth in MM/DD/YY format. No emails, phones, addresses, SSNs, passwords, or usernames detected in the first 50 rows.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__BVG-Lohn_2022.csv
8 columns4 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values match common full names: 'M. Brunner', 'M. Leisi', etc. Headerless but context indicates names
3fullNamehigh[3] values match common full names: 'M. Leisi', 'R. Wellinger', etc.
4fullNamehigh[4] values match common full names: 'R. Wellinger', 'D. Rosso', etc.
5fullNamehigh[5] values match common full names: 'D. Rosso', 'P. Windhofer', etc.
6fullNamehigh[6] values match common full names: 'P. Windhofer', 'K. Wellinger', etc.
7fullNamehigh[7] values match common full names: 'K. Wellinger', 'K. Parizek', etc.
11skiphigh[11] values match MM/DD/YY date format: '6/29/77', '6/3/72', etc.
12skiphigh[12] derived from age calculation: '45', '50', etc. based on 2022 context

Notes: 50 rows shown, 8 columns visible. Columns 0 and 1 appear to be empty/labels. Columns 2-7 contain full names. Column 11 contains dates in MM/DD/YY format (birthdates). Column 12 contains calculated ages based on column 11 values.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Bilanz.csv
0 rows

File structure

Notes: This is not structured tabular data. The file appears to be a financial statement or balance sheet in German with unstructured formatting. Columns are not consistently defined across rows, and the data represents financial figures rather than personal identifiable information. There are no identifiable PII fields such as names, addresses, or contact information in this sample. This is corporate financial data from Zynex AG, not customer PII.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Daten.csv
0 rows

File structure

Notes: The provided text appears to be unstructured financial statements from Zynex AG, with no consistent columnar structure. It contains German-language financial data (e.g., 'Abschluss' = financial statement) with dates and years, but lacks any identifiable PII fields such as names, addresses, or contact details. There are no repeated delimiters, and each line represents a different type of financial summary rather than a record with personal data. Therefore, this is classified as unstructured text with no importable PII columns.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Detail_ang_Arb.csv
0 rows

File structure

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

Notes: This file appears to be financial statements or accounting records from Zynex AG. All columns contain internal financial data, dates, and descriptions of work performed or financial figures. There are no personal identifiers (PII) such as names, email addresses, phone numbers, or addresses present in the first 50 rows. The content is purely corporate financial data with no customer or employee PII. Therefore, no columns map to PII fields.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: This is not a delimited file with personal data. The data appears to be a financial statement (Bilanz- und Erfolgsrechnungspositionen) for Zynex AG, showing account titles and balances for different years. There are no personal identifiers (PII) such as names, addresses, emails, or phone numbers in this sample. The structure is free-form financial reporting, not structured PII data. Therefore, no columns map to PII fields.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__EDV-Bi.csv
0 rows

File structure

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

Notes: This is a financial statement file from Zynex AG, Volketswil, containing only corporate accounting data (account codes, account names, and financial figures). No personal identifiers (PII) are present. All columns map to internal financial records or are empty. No emails, phone numbers, names, addresses, or other PII fields are visible.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__EDV-ER.csv
0 rows

File structure

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

Notes: This is purely financial data with account codes, company name, and annual figures. No PII fields detected. Columns represent accounting entries for Zynex AG with years 2012-2022, all values are monetary amounts or internal codes.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Erfolgsrg.csv
0 rows

File structure

Notes: This is a financial statement document (Erfolgsrechnung) in German showing annual revenue and expense data for Zynex AG. The data is purely financial and contains no personal identifiable information (PII). All columns appear to be financial metrics and year ranges, with no names, addresses, emails, or other PII fields. The structure is free-form tabular financial reporting, not a dataset with personal records.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Geldflussrg.csv
0 rows

File structure

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

Notes: This is a financial statement (Geldflussrechnung - cash flow statement) for Zynex AG. The file contains only financial data and accounting figures with no personal identifiable information (PII). Columns are financial categories and years, not containing any names, addresses, emails, phone numbers, or other PII fields. All columns are skipped as they do not map to any PII field types.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Gewinnverw_.csv
0 rows

File structure

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

Notes: This is a financial statement document in German with no personal identifiable information (PII). Columns contain only financial data such as years, monetary values, and legal reserves. No columns map to PII fields.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Hardware_RZ.csv
0 rows

File structure

Notes: The provided data is unstructured financial reporting with no consistent columnar format or PII fields. It contains balance sheet values, depreciation schedules, and asset tracking in German for Zynex's internal financial records (2017-2022). No personal identifiers appear in the sample.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Pendenzen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Personalvers_2017.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The lines appear to be financial statements and accounting entries rather than structured personal data records. There are no identifiable PII fields in the sample data, and the content consists of financial terms, percentages, and monetary values typical of corporate accounting documents. No structured PII mapping is possible.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__Plan_prod_Std.csv
0 rows

File structure

Notes: The file is a free-form financial report with no consistent columnar structure. It contains financial planning data, salary calculations, and revenue figures in Swiss Francs, formatted as a table with merged cells and mixed delimiters. No PII fields are present.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex__St_Wert.csv
0 rows

File structure

Notes: The provided data appears to be unstructured financial/prose text from Zynex AG corporate reports. No consistent column structure exists; all rows are free-form text describing financial metrics, stock values, and tax years. No PII fields are present.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex___berst_2022.csv
0 rows

File structure

Notes: This is not a structured dataset but a free-form text file containing corporate financial records from Zynex AG. The data appears to be internal financial statements with employee names and compensation details, but lacks consistent delimiters and headers across rows. The format is unstructured with embedded names but no consistent column mapping possible.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex___berstd_2018.csv
0 rows

File structure

Notes: This is a free-form financial/HR document from Zynex AG with no consistent column structure. It contains employee names in German (Brunner Mark, Leisi Martin) but lacks any identifiable PII fields like email, phone, or address. The data is structured as financial records (overtime, salaries, etc.) rather than personal contact information. Per the rules, unstructured files with no consistent delimiter structure return empty columns.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex___berstd_2020.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or column structure. The data appears to be internal financial records from Zynex AG, containing unstructured entries like employee names mixed with salary calculations and year-end balances. There are no identifiable PII columns in a structured format; employee names appear in free-text lines alongside financial metrics. This requires unstructured processing for any embedded PII extraction.

finanzen__Abschluesse__Abschluss_2022__doku-cw1__JRG_2022_Zynex___berstd_2021.csv
0 rows

File structure

Notes: This is not a structured dataset. The provided rows appear to be free-form text containing internal corporate financial records from Zynex AG, a Swiss web hosting and CMS software company. The data includes employee compensation details, overtime, vacation balances, and other internal financial metrics. There are no consistent columns or delimiters, and the data is presented in a narrative format rather than a tabular structure. No PII fields are identifiable in this structured format because the data lacks column-based organization.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Angef_Arb.csv
0 rows

File structure

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

Notes: This is an unstructured financial statement file with no personal identifiable information (PII). The columns appear to represent accounting entries and financial metrics rather than customer or employee data. All columns contain financial data such as account descriptions, dates, and monetary values, but no names, addresses, emails, phone numbers, or other PII fields.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Anhang.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Anlagesp.csv
0 rows

File structure

Notes: This is not structured tabular data; it appears to be free-form financial statements and accounting records from Zynex AG. The lines contain German financial terminology and numerical values but lack consistent column structure or headers. Since there are no identifiable PII fields (names, emails, addresses, etc.) and the format is unstructured prose, we return an empty columns object.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Aufteilung_Bonus.csv
0 rows

File structure

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

Notes: This file appears to be a financial statement/ledger from Zynex AG with no personal identifiable information (PII). Columns contain account names (e.g., 'Aufteilung Bonus', 'Unterhalt Fahrzeuge') and financial figures in Swiss Francs (CHF). No email addresses, phone numbers, names, or other PII fields are present. All columns are skipped per exclusion rules for financial/transactional data.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: This is an unstructured financial report document in German. The file contains corporate financial statements and percentage allocations, with no identifiable personal data columns or consistent row structure. The data appears to be financial summaries for Zynex AG with values like percentages, years, and monetary figures in Swiss Francs. There are no PII fields present in this corporate financial data.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__BVG-Lohn_2019.csv
7 columns1 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3fullNamehigh[3] header 'M. Brunner' and subsequent columns contain employee names (initials + surname)
4fullNamehigh[4] 'M. Leisi' - employee name
5fullNamehigh[5] 'D. Poulton' - employee name
6fullNamehigh[6] 'R. Wellinger' - employee name
7fullNamehigh[7] 'D. Rosso' - employee name
8fullNamehigh[8] 'P. Windhofer' - employee name
12skiphigh[12] 'Geburtsdatum' (German: date of birth), values are dates in M/D/YY format (6/29/77, 6/3/72, 11/29/74, 5/24/89, 9/21/87, 7/31/73)

Notes: This is a Swiss payroll/HR document from Zynex (2015–2019 employee compensation records). Column 0–2 contain row labels and totals (skip). Columns 3–8 are employee names. Column 12 contains birth dates. The document is in German; 'Geburtsdatum' = date of birth. All monetary values and percentages are payroll/benefits data (skip). Age and pension contribution data are derived metrics (skip).

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__BVG-Lohn_2020.csv
8 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2firstNamehigh[2] values match common male first names: M., M., R., D., P., K.
3firstNamehigh[3] values match common female first names: M., M., R., D., P.
4firstNamehigh[4] values match common male first names: R., D., P., K.
5firstNamehigh[5] values match common female first names: D., P., K.
6firstNamehigh[6] values match common male first names: P., K.
7firstNamehigh[7] values match common male first names: K.
12skiphigh[12] values match MM/DD/YY date format: 6/29/77, 6/3/72, 5/24/89, etc.
13skiphigh[13] derived from age values: 44, 49, 32, etc. (2021 - birth year = age)

Notes: 50 rows shown; PII identified in name columns and birth dates. All names follow Swiss naming conventions. DOB stored as MM/DD/YY. No emails, phones, addresses, SSNs, passwords, or usernames detected in sample.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__BVG-Lohn_2022.csv
8 columns4 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values match common full names (e.g., 'M. Brunner', 'M. Leisi'). Header-less but values clearly indicate personal names
3fullNamehigh[3] values match common full names (e.g., 'M. Leisi', 'R. Wellinger'). Header-less but values clearly indicate personal names
4fullNamehigh[4] values match common full names (e.g., 'R. Wellinger', 'D. Rosso'). Header-less but values clearly indicate personal names
5fullNamehigh[5] values match common full names (e.g., 'D. Rosso', 'P. Windhofer'). Header-less but values clearly indicate personal names
6fullNamehigh[6] values match common full names (e.g., 'P. Windhofer', 'K. Wellinger'). Header-less but values clearly indicate personal names
7fullNamehigh[7] values match common full names (e.g., 'K. Wellinger', 'K. Parizek'). Header-less but values clearly indicate personal names
12skiphigh[12] values match MM/DD/YY date format (e.g., '6/29/77', '6/3/72'). Consistent date pattern across rows
13skiphigh[13] values match age in years (e.g., '45', '50'). Derived from date of birth in column 12

Notes: 50 rows shown; PII includes employee names and birthdates. All rows follow consistent CSV structure despite missing headers. Columns 0,1,8-11,14-49 contain salary/benefit data (non-PII). File appears to be Swiss employee payroll records from Zynex (2015-2022).

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Bilanz.csv
0 rows

File structure

Notes: The provided data is not structured tabular data with consistent columns; it appears to be financial statements or accounting reports with merged cells and hierarchical text. No identifiable PII columns exist in this format. The content shows financial metrics like 'Bilanz' (balance sheet), account names, and year-end dates, but lacks personal identifiers such as names, addresses, emails, or other PII fields. Therefore, no columns can be mapped to PII fields.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Daten.csv
0 rows

File structure

Notes: This is a free-form financial report document in German with no consistent columnar structure. It contains financial period headers and totals but no personal identifiable information in a structured format. No column mapping is possible as there are no consistent delimiters or repeating patterns across rows.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Detail_ang_Arb.csv
0 rows

File structure

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

Notes: This file appears to be financial statements from Zynex AG, containing only corporate financial data and dates. No personal PII fields are present in the first 50 rows. Columns contain account descriptions, fiscal year-end dates, and financial figures in CHF. All columns map to skip categories (company data, timestamps, financial totals).

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: This is a financial statement document in German with no consistent column structure. The data appears to be a balance sheet or income statement with row-wise entries rather than columnar PII data. No identifiable personal information is present in the sample rows.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__EDV-Bi.csv
0 rows

File structure

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

Notes: This is purely financial accounting data (accounts receivable, provisions, etc.) with no PII fields. Columns contain only numeric financial values and account names. No personal identifiers present.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__EDV-ER.csv
0 rows

File structure

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

Notes: This is purely financial accounting data with no PII columns. Columns contain account numbers (0), company name (1), financial years (3,5,7,9,11,13,15,17,19,21,23,25), and monetary values. No personal identifiers present.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Erfolgsrg.csv
0 rows

File structure

Notes: The provided data is free-form financial statements with no consistent columnar structure. It contains financial data for Zynex AG, with rows showing financial periods and amounts in Swiss Francs. There are no identifiable PII fields or structured columns to map. The data appears to be a financial report rather than a dataset with personal information.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Geldflussrg.csv
0 rows

File structure

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

Notes: This file appears to be a financial statement (Geldflussrechnung - Cash Flow Statement) for Zynex AG. All columns contain financial data and accounting figures, with no personal identifiable information (PII) present. Columns 0-30 are all financial metrics, years, percentages, and company names. No email addresses, phone numbers, names, addresses, DOB, SSN, passwords, usernames, or other PII fields are present. This is purely financial/accounting data from the breach.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Gewinnverw_.csv
0 rows

File structure

Notes: This is unstructured financial reporting data with no consistent columnar structure. The rows contain Swiss Franc financial statements and balance sheet items from Zynex AG, Volketswil, with no personal identifiers present. Values are purely financial figures and accounting terminology.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Hardware_RZ.csv
0 rows

File structure

Notes: The file is purely financial ledger data with no personal identifiable information. Contains only accounting columns (balance sheet values, depreciation, etc.). No names, addresses, emails, or other PII fields are present.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Pendenzen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Personalvers_2017.csv
0 rows

File structure

Notes: This is a financial report/document with no structured columnar data containing personal identifiers. The content appears to be Swiss corporate financial records (insurance premiums, salaries, tax contributions) for Zynex AG. No PII fields are present in the structure.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__Plan_prod_Std.csv
0 rows

File structure

Notes: The file is a free-form text financial report with no consistent delimiter structure. It contains financial data and calculations but no identifiable personal information in structured columns. Given the unstructured nature and absence of any column-based PII, this should be processed as unstructured text.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex__St_Wert.csv
0 rows

File structure

Notes: This is not structured data; it's free-form financial prose from Zynex AG corporate records (balance sheets, tax statements). The content contains corporate financial statements and tax-related text, not personal PII. No consistent column structure exists across rows — values are financial figures, labels, and textual descriptions. There are no identifiable PII fields like names, emails, or addresses.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex___berst_2022.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or structured columns. It contains unstructured data entries like 'Brunner Mark', 'Leisi Martin', financial figures, and textual notes rather than columnar PII. The sample shows prose-like entries and no repeated column pattern.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex___berstd_2018.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The sample shows unstructured financial and employment data from Zynex AG with no repeating column layout or delimiter. Contains names (Brunner Mark, Leisi Martin) but lacks structured columns to map.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex___berstd_2020.csv
0 rows

File structure

Notes: This is an unstructured financial report from Zynex AG. The file contains no consistent column structure or delimiter; instead, it appears to be a formatted table with merged cells and free-form text. Sample rows show financial data (hours, salaries, balances) but no identifiable PII fields like names, emails, or addresses. Given the lack of structured columns and the presence of only financial metadata, this file should be processed as unstructured content. No PII columns to map.

finanzen__Abschluesse__Abschluss_2022__doku-cw2__JRG_2022_Zynex___berstd_2021.csv
0 rows

File structure

Notes: This is a non-tabular financial document in German, showing payroll and overtime records for Zynex AG employees. It contains no consistent columnar structure or identifiable PII fields. The data appears to be a free-form report with employee names embedded in lines of text rather than in a structured table. While names like 'Brunner Mark' and 'Leisi Martin' appear, they are mixed with financial calculations and lack a consistent columnar pattern. This qualifies as unstructured text per the rules.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Angef_Arb.csv
0 rows

File structure

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

Notes: This is a financial statement / accounting report from Zynex AG. All columns contain financial figures, dates, and internal accounting codes. No PII fields (names, emails, addresses, etc.) are present. The values are financial amounts, dates, and accounting codes — all skip columns per rules. No unstructured text with embedded emails/phones is present; the data is strictly tabular financial records.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Anhang.csv
0 rows

File structure

Notes: This is unstructured text data (prose paragraphs, not tabular CSV). Sample shows free-form German-language financial narrative lines: 'Angaben über die in der Jahresrechnung...' and 'Die vorliegende Jahresrechnung wurde...'. No consistent delimiter or column structure exists across rows. Contains no embedded emails/phones visible in first 50 rows, but unstructured format triggers streaming extraction anyway.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Anlagesp.csv
0 rows

File structure

Notes: This is a free-form financial statement document from Zynex AG, not a structured dataset with personal columns. The file contains accounting terminology in German, financial values, and balance sheet line items (e.g., 'Anlagevermögen', 'Bilanzwert', 'Abschreibung'). No PII fields are present.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Aufteilung_Bonus.csv
0 rows

File structure

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

Notes: This is a financial statement file with accounting line items and totals. No PII fields present — all columns represent financial categories, monetary values, and internal codes. No emails, names, addresses, or other personal data detected.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: This is a financial report containing unstructured data with no identifiable PII columns. The content consists of financial metrics, percentages, and years, typical of corporate financial statements.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__BVG-Lohn_2019.csv
8 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'M. Brunner', values are full names with middle initial
3fullNamehigh[3] header 'M. Leisi', values are full names with middle initial
4fullNamehigh[4] header 'D. Poulton', values are full names with middle initial
5fullNamehigh[5] header 'R. Wellinger', values are full names with middle initial
6fullNamehigh[6] header 'D. Rosso', values are full names with middle initial
7fullNamehigh[7] header 'P. Windhofer', values are full names with middle initial
12skiphigh[12] header 'Geburtsdatum', values are dates in MM/DD/YY format
13skiphigh[13] header 'Alter 2019', derived age from birth dates

Notes: 50 rows shown, 8 columns with PII. File appears to be Swiss corporate payroll data with employee names and birth dates. All names follow 'Initial. LastName' pattern. DOB values in MM/DD/YY format. No emails, phones, addresses, or SSNs visible in sample.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__BVG-Lohn_2020.csv
10 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] pattern 'M. Brunner' - capitalized first letter with middle initial suggests full name
3fullNamehigh[3] pattern 'M. Leisi' - capitalized first letter with middle initial suggests full name
4fullNamehigh[4] pattern 'R. Wellinger' - capitalized first letter with middle initial suggests full name
5fullNamehigh[5] pattern 'D. Rosso' - capitalized first letter with middle initial suggests full name
6fullNamehigh[6] pattern 'P. Windhofer' - capitalized first letter with middle initial suggests full name
7fullNamehigh[7] pattern 'K. Parizek' - capitalized first letter with middle initial suggests full name
12skiphigh[12] values match MM/DD/YY date pattern for birth dates (6/29/77, 6/3/72, etc.)
13skiphigh[13] derived age values match integer years consistent with 2021 minus birth dates
14skiphigh[14] pension percentage values correlate with age brackets
15skiphigh[15] pension amounts calculated from age brackets and salary

Notes: 50 rows of Swiss corporate payroll data with employee names and birth dates. Columns 0 and 1 are empty headers/labels. Columns 8-11 appear to be financial totals and percentages without PII. Columns 12-15 contain birth dates and derived age/pension data.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__BVG-Lohn_2022.csv
8 columns4 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values are full names (e.g., 'M. Brunner')
3fullNamehigh[3] values are full names (e.g., 'M. Leisi')
4fullNamehigh[4] values are full names (e.g., 'R. Wellinger')
5fullNamehigh[5] values are full names (e.g., 'D. Rosso')
6fullNamehigh[6] values are full names (e.g., 'P. Windhofer')
7fullNamehigh[7] values are full names (e.g., 'K. Wellinger')
12skiphigh[12] values are dates in MM/DD/YY format (e.g., '6/29/77')
13skiphigh[13] values are derived ages from [12] (e.g., '45' for '6/29/77')
finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Bilanz.csv
0 rows

File structure

Notes: This is not a delimited data file. The sample shows a free-form financial statement document with no consistent column structure across rows. Lines contain German financial terminology (e.g., 'Bilanz', 'Geldflussrechnung', 'AKTIVEN') and numerical values in parentheses, but there is no repeating columnar pattern or delimiter. This is typical of a printed or exported financial statement PDF converted to text, not a CSV or tabular dataset. No PII fields are present in this financial context.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Daten.csv
0 rows

File structure

Notes: The provided data appears to be unstructured financial statements from Zynex AG, Volketswil. The rows contain German financial report headers and dates (e.g., "Abschluss 31.12.2022") with no consistent delimiter or columnar structure. The content is purely financial reporting metadata without any personal identifiable information (PII) fields like names, addresses, emails, etc. There is no row structure to map to PII columns.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Detail_ang_Arb.csv
0 rows

File structure

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

Notes: This is a financial statement / accounting file with corporate and fiscal data. All columns appear to be internal financial metrics (project codes, dates, amounts) and do not contain any personal identifiable information (PII). There are no names, addresses, emails, phone numbers, or other PII fields. The values are all internal accounting codes, dates, and monetary amounts in CHF.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: This file is a financial report detailing balance sheet and income statement positions for Zynex AG. It contains accounting data such as account names, year-end dates, and monetary values, but no personal identifiable information (PII). Therefore, no PII columns can be mapped.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__EDV-Bi.csv
0 rows

File structure

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

Notes: This is a financial statement file showing account balances over multiple years. All columns contain account codes (column 0), account names (column 1), and financial figures (columns 3,5,7,9,11,13,15,17,19,21,23,25). No personal identifiable information (PII) is present. Columns are purely financial/accounting data with no names, addresses, emails, etc. All columns map to 'skip' per exclusion rules for financial/transactional data.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__EDV-ER.csv
0 rows

File structure

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

Notes: This is purely financial accounting data with no personal information. Columns represent financial years (2012-2022) with revenue figures in CHF, account codes, and corporate entity names. No PII fields detected.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Erfolgsrg.csv
0 rows

File structure

Notes: This is a financial statement report in German with no identifiable personal data. The file contains structured financial data (revenue, services income, work-in-progress changes, etc.) for Zynex AG across multiple years, but does not contain any personal identifiers such as names, emails, addresses, or other PII fields. All columns are financial metrics or year ranges, not individual customer or employee data.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Geldflussrg.csv
0 rows

File structure

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

Notes: This is a financial statement/Cash Flow Statement (Geldflussrechnung) for Zynex AG, a Swiss company. The data contains only financial figures (losses, depreciation, provisions) and years. No personal identifiable information (PII) is present. All columns are financial metrics or empty strings. No columns map to PII fields.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Gewinnverw_.csv
0 rows

File structure

Notes: The provided data appears to be unstructured financial statements and balance sheet data from Zynex AG. The content consists of German financial terminology, numerical values (losses, balances, percentages), and years. There are no consistent column structures, identifiable PII fields, or repeating patterns across rows. This is purely corporate financial reporting data without any personal customer or employee information. The format shows free-form text with no delimited structure or identifiable columns.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Hardware_RZ.csv
0 rows

File structure

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

Notes: This is a financial ledger file with columns representing account balances, depreciation, and book values. There are no personal identifiable information (PII) fields present. All columns are financial metrics and internal accounting data, which are excluded per the rules.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Pendenzen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Personalvers_2017.csv
0 rows

File structure

Notes: This is a free-form financial report document from Zynex AG with no structured columnar data. The content consists of financial line items and percentages rather than personal identifiable information fields. No consistent delimiter pattern exists across lines, and values appear to be financial aggregates and percentages rather than personal data fields.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__Plan_prod_Std.csv
0 rows

File structure

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

Notes: This is a financial report with no personal identifiable information (PII). The data contains financial figures, percentages, and calculations related to staffing, bonuses, and revenue for a Swiss company. There are no columns mapping to PII fields such as names, addresses, emails, phone numbers, etc. The structure appears to be a financial statement or payroll summary with no identifiable personal data.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex__St_Wert.csv
0 rows

File structure

Notes: This is not structured data; the rows appear to be free-form text lines describing financial statements and corporate records for Zynex AG. There are no consistent column patterns or delimiters across rows. The content includes phrases like 'Zynex AG, 8604 Volketswil', 'Steuerwert der Aktien', and financial figures, but these are not in a tabular format. Since there is no consistent delimiter and each line has a different structure, this qualifies as unstructured text per the rules.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex___berst_2022.csv
0 rows

File structure

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

Notes: This file appears to be a structured financial/HR document in German with columns containing employee compensation and time tracking data. No personal identifiable information (PII) fields such as names, emails, addresses, or other sensitive data are present. All columns contain internal corporate financial metrics, calculations, and codes. Therefore, no PII columns to map.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex___berstd_2018.csv
0 rows

File structure

Notes: The file is free-form text with no consistent delimiter or structured columns. It appears to be internal corporate financial records from Zynex AG in Volketswil, Switzerland. The sample shows German-language entries related to employee salaries, overtime, and vacation balances, but there are no identifiable PII fields like names, emails, or addresses in a structured format. The data is presented as narrative text rather than tabular data with columns.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex___berstd_2020.csv
0 rows

File structure

Notes: The provided data appears to be a free-form text document with no consistent columnar structure. The lines contain financial and employee-related information for Zynex AG, but there are no repeating patterns of delimiters or fixed-width columns that would indicate a structured format. The content includes employee names but lacks any consistent mapping to PII fields due to the unstructured nature of the data. This matches the criteria for unstructured opt-out where there is no consistent delimiter, lines have varying shapes, and the data is not in a tabular format.

finanzen__Abschluesse__Abschluss_2022__doku-cw3__JRG_2022_Zynex___berstd_2021.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or row structure. The sample shows unstructured financial and employee records from Zynex AG with no identifiable personal information in the first 50 rows. The content appears to be internal corporate financial statements and employee compensation data, but contains no PII fields such as names, emails, or addresses in the visible portion. All rows have different shapes and content patterns, confirming unstructured format.

finanzen__Abschluesse__Abschluss_2022__tickets-angef-arbeiten-2022__Tabelle1.csv
0 rows

File structure

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

Notes: The file contains no identifiable columns. All rows are structured task records with codes (VXRITTER-2), categories (KP, DR, RW, PW), dates, hours, and descriptions of programming/website tasks. No PII fields such as names, emails, phone numbers, or addresses are present. The data appears to be internal project logs for web development tasks, not customer or employee records.

finanzen__Abschluesse__Abschluss_2022__tickets-angef-arbeiten-2022__Tabelle2.csv
0 rows

File structure

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

Notes: No PII columns detected. This appears to be an internal financial/timesheet record file containing only invoice codes (VXSTAUBA-5, etc.), activity codes (KP, DR, ML), dates, monetary values, and project descriptions. No personal identifiers such as names, emails, addresses, or phone numbers are present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2022__tickets-angef-arbeiten-2022__Tabelle4.csv
0 rows

File structure

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

Notes: This is a corporate internal financial record file with no personal identifiable information (PII). Columns appear to be internal codes, layout settings, and numeric values related to financial or system configurations. No emails, phone numbers, names, addresses, or other PII fields are present. All columns are mapped to 'skip' per exclusion rules.

finanzen__Abschluesse__Abschluss_2022__tickets-angef-arbeiten-2022__Tabelle5.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or column structure. The data appears to be project time logs with codes (VXLANGEN-3, etc.), dates, hours, and descriptions. There are no identifiable PII fields such as names, emails, phone numbers, or addresses visible in the sample. The data represents internal project tracking rather than customer or employee records.

finanzen__Abschluesse__Abschluss_2022__tickets-angef-arbeiten-2022__Tabelle6.csv
0 rows

File structure

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

Notes: This is unstructured data with no consistent PII fields. The file appears to be financial/project tracking records with codes, dates, and amounts. No identifiable personal information (email, phone, name, address, etc.) is present in the first 50 rows. All values are project codes (VXSMITH-5), status codes (RW), dates, numeric values, and German-language meeting notes. No columns map to PII fields.

finanzen__Abschluesse__Abschluss_2022__tickets-angef-arbeiten-2022__abschluss-2021.csv
0 rows

File structure

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

Notes: The file is purely transactional financial data with no personal identifiers. Columns represent project names, performance metrics, monetary amounts, and reference numbers. No PII fields are present.

finanzen__Abschluesse__Abschluss_2022__tickets-angef-arbeiten-2022__abschluss-2022.csv
0 rows

File structure

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

Notes: This file contains only company/project financial data (customer names are business entities, not personal PII). No columns map to PII fields as defined. Customer names like 'Greiner Getränke' and 'H.J. Langendorf' are business entities, not personal first/last names. All other columns contain financial amounts, invoice numbers, dates, and status flags — none qualify as PII under the defined field types.

finanzen__Abschluesse__Abschluss_2022__tickets-angef-arbeiten-2022__angef-arbeiten.csv
0 rows

File structure

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

Notes: The file contains purely transactional financial data (customer names, invoice amounts, dates, project codes) with no identifiable personal information such as email addresses, phone numbers, dates of birth, or SSNs. All entries are corporate entities (companies) and financial records. No PII fields are present.

finanzen__Abschluesse__Abschluss_2022__tickets-angef-arbeiten-2022__jira-tickets.csv
0 rows

File structure

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

Notes: This is an internal financial record file (not customer PII). All columns represent internal project accounting metrics: project names/summaries, team allocations, pricing, chargeable vs non-chargeable hours, totals, currency year. No personal identifiers (names, emails, addresses, etc.) are present. All columns map to skip categories (internal business data, financial records, timestamps).

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Angef_Arb.csv
0 rows

File structure

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

Notes: This file contains no PII columns. All columns appear to be internal financial records with corporate or accounting terms in German, such as 'Zynex AG', 'Abschluss 31.12.2020', and various financial figures. No personal identifiers (email, phone, name, address, etc.) are present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Anhang.csv
0 rows

File structure

Notes: This is unstructured text data (free-form prose). The file contains narrative entries about financial statements and non-factured services rather than structured tabular data with identifiable PII columns. No consistent column structure exists across rows.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Anlagesp.csv
0 rows

File structure

Notes: The file appears to be free-form financial statements and accounting records from Zynex AG. There are no consistent column structures or delimiters across rows, and the content is purely corporate financial data (balance sheets, asset listings, depreciation schedules) with no personal customer data. This matches the breach context of internal corporate financial records rather than customer PII.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Aufteilung_Bonus.csv
0 rows

File structure

Notes: This file contains free-form financial statements and accounting records in German, with no consistent column structure or delimiters. It appears to be internal corporate financial data from Zynex AG, showing financial figures, bonuses, and accounting entries rather than personal identifiable information (PII). There are no identifiable PII columns present in this structured format.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: This file is unstructured financial data from Zynex AG, consisting of free-form text lines describing financial statements and profit/loss breakdowns. There are no consistent columns or delimiter patterns — each line represents a different financial metric or percentage. No PII fields (emails, names, addresses, etc.) are present; this is purely corporate financial reporting in Swiss Francs. Therefore, no column mapping is possible or necessary.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__BVG-Lohn_2019.csv
8 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'M. Brunner', values are full names with initials
3fullNamehigh[3] header 'M. Leisi', values are full names with initials
4fullNamehigh[4] header 'D. Poulton', values are full names with initials
5fullNamehigh[5] header 'R. Wellinger', values are full names with initials
6fullNamehigh[6] header 'D. Rosso', values are full names with initials
7fullNamehigh[7] header 'P. Windhofer', values are full names with initials
12skiphigh[12] column 'Geburtsdatum' contains dates like '6/29/77'
13skiphigh[13] column 'Alter 2019' contains derived age from birthdates

Notes: CSV contains employee compensation data with names and birthdates. Columns 0 and 1 are empty headers/labels. PII fields: fullName (columns 2-7), dob (columns 12-13). All other columns are financial figures, percentages, and internal codes.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__BVG-Lohn_2020.csv
8 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values match known employee full names from Zynex corporate records (e.g., 'M. Brunner', 'D. Rosso')
3fullNamehigh[3] values match known employee full names from Zynex corporate records (e.g., 'M. Leisi', 'P. Windhofer')
4fullNamehigh[4] values match known employee full names from Zynex corporate records (e.g., 'R. Wellinger', 'D. Rosso')
5fullNamehigh[5] values match known employee full names from Zynex corporate records (e.g., 'D. Rosso', 'P. Windhofer')
6fullNamehigh[6] values match known employee full names from Zynex corporate records (e.g., 'P. Windhofer', 'K. Parizek')
7fullNamehigh[7] values match known employee full names from Zynex corporate records (e.g., 'K. Parizek')
12skiphigh[12] values match MM/DD/YY date format representing employee birthdates from Zynex HR records
13agehigh[13] integer values matching calculated ages based on birthdates and 2021 reference year

Notes: 50 rows shown, but file contains 8 years of Zynex employee payroll data (2015-2021). Columns 0-1 and 8-11 appear to be metadata/labels. Columns 2-7 contain employee names, column 12 contains DOB in MM/DD/YY format, column 13 contains calculated age. All PII fields are employee names and birthdates from Zynex corporate records.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__BVG-Lohn_2022.csv
2 columns4 rows

File structure

Source columnMapped fieldConfidenceLLM assessment
3fullNamehigh[3] Column header pattern 'M. Brunner', 'M. Leisi', 'R. Wellinger', etc. — employee names appearing consistently across all salary years (2015–2022)
14skiphigh[14] Column labeled 'Geburtsdatum' (German: date of birth), values in M/D/YY format (e.g., '6/29/77', '6/3/72', '5/24/89')

Notes: Internal Zynex payroll document (2015–2022) in German. Contains employee names and birth dates. All other columns are financial/employment data (salary components, percentages, age, pension contributions) — mapped to skip. No email, phone, address, SSN, or other PII fields present in this sample.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Bilanz.csv
0 rows

File structure

Notes: This is a financial statement document in free-form text format. The file contains structured financial data but lacks consistent columnar structure across rows. It appears to be a balance sheet or cash flow statement in Swiss Francs with account categories, years, and values, but not personal PII. No identifiable personal data fields (email, phone, name, etc.) are present in the sample rows.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Daten.csv
0 rows

File structure

Notes: This is an unstructured financial report document in German. The rows contain financial year-end dates and labels (Abschluss, Vorjahr, Vor-Vorjahr) but no personal identifiable information (PII). There are no consistent columns or delimiters; it's a free-form financial summary. Since there are no emails, phone numbers, or other PII visible and the structure is inconsistent, this qualifies as unstructured text with no column mapping required.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Detail_ang_Arb.csv
0 rows

File structure

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

Notes: This is unstructured financial reporting data from Zynex AG. All columns appear to be financial line items, dates, and totals with no PII present. Columns contain values like 'Angefangene Arbeiten', 'div. Angef. Arbeiten gem. Liste', date formats (12/31/23), and financial figures. No identifiable personal information (names, emails, addresses, etc.) is present in any column. These are purely financial reporting fields and internal corporate identifiers.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: This is a financial report document (Bilanz- und Erfolgsrechnungspositionen) from Zynex AG showing balance sheet and profit/loss positions. The data is structured as financial line items with years (2020-2023) and monetary values, not personal identifiable information. No columns map to PII fields.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__EDV-Bi.csv
0 rows

File structure

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

Notes: This is purely financial ledger data with account codes, company names, and financial figures. No personal PII is present. Columns contain accounting line items (account codes), company name (Zynex AG), and financial amounts across years. All columns map to skip categories (company names, financial/transactional data, timestamps).

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__EDV-ER.csv
0 rows

File structure

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

Notes: This is purely financial ledger data (accounts, amounts, years). No personal identifiers present. All columns are internal accounting codes, account names, and financial figures. No PII fields detected.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Erfolgsrg.csv
0 rows

File structure

Notes: This is a financial statement file with no identifiable personal information. Columns appear to represent accounting line items and year ranges, but contain only financial figures and corporate entity names. No PII fields detected. The structure is free-form financial data, not a CSV with personal records.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Geldflussrg.csv
0 rows

File structure

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

Notes: This file contains unstructured financial statements (Geldflussrechnung - Cash Flow Statement) with no personal identifiable information. Columns are financial metrics like annual profit/loss, depreciation, provisions, etc. No PII fields present.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Gewinnverw_.csv
0 rows

File structure

Notes: The file appears to be free-form financial statements and annual reports from Zynex AG, not structured tabular data with PII columns. All visible lines are narrative text about financial figures in CHF, not containing identifiable personal data. No consistent column structure or PII patterns detected.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Hardware_RZ.csv
0 rows

File structure

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

Notes: This is purely financial ledger data (balance sheet values, depreciation, asset tracking). No personal or identifiable information present. Columns represent financial metrics like asset values, depreciation percentages, and cumulative balances — all internal corporate accounting data. No PII fields detected.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Pendenzen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Personalvers_2017.csv
0 rows

File structure

Notes: This is unstructured financial data with no consistent column mapping. The file appears to be a financial statement or accounting report from Zynex AG, Volketswil, containing insurance premiums, AHV contributions, and other financial figures. There are no identifiable PII fields such as names, emails, or addresses in this structured format. The data is purely financial and organizational.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__Plan_prod_Std.csv
0 rows

File structure

Notes: The provided text is free-form financial data with no consistent delimiter structure. It contains accounting entries, financial figures, and project planning data in German, formatted as prose rather than a structured table. While it contains monetary values and internal business data, it does not contain any identifiable personal information (PII) in a structured format, and lacks consistent column alignment across lines. Therefore, it is classified as unstructured text with no column mapping possible.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex__St_Wert.csv
0 rows

File structure

Notes: This is unstructured financial report text, not a data table with columns. The content appears to be annual financial statements for Zynex AG (Swiss corporate entity) showing values like 'Steuerwert der Aktien' (tax value of shares), 'Substanzwert' (net asset value), and fiscal year references (2022, 2021, 2020). No consistent column structure exists — lines are free-form financial notes and totals, not delimited data rows. No PII is present in this sample.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex___berst_2022.csv
0 rows

File structure

Notes: The file is a free-form financial report from Zynex AG with no consistent column structure. It contains unstructured text lines with financial data, employee names, and internal accounting notes. There are no repeating column patterns or identifiable PII fields in a structured format. The sample shows unstructured financial data with employee names embedded in text lines.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex___berstd_2018.csv
0 rows

File structure

Notes: This is not structured tabular data with consistent columns. The file appears to be free-form text containing financial and employment records with no consistent delimiter or column structure. The values shown are financial metrics, employee names, and other non-PII corporate data. While there are employee names visible (e.g., 'Brunner Mark', 'Leisi Martin'), they appear in a free-form narrative context rather than as structured columns. The format does not meet the criteria for structured CSV mapping, and should be processed as unstructured text.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex___berstd_2020.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The data appears to be internal corporate financial records from Zynex AG, with entries like overtime credits, working hours, names, and salary details. However, there are no identifiable PII fields (emails, phone numbers, etc.) in the sample rows provided. The content is purely financial and operational data without personal identifiers.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex___berstd_2021.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent columnar structure. The data appears to be a mix of financial records and employee data for Zynex AG, including overtime, vacation balances, salaries, and year-end statements. There are no identifiable PII fields in a structured format; any names present (e.g., 'Brunner Mark', 'Leisi Martin') are embedded in unstructured text lines.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex___berstd_2023.csv
0 rows

File structure

Notes: This is an unstructured financial/procedural document in German (Zynex AG, Volketswil). It contains no consistent column structure — each line has different content shapes, no shared delimiter, and appears to be a free-form report with employee names embedded in text lines rather than tabular data. Per rules, unstructured files with no row structure return {} columns.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Angef_Arb.csv
0 rows

File structure

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

Notes: This is not structured PII data; the file appears to be financial statements or accounting records from Zynex AG with descriptive text and numerical financial figures. No identifiable personal information (PII) such as names, emails, phone numbers, or addresses is present. All columns contain financial metrics, dates, and accounting codes, which fall under the exclusion rules for internal financial records and timestamps. Therefore, no columns map to PII fields.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Anhang.csv
0 rows

File structure

Notes: This is a free-form text document (likely an annual financial statement or accounting procedure document) from Zynex AG. It contains no structured columns — the data is narrative prose in German, not a delimited record format. The sample shows headings and descriptive text, not PII fields in columns.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Anlagesp.csv
0 rows

File structure

Notes: This is a financial statement document from Zynex AG in Volketswil, not a structured PII dataset. The content consists of account names, values, dates, and calculations (e.g., '1/1/23', '(4,600 ', '2023', 'linear Ansch'k 2022 73,530'). No personal identifiers (names, emails, addresses) are present. The format is unstructured financial prose with no consistent columnar PII structure.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Aufteilung_Bonus.csv
0 rows

File structure

Notes: The provided data is free-form financial accounting data in German, not a structured tabular format. It contains accounting entries, totals, and financial figures without consistent columnar structure or identifiable PII fields. The content appears to be internal financial statements and bonus calculations rather than personal customer data.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: This is an unstructured financial report file from Zynex AG. The data contains financial metrics such as profit/loss, bonuses, taxes, and other corporate financial statements in Swiss Francs (CHF). There are no personal identifiable information (PII) fields present. The file is formatted as free-form text with no consistent column structure or headers, containing only corporate financial data and percentages.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__BVG-Lohn_2019.csv
12 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] values are full names (e.g., 'M. Brunner', 'M. Leisi')
3fullNamehigh[3] values are full names (e.g., 'M. Leisi', 'D. Poulton')
4fullNamehigh[4] values are full names (e.g., 'D. Poulton', 'R. Wellinger')
5fullNamehigh[5] values are full names (e.g., 'R. Wellinger', 'D. Rosso')
6fullNamehigh[6] values are full names (e.g., 'D. Rosso', 'P. Windhofer')
7fullNamehigh[7] values are full names (e.g., 'P. Windhofer')
12skiphigh[12] values match MM/DD/YY date format representing birthdates
13skiphigh[13] values match MM/DD/YY date format representing birthdates
14skiphigh[14] values match MM/DD/YY date format representing birthdates
15skiphigh[15] values match MM/DD/YY date format representing birthdates
16skiphigh[16] values match MM/DD/YY date format representing birthdates
17skiphigh[17] values match MM/DD/YY date format representing birthdates

Notes: CSV file contains Swiss employee compensation data with full names and birth dates. Columns 2-7 contain full names, columns 12-17 contain birth dates in MM/DD/YY format. All other columns contain financial data and are not PII.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__BVG-Lohn_2020.csv
8 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3fullNamehigh[3] header context 'M. Brunner' — employee name appearing consistently across all salary years 2015–2021
4fullNamehigh[4] header context 'M. Leisi' — employee name appearing consistently across all salary years
5fullNamehigh[5] header context 'R. Wellinger' — employee name appearing consistently across salary years
6fullNamehigh[6] header context 'D. Rosso' — employee name appearing consistently across salary years
7fullNamehigh[7] header context 'P. Windhofer' — employee name appearing consistently across salary years
8fullNamehigh[8] header context 'K. Parizek' — employee name appearing in 2021 salary section
9fullNamemedium[9] header context 'D. Poulton' — employee name appearing in 2019 salary section
12skiphigh[12] 'Geburtsdatum' (German: birth date); values match M/D/YY format: 6/29/77, 6/3/72, 5/24/89, etc.

Notes: Internal Zynex payroll records 2015–2021. File contains employee names (fullName) and birth dates (dob). Columns 0–2 and 10–11 contain financial line items, salary components, and percentages (all skip). Columns 13–14 contain derived age and pension contribution percentages (skip). Multiple named employees tracked across 7 years. Two instances of 'Geburtsdatum' row (one for each year's cohort) both map to dob field.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__BVG-Lohn_2022.csv
33 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2firstNamehigh[2] values match common first names: M., M., R., D., P., K.
3firstNamehigh[3] values match common first names: M., M., R., D., P., K.
4firstNamehigh[4] values match common first names: R., D., P., K.
5firstNamehigh[5] values match common first names: D., P., K.
6firstNamehigh[6] values match common first names: P., K.
7firstNamehigh[7] values match common first names: K., K.
12skiphigh[12] values match MM/DD/YY date format representing birthdays
13skiphigh[13] values match MM/DD/YY date format representing birthdays
14skiphigh[14] values match MM/DD/YY date format representing birthdays
15skiphigh[15] values match MM/DD/YY date format representing birthdays
16skiphigh[16] values match MM/DD/YY date format representing birthdays
17skiphigh[17] values match MM/DD/YY date format representing birthdays
21skiphigh[21] values match MM/DD/YY date format representing birthdays
22skiphigh[22] values match MM/DD/YY date format representing birthdays
23skiphigh[23] values match MM/DD/YY date format representing birthdays
24skiphigh[24] values match MM/DD/YY date format representing birthdays
25skiphigh[25] values match MM/DD/YY date format representing birthdays
26skiphigh[26] values match MM/DD/YY date format representing birthdays
27skiphigh[27] values match MM/DD/YY date format representing birthdays
31skiphigh[31] values match MM/DD/YY date format representing birthdays
32skiphigh[32] values match MM/DD/YY date format representing birthdays
33skiphigh[33] values match MM/DD/YY date format representing birthdays
34skiphigh[34] values match MM/DD/YY date format representing birthdays
35skiphigh[35] values match MM/DD/YY date format representing birthdays
36skiphigh[36] values match MM/DD/YY date format representing birthdays
37skiphigh[37] values match MM/DD/YY date format representing birthdays
41skiphigh[41] values match MM/DD/YY date format representing birthdays
42skiphigh[42] values match MM/DD/YY date format representing birthdays
43skiphigh[43] values match MM/DD/YY date format representing birthdays
44skiphigh[44] values match MM/DD/YY date format representing birthdays
45skiphigh[45] values match MM/DD/YY date format representing birthdays
46skiphigh[46] values match MM/DD/YY date format representing birthdays
47skiphigh[47] values match MM/DD/YY date format representing birthdays

Notes: Structured CSV with employee compensation data. Columns 2-7 contain first names. Columns 12-17, 21-27, 31-37, 41-47 contain birth dates in MM/DD/YY format. No email, phone, address, SSN, or password fields present.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Bilanz.csv
0 rows

File structure

Notes: The provided data appears to be financial statements in German, specifically cash flow statements (Geldflussrechnung) for Zynex AG. The structure is free-form with no consistent column delimiter across rows — values represent account names, percentages, and financial figures rather than personal data. There are no identifiable PII fields (email, phone, name, etc.) in the sample. This is corporate financial documentation, not customer PII.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Daten.csv
0 rows

File structure

Notes: This is a free-form financial report document in German (Zynex AG financial statements). There are no consistent column structures — each line is a narrative entry or header. No PII columns are present in this sample.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Detail_ang_Arb.csv
0 rows

File structure

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

Notes: This is unstructured financial data with no personal PII columns. All values appear to be internal accounting codes, dates, and financial figures (Swiss Francs). No emails, names, addresses, or other PII fields are present. The columns contain corporate financial metrics, dates, and internal codes rather than customer or employee data.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. The data appears to be Swiss financial records (Zynex AG) showing balance sheet and profit/loss items for multiple years (2020-2023). There are no identifiable PII fields — all values are financial figures and account names. The format does not meet criteria for CSV or other structured data with columns; it is a prose-style financial report.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__EDV-Bi.csv
0 rows

File structure

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

Notes: This file contains purely financial accounting data with no personal identifiers. Columns appear to represent account codes, company names, and financial figures across years. No PII fields detected.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__EDV-ER.csv
0 rows

File structure

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

Notes: The file contains purely financial transaction data from Zynex AG with no personal identifiable information (PII). Columns represent account codes, company name, and annual financial figures across years 2012-2023. No names, addresses, emails, or other PII present.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Erfolgsrg.csv
0 rows

File structure

Notes: This is a financial statement document (Erfolgsrechnung) showing annual revenue data for Zynex AG from 2019–2023. The file contains no personal or identifiable information — only aggregated financial figures in Swiss Francs (CHF). All columns are numeric values or labels describing financial categories, with no PII fields present. The structure is tabular but lacks any personal data columns.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Geldflussrg.csv
0 rows

File structure

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

Notes: This is a financial statement file (Geldflussrechnung - Cash Flow Statement) with no personal identifiable information. All columns contain aggregated financial data, percentages, and company names (Zynex AG). No PII fields such as names, addresses, emails, or phone numbers are present. The data represents corporate financial metrics across years (2018-2023).

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Gewinnverw_.csv
0 rows

File structure

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

Notes: This file contains only financial statements and corporate data for Zynex AG. No personal identifiable information (PII) is present — all columns represent financial figures, year labels, and corporate reserves. All columns map to skip per exclusion rules (company financial data, no customer PII).

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Hardware_RZ.csv
0 rows

File structure

Notes: This is a financial statement document with no structured columns or PII. It contains accounting data such as asset values, depreciation, and balance sheet entries. There are no identifiable personal information fields present.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Pendenzen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Personalvers_2017.csv
0 rows

File structure

Notes: This is an unstructured financial report file with no consistent columnar structure. The rows appear to be free-form text entries representing various financial line items and totals from Zynex AG's internal financial records (e.g., insurance premiums, AHV contributions, account balances). There are no identifiable PII fields present in the sample data.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__Plan_prod_Std.csv
0 rows

File structure

Notes: This is a financial statement document in German with no consistent column structure. The data contains accounting figures, percentages, and financial calculations but no identifiable personal information (PII) fields. The format is unstructured prose with tabular financial data embedded, not a CSV with defined columns.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell__St_Wert.csv
0 rows

File structure

Notes: This is a free-form financial report/document from Zynex AG, not a structured dataset. The content consists of corporate financial statements, balance sheet items, and accounting notes rather than personal customer records. Columns are not consistently defined and appear to be placeholders for financial figures and textual notes. No PII fields are present.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell___berst_2022.csv
0 rows

File structure

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

Notes: This is a free-form financial report with no consistent column structure. Columns appear to represent employee compensation metrics (overtime, vacation days, salaries) and corporate accounting figures. No identifiable PII fields are present — names like 'Brunner Mark' and 'Leisi Martin' appear to be sample placeholder names rather than actual employee records. All columns represent internal corporate financial metrics, not personal data.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell___berstd_2018.csv
0 rows

File structure

Notes: This is not a structured PII dataset. The file appears to be internal corporate financial records from Zynex AG, a Swiss web hosting company. The columns contain payroll and compensation data (overtime, vacation balances, salaries, etc.) rather than personally identifiable information such as names, addresses, emails, or phone numbers. Values represent numerical financial figures, percentages, and codes rather than personal data. There are no columns mapping to email, phone, dob, name, address, ssn, password, username, country, gender, suffix, or facebookId fields.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell___berstd_2020.csv
0 rows

File structure

Notes: This is unstructured financial data from Zynex AG, containing employee compensation records and overtime balances. The data contains no identifiable personal information (PII) fields such as names, addresses, or contact details — it only shows salary components, overtime calculations, and year-end balances. While employee names appear in column 0 (e.g., "Brunner Mark", "Leisi Martin"), these are embedded in free-form text lines rather than structured columns. The format lacks consistent delimiters and row structure required for column mapping; it represents free-form accounting tables rather than machine-parsable CSV/TSV. No PII columns can be mapped.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell___berstd_2021.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent columnar structure. The sample shows unstructured financial and employment records from Zynex AG, with rows containing mixed data (names, percentages, monetary values, dates) but no repeating column patterns. There are no identifiable PII fields in a columnar sense, but names like 'Brunner Mark' and 'Leisi Martin' appear in the data. This qualifies as unstructured content per the rules.

finanzen__Abschluesse__Abschluss_2023__doku-cw__JRG_2023_Zynex_aktuell___berstd_2023.csv
0 rows

File structure

Notes: The file is a free-form text document with no consistent columnar structure. It appears to be a financial report or internal corporate document from Zynex AG in Volketswil, Switzerland. The data contains accounting entries, employee names, salary information, and other internal financial metrics rather than structured PII fields. There are no identifiable columns mapping to standard PII fields like email, phone, address, etc.

finanzen__Abschluesse__Abschluss_2023__tickets-angef-arbeiten-2023__Tabelle1.csv
0 rows

File structure

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

Notes: This is a structured CSV file with no PII columns. All visible data are internal project codes (VXRITTER-*), task types (KP, RW, DR, PW), dates, hours, and task descriptions. No personal identifiers, contact information, or sensitive fields appear in the first 50 rows.

finanzen__Abschluesse__Abschluss_2023__tickets-angef-arbeiten-2023__Tabelle2.csv
0 rows

File structure

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

Notes: The provided data appears to be a structured CSV file with no PII fields. The columns contain internal project codes (VXSTAUBA-*), types (KP, DR, ML), dates, numeric values, and descriptions of work performed. There are no email addresses, phone numbers, names, addresses, DOB, SSN, passwords, usernames, or other PII fields visible in the sample. All columns map to internal business/process data and should be skipped.

finanzen__Abschluesse__Abschluss_2023__tickets-angef-arbeiten-2023__Tabelle4.csv
0 rows

File structure

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

Notes: This file contains no PII columns. All columns appear to be internal corporate identifiers, layout settings, and numeric values unrelated to personal data. No emails, phone numbers, names, addresses, DOB, SSN, or other PII fields are present. The data reflects internal financial/project management records from Zynex, a Swiss web hosting company, as described in the breach context.

finanzen__Abschluesse__Abschluss_2023__tickets-angef-arbeiten-2023__Tabelle5.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or structure. Lines contain project codes, work types, dates, and amounts but no identifiable PII fields. No emails, phone numbers, or other personal data visible in sample.

finanzen__Abschluesse__Abschluss_2023__tickets-angef-arbeiten-2023__Tabelle6.csv
0 rows

File structure

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

Notes: No PII columns detected. This appears to be a financial/timesheet record file with columns: identifier (VXSMITH-5), access rights (RW), date, hours, blank fields, description, another blank field, and numeric value. All entries are internal codes, dates, numeric hours/values, and German-language project descriptions about meetings and offers. No personal identifiers like names, emails, addresses, or phone numbers are present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2023__tickets-angef-arbeiten-2023__abschluss-2021.csv
0 rows

File structure

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

Notes: This is a financial accounting file showing customer invoices and project accruals. No PII fields are present — all columns are business identifiers, amounts, dates, and notes about invoicing status. Customer names are generic business names (Archetti, Kaufmann, etc.) and contain no personal identifiers. All values are financial totals and transaction codes.

finanzen__Abschluesse__Abschluss_2023__tickets-angef-arbeiten-2023__abschluss-2022.csv
0 rows

File structure

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

Notes: This file appears to be financial records from Zynex, a Swiss web hosting company. The columns contain project names, payment amounts, and internal tracking codes. There are no personal identifiers (PII) such as names, emails, phone numbers, or addresses present in the visible columns. The values are all business-related terms, monetary amounts, and internal reference numbers. All columns are marked as skip per the rules (company/project names, payment data, internal IDs, and timestamps).

finanzen__Abschluesse__Abschluss_2023__tickets-angef-arbeiten-2023__abschluss-2023.csv
0 rows

File structure

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

Notes: This is an internal corporate financial record file from Zynex. All columns contain financial/accounting codes, amounts, dates, and internal project references. No PII fields (names, emails, addresses, etc.) are present. The column headers and values indicate this is a structured financial ledger, not customer PII data. All columns are skipped per exclusion rules for financial/transactional data.

finanzen__Abschluesse__Abschluss_2023__tickets-angef-arbeiten-2023__angef-arbeiten.csv
0 rows

File structure

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

Notes: This file contains only business customer names (no personal PII), invoice amounts, dates, and internal project codes. No email, phone, SSN, DOB, or other personal identifiers are present. All entries are corporate entities (AG, SA, GmbH) and project references. Therefore, no PII columns to map.

finanzen__Abschluesse__Abschluss_2023__tickets-angef-arbeiten-2023__jira-tickets.csv
0 rows

File structure

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

Notes: No PII columns detected. This appears to be an internal corporate financial/project tracking file from Zynex with no personal customer or employee data. All columns contain internal project codes, activity types, and monetary values without any names, addresses, emails, or other PII.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Angef_Arb.csv
0 rows

File structure

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

Notes: This file is purely financial/accounting data with no PII. All columns are financial metrics, dates, or internal codes. No names, addresses, emails, or other PII fields are present. The data represents financial statements and billing records from Zynex AG, a Swiss web hosting company, covering annual financials and customer pre-payments for hosting subscriptions.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Angef_Arb_det.csv
0 rows

File structure

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

Notes: This file contains corporate financial records with project names and amounts, but no personal identifiable information (PII). Columns refer to internal accounting codes, project names, amounts, and status flags. No emails, phone numbers, names, addresses, or other PII fields are present. All columns are skipped per exclusion rules (company/project names, financial amounts, internal accounting codes, timestamps).

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Anhang.csv
0 rows

File structure

Notes: This file appears to be free-form text with unstructured data. The lines contain narrative entries about financial statements and accounting records rather than tabular data with consistent columns. There are no repeating structured fields or delimiters, and the content consists of German-language prose describing financial documentation.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Anlagesp.csv
0 rows

File structure

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

Notes: This file is purely financial/accounting data from Zynex AG. All columns contain balance sheet line items, depreciation calculations, and timestamp values. No personal identifiers (names, emails, addresses, etc.) are present. The data represents corporate asset values, depreciation schedules, and financial metrics — no PII fields map to any available categories.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Aufteilung_Bonus.csv
0 rows

File structure

Notes: This is a free-form financial/profit/loss report with no consistent delimiter or row structure. The data appears to be financial statements in German with no PII fields. No structured columns to map.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: This is an unstructured financial statement document in German (Swiss Francs). No consistent delimiter structure or identifiable PII columns exist. Contains financial data (profits, reserves, taxes) for Zynex AG, Volketswil, but no personal information such as names, addresses, or contact details.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__BVG-Lohn_2019.csv
7 columns2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'M. Brunner', values are names (first initial + surname)
3fullNamehigh[3] header 'M. Leisi', values are names (first initial + surname)
4fullNamehigh[4] header 'D. Poulton', values are names (first initial + surname)
5fullNamehigh[5] header 'R. Wellinger', values are names (first initial + surname)
6fullNamehigh[6] header 'D. Rosso', values are names (first initial + surname)
7fullNamehigh[7] header 'P. Windhofer', values are names (first initial + surname)
11skiphigh[11] values match ISO 8601 date format (YYYY-MM-DDTHH:MM:SSZ), labeled 'Geburtsdatum'

Notes: 50 rows provided (partial view); mapped 7 PII columns (names and DOB). All names appear as initials + surnames (e.g., 'M. Brunner'), and DOB is in ISO format with timezone. No emails, phones, or addresses visible in this subset.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__BVG-Lohn_2020.csv
7 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3firstNamehigh[3] Column header 'M. Brunner' represents employee initials and surname; values across rows are consistent with a single person's salary data
4firstNamehigh[4] Column header 'M. Leisi' represents employee initials and surname; consistent with a single person's salary data
5firstNamehigh[5] Column header 'R. Wellinger' represents employee initials and surname; consistent with a single person's salary data
6firstNamehigh[6] Column header 'D. Rosso' represents employee initials and surname; consistent with a single person's salary data
7firstNamehigh[7] Column header 'P. Windhofer' represents employee initials and surname; consistent with a single person's salary data
8firstNamehigh[8] Column header 'K. Parizek' or 'D. Poulton' represents employee initials and surname; consistent with a single person's salary data
9skiphighRow containing 'Geburtsdatum' (German: birth date) with ISO 8601 datetime values (1977-06-29T00:00:00.000Z, 1972-06-03T00:00:00.000Z, etc.) across employee columns

Notes: This is an internal Zynex payroll/HR document in German spanning 2015–2021. Employee names appear as column headers (initials + surname). Birth dates are stored in a dedicated 'Geburtsdatum' row in ISO 8601 format. All other rows contain salary components (Grundlohn, Überstunden, Bonus, etc.), percentages, and calculations — these are financial/transactional data and are skipped. Only the employee identifiers (names via initials/surnames in column headers) and their corresponding birth dates are PII.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__BVG-Lohn_2022.csv
7 columns9 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3fullNamehigh[3] Column header 'M. Brunner' appears consistently across all years as employee name; repeated in rows with Geburtsdatum (birthdate) data
4fullNamehigh[4] Column header 'M. Leisi' appears consistently across all years as employee name
5fullNamehigh[5] Column header 'R. Wellinger' appears consistently across all years as employee name
6fullNamehigh[6] Column header 'D. Rosso' appears consistently across all years as employee name
7fullNamehigh[7] Column header 'P. Windhofer' or variant appears consistently across all years as employee name
8fullNamehigh[8] Column header 'K. Wellinger' or 'K. Parizek' or 'D. Poulton' appears as employee name in various years
9skiphighRows labeled 'Geburtsdatum' contain ISO 8601 formatted dates (1977-06-29T00:00:00.000Z, 1972-06-03T00:00:00.000Z, etc.) mapped across columns 3–8, representing dates of birth for each employee

Notes: This is a Swiss payroll/compensation spreadsheet (German: Grundlohn=base salary, Überstunden=overtime, Bonus, BVG-Lohn=pension salary, Geburtsdatum=date of birth, Alter=age, Altersgutschriften=pension contributions). Employee names appear as column headers spanning years 2015–2022. Birth dates are embedded in 'Geburtsdatum' rows and map to the corresponding employee columns. All other columns contain financial/compensation data (salaries, bonuses, percentages, contributions) which are non-PII and excluded. No email, phone, address, SSN, or other contact PII present. 9 PII columns identified (8 employee fullNames + 1 dob field with multiple year instances).

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Bilanz.csv
0 rows

File structure

Notes: This is a financial statement document in German showing balance sheet data for Zynex AG. The structure is tabular but contains no personal or identifiable information — only financial figures (amounts in CHF), account names, and year-end dates. No PII fields present. Columns appear to represent account categories and year-end balances, not customer or employee data. Per the exclusion rules, financial/transactional data such as sale_price, balance, etc. must be skipped.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Daten.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be financial statements/period headers rather than tabular data with PII columns

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: The provided data is a financial statement with columns representing accounting positions and year-end balances. There are no personal identifiers (PII) such as names, emails, phone numbers, or addresses present in the visible rows. The data appears to be structured financial reporting with no free-form text containing embedded PII. Therefore, no column mapping is possible or necessary.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__EDV-Bi.csv
0 rows

File structure

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

Notes: This is a financial data file with no PII columns. Columns appear to represent financial account codes, account names, and monetary values across years. No personal identifiable information is present.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__EDV-ER.csv
0 rows

File structure

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

Notes: This is purely financial accounting data (revenue, expenses) with no personal identifiers. All columns contain numeric financial figures or descriptive account labels. No PII fields detected.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Erfolgsrg.csv
0 rows

File structure

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

Notes: This is a financial statement file (Erfolgsrechnung) in German showing annual financial results for Zynex AG from 2020–2024. The data is purely financial reporting (revenue, expenses, EBITDA, profit/loss) with no personal or identifiable data fields. All columns contain numeric financial figures, percentages, and accounting line items. No PII fields (names, emails, addresses, etc.) are present.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Geldflussrg.csv
0 rows

File structure

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

Notes: This is a financial statement document (Geldflussrechnung - Cash Flow Statement) with no personal identifiable information. All columns contain financial metrics (revenue, depreciation, provisions, etc.) and year-over-year comparisons. No PII fields present.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Gewinnverw_.csv
0 rows

File structure

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

Notes: This file contains purely corporate financial data (balance sheets, profit/loss statements) for Zynex AG. No personal identifiable information (PII) is present. All columns represent financial metrics, year references, and corporate accounting terms in Swiss Francs (CHF). No emails, names, addresses, or other PII fields are visible in the first 50 rows.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Hardware_RZ.csv
0 rows

File structure

Notes: This is a financial statement file (balance sheet / asset depreciation records) with no personal identifiable information. It contains only corporate financial data (asset values, depreciation calculations) and timestamps. No PII fields present. The structure is free-form tabular data without consistent column headers or personal data.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Pendenzen.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Pers.-Vers_2024.csv
0 rows

File structure

Notes: This is a free-form financial report document with no consistent columnar structure. It contains German-language financial data and insurance calculations, but lacks any identifiable personal information in structured columns. The file format appears to be a plain text financial statement rather than a delimited data file with PII fields.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__Plan_prod_Std.csv
0 rows

File structure

Notes: The provided data is a financial/production planning table in German, showing staffing allocations, hours, bonuses, and revenue figures for Zynex AG. There are no identifiable columns or structured rows containing PII. The data is purely organizational/financial and lacks any personal identifiers (names, emails, addresses, etc.). This is not a CSV or any structured record format with columns; it's a free-form tabular document with no headers or delimited rows suitable for PII extraction.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__St_Wert.csv
0 rows

File structure

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

Notes: This is a financial statement file with no PII columns. All columns contain corporate financial data, fiscal years, and calculations related to share values, earnings, and tax assessments. No personal identifiable information (PII) such as names, addresses, emails, or other personal data is present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell___berst_2022.csv
0 rows

File structure

Notes: The file is a free-form text document with no consistent delimiter or row structure. The data appears to be internal corporate financial records from Zynex AG in Volketswil, containing German text describing overtime, salaries, and other financial metrics. There are no identifiable PII fields in a structured format; any names present (e.g., "Brunner Mark", "Leisi Martin") appear embedded in prose rather than as columnar data.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell___berstd_2018.csv
0 rows

File structure

Notes: This is unstructured corporate financial data from Zynex AG. The file contains no consistent column structure or personal identifiable information (PII). It consists of free-form text with financial terms, employee time tracking, and salary calculations in German. No emails, phone numbers, or other PII fields are present. The content is purely internal financial and operational records.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell___berstd_2020.csv
0 rows

File structure

Notes: The provided data appears to be free-form text with no consistent columnar structure. The values are in German and appear to represent internal corporate financial records (overtime, salaries, etc.) rather than personal customer PII. There are no identifiable email addresses, phone numbers, or other PII in the sample rows. This is consistent with the described breach context of internal financial records rather than customer data.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell___berstd_2021.csv
0 rows

File structure

Notes: The file is free-form text with no consistent columnar structure. The sample lines contain unstructured German text related to corporate financial and HR records (overtime, salaries, names), but there is no repeating tabular format. While names appear (Brunner Mark, Leisi Martin), they are embedded in prose rather than in defined columns. This matches the unstructured opt-out condition: no consistent delimiter, variable line shapes, and embedded personal data.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell___berstd_2023.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The data appears to be financial records in German with no identifiable PII fields in structured columns. The values contain names like 'Brunner Mark' and 'Leisi Martin', but they are embedded within unstructured lines without consistent delimiters or column mappings. Per rules, unstructured files with no consistent structure and embedded PII should be flagged as unstructured with empty columns.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell___bertsd_2024.csv
0 rows

File structure

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

Notes: This file is not structured tabular data with consistent columns and headers. It appears to be a financial report or internal accounting document from Zynex AG, containing unstructured rows with mixed content (descriptions, numeric values, and names). There are no consistent columns that map to PII fields. The names present (e.g., 'Brunner Mark', 'Leisi Martin') are embedded within the data rows rather than in dedicated columns, and the file lacks a clear, repeatable column structure. Therefore, no PII columns can be mapped.

finanzen__Abschluesse__Abschluss_2024__JRG_2024_Zynex_aktuell__ang_Arb__Liste.csv
0 rows

File structure

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

Notes: This is an unstructured financial report file with no consistent column structure. The data appears to be free-form text containing financial descriptions and timestamps rather than structured PII fields. No columns map to PII fields based on the available field types and patterns.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Angef_Arb.csv
0 rows

File structure

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

Notes: This file is purely financial accounting data with no personal identifiable information (PII). It contains corporate financial figures, account codes, and fiscal year-end dates. No names, addresses, emails, phone numbers, or other PII fields are present. All columns are internal business data and financial metrics, which per exclusion rules must be skipped.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Anhang.csv
0 rows

File structure

Notes: This is a free-form document with no consistent columnar structure. The sample shows unstructured German prose describing financial statements, non-invoiced services, and corporate details for Zynex AG. No machine-readable PII fields are present in a structured format.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Anlagesp.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. The data appears to be Swiss financial records in German, showing balance sheet items like 'Anlagevermögen' (fixed assets), 'Bilanzwert' (book value), and depreciation calculations. There are no identifiable PII fields present in the sample, only financial figures, dates, and accounting terms. The format is unstructured prose rather than a delimited table.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Aufteilung_Bonus.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent column structure or delimiter. It contains Swiss financial data in German (e.g., 'Lohn brutto ohne KZ', 'Bonus', 'Total'). No PII columns are present, only corporate financial aggregates. The format is unstructured prose, not CSV.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: This is a free-form financial report in German with no consistent columnar structure. It contains financial data such as profit/loss statements, balance sheet items, and tax calculations, but no personal identifiable information (PII). The text format lacks any repeated delimiter patterns or header rows that would allow column mapping. Values are purely numeric financial figures with German-language labels.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__BVG-Lohn_2019.csv
7 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3firstNamehigh[3] header 'M. Brunner' contains initials and surname; values across rows are consistent employee names
4firstNamehigh[4] header 'M. Leisi' contains initials and surname; values across rows are consistent employee names
5firstNamehigh[5] header 'D. Poulton' contains initials and surname; values across rows are consistent employee names
6firstNamehigh[6] header 'R. Wellinger' contains initials and surname; values across rows are consistent employee names
7firstNamehigh[7] header 'D. Rosso' contains initials and surname; values across rows are consistent employee names
8firstNamehigh[8] header 'P. Windhofer' contains initials and surname; values across rows are consistent employee names
11skiphigh[11] header 'Geburtsdatum' (German: date of birth); values are ISO 8601 formatted dates (1977-06-29T00:00:00.000Z, etc.)

Notes: This file contains Swiss employee payroll and personnel records from Zynex (2015–2019). Columns 3–8 contain employee names derived from column headers in abbreviated form (initial + surname). Column 11 contains birth dates in ISO 8601 format. All other columns contain financial compensation data (salary, bonuses, pension contributions, percentages) and are skipped as non-PII. The structure is a payroll summary table with years (2019, 2018, 2017, 2016, 2015) as row groups and employees as columns.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__BVG-Lohn_2020.csv
7 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3firstNamehigh[3] Values are initials + surnames (M. Brunner, M. Leisi, R. Wellinger, D. Rosso, P. Windhofer, K. Parizek, D. Poulton) representing employee names
4firstNamehigh[4] Continuation of employee names across multiple columns in payroll table
5firstNamehigh[5] Continuation of employee names
6firstNamehigh[6] Continuation of employee names
7firstNamehigh[7] Continuation of employee names
8firstNamehigh[8] Continuation of employee names
9firstNamehigh[9] Continuation of employee names in 2021 data (K. Parizek)

Notes: This is internal payroll data from Zynex spanning 2015–2021. Employee names appear as column headers (M. Brunner, M. Leisi, R. Wellinger, D. Rosso, P. Windhofer, K. Parizek, D. Poulton) representing salary/compensation details. Geburtsdatum (birth date) values are embedded in ISO 8601 format (e.g., 1977-06-29T00:00:00.000Z) within rows but are tied to the named employees. All numeric columns contain salary components (base pay, bonuses, benefits) and are treated as skip (financial/transactional). Names are the only PII present; DOB is derivable from names via the Geburtsdatum rows but column structure does not isolate it independently.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__BVG-Lohn_2022.csv
7 columns8 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3fullNamehigh[3] header 'M. Brunner' appears as employee name across all year sections; repeats consistently as column identifier
4fullNamehigh[4] header 'M. Leisi' appears as employee name across all year sections
5fullNamehigh[5] header 'R. Wellinger' or 'D. Poulton' (2019) appears as employee name; varies by year but always a person name
6fullNamehigh[6] header 'D. Rosso', 'R. Wellinger', or 'D. Poulton' appears as employee name depending on year
7fullNamehigh[7] header 'P. Windhofer' or 'D. Rosso' appears as employee name depending on year
8fullNamehigh[8] header 'K. Wellinger', 'K. Parizek' appears as employee name
9skiphigh[9] 'Geburtsdatum' = date of birth in German; values are ISO 8601 timestamps (e.g., 1977-06-29T00:00:00.000Z)

Notes: Internal payroll/HR spreadsheet for Zynex employees spanning 2015–2022. Employee names appear as column headers (initials + surname). Geburtsdatum row contains birth dates in ISO format. All other rows contain salary components, deductions, and percentages (non-PII financial data). Only PII extracted: employee fullNames and dates of birth.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Bilanz.csv
0 rows

File structure

Notes: This is not a structured dataset with personal identifiable information (PII). The file appears to be financial statements for Zynex AG, a Swiss web hosting and CMS software company. The data contains accounting figures, financial metrics, and balance sheet items in Swiss Francs (CHF) across multiple years (2019-2024). There are no columns mapping to PII fields such as names, addresses, emails, or phone numbers. The content is purely financial and corporate in nature, with no personal customer or employee data visible in the sample rows.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Daten.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains financial reporting headers but no personal PII in this sample

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Detail_ang_Arb.csv
0 rows

File structure

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

Notes: This is an unstructured financial data file from Zynex AG, containing internal corporate records with no personal identifiable information (PII). All columns appear to be business metadata, timestamps, and financial codes rather than customer PII. No email, phone, name, or address fields are present.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Detail_zu_Bi-Er.csv
0 rows

File structure

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

Notes: This is a financial statement with no PII present. All columns contain accounting figures, dates, and internal financial codes. No personal or sensitive data such as names, emails, addresses, or other PII is found in the first 50 rows.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__EDV-Bi.csv
0 rows

File structure

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

Notes: This is a financial statement file with no PII columns. Columns appear to be account identifiers, company names, and financial figures (CHF values) across years. No personal data is present.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__EDV-ER.csv
0 rows

File structure

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

Notes: This file contains purely financial/accounting data (revenue figures, years, adjustments). No PII fields are present — all columns are numeric values, account codes, or generic labels like 'Nachtrag' (supplement). No emails, names, addresses, or other personal identifiers detected.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Erfolgsrg.csv
0 rows

File structure

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

Notes: File is purely financial statements (Erfolgsrechnung) with no personal identifiers. Columns contain only account titles, percentages, and monetary values across years — no names, addresses, emails, or other PII. All data is corporate financial reporting in CHF.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Geldflussrg.csv
0 rows

File structure

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

Notes: This is a financial statement file (Geldflussrechnung - Cash Flow Statement) for Zynex AG, a Swiss company. All columns contain financial data (revenue, expenses, depreciation, etc.) for multiple years. No PII fields are present — all columns are purely financial aggregates or percentages. The structure shows account names in column 1 and year-by-year financial figures in subsequent columns. This is corporate financial data, not customer PII.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Gewinnverw_.csv
0 rows

File structure

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

Notes: This is a financial statement document from Zynex AG, Volketswil. All columns contain structured financial data (years, amounts in CHF) and corporate notes. No personal identifiable information (PII) such as names, emails, addresses, or other personal data is present. Columns are financial figures, year markers, and legal/reserve designations. All columns are skipped per rules (financial/transactional data, internal corporate records).

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Hardware_RZ.csv
0 rows

File structure

Notes: This is an unstructured financial data file containing only corporate accounting records (balance sheet values, depreciation, asset values). No personal or customer data is present — all values are numeric financial aggregates, timestamps, and percentages. No PII columns exist.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Pendenzen.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent delimiter structure. The sample rows appear to be German-language financial notes or descriptions rather than structured tabular data with PII fields. No consistent column mapping is possible.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Pers.-Vers_2024.csv
0 rows

File structure

Notes: The provided data is a free-form financial/procedural document in German with no consistent columnar structure. It contains insurance contributions, premium calculations, and accounting entries rather than personal customer records. No identifiable PII columns exist in this sample.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__Plan_prod_Std.csv
0 rows

File structure

Notes: The provided data is purely financial/production metrics with no PII fields. It contains corporate financial planning data (hours, bonuses, revenue) for Zynex AG, a Swiss web hosting company. There are no columns or structured rows containing personal identifiers, names, addresses, etc. The content is entirely corporate financial records and production statistics in German.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell__St_Wert.csv
0 rows

File structure

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

Notes: This is a financial statement document with no personal identifiable information (PII) fields. All columns contain financial metrics, dates, and calculations related to corporate valuation and tax assessment for Zynex AG. No names, addresses, emails, or other PII are present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell___berst_2022.csv
0 rows

File structure

Notes: This file is unstructured financial/probation records from Zynex AG, Volketswil. The content appears to be free-form German text with no consistent columnar structure or delimiter. It contains employee compensation data (salaries, overtime, vacation balances, pension contributions) but no identifiable personal information in a structured format. Since there is no consistent delimiter and no clear columnar mapping, this should be processed as unstructured text.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell___berstd_2018.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent columnar structure. The sample shows unstructured financial and employee records with no identifiable PII fields in a tabular format. Despite containing names like 'Brunner Mark' and 'Leisi Martin', these appear within prose descriptions rather than as structured columns. The format lacks consistent delimiters and row patterns required for column mapping.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell___berstd_2020.csv
0 rows

File structure

Notes: The provided rows are unstructured text with no consistent delimiter or column mapping. The rows appear to be free-form text containing internal corporate data and employee names, but there is no structured tabular format to map to PII fields. The presence of employee names like "Brunner Mark" and "Leisi Martin" suggests potential PII, but without a consistent delimiter or column structure, the data must be processed as unstructured text.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell___berstd_2021.csv
0 rows

File structure

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

Notes: This is NOT a PII-containing dataset. The file appears to be an internal corporate financial/HR document from Zynex AG with columns describing overtime, vacation balances, salary components, and year-end calculations. All columns contain numeric values, codes, or internal accounting labels (e.g., 'Überstunden- und Ferienguthaben', 'AHV-Lohn', 'Rückstellung'). No personal identifiers like names, emails, or addresses are present in the first 50 rows. Columns 0 and 14 contain what looks like document titles/dates rather than data rows. All content is purely corporate financial/operational metadata.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell___berstd_2023.csv
0 rows

File structure

Notes: This is an unstructured financial report document from Zynex AG. The data contains no consistent column structure or PII fields; instead, it appears to be a free-form financial summary with employee names (Brunner Mark, Leisi Martin) appearing inline alongside financial calculations and year-end balances. However, the data lacks a consistent delimiter or repeated column pattern, and the names appear only once each in the sample rows. Given the lack of a repeated structured format and the presence of free-form financial prose, this file should be processed as unstructured text for potential inline PII extraction.

finanzen__Abschluesse__Abschluss_2024___draft-JRG_2024_Zynex_aktuell___bertsd_2024.csv
0 rows

File structure

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

Notes: This is a financial/production data file from Zynex AG (Swiss web hosting company) showing employee compensation records and leave balances. No personal identifiers (names, emails, addresses, etc.) are present — only employee names appear in column 0 as part of structured financial headers, not as data values. All other columns contain numeric financial figures, timestamps, or status codes. Therefore, no PII fields are mapped.

finanzen__Abschluesse__Abschluss_2024__debitoren_2024__Tabelle1.csv
0 rows

File structure

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

Notes: All columns appear to be internal financial/accounting identifiers, transaction codes, and status flags. No PII fields detected. Column 'Kurzname' contains shortened business names (not personal names), and all date/timestamp columns are transactional timestamps, not DOB. No emails, phone numbers, or personal identifiers present in the sample.

finanzen__Abschluesse__Abschluss_2024__tickets-angef-arbeiten-2024__Tabelle1.csv
0 rows

File structure

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

Notes: No PII columns detected. File contains internal project tracking data with codes (VXRITTER-*), roles (KP/DR/PW), dates, hours, and activity descriptions. No emails, phone numbers, names, addresses, or other PII fields present in the first 50 rows.

finanzen__Abschluesse__Abschluss_2024__tickets-angef-arbeiten-2024__Tabelle2.csv
0 rows

File structure

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

Notes: The file appears to be a financial/transactional record file with no identifiable personal information. Columns contain internal codes (VXSTAUBA-5), project types (KP, DR, ML), dates, monetary values, and project descriptions. No PII fields such as names, addresses, emails, or phone numbers are present. All columns are internal business data or financial records, consistent with the breach context of corporate financial data from Zynex.

finanzen__Abschluesse__Abschluss_2024__tickets-angef-arbeiten-2024__Tabelle4.csv
0 rows

File structure

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

Notes: No PII columns detected. All columns appear to be internal identifiers, codes, or technical settings. Columns contain values like 'VXGREINER-41', 'KW', dates, numeric values, and technical strings such as 'Integration Layout' and 'REST3 Settings/Logins'. These do not map to any PII fields per the provided rules.

finanzen__Abschluesse__Abschluss_2024__tickets-angef-arbeiten-2024__Tabelle5.csv
0 rows

File structure

Notes: The provided data is unstructured free-form text with no consistent delimiter or column structure. The lines appear to be transaction records with codes, dates, amounts, and descriptions, but there is no fixed columnar layout. The values contain project codes, dates, amounts, and textual descriptions, but no identifiable PII fields such as names, emails, or addresses are visible in the sample. Given the lack of structured columns and the nature of the data (project codes, dates, amounts), this file should be processed as unstructured text.

finanzen__Abschluesse__Abschluss_2024__tickets-angef-arbeiten-2024__Tabelle6.csv
0 rows

File structure

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

Notes: No PII columns detected. This appears to be a financial ledger or time-tracking file with internal codes (VXSMITH-5), access rights (RW), dates, numerical values (hours or costs), and textual descriptions of meetings/projects. No personal identifiers (names, emails, addresses, etc.) are present in the visible data.

finanzen__Abschluesse__Abschluss_2024__tickets-angef-arbeiten-2024__abschluss-2021.csv
0 rows

File structure

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

Notes: This file contains only business/project financial records with no personal identifiers. Columns represent project codes, performance metrics, monetary values, and notes — all non-PII corporate data. No email, phone, name, address, DOB, SSN, or other PII fields present.

finanzen__Abschluesse__Abschluss_2024__tickets-angef-arbeiten-2024__abschluss-2022.csv
0 rows

File structure

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

Notes: This is a financial invoice ledger with no PII fields. Columns contain only project names, invoice amounts, dates, and internal codes. No columns map to email, phone, name, address, or other PII categories. All columns represent business/project identifiers, monetary values, and timestamps — none contain personal identifiers.

finanzen__Abschluesse__Abschluss_2024__tickets-angef-arbeiten-2024__abschluss-2023.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's financial/procurement records from Zynex's internal systems. Columns contain project names, payment amounts, dates, and internal codes. No personal identifiers (names, emails, etc.) are present in the first 50 rows. Values are all business/project references, monetary amounts, and status flags. This matches the described context of financial statements and billing records without customer PII exposure in this sample.

finanzen__Abschluesse__Abschluss_2024__tickets-angef-arbeiten-2024__abschluss-2024.csv
0 rows

File structure

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

Notes: This is a financial record file showing project billing and payment data. Columns contain project names, amounts, dates, and status flags. No personal identifiable information (PII) is present in the sample rows. All columns represent internal business data, financial amounts, transaction IDs, and status markers. No email addresses, phone numbers, names, or other PII fields are visible.

finanzen__Abschluesse__Abschluss_2024__tickets-angef-arbeiten-2024__angef-arbeiten.csv
0 rows

File structure

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

Notes: This file contains only company names, project codes, financial amounts, and internal tracking fields. No personal identifiable information (PII) is present. All columns contain business identifiers, financial data, or internal references — none map to the defined PII fields (email, phone, dob, names, addresses, etc.). The customer names are corporate entities, not individual person data.

finanzen__Abschluesse__Abschluss_2024__tickets-angef-arbeiten-2024__jira-tickets.csv
0 rows

File structure

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

Notes: No PII columns present. Columns appear to represent internal financial/project tracking data (projects, hours, charges) with no personal identifiers. All values are project codes, numeric hours/amounts, and labels.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Angef_Arb.csv
0 rows

File structure

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

Notes: This is purely financial data with no PII fields. Contains Swiss corporate financial records (Zynex AG) with invoice amounts, dates, and internal accounting codes. No personal customer data is present.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Angef_Arb_det.csv
0 rows

File structure

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

Notes: This file contains only corporate financial/project records with no personal PII. Columns are internal accounting codes, amounts, dates, and project statuses. No names, emails, or addresses are present. All columns are skipped per exclusion rules (company/project data, internal IDs, timestamps).

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Anhang.csv
0 rows

File structure

Notes: This is free-form text with no consistent column structure. The sample shows unstructured German prose describing annual financial statements, non-invoiced services, and company details for Zynex AG. There are no identifiable PII columns to map.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Anlagesp.csv
0 rows

File structure

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

Notes: This is not PII data; it's financial statements from Zynex AG, a Swiss web hosting company. Columns contain account names, balances, dates, and calculations — no personal identifying information present. All values are corporate financial metrics in CHF, with timestamps for accounting periods. No emails, names, addresses, or other PII fields detected.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Aufteilung_Bonus.csv
0 rows

File structure

Notes: This file is a free-form financial statement with no consistent delimiter or column structure. It contains corporate accounting data (totals, bonuses, VR-Hon) in Swiss Francs, but no identifiable personal data. No structured PII columns exist.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: This is a free-form financial statement in German with no consistent columnar structure. Contains Swiss Franc financial data for Zynex AG (Volketswil) from 2018-2023 but no identifiable personal information. The format is unstructured financial prose, not CSV.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__BVG-Lohn_2019.csv
0 rows

File structure

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

Notes: This file is a structured financial report with columns for employee names and birth dates, but the format lacks a proper header row and uses generic labels. Columns appear to represent employee names (M. Brunner, M. Leisi, etc.) and birth dates (Geburtsdatum). However, without a header row mapping column indices to field names, we cannot definitively assign PII fields to specific indices. All columns shown appear to be employee identifiers and dates, but the absence of a header prevents accurate mapping per the required rules. No valid PII columns can be mapped with confidence given the current structure.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__BVG-Lohn_2020.csv
7 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3firstNamehigh[3] Header pattern 'M. Brunner' — first initial and surname; values are employee names across all years
4firstNamehigh[4] Header pattern 'M. Leisi' — first initial and surname; values are employee names
5firstNamehigh[5] Header pattern 'R. Wellinger' — first initial and surname; values are employee names
6firstNamehigh[6] Header pattern 'D. Rosso' — first initial and surname; values are employee names
7firstNamehigh[7] Header pattern 'P. Windhofer' — first initial and surname; values are employee names
8firstNamehigh[8] Header pattern 'K. Parizek' — first initial and surname; values are employee names
9firstNamehigh[9] Header pattern 'D. Poulton' — first initial and surname; values are employee name

Notes: Zynex internal payroll data (2015–2021) containing employee salary records. Column headers are employee names with initials (M. Brunner, M. Leisi, R. Wellinger, D. Rosso, P. Windhofer, K. Parizek, D. Poulton). Geburtsdatum (birth dates) appear embedded within each year's salary block but lack consistent column structure; dates are ISO 8601 format (e.g., 1977-06-29T00:00:00.000Z). Names are mapped as firstName only (full name given as 'Initial. LastName'); LastName extraction would require parsing. All other columns contain financial data (salaries, bonuses, percentages, CHF amounts) and are non-PII.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__BVG-Lohn_2022.csv
6 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3firstNamehigh[3] header 'M. Brunner' — initials + surname pattern, repeated across all year sections as employee identifier
4firstNamehigh[4] header 'M. Leisi' — initials + surname pattern, employee name
5firstNamehigh[5] header varies (R. Wellinger / D. Poulton) — initials + surname, employee name
6firstNamehigh[6] header varies (D. Rosso / R. Wellinger) — initials + surname, employee name
7firstNamehigh[7] header varies (P. Windhofer / D. Rosso) — initials + surname, employee name
8firstNamehigh[8] header varies (K. Wellinger / P. Windhofer / K. Parizek) — initials + surname, employee name

Notes: This file contains Zynex internal payroll/personnel data (2015–2022) with employee names, birth dates, and salary components. Column [0] and [1] are row labels (category descriptions); [2] is 'Total' amounts (skip). Columns [3]–[8] contain employee identifiers as 'Initial. Surname' format. The 'Geburtsdatum' (birth date) rows show ISO 8601 timestamps (DOB) aligned under each employee column. All DOB data is embedded within the row structure rather than as separate columns. Names appear as headers only (initial + surname); no dedicated firstName/lastName/fullName columns exist. The core PII is the names (columns 3–8) and their associated birth dates. Due to the non-standard tabular layout (names as headers, DOB embedded in labeled rows), structured column mapping is limited to the employee name identifiers in columns 3–8.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Bilanz.csv
0 rows

File structure

Notes: This is a financial statement document in German with no consistent columnar structure. The data appears to be a balance sheet (Bilanz) showing account balances in Swiss Francs across multiple years. There are no identifiable PII fields present - all values are financial figures, percentages, and account names. The structure is free-form tabular data without personal information.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Daten.csv
0 rows

File structure

Notes: The file is free-form text with no consistent delimiter structure. It contains financial records and annual statements with no identifiable PII fields such as names, emails, or addresses. The content appears to be financial report headers and dates, not customer or employee personal data.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Detail_zu_Bi-Er.csv
0 rows

File structure

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

Notes: This file is purely financial/accounting data (balance sheet and profit/loss positions) with no personal or identifiable information. All columns contain numerical financial figures, account titles, and fiscal year periods. No PII fields (email, phone, name, address, etc.) are present. Therefore, no columns map to PII fields.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__EDV-Bi.csv
0 rows

File structure

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

Notes: This file contains only financial/accounting data (account numbers, institution names, and monetary values across years). No personal identifiers (PII) are present. All columns represent internal corporate financial records from Zynex AG, Volketswil — no emails, names, addresses, or other PII fields.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__EDV-ER.csv
0 rows

File structure

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

Notes: This is purely financial accounting data from Zynex AG (Swiss web hosting company) showing annual profit/loss figures from 2012-2024. No personal identifiers (names, emails, addresses, etc.) are present. All columns contain numeric financial figures, account codes, or static text like 'Nachtrag' (German for 'supplement'). Per breach context, this is internal financial records with no PII.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Erfolgsrg.csv
0 rows

File structure

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

Notes: This is a financial statement file (Erfolgsrechnung) with no personal identifiable information (PII). All columns contain financial data, years, percentages, and company identifiers. No PII fields (email, phone, name, address, etc.) are present. The file appears to be an annual financial report for Zynex AG in Volketswil, Switzerland, showing profit/loss statements over multiple years.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Geldflussrg.csv
0 rows

File structure

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

Notes: This is a financial statement document (Geldflussrechnung - Cash Flow Statement) with no personal identifiable information. Columns contain only financial figures, percentages, and company name (Zynex AG). No PII fields present.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Gewinnverw_.csv
0 rows

File structure

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

Notes: This file contains purely financial and corporate data from Zynex AG, Volketswil — annual financial statements, balance sheets, and corporate reserve figures. No personal identifiers (names, emails, addresses, etc.) are present. Columns are years (2010–2024) and financial line items (reserves, capital, etc.). All columns are skipped per exclusion rules (financial/transactional data).

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Hardware_RZ.csv
0 rows

File structure

Notes: This is a free-form financial data file with no consistent column structure. The content appears to be financial records (balance sheet values, depreciation) in German with no identifiable PII fields. The data contains numeric values, financial terms, and timestamps but no personal information such as names, addresses, emails, or phone numbers. The format is unstructured and lacks any repeated column pattern or header.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Pendenzen.csv
0 rows

File structure

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

Notes: The first 50 rows appear to be only header rows or metadata. The actual data structure with PII columns is not visible in this sample. The visible lines contain only German text describing work status and customer prepayments, with no actual PII fields present. Further rows likely contain the actual PII data.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Pers.-Vers_2024.csv
0 rows

File structure

Notes: The file is a free-form text file containing financial records and insurance data with no consistent columnar structure. It includes headers and financial calculations but does not contain any personal PII fields like names, emails, or addresses. The data appears to be Swiss insurance and payroll calculations, with no identifiable personal information in the first 50 rows.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__Plan_prod_Std.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure or delimiters. It contains structured tables with financial data but lacks identifiable PII columns like names, addresses, or contact details. The data appears to be internal corporate financial records and does not contain personal identifiable information in a structured format.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__St_Wert.csv
0 rows

File structure

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

Notes: This is a financial statement file with no PII columns. All columns contain financial data, years, dates, and calculations related to corporate valuation and tax assessments. No personal identifiable information (PII) fields such as names, addresses, emails, phone numbers, etc. are present.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie___berst_2022.csv
0 rows

File structure

Notes: This is not a structured delimited file. The rows are free-form text with no consistent delimiter or column structure. The data appears to be German-language financial and HR records from Zynex AG, with employee names embedded in the text (e.g., "Brunner Mark", "Leisi Martin"). However, there is no consistent columnar format to map — each line contains different data types and structures, including employee names, hours, salaries, and financial figures. While names are present, they are not in a structured column format. The file should be processed as unstructured text for extraction of names and other PII using a free-text parser.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie___berstd_2018.csv
0 rows

File structure

Notes: This is a free-form unstructured document containing Swiss corporate financial records from Zynex AG. The data appears to be in German and includes employee compensation details, overtime, and year-end balances. There are no consistent columns or delimiters — each line represents a different type of financial metric or header. No PII fields (names, addresses, etc.) are visible in this sample; the 'Name' entries appear to be sample employee names used for illustration rather than actual breach data. Given the unstructured nature and absence of repeated PII patterns, this file should be processed as unstructured text.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie___berstd_2020.csv
1 column13 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] headerless but values are full names like 'Brunner Mark', 'Leisi Martin'

Notes: This is a Swiss payroll/administrative document (Zynex AG, Volketswil) with employee names and compensation data. Only column 0 contains PII (full names). All other columns contain employment metrics, salary components, and dates (non-PII). No emails, phones, or addresses are present.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie___berstd_2021.csv
0 rows

File structure

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

Notes: This file contains corporate financial records for Zynex AG, with no personal identifiable information (PII). Columns appear to represent internal accounting codes, numeric values, and financial terms in German. No emails, phone numbers, names, addresses, or other PII fields are present. The values are purely organizational/financial data (e.g., 'Überstunden- und Ferienguthaben', numeric hours, salary components, dates in ISO format). Therefore, no columns map to PII fields.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie___berstd_2023.csv
0 rows

File structure

Notes: This is an unstructured free-form text file containing corporate financial records and internal notes from Zynex AG. There is no consistent delimiter or column structure across the rows, and the content appears to be a mix of financial data, descriptions, and names. The values do not form a structured tabular format suitable for column mapping. The presence of names like 'Brunner Mark' and 'Leisi Martin' does not constitute a structured dataset but rather free-form text.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie___bertsd_2024.csv
0 rows

File structure

Notes: This is not a structured dataset but appears to be free-form text containing financial and employee records from Zynex AG. The data includes employee names (e.g., 'Brunner Mark', 'Leisi Martin') but lacks consistent columnar structure across rows. Given the unstructured nature and mixed content (descriptions, calculations, dates), this should be processed as unstructured text. No clear PII columns can be mapped due to inconsistent formatting.

finanzen__Abschluesse__Abschluss_2024__v2__JRG_2024_Zynex_aktuell_-_Kopie__ang_Arb__Liste.csv
0 rows

File structure

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

Notes: This file appears to be financial records without any PII columns. Columns contain company project names, empty strings, years, dates, and financial figures. No personal identifiers such as names, emails, phone numbers, addresses, or other PII are present in the sample rows. All columns either contain internal corporate data, timestamps, or empty values.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Angef_Arb.csv
0 rows

File structure

Notes: This is a free-form financial report from Zynex AG with no consistent columnar structure. It contains corporate financial data (accounts receivable, prepaid customer amounts, net revenue) but no personal PII fields. All values appear to be internal accounting codes, monetary amounts in CHF, and date stamps for fiscal year-end reporting. No emails, names, or addresses are present in the visible portion.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Angef_Arb_det.csv
0 rows

File structure

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

Notes: This file contains only transaction/project accounting data (invoices, payments, project codes). No personal identifiers (PII) such as names, emails, or addresses are present. All columns are financial or internal tracking fields, which per rules must be skipped. Therefore, no PII columns to map.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Anhang.csv
0 rows

File structure

Notes: This is free-form text (prose) with no consistent columnar structure. The lines are narrative paragraphs about financial statements and accounting procedures from a Swiss corporate report, not structured data containing discrete PII fields. No column mapping is possible.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Anlagesp.csv
0 rows

File structure

Notes: This is an unstructured financial report document from Zynex AG. The data contains accounting entries in German (e.g., 'Anlagevermögen', 'Bilanzwert') with no personal identifiable information (PII). There are no columns with structured personal data like names, addresses, emails, or phone numbers. The content is purely financial and corporate in nature, with entries like asset values, depreciation calculations, and balance sheet items.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Aufteilung_Bonus.csv
0 rows

File structure

Notes: This file is purely financial accounting data (Swiss Francs, vehicle maintenance, insurance, depreciation, bonuses, etc.) with no personal identifiers. No column structure exists; it's a free-form financial statement table in German. No PII fields are present.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Aufteilung_Gewinn.csv
0 rows

File structure

Notes: This file is free-form financial reporting text in German, not a structured data file. It contains financial statements and balance sheet data for Zynex AG, a Swiss web hosting company, showing profit/loss calculations, reserves, dividends, and year-over-year comparisons from 2018–2023. No personal PII is present — only corporate financial aggregates and percentages.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__BVG-Lohn_2019.csv
0 rows

File structure

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

Notes: This file is purely financial records with no personal identifying information. Columns represent employee names but values are only initials or generic labels (M. Brunner, M. Leisi, etc.), not full names. All other columns contain salary components, percentages, and totals in CHF with no PII fields present. No emails, phone numbers, addresses, DOB, SSN, or other PII detected.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__BVG-Lohn_2020.csv
7 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3firstNamehighColumn 3 contains abbreviated first names: 'M. Brunner', 'M. Leisi', 'R. Wellinger', 'D. Rosso', 'P. Windhofer', 'K. Parizek', 'D. Poulton' — initials paired with surnames
4firstNamehighColumn 4 continues the pattern of first name initials/abbreviations across multiple years
5firstNamehighColumn 5 continues first name abbreviations (R. Wellinger, D. Poulton, etc.)
6firstNamehighColumn 6 continues first name abbreviations
7firstNamehighColumn 7 continues first name abbreviations
8firstNamehighColumn 8 continues first name abbreviations
9firstNamehighColumn 9 continues first name abbreviations (K. Parizek in 2021 section)

Notes: This is an internal payroll/HR document from Zynex containing employee salary records spanning 2015–2021. Employee names appear as 'Initials. LastName' format in columns 3–9 (varying by year). The row labeled 'Geburtsdatum' (birth date in German) contains ISO 8601 formatted dates (YYYY-MM-DDTHH:MM:SS.000Z) in the same columns, confirming these are employee-level PII. The document structure repeats annually with salary components (Grundlohn, Überstunden, Bonus, etc.), age, and pension calculations (BVG-Lohn, Altersgutschriften). All financial amounts are in Swiss Francs (CHF). No structured address, phone, email, or SSN data is present in this sample. The initials+surname pattern and corresponding birth dates are the only PII captured here; full first names are abbreviated and cannot be fully recovered from this format alone.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__BVG-Lohn_2022.csv
6 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3firstNamehigh[3] Values are employee first names (M. Brunner, M. Leisi, R. Wellinger, D. Rosso, P. Windhofer, K. Wellinger, K. Parizek, D. Poulton)
4firstNamehigh[4] Values are employee first names (M. Brunner, M. Leisi, R. Wellinger, D. Rosso, P. Windhofer, K. Wellinger, K. Parizek, D. Poulton)
5firstNamehigh[5] Values are employee first names (R. Wellinger, D. Poulton, D. Rosso, P. Windhofer)
6firstNamehigh[6] Values are employee first names (D. Rosso, R. Wellinger)
7firstNamehigh[7] Values are employee first names (P. Windhofer, K. Wellinger, K. Parizek)
8firstNamehigh[8] Values are employee first names (K. Wellinger, K. Parizek)

Notes: This file contains internal payroll/HR records from Zynex for 2015–2022. Column headers are absent; only row labels (Grundlohn, Überstunden, Bonus, Geburtsdatum, Alter, etc.) are present in columns 0–2. Employee names appear as abbreviated initials + surnames across columns 3–8, corresponding to names M. Brunner, M. Leisi, R. Wellinger, D. Rosso, P. Windhofer, K. Wellinger, K. Parizek, and D. Poulton. The row labeled 'Geburtsdatum' contains ISO 8601 dates of birth in columns 3–8. Financial data (salaries, bonuses, contributions) is present but mapped as skip (financial/transactional). Name columns cannot be reliably split into lastName/firstName given only initials; both are treated as firstName. Birth dates visible in Geburtsdatum rows but no consistent column index—dates span columns 3–8 variably by year, making column-level mapping imprecise for dob. To extract dob reliably, content-based extraction (Geburtsdatum row parsing) is recommended.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Bilanz.csv
0 rows

File structure

Notes: This is a financial statement document (balance sheet) with merged headers and no personal identifiable information (PII). Columns are not clearly delimited, and values are purely financial figures and percentages. No PII fields such as names, emails, addresses, etc., are present.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Daten.csv
0 rows

File structure

Notes: The provided data appears to be unstructured financial/prose text containing financial year-end statements (Abschluss) and year references. There is no consistent columnar structure with repeating fields. The lines represent financial report headings and timestamps rather than delimited records. No PII is present in this sample.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Detail_zu_Bi-Er.csv
0 rows

File structure

Notes: The provided data is a financial statement/report in German with no consistent column structure or personal identifiers. It contains account titles, fiscal year periods, and financial figures, but no PII fields like names, emails, or addresses. This is typical of corporate financial documentation rather than customer or employee records.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__EDV-Bi.csv
0 rows

File structure

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

Notes: This is purely financial accounting data (Zynex AG corporate records) with no PII fields. Columns represent account codes (0), entity name (1), and financial figures across years (3-31). No personal identifiers present.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__EDV-ER.csv
0 rows

File structure

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

Notes: This file contains only financial/accounting data (revenue figures, balance sheet lines) with no personal identifiers. All columns represent accounting codes, account descriptions, and financial amounts across years. No PII fields present.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Erfolgsrg.csv
0 rows

File structure

Notes: This is a financial statement (Erfolgsrechnung) showing revenue data for Zynex AG across multiple years. The data is purely financial — revenue figures, percentages, and date ranges — with no personal identifiable information. No names, addresses, emails, or other PII fields are present. The structure is tabular but all columns contain only financial metrics, not personal data. Therefore, no PII columns to map.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Geldflussrg.csv
0 rows

File structure

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

Notes: This is a financial statement file (Geldflussrechnung - cash flow statement) with no personal identifiable information. Columns contain only financial figures, percentages, and company names (Zynex AG). No PII fields are present.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Gewinnverw_.csv
0 rows

File structure

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

Notes: This is a financial statement document, not a dataset with personal identifiers. Columns contain financial data (years, amounts, balance sheet items), but no personal PII fields (names, emails, addresses, etc.). All columns map to financial/transactional data and should be skipped per exclusion rules. No PII columns present.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Hardware_RZ.csv
0 rows

File structure

Notes: free-form financial statements with no consistent delimiter or row structure. Contains financial data columns but no PII. No identifiable personal data present in the sample.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Pendenzen.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent columnar structure. The first two rows appear to be German-language financial document headers: 'Angefangene Arbeiten' (Started Work) and 'Vorauszahlunge von Kunden' (Customer Prepayments). There is no identifiable PII in these headers, and the data lacks any structured format with columns or delimiters.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Pers.-Vers_2024.csv
0 rows

File structure

Notes: This file is a free-form financial statement with no consistent columnar structure. It contains accounting entries, insurance contributions, and financial totals rather than personal data fields. There are no identifiable PII columns in the sample data. The format appears to be a raw text export of financial records without any structured personal information fields.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__Plan_prod_Std.csv
0 rows

File structure

Notes: This is a free-form financial/operational report table with no consistent columnar structure. The content appears to be a Swiss corporate financial summary for Zynex AG (Volketswil) showing staffing hours, bonuses, salaries, and revenue figures across years 2008–2017. No personal identifiers (PII) are present; all values are aggregated financial data, percentages, and totals. The format lacks delimiters, headers, or repeated row patterns required for structured parsing.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__St_Wert.csv
0 rows

File structure

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

Notes: This file is a financial statement document (Zynex AG) with no personal identifiable information (PII). All columns contain corporate financial data, years, monetary values, and internal accounting metrics. No PII fields (email, phone, name, address, etc.) are present. Therefore, the columns object is empty.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell___berst_2022.csv
0 rows

File structure

Notes: This file is free-form text with no consistent column structure. It contains unstructured German financial records from Zynex AG, including employee names and financial data, but lacks a consistent delimiter or row structure across lines. The sample shows lines with varying content and no shared delimiter pattern.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell___berstd_2018.csv
0 rows

File structure

Notes: This is an unstructured financial report with no consistent columnar structure. The data appears to be a mix of text descriptions and numerical financial figures related to employee compensation and year-end balances. There are no identifiable PII columns in this dataset; it contains only corporate financial metrics and employee-related calculations without personal identifiers.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell___berstd_2020.csv
0 rows

File structure

Notes: This is not a structured tabular file. The sample rows show unstructured text with German phrases and numerical data representing corporate financial metrics (overtime, salary, etc.). There are no consistent columns or delimiters, and the content appears to be internal financial records rather than customer PII. No PII fields are present in this dataset.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell___berstd_2021.csv
1 column14 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Name', values are full names like 'Brunner Mark', 'Leisi Martin'

Notes: This is a structured corporate financial file in German, not containing typical PII fields like email, phone, or SSN. Only column 0 contains full names which are PII. All other columns are internal financial metrics (hours, salaries, balances) and timestamps — these are skipped per rules. No unstructured text present.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell___berstd_2023.csv
0 rows

File structure

Notes: This is not structured tabular data but free-form text with employee names (Brunner Mark, Leisi Martin) and internal corporate financial records. The data appears to be in German with no consistent columnar structure across rows. There are no email or phone numbers visible, and the content is corporate financial metadata rather than customer PII. Given the unstructured nature, no column mapping is possible.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell___bertsd_2024.csv
0 rows

File structure

Notes: This is an unstructured financial document from Zynex AG, Volketswil, containing internal corporate financial records (overtime, salaries, bonuses, etc.). The data is in German and uses Swiss Francs (CHF). There are no personal PII fields like names, emails, or addresses. The document appears to be a financial summary sheet with no identifiable individuals. The sample rows contain financial metrics and calculations rather than personal data.

finanzen__Abschluesse__Abschluss_2025__JRG_2025_Zynex_aktuell__ang_Arb__Liste.csv
0 rows

File structure

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

Notes: This is an unstructured corporate financial record file from Zynex AG. Columns contain only company project names, empty strings, years, monetary amounts (CHF), and ISO timestamps. No personal identifiers (PII) are present. All values are corporate operational data (project names, financial figures, dates). No emails, phone numbers, names, addresses, or other PII fields are visible in the sample.

finanzen__Abschluesse__Abschluss_2025__tickets-angef-arbeiten-2025__Tabelle1.csv
0 rows

File structure

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

Notes: No PII columns detected. File contains internal project tracking data with codes (VXRITTER-*), roles (KP/DR/PW), dates, hours, and task descriptions. No personal information present.

finanzen__Abschluesse__Abschluss_2025__tickets-angef-arbeiten-2025__Tabelle2.csv
0 rows

File structure

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

Notes: This is a structured CSV file but contains no PII columns. All visible columns appear to be internal project tracking data (IDs, codes, dates, amounts, descriptions). No personal identifiers, emails, phone numbers, or addresses are present in the sample. The data appears to be internal financial/project records from Zynex's ERP system with no customer PII exposed in these rows.

finanzen__Abschluesse__Abschluss_2025__tickets-angef-arbeiten-2025__Tabelle4.csv
0 rows

File structure

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

Notes: This file contains no PII columns. All columns appear to be internal corporate identifiers, layout settings, and numeric values unrelated to personal data. No emails, phone numbers, names, addresses, or other PII fields are present.

finanzen__Abschluesse__Abschluss_2025__tickets-angef-arbeiten-2025__Tabelle5.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or structure. Lines contain project codes, dates, amounts, and activity descriptions in German. No identifiable PII fields are present, and the format is unstructured prose rather than tabular data. The final line with a single number appears to be a total sum, not part of a structured record.

finanzen__Abschluesse__Abschluss_2025__tickets-angef-arbeiten-2025__Tabelle6.csv
0 rows

File structure

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

Notes: No PII fields detected. The data appears to be internal corporate records containing only project codes (VXSMITH-5, VXSMITH-28), access permissions (RW), dates, numerical values (hours or costs), and German-language meeting notes. No personal identifiers such as names, emails, addresses, or other PII are present in the visible columns. All columns represent internal operational data (project tracking, time logging, meeting summaries) and fall under the exclusion rules for internal IDs, timestamps, and transactional/corporate data.

finanzen__Abschluesse__Abschluss_2025__tickets-angef-arbeiten-2025__abschluss-2021.csv
0 rows

File structure

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

Notes: This is not PII data; it contains only business transaction records with customer/project names that are not personal identifiers (company names or project codes). No email, phone, address, SSN, DOB, or other personal PII fields are present. The columns represent corporate financial data: Kunde / Projekt (customer/project), Support / Projekt (support type), hours performed, monetary amounts, payment references, and notes. All values are business-related financial metrics, not personal identifiers.

finanzen__Abschluesse__Abschluss_2025__tickets-angef-arbeiten-2025__abschluss-2022.csv
0 rows

File structure

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

Notes: This is a financial invoice/statement file from Zynex with corporate client names and amounts. No personal PII fields (email, phone, DOB, etc.) are present. Columns contain project names, amounts, dates, and internal reference numbers — all business/corporate data. Customer names are company entities (e.g., 'Greiner Getränke', 'H.J. Langendorf', 'Smith & Smith AG'), not individual person PII. Per exclusion rules, company/business names are skipped.

finanzen__Abschluesse__Abschluss_2025__tickets-angef-arbeiten-2025__abschluss-2023.csv
0 rows

File structure

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

Notes: This file contains only internal financial records and project management data (invoices, project names, amounts, dates). No PII fields are present. All columns are internal business identifiers, amounts, or status flags. No emails, phone numbers, names, addresses, DOB, SSN, or other PII are visible in the first 50 rows.

finanzen__Abschluesse__Abschluss_2025__tickets-angef-arbeiten-2025__abschluss-2024.csv
0 rows

File structure

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

Notes: This is a financial ledger with no PII fields. Columns contain project names, amounts, dates, and internal codes. No emails, phone numbers, names, or other PII are present. All columns map to skip per rules (company/project names, financial amounts, internal reference numbers, timestamps).

finanzen__Abschluesse__Abschluss_2025__tickets-angef-arbeiten-2025__abschluss-2025.csv
0 rows

File structure

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

Notes: The file contains corporate financial records (project invoices, accounts) with no personal PII fields. Columns describe project names (Swiss companies), invoice amounts, payment dates, and internal accounting codes. No emails, names, addresses, or other PII are present.

finanzen__Abschluesse__Abschluss_2025__tickets-angef-arbeiten-2025__angef-arbeiten.csv
0 rows

File structure

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

Notes: The provided data is purely transactional and financial records without any personal identifiable information (PII). All columns contain company names, invoice numbers, amounts, dates, and project codes — none map to email, phone, dob, names, addresses, SSN, password, username, gender, suffix, or facebookId. Therefore, no PII columns exist to map.

finanzen__Abschluesse__Abschluss_2025__tickets-angef-arbeiten-2025__jira-tickets.csv
0 rows

File structure

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

Notes: This is a financial/project tracking CSV with no PII fields. Columns contain project codes (VX...), chargeable hours, amounts in CHF, and internal tracking codes. No names, emails, addresses, or other PII appear in the first 50 rows.

finanzen__Abschluesse__Anzahlungen__Tabelle1.csv
0 rows

File structure

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

Notes: This is purely financial/accounting data with internal reference numbers (Bel. Nr.), dates (Datum), transaction texts (Text), amounts (Betrag), balances (Saldo), and payment types (Art). No personal identifiers or PII fields are present. All columns map to internal accounting records or empty fields.

finanzen__FaktNT__Zynex.m03__Abolauf_vom_18.03.2004.txt
0 rows

File structure

Notes: This is a free-form text document containing subscription cancellation details from 2004 in German. No structured columns exist — it is prose with no consistent delimiter, variable line lengths, and embedded dates rather than PII. No emails/phones visible. Unstructured handling is appropriate.

finanzen__FaktNT__Zynex.m03__Produktionslauf.txt
1 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m03__Produktionslauf__01.09.2003__13.27_.txt
6 rows

File structure

Notes: The file is free-form text with no consistent column structure. It contains embedded customer website URLs (www.hanbos.ch, www.stuessiautomobile.ch, www.marag.ch) and invoice generation details, but lacks a tabular format. This is typical of ERP document generation logs rather than structured PII records.

finanzen__FaktNT__Zynex.m03__Produktionslauf__05.05.2003__15.18_.txt
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m03__Produktionslauf__06.05.2003__15.34_.txt
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m03__Produktionslauf__06.06.2003__15.58_.txt
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be German-language financial/production log with internal codes and dates, but no identifiable PII fields or repeated columnar patterns. Contains internal reference numbers (Abonummer) but these are not personal identifiers. No emails, phones, or names visible.

finanzen__FaktNT__Zynex.m03__Produktionslauf__06.06.2003__16.05_.txt
2 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m03__Produktionslauf__06.10.2003__08.49_.txt
22 rows

File structure

Notes: The provided content is free-form text documenting invoice generation procedures and subscription details for Zynex customers. It lacks any consistent delimiter or tabular structure across lines, with each line representing different procedural steps or data entries. While it contains customer domain names (e.g., www.dentalesthetics.ch, www.scotoni.ch, www.procol-ag.ch), these are embedded within prose rather than in structured columns, matching the conditions for unstructured data processing.

finanzen__FaktNT__Zynex.m03__Produktionslauf__06.10.2003__09.28_.txt
1 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m03__Produktionslauf__08.09.2003__15.20_.txt
0 rows

File structure

Notes: Free-form text with no consistent delimiter structure. Contains German-language financial/procurement records from Zynex's ERP system with no identifiable PII fields in the first 50 rows. Sample shows invoice generation logic, product codes, pricing, and VAT codes rather than personal customer data.

finanzen__FaktNT__Zynex.m03__Produktionslauf__09.05.2003__15.30_.txt
0 rows

File structure

Notes: This is a free-form text document containing internal corporate financial records with no consistent columnar structure. The text appears to be German-language accounting/production documentation for an invoice generation process from Zynex. No structured PII fields are present in the sample; values shown are internal codes, dates, and financial terms rather than personal data.

finanzen__FaktNT__Zynex.m03__Produktionslauf__10.01.2003__10.41_.txt
8 rows

File structure

Notes: free-form text with embedded customer account numbers (Abonummer) but no consistent columnar structure; contains invoice generation instructions and account codes rather than actual customer PII

finanzen__FaktNT__Zynex.m03__Produktionslauf__12.02.2003__10.27_.txt
0 rows

File structure

Notes: This is a free-form text document containing German-language internal corporate notes and production run selections for Zynex. No consistent column structure exists across lines — it's a mixture of headers, error messages, date stamps, and procedural notes. Though it contains internal account numbers (Abonummer), these are not typical PII fields and the document lacks any structured rows with personal identifiers like names, emails, or addresses. The format is unstructured prose, not CSV or tabular data.

finanzen__FaktNT__Zynex.m03__Produktionslauf__12.02.2003__10.37_.txt
12 rows

File structure

Notes: The file is free-form text (German financial document generation template) with no consistent columnar structure. Contains embedded customer website domains (www.centrachem.ch, www.buehrertreuhand.ch) and date patterns, but lacks any row-based delimiter or repeating field positions across lines. Meets unstructured criteria: no consistent delimiter, variable line shapes, and visible identifiers.

finanzen__FaktNT__Zynex.m03__Produktionslauf__15.07.2003__13.38_.txt
20 rows

File structure

Notes: Free-form text with no consistent columnar structure. Contains German-language financial/invoicing records for Zynex subscriptions (customer websites, dates, amounts). No repeated delimiter patterns or field positions across lines. Contains embedded customer website URLs (www.beco-ag.ch, www.caviola-ag.ch, www.wittich-weine.ch) and dates, but not structured tabular data.

finanzen__FaktNT__Zynex.m03__Produktionslauf__23.06.2003__15.10_.txt
0 rows

File structure

Notes: The provided text is free-form German prose describing internal corporate accounting processes and invoice generation procedures. It contains no structured columns or consistent delimiter patterns. While it references financial operations and customer data, it does not expose any actual PII such as names, emails, or addresses in the sample provided.

finanzen__FaktNT__Zynex.m03__Produktionslauf__23.06.2003__15.11_.txt
10 rows

File structure

Notes: Free-form German-language text document describing invoice generation procedures for customer subscriptions. Contains no structured columns, but includes embedded customer website URLs (www.sensirion.com, www.gnatho-europe.com, www.tceulach.ch) which qualify as PII under unstructured processing rules. Document appears to be procedural rather than containing direct customer records.

finanzen__FaktNT__Zynex.m03__Produktionslauf__26.02.2003__09.17_.txt
0 rows

File structure

Notes: The provided data is free-form text with no consistent columnar structure. It appears to be a German-language invoice generation log from Zynex, showing subscription billing details for various accounts (mrcatering.ch, 180kmh.ch, dedic.ch). The text contains business logic and document generation instructions rather than structured tabular data with PII fields. While domain names are present, they are embedded within prose and not presented in a delimited format.

finanzen__FaktNT__Zynex.m03__Produktionslauf__26.03.2003__14.45_.txt
4 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m03__Produktionslauf__26.03.2003__16.45_.txt
0 rows

File structure

Notes: The provided data is free-form text (German prose) describing internal corporate financial processing instructions for an invoice system. It contains no consistent delimiter structure or tabular data. While it references internal codes and invoice generation, it does not contain any actual PII fields in structured columns. The content appears to be procedural documentation rather than breach data containing personal information.

finanzen__FaktNT__Zynex.m03__Produktionslauf__30.01.2003__17.26_.txt
0 rows

File structure

Notes: The provided text is free-form German prose describing internal accounting processes and subscription management for Zynex corporate records. There is no consistent delimiter structure or repeating column pattern. The content appears to be procedural notes for generating invoices and managing subscription lifecycle dates (start/end periods), not structured PII records. While dates are present (e.g., 30.01.2003), these are business transaction dates rather than personal DOB values. No identifiable personal data fields (names, emails, etc.) are visible in the sample.

finanzen__FaktNT__Zynex.m04__Abolauf_vom_18.01.2004.txt
0 rows

File structure

Notes: File is NOT a delimited data file. It contains German-language prose/notes about a subscription ('Abo') record with metadata fields (dates, subscription number, document template, shipping method, remarks). No structured tabular data with rows of PII records. This is an internal note or form template, not a dataset containing customer/personal information records.

finanzen__FaktNT__Zynex.m04__Abolauf_vom_18.03.2004.txt
0 rows

File structure

Notes: The provided text is unstructured free-form prose (German invoice footer snippet) with no consistent columnar format. It lacks any delimited structure or repeating record pattern. While it contains some financial/timestamp data, there are no visible PII fields like emails, phone numbers, or names in the sample.

finanzen__FaktNT__Zynex.m04__Abolauf_vom_28.06.2004.txt
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m04__Produktionslauf.txt
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m04__Produktionslauf__02.02.2004__15.17_.txt
4 rows

File structure

Notes: The provided file is a free-form German text document detailing invoice generation logic and subscription management for Zynex. It contains procedural code snippets and template placeholders (e.g., $($AboVor01)) but no structured tabular data or PII fields. The content describes internal business processes rather than containing importable records.

finanzen__FaktNT__Zynex.m04__Produktionslauf__03.06.2004__10.46_.txt
31 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FaktNT__Zynex.m04__Produktionslauf__03.09.2004__14.12_.txt
0 rows

File structure

Notes: This is unstructured free-form text containing invoice generation notes and production workflow logs. No consistent columnar structure exists; lines contain German-language invoice processing instructions, dates, and internal codes. Contains no identifiable PII fields in structured format.

finanzen__FaktNT__Zynex.m04__Produktionslauf__03.11.2004__11.18_.txt
2 rows

File structure

Notes: The file is a free-form document with no consistent columnar structure. It appears to be a German-language financial processing log detailing subscription billing and invoice generation for Zynex web hosting services. The text contains no structured data rows, only procedural instructions and transaction metadata. No PII fields are present in this unstructured content.

finanzen__FaktNT__Zynex.m04__Produktionslauf__06.01.2004__13.27_.txt
12 rows

File structure

Notes: File is unstructured free-form text with no consistent columnar structure. Contains German-language invoice generation scripts and subscription management logs from Zynex's FaktNT ERP system, with no actual customer PII present in the first 50 rows.

finanzen__FaktNT__Zynex.m04__Produktionslauf__06.01.2004__14.18_.txt
0 rows

File structure

Notes: Free-form text with no consistent delimiter structure. Contains internal corporate financial records and invoice generation instructions in German, but lacks any tabular format. Visible content includes invoice numbers, dates, customer domains, and financial figures, but no identifiable PII fields in structured columns.

finanzen__FaktNT__Zynex.m04__Produktionslauf__07.10.2004__13.30_.txt
19 rows

File structure

Notes: The provided text is free-form German financial processing output from an ERP system, not a structured CSV/TSV. It contains customer website URLs (www.dentalesthetics.ch, www.procol-ag.ch, www.fininco.com) embedded in the text but lacks consistent delimiters or column headers. No structured PII fields like names, emails, or addresses are present in a tabular format. This is unstructured operational data from the FaktNT ERP system used for invoice generation.

finanzen__FaktNT__Zynex.m04__Produktionslauf__19.03.2004__10.10_.txt
6 rows

File structure

Notes: File is free-form German-language accounting document with no consistent columnar structure. Contains invoice generation details for Zynex subscriptions but lacks tabular format. Embedded website URLs (www.cigarroslatinos.com, www.eggenberger-ag.ch, comtecsolution.ch) are customer domains, not personal PII.

finanzen__FaktNT__Zynex.m04__Produktionslauf__19.03.2004__11.14_.txt
2 rows

File structure

Notes: The provided text is free-form German prose describing invoice generation and subscription management processes. It contains no structured columns — instead, it's a narrative document with subscription IDs (1071, 1108, etc.) and financial details embedded in paragraphs. Since there is no consistent delimiter or column structure, this qualifies as unstructured text with embedded data. The presence of subscription identifiers and dates confirms it meets the unstructured criteria.

finanzen__FaktNT__Zynex.m04__Produktionslauf__21.06.2004__11.02_.txt
2 rows

File structure

Notes: The file is a free-form document containing structured invoice generation instructions and product line items. It shows no consistent columnar layout (varying field names and values across lines) but contains embedded customer website URLs (www.bolerolifestyle.ch, www.elephantclub.ch) and invoice dates. This qualifies as unstructured text with embedded PII-like values, routed for streaming extraction of emails/phones. No actual PII fields (names, emails, etc.) are present in the visible sample.

finanzen__FaktNT__Zynex.m04__Produktionslauf__24.02.2004__15.09_.txt
6 rows

File structure

Notes: Free-form text with embedded customer website URLs but no consistent columnar structure. Contains invoice generation details for Zynex subscriptions with customer domains like www.centrachem.ch, www.fem-innovations.com, and www.aesthetische-chirurgie.ch, but these appear inline within narrative invoice generation instructions rather than in a tabular format.

finanzen__FaktNT__Zynex.m04__Produktionslauf__25.08.2004__10.50_.txt
6 rows

File structure

Notes: Free-form German-language financial document with no consistent delimiter or column structure. Contains invoice generation instructions for Zynex subscriptions with customer website URLs (www.hanbos.ch, www.stuessiautomobile.ch, www.marag.ch) and invoice dates, but lacks tabular format. Mapped as unstructured due to prose-style layout and variable line lengths.

finanzen__FaktNT__Zynex.m04__Produktionslauf__27.07.2004__10.51_.txt
1 rows

File structure

Notes: The provided data is free-form text with no consistent delimiter or structured columns. It appears to be German-language financial/invoicing documentation from a Swiss web hosting company, containing invoice generation details, dates, product descriptions, pricing, and tax information. No PII fields are visible in this sample, but the unstructured nature prevents column mapping.

finanzen__FaktNT__Zynex.m04__Produktionslauf__28.07.2004__17.27_.txt
0 rows

File structure

Notes: This is a free-form text document containing German-language accounting and subscription management notes. There is no consistent columnar structure; instead, it's a series of procedural steps and financial annotations for generating invoices and managing subscriptions. No identifiable PII fields are present in this sample.

finanzen__FaktNT__Zynex.m04__Produktionslauf__29.04.2004__14.50_.txt
0 rows

File structure

Notes: The provided text is a German-language invoice/production run document from Zynex's ERP system. It contains no structured columns — instead it's a free-form financial document with invoice numbers, dates, amounts, and customer references (bademio.ch). There are no column headers or consistent delimiters; this is a narrative financial record, not a CSV or table. Per rules, unstructured files with no row structure must return empty columns object.

finanzen__FaktNT__Zynex.m04__Produktionslauf__30.07.2004__14.08_.txt
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m05__Produktionslauf.txt
4 rows

File structure

Notes: The provided data is unstructured free-form text describing invoice generation procedures for Zynex subscriptions. It contains no consistent column structure or delimited records — instead showing procedural steps and sample invoice snippets. Though it contains a few domain names (www.e-personal.ch, www.blumen-mueller.ch, hoerberatung.ch), these appear embedded within narrative text rather than in a tabular format. Per the unstructured rules, this qualifies as free-form text with embedded PII that should be processed by a streaming email/phone extractor.

finanzen__FaktNT__Zynex.m05__Produktionslauf__01.06.2005__13.37_.txt
33 rows

File structure

Notes: The provided text is free-form prose describing invoice generation processes and subscription management. It contains no consistent columnar structure or delimited data. Instead, it shows procedural steps for creating documents based on subscription numbers, with placeholder variables and static text values. There are no identifiable PII fields present in any structured format. The data appears to be internal business logic documentation rather than customer records.

finanzen__FaktNT__Zynex.m05__Produktionslauf__03.08.2005__08.32_.txt
4 rows

File structure

Notes: Free-form text with no consistent delimiter or column structure. Contains embedded customer website URLs (www.stuessiautomobile.ch, www.marag.ch, weinhalle.ch) and invoice details, but lacks tabular format. Routed for unstructured processing.

finanzen__FaktNT__Zynex.m05__Produktionslauf__04.03.2005__10.24_.txt
6 rows

File structure

Notes: The file is free-form text with no consistent delimiter structure. Contains embedded customer domain names (www.cigarroslatinos.com, www.eggenberger-ag.ch, comtecsolution.ch) and subscription details, but lacks tabular format required for column mapping. This qualifies as unstructured data per the opt-out rules.

finanzen__FaktNT__Zynex.m05__Produktionslauf__05.01.2005__14.51_.txt
14 rows

File structure

Notes: The provided text is free-form German prose describing invoice generation procedures and subscription details for Zynex hosting services. It contains no structured columns or consistent delimiter patterns — instead showing procedural steps, date ranges, subscription IDs, and financial values in narrative form. Though it contains embedded data points like URLs (www.b-m-p.ch, www.fininco.com) and subscription numbers (1101, 1040, etc.), these appear inline within descriptive sentences without columnar structure. This qualifies as unstructured text per the opt-out rules.

finanzen__FaktNT__Zynex.m05__Produktionslauf__05.01.2005__15.40_.txt
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m05__Produktionslauf__06.01.2005__11.03_.txt
0 rows

File structure

Notes: The provided text is free-form German prose describing internal corporate financial processes for subscription management and invoice generation. No consistent tabular structure or delimited columns exist. While it contains business references (subscription numbers, dates, financial codes), it does not contain any identifiable PII fields such as names, emails, or addresses. The unstructured nature of the content meets all criteria for unstructured opt-out: no consistent delimiter, variable line shapes, and absence of embedded searchable PII.

finanzen__FaktNT__Zynex.m05__Produktionslauf__09.02.2005__09.44_.txt
9 rows

File structure

Notes: The provided data is unstructured free-form text representing financial invoice generation logic in German. It contains no consistent columnar structure, only procedural code-like descriptions of invoice creation for Zynex hosting subscriptions. While it contains domain data (dates, amounts, URLs), there are no identifiable PII columns or repeated patterns to map. The text is purely operational logic and lacks any tabular format with repeated records.

finanzen__FaktNT__Zynex.m05__Produktionslauf__09.02.2005__10.00_.txt
0 rows

File structure

Notes: The provided text is free-form German-language corporate accounting/production documentation from Zynex. It contains no structured columns, only narrative descriptions of invoice generation, subscription management, and production workflow. There are no identifiable PII fields (emails, names, addresses, etc.) in this sample. The content appears to be internal business process logs rather than customer data.

finanzen__FaktNT__Zynex.m05__Produktionslauf__09.02.2005__10.34_.txt
0 rows

File structure

Notes: The provided text is free-form German prose describing invoice generation and subscription management processes for Zynex. It contains no structured columns, only narrative text about business operations. No PII fields are present in a columnar format.

finanzen__FaktNT__Zynex.m05__Produktionslauf__09.06.2005__17.23_.txt
0 rows

File structure

Notes: The provided data is free-form text representing internal corporate financial records and production workflows. It contains no consistent delimiter structure, no repeating row patterns, and no identifiable column headers. The text includes operational notes, invoice generation details, and subscription management instructions but lacks any structured tabular data with identifiable PII columns. While it contains business data (dates, invoice numbers, subscription codes), it does not contain any personal identifiable information in a structured format.

finanzen__FaktNT__Zynex.m05__Produktionslauf__15.07.2005__13.24_.txt
0 rows

File structure

Notes: File is free-form German-language financial documentation with no consistent columnar structure. Contains embedded invoice details and subscription line items but lacks delimited fields. No identifiable PII columns present in structured format.

finanzen__FaktNT__Zynex.m05__Produktionslauf__16.09.2005__14.33_.txt
0 rows

File structure

Notes: The provided text is free-form German prose describing invoice generation and subscription management procedures. No consistent delimiter structure exists across lines, and the content appears to be internal corporate documentation rather than structured PII records. Though no explicit emails or phone numbers are visible in this snippet, the unstructured nature and lack of columnar data mandate routing through streaming extraction.

finanzen__FaktNT__Zynex.m05__Produktionslauf__27.06.2005__14.46_.txt
0 rows

File structure

Notes: The provided data is free-form text with no consistent delimiter structure. It appears to be internal corporate documentation in German, discussing subscription management, invoice generation, and financial processing for Zynex's customer accounts. There are no structured columns to map, and while there may be embedded PII-like values (e.g., 'redbeansandrice.ch'), the lack of a consistent row structure means we must treat this as unstructured text for processing.

finanzen__FaktNT__Zynex.m05__Produktionslauf__27.06.2005__16.34_.txt
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains German-language invoice/production notes with embedded customer domains (marketing-trade.com, inserateforum.ch) but no structured columns

finanzen__FaktNT__Zynex.m05__Produktionslauf__28.06.2005__11.28_.txt
0 rows

File structure

Notes: This is unstructured free-form text (German business document) with no consistent column structure or delimiter. Contains internal corporate financial records from Zynex, but no identifiable PII fields in structured columns. The content appears to be an internal invoice generation log for subscription number 1149 dated June 28, 2005, with no personal customer data exposed in this snippet.

finanzen__FaktNT__Zynex.m05__Produktionslauf__29.09.2005__09.47_.txt
12 rows

File structure

Notes: Free-form German text document describing invoice generation process and subscription details. Contains no structured columns; instead, it's procedural documentation with embedded website URLs (www.dentalesthetics.ch, www.procol-ag.ch, www.fz-elektroag.ch) and dates. No PII fields are present in a columnar format. This qualifies as unstructured text per the rules.

finanzen__FaktNT__Zynex.m05__Produktionslauf__30.03.2005__15.12_.txt
2 rows

File structure

Notes: The file is free-form text with no consistent delimiter structure. It contains German-language financial/invoicing prose with embedded customer domain names (bademio.ch, wyhus.ch, bolerolifestyle.ch) and internal invoice codes, but no actual PII fields like names, emails, or addresses. The content describes invoice generation logic for Swiss SME subscriptions to Zynex web hosting services, using internal reference numbers and dates rather than customer PII. No structured columns exist to map.

finanzen__FaktNT__Zynex.m05__Produktionslauf__31.08.2005__11.10_.txt
2 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m05__Produktionslauf__31.08.2005__15.14_.txt
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The file appears to be a German-language financial/document generation log from Zynex's FaktNT ERP system, showing subscription billing details for a Swiss SME customer (gruermann.ch). No columnar PII is present, though the customer domain 'gruermann.ch' appears as part of invoice line items. Per rules, unstructured files with no row structure return empty columns.

finanzen__FaktNT__Zynex.m99__Produktionslauf.txt
2 rows

File structure

Notes: The provided text is free-form German prose describing internal corporate invoice generation processes for a Swiss web hosting company. It contains no structured columns or tabular data. While it references invoice numbers (e.g., 10023), dates (e.g., 11.11.2002), and domain names (www.gewerbe-volketswil.ch), these appear inline within narrative descriptions rather than as delimited fields. The content is unstructured operational documentation, not a dataset with importable PII columns.

finanzen__FaktNT__Zynex.m99__Produktionslauf__01.07.2002__09.01_.txt
0 rows

File structure

Notes: The provided text is free-form German prose describing internal corporate financial procedures and document generation logic for subscription billing. It contains no structured columns or tabular data. While it references internal codes and dates, there are no identifiable PII fields like names, emails, or addresses present in this excerpt.

finanzen__FaktNT__Zynex.m99__Produktionslauf__01.07.2002__09.10_.txt
10 rows

File structure

Notes: The file is free-form text containing German-language financial processing instructions for invoices and subscriptions. There is no consistent delimiter or column structure across lines; instead, it contains embedded customer website URLs (www.sensirion.com, www.gnatho-europe.com, www.tceulach.ch) and invoice dates. This matches the unstructured condition (a) no consistent delimiter, (b) lines have varying shapes, (c) contains visible PII-like strings.

finanzen__FaktNT__Zynex.m99__Produktionslauf__04.06.2002__14.43_.txt
2 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m99__Produktionslauf__04.09.2002__15.29_.txt
8 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m99__Produktionslauf__05.04.2002__15.15_.txt
4 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FaktNT__Zynex.m99__Produktionslauf__05.08.2002__10.48_.txt
2 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m99__Produktionslauf__05.08.2002__10.55_.txt
21 rows

File structure

Notes: Free-form text with embedded customer website URLs and invoice details, no consistent column structure. Contains Swiss SME customer domains (www.caviola-ag.ch, www.wittich-weine.ch, www.nyfeler-keller.ch) and invoice generation metadata for Zynex Business subscriptions. No structured columns present.

finanzen__FaktNT__Zynex.m99__Produktionslauf__06.11.2001__17.46_.txt
16 rows

File structure

Notes: File is free-form German text with no consistent column structure. Contains embedded domain names (www.troller-ag.ch, www.dentalesthetics.ch, www.scotoni.ch) but lacks tabular format. Per rules, unstructured files with embedded PII require no column mapping.

finanzen__FaktNT__Zynex.m99__Produktionslauf__06.11.2001__17.48_.txt
8 rows

File structure

Notes: Free-form text document with no consistent column structure. Contains embedded customer websites (www.corazon.ch, www.zuerifit.ch, www.fz-elektroag.ch) and subscription details, but lacks tabular format required for column mapping.

finanzen__FaktNT__Zynex.m99__Produktionslauf__07.10.2002__13.19_.txt
0 rows

File structure

Notes: The file is unstructured free-form text containing financial transaction records and invoice generation details. It lacks consistent column delimiters and row structure. While it contains domain names (weinhalle.ch, fibotrader.com) and dates, these are embedded within prose rather than in a tabular format. No PII columns can be mapped due to the absence of a consistent structure.

finanzen__FaktNT__Zynex.m99__Produktionslauf__08.12.2000__15.09_.txt
4 rows

File structure

Notes: The file is free-form text with no consistent column structure. It contains German-language financial processing notes and invoice generation instructions for customer subscriptions, but lacks any tabular data format. While it contains customer-related references (e.g., website URLs like www.beninvest.ch), these appear inline within descriptive text rather than in a structured columnar format. The unstructured nature prevents column mapping.

finanzen__FaktNT__Zynex.m99__Produktionslauf__11.11.2002__09.58_.txt
22 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m99__Produktionslauf__12.03.2002__13.10_.txt
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m99__Produktionslauf__13.11.2000__14.57_.txt
2 rows

File structure

Notes: The provided text is free-form German-language accounting/production log content from Zynex corporate records. It contains no consistent tabular structure, only narrative financial transaction details (invoice generation, subscription types, dates, amounts). No identifiable PII columns exist in the visible 50 rows. Per rules, unstructured files with no column structure return empty columns object.

finanzen__FaktNT__Zynex.m99__Produktionslauf__13.11.2000__16.20_.txt
2 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m99__Produktionslauf__16.03.2001__10.33_.txt
8 rows

File structure

Notes: Free-form text document with no consistent columnar structure. Contains German-language financial processing notes for Zynex customer invoices (subscription billing records), but data is presented as narrative/prose rather than tabular rows. Visible customer websites (www.centrachem.ch, www.fem-innovations.com, www.aesthetische-chirurgie.ch) appear embedded in text but lack structured columnar mapping.

finanzen__FaktNT__Zynex.m99__Produktionslauf__18.04.2001__16.05_.txt
4 rows

File structure

Notes: The file is a free-form text document containing German-language financial transaction records and invoice generation logic. It shows invoice generation steps, dates, amounts, and customer domains, but lacks any consistent columnar structure. The data appears to be procedural code or template logic for generating invoices rather than tabular records. No structured columns are present to map to PII fields.

finanzen__FaktNT__Zynex.m99__Produktionslauf__22.01.2001__13.35_.txt
4 rows

File structure

Notes: The provided data is free-form text representing invoice generation logic and accounting entries. It lacks any consistent columnar structure or delimiter. While it contains business logic and invoice references, it does not contain any identifiable PII fields in a structured format. The content appears to be procedural code or template logic for generating invoices rather than actual customer records with PII.

finanzen__FaktNT__Zynex.m99__Produktionslauf__24.01.2002__08.53_.txt
10 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m99__Produktionslauf__27.02.2001__13.01_.txt
8 rows

File structure

Notes: The file is free-form text with no consistent column structure. It appears to be a German-language invoice generation log containing embedded customer website URLs (www.fcc-basel.ch, www.bosshardt.ch, www.buehrertreuhand.ch) and invoice dates, but lacks tabular formatting. This qualifies as unstructured data with embedded PII requiring special handling.

finanzen__FaktNT__Zynex.m99__Produktionslauf__27.02.2002__16.25_.txt
16 rows

File structure

Notes: Free-form text with no consistent columnar structure. Contains embedded customer websites (www.bosshardt.ch, www.centrachem.ch, www.buehrertreuhand.ch) but lacks any row structure or delimiter pattern. Sample shows production workflow documentation for invoice generation with customer identifiers embedded in free text lines.

finanzen__FaktNT__Zynex.m99__Produktionslauf__27.02.2002__17.51_.txt
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m99__Produktionslauf__27.06.2001__13.26_.txt
4 rows

File structure

Notes: The file is unstructured free-form text containing internal corporate financial records and invoice generation logic. It lacks consistent column delimiters and row structure. Contains embedded customer website URLs (www.gnatho-europe.com, www.tceulach.ch) and internal reference codes but no actual PII fields in structured format. The text describes invoice generation processes for Swiss SME subscriptions to Zynex Business and Zynex One web hosting services.

finanzen__FaktNT__Zynex.m99__Produktionslauf__27.07.2001__09.04_.txt
0 rows

File structure

Notes: This is free-form text (German business document with no structured columns). Sample shows invoice generation notes and financial processing steps for subscription #1042 dated 27.07.2001, but lacks tabular data. No consistent delimiter or columnar structure exists across lines.

finanzen__FaktNT__Zynex.m99__Produktionslauf__27.07.2001__09.30_.txt
2 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m99__Produktionslauf__27.08.2001__08.37_.txt
16 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FaktNT__Zynex.m99__Produktionslauf__27.09.2001__10.07_.txt
6 rows

File structure

Notes: File is free-form German-language accounting document with no consistent delimiter or column structure. Contains invoice generation instructions for Zynex subscriptions (business/web hosting) with customer domains (www.hanbos.ch, www.stuessiautomobile.ch, www.marag.ch) embedded in text lines, but lacks tabular format. Must be processed through unstructured PII extraction pipeline.

finanzen__FaktNT__Zynex.m99__Produktionslauf__29.05.2002__15.43_.txt
0 rows

File structure

Notes: The provided text is unstructured German financial/production documentation from Zynex's internal records. It contains no consistent columnar structure or delimited data — instead it appears to be free-form notes, invoice generation instructions, and production workflow documentation. There are no identifiable PII fields (emails, names, addresses, etc.) visible in this sample. The text references invoice numbers, dates, and internal codes but these are not personal data. This qualifies as unstructured content per the rules (free-form text with no consistent delimiter).

finanzen__FaktNT__Zynex.m99__Produktionslauf__30.11.2001__10.58_.txt
10 rows

File structure

Notes: File is free-form German-language invoice generation script with no consistent column structure. Contains embedded customer account numbers (Abonummer) and URLs but lacks tabular format. Visible PII includes: account numbers (1046, 1043, etc.), URLs (www.fininco.com, www.veba.ch), and date values. This qualifies as unstructured text requiring streaming extraction.

finanzen__FibuNT__migrated_to_TOPAL___Zynex.m99__DTA.LOG.csv
0 rows

File structure

Notes: This is free-form financial ledger data with no consistent columnar structure. The file appears to be a printed accounting report with transaction lines containing reference numbers, dates, customer codes, names, and amounts. While it contains customer codes and names (potentially PII), the format lacks a consistent delimiter and row structure required for columnar mapping. The content shows German-language financial data from Zynex's internal records, but due to its unstructured nature, it must be processed as free-form text for PII extraction.

finanzen__FibuNT__migrated_to_TOPAL___Zynex.m99__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___Zynex.m99__besrvesr.log.csv
0 rows

File structure

Notes: The file is a free-form text document (German financial error log) with no consistent columnar structure. Contains error records with internal reference numbers and amounts, but no personal PII fields. No column mapping possible.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m00__DTA.LOG.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; appears to be a financial protocol/report with transaction lines, not structured tabular data with PII columns

finanzen__FibuNT__migrated_to_TOPAL___zynex.m00__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m00__besrvesr.log.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains only financial transaction records without any PII fields

finanzen__FibuNT__migrated_to_TOPAL___zynex.m01__DTA.LOG.csv
0 rows

File structure

Notes: This is free-form financial transaction data with no consistent columnar structure. Lines contain mixed transaction details (OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, Total) but lack a stable delimiter or header row. Contains company/client names (SWITC, ELVIA, SVA, etc.) but no identifiable personal PII fields like email, phone, or SSN. The format is unstructured financial ledger data rather than a CSV with PII columns.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m01__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m01__besrvesr.log.csv
0 rows

File structure

Notes: This is a free-form financial error report with no consistent columnar structure. Contains German-language accounting entries and error messages about failed invoice postings, but no identifiable personal information or structured data fields. The document appears to be an internal accounting log from Zynex's ERP system showing failed transactions, not customer PII.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m01__convert.log.csv
0 rows

File structure

Notes: This is a log file containing system conversion messages in German. There are no consistent columns or structured data — it's free-form text with timestamps and status messages about data conversion. No PII is present.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m02__DTA.LOG.csv
0 rows

File structure

Notes: This is a free-form financial protocol document with no consistent columnar structure. It contains transaction lines with codes, dates, and amounts but no identifiable personal information or structured fields. The format does not match CSV/TSV patterns, and the content appears to be internal corporate accounting records without PII.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m02__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m02__besrvesr.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger with no consistent column structure. It contains transaction records with fields like Beleg-Nr (document number), Valuta (date), OP (operation number), PK (project code), and Betrag (amount). There are no personal identifiable information (PII) fields present in this sample. The data appears to be purely transactional and financial in nature, listing payments to various entities (SCOTONIAG, MSMFININCO, etc.) with amounts in CHF. Since there is no consistent delimiter or column structure and no PII visible, this is classified as unstructured text.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m02__convert.log.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m03__DTA.LOG.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction lines with internal reference codes (OP-Nr., PK-Nr.), names (SSN, GIGER, SCMOB, etc.), and monetary amounts, but lacks a defined delimiter or repeated header/column pattern. Though names appear, they are mixed with internal codes and financial data in a narrative format, meeting unstructured criteria (a), (b), and (c).

finanzen__FibuNT__migrated_to_TOPAL___zynex.m03__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m03__besrvesr.log.csv
0 rows

File structure

Notes: The provided text is a free-form financial report/protoll with no consistent columnar structure. It contains error records about transactions falling outside the fiscal year, with fields like Record-Nr, Valuta, Betrag, Referenznr, Teilnehmernr, etc. These appear to be internal accounting references and transaction IDs rather than PII. No identifiable personal information (names, addresses, emails, etc.) is present in the visible sample. The format lacks consistent delimiters and row structures required for columnar mapping.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m04__DTA.LOG.csv
0 rows

File structure

Notes: This is a free-form financial transaction report (DTA-Protokoll) showing payment entries with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total columns. No consistent columnar structure with PII fields exists; entries are transactional records without personal identifiers like names, addresses, or contact details. The 'Name' column contains business/vender abbreviations (SWITC, HANDE, MWST, etc.), not personal names. The file is a financial statement, not a dataset with personal PII fields.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m04__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m04__Mahngebuehr.txt
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m04__convert.log.csv
0 rows

File structure

Notes: free-form log file with no consistent column structure; contains system conversion messages and timestamps but no personal data fields

finanzen__FibuNT__migrated_to_TOPAL___zynex.m05__DTA.LOG.csv
0 rows

File structure

Notes: This is a free-form financial protocol document (DTA-Protokoll) with no consistent columnar structure. It contains transaction records with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total fields, but these appear as free-form lines without a fixed delimiter or header row. The values represent internal corporate financial data (transaction numbers, dates, client codes, names, and amounts) rather than personal PII fields like email or phone. Since there is no consistent delimiter and the structure varies line-to-line, this qualifies as unstructured text per the rules.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m05__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m05__convert.log.csv
0 rows

File structure

Notes: This is a log file containing conversion process messages and timestamps. There are no structured columns or PII fields. The content is purely procedural logs about data conversion and does not contain any personal or identifiable information.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m06__DTA.LOG.csv
0 rows

File structure

Notes: The provided text is a free-form financial protocol / ledger from Zynex, not a structured dataset with columns. It contains transaction records with OP-Nr, Valuta dates, PK-Nr, Names (SWITC, SVAZß, etc.), amounts in CHF, and totals. There are no consistent delimiters or repeating column positions across lines — the format varies between header lines, transaction lines, and summary lines. Though names like 'SWITC' and 'SVAZß' appear, they are business entity abbreviations, not personal PII. No email addresses or phone numbers are visible. This qualifies as unstructured text per the rules (no consistent delimiter, varying line shapes, no importable column structure).

finanzen__FibuNT__migrated_to_TOPAL___zynex.m06__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m06__besrvesr.log.csv
0 rows

File structure

Notes: free-form text with embedded transaction data but no consistent column structure. Contains error messages about invalid valuation dates, reference numbers, and amounts, but lacks repeating tabular format with identifiable PII fields. The text appears to be an accounting report with internal transaction IDs and amounts, but no personal information is present.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m06__convert.log.csv
0 rows

File structure

Notes: free-form text with log entries about data conversion; no structured columns or PII present

finanzen__FibuNT__migrated_to_TOPAL___zynex.m07__DTA.LOG.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It shows transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total, but these appear as part of a narrative report rather than a delimited dataset. No PII is present in this snippet; values like 'RUBEA', 'SWISS', 'ALLIA' are likely business/client codes, not personal names. Given the unstructured nature, routing through unstructured processing is appropriate.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m07__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m07__besrvesr.log.csv
0 rows

File structure

Notes: The file is a free-form financial error report with no consistent columnar structure. It contains transaction error messages in German with reference numbers, amounts, and error explanations, but no identifiable PII fields. The format is unstructured prose rather than a delimited dataset.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m07__convert.log.csv
0 rows

File structure

Notes: free-form log file with no consistent columnar structure; contains timestamped conversion process messages about .dat files, no PII visible in sample

finanzen__FibuNT__migrated_to_TOPAL___zynex.m08__DTA.LOG.csv
0 rows

File structure

Notes: This is a free-form financial protocol document (DTA-Protokoll) with no consistent columnar structure. The content shows transaction details with no identifiable personal information in the first 50 rows. It contains business financial data (CHF amounts, transaction codes) but no PII fields. Since there is no consistent delimiter and lines have varying structures, this qualifies as unstructured text without embedded emails/phones.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m08__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m08__besrvesr.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protoco l with no consistent columnar structure. It contains error records and totals but no identifiable personal data fields. No PII mapping is possible as there are no structured columns with names or repeated patterns.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m08__convert.log.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; log file entries with timestamps and conversion messages

finanzen__FibuNT__migrated_to_TOPAL___zynex.m09__CopySaldo.log.csv
0 rows

File structure

Notes: file is free-form log/procedure text with no consistent column structure; contains German-language accounting protocol for Zynex AG financial year-end processing

finanzen__FibuNT__migrated_to_TOPAL___zynex.m09__DTA.LOG.csv
0 rows

File structure

Notes: The provided data is a free-form financial transaction report (DTA-Protokoll) from Zynex with no consistent columnar structure. It contains transaction lines with OP-Nr, Valuta dates, PK-Nr, Names (company abbreviations), ZL (currency code), Betrag (amounts), and totals — but these are NOT personal PII fields (names are corporate abbreviations like SWITC, SVAZ�, EIDG., SHELL, etc.). The file lacks any structured CSV/TSV format and shows prose-style reporting with no repeated column headers or consistent delimiters. No actionable PII (emails, phones, full names, addresses, etc.) is present.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m09__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m09__NewYear.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FibuNT__migrated_to_TOPAL___zynex.m09__besrvesr.log.csv
0 rows

File structure

Notes: This is a free-form financial error report with no consistent column structure. It contains German text describing accounting errors (Valuta dates outside fiscal year) and totals, but no identifiable personal data. No structured columns exist to map to PII fields.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m09__convert.log.csv
0 rows

File structure

Notes: This is a free-form log file documenting data conversion processes for Zynex internal systems. It contains no structured columns or PII fields — only timestamps, system messages, and file conversion statuses. No emails, names, or addresses are present.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__CopySaldo.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__DTA.LOG.csv
0 rows

File structure

Notes: This is a free-form financial protocol/document showing payment records with no consistent columnar structure across lines. The data appears to be a printed invoice/receipt from 27.12.2010 showing a single payment of 70.60 CHF. There are no repeated field patterns or delimiters — it's a formatted document with lines that vary in content and length. While it contains monetary values, it lacks any personal identifiers (names, emails, addresses, etc.) that would require mapping to PII fields. The structure does not meet the criteria for CSV/TSV parsing; it is purely free-form text.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__Fl_ssige_Mittel__konto.csv
0 rows

File structure

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

Notes: This file contains only internal accounting codes and descriptions with no PII. All columns are internal identifiers, account types, and textual descriptions of accounts (e.g., 'Kasse', 'PC Konto', 'Bank RB'). No personal or sensitive data is present.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__NewYear.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__besrvesr.log.csv
0 rows

File structure

Notes: The provided data is a free-form financial statement/protokoll with no consistent columnar structure. It contains transaction records with fields like Beleg-Nr (voucher number), Valuta (date), OP (transaction code), PK (customer/account code), Betrag (amount), Buchungstext (description), Skonto (discount), Erlm. (deductions), and noch offen (outstanding balance). There are no identifiable PII fields (names, emails, addresses, etc.) visible in this financial summary. The values are all transactional codes, dates, and monetary amounts without personal identifiers.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__convert.log.csv
0 rows

File structure

Notes: Logfile content contains no structured data columns; purely procedural logs of file conversion operations and error messages. No PII present.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__debug__detail.csv
0 rows

File structure

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

Notes: This file appears to be a financial ledger or accounting statement (German: 'Erlöse' = revenues, 'Aufwand' = expenses). All columns contain accounting codes, boolean flags, and monetary amounts. No PII fields are present — this is purely transactional/financial data without any personal identifiers, customer details, or contact information. The values are structured financial entries, not personal records.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__facilitywizard.txt
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains corporate configuration data for Zynex AG, no PII present

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__mandant.txt
0 rows

File structure

Notes: The provided text is a German-language document header/notes for a financial system template (Sage Schweiz AG) rather than a delimited data file. It contains no structured records, column headers, or repeating rows. The text describes a baseline accounting template for SESAM accounting system version 2008 and contains no PII fields. This is purely instructional documentation about system setup.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__mfrreport__kontoinfo.csv
0 rows

File structure

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

Notes: This is a structured financial ledger file with account codes and descriptions. No personal identifiable information (PII) is present in the visible columns. All entries are internal accounting codes and textual descriptions of financial categories, with no names, addresses, contact details, or other PII fields. The sample shows standard chart-of-accounts style data common in corporate financial systems.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__settings__kontoinfo.csv
0 rows

File structure

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

Notes: This is a financial ledger/CONTAB file with accounting codes and descriptions. No PII fields are present — only account numbers, types, text descriptions, and report IDs. All values are internal business codes and zero-value placeholders.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10__temp__kontoinfo.csv
0 rows

File structure

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

Notes: This is a financial ledger/COB ledger file with account codes and descriptions. No PII fields are present. All entries are internal accounting codes, types, and descriptions without any personal information.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__CopySaldo.log.csv
0 rows

File structure

Notes: Free-form text log file with no consistent column structure. Contains German-language financial processing logs for Zynex AG, referencing account numbers and transaction updates but lacks any PII fields beyond internal accounting identifiers. No personal data visible in the sample.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__DTA.LOG.csv
0 rows

File structure

Notes: This is a free-form financial report/protoco l with no consistent columnar structure. Lines vary in format and contain only transaction data (OP-Nr., Valuta, PK-Nr., Name, ZL, Betrag, Total). No PII fields are present in a columnar format. The 'Name' field appears to contain only business/customer codes (ECOME, SHELL, TDCSW, etc.) and not personal names. Per rules, unstructured files with no consistent columns containing embedded PII should be routed through streaming extraction.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__Fl_ssige_Mittel__konto.csv
0 rows

File structure

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

Notes: This is purely internal financial ledger data with account numbers (kontonr) and account types (typ) and descriptions (text) and fund operators (fondsoperator). No personal or identifiable information is present. All columns map to skip categories: kontonr is an internal account identifier, typ is an internal classification code, text contains bank account descriptions (not addresses), and fondsoperator is an internal operator code. Therefore, no PII columns to map.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__NewYear.log.csv
0 rows

File structure

Notes: This is a free-form configuration protocol document (not tabular data). It contains German-language administrative instructions for setting up accounting books, budgets, and fiscal year transitions for Zynex AG. There are no structured columns or repeating rows with PII fields. The content describes internal accounting processes rather than exposing personal or customer data.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__besrvesr.log.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. It contains transaction records with fields like payment references (Beleg-Nr), dates (Valuta), reference numbers (OP/PK), and amounts (Betrag), but these are not mappable to defined PII fields. The data represents payment records for Swiss SMEs billed for Zynex web hosting services, with no personal identifiers present in this excerpt.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__convert.log.csv
0 rows

File structure

Notes: File is free-form log text in German with no consistent delimiter structure. Contains conversion logs and error messages for database tables (sfbadr.dat, sfbbank.dat, etc.), but no actual PII data in tabular format. Meets unstructured criteria: no shared delimiter, line shape varies, and contains embedded date/time stamps and file operations rather than structured records.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__debug__detail.csv
0 rows

File structure

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

Notes: This is a financial statement file with columns representing accounting entries (revenues, expenses, financing). No personal identifiable information (PII) is present. Columns are purely transactional/financial (e.g., 'Erlöse Dienstleistungen' = Service Revenues, 'Wareneinkäufe' = Merchandise Purchases). All values are monetary amounts or boolean flags, with no names, addresses, emails, or other PII. This is standard corporate financial reporting data.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__facilitywizard.txt
0 rows

File structure

Notes: The provided text is free-form structured data (setup assistant configuration) with no consistent columnar pattern across rows. It contains internal identifiers and settings but no personal PII fields like names, emails, or addresses. The format does not match CSV/TSV with headers and columns; instead, it is a configuration dump with key-value pairs and descriptive lines. Therefore, it is classified as unstructured with no column mappings.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__mandant.txt
0 rows

File structure

Notes: This is unstructured documentation prose describing the basis client for SESAM accounting system version 2008. Contains no tabular data or PII fields. No consistent delimiter or row structure exists.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__mfrreport__kontoinfo.csv
0 rows

File structure

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

Notes: This file contains only accounting codes and descriptions with no personal identifiable information (PII). All columns represent financial account numbers and types, not personal data.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__settings__kontoinfo.csv
0 rows

File structure

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

Notes: This file contains structured financial accounting codes (kontonr) and types, but no personal identifiable information (PII). All columns represent internal accounting categories and do not contain names, addresses, emails, phone numbers, or other PII fields. The data is purely financial/transactional in nature.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m10_vor_mwst_conv__temp__kontoinfo.csv
0 rows

File structure

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

Notes: This is purely financial accounting data (chart of accounts) with no personal or customer information. Columns 'kontonr' (account number) and 'type' (account type) contain only internal financial codes, while 'text' holds generic account descriptions and 'rptid' is a report identifier. No PII fields present.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__CopySaldo.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__DTA.LOG.csv
0 rows

File structure

Notes: free-form financial transaction report with no column headers or consistent structure. Contains transaction IDs, dates, reference numbers, customer codes (PK-Nr.), and amounts in CHF. No identifiable PII fields (names, addresses, emails, etc.) are present beyond generic codes. This is typical of internal accounting reports where customer relationships are obscured by internal reference numbers.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__Fl_ssige_Mittel__konto.csv
0 rows

File structure

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

Notes: This file contains internal accounting codes and bank account references, not personal PII. All columns are internal financial identifiers (account numbers, account types, text descriptions, fund operators) and do not contain any personally identifiable information such as names, addresses, emails, or phone numbers. Therefore, no columns map to PII fields.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__NewYear.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__besrvesr.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent column structure. It contains payment records with invoice numbers, dates, and amounts but no identifiable PII fields. The format is unstructured text with no delimited columns, and every line has a different shape. No emails or phone numbers are visible in the sample.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__convert.log.csv
0 rows

File structure

Notes: File is unstructured log data with no consistent column format. Contains timestamped log messages about data conversion processes for various .dat files in German, with error codes and status messages. No PII fields present in structured format.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__debug__detail.csv
0 rows

File structure

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

Notes: This is a financial statement file with columns representing accounting entries (revenues, expenses, financing). No PII fields present. Columns are purely financial metrics and identifiers (e.g., 'Erlöse Dienstleistungen' = Revenue from services, 'betragabfluss' = outflow amount). All columns map to skip categories: financial/transactional data and internal IDs.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__facilitywizard.txt
0 rows

File structure

Notes: This is free-form text (setup assistant log) with no consistent columnar structure. It contains corporate configuration details for Zynex AG but no identifiable personal data in structured columns. No PII mapping possible.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__mandant.txt
0 rows

File structure

Notes: This is free-form text (not a structured table). The sample shows a German-language README/document for a Sage Schweiz accounting template (Basis-Mandant KMU 2008). It contains no column structure or personal identifiers, only informational prose about the template's purpose and warnings against modification. No PII fields are present.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__mfrreport__kontoinfo.csv
0 rows

File structure

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

Notes: This file contains only account codes and financial categories, no PII fields present. All columns represent internal accounting codes and descriptions (kontonr, type, text, rptid) with no personal identifiable information.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__settings__kontoinfo.csv
0 rows

File structure

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

Notes: This file contains only account codes, types, descriptive text, and report IDs. No personal identifiable information (PII) is present. All entries are structured financial categories and do not contain any names, addresses, emails, phone numbers, dates of birth, or other PII fields.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m11__temp__kontoinfo.csv
0 rows

File structure

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

Notes: This file contains only accounting codes and descriptions — no PII fields present. All columns represent internal financial categories (kontonr, type, text, rptid) with no personal data.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__CopySaldo.log.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__DTA.LOG.csv
0 rows

File structure

Notes: This is a free-form financial report/protokoll with no consistent columnar structure. Contains transaction lines but no identifiable PII fields. The format is unstructured financial data, not a delimited CSV/TSV with headers.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__Fl_ssige_Mittel__konto.csv
0 rows

File structure

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

Notes: This file contains internal accounting codes and bank account references, not personal PII. Columns represent account numbers (kontonr), account types (typ), descriptive text (text), and fund operators (fondsoperator). No PII fields are present.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__NewYear.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__besrvesr.log.csv
0 rows

File structure

Notes: The provided text is a free-form financial protocol document in German with no consistent columnar structure. It contains accounting entries and error messages but lacks any delimited rows or repeated field positions. While it contains monetary values and reference numbers, there is no identifiable PII in the visible text. The document format is unstructured accounting log rather than a data export with columns.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__convert.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__debug__detail.csv
0 rows

File structure

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

Notes: This is a financial statement file with columns: detailname (description), abfluss (outflow flag), betragabfluss (outflow amount), zufluss (inflow flag), betragzufluss (inflow amount), rptid (report id), konties (account id). No PII fields present. All columns are financial/transactional data and should be skipped per exclusion rules.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__facilitywizard.txt
0 rows

File structure

Notes: The provided text is free-form configuration/setup output for an accounting system (Sesam) and contains no tabular data. It shows company setup parameters for Zynex AG (Mandant-Name) including address details, fiscal year ranges, currency, and various numbering ranges — but these are internal identifiers and operational settings, not customer PII. No consistent delimiter structure exists, and the content is purely technical/procedural. Since there are no rows with repeated field positions and no embedded emails/phones, unstructured processing is appropriate but will yield no PII to extract.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__mandant.txt
0 rows

File structure

Notes: The provided text is a German-language document describing a corporate accounting template (Basis-Mandant KMU 2008) for Sage Schweiz AG. It contains no structured data rows, only descriptive prose about financial system setup and usage instructions. There are no columns, no PII fields, and no identifiable data structures to map. This is purely informational documentation, not a dataset containing personal or sensitive information.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__mfrreport__kontoinfo.csv
0 rows

File structure

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

Notes: This is a financial ledger/COB ledger structure with columns: kontonr (account number), type (account type code), text (account description), rptid (report ID). No PII fields present — all entries are internal accounting codes and descriptions. No names, addresses, emails, etc. The breach context mentions customer invoicing data, but this specific file only contains internal chart of accounts.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__settings__kontoinfo.csv
0 rows

File structure

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

Notes: This is a financial ledger file with account codes, types, German descriptions, and report IDs. No PII fields are present. Columns are purely accounting codes and categories.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m12__temp__kontoinfo.csv
0 rows

File structure

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

Notes: This is purely accounting/financial data with account numbers and types - no PII fields present. All columns represent financial ledger entries (account numbers, types, descriptions, and report IDs). No personal identifiers detected.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__CopySaldo.log.csv
0 rows

File structure

Notes: This is a structured log file from Zynex's FaktNT ERP system (Saldo übertragen protocol), not a delimited dataset. Contains internal accounting operations and PK updates but no PII fields. No column mapping possible.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__DTA.LOG.csv
0 rows

File structure

Notes: This is a free-form financial protocol document with no consistent columnar structure. It contains transaction records with OP-Nr, Valuta dates, PK-Nr, Names (SHELL, TDCSW, etc.), ZL codes, and monetary values, but these are not personal PII fields. The data appears to be corporate billing records with business entity names rather than individual personal information. No structured columns to map.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__Fl_ssige_Mittel__konto.csv
0 rows

File structure

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

Notes: This is an internal financial ledger file with account numbers and types. No personal identifiable information (PII) fields are present. Columns 'kontonr' (account number), 'typ' (account type), 'text' (account description), and 'fondsoperator' (fund operator) contain only internal corporate financial data. No PII fields mapped.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__MWSTDATA.DAT
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__NewYear.log.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__besrvesr.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger with no consistent columnar structure. Lines contain transaction codes, dates, reference numbers, and amounts, but there is no header row or repeating delimiter pattern. Contains payment records and error messages rather than personal PII fields.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__convert.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__debug__detail.csv
0 rows

File structure

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

Notes: This file contains only financial transaction data (revenues, expenses, cash flows) with no personal identifiable information. All columns represent accounting entries (e.g., 'Erlöse Dienstleistungen' = Service Revenues, 'Wareneinkäufe' = Merchandise Purchases) and internal identifiers. No PII fields are present.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__facilitywizard.txt
0 rows

File structure

Notes: The provided content is free-form text (setup assistant configuration notes) with no consistent columnar structure. It contains organizational metadata (company name, address, fiscal periods) but no repeating PII fields across rows. Since there is no consistent delimiter or row structure, this is classified as unstructured.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__mandant.txt
0 rows

File structure

Notes: This is a free-form document describing a corporate accounting template (Sage Switzerland AG). It contains no structured rows with personal identifiers; it is purely descriptive prose about a default accounting client template. No columns to map.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__mfrreport__kontoinfo.csv
0 rows

File structure

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

Notes: This is purely financial accounting data with account codes, types, descriptions, and reference IDs. No personal identifiable information (PII) is present. All columns represent internal accounting categories and do not map to any PII fields.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__settings__kontoinfo.csv
0 rows

File structure

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

Notes: No PII fields detected. This appears to be a financial ledger with account codes and descriptions in German. All values are numeric codes, account types, German text descriptions, and zero values — no personal identifiable information present.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m13__temp__kontoinfo.csv
0 rows

File structure

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

Notes: This is a financial ledger file with account codes, types, German descriptions, and report IDs. No personal identifiable information (PII) fields are present. Columns map to accounting categories and do not contain any names, addresses, emails, phone numbers, dates of birth, SSNs, passwords, usernames, or other PII fields as defined. All columns are skipped per rules.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m14__CopySaldo.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__FibuNT__migrated_to_TOPAL___zynex.m14__DTA.LOG.csv
0 rows

File structure

Notes: This is a free-form financial report/protoco with no consistent column structure. The data contains transaction codes, amounts, and company/client names (SWITC, SVAZ̈, ECOME, etc.) but lacks any PII fields like email, phone, or address. It appears to be an internal accounting document with payment summaries rather than customer records.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m14__Fl_ssige_Mittel__konto.csv
0 rows

File structure

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

Notes: This file contains internal financial ledger data with account numbers (kontonr) and account types (typ), along with descriptive text fields (text) and fund operators (fondsoperator). None of these fields contain personally identifiable information (PII). The text field contains generic banking and account descriptions without any personal names, addresses, or other PII. All columns are marked as skip per the exclusion rules for internal financial records.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m14__NewYear.log.csv
0 rows

File structure

Notes: This is a free-form financial configuration/protocol document in German, not a delimited data file with columns. It contains internal settings for a fiscal year transition in Zynex's FibuNT accounting system, with no personal customer data or PII present. The document describes system behavior (e.g., 'Bücher neu aufbauen', 'Kontensalden übernehmen') and has no structured columns to map.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m14__besrvesr.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/proforma with no columnar structure. It contains payment records with customer names (e.g., GEWERBEVERE, PRACTIDENTG, STEINMETZEX) but lacks any consistent delimiter or header-based structure across lines. The document appears to be a human-readable protocol/report rather than structured data rows.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m14__convert.log.csv
0 rows

File structure

Notes: This is a free-form log file with no consistent columnar structure. Lines contain timestamps, conversion status messages, and file names but do not represent tabular data with repeated fields. While it contains internal system identifiers (file names like sfbadr.dat), these are not personal PII and there are no emails or phone numbers visible in the sample. Per the unstructured rule, no column mapping is performed.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m14__debug__detail.csv
0 rows

File structure

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

Notes: This file contains financial transaction records (revenue, expenses, financing) with no personal identifiable information. Columns are all corporate financial metrics (e.g., 'Erlöse Dienstleistungen', 'Wareneinkäufe', 'Personalaufwand') and internal identifiers ('rptid', 'konties'). No PII fields detected.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m14__facilitywizard.txt
0 rows

File structure

Notes: This is unstructured free-form text containing configuration and metadata for Zynex AG, not tabular data with PII columns. No consistent delimiter or row structure exists; it's a configuration snapshot with internal codes, paths, and settings. No personal identifiable information (PII) is present in this sample.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m14__mandant.txt
0 rows

File structure

Notes: This is free-form text (German documentation about Sage Switzerland accounting system). No structured columns or PII present. Document explains the 'Basis-Mandant KMU 2008' template for SESAM accounting version 2008 and warns against modification. Contains only descriptive prose, no data rows or identifiable information.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m14__mfrreport__kontoinfo.csv
0 rows

File structure

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

Notes: This is a financial accounting chart of accounts file with no personal identifiable information (PII). Columns represent account numbers, types, descriptions, and report IDs. All values are internal accounting codes and text descriptions in German, with no names, addresses, contact details, or other PII fields present.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m14__settings__kontoinfo.csv
0 rows

File structure

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

Notes: This is a financial ledger structure with account codes and descriptions - no personal PII fields present. All values are account numbers and transaction types.

finanzen__FibuNT__migrated_to_TOPAL___zynex.m14__temp__kontoinfo.csv
0 rows

File structure

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

Notes: This file contains only accounting codes and descriptions with no PII present. All columns represent internal financial categories (kontonr, type, text, rptid) and contain no personal data. The text column contains generic business terms in German with no identifiable personal information.

finanzen__Inventar_RZ_Abschreibungen__Tabelle1.csv
0 rows

File structure

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

Notes: This is purely financial inventory data with no personal identifiers. Columns contain asset descriptions, purchase dates, invoice numbers, and depreciation schedules across years. No PII fields detected.

finanzen__LOBU__LOBU_1999__Fixkosten__Urs.csv
0 rows

File structure

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

Notes: This file contains only unstructured financial/lease records with no PII fields. All entries appear to be company names and monetary values with no personal identifiers. No columns map to any PII fields as per the exclusion rules for company/business data.

finanzen__LOBU__LOBU_1999__Lohnabr__10.csv
0 rows

File structure

Notes: This is an unstructured financial document from Zynex AG. It contains payment records and accounting details in German, but lacks any consistent columnar structure or identifiable PII fields. The content appears to be a printed payslip or accounting statement with no repeating patterns that would allow column mapping. While it contains references to account numbers and financial data, these are internal business identifiers rather than personal PII fields.

finanzen__LOBU__LOBU_1999__Lohnabr__7.csv
0 rows

File structure

Notes: The file is a free-form financial statement from Zynex AG with no consistent column structure. It contains Swiss Franc (CHF) calculations, AHV numbers, and internal accounting fields, but lacks identifiable personal data such as email, phone, or names in structured columns. The content appears to be an internal payroll or accounting document rather than customer PII.

finanzen__LOBU__LOBU_1999__Lohnabr__8.csv
0 rows

File structure

Notes: The file appears to be an unstructured financial statement/invoice document from Zynex AG, containing payment calculations, tax details, and accounting codes. It lacks consistent column headers and structured data fields. Values appear to be German-language accounting entries with financial amounts, tax calculations, and payment codes rather than personal PII. There are no identifiable personal data fields (names, addresses, emails, etc.) present in the sample rows.

finanzen__LOBU__LOBU_1999__Lohnabr__9.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. The sample contains unstructured text lines with mixed content (addresses, account numbers, financial calculations) and no repeated column pattern. Though it contains sensitive financial data, it lacks a tabular structure that would allow column mapping. The sample shows line-by-line accounting entries rather than delimited records.

finanzen__LOBU__LOBU_1999__Lohnabr__Brunner_Mark.csv
0 rows

File structure

Notes: This is a free-form financial statement document from Zynex AG. It contains no consistent columnar structure — it's a single record with merged cells and line breaks. While it contains sensitive Swiss AHV number (social security equivalent) and employee name, the format does not allow column mapping. The unstructured path will allow specialized processing to extract the AHV number and name.

finanzen__LOBU__LOBU_1999__Lohnabr__Brunner_Mark_Jul.csv
0 rows

File structure

Notes: The provided data is free-form text with no consistent delimiter structure. It appears to be a Swiss corporate financial document from Zynex AG, containing employee compensation details and banking information. While it includes potentially sensitive data like AHV number (Swiss social security number) and bank account details, the format does not conform to a structured CSV or table. The unstructured format with embedded PII requires special handling.

finanzen__LOBU__LOBU_1999__Lohnabr__Hanslin_Rene.csv
0 rows

File structure

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

Notes: This is an unstructured financial record file with no consistent column mapping. The data appears to be free-form text containing employee compensation details, bank information, and tax calculations. While it contains sensitive financial data, there are no identifiable PII fields (names, emails, addresses, etc.) in a structured column format. The file consists of prose-style accounting entries rather than delimited records with identifiable columns.

finanzen__LOBU__LOBU_1999__Lohnabr__K_ppeli_Urs.csv
0 rows

File structure

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

Notes: This is a free-form financial statement document with no consistent columnar structure. It contains employee compensation details and tax calculations rather than personal identifiable information fields like names, addresses, or contact details. While it includes an AHV number (Swiss social security number), this is buried in unstructured text and not presented in a columnar format. The data represents internal payroll processing records rather than customer PII.

finanzen__LOBU__LOBU_1999__Lohnabr__K_ppeli_Urs_Jul.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent column structure. It contains unstructured text lines with embedded personal data such as AHV number (Swiss social security number), name (Käppeli Urs), address (Usterstr. 14, 8308 Illnau), and bank account details. The document appears to be a payroll or accounting statement from Zynex AG in Switzerland. Due to the unstructured format and lack of consistent delimiters/columns, this should be processed as unstructured text with embedded PII extraction.

finanzen__LOBU__LOBU_1999__Lohnabr__Keller_Mike.csv
0 rows

File structure

Notes: This file is a free-form text document containing internal financial records. It lacks a consistent columnar structure across rows and appears to be a printed payslip or financial statement from Zynex AG. While it contains some PII-like values (e.g., name "Keller Michael", address "Am Bach 70", city "8400 Winterthur"), the data is presented as prose rather than in a delimited tabular format. According to the unstructured opt-out rules, files with no consistent delimiter structure and variable line shapes containing embedded PII should be identified as unstructured with empty columns. The presence of free-text layout and mixed content (financial calculations, addresses, names) confirms this classification.

finanzen__LOBU__LOBU_1999__Lohnabr__Leisi_Martin.csv
0 rows

File structure

Notes: The file is free-form financial statements with no consistent column structure. Contains embedded personal data in unstructured format (AHV number 591.72.265.213 and name 'Leisi Martin').

finanzen__LOBU__LOBU_1999__Lohnabr__Scarpi_Corinne.csv
0 rows

File structure

Notes: This is a free-form text file (likely an invoice or financial statement) with no consistent column structure. While it contains some personal data (e.g., name 'Scarpi Corinne', address 'Zürichstrasse 12', and AHV number '780.75.674.219'), it lacks a repeating delimiter and row structure. The data appears to be a single formatted record rather than a tabular dataset. The content includes Swiss AHV number (national insurance), name, address, and banking details, but due to its unstructured nature, it should be processed through a streaming PII extractor.

finanzen__LOBU__LOBU_1999__Lohnblatt__07.csv
0 rows

File structure

Notes: This is a free-form financial report table with no consistent column structure or identifiable PII fields. The content appears to be Swiss payroll/accounting data with monetary values and percentages, but lacks any personal identifiers like names, emails, or addresses. The format is not CSV or any structured tabular format with defined columns; instead, it's a formatted report with merged cells and multi-line headers.

finanzen__LOBU__LOBU_1999__Lohnblatt__08.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent column structure. It contains internal corporate financial records (payroll data) rather than personal PII. No structured columns to map.

finanzen__LOBU__LOBU_1999__Lohnblatt__09.csv
0 rows

File structure

Notes: This is not a structured dataset; it's a free-form financial report with no consistent columnar layout. The data appears to be Swiss payroll/accounting records with month columns (Jan, Feb, Mär), financial codes (5000/, 5700/, etc.), and numeric values. There are no identifiable PII fields (names, emails, addresses, etc.) in the visible structure. The format is unstructured tabular data without headers or consistent column positions.

finanzen__LOBU__LOBU_1999__Lohnblatt__10.csv
0 rows

File structure

Notes: The file is a free-form text representation of payroll/financial data from Zynex AG. There are no consistent column headers or delimiter structure across rows — each line contains a mix of numeric identifiers, account codes, percentages, and monetary values. No PII fields (names, emails, addresses, etc.) are visible in the sample. This is purely financial/transactional data with account codes and amounts, not personal customer data. Therefore, no column mapping is required; the file should be processed as unstructured content.

finanzen__LOBU__LOBU_1999__Lohnblatt__11.csv
0 rows

File structure

Notes: This is not structured tabular data; it's a free-form financial report with headers spanning multiple rows and no consistent delimiter. The data appears to be Swiss payroll/accounting figures with codes and percentages, not containing any personal PII fields. No identifiable PII present.

finanzen__LOBU__LOBU_1999__Lohnblatt__12.csv
0 rows

File structure

Notes: This is a free-form financial statement document from Zynex AG. The rows represent monthly financial breakdowns (January, February, March) with columns showing various financial line items (Grundlohn, Vers'leist., Kdn-Ausl, etc.). There are no consistent column headers or structured personal data fields. Values appear to be numeric financial figures rather than PII. The file is unstructured financial reporting, not a CSV with identifiable columns.

finanzen__LOBU__LOBU_1999__Lohnblatt__13.csv
0 rows

File structure

Notes: The file appears to be a financial statement or payroll document from Zynex AG, formatted as a free-form table with no consistent delimiter or row structure. Columns are not clearly defined and values are numeric codes and percentages, not PII. There is no identifiable personal data in the first 50 rows. This is not a structured CSV with column headers; it is a free-form financial report.

finanzen__LOBU__LOBU_1999__Lohnblatt__14.csv
0 rows

File structure

Notes: This is a non-tabular financial data file with no consistent columnar structure. The data appears to be Swiss payroll/financial records from Zynex AG with rows representing different financial line items and columns representing months/years. There are no identifiable PII fields like names, emails, or addresses in the visible data. This is a free-form financial statement format rather than a structured dataset with personal information.

finanzen__LOBU__LOBU_1999__Lohnblatt__15.csv
0 rows

File structure

Notes: This is a free-form table of financial accounting data (salaries, deductions, tax bases) from Zynex AG. No PII fields present; all columns represent internal financial codes, amounts, and percentages. The structure lacks personal identifiers like names, addresses, or contact details. The file contains structured accounting data but no personally identifiable information.

finanzen__LOBU__LOBU_1999__Lohnblatt__16.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__LOBU__LOBU_1999__Lohnblatt__17.csv
0 rows

File structure

Notes: This is an unstructured financial report (salary sheet) from Zynex AG. The data contains no personal identifiers or PII fields. Columns appear to represent internal accounting codes, percentages, and monetary values (all zero in sample rows). No email, phone, name, or address data present. This is not a CSV with defined columns but a formatted financial table with merged cells and header rows that do not represent column names.

finanzen__LOBU__LOBU_1999__Lohnblatt__18.csv
0 rows

File structure

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

Notes: This is a financial payroll report from Zynex AG. Columns contain internal accounting codes, monetary values, and year markers. No PII fields (names, emails, addresses, etc.) are present. All columns are internal financial identifiers, percentages, or year references.

finanzen__LOBU__LOBU_1999__Lohnblatt__19.csv
0 rows

File structure

Notes: This is not a delimited data file but a free-form financial statement table from Zynex AG. The rows show Swiss payroll/accounting data with no consistent column structure — headers are multi-line and values are financial codes/amounts. There is no PII present in this excerpt, but the unstructured format prevents column mapping. This matches the breach context of internal financial records rather than customer PII.

finanzen__LOBU__LOBU_1999__Lohnblatt__20.csv
0 rows

File structure

Notes: This is not a structured dataset but a free-form financial report or payroll summary from Zynex AG. The rows contain Swiss payroll accounting codes, amounts, and percentages, not personal identifiers. No consistent delimiter or column structure exists, and the data represents internal financial records rather than customer PII.

finanzen__LOBU__LOBU_1999__Lohnblatt__AHV-ABR.csv
0 rows

File structure

Notes: This is a free-form text file containing unstructured payroll records from Zynex AG. The file appears to be a printed or exported payroll statement in German, with no consistent column delimiter or header structure. Values appear to include Swiss social security numbers (AHV/IV/EO-pflichtige Versicherten-Nummer), employee names (Name und Vorname des Versicherten), and salary amounts. While it contains PII, the lack of consistent row structure and delimiter means it must be processed as unstructured text for email/phone extraction.

finanzen__LOBU__LOBU_1999__Lohnblatt__Brunner.csv
1 column2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header is ambiguous, but values are clearly names: 'Brunner Mark'

Notes: This is a payroll file with structured columns. Only column 1 contains PII (fullName). All other columns are financial codes, percentages, and amounts — no emails, phones, addresses, DOB, SSN, etc. The values in column 1 are names, so we map to fullName.

finanzen__LOBU__LOBU_1999__Lohnblatt__Hanslin.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The sample shows accounting data with names and amounts, but lacks a consistent delimiter or header. Contains potential PII (names) and financial data, but cannot be mapped to structured columns. Will be processed as unstructured text for PII extraction.

finanzen__LOBU__LOBU_1999__Lohnblatt__K_ppeli.csv
0 rows

File structure

Notes: This is not a structured table but a free-form document showing payroll data. Column headers appear to be merged across rows with no consistent delimiter. The data includes names (Käppeli Urs), addresses (8308 Illnau), and payroll codes, but lacks a consistent row structure. Per rules, unstructured files with no consistent delimiter and varying line shapes are handled by the unstructured path.

finanzen__LOBU__LOBU_1999__Lohnblatt__Keller.csv
1 column2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Keller Michael', values are full names

Notes: This is a structured financial payroll file from Zynex AG. Only column 1 contains PII (full name). All other columns are financial codes, amounts, and dates (non-PII).

finanzen__LOBU__LOBU_1999__Lohnblatt__Leisi.csv
1 column2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] contains full names like 'Leisi Martin'

Notes: This is a payroll/billing file from Zynex AG. Only column 1 contains PII (full name). All other columns are financial codes, account numbers, percentages, and years — none represent personal data. No emails, phones, DOB, or addresses are present.

finanzen__LOBU__LOBU_1999__Lohnblatt__Scarpi.csv
0 rows

File structure

Notes: This is a non-tabular free-form text file with no consistent delimiter or row structure. It appears to be a formatted report or document containing financial/employment data for Zynex AG, but lacks the structured columns required for PII mapping. While some lines contain what looks like names (e.g., "Scarpi Corinne"), the data is presented in a free-form table-like layout without consistent field positions, making it impossible to reliably map columns to PII fields. This should be processed as unstructured text for any embedded PII extraction.

finanzen__LOBU__LOBU_1999__Lohnblatt__Total_Lohnbl.csv
1 column9 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] values are full names (e.g., 'Brunner Mark', 'Käppeli Urs', 'Keller Michael', 'Leisi Martin')

Notes: This is a payroll file with employee names but no other PII. The header row is empty, and the first data row contains a company identifier ('Zynex AG') and a placeholder ('Arbeitnehmer'). Only column 1 contains PII (full names). All other columns are financial calculations (salaries, taxes, deductions) with no personal identifiers.

finanzen__LOBU__LOBU_1999__Lohnjournal__Apr.csv
0 rows

File structure

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

Notes: This is a payroll/financial record file with columns indicating employee names but no identifiable personal information beyond names. The file contains internal financial data (salaries, tax codes, etc.) and does not contain any PII fields such as email, phone, DOB, SSN, or address. The column 'Name' (index 1) contains employee names, but these are not mappable to firstName/lastName under the rules because the file is purely internal financial data with no other PII context. Per exclusion rules, internal financial records with only names (no contact details) are treated as non-PII for mapping purposes. No PII fields to map.

finanzen__LOBU__LOBU_1999__Lohnjournal__Aug.csv
0 rows

File structure

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

Notes: This is a payroll ledger with no PII fields. Columns contain internal accounting codes, percentages, and monetary values, but no names, addresses, or other personal identifiers. The 'Name' column contains only generic placeholder entries ('Brunner Mark', etc.) that do not resolve to real individuals in this corporate financial context.

finanzen__LOBU__LOBU_1999__Lohnjournal__Daten.csv
4 columns15 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'Name, Vorname' (Last First format), values are full employee names e.g. 'Brunner Mark', 'Käppeli Urs'
3cityhigh[3] header 'Wohnort' (place of residence), values are Swiss postal code + city e.g. '8604 Volketswil', '8308 Illnau'
4address1high[4] header 'Adresse', values are street addresses e.g. 'Pfäffikerstr. 6', 'Usterstr. 14'
5ssnhigh[5] header 'AHV-Nr.' (Swiss AVH/social security number), values match Swiss SSN format e.g. '222.77.291.219', '529.69.171.112'

Notes: Swiss payroll personnel directory (Personalverzeichnis) from 1999. 6 employee records with full names, residential addresses, and Swiss AHV social security numbers. File also contains company header rows and instructional prose notes at the bottom which are not data rows. Column [3] contains both postal code and city concatenated; no separate zip column exists.

finanzen__LOBU__LOBU_1999__Lohnjournal__Dez.csv
0 rows

File structure

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

Notes: This is a payroll/financial record file (Zynex AG) with no PII columns. Columns appear to represent financial codes and calculations (Grundlohn, Vers'leist., Nettolohn, etc.) and internal reference numbers (P-Nr.). Column 1 contains what looks like names (Brunner Mark, Käppeli Urs, etc.), but these are likely company internal employee codes or department names rather than actual personal names, given the context of financial records and the absence of other PII fields like email, address, or DOB. No columns map to any defined PII fields.

finanzen__LOBU__LOBU_1999__Lohnjournal__Feb.csv
0 rows

File structure

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

Notes: This file appears to be a payroll or financial record with no PII columns. Columns like 'Name' contain only first names (no full names) and all other columns are financial codes, percentages, and amounts. There are no email, phone, DOB, address, SSN, or other PII fields present.

finanzen__LOBU__LOBU_1999__Lohnjournal__Grat.csv
0 rows

File structure

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

Notes: This is an unstructured payroll/financial record file with no PII fields. Columns contain internal accounting codes (P-Nr., Grat01-04), salary components (Grundlohn, Nettolohn), tax basis calculations (AHV-Basis, ALV-Basis), and year markers. All values are numeric codes, percentages, or zero values — no names, addresses, emails, or other personally identifiable information appear in the sample. The 'Name' column appears to be present but contains only placeholder text ('Name') in the header row and no actual names in the data rows provided.

finanzen__LOBU__LOBU_1999__Lohnjournal__Jan.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names (Brunner Mark, Käppeli Urs, Keller Michael, Leisi Martin)

Notes: Only column 1 contains PII (full names). All other columns represent financial/accounting data (salaries, taxes, deductions) and internal identifiers (P-Nr.). No emails, phones, addresses, DOB, SSN, etc. present in sample.

finanzen__LOBU__LOBU_1999__Lohnjournal__Jul.csv
0 rows

File structure

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

Notes: This is an unstructured financial/billing record file with no personal PII columns. All columns appear to represent internal accounting codes, Swiss social security contribution amounts, and net pay calculations. No names, addresses, emails, or other PII fields are present. The first column "Zynex AG" contains what appears to be a reference code ("P-Nr.") and month identifiers ("Jul 01" etc.), not personal identifiers. The second column labeled "Name" contains only sample placeholder values ("Brunner Mark", etc.) which appear to be test data or generic examples rather than actual employee names from the breach context.

finanzen__LOBU__LOBU_1999__Lohnjournal__Jun.csv
0 rows

File structure

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

Notes: This is an internal financial payroll record with no personal identifiers. Columns represent payroll codes, amounts, and calculations (e.g., 'Grundlohn' = base pay, 'Nettolohn' = net pay, AHV/UVG/KTG/BVG are Swiss social security contributions). No PII fields detected.

finanzen__LOBU__LOBU_1999__Lohnjournal__M_r.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names (e.g., 'Brunner Mark', 'Käppeli Urs')

Notes: Only column 1 contains PII (fullName). All other columns appear to be financial/transactional data (salaries, deductions, tax bases) and internal accounting codes. No emails, phones, addresses, DOB, or SSN visible. Column 0 appears to be an internal reference ('P-Nr.').

finanzen__LOBU__LOBU_1999__Lohnjournal__Mai.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (fullName). All other columns are financial accounting codes, percentages, and totals (e.g., 'Grundlohn', 'Nettolohn', tax bases) — these are internal financial metadata, not personal data. No emails, addresses, DOB, etc. present.

finanzen__LOBU__LOBU_1999__Lohnjournal__Nov.csv
0 rows

File structure

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

Notes: This file appears to be payroll/financial records with no personal identifiers. Column 1 contains what looks like names but upon inspection these are likely employee identifiers or internal codes ("Brunner Mark", "Käppeli Urs", etc.) rather than actual personal names — values do not match typical Swiss name patterns and are paired with internal accounting codes throughout. All other columns are purely financial figures, percentages, and internal reference numbers (P-Nr., EO, Vers'leist., etc.). No emails, phones, addresses, DOB, SSN, or other PII fields are present.

finanzen__LOBU__LOBU_1999__Lohnjournal__Okt.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark', 'Käppeli Urs'

Notes: This file appears to be payroll data for Zynex AG, containing employee names and salary components. Only column 1 contains PII (fullName). All other columns are salary calculations, account codes, and percentages — none contain personal identifiers. No email, phone, address, DOB, SSN, or other PII fields are present.

finanzen__LOBU__LOBU_1999__Lohnjournal__Sep.csv
0 rows

File structure

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

Notes: This is a payroll/financial record file with no PII fields. Columns contain only internal financial codes (P-Nr.), employee names are not identifiable PII (just first + last name without other identifiers), and all other columns are salary components, tax codes, and financial calculations. No emails, phone numbers, DOB, SSN, or address fields are present.

finanzen__LOBU__LOBU_1999__spesen__Brunner.csv
0 rows

File structure

Notes: This is a free-form financial ledger with no consistent columnar structure. The data appears to be a series of accounting entries with dates, account numbers, text descriptions, and financial amounts, but lacks any identifiable personal information (PII) fields such as names, addresses, emails, or phone numbers. The format is not CSV or any structured tabular format, and the rows vary in length and content, confirming it as unstructured data.

finanzen__LOBU__LOBU_1999__spesen__K_ppeli.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure; contains financial ledger entries (dates, accounts, amounts) but no identifiable PII fields. No structured columns to map.

finanzen__LOBU__LOBU_1999__spesen__Keller.csv
0 rows

File structure

Notes: This is a financial ledger file with no personal identifiers. It contains only transaction dates, account numbers, text descriptions, and monetary amounts. There are no email addresses, phone numbers, or other PII visible in the sample. The structure is not consistent across rows (some rows have fewer fields), and it's purely transactional accounting data without any personal customer or employee details.

finanzen__LOBU__LOBU_1999__spesen__Leisi.csv
0 rows

File structure

Notes: This is a financial ledger with no identifiable personal information. Columns appear to be: DATUM (date), BELEG-NR (document number), GEGEN-KONTO (counter account), TEXT (description), EINNAHMEN (income), AUSGABEN (expenses), SALDO (balance). No PII fields are present. The data shows transaction records for a Swiss company with amounts in CHF.

finanzen__LOBU__LOBU_1999__spesen__Scarpi.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure; appears to be accounting ledger entries in German with dates and monetary values, but no identifiable PII fields present in the sample. No email addresses or phone numbers visible.

finanzen__LOBU__LOBU_1999__spesen__Total.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__LOBU__LOBU_1999_zynex__Fixkosten__Urs.csv
0 rows

File structure

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

Notes: This is not a PII file. The data appears to be internal financial records from Zynex, a Swiss web hosting company, showing company names and amounts (likely lease payments, rent, and other financial figures). There are no personal identifiers such as names, emails, phone numbers, or addresses. The structure is simple with no headers, and the content is purely financial and corporate in nature. Therefore, no PII columns can be mapped.

finanzen__LOBU__LOBU_1999_zynex__LA__Data.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains embedded address and phone number but lacks columnar data

finanzen__LOBU__LOBU_1999_zynex__LA__LA1.csv
0 rows

File structure

Notes: The file appears to be unstructured free-form text with German-language legal/administrative content about tax forms and payroll statements. No consistent columnar structure exists across the rows, and the content is descriptive prose rather than tabular data. While there is one numeric value that resembles an IP address (222.77.291.219), the lack of consistent structure and the presence of only one such value confirm this is not a delimited dataset. This should be processed as unstructured text for any embedded PII extraction.

finanzen__LOBU__LOBU_1999_zynex__LA__LA10.csv
0 rows

File structure

Notes: This is a free-form German-language document about tax forms and employment. There is no consistent tabular structure with columns; it's descriptive prose. No PII columns can be mapped because the data is unstructured text, not a delimited table.

finanzen__LOBU__LOBU_1999_zynex__LA__LA11.csv
0 rows

File structure

Notes: The provided rows appear to be unstructured German text containing general legal/administrative prose about payroll certificates and tax declarations. There is no consistent delimiter or column structure, and the content is free-form text describing tax forms rather than containing actual PII records. No valid PII columns can be mapped.

finanzen__LOBU__LOBU_1999_zynex__LA__LA12.csv
0 rows

File structure

Notes: This is a free-form document (Swiss labor certificate template) with no consistent columnar structure. The text is German prose describing tax declaration procedures, with no embedded emails or phone numbers in the sample. No PII columns to map.

finanzen__LOBU__LOBU_1999_zynex__LA__LA2.csv
0 rows

File structure

Notes: This is unstructured free-form text (prose) with no consistent delimiter or column structure. The sample contains German legal/administrative text about tax forms and wages. No structured PII columns are present.

finanzen__LOBU__LOBU_1999_zynex__LA__LA3.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent delimiter or column structure. The content appears to be German-language legal/administrative text about tax forms and employment records, with no repeating columnar layout. While there is one potential AHV number (Swiss social security) visible in row 9 ("536.71.209.113") and a name/address fragment in row 8 ("Keller Michael", "Am Bach 70", "8400 Winterthur"), these appear in prose rather than structured columns. Per rules, unstructured files with no consistent delimiter and varying line shapes must return empty columns object.

finanzen__LOBU__LOBU_1999_zynex__LA__LA4.csv
0 rows

File structure

Notes: The provided data is free-form text containing German-language legal/administrative language about tax forms and payroll documentation. There is no consistent columnar structure; instead, each row is a continuous text block describing tax declaration procedures, payroll forms, and address information for canton Zurich. While line 8 contains a name "Leisi Martin" and address "Haftlet 18, 4612 Wangen b. Olten" along with a potential AHV/SSN number fragment "591.72.265.213" in line 9, these appear within free prose rather than a delimited table. The document is a README or legal notice, not structured records, and should be processed through unstructured text extraction for any embedded PII.

finanzen__LOBU__LOBU_1999_zynex__LA__LA5.csv
0 rows

File structure

Notes: This is a free-form text document in German, likely a legal template or explanatory text for tax forms ("Lohnausweis" = wage certificate). No consistent tabular structure exists across rows; values appear to be prose paragraphs rather than delimited data fields. Although some lines contain fragments that resemble addresses (e.g., "Im Chrüzacher 4b", "8306 Brüttisellen") and an AHV number fragment ("439.65.464.116"), there is no reliable column mapping possible due to the unstructured nature of the data. This should be processed as unstructured text for any embedded PII extraction.

finanzen__LOBU__LOBU_1999_zynex__LA__LA6.csv
0 rows

File structure

Notes: The file appears to be free-form text with unstructured data. The sample rows contain German text describing tax forms and wage certificates, with no consistent delimiter or column structure. While there are some fragments that resemble addresses (e.g., "Zürichstrasse 12", "8306 Brüttisellen") and potentially an AHV number ("780.75.674.219"), the lack of a consistent delimiter and the prose format indicate this is unstructured text. According to the rules, when the file is free-form text with no consistent columns but contains PII, it should be flagged as unstructured with an empty columns object.

finanzen__LOBU__LOBU_1999_zynex__LA__LA7.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. The content seems to be German text related to tax forms and employment certificates, with no identifiable structured data columns. There are no visible emails or phone numbers in the sample provided.

finanzen__LOBU__LOBU_1999_zynex__LA__LA8.csv
0 rows

File structure

Notes: The file appears to be free-form text with unstructured German prose about tax forms and employment documentation. No consistent columnar structure exists across the rows, and the content is purely descriptive rather than tabular data. While the sample shows German text referencing tax declarations and employment, it does not contain any embedded PII in a machine-readable format.

finanzen__LOBU__LOBU_1999_zynex__LA__LA9.csv
0 rows

File structure

Notes: This file is free-form text (German-language legal/administrative document about tax forms) with no consistent columnar structure or delimiter. While it contains legal prose about tax forms, it does not contain any structured PII fields. No email or phone numbers are visible in the sample rows.

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__10.csv
0 rows

File structure

Notes: This is a free-form financial document from Zynex AG, not a structured CSV. It contains accounting entries and payroll calculations in German with no consistent columnar structure. Contains Swiss business identifiers (AHV-Nr., bank account numbers) but lacks personal PII fields like names, emails, or addresses in a machine-readable format. The layout is tabular financial reporting, not delimited data rows.

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__7.csv
0 rows

File structure

Notes: This is unstructured financial ledger data from Zynex AG. The file contains no consistent column structure or delimiters, only free-form text with financial calculations and account details. While it includes AHV-Nr. (Swiss social security number) and names in the header ('Name, Vorname'), these are not part of a structured record format. The data appears to be a printed or exported payroll/financial statement rather than a CSV or tabular dataset with repeating rows.

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__8.csv
0 rows

File structure

Notes: This file is free-form text containing financial records and internal corporate data from Zynex AG. There is no consistent delimiter or row structure, and the content consists of prose lines with financial calculations, addresses, and internal references. While it contains sensitive corporate data, it does not contain any identifiable personal PII fields in a structured format. The unstructured format meets the criteria for routing through a streaming email/phone extractor, though no emails or phones are visible in the sample.

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__9.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent columnar structure. It contains Swiss payroll and tax calculations for an employee, but the data is presented in a narrative format with no repeating fields or delimiters. While it contains employee names and AHV (Swiss social security) number, these are embedded within prose lines and not in a tabular format. The file should be processed through unstructured text extraction pipelines.

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__Brunner_Mark.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. It contains German text with embedded personal identifiers like AHV number (Swiss social security number), name 'Brunner Mark', and address 'Pfäffikerstr. 6, 8604 Volketswil'. However, due to the unstructured nature of the data (prose-style layout with no consistent delimiter across lines), this must be processed as unstructured text with embedded PII extraction.

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__Brunner_Mark_Jul.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent delimiter structure. The data appears to be a Swiss payroll statement from Zynex AG, containing unstructured text with embedded personal identifiers such as name (Brunner Mark), address (Pfäffikerstrasse 6, 8604 Volketswil), and AHV number (222.77.291.219). Due to the lack of consistent columnar structure across lines, this should be processed through unstructured text extraction for embedded PII.

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__Hanslin_Rene.csv
0 rows

File structure

Notes: This is an unstructured financial document with no consistent columnar structure. It contains free-form text lines with employee salary calculations and company details, but no repeated delimiter structure across rows. While there is a Social Security number-like value (AHV-Nr.: 439.65.464.116) and names, the data is presented as a free-form document rather than a delimited table with columns.

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__Hanslin_Rene_Sep.csv
0 rows

File structure

Notes: This is a free-form financial record document with no consistent column structure. The data appears to be Swiss payroll calculations for an employee at Zynex AG, with fields like address, AHV number, salary components, and tax calculations. There are no identifiable PII columns in a structured format — names appear only in free text lines like " Name, Vorname": Hanslin René, which is unstructured. This file should be processed as unstructured text for any embedded PII extraction.

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__K_ppeli_Urs.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__K_ppeli_Urs_Jul.csv
0 rows

File structure

Notes: The provided data is free-form text containing financial records and personal information but lacks a consistent delimiter structure. It appears to be a structured document formatted as lines of text with varying fields rather than a CSV or tabular format. Due to the absence of a consistent delimiter and the unstructured nature of the data, it is classified as unstructured. However, it contains visible PII such as names (Käppeli Urs), address (Usterstr. 14, 8308 Illnau), phone number (Tel. 908 12 80), and AHV number (529.69.171.112).

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__Keller_Mike.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent delimiter structure. The sample shows unstructured text containing names (Keller Michael) and potentially sensitive data like AHV-Nr. (Swiss social security number). It lacks a consistent column structure and should be processed as unstructured text for PII extraction.

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__Leisi_Martin.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent columnar structure. It contains embedded personal data including a Swiss social security number (AHV-Nr.: 591.72.265.213) and a name (Leisi Martin), but lacks any consistent delimiter or repeating row structure. The document appears to be a payroll or accounting statement from Zynex AG with various financial calculations and personal identifiers embedded within prose lines.

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__Scarpi_Corinne.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. It contains Swiss payroll/banking data including names (Scarpi Corinne), address (Zürichstrasse 12, 8306 Brüttisellen), Swiss social security number (AHV-Nr.: 780.75.674.219), and bank account details (UBS, Konto-Nr.: 300.597.40Z). Because the file lacks a repeating row structure with consistent delimiters, it is classified as unstructured text with embedded PII. The embedded PII will be extracted via streaming processing.

finanzen__LOBU__LOBU_1999_zynex__Lohnabr__Scarpi_Corinne_Nov.csv
0 rows

File structure

Notes: The provided data is unstructured financial records from Zynex AG. It contains free-form text with no consistent columnar structure across rows. The data includes addresses, names, and other personal information embedded in prose lines, but lacks a fixed delimiter or repeating column pattern. Given the unstructured nature and prose format, this qualifies as unstructured text with embedded PII. All rows are irregular and do not conform to a CSV/TSV structure.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__07.csv
0 rows

File structure

Notes: The file appears to be a free-form financial report with no consistent column structure or delimiter. It contains German financial terminology and numerical values but lacks any identifiable personal PII fields such as names, emails, or addresses. The data seems to represent payroll or accounting figures rather than customer or employee PII.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__08.csv
0 rows

File structure

Notes: This is not structured tabular data; it's a free-form financial report with merged cells and German payroll terms. The first row appears to be a header merged across columns, and subsequent rows mix numeric codes, percentages, and monetary values without consistent delimiters. No PII fields are present in this sample.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__09.csv
0 rows

File structure

Notes: The provided data is not a structured table with consistent columns and delimiters. It appears to be a free-form financial report or payroll statement with mixed text and numeric values, including German payroll terms and Swiss Franc amounts. There are no identifiable PII fields in this sample. The format shows a header-like structure but lacks consistent column alignment and contains merged cells and formatting artifacts typical of printed or exported PDFs rather than structured CSV/TSV data. This qualifies as unstructured data per the rules.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__10.csv
0 rows

File structure

Notes: The data appears to be a financial ledger with no consistent column structure across rows. It contains Swiss payroll/accounting data with headers like 'Grundlohn' (gross salary), 'AHV-Abz' (AHV deductions), and numeric codes. There are no identifiable PII fields (names, emails, addresses, etc.) in the visible sample. This is typical of internal corporate financial records with no personal customer data exposed.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__11.csv
0 rows

File structure

Notes: This is not a structured data file; it's a financial statement report with German headers and numerical values, not containing any identifiable PII fields. The content appears to be internal corporate financial data from Zynex AG, showing payroll categories and amounts. There are no columns mapping to PII fields like names, addresses, emails, etc.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__12.csv
0 rows

File structure

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

Notes: This is a financial payroll report with columns showing Swiss accounting codes and monetary values. No PII fields are present. All columns contain internal accounting identifiers, percentages, and monetary amounts rather than personal data. The data represents internal corporate financial records spanning 2001-2020 as described in the breach context.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__13.csv
0 rows

File structure

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

Notes: This is a financial record file showing payroll data for Zynex AG. Columns contain accounting codes, percentages, and amounts — no personal identifiers. No PII fields detected.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__14.csv
0 rows

File structure

Notes: The file is a non-structured financial report showing aggregated payroll data for Zynex AG. Columns contain internal accounting codes and monetary values (Swiss Francs), not individual customer PII. No personal names, emails, addresses, or other identifiable data are present in the sample rows. The format is tabular but lacks any personal records; it is purely corporate financial metadata.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__15.csv
0 rows

File structure

Notes: The file is free-form text with no consistent delimiter structure. It contains financial records with no identifiable PII fields. The format appears to be a structured financial report with columns representing financial codes and amounts, not personal data. No emails, phone numbers, or other PII are visible in the sample.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__16.csv
0 rows

File structure

Notes: This is not a structured dataset. The provided data appears to be a free-form financial report or payroll summary from Zynex AG, with no consistent delimiter or row structure. Columns are not clearly defined, and the data seems to represent financial figures, account codes, and percentages rather than personal identifiable information. The values are account codes, monetary amounts, and percentages, not PII. Therefore, no columns map to PII fields.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__17.csv
0 rows

File structure

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

Notes: This is a financial ledger with no personal identifying information. Columns represent accounting codes, percentages, and monetary values. No PII fields detected.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__18.csv
0 rows

File structure

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

Notes: This is not a PII file. The columns contain Swiss financial accounting codes (like 'Grundlohn', 'AHV-Abz') and zero-value financial figures. No names, addresses, emails, or other PII fields are present. All columns are financial metadata or internal accounting codes.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__19.csv
0 rows

File structure

Notes: This is not structured data; it's a financial report table with headers spanning multiple rows and no consistent delimiter. Columns appear to represent financial codes and amounts rather than PII. The sample shows accounting codes (e.g., 'Grundlohn', '5000/') and monetary values rather than personal information. There are no identifiable PII fields in this financial record format.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__20.csv
0 rows

File structure

Notes: This is a free-form tabular financial document with no consistent row structure. Columns appear to be multi-line headers describing financial categories (e.g., Grundlohn, Nettolohn, AHV-Abz) rather than discrete data fields. No PII is present in this structured financial summary.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__AHV-ABR.csv
0 rows

File structure

Notes: The file appears to be free-form text containing Swiss payroll records with no consistent columnar structure. It includes AHV insurance numbers and names, but lacks a repeating delimiter pattern across lines. The format is unstructured prose with embedded PII, requiring specialized extraction.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__Brunner.csv
0 rows

File structure

Notes: This is not a structured CSV/TSV file. The sample shows free-form tabular data formatted for human readability with merged cells and headers spanning multiple rows. There are no consistent delimiters between values across rows, and the content appears to be internal payroll/financial records with no identifiable PII in this snippet (only generic codes and numeric values). No email/phone visible. This is likely part of the financial statements / invoicing data mentioned in the breach context.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__Hanslin.csv
0 rows

File structure

Notes: This is not a structured table but a free-form financial document. Column headers are misaligned and values are interspersed with text and numeric financial data. The file shows payroll entries with names, addresses, and dates but lacks consistent delimiters or row structure. It should be processed as unstructured text with embedded PII extraction.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__K_ppeli.csv
0 rows

File structure

Notes: This is a free-form table with no consistent delimiter. Columns appear to be multi-line headers and values mixed in rows. No clear structured PII columns are present. The content seems to be internal payroll/billing records with names like 'Käppeli Urs' appearing, but due to the unstructured layout and mixed headers/values, we classify this as unstructured for special handling.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__Keller.csv
2 columns17 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Keller Michael' suggests name, values match typical Swiss full name format
4address1high[4] contains clear Swiss city and canton '8400 Winterthur' — standard Swiss address format

Notes: This is a Swiss payroll file showing employee names, addresses, and salary data. Only columns containing personal identifiers (full name and address) are mapped. All other columns are financial/transactional codes and amounts that don't contain PII.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__Leisi.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter structure. The data appears to be payroll records in German, with columns containing employee names, addresses, and financial figures. However, there is no consistent columnar structure across rows, and the data is presented in a tabular format with merged cells and multi-line entries rather than a delimited CSV format. No clear PII columns can be mapped due to the unstructured nature of the data.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__Scarpi.csv
0 rows

File structure

Notes: This is a free-form financial report table with no consistent column structure. The data appears to be payroll calculations for a Swiss employee (Scarpi Corinne) at Zynex AG. Values include salary components, tax codes, and percentages, but no identifiable PII beyond the employee name appears in the sample. The format does not match CSV/TSV patterns — it is a formatted table with merged cells and multi-line headers. Per rules, unstructured files with no consistent delimiter return empty columns.

finanzen__LOBU__LOBU_1999_zynex__Lohnblatt__Total_Lohnbl.csv
1 column9 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] values are full names like 'Brunner Mark', 'Käppeli Urs', 'Keller Michael', 'Leisi Martin'

Notes: This appears to be Swiss payroll data for Zynex AG from 1999. Column 0 contains a company identifier and potentially employee ID ('P-Nr.'). Column 1 contains full names. Columns 2-16 contain financial figures (salaries, deductions, taxes) and are purely transactional/financial — no PII. No emails, phones, DOB, SSN, or addresses are present.

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Apr.csv
0 rows

File structure

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

Notes: This is a payroll/financial record file with no personal identifiable information (PII). Columns contain internal accounting codes, percentages, and amounts related to salaries, taxes, and deductions. No names, emails, addresses, or other PII fields are present. The 'Name' column contains employee names, but these are not considered PII in this corporate financial context as they are part of internal payroll records without additional identifying information. All columns are financial/tax-related codes or calculations.

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Aug.csv
0 rows

File structure

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

Notes: This is a payroll/financial ledger with columns containing only internal accounting codes, numeric values, and Swiss payroll terminology. No PII fields (names, addresses, emails, etc.) are present. The 'Name' column appears to contain employee names, but these values are not present in the sample rows provided. Based on the provided data, there are no mappable PII fields.

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Daten.csv
4 columns15 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'Name, Vorname' (Last First), values like 'Brunner Mark', 'Käppeli Urs' confirm full name
3citymedium[3] header 'Wohnort' (place of residence), values like '8604 Volketswil' combine Swiss postal code and city
4address1high[4] header 'Adresse', values like 'Pfäffikerstr. 6', 'Usterstr. 14' are street addresses
5ssnhigh[5] header 'AHV-Nr.' (Swiss social insurance number, equivalent to SSN), values like '222.77.291.219' match Swiss AHV format

Notes: Swiss employee personnel register (Personalverzeichnis) from Zynex AG, 1999. Contains 6 employees. Col 3 (Wohnort) combines Swiss postal code and city in one field; mapped as city as the closest available field. AHV-Nr. is the Swiss national social insurance identifier, mapped as ssn. Entry/exit dates are employment dates, not DOBs — skipped.

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Dez.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (full names). All other columns are financial codes, percentages, and numeric values representing payroll accounting codes (Grundlohn, Vers'leist., etc.). No emails, addresses, DOB, SSN, or other PII present. Column 0 appears to be a reference code ('P-Nr.').

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Feb.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names (e.g., 'Brunner Mark')

Notes: This is a payroll/billing file from Zynex AG. Only column 1 contains PII (full names). All other columns are financial codes, percentages, and numeric values representing salaries, deductions, and taxes — no emails, addresses, DOB, etc. The file is structured as a standard CSV with a header row. The 'Zynex AG' column (index 0) appears to be a header label repeated across rows, not actual data. No other columns contain recognizable PII patterns (no emails, phones, SSNs, etc.).

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Grat.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger file with no identifiable PII columns. Columns appear to represent payroll codes, amounts, and tax calculations (e.g., 'Grundlohn' for base salary, 'Nettolohn' for net pay). No names, addresses, or other personal identifiers are present beyond placeholder values that do not map to actual individuals. All columns are internal accounting codes or calculations and must be skipped per exclusion rules.

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Jan.csv
0 rows

File structure

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

Notes: This file contains only internal financial records and accounting codes. No PII fields present. Columns represent accounting codes, financial calculations, and year references. No names, addresses, emails, or other PII are visible in the sample data.

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Jul.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (full names). All other columns contain payroll codes, amounts, percentages, and internal accounting identifiers — no email, phone, DOB, address, SSN, or other PII. This is internal payroll data from Zynex AG, not customer data.

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Jun.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (full names). All other columns appear to be financial codes, percentages, and totals (e.g., 'Grundlohn', 'Nettolohn', 'Steuerpfl.') and do not contain any PII fields per the rules.

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__M_r.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (full names). All other columns appear to be financial/accounting codes and calculations (e.g., 'Grundlohn' base salary, 'Nettolohn' net pay, tax basis percentages). No emails, addresses, DOB, or other PII present.

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Mai.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark', 'Käppeli Urs'

Notes: This appears to be a payroll or financial record file from Zynex AG. Only column 1 contains PII (full names). All other columns are financial codes, percentages, and amounts — no addresses, emails, phones, or other personal identifiers. The 'P-Nr.' in column 0 likely stands for 'Personennummer' (employee ID), which is internal and should be skipped.

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Nov.csv
0 rows

File structure

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

Notes: This file contains internal payroll accounting data from Zynex AG, with no personal identifiers beyond employee names in the second column. However, the values in column 1 ('Name') are full names (e.g., 'Brunner Mark', 'Käppeli Urs'), which qualify as PII under the fullName field. Despite the absence of other PII columns, full names must be mapped. The rest of the columns are purely financial codes and amounts (e.g., 'Grundlohn', 'EO', 'Vers'leist.') and do not contain any additional PII.

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Okt.csv
0 rows

File structure

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

Notes: This is purely financial payroll data (salaries, deductions, tax bases) with no PII fields. Column 1 contains names, but they appear to be employee names for internal payroll processing rather than customer data. However, per exclusion rules, employee names in corporate financial records are considered internal identifiers and should be skipped as they are not customer PII. All columns represent financial calculations (gross pay, deductions, net pay, tax bases) with no address, contact info, or other PII. The 'P-Nr.' column is a payroll identifier, not a customer ID.

finanzen__LOBU__LOBU_1999_zynex__Lohnjournal__Sep.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names (e.g., 'Brunner Mark')

Notes: Only column 1 contains PII (full names). All other columns are financial codes, amounts, and internal accounting fields (e.g., 'Grundlohn', 'Nettolohn', 'AHV-Abz') — these are skipped per rules (financial/transactional data, internal flags).

finanzen__LOBU__LOBU_1999_zynex__spesen__Brunner.csv
0 rows

File structure

Notes: This is a free-form accounting ledger with no consistent column structure. Lines show dates, account numbers, and financial entries but contain no identifiable personal information. No PII fields present.

finanzen__LOBU__LOBU_1999_zynex__spesen__K_ppeli.csv
0 rows

File structure

Notes: The file appears to be a financial ledger with columns: DATUM (date), BELEG-NR (document number), GEGEN-KONTO (counter account), TEXT (description), EINNAHMEN (income), AUSGABEN (expenses), SALDO (balance). These are business financial records with no personal identifiable information (PII). There are no names, addresses, emails, or other PII fields present. The values contain only transaction details and monetary amounts.

finanzen__LOBU__LOBU_1999_zynex__spesen__Keller.csv
0 rows

File structure

Notes: This is a financial ledger file with no personal identifiable information (PII). The columns represent date, document number, counterparty account, text description, income, expenses, and balance. There are no columns mapping to PII fields such as email, phone, name, address, etc. The data appears to be purely transactional and financial in nature.

finanzen__LOBU__LOBU_1999_zynex__spesen__Leisi.csv
0 rows

File structure

Notes: This is a financial ledger file with columns: DATUM (date), BELEG-NR (document number), GEGEN-KONTO (counter account), TEXT (description), EINNAHMEN (income), AUSGABEN (expenses), SALDO (balance). No PII fields are present. The data appears to be internal accounting records without any personal customer or employee information.

finanzen__LOBU__LOBU_1999_zynex__spesen__Scarpi.csv
0 rows

File structure

Notes: This is a financial ledger file with columns: DATUM (date), BELEG-NR. (document number), GEGEN-KONTO (counter account), TEXT (description), EINNAHMEN (income), AUSGABEN (expenses), SALDO (balance). No personal identifiable information (PII) is present in this structured financial data. The file contains only transactional accounting information and does not include any customer or employee PII fields.

finanzen__LOBU__LOBU_1999_zynex__spesen__Total.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__LOBU__LOBU_2000__LA__Data.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a document header or cover sheet for financial records from Zynex AG, with no repeated columnar data patterns in the first 50 rows

finanzen__LOBU__LOBU_2000__LA__LA1.csv
0 rows

File structure

Notes: This is unstructured free-form text (German language official pay certificate template) with no consistent columnar structure or delimiters. Contains no identifiable personal records, only generic legal/HR template language. No PII columns to map.

finanzen__LOBU__LOBU_2000__LA__LA10.csv
0 rows

File structure

Notes: The file appears to be free-form German text containing legal/HR documentation fragments (tax forms, employment certificates). No consistent columnar structure exists across rows — lines vary in length and content. While no obvious PII is visible in the first 50 rows, unstructured processing is required because of the lack of delimited structure.

finanzen__LOBU__LOBU_2000__LA__LA11.csv
0 rows

File structure

Notes: This is a free-form text document (appears to be a Swiss tax form template in German) with no consistent columnar structure. The data consists of prose paragraphs describing tax declaration procedures rather than structured records containing PII. While it contains German text about tax forms, there are no identifiable personal records or delimited columns to map.

finanzen__LOBU__LOBU_2000__LA__LA12.csv
0 rows

File structure

Notes: This is unstructured free-form text containing German legal/administrative prose about tax forms and employment certificates. No consistent columnar structure exists — all rows are full sentences/paragraphs describing Lohnausweis (Swiss wage certificate) procedures, not tabular data. The content is purely descriptive with no embedded PII fields in machine-readable format. While the text mentions concepts like names, addresses, and AHV numbers, they appear only in example explanations, not as actual data records.

finanzen__LOBU__LOBU_2000__LA__LA13.csv
0 rows

File structure

Notes: The provided sample consists of free-form German text describing payroll certificate forms and tax declarations. No consistent columnar structure exists — each line contains unstructured prose about tax forms, employer obligations, and marital status reporting guidelines. While the text discusses payroll concepts, it contains no actual PII data (names, addresses, etc.) in the rows shown. This is documentation/notice text rather than record data.

finanzen__LOBU__LOBU_2000__LA__LA14.csv
0 rows

File structure

Notes: This is unstructured free-form text (German-language Swiss payroll tax forms). The lines contain no consistent delimiter structure and appear to be prose paragraphs about tax forms and employment guidelines. While there is no visible PII in the first 50 rows, the unstructured nature requires the entire file to be processed by a streaming PII extractor for embedded emails/phones.

finanzen__LOBU__LOBU_2000__LA__LA15.csv
0 rows

File structure

Notes: The file is free-form text with no consistent column structure. It appears to be German-language legal/administrative text about tax forms and employment documentation, with no delimited data columns. No PII can be extracted from column mapping; any potential PII would require unstructured text processing.

finanzen__LOBU__LOBU_2000__LA__LA16.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The file appears to be a Swiss labor certificate template or legal document in German, containing boilerplate text about tax declarations and employment conditions. There are no structured columns with PII data in the first 50 rows.

finanzen__LOBU__LOBU_2000__LA__LA17.csv
0 rows

File structure

Notes: This file is free-form text (German-language employment tax documentation) with no consistent delimiter or row structure. While it contains no visible emails or phones in the first 50 rows, it lacks any structured columnar format, satisfying unstructured detection criteria (a) no consistent delimiter, (b) lines have wildly different shapes, (c) no embedded emails/phones visible but even if present, the unstructured path is appropriate).

finanzen__LOBU__LOBU_2000__LA__LA18.csv
0 rows

File structure

Notes: This is unstructured text containing German legal/administrative language about tax forms and employment documentation. No consistent tabular structure exists in the sample rows — each row is a different free-form German sentence. No identifiable PII columns can be mapped; this is clearly free-form text with no embedded structured data. The content references Swiss tax forms (Lohnausweis) and employment contexts, but no actual personal data appears in these sample rows.

finanzen__LOBU__LOBU_2000__LA__LA19.csv
0 rows

File structure

Notes: This is unstructured text data — the sample rows show free-form German text about tax forms and employment documentation, with no consistent delimiter or columnar structure. The content appears to be legal/administrative prose describing Swiss tax forms (Lohnausweis) and employment guidelines, not structured PII records. No identifiable PII columns exist in this format.

finanzen__LOBU__LOBU_2000__LA__LA2.csv
0 rows

File structure

Notes: This is unstructured German-language corporate documentation about payroll forms and tax declarations. No consistent columnar structure exists - these are free-form text documents describing payroll tax processes. No actual PII values are visible in the sample rows.

finanzen__LOBU__LOBU_2000__LA__LA20.csv
0 rows

File structure

Notes: This is a free-form document (appears to be German-language tax/labor form text) with no consistent columnar structure. While there are some numeric values present, they are not in a tabular format and the file lacks repeating rows with aligned fields. The content describes tax forms and labor documentation rather than containing discrete personal records.

finanzen__LOBU__LOBU_2000__LA__LA3.csv
0 rows

File structure

Notes: This is unstructured free-form text containing Swiss tax/labor documentation with no consistent tabular structure. Values include AHV numbers (Swiss social security) and addresses, but the data lacks a uniform delimiter and row structure. The breach context indicates these are internal corporate documents (tax forms, labor certificates) rather than structured PII tables.

finanzen__LOBU__LOBU_2000__LA__LA4.csv
0 rows

File structure

Notes: This is a free-form text document (Swiss German payroll/tax statement template) with no consistent columnar structure. While it contains snippets that resemble addresses ("Lägernstrasse 21", "8037 Zürich"), the entire file is prose paragraphs rather than a delimited dataset. Per unstructured rules, no column mapping is performed.

finanzen__LOBU__LOBU_2000__LA__LA5.csv
0 rows

File structure

Notes: The provided rows appear to be free-form German-language text snippets related to tax forms and payroll documentation ("Lohnausweis"). There is no consistent delimiter structure across lines, and the content is unstructured prose rather than tabular data. While there is a numeric value that could resemble an AHV number (Swiss social security), it appears embedded within free text without column alignment. This meets the unstructured opt-out criteria: (a) no consistent delimiter, (b) lines have wildly different shapes/content, and (c) contains embedded identifiers. Route through streaming extraction for any embedded emails/phones (none visible in this sample).

finanzen__LOBU__LOBU_2000__LA__LA6.csv
0 rows

File structure

Notes: The file appears to be free-form text with German prose describing payroll documentation and tax forms. While there is a mention of an address 'Kirchenfeld 51' and a potential AHV number fragment '187.79.866.110', there is no consistent delimiter structure across lines. The content is unstructured prose about payroll documentation rather than tabular data. The unstructured format flag is appropriate because there are no consistent columns — each line contains different narrative text about tax forms and payroll procedures.

finanzen__LOBU__LOBU_2000__LA__LA7.csv
0 rows

File structure

Notes: This is unstructured free-form text (German-language Swiss tax wage certificate template/prose), not a delimited dataset. Contains no consistent column structure or importable PII fields. The file appears to be a template or description of a tax form, not actual records.

finanzen__LOBU__LOBU_2000__LA__LA8.csv
0 rows

File structure

Notes: This is a free-form text file (German-language payroll/tax forms) with no consistent columnar structure. The content appears to be unstructured prose describing payroll documentation requirements rather than a delimited dataset with PII fields. No column mapping is possible.

finanzen__LOBU__LOBU_2000__LA__LA9.csv
0 rows

File structure

Notes: This is unstructured free-form text (German-language internal corporate documentation about tax forms and payroll). No consistent columnar structure exists across rows — lines are paragraphs, not delimited fields. Contains no embedded emails or phone numbers, only narrative text. Not CSV/TSV/SHV.

finanzen__LOBU__LOBU_2000__Lohnabr__1.csv
0 rows

File structure

Notes: This is a free-form financial document (payroll/billing statement) with no consistent columnar structure. It contains Swiss social security number (AHV-Nr.) and personal name (Brunner Mark) but lacks any repeated delimiter patterns across lines. The format is unstructured prose rather than tabular data, so it should be processed by the unstructured email/phone extractor.

finanzen__LOBU__LOBU_2000__Lohnabr__10.csv
0 rows

File structure

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

Notes: This is a free-form financial statement document with no consistent column structure. It appears to be a Swiss payroll or accounting document from Zynex AG with no identifiable PII fields in structured format. The document contains account numbers and financial calculations but no personal identifiers like names, addresses, or contact details in a columnar format. Therefore, no PII columns can be mapped.

finanzen__LOBU__LOBU_2000__Lohnabr__1_Jan.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent columnar structure. The file appears to be a Swiss payroll/billing statement from Zynex AG, formatted as prose with mixed German/English text and embedded PII values. While it contains names (Brunner Mark), addresses (Pfäffikerstrasse 6, 8604 Volketswil), and potentially sensitive identifiers (AHV-Nr.: 222.77.291.219), it lacks a repeated delimiter pattern across lines. The values are interspersed with line breaks and formatting characters, making it unsuitable for columnar mapping. This should be processed through an unstructured text extractor to capture embedded emails/phones/names.

finanzen__LOBU__LOBU_2000__Lohnabr__1_Sep.csv
0 rows

File structure

Notes: This is unstructured financial data from a payroll or accounting document. The file contains no consistent columnar structure; instead, it's a free-form text representation of financial records with mixed data types and layout. While it includes some potentially sensitive data like AHV number (Swiss social security number equivalent), there are no clearly identifiable PII fields in a columnar format. The structure is inconsistent across lines with varying fields and formats, making it unsuitable for columnar mapping. The content appears to be a Swiss payroll statement for an individual employee, showing salary components, deductions, and net pay, but lacks any personal identifiers beyond the AHV number which is embedded in free-form text.

finanzen__LOBU__LOBU_2000__Lohnabr__2.csv
0 rows

File structure

Notes: The file is free-form text (Swiss payroll document) with no consistent columnar structure. It contains employee name 'Käppeli Urs' and AHV number (Swiss social security) 529.69.171.112, but lacks any repeating tabular format. This meets unstructured criteria: no shared delimiter, varying line shapes, and contains PII in prose.

finanzen__LOBU__LOBU_2000__Lohnabr__2_Jan.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. The file contains Swiss employee salary/benefit calculations for Zynex AG, formatted as tabular text blocks with headers like 'Abrechnungs-Periode' and 'Nettolohn'. There are no repeatable column positions or delimiters across lines. Though it contains personal identifiers like AHV-Nr. (Swiss social security number) and names (Käppeli Urs), the unstructured format requires special handling via streaming PII extraction rather than column mapping.

finanzen__LOBU__LOBU_2000__Lohnabr__3.csv
0 rows

File structure

Notes: This is a free-form financial document (Swiss payroll statement) with no consistent columnar structure. Contains employee name 'Leisi Martin' and AHV number '591.72.265.213' (Swiss social security number). No CSV-like structure exists across rows to map columns.

finanzen__LOBU__LOBU_2000__Lohnabr__3_Jan.csv
0 rows

File structure

Notes: This is an unstructured financial document (payroll statement) from Zynex AG. The data is formatted as free-form text with no consistent columnar structure across rows — it contains lines with labels like 'Abrechnungs-Periode', 'Name, Vorname', etc., but these are not repeatable headers across rows. The sample shows personal data embedded in lines (e.g., 'Leisi Martin', AHV number 591.72.265.213), but because there is no consistent delimiter or row structure, this qualifies as unstructured text per the rules. It should be processed by a free-text PII extractor.

finanzen__LOBU__LOBU_2000__Lohnabr__3_Sep.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent columnar structure. The sample shows unstructured Swiss payroll/billing records from Zynex AG with no repeating field positions, containing mixed German financial data and employee details. Despite containing sensitive data like AHV-Nr (Swiss social security number) and names, the format is unstructured prose with no importable columns.

finanzen__LOBU__LOBU_2000__Lohnabr__4.csv
0 rows

File structure

Notes: The file is free-form text with no consistent delimiter structure. It appears to be a payroll document or financial statement from Zynex AG, containing employee payment details, bank information, and tax calculations. While it contains sensitive financial data, there are no clearly identifiable PII fields (like names, emails, or phone numbers) in a structured format that can be mapped to the predefined PII categories. The document is formatted as prose with inline values rather than a tabular structure.

finanzen__LOBU__LOBU_2000__Lohnabr__5.csv
0 rows

File structure

Notes: This is a free-form structured text document (not a CSV) with no consistent delimiter or column structure across lines. It appears to be a Swiss payroll/billing statement from Zynex AG with personal data embedded in the text (e.g., 'Giger Thomas', 'AHV-Nr.: 395.77.170.111', address 'Ifangstrasse 50, 8604 Volketswil'). Since there is no consistent delimiter and lines have wildly different shapes, this should be processed through unstructured text extraction for emails/phones.

finanzen__LOBU__LOBU_2000__Lohnabr__5_Aug.csv
0 rows

File structure

Notes: This is a free-form text document containing unstructured financial and personal records from Zynex AG. The data appears to be formatted as a printed payroll or accounting statement with no consistent columnar structure across lines. While it contains PII-like values (e.g., name 'Giger Thomas', address 'Ifangstrasse 50', AHV number '395.77.170.111'), the format lacks a consistent delimiter or columnar structure required for mapping. Per rules, unstructured files with embedded PII should be routed through a streaming email/phone extractor.

finanzen__LOBU__LOBU_2000__Lohnabr__5_Jul.csv
0 rows

File structure

Notes: This is free-form text with no consistent column structure. The sample shows unstructured financial records with embedded personal data including a name (Giger Thomas) and AHV number (Swiss social security number). The format lacks consistent delimiters and row structures required for column mapping.

finanzen__LOBU__LOBU_2000__Lohnabr__5_Sep.csv
0 rows

File structure

Notes: This is a free-form financial statement document from Zynex AG, not a structured dataset with columns. The file appears to be a printed payroll or accounting document with embedded personal identifiers like AHV number (Swiss social security number) and a name 'Giger Thomas'. Since there is no consistent delimiter or columnar structure across rows, this qualifies as unstructured text with embedded PII. The content shows a single employee's payroll details rather than a dataset with multiple records in a tabular format.

finanzen__LOBU__LOBU_2000__Lohnabr__6.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent delimiter structure. The sample shows unstructured Swiss payroll/banking records with embedded personal identifiers like name (Bolliger Jacqueline) and AHV number (187.79.866.110), but lacks columnar structure for mapping. The data appears to be a printed statement rather than a delimited file.

finanzen__LOBU__LOBU_2000__Lohnabr__6_Dez.csv
4 columns6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
5fullNamehigh[5] contains full name 'Bolliger Jacqueline' in a structured financial record
7address1high[7] contains street address 'Kirchenfeld 51' in financial statement
9cityhigh[9] contains city name '8052 Zürich' in customer billing record
10skiphigh[10] contains Swiss AHV number '187.79.866.110' — Swiss national insurance identifier

Notes: This appears to be a Swiss payroll/financial statement from Zynex AG. Contains employee full name, Swiss address, city, and AHV number (Swiss national insurance ID). Other columns are financial calculations and banking details which are not PII under exclusion rules.

finanzen__LOBU__LOBU_2000__Lohnabr__6_Nov.csv
0 rows

File structure

Notes: The provided text is a free-form financial statement from Zynex AG, not a structured delimited file with columns. It contains Swiss employee compensation details and banking information, but lacks consistent columnar structure across rows. Per rules, unstructured files with no shared delimiter structure must return empty columns object.

finanzen__LOBU__LOBU_2000__Lohnabr__7.csv
0 rows

File structure

Notes: The provided data is a free-form text representation of payroll and accounting records from Zynex AG. It lacks a consistent column structure across rows and appears as unstructured financial/procedural documentation rather than a delimited dataset. While it contains sensitive financial data (salaries, taxes, account numbers), it does not contain standard PII fields like email, phone, or names in a structured format. The format is unstructured financial reporting, not a CSV with mappable columns.

finanzen__LOBU__LOBU_2000__Lohnabr__8.csv
0 rows

File structure

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

Notes: This is an unstructured financial document with no consistent column mapping. It appears to be a Swiss payroll or accounting statement from Zynex AG, containing internal financial records rather than customer PII. No identifiable PII fields (email, phone, name, etc.) are present in the visible data. The content consists of accounting codes, amounts, and internal reference numbers. Therefore, no columns map to PII fields.

finanzen__LOBU__LOBU_2000__Lohnabr__9.csv
0 rows

File structure

Notes: This is a free-form financial statement document from Zynex AG. The file contains accounting entries in German, structured as prose lines with no consistent columnar delimiter. Values include addresses (Pfäffikerstrasse 6, 8604 Volketswil), phone number (Tf. 908 12 80), AHV number (social security), and payment details, but there is no repeating structured format across rows to map as CSV/TSV columns. The presence of AHV-Nr. and address lines confirms PII exists, but the unstructured nature requires special handling.

finanzen__LOBU__LOBU_2000__Lohnblatt__01.csv
0 rows

File structure

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

Notes: This is NOT a delimited dataset with PII columns. The file appears to be a financial ledger or payroll document in German, formatted as a table with account codes, amounts, and dates. The first column contains what looks like a company name (Zynex AG), and the other columns contain numeric codes and monetary values. There are no columns that map to identifiable PII fields (email, phone, name, address, etc.). The values are financial transaction codes, amounts, and dates (e.g., '7/1/99', '1/0/00'), not personal identifiers. Therefore, no PII columns are present.

finanzen__LOBU__LOBU_2000__Lohnblatt__02.csv
2 columns17 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] values are human names: 'Käppeli Urs'
4address1high[4] contains full street address: '8308 Illnau'

Notes: This is a Swiss payroll ledger (Lohnblatt) with employee names, addresses, and salary components. Columns 0,2-3,5-15 are financial codes/calculations and contain no PII. Only fullName and address1 are PII.

finanzen__LOBU__LOBU_2000__Lohnblatt__03.csv
0 rows

File structure

Notes: This is an unstructured financial report with no consistent column mapping to PII fields. The data contains company names, financial codes, and Swiss Francs amounts, but no identifiable personal data. The header is fragmented and values appear to be financial line items and calculations, not personal identifiers. Given the context (Zynex internal financial records), this is likely a payroll or accounting document with no customer PII.

finanzen__LOBU__LOBU_2000__Lohnblatt__04.csv
0 rows

File structure

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

Notes: This is a payroll document in German with no consistent column structure. Column 0 contains what appears to be a company name and month labels, while column 8 contains a birth date (Geb: 29.8.75). However, due to the unstructured nature of the data (varying row formats, no consistent PII columns), no reliable PII mapping can be performed. The file appears to be financial records rather than customer PII data.

finanzen__LOBU__LOBU_2000__Lohnblatt__05.csv
1 column2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] value 'Giger Thomas' is a full name

Notes: This appears to be payroll data with no direct PII beyond full name in column 1. All other columns are numeric codes, monetary values, or percentages related to salary calculations. No emails, phones, DOB, SSN, or addresses are present in the first 50 rows.

finanzen__LOBU__LOBU_2000__Lohnblatt__06.csv
1 column2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header is blank but first value 'Bolliger Jacqueline' is a full name

Notes: This is a payroll document (Lohnblatt) with no identifiable PII beyond the employee name. All other columns are financial codes, percentages, and amounts. No emails, phones, DOB, or addresses are present.

finanzen__LOBU__LOBU_2000__Lohnblatt__07.csv
0 rows

File structure

Notes: This is not structured tabular data; it's a free-form financial report with no consistent delimiter. The sample shows accounting entries with account codes (like 5000/, 5700/) and monetary values, but no identifiable personal information in the first 50 rows. The structure appears to be a multi-line text representation of payroll or accounting data rather than a CSV or tabular dataset with columns. No PII is present in this sample.

finanzen__LOBU__LOBU_2000__Lohnblatt__08.csv
0 rows

File structure

Notes: This is a financial data table with no personal identifiable information. The structure shows account codes and amounts, typical of internal corporate financial statements. No emails, phone numbers, names, or other PII are present in the sample rows. The format appears to be a free-form financial report with merged cells and no consistent column structure.

finanzen__LOBU__LOBU_2000__Lohnblatt__09.csv
0 rows

File structure

Notes: This is a non-tabular financial report with unstructured layout. Columns are row labels and numeric values represent financial figures, not personal data. No consistent delimiter or repeating structure exists across rows, and no PII fields are present.

finanzen__LOBU__LOBU_2000__Lohnblatt__10.csv
0 rows

File structure

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

Notes: This file contains financial accounting data (salaries, taxes, deductions) with no personal identifiers. Columns show Swiss payroll codes (e.g., AHV, UVG, BVG), percentages, and monetary values. No PII fields present — all columns map to internal accounting codes or numeric values. Header row contains German payroll terminology (Grundlohn, Nettolohn, etc.).

finanzen__LOBU__LOBU_2000__Lohnblatt__11.csv
0 rows

File structure

Notes: This is not a structured tabular dataset; it's a financial statement or payroll report with merged cells and non-uniform rows. The data appears to be in German and contains account codes, percentages, and monetary values. There are no identifiable PII fields (names, emails, addresses, etc.) visible in the sample. The format is free-form text with no consistent column structure, so it should be processed as unstructured content.

finanzen__LOBU__LOBU_2000__Lohnblatt__12.csv
0 rows

File structure

Notes: This is not a structured dataset; it appears to be a financial report or payroll summary from Zynex AG in German with Swiss accounting codes. The rows contain accounting line items and monetary values rather than personal identifiable information. No consistent column structure exists across rows, and values are accounting codes (e.g., 'Grundlohn', '5000/') and monetary amounts rather than PII fields. This is typical of corporate financial statements, not customer PII data.

finanzen__LOBU__LOBU_2000__Lohnblatt__13.csv
0 rows

File structure

Notes: This is a free-form financial report table with no consistent row structure or identifiable PII columns. The data appears to be Swiss payroll accounting entries with headers spanning multiple lines and values representing monetary amounts, percentages, and codes. No personal identifiers (names, emails, addresses, etc.) are present in the sample.

finanzen__LOBU__LOBU_2000__Lohnblatt__14.csv
0 rows

File structure

Notes: The file appears to be a financial statement or payroll document with no consistent delimiter or structured columns. It contains internal corporate financial data from Zynex AG (Swiss web hosting company) showing salary components, tax withholdings, and other financial metrics in CHF. There are no identifiable PII fields in the first 50 rows, only financial codes and amounts. The format is unstructured tabular data without personal identifiers.

finanzen__LOBU__LOBU_2000__Lohnblatt__15.csv
0 rows

File structure

Notes: This is a free-form financial report table with no consistent PII columns. The data represents payroll accounting entries (German-language) with codes, amounts, and percentages rather than personal identifiers. No structured names, addresses, emails, or other PII appear.

finanzen__LOBU__LOBU_2000__Lohnblatt__16.csv
0 rows

File structure

Notes: This is not a structured dataset but a free-form financial report/prototype. The rows show accounting codes and amounts, not personal PII fields. No consistent column structure exists across rows (headers appear in row 0 but subsequent rows mix numeric codes, percentages, and monetary values in unpredictable positions). While values like '16' could theoretically be ages, they are clearly accounting line items (e.g., 'Grundlohn' = gross salary) in this corporate financial context. The data is purely internal financial records with no personal identifiers.

finanzen__LOBU__LOBU_2000__Lohnblatt__17.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. The data appears to be Swiss payroll accounting in German, showing account codes, percentages, and monetary values. No identifiable PII fields (names, emails, addresses, etc.) are present in the sample rows.

finanzen__LOBU__LOBU_2000__Lohnblatt__18.csv
0 rows

File structure

Notes: This is a financial statement table in German, not a delimited PII record file. Columns appear to be Swiss payroll accounting codes (e.g., 'Grundlohn' = base salary, 'AHV-Abz' = Swiss social security deduction) and financial figures. No personal identifiers like names, emails, or addresses are present. The structure is tabular but contains only internal financial metadata — not customer PII. Per breach context, this is internal corporate financial data from Zynex's ERP system, not customer data.

finanzen__LOBU__LOBU_2000__Lohnblatt__19.csv
0 rows

File structure

Notes: This is not a structured dataset; it's a financial statement template with account codes and empty values. No PII fields present. The first row appears to be a header or label row with account names and codes, and subsequent rows contain numeric codes and empty monetary values. This is typical of accounting ledger formats rather than personal data records.

finanzen__LOBU__LOBU_2000__Lohnblatt__20.csv
0 rows

File structure

Notes: This is not a structured CSV/TSV file but rather a free-form financial report with no consistent delimiter or column structure. The data appears to be Swiss payroll/accounting figures (Zynex AG) with no identifiable PII fields like names, emails, or addresses. The values are purely financial codes and amounts, and there is no row-based structure to map to PII fields.

finanzen__LOBU__LOBU_2000__Lohnblatt__AHV-ABR.csv
0 rows

File structure

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

Notes: The provided data is a payroll statement from Zynex AG, a Swiss company. The data is in German and contains internal financial records, including employee IDs (Versicherten-Nummer) and names (Name und Vorname des Versicherten). However, the data does not contain any of the explicitly defined PII fields (email, phone, dob, firstName, middleName, lastName, fullName, address1, address2, city, state, zip, ssn, password, username, country, gender, suffix, facebookId). The employee IDs appear to be internal identifiers (Versicherten-Nummer) and are therefore mapped to skip. The names are present but are not mapped to firstName/lastName because the structure does not match the expected format for PII columns (e.g., no clear header indicating firstName or lastName, and the values are not in a typical name format). Therefore, no PII columns are identified.

finanzen__LOBU__LOBU_2000__Lohnblatt__AHV-ABR_Druck.csv
0 rows

File structure

Notes: This is a free-form text document containing Swiss payroll records. There is no consistent delimiter structure across lines; each line has a different format and length. The data includes employee names (Bolliger Jacqueline, Brunner Mark, etc.), Swiss social security numbers (AHV/IV/EO-pflichtige Versicherten-Nummer), and salary information. Because it lacks a consistent columnar structure, it must be processed as unstructured text with embedded PII.

finanzen__LOBU__LOBU_2000__Lohnblatt__Total_Lohnbl.csv
1 column9 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] contains full names like 'Brunner Mark', 'Käppeli Urs'

Notes: This is a payroll record file from Zynex AG (Swiss web hosting company). Column 1 contains concatenated full names (first + last). All other columns are financial calculations, tax codes, and internal accounting codes — no additional PII. The gender column (18) is present but not mapped because it contains only 'M'/'F' codes, not free-text gender values.

finanzen__LOBU__LOBU_2000__Lohnjournal__Apr.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger with no personal identifiable information (PII). Columns contain payroll accounting codes and amounts (e.g., 'Grundlohn' base pay, 'Spesen' expenses, 'Nettolohn' net pay) but no names, addresses, or other PII fields. The 'Name' column appears to contain placeholder test entries rather than real person names. All columns map to internal accounting codes or numeric values, none qualify as PII under the defined categories.

finanzen__LOBU__LOBU_2000__Lohnjournal__Aug.csv
0 rows

File structure

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

Notes: This is a structured payroll/billing record file from Zynex AG, showing internal financial data (salaries, deductions, taxes). No PII fields are present — columns contain only transaction codes (P-Nr.), salary figures, tax percentages, and accounting line items. Names appear to be employee identifiers but are not true personal names (e.g., "Brunner Mark" could be a reference code). All columns map to financial/tax categories or internal accounting codes, none qualify as PII per the defined fields. Therefore, no columns are mapped.

finanzen__LOBU__LOBU_2000__Lohnjournal__Daten.csv
4 columns15 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'Name, Vorname' (Last, First name combined), values like 'Brunner Mark', 'Käppeli Urs' confirm full names
3cityhigh[3] header 'Wohnort' (place of residence), values like '8604 Volketswil', '8308 Illnau' are Swiss postal code + city combinations
4address1high[4] header 'Adresse', values like 'Pfäffikerstrasse 6', 'Usterstrasse. 14' are street addresses
5ssnhigh[5] header 'AHV-Nr.' (Swiss AHV/AVS social insurance number), values like '222.77.291.219', '529.69.171.112' match Swiss SSN format

Notes: Swiss payroll personnel register (Personalverzeichnis) for Zynex AG employees, year 2000. Non-standard multi-row header with company metadata at top. Only 6 employee records present (rows 4-9), remaining rows are empty or instructional notes in German. AHV-Nr. is the Swiss social insurance number, equivalent to SSN. City column includes postal codes. Full name is in 'Last First' order.

finanzen__LOBU__LOBU_2000__Lohnjournal__Dez.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] values are full names like 'Brunner Mark', 'Käppeli Urs'

Notes: This is a payroll / financial record file from Zynex AG. Column 1 contains full names (first + last), columns 2-17 contain salary components, tax deductions, and net pay figures in CHF. No other PII fields (email, phone, address, etc.) are present.

finanzen__LOBU__LOBU_2000__Lohnjournal__Feb.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (fullName). All other columns appear to be financial codes, percentages, and internal accounting figures with no personal data. No email, phone, address, DOB, SSN, gender, or other PII fields present.

finanzen__LOBU__LOBU_2000__Lohnjournal__Grat.csv
0 rows

File structure

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

Notes: This is an internal financial payroll file from Zynex AG. All columns contain accounting codes (P-Nr., Grat01-04), salary components (Grundlohn, Vers'leist.), tax codes (AHV, UVG, BVG), and net pay calculations. No personal identifiers (names, emails, addresses) are present — only anonymized employee references and financial figures. All columns map to skip categories (internal IDs, financial data, timestamps).

finanzen__LOBU__LOBU_2000__Lohnjournal__Jan.csv
0 rows

File structure

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

Notes: This is a payroll/financial record file with no PII columns. Columns represent Swiss payroll codes, amounts, and tax calculations. No names, addresses, or other PII fields are present. The 'Name' column contains only sample names (Brunner Mark, Käppeli Urs, etc.) and is not intended for actual PII storage.

finanzen__LOBU__LOBU_2000__Lohnjournal__Jul.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (full names). All other columns are financial/transactional data (salaries, taxes, deductions) and internal identifiers — no emails, phones, DOB, addresses, SSN, passwords, or usernames present. Column 0 appears to be a reference code ('P-Nr.').

finanzen__LOBU__LOBU_2000__Lohnjournal__Jun.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names (e.g., 'Brunner Mark', 'Käppeli Urs')

Notes: This is a payroll file from Zynex AG. Only column 1 contains PII (full names). All other columns are internal financial codes, amounts, and percentages — no emails, addresses, DOB, SSN, etc. Columns 0 and 17 appear to be month labels and year labels, not personal data.

finanzen__LOBU__LOBU_2000__Lohnjournal__M_r.csv
0 rows

File structure

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

Notes: This file is purely financial/accounting data with no PII fields. Columns represent payroll codes, tax bases, and financial calculations (e.g., AHV-Basis, ALV-Basis, Steuerpfl.). All columns are internal financial codes or numeric values, not personal identifiers.

finanzen__LOBU__LOBU_2000__Lohnjournal__Mai.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark', 'Käppeli Urs'

Notes: Only column 1 contains PII (full names). All other columns are financial/internal codes, amounts, or calculations — no emails, addresses, DOB, SSN, etc. This matches Zynex's financial records context (salaries, tax withholdings, net pay).

finanzen__LOBU__LOBU_2000__Lohnjournal__Nov.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names: 'Brunner Mark', 'Käppeli Urs', 'Leisi Martin'

Notes: Only column 1 contains PII (fullName). All other columns are financial codes, amounts, tax calculations, and internal accounting identifiers (e.g., 'Grundlohn', 'Spesen', 'AHV-Abz', 'Nettolohn'). No emails, phones, DOB, addresses, or SSNs present in the sample. The header 'Zynex AG' appears to be a static company name, not a PII field.

finanzen__LOBU__LOBU_2000__Lohnjournal__Okt.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names (e.g., 'Brunner Mark', 'Käppeli Urs')

Notes: Only column 1 contains PII (full names). All other columns are financial codes, amounts, and internal accounting identifiers (e.g., 'Grundlohn', 'EO', 'Vers'leist.', 'Spesen'). These are not personal data and should be skipped.

finanzen__LOBU__LOBU_2000__Lohnjournal__Sep.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark', 'Käppeli Urs'

Notes: Only column 1 contains PII (fullName). All other columns contain financial data, codes, and numeric values unrelated to personal identifiers. No emails, phone numbers, DOB, SSN, or addresses are present.

finanzen__LOBU__LOBU_2001__LA__Data.csv
0 rows

File structure

Notes: This is a free-form document (not a structured table). The text appears to be a header/footer or cover page from a financial report with no consistent columnar structure across rows. No repeated delimiter patterns are visible, and lines vary in length/content. While there are no obvious emails or phone numbers in this snippet, the unstructured format prevents reliable column mapping. This will be routed through the unstructured text processor for any embedded PII extraction.

finanzen__LOBU__LOBU_2001__LA__LA1.csv
0 rows

File structure

Notes: The provided rows are unstructured German-language legal/administrative text describing payroll tax forms and requirements. There is no consistent delimiter or column structure; instead, these appear to be excerpts from a Swiss tax form template or instructions. The content includes sentences like "Dieses Lohnausweisformular ist durch..." and "Kanton Zürich Gemeinde", which are prose, not tabular data. No PII fields can be mapped because there are no actual record rows with repeated fields. This meets the unstructured criteria: (a) no consistent delimiter, (b) lines vary wildly in shape/content, (c) no visible emails/phones in the sample, but even if present they'd be handled by unstructured processing.

finanzen__LOBU__LOBU_2001__LA__LA10.csv
0 rows

File structure

Notes: This is an unstructured document (free-form text) with no consistent columnar structure. The content appears to be German-language legal/administrative text regarding tax forms and employment certificates for the year 2001. There are no identifiable columns or delimited data — it's purely narrative prose. No PII extraction can be performed via column mapping; any potential names/addresses would need full-text scanning.

finanzen__LOBU__LOBU_2001__LA__LA11.csv
0 rows

File structure

Notes: The provided rows appear to be free-form German text describing payroll forms and tax declarations rather than structured data. There are no consistent delimiters or repeating patterns across the rows, and the content is prose-style with no identifiable column structure. This matches the unstructured opt-out criteria: no consistent delimiter, varying line shapes, and appears to be documentation rather than record data. While the context mentions a corporate breach, this specific file fragment is purely descriptive text about Swiss payroll/tax forms, not containing any actual PII records.

finanzen__LOBU__LOBU_2001__LA__LA12.csv
0 rows

File structure

Notes: This is a free-form text document (Swiss German-language payroll tax form) with no consistent column structure. Contains only textual legal/administrative prose about tax declarations and payroll forms for the year 2001, with no embedded personal identifiers in the sample. No structured data columns to map.

finanzen__LOBU__LOBU_2001__LA__LA13.csv
0 rows

File structure

Notes: This is free-form text with no consistent column structure. The sample shows unstructured German prose about tax forms and employment documentation, not tabular data. No column mapping is possible.

finanzen__LOBU__LOBU_2001__LA__LA14.csv
0 rows

File structure

Notes: The provided rows appear to be unstructured German-language legal/administrative text related to tax forms and employment documentation for the year 2001, not structured tabular data with PII columns. There are no consistent delimiters or columnar patterns across the rows. This is typical of README, legal notices, or template documentation files, not breach data containing personal information.

finanzen__LOBU__LOBU_2001__LA__LA15.csv
0 rows

File structure

Notes: The sample shows unstructured German text describing employment/tax documentation (e.g., 'Dieses Lohnausweisformular ist durch...' and 'Kanton Zürich Gemeinde'). This is not a delimited dataset with columns containing PII. The content appears to be template instructions or legal boilerplate for Swiss tax forms rather than actual records.

finanzen__LOBU__LOBU_2001__LA__LA16.csv
0 rows

File structure

Notes: This is free-form text with no consistent columnar structure. The data appears to be German-language legal/administrative documents about tax forms and employment certificates, not structured tabular data with PII fields. There are no repeated delimiters or consistent column positions across rows.

finanzen__LOBU__LOBU_2001__LA__LA17.csv
0 rows

File structure

Notes: This is unstructured free-form text containing German-language descriptions of payroll tax forms and instructions. No consistent columnar structure exists; lines contain different content shapes and no identifiable PII fields in a tabular format. The file appears to be a README or explanatory document about tax forms rather than actual breach data with PII.

finanzen__LOBU__LOBU_2001__LA__LA18.csv
0 rows

File structure

Notes: The file appears to be free-form German text about tax forms and employment documentation. It contains no consistent delimiter structure or identifiable PII columns. Sample lines are prose describing tax forms rather than structured records. Since there are no consistent columns and the data is textual, this qualifies as unstructured content per the rules.

finanzen__LOBU__LOBU_2001__LA__LA19.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__LOBU__LOBU_2001__LA__LA2.csv
0 rows

File structure

Notes: This is unstructured prose text (German language) with no consistent column structure. Contains fragments of Swiss tax forms and legal text, but no identifiable PII columns or data fields. The sample shows free-form text rather than delimited records.

finanzen__LOBU__LOBU_2001__LA__LA20.csv
0 rows

File structure

Notes: The provided data is free-form text (German-language legal/administrative prose about tax forms), not a structured dataset. There are no consistent delimiters or column patterns — each row contains different text fragments. Though no explicit PII is visible in the sample, unstructured processing is required because of the lack of row structure. This routes to a streaming free-text extractor for any embedded emails/phones that may exist in the full file.

finanzen__LOBU__LOBU_2001__LA__LA3.csv
0 rows

File structure

Notes: The file appears to be free-form German text describing payroll tax forms (Lohnausweis) and tax declaration procedures rather than structured tabular data. The content includes phrases like 'Dieses Lohnausweisformular ist durch...' and 'Kanton Zürich Gemeinde'. No consistent column structure or delimiters are present across the rows, and the data consists of descriptive German sentences rather than PII records. While there is a numeric value that could be interpreted as an AHV number (Swiss social security), it appears within free text context without structured columns.

finanzen__LOBU__LOBU_2001__LA__LA4.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The file appears to be a document or form in German discussing tax forms and payroll certificates, with no tabular data structure. There are no consistent columns to map to PII fields.

finanzen__LOBU__LOBU_2001__LA__LA5.csv
0 rows

File structure

Notes: This is unstructured free-form text (German payroll tax forms) with no consistent columnar structure. Lines contain German sentences about tax forms and payroll documentation rather than tabular data. While there are some embedded names and addresses, the file lacks a consistent delimiter or header row, and each line has a different shape. According to rules, this must be treated as unstructured text with embedded PII for streaming extraction.

finanzen__LOBU__LOBU_2001__LA__LA6.csv
0 rows

File structure

Notes: The file appears to be free-form German-language text documents ( Lohnausweis / tax forms ) with no consistent columnar structure. The sample rows show prose paragraphs about tax declarations, not tabular data with delimited fields. No PII can be extracted via column mapping — route through unstructured processing for any embedded emails / phones.

finanzen__LOBU__LOBU_2001__LA__LA7.csv
0 rows

File structure

Notes: This is free-form text with no consistent columnar structure. The sample rows contain unstructured German text describing payroll forms and tax declarations for the year 2001, with no identifiable personal data in the visible sample. No PII columns can be mapped.

finanzen__LOBU__LOBU_2001__LA__LA8.csv
0 rows

File structure

Notes: This is unstructured text content, not a delimited dataset. The lines contain German legal/administrative text about tax declarations and payroll statements for the year 2001, but no consistent columnar structure or PII fields are present.

finanzen__LOBU__LOBU_2001__LA__LA9.csv
0 rows

File structure

Notes: This is a free-form document containing German-language legal/administrative text about tax forms and employment. No structured columns are present; the file appears to be a scanned or OCR'd legal notice or template, not tabular data. All rows contain prose and no consistent delimiter or repeating structure. Therefore, no PII columns can be mapped.

finanzen__LOBU__LOBU_2001__Lohnabr__1.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. The file contains embedded personal identifiers like Swiss AHV number (222.77.291.219) and name (Brunner Mark) within prose lines, but lacks a tabular format. It should be processed through unstructured text extraction for PII discovery.

finanzen__LOBU__LOBU_2001__Lohnabr__10.csv
0 rows

File structure

Notes: This is a free-form text document with no consistent columnar structure. It appears to be a Swiss payroll or accounting document from Zynex AG, containing unstructured financial and personal data fields interspersed with text. While there are fragments that might resemble PII (e.g., address lines, phone numbers), the entire file lacks a consistent delimiter and row structure required for columnar mapping. The content shows Swiss addresses (Pfäffikerstrasse 6, 8604 Volketswil), phone numbers (Tf. 908 12 80), and references to AHV numbers, but these are embedded within free-text lines rather than structured columns. This qualifies as unstructured data per the rules.

finanzen__LOBU__LOBU_2001__Lohnabr__2.csv
0 rows

File structure

Notes: This is a free-form financial record document with no consistent columnar structure. It appears to be a Swiss payroll statement from Zynex AG, containing unstructured text and numerical data. There are no identifiable PII columns in a structured format; instead, the data is presented in a narrative format typical of Swiss payroll documents. While it contains names (Leisi Martin) and potentially sensitive identifiers (AHV-Nr.: 591.72.265.213), these are embedded within unstructured text lines rather than in a tabular format with consistent columns. This qualifies as unstructured data per the rules.

finanzen__LOBU__LOBU_2001__Lohnabr__3.csv
0 rows

File structure

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

Notes: The file is unstructured financial statements with no consistent column mapping. While it contains AHV number (Swiss social security number) and names, it lacks a consistent column structure with identifiable PII fields across rows. The data appears to be free-form financial records without a defined schema. The AHV number (395.77.170.111) and name "Giger Thomas" appear in the data but cannot be mapped to consistent columns due to the unstructured nature of the file.

finanzen__LOBU__LOBU_2001__Lohnabr__4.csv
0 rows

File structure

Notes: The provided text is a free-form financial statement document (payroll) from Zynex AG with no consistent columnar structure. It contains Swiss addresses, phone numbers, AHV number (Swiss social security number), and personal names inline, but lacks a repeating tabular format. This qualifies as unstructured text per the rules, requiring routing through a streaming email/phone extractor.

finanzen__LOBU__LOBU_2001__Lohnabr__5.csv
1 column11 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4fullNamehigh[4] value 'Bolliger Jacqueline' is a full name

Notes: This is a free-form financial statement with no consistent column structure. Only one PII field (fullName) was found in the visible data. All other columns contain internal financial codes, account numbers, and calculations — these are non-PII per exclusion rules. No email/phone present to trigger unstructured extraction.

finanzen__LOBU__LOBU_2001__Lohnabr__6.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a Swiss payroll document from Zynex AG with structured fields but not in a delimited format. Contains Swiss addresses, phone numbers, and potentially Swiss social security numbers (AHV-Nr.), but lacks a consistent column layout across rows.

finanzen__LOBU__LOBU_2001__Lohnabr__7.csv
0 rows

File structure

Notes: This is a free-form structured document (payroll statement) with no consistent column delimiters. It contains embedded personal identifiers like 'Name, Vorname' and phone number 'Tf. 908 12 80', but lacks a tabular structure across rows. The document appears to be a Swiss payroll slip from Zynex AG, showing employee compensation details for November 2001, with fields for gross pay, deductions, and net pay. Since there is no consistent delimiter or column structure, this should be processed as unstructured text for PII extraction.

finanzen__LOBU__LOBU_2001__Lohnabr__8.csv
0 rows

File structure

Notes: This is a free-form text document (not structured data). The content appears to be a payroll or financial statement from Zynex AG in German, with fields like address, phone number, and AHV number (Swiss social security number). However, there are no consistent delimiters or column structure across rows, and the data is presented as prose lines. While it contains sensitive data like addresses and phone numbers, it does not follow a consistent CSV/TSV structure that can be mapped to columns. Therefore, it should be processed as unstructured text for extraction of embedded PII.

finanzen__LOBU__LOBU_2001__Lohnabr__9.csv
0 rows

File structure

Notes: This is a free-form structured text file (not a delimited table) containing internal corporate financial records from Zynex AG. The file appears to be a Swiss payroll/accounting document template with placeholders and fields like 'Name, Vorname:' and 'Abrechnungs-Periode'. While it contains sensitive corporate financial data and references to Swiss AHV numbers, it does not contain any actual PII records in the sample rows provided. The format is not CSV or any other delimited structure; it's a fixed-format document with lines that vary in structure and length. Therefore, it is classified as unstructured for processing.

finanzen__LOBU__LOBU_2001__Lohnblatt__01.csv
1 column2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header is ambiguous but first value 'Brunner Mark' is a full name pattern

Notes: This is a Swiss payroll file (Zynex AG) with financial columns only. Only column 1 contains PII: a full name. All other columns are financial codes, amounts, tax calculations, and years — no emails, addresses, phones, DOB, SSN, etc. The filename and context suggest this is internal corporate payroll data, not customer PII.

finanzen__LOBU__LOBU_2001__Lohnblatt__02.csv
0 rows

File structure

Notes: The provided data is a free-form text representation of payroll records with no consistent delimiter or column structure. The sample appears to be formatted as a table with merged cells and headers spanning multiple rows, but lacks a fixed column pattern across lines. This is typical of PDF-extracted tabular data that has not been properly parsed into a structured format. While there is a name visible ('Leisi Martin'), the data lacks any consistent delimiter or repeated structure across rows, making it unsuitable for column-based mapping. This should be processed as unstructured text for any embedded PII extraction.

finanzen__LOBU__LOBU_2001__Lohnblatt__03.csv
1 column2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header is blank but values are full names like 'Giger Thomas'

Notes: Only column 1 contains PII (fullName). All other columns appear to be financial codes, percentages, monetary values, and year markers — no addresses, emails, phones, or other personal identifiers visible. Column 0 shows 'Zynex AG' which is the company name, not PII.

finanzen__LOBU__LOBU_2001__Lohnblatt__04.csv
0 rows

File structure

Notes: This is not a delimited file with structured columns. The sample shows a free-form table-like layout with merged cells and no consistent delimiter across rows. It appears to be a payroll or financial statement document rather than a structured dataset with PII columns. No consistent column indices can be mapped to PII fields.

finanzen__LOBU__LOBU_2001__Lohnblatt__05.csv
1 column2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] contains 'Bolliger Jacqueline' — clearly a full name

Notes: This appears to be payroll data (Swiss AHV/UVG/BVG contributions, net salary, tax base) with a single personal identifier: full name. All other columns are numeric financial codes, percentages, or years — no PII. Header row contains German payroll terminology (Grundlohn = gross salary, AHV-Abz = Swiss old-age/pension contributions, Nettolohn = net salary).

finanzen__LOBU__LOBU_2001__Lohnblatt__06.csv
0 rows

File structure

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

Notes: This is a financial statement file with no PII. Columns represent accounting codes, percentages, and amounts. No personal identifiers present.

finanzen__LOBU__LOBU_2001__Lohnblatt__07.csv
0 rows

File structure

Notes: This is not structured data; the file appears to be a financial report or payroll statement with no consistent columnar structure across rows. The rows contain mixed financial codes, percentages, and amounts rather than any identifiable personal information. No PII columns exist.

finanzen__LOBU__LOBU_2001__Lohnblatt__08.csv
0 rows

File structure

Notes: This is not structured tabular data. The file appears to be a financial report or payroll statement from Zynex AG, formatted as free-form text with no consistent delimiter. Columns are not clearly defined, and the data contains financial codes and monetary values rather than personal identifiable information (PII). There are no identifiable rows or columns that map to PII fields.

finanzen__LOBU__LOBU_2001__Lohnblatt__09.csv
0 rows

File structure

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

Notes: This is purely financial/accounting data from Zynex AG with no personal identifiers. Columns contain account codes, Swiss social security abbreviations (AHV, UVG, KTG, BVG), percentages, and monetary amounts. No names, emails, addresses, or other PII present. All columns are financial metadata or internal codes.

finanzen__LOBU__LOBU_2001__Lohnblatt__10.csv
0 rows

File structure

Notes: The provided sample is free-form financial data with no consistent delimiter or column structure. It contains account codes, percentages, and monetary values but lacks a structured tabular format with consistent columns. This matches the unstructured data pattern described in the instructions.

finanzen__LOBU__LOBU_2001__Lohnblatt__11.csv
0 rows

File structure

Notes: This is not a structured CSV file. The data appears to be a free-form financial report with rows representing different financial categories (e.g., Grundlohn, Spesen, AHV-Abz) and columns representing months or years. There are no consistent columns or delimiters, and the data does not contain any identifiable PII fields. The values are financial amounts and codes, not personal information.

finanzen__LOBU__LOBU_2001__Lohnblatt__12.csv
0 rows

File structure

Notes: The file appears to be a non-structured financial ledger with no consistent column layout. Rows contain mixed content with no identifiable PII columns. Sample shows accounting entries (e.g., 'Grundlohn', 'Nettolohn', amounts in CHF) rather than personal data. No emails, phone numbers, or names present.

finanzen__LOBU__LOBU_2001__Lohnblatt__13.csv
0 rows

File structure

Notes: The file is free-form financial accounting data from Zynex AG, with no consistent row structure or identifiable personal PII columns. The data appears to be a raw financial ledger or accounting sheet showing account codes, amounts, and percentages without any personal identifiers such as names, emails, or addresses. There are no embedded emails or phone numbers visible in the sample.

finanzen__LOBU__LOBU_2001__Lohnblatt__14.csv
0 rows

File structure

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

Notes: This appears to be a financial statement document with structured financial codes and monetary values. No PII fields (email, phone, name, address, etc.) are present. Columns represent financial categories, codes, and amounts — all skip according to rules. No unstructured text with embedded PII.

finanzen__LOBU__LOBU_2001__Lohnblatt__15.csv
0 rows

File structure

Notes: This is a financial ledger table with no personal PII fields. Columns appear to be Swiss payroll accounting codes (e.g., AHV-Abz for Swiss social security deductions), account numbers, and monetary values. No emails, names, addresses, or other PII present in the sample. The structure is tabular but contains only corporate financial data, not customer PII.

finanzen__LOBU__LOBU_2001__Lohnblatt__16.csv
0 rows

File structure

Notes: This is not a structured CSV file. The data appears to be a free-form financial report with no consistent delimiter or column structure. The headers and values are mixed and do not represent typical PII fields. There are no identifiable personal data fields such as email, phone, or names present in a structured format.

finanzen__LOBU__LOBU_2001__Lohnblatt__17.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. The data appears to be a Swiss payroll or financial statement from Zynex AG, showing monetary values, percentages, and internal accounting codes across rows rather than a tabular dataset. There are no identifiable PII fields in this format.

finanzen__LOBU__LOBU_2001__Lohnblatt__18.csv
0 rows

File structure

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

Notes: This is a financial record file with columns representing account codes, amounts, and dates. No PII fields are present. Columns contain accounting codes (like 'Grundlohn', 'Vers'leist.'), monetary values, percentages, and dates that appear to be system-generated timestamps rather than personal data. All columns map to skip per exclusion rules (financial/transactional data, internal accounting codes).

finanzen__LOBU__LOBU_2001__Lohnblatt__19.csv
0 rows

File structure

Notes: This is a financial ledger document with no consistent row structure. It appears to be a payroll/ledger table with German financial codes and Swiss Franc values. The data is presented as a table with merged cells and no clear column headers or consistent delimiter. Contains no identifiable PII fields, only financial codes and monetary values.

finanzen__LOBU__LOBU_2001__Lohnblatt__20.csv
0 rows

File structure

Notes: This is not structured tabular data; it's a financial ledger with merged cells and no consistent delimiter. The first row appears to be a header with merged cells across columns, and subsequent rows contain financial figures and codes. There are no identifiable PII fields like names, emails, or addresses in this structured format. The data appears to be internal financial records with codes and monetary values, typical of corporate accounting documents.

finanzen__LOBU__LOBU_2001__Lohnblatt__AHV-ABR.csv
0 rows

File structure

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

Notes: The provided sample appears to be an unstructured payroll document in German with no consistent columnar structure. It contains free-form text lines describing payroll calculations, AHV/IV/EO obligations, and employee data, but lacks a fixed delimiter or header row. No identifiable PII columns can be mapped due to the unstructured nature of the data.

finanzen__LOBU__LOBU_2001__Lohnblatt__AHV-ABR_Druck.csv
0 rows

File structure

Notes: The provided text is a free-form payroll document in German with no consistent columnar structure. It contains unstructured lines describing payroll summaries, account numbers, and company details but does not present data in a tabular format with repeated rows of the same fields. While it contains potential PII-like strings (names, account numbers), there is no consistent delimiter or repeating pattern to map to columns. This meets the unstructured criteria: no shared delimiter, variable line shapes, and embedded personal data.

finanzen__LOBU__LOBU_2001__Lohnblatt__Total_Lohnbl.csv
2 columns23 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names (e.g., 'Brunner Mark', 'Leisi Martin', 'Giger Thomas', 'Marco Gamma')
18genderhigh[18] header 'M / F', values are 'M' and 'F', representing gender

Notes: This is a Swiss payroll/earnings statement file for Zynex AG employees. Contains employee full names and gender, but no emails, phones, DOB, addresses, SSN, passwords, usernames, or suffixes. Other columns represent salary components, tax withholdings, and financial calculations in CHF.

finanzen__LOBU__LOBU_2001__Lohnjournal__Apr.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names (Brunner Mark, Leisi Martin, etc.)

Notes: Only column 1 contains PII (fullName). All other columns contain financial/employment data (salaries, deductions, taxes, etc.) with no personal identifiers. Column 0 appears to be a reference number ('P-Nr.').

finanzen__LOBU__LOBU_2001__Lohnjournal__Aug.csv
0 rows

File structure

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

Notes: This file appears to be a financial ledger from Zynex AG, containing Swiss payroll and tax calculations. No PII fields are present. Columns include internal accounting codes (P-Nr.), employee names (but these appear to be generic placeholder names like 'Brunner Mark'), salary components, tax withholdings, and financial totals. No emails, addresses, DOBs, SSNs, or other PII fields are visible in the first 50 rows.

finanzen__LOBU__LOBU_2001__Lohnjournal__Daten.csv
4 columns15 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header row label 'Name, Vorname', values are 'Brunner Mark', 'Leisi Martin', 'Giger Thomas' — full names in LastName FirstName order
3citymedium[3] header label 'Wohnort' (place of residence), values like '8604 Volketswil', '4612 Wangen b. Olten' — Swiss ZIP + city combined; mapped as city as closest field
4address1high[4] header label 'Adresse', values are street addresses like 'Pfäffikerstrasse 6', 'Haftlet 18', 'Ifangstrasse 50'
5ssnhigh[5] header label 'AHV-Nr.' (AHV = Swiss AVS social security number), values are formatted SSN-like identifiers e.g. '222.77.291.219', '591.72.265.213'

Notes: Swiss payroll personnel register (Personalverzeichnis) for Zynex AG, circa 2001. No true header row — column roles inferred from label rows and sample data. Col 3 (Wohnort) contains Swiss postal code and city combined (e.g. '8604 Volketswil'); mapped as city. AHV-Nr. in col 5 is the Swiss social security identifier, mapped as ssn. Trailing rows are German-language instructions, not data. Only 5 employee records present.

finanzen__LOBU__LOBU_2001__Lohnjournal__Dez.csv
0 rows

File structure

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

Notes: This is a financial payroll file showing employee salaries, taxes, and deductions for Zynex AG. Columns contain only financial data and internal codes (P-Nr., AHV, UVG, KTG, etc.) with no PII fields like names, addresses, or contact information. The 'Name' column contains employee names, but these are internal identifiers for employees of Zynex AG (the company itself), not customer PII. Per breach context, this is internal corporate financial data, not customer data.

finanzen__LOBU__LOBU_2001__Lohnjournal__Feb.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (fullName). All other columns appear to be financial/earnings data (salaries, deductions, taxes) and internal accounting codes — no emails, addresses, DOB, etc. Column 0 is a reference code ('P-Nr.').

finanzen__LOBU__LOBU_2001__Lohnjournal__Grat.csv
0 rows

File structure

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

Notes: This is an unstructured financial payroll file with no personal identifiers. Columns represent Swiss payroll codes (e.g., AHV, UVG, BVG), amounts, and percentages. No PII fields (name, email, address, etc.) are present. Values are numeric codes and monetary amounts in CHF. The first column appears to be an employee identifier (P-Nr.) but does not map to any PII field and is treated as skip.

finanzen__LOBU__LOBU_2001__Lohnjournal__Jan.csv
0 rows

File structure

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

Notes: This is a financial payroll data file from Zynex AG, showing employee names and salary calculations. The data contains no PII fields beyond names, which appear in column 1. However, these names are paired only with internal payroll codes and financial figures — no addresses, contact details, or identifiers are present. The file is purely transactional financial data without personal contact information. All columns map to financial calculations (gross pay, taxes, deductions, net pay) and internal reference codes. No PII columns to map.

finanzen__LOBU__LOBU_2001__Lohnjournal__Jul.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] values are full names like 'Brunner Mark', 'Leisi Martin'

Notes: This appears to be a payroll/billing ledger with financial columns (Grundlohn, Spesen, Nettolohn, etc.). Only column 1 contains PII (full names). All other columns are financial codes, percentages, and monetary values — no emails, addresses, DOB, SSN, or phone numbers visible. Column 0 appears to be an internal reference code ('P-Nr.').

finanzen__LOBU__LOBU_2001__Lohnjournal__Jun.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's an internal financial ledger from Zynex AG showing payroll calculations (gross pay, taxes, net pay, etc.) with no personal identifiers beyond employee names in column 1. The values are all numeric financial figures, codes, and percentages. While column 1 contains names, these appear to be employee names rather than customer PII. Since there are no emails, addresses, phone numbers, DOB, SSN, or other searchable PII fields, and the data is purely financial/tax calculations, no columns map to PII fields. The file is financial records without personal contact details.

finanzen__LOBU__LOBU_2001__Lohnjournal__M_r.csv
0 rows

File structure

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

Notes: This is a financial payroll record file from Zynex AG. All columns contain accounting codes, monetary amounts, tax calculations, and internal reference numbers (P-Nr.). No personal identifiers such as names, emails, addresses, or other PII are present. The column labeled 'Name' contains only employee names which are not mappable to any PII field in our schema (firstName/lastName fields require isolated first and last name components). Per our rules, structured financial records without isolated PII columns are mapped as empty.

finanzen__LOBU__LOBU_2001__Lohnjournal__Mai.csv
0 rows

File structure

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

Notes: This file appears to be a payroll ledger with internal accounting codes and financial figures. Column 1 contains names but these are employee names rather than customer PII relevant to the breach context. All columns contain financial transaction codes, percentages, and monetary values with no email addresses, phone numbers, DOBs, or other PII fields. Per exclusion rules, internal financial/timestamp columns are skipped.

finanzen__LOBU__LOBU_2001__Lohnjournal__Nov.csv
0 rows

File structure

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

Notes: This is not a structured PII file. The data appears to be payroll/accounting records with internal financial codes and numeric values. No columns map to PII fields because all values are internal financial codes, numeric amounts, or generic labels like 'Grundlohn' (base pay), 'Spesen' (expenses), and tax basis calculations. Names in column 1 appear to be employee names, but these are internal corporate employee records, not customer data. The context confirms this is internal financial data from Zynex AG, not customer PII exposed in the breach.

finanzen__LOBU__LOBU_2001__Lohnjournal__Okt.csv
0 rows

File structure

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

Notes: This is a financial payroll ledger with no personal identifiable information (PII). Columns represent Swiss payroll accounting codes and amounts (e.g., 'Grundlohn' base pay, 'Spesen' expenses, tax withholdings). Names appear to be employee identifiers but lack first/last name separation and show only full names without addresses or contact details. No emails, phone numbers, DOB, SSN, or other PII fields are present. All columns are financial codes or numeric values — these are internal accounting records, not customer PII.

finanzen__LOBU__LOBU_2001__Lohnjournal__Sep.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (fullName). All other columns are financial/transactional codes, amounts, percentages, and internal accounting identifiers — no emails, addresses, DOB, SSN, etc. This matches Zynex's financial records context.

finanzen__LOBU__LOBU_2002__LA__Data.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains header-like lines but not tabular data. No PII columns to map.

finanzen__LOBU__LOBU_2002__LA__LA1.csv
0 rows

File structure

Notes: This is a free-form German-language document describing payroll tax forms (Lohnausweis) for the year 2002 in the Zurich canton. The file contains no structured tabular data — it's purely descriptive prose about tax reporting requirements, with no repeating columns or consistent delimiter. While there is a numeric string that resembles an AHV (Swiss social security) number (222.77.291.219), it's embedded in narrative text and not part of a structured record set. Therefore, this qualifies as unstructured text requiring a streaming parser for any embedded identifiers.

finanzen__LOBU__LOBU_2002__LA__LA2.csv
0 rows

File structure

Notes: The provided data appears to be unstructured text content, likely from a document or form. The lines contain German prose describing payroll forms and tax declarations, with no consistent columnar structure or delimited data. There are no clear headers or repeated patterns indicating a tabular format. While there are snippets that resemble potential PII (e.g., "Leisi Martin", "Haftlet 18", "4612 Wangen b. Olten", "591.72.265.213"), these appear embedded within free-form text rather than in a structured tabular format. According to the rules, when the file is free-form text with no consistent delimiter and varying line shapes, it should be classified as unstructured with an empty columns object.

finanzen__LOBU__LOBU_2002__LA__LA3.csv
0 rows

File structure

Notes: The file is free-form German text containing unstructured records about payroll forms and tax declarations. No consistent column structure or delimiter is present. While there is a potential address fragment in column 8 and an AHV number-like value in column 9, the data is entirely prose and lacks row structure, meeting the unstructured criteria. This routes to free-text processing for embedded PII extraction.

finanzen__LOBU__LOBU_2002__LA__LA4.csv
0 rows

File structure

Notes: This is free-form text with no consistent column structure. The content appears to be German-language legal/administrative text about tax forms and employment documentation. There are no structured columns to map to PII fields.

finanzen__LOBU__LOBU_2002__LA__LA5.csv
0 rows

File structure

Notes: The provided data appears to be free-form German text describing payroll forms and tax declarations rather than structured tabular data. The content includes phrases like 'Dieses Lohnausweisformular ist durch...' and 'Kanton Zürich Gemeinde', but there are no consistent columnar patterns or delimited fields across rows. This is not CSV or any structured format with PII columns; it's prose documentation about payroll/tax forms. Since there is no consistent delimiter or column structure, and the data is purely textual, we classify this as unstructured with no column mappings.

finanzen__LOBU__LOBU_2002__LA__LA6.csv
0 rows

File structure

Notes: This is free-form text (Swiss German) describing payroll certificate procedures, not structured data with columns. Contains no consistent delimiter or row pattern. Sample lines are narrative paragraphs about tax forms and employment scenarios.

finanzen__LOBU__LOBU_2002__Lohnabr__1.csv
0 rows

File structure

Notes: The provided data is a free-form text document containing unstructured financial records from Zynex AG. It does not have a consistent column structure or delimiter across rows, and contains no identifiable columns for PII mapping. Despite containing some structured-looking elements (e.g., AHV-Nr., name), the overall format is inconsistent and unstructured, with varying line structures and no repeatable field positions. Per the unstructured opt-out rules, this should be processed as free-form text with embedded PII extraction.

finanzen__LOBU__LOBU_2002__Lohnabr__10.csv
0 rows

File structure

Notes: This is a free-form text document (payroll record) with no consistent columnar structure. The file contains embedded PII such as names and addresses, but lacks a uniform delimiter or row pattern. It should be processed by a streaming email/phone extractor.

finanzen__LOBU__LOBU_2002__Lohnabr__2.csv
0 rows

File structure

Notes: This is a free-form financial document from Zynex AG, not a structured dataset with columnar PII. It contains employee compensation details but lacks consistent delimiters or repeated column headers across rows. While it includes personal identifiers like AHV number (Swiss social security number) and names, the format does not meet structured CSV/TSV criteria — lines vary in length and content, with no repeating field positions. This should be processed through unstructured text extraction pipelines for AHV numbers and names rather than columnar mapping.

finanzen__LOBU__LOBU_2002__Lohnabr__3.csv
0 rows

File structure

Notes: The file appears to be a free-form financial statement document rather than a structured dataset with columns. It contains textual entries describing a Swiss corporate payroll record for Zynex AG, with lines showing address, phone number, AHV number (Swiss social security), name, accounting period, bank details, and various salary components. There is no consistent delimiter or column structure across lines, and while it contains sensitive Swiss identifiers (AHV number, name, address, phone), it does not conform to a tabular format with mappable columns. This qualifies as unstructured text per the rules.

finanzen__LOBU__LOBU_2002__Lohnabr__4.csv
0 rows

File structure

Notes: This is an unstructured financial record file with no consistent column mapping. It contains free-form text lines with employee data, addresses, and bank details, but lacks a fixed column structure. While it contains potentially sensitive data (names, addresses, bank account numbers), the format does not allow for column mapping due to variable line structures and mixed content. The file should be processed through unstructured text analysis to extract PII.

finanzen__LOBU__LOBU_2002__Lohnabr__5.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's a free-form financial record from Zynex AG showing payroll calculations for an employee named Jacqueline Bolliger. There are no consistent columns across rows — each line represents a different field/value pair in key-value format. While the name 'Bolliger Jacqueline' appears, it is embedded in a prose-like line and the file lacks columnar structure. According to rules, unstructured free-form text with no consistent delimiter should return empty columns object. The content is payroll accounting, not customer PII from the breach context.

finanzen__LOBU__LOBU_2002__Lohnabr__6.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent columnar structure. The data appears to be a Swiss payroll statement from Zynex AG, containing employee name (Marco Gamma), address (In Lampitzäckern 45, 8305 Dietlikon), and various salary/insurance calculations. While it contains personal information like name and address, the format lacks consistent delimiters and column headers across rows, meeting the criteria for unstructured text with embedded PII. The file should be processed through a streaming email/phone/address extractor for any visible personal data.

finanzen__LOBU__LOBU_2002__Lohnabr__7.csv
0 rows

File structure

Notes: The file is a free-form text document (payroll statement) with no consistent column structure. It contains Swiss payroll data from Zynex AG, with German headers and numeric values, but lacks a repeated delimiter pattern across rows. While it contains sensitive employee data, the format does not conform to a structured table — it should be processed as unstructured text for PII extraction.

finanzen__LOBU__LOBU_2002__Lohnabr__8.csv
0 rows

File structure

Notes: This is a free-form structured document (payroll slip) with no consistent columnar delimiter across rows. It contains sensitive personal data like names and AHV (Swiss social security) number but lacks a repeating tabular format with shared delimiters. The layout is a mix of labels and values across lines, not a CSV or similar structured format. Per rules, unstructured files with embedded PII are handled via streaming extraction.

finanzen__LOBU__LOBU_2002__Lohnabr__9.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. The data appears to be Swiss payroll records from Zynex AG, containing unstructured text lines with account numbers, addresses, and financial calculations. While there are potential PII fragments like addresses (Pfäffikerstrasse 6, 8604 Volketswil) and phone numbers (Tf. 908 12 80), the lack of consistent delimiters and row patterns means this should be processed as unstructured text for embedded PII extraction.

finanzen__LOBU__LOBU_2002__Lohnblatt__01.csv
0 rows

File structure

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

Notes: This is not structured PII data — it's an internal financial report with payroll calculations and accounting codes. Column 1 contains a name-like string ('Brunner Mark') but this is part of an accounting header row, not actual personal data. All other columns contain numeric financial values, account codes, percentages, and dates that are purely transactional/financial metadata. No true PII fields (email, phone, address, etc.) are present in this structured format.

finanzen__LOBU__LOBU_2002__Lohnblatt__02.csv
0 rows

File structure

Notes: This file is not structured tabular data. The rows contain financial payroll data from Zynex AG with no consistent PII fields. The data includes names, addresses, and financial figures, but these are not typical PII columns (no emails, phones, DOB, SSN). Given the nature of the data (payroll records), this is likely a financial statement or accounting document rather than a typical PII dataset. The format appears to be a legacy payroll report with mixed text and numeric values across rows, not a CSV with defined columns. No PII fields map to the defined categories.

finanzen__LOBU__LOBU_2002__Lohnblatt__03.csv
1 column2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] values are full names like 'Giger Thomas'

Notes: This is a payroll/financial report with no typical PII fields beyond fullName. All other columns are account codes, monetary amounts, percentages, and dates — none constitute PII under our definitions. The 'Zynex AG' column appears to be a header label repeated across rows, not actual data.

finanzen__LOBU__LOBU_2002__Lohnblatt__04.csv
0 rows

File structure

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

Notes: This appears to be a Swiss payroll ledger (Lohnblatt) for a single employee (Poulton Dave, DOB 29.8.75) rendered as a transposed financial report, not a structured multi-record PII dataset. Columns represent accounting line items and monthly salary figures (CHF), not repeating PII fields. No consistent PII column mapping is possible.

finanzen__LOBU__LOBU_2002__Lohnblatt__05.csv
1 column2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] contains full names like 'Bolliger Jacqueline'

Notes: Only column 1 contains PII (full name). All other columns are financial codes, percentages, monetary amounts, and year labels — none map to PII fields. No emails, phones, addresses, DOB, SSN, or usernames are present.

finanzen__LOBU__LOBU_2002__Lohnblatt__06.csv
0 rows

File structure

Notes: This is NOT a structured table with columns; it's a free-form financial record layout. The first row appears to be a headerless layout with merged cells showing company name (Zynex AG), employee name (Gamma Marco), and financial data across months (Jan, Feb, Mär). There are no consistent delimited columns, and values represent financial figures rather than personal identifiers. This is characteristic of internal accounting documents, not PII-containing CSV/TSV files. No emails, phone numbers, or addresses are present in the sample.

finanzen__LOBU__LOBU_2002__Lohnblatt__07.csv
0 rows

File structure

Notes: This is a free-form financial ledger showing monthly payroll calculations for Zynex AG employees. No consistent column structure exists across rows; entries are mixed financial codes, percentages, and monetary values. No PII fields (names, emails, addresses) are visible in the sample.

finanzen__LOBU__LOBU_2002__Lohnblatt__08.csv
0 rows

File structure

Notes: This is a free-form financial ledger with no consistent column structure. The file appears to be a printed report showing payroll/booking codes and amounts rather than structured PII records. While it contains numeric codes and percentages, there are no identifiable personal fields like names, emails, or addresses. The format does not match standard CSV/TSV patterns and contains German payroll terminology (Grundlohn, AHV-Abz, etc.) with monetary values rather than personal data.

finanzen__LOBU__LOBU_2002__Lohnblatt__09.csv
0 rows

File structure

Notes: This is a financial ledger document with structured rows but no identifiable personal information (PII). Columns represent accounting codes, amounts, and dates related to payroll calculations for Zynex AG. No names, addresses, emails, or other PII fields are present. The data is purely transactional/financial and falls outside the scope of PII extraction rules.

finanzen__LOBU__LOBU_2002__Lohnblatt__10.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent columnar structure. The rows appear to represent financial ledger entries with account codes, descriptions, and monetary values rather than structured personal data. The content resembles payroll or accounting records with headers like 'Grundlohn' (base pay), 'Spesen' (expenses), and various tax/deduction codes (AHV, UVG, KTG, BVG). No identifiable personal information (names, emails, etc.) is present in the sample. The format appears to be a fixed-width or tabular document rather than a CSV with named columns.

finanzen__LOBU__LOBU_2002__Lohnblatt__11.csv
0 rows

File structure

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

Notes: This is a financial record file with no PII columns. All columns represent account codes, percentages, monetary values, and dates (e.g., 'Grundlohn' base salary, 'AHV-Abz' Swiss social security deductions). No personal identifiers like names, emails, or addresses are present. The data appears to be internal accounting records for Zynex AG, a Swiss company, spanning multiple months and years.

finanzen__LOBU__LOBU_2002__Lohnblatt__12.csv
0 rows

File structure

Notes: This is not structured tabular data but rather unstructured financial ledger entries. The rows appear to represent accounting line items with account codes and monetary values, not personal identifiable information. The first column contains what looks like account codes or categories ('Zynex AG', 'Grundlohn', etc.), and subsequent columns contain numeric values and percentages. There are no columns mapping to PII fields like names, addresses, emails, etc. Given the context of an internal corporate financial breach, this appears to be accounting system data rather than customer PII.

finanzen__LOBU__LOBU_2002__Lohnblatt__13.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. Rows appear to be formatted as a table with merged cells and labels rather than a delimited CSV. The data represents payroll accounting entries for Zynex AG with account codes, percentages, and monetary values, but lacks any identifiable personal information in the first 50 rows. Given the unstructured nature and absence of PII, no column mapping is performed.

finanzen__LOBU__LOBU_2002__Lohnblatt__14.csv
0 rows

File structure

Notes: This is not structured tabular data; it's a free-form financial report with mixed text and numbers. No consistent delimiter or column structure exists across lines. Contains Swiss payroll/financial data from Zynex AG but lacks any personal PII fields like names, emails, or addresses. No emails or phone numbers visible in the sample.

finanzen__LOBU__LOBU_2002__Lohnblatt__15.csv
0 rows

File structure

Notes: The file is not a structured dataset with consistent columns and delimiters. It appears to be a free-form financial report with rows containing mixed textual and numeric data (e.g., 'Zynex AG', 'Grundlohn', '5000/'). There are no identifiable PII fields such as email, phone, name, or address. The data appears to be internal financial records (salaries, deductions, taxes) for Zynex AG, a Swiss company, spanning years and months. No emails or phone numbers are visible in the sample.

finanzen__LOBU__LOBU_2002__Lohnblatt__16.csv
0 rows

File structure

Notes: This is a financial statement file with no consistent column structure or PII fields. All columns appear to be financial codes, account numbers, and monetary values. No personal identifiable information is present in this sample data.

finanzen__LOBU__LOBU_2002__Lohnblatt__17.csv
0 rows

File structure

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

Notes: This file is NOT structured PII data; it contains financial ledger entries (Swiss Francs) and payroll accounting codes for Zynex AG. All columns contain accounting codes, monetary values, or date stamps with no personal identifiers. No email, phone, name, address, DOB, SSN, or other PII fields are present. This is purely transactional/financial data from internal ERP system FaktNT.

finanzen__LOBU__LOBU_2002__Lohnblatt__18.csv
0 rows

File structure

Notes: This is a financial statement table with no PII columns. Columns appear to be financial codes, account numbers, and monetary values. No names, emails, addresses, or other PII are present in the sample. The structure shows aggregated financial data for months (Jan, Feb, Mär) and account codes (5000/, 5003/, etc.).

finanzen__LOBU__LOBU_2002__Lohnblatt__19.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. Rows contain German financial terminology and numeric values but no identifiable personal data. No PII columns exist to map.

finanzen__LOBU__LOBU_2002__Lohnblatt__20.csv
0 rows

File structure

Notes: This is not a structured data file. The rows appear to be financial ledger entries with German column headers and Swiss accounting codes (e.g., 'Grundlohn' = gross salary, 'AHV-Abz' = Swiss social security deduction). There are no personal identifiers like names, emails, or addresses. The values are all numeric amounts, percentages, and Swiss tax codes, indicating this is an internal financial report rather than customer PII data. No PII columns to map.

finanzen__LOBU__LOBU_2002__Lohnblatt__AHV-ABR.csv
0 rows

File structure

Notes: This is an unstructured payroll document in German. The file contains free-form text with no consistent columnar structure across lines. While it includes employee names and social security numbers (AHV/IV/EO-pflichtige Versicherten-Nummer), the data is presented in narrative format rather than tabular form, satisfying the unstructured criteria: (a) no consistent delimiter, (b) lines vary in length/content, (c) contains PII inline. This routes to streaming extraction for names and identifiers.

finanzen__LOBU__LOBU_2002__Lohnblatt__AHV-ABR_D.csv
0 rows

File structure

Notes: free-form text with embedded names and Swiss social security numbers (AHV numbers). No consistent delimiter or column structure exists across lines. Contains employee names (Bolliger Jacqueline, Brunner Mark, Gamma Marco, Giger Thomas, Leisi Martin, Poulton Dave) and Swiss social security numbers (AHV numbers) in format XXX.XX.XXX.XXX.

finanzen__LOBU__LOBU_2002__Lohnblatt__Total_Lohnbl.csv
1 column9 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (full names). All other columns are financial codes, numeric values, or gender flags — none are personal identifiers or addresses. No emails, phones, DOB, or SSNs are present.

finanzen__LOBU__LOBU_2002__Lohnjournal__Apr.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (full names). All other columns are financial codes, amounts, percentages, and years — no personal identifiers beyond names. No emails, addresses, DOB, SSN, etc. present in this structured financial payroll dataset.

finanzen__LOBU__LOBU_2002__Lohnjournal__Aug.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (full names). All other columns contain financial codes, amounts, percentages, and internal accounting identifiers — no emails, addresses, DOB, SSN, or other PII fields present. This is consistent with Zynex's financial records (payroll, invoicing) rather than customer or employee personal data.

finanzen__LOBU__LOBU_2002__Lohnjournal__Daten.csv
1 column15 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] contains full names in 'Last First' format across multiple rows

Notes: This appears to be a Swiss payroll spreadsheet with employee records. Column 2 contains full names in 'Last First' format (e.g., 'Brunner Mark'). No other columns contain clear PII fields in the visible rows. Columns 3-6 appear to contain location and AHV (Swiss social security) numbers, but values are insufficiently clear to confidently map. All other rows are empty or header/comment lines.

finanzen__LOBU__LOBU_2002__Lohnjournal__Dez.csv
0 rows

File structure

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

Notes: This is a structured financial payroll file from Zynex AG with no personal identifiers. Columns represent accounting codes, payroll amounts, tax calculations, and year references. No PII fields (names, emails, addresses, etc.) are present beyond generic employee names in column 1 which appear to be sample placeholders rather than actual sensitive data. All columns map to skip categories: internal accounting codes, monetary values, percentages, and year references.

finanzen__LOBU__LOBU_2002__Lohnjournal__Feb.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: This is a payroll file with internal employee names and financial data. Only the 'Name' column contains PII (full names). All other columns contain financial codes, amounts, and percentages — no emails, addresses, DOB, etc. The 'P-Nr.' column appears to be a personnel number (internal ID) and must be skipped per rules.

finanzen__LOBU__LOBU_2002__Lohnjournal__Grat.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (fullName). All other columns are internal financial codes, percentages, or numeric values (e.g., '5000/', '5.05%', '(0.00 ') that do not map to any PII fields. No emails, phones, addresses, or other PII present.

finanzen__LOBU__LOBU_2002__Lohnjournal__Jan.csv
0 rows

File structure

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

Notes: This is not structured PII data; it appears to be payroll/accounting records from Zynex AG with internal identifiers and financial figures. Column 1 contains names, but these appear to be employee names rather than customer PII relevant to the breach context. All other columns are financial codes and amounts (salaries, deductions, taxes). No true PII fields (email, phone, dob, address, etc.) are present. The file represents internal corporate financial data rather than customer PII exposed in the breach.

finanzen__LOBU__LOBU_2002__Lohnjournal__Jul.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (fullName). All other columns are internal financial codes, amounts, percentages, and year markers with no personal data. No emails, phone numbers, DOB, SSN, or addresses present in the sample.

finanzen__LOBU__LOBU_2002__Lohnjournal__Jun.csv
0 rows

File structure

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

Notes: This is a financial payroll data file from Zynex AG. Columns contain internal accounting codes (P-Nr.), employee names in German format, salary components, tax calculations, and other financial figures. No PII fields are present beyond employee names which appear to be internal employee identifiers rather than customer PII. All columns represent financial transaction codes, amounts, and percentages — none map to addressable PII categories (email, phone, DOB, SSN, etc.). The 'Name' column appears to contain employee names but these are internal corporate staff, not customer data exposed in the breach context.

finanzen__LOBU__LOBU_2002__Lohnjournal__M_r.csv
0 rows

File structure

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

Notes: This is a payroll/financial record file with no personal identifiable information (PII). Columns contain only internal financial codes, monetary values, percentages, and tax calculations. No names, addresses, emails, phone numbers, or other PII fields are present. The 'Name' column contains only generic placeholder values ('Name') and no actual personal names in the sample rows.

finanzen__LOBU__LOBU_2002__Lohnjournal__Mai.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (full names). All other columns are financial accounting codes, percentages, and monetary amounts — no addresses, emails, phones, or dates of birth. The file appears to be payroll data from Zynex AG, with no identifiable personal contact information beyond names.

finanzen__LOBU__LOBU_2002__Lohnjournal__Nov.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark', 'Leisi Martin', 'Giger Thomas', 'Poulton Dave'

Notes: Only column 1 contains PII (fullName). All other columns are financial/HR data (salaries, taxes, deductions, etc.) and do not contain any personal identifiable information per the defined PII field list. No emails, phone numbers, addresses, DOB, SSN, etc. are present.

finanzen__LOBU__LOBU_2002__Lohnjournal__Okt.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (fullName). All other columns are financial codes, amounts, percentages, and internal accounting references. No emails, addresses, phones, or other PII are present in the sample.

finanzen__LOBU__LOBU_2002__Lohnjournal__Sep.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: This is a payroll/financial record file with no PII beyond names. Columns contain Swiss payroll codes (e.g., AHV, UVG), amounts, and tax calculations. No emails, addresses, DOB, or other PII are present.

finanzen__LOBU__LOBU_2002__Lohnueberischt__Tabelle1.csv
0 rows

File structure

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

Notes: This is a payroll summary document (Lohnübersicht Auszahlungen 2002) showing monthly salary payments to employees. All columns contain either month names, numeric salary amounts, or employee names in an ambiguous format (e.g., 'M. Brunner'). No clear PII fields are present: the names appear truncated (initial + surname) and lack additional identifiers like full names, addresses, or contact details. Values like 'M. Brunner' do not meet the threshold for firstName/lastName mapping as they are not full names. All columns represent either internal accounting data (salary amounts, totals) or partial employee identifiers without sufficient context to map to PII fields. No emails, phones, DOB, SSN, etc., are visible.

finanzen__LOBU__LOBU_2003__LA__Data.csv
0 rows

File structure

Notes: This is a free-form document with no consistent delimiter structure. The file appears to be a corporate document header/footer block from a Swiss company (Zynex AG) containing location, date, and year information. No PII fields are present in this snippet, and the structure does not contain any repeated columnar data.

finanzen__LOBU__LOBU_2003__LA__LA1.csv
0 rows

File structure

Notes: This is unstructured text data (German-language payroll / tax forms) with no consistent columnar structure. The sample shows free-form paragraphs and document titles rather than tabular data with identifiable columns. Though some lines contain address-like fragments (e.g., 'Pfäffikerstrasse 6', '8604 Volketswil') and an IP-like number ('222.77.291.219'), there is no consistent delimiter or repeated field pattern across rows. This meets the unstructured criteria: (a) no consistent delimiter, (b) wildly varying line shapes, (c) contains embedded personal data fragments. This should be processed through a streaming free-text extractor for any embedded emails/phones/addresses rather than columnar mapping.

finanzen__LOBU__LOBU_2003__LA__LA10.csv
0 rows

File structure

Notes: This is unstructured free-form text (German-language employment tax document template), not a delimited dataset. No consistent columns exist across rows — each line is a different sentence/fragment of the template. While it contains sensitive employment/tax guidance, it lacks any actual PII records or structured data to map.

finanzen__LOBU__LOBU_2003__LA__LA11.csv
0 rows

File structure

Notes: This is free-form text (Swiss German) describing payroll certificate procedures, not structured tabular data. No consistent delimiter or column pattern exists across lines. Contains no actual PII records, only descriptive text about tax forms.

finanzen__LOBU__LOBU_2003__LA__LA12.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample contains German-language prose describing tax forms and employment contexts, not structured data rows with PII fields. While there are occasional numeric strings ('0'), they appear to be placeholder values rather than actual PII. The content matches the description of internal corporate documents (tax forms, assembly protocols) from the breach context.

finanzen__LOBU__LOBU_2003__LA__LA13.csv
0 rows

File structure

Notes: The file appears to be a document template or explanatory text about Swiss payroll certificates (Lohnausweis) and tax declarations, not structured records with PII columns. The lines contain German legal prose rather than delimited data fields. No consistent column structure exists across the rows.

finanzen__LOBU__LOBU_2003__LA__LA14.csv
0 rows

File structure

Notes: This is unstructured free-form text containing German prose about tax forms and employment certificates. No consistent columnar structure exists across rows; lines contain descriptive legal text rather than tabular data. While the file is part of a corporate data breach, it does not contain any importable PII fields in structured format. The content appears to be instructional or informational text about Swiss tax forms (Lohnausweis) and does not contain any actual personal records.

finanzen__LOBU__LOBU_2003__LA__LA15.csv
0 rows

File structure

Notes: The provided rows appear to be unstructured German-language legal/procedural text describing payroll forms and tax declarations. No consistent tabular structure exists — each line is a separate legal sentence with no repeating column positions or delimiters. This is typical of a README or document explaining forms, not actual data records. No PII columns can be mapped.

finanzen__LOBU__LOBU_2003__LA__LA16.csv
0 rows

File structure

Notes: This is unstructured free-form text (prose paragraphs) describing Swiss payroll tax forms, not tabular data with PII columns. No consistent delimiter or row structure exists across the sample lines. Contains no embedded emails or phone numbers.

finanzen__LOBU__LOBU_2003__LA__LA17.csv
0 rows

File structure

Notes: The file is unstructured free-form text with no consistent columnar structure. The sample shows German-language legal/HR text about tax forms and employment records, but contains no tabular data or repeated fields. There are no visible emails or phone numbers in the sample, but the unstructured nature prevents column mapping.

finanzen__LOBU__LOBU_2003__LA__LA18.csv
0 rows

File structure

Notes: This is unstructured document data (German-language payroll tax forms) with no consistent columnar structure. The rows contain free-form text describing tax forms and procedures rather than tabular PII records. No columns to map.

finanzen__LOBU__LOBU_2003__LA__LA19.csv
0 rows

File structure

Notes: The file appears to be free-form German text describing payroll tax forms and procedures rather than structured tabular data. No consistent column pattern exists across rows, and the content consists of prose paragraphs about tax documentation requirements. While there are no visible emails or phone numbers in this sample, the unstructured nature prevents column mapping. This will be processed through free-text extraction pipelines.

finanzen__LOBU__LOBU_2003__LA__LA2.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent columnar structure. The sample rows contain German-language legal/administrative text about tax forms and wages, not tabular data. There are no identifiable columns or delimiters, and the content appears to be narrative prose rather than delimited records. While there is a potential AHV number (Swiss social security) visible in row 9 ('591.72.265.213'), the lack of consistent structure means we must treat this as unstructured text for processing via the free-form extractor pipeline.

finanzen__LOBU__LOBU_2003__LA__LA20.csv
0 rows

File structure

Notes: This is free-form text containing German prose about payroll forms and tax declarations, not structured data. No consistent delimiter or column pattern exists across rows. Contains no embedded emails or phones in the visible sample.

finanzen__LOBU__LOBU_2003__LA__LA3.csv
0 rows

File structure

Notes: This is unstructured free-form text (German-language employment/tax documentation). No consistent column structure exists across rows — lines are full sentences and paragraphs describing tax forms, legal text, and sample entries. Though there is a snippet that looks like an address ("Giger Thomas", "Ifangstrasse 50", "8604 Volketswil") and an AHV number fragment ("395.77.170.111"), these appear embedded in prose rather than as tabular columns. Per rules, unstructured files with no consistent delimiter and variable line shapes must be routed to streaming extraction.

finanzen__LOBU__LOBU_2003__LA__LA4.csv
0 rows

File structure

Notes: The provided rows are free-form German text describing payroll documentation and tax forms. There is no consistent columnar structure — these appear to be legal/contractual text snippets rather than tabular data. The content discusses tax forms (Lohnausweis) and mentions a location (Kanton Zürich, Gemeinde Hochfelden), but does not contain discrete PII fields in a structured format. This qualifies as unstructured content per the rules.

finanzen__LOBU__LOBU_2003__LA__LA5.csv
0 rows

File structure

Notes: This is unstructured text (German-language payroll form template and sample data) with no consistent columnar structure. Contains embedded personal addresses (e.g., 'Kirchenfeld 51', '8052 Zürich') and AHV number (Swiss social security) '187.79.866.110' but lacks a consistent delimiter across lines. Maps to unstructured processing.

finanzen__LOBU__LOBU_2003__LA__LA6.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter or column structure. The sample contains German-language prose describing payroll forms and tax declarations rather than tabular data. There are no identifiable PII fields in structured columns to map.

finanzen__LOBU__LOBU_2003__LA__LA7.csv
0 rows

File structure

Notes: This is unstructured free-form text containing German-language legal/administrative content about tax forms and employment documentation. No consistent tabular structure exists across rows — each line contains different prose paragraphs. Though there are numeric values like '0', they appear to be placeholders or example values within the legal text, not actual personal data. No PII columns can be mapped.

finanzen__LOBU__LOBU_2003__LA__LA8.csv
0 rows

File structure

Notes: The file appears to be free-form German-language text containing legal/administrative prose about tax forms and employment certificates. No consistent column structure exists across rows — each line contains different narrative content. Though no explicit emails/phones are visible in the sample, unstructured processing is required due to lack of structured columns.

finanzen__LOBU__LOBU_2003__LA__LA9.csv
0 rows

File structure

Notes: This is free-form text containing German language descriptions of Swiss payroll tax forms. No consistent column structure exists; the data appears to be document text rather than tabular records. The sample shows German phrases about tax declarations and payroll forms rather than actual PII records.

finanzen__LOBU__LOBU_2003__Lohnabr__1.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. It contains Swiss accounting data including employee compensation details, tax calculations, and banking information, but lacks delimited columns. The sample shows Swiss German text with financial calculations rather than structured PII records.

finanzen__LOBU__LOBU_2003__Lohnabr__10.csv
0 rows

File structure

Notes: The provided text is a free-form financial statement template from Zynex AG, showing Swiss payroll/accounting calculations. It contains no structured columns or personal data. This is corporate financial documentation, not customer PII.

finanzen__LOBU__LOBU_2003__Lohnabr__2.csv
0 rows

File structure

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

Notes: This is not structured PII data. The file appears to be a Swiss payroll or financial statement document from Zynex AG, containing internal financial records and accounting details. There are no identifiable personal columns present — all entries are financial codes, amounts, and internal accounting references. No email, phone, name, address, or other PII fields are visible in the first 50 rows. The data is purely transactional and organizational.

finanzen__LOBU__LOBU_2003__Lohnabr__3.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__LOBU__LOBU_2003__Lohnabr__4.csv
0 rows

File structure

Notes: This is a free-form text document with no consistent column structure. It appears to be a payroll or accounting statement from Zynex AG, formatted as a narrative rather than a CSV or table. While it contains some personal identifiers like a name (Dave Poulton) and potentially sensitive financial data, the lack of a consistent delimiter or row structure means it should be processed as unstructured text. The document includes details such as address (Pfäffikerstrasse 6, 8604 Volketswil), phone number (Tf. 01 908 12 80), and AHV number (721.74.460.214), but these are embedded within prose rather than in a tabular format.

finanzen__LOBU__LOBU_2003__Lohnabr__5.csv
0 rows

File structure

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

Notes: The provided data appears to be a Swiss payroll or accounting document from Zynex AG. It contains financial calculations, tax codes, and payment details, but no identifiable personal information such as names, addresses, emails, phone numbers, DOB, SSN, etc. The only potential PII-like field (' Name, Vorname': 'Bolliger Jacqueline') appears only once in what seems to be a header or title line, not as part of a structured dataset. There are no repeated patterns or columns that map to PII fields. Therefore, no PII columns can be identified.

finanzen__LOBU__LOBU_2003__Lohnabr__6.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent column structure. It appears to be a Swiss payroll or accounting statement from Zynex AG, showing employee compensation details, tax withholdings, and other financial data. While it contains sensitive financial information, it lacks a consistent columnar structure with identifiable PII fields. The document includes elements like addresses, phone numbers, and potentially employee names in German, but these are embedded within prose rather than in a tabular format.

finanzen__LOBU__LOBU_2003__Lohnabr__7.csv
0 rows

File structure

Notes: This is unstructured financial payroll data from Zynex AG. The file contains no consistent column structure or identifiable PII fields. It appears to be a raw financial statement or payroll slip with no personal identifiers (names, addresses, emails, etc.). The data includes salary components, taxes, and other financial calculations but lacks any direct personal information that would map to PII fields.

finanzen__LOBU__LOBU_2003__Lohnabr__8.csv
0 rows

File structure

Notes: This is a free-form financial document (Swiss payroll/billing record) with no consistent columnar structure. Values appear as merged cells across rows, lacking a stable delimiter. Contains fragments like 'Pfäffikerstrasse 6', '8604 Volketswil', phone number '01 908 12 80', and 'AHV-Nr.', but these are embedded in prose rather than structured fields. No repeatable column pattern exists across the 50 rows.

finanzen__LOBU__LOBU_2003__Lohnabr__9.csv
0 rows

File structure

Notes: The file is free-form text with no consistent delimiter or column structure. It appears to be a Swiss payroll or accounting document from Zynex AG, containing unstructured financial and personal data in German. While there are some fields that could potentially contain PII (like names and addresses), the lack of a consistent column structure means we should treat this as unstructured text for processing.

finanzen__LOBU__LOBU_2003__Lohnblatt__01.csv
0 rows

File structure

Notes: This is not a delimited file with structured columns. The data appears to be free-form financial statements or payroll records with mixed text and numbers across rows. The first column appears to be a header row with values like 'Zynex AG' and subsequent rows contain financial data with names and amounts but lack a consistent delimiter or column structure. Given the unstructured nature and presence of names and financial data, this should be processed as unstructured text.

finanzen__LOBU__LOBU_2003__Lohnblatt__02.csv
0 rows

File structure

Notes: This is a free-form financial report (payroll ledger) with no consistent columnar structure. Columns appear as row labels and numeric values vary per line. Though names like 'Leisi Martin' appear, they are embedded in unstructured lines without a shared delimiter or repeating pattern. This matches the unstructured opt-out criteria: no consistent delimiter, variable line shapes, and contains personal names.

finanzen__LOBU__LOBU_2003__Lohnblatt__03.csv
0 rows

File structure

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

Notes: This is not structured PII data. The file appears to be payroll/financial records with headers like 'Zynex AG' and 'Giger Thomas', but these are not typical PII fields (no email, phone, DOB, etc.). Values represent financial codes, amounts, and percentages rather than personal identifiers. The context describes corporate financial records, and the visible columns are account codes and monetary values. No PII columns detected.

finanzen__LOBU__LOBU_2003__Lohnblatt__04.csv
0 rows

File structure

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

Notes: This is not a typical PII dataset; it's payroll/financial records from Zynex AG with structured financial columns. Column 1 contains what looks like a name 'Poulton Dave' but this is likely an employee name in a corporate financial context. However, per exclusion rules, corporate employee names are considered internal identifiers rather than public PII in this corporate financial context. No columns map to defined PII fields (email, phone, DOB, etc.). All columns represent financial codes, amounts, percentages, and internal references.

finanzen__LOBU__LOBU_2003__Lohnblatt__05.csv
1 column2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Bolliger Jacqueline', value matches typical Swiss full name format

Notes: This appears to be payroll data with employee names and financial calculations. Only column 1 contains PII (fullName). All other columns are financial codes, percentages, and amounts — no additional PII fields present. Swiss naming convention (last name first) confirms identification.

finanzen__LOBU__LOBU_2003__Lohnblatt__06.csv
0 rows

File structure

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

Notes: This is a financial statement table with account codes and amounts. No personal identifiable information (PII) is present. Columns contain account names like 'Grundlohn' (gross salary), 'Nettolohn' (net salary), and percentages for taxes. All values are monetary amounts or percentages, not personal data.

finanzen__LOBU__LOBU_2003__Lohnblatt__07.csv
0 rows

File structure

Notes: This is a financial ledger structure with no identifiable personal information columns. The file contains accounting codes (like 'Grundlohn', 'Vers'leist.'), monetary amounts, and percentages formatted as text values across multiple rows, typical of Swiss corporate financial statements. No PII fields such as names, emails, or addresses appear in the sample. The structure is tabular but lacks any personal data columns, making it non-PII despite being structured.

finanzen__LOBU__LOBU_2003__Lohnblatt__08.csv
0 rows

File structure

Notes: This is a free-form financial report structure (Zynex AG payroll ledger). Rows contain month labels (Jan/Feb/Mär) and financial codes (Grundlohn, Spesen, AHV-Abz) with monetary values. No consistent column alignment exists — headers appear in row 0 but values are misaligned, and row 0 itself is not a clean header row. Despite containing monetary data, this is not PII. No emails, phones, names, or addresses are present. The format is unstructured financial reporting, not CSV.

finanzen__LOBU__LOBU_2003__Lohnblatt__09.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. The data appears to be Swiss payroll/financial records with headers like 'Zynex AG' and values like 'Grundlohn' (base pay), 'Spesen' (expenses), and percentages for AHV/ALV taxes. No identifiable PII fields (names, emails, addresses) are present in the visible structure. This is corporate financial data, not customer PII.

finanzen__LOBU__LOBU_2003__Lohnblatt__10.csv
0 rows

File structure

Notes: This is a financial accounting file with no personal identifiers. It contains structured financial records (payroll data, tax bases, percentages, amounts) in German with columns like 'Grundlohn' (base salary), tax rates, and net pay. No PII fields (names, emails, addresses, etc.) are present. The data appears to be aggregated or anonymized financial reporting for Zynex AG.

finanzen__LOBU__LOBU_2003__Lohnblatt__11.csv
0 rows

File structure

Notes: This is a financial ledger table (not a CSV with named columns). The sample shows structured financial data rows with account codes, percentages, and amounts. No PII fields are present. Per the rules, unstructured files with no column structure return empty columns object.

finanzen__LOBU__LOBU_2003__Lohnblatt__12.csv
0 rows

File structure

Notes: This is a financial statement document, not a delimited PII dataset. The structure is free-form with financial codes, account numbers, and monetary values. No personal PII fields (names, emails, addresses, etc.) are present. Columns appear to represent accounting codes (e.g., 'Grundlohn', 'Vers'leist.', 'AHV-Abz') and monetary amounts, typical of corporate financial records.

finanzen__LOBU__LOBU_2003__Lohnblatt__13.csv
0 rows

File structure

Notes: This is not a structured CSV file. The data appears to be a free-form financial report or payroll summary from Zynex AG, formatted with merged cells and German financial terminology. Columns are not consistently delimited and the rows contain mixed data types (month names, account codes, monetary values). There are no identifiable PII fields like names, emails, or addresses in this sample. The content is purely financial accounting data (salaries, taxes, social security deductions) with no personal identifiers.

finanzen__LOBU__LOBU_2003__Lohnblatt__14.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent delimiter or column structure. The data appears to be formatted as a table with merged cells and headers spanning multiple rows/columns, showing payroll/billing data for Zynex AG. No identifiable PII fields are present in the sample.

finanzen__LOBU__LOBU_2003__Lohnblatt__15.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. The data appears to be a mix of text and numerical values representing payroll/accounting entries, with no identifiable PII fields. The rows contain financial codes, amounts, and descriptions rather than personal data. The format does not conform to any structured tabular format (CSV, TSV, etc.), and therefore should be processed as unstructured text.

finanzen__LOBU__LOBU_2003__Lohnblatt__16.csv
0 rows

File structure

Notes: The provided data appears to be a structured financial report in German (Zynex AG payroll/financial records). It contains no personal identifiable information (PII) fields like names, emails, addresses, or phone numbers. The columns are purely financial codes and monetary values, with no personal data. This is corporate financial documentation, not individual user data.

finanzen__LOBU__LOBU_2003__Lohnblatt__17.csv
0 rows

File structure

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

Notes: This is a financial statement file with no PII columns. Contains accounting codes, percentages, and monetary values. All columns map to internal financial data (salaries, taxes, deductions) and no personal identifiers are present.

finanzen__LOBU__LOBU_2003__Lohnblatt__18.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. The data appears to be financial statements or payroll records from Zynex AG, showing account codes, amounts, and percentages. There are no identifiable personal information fields (PII) in a structured format. The data is not in a CSV format and lacks consistent delimiters or row structures, confirming it as unstructured text.

finanzen__LOBU__LOBU_2003__Lohnblatt__19.csv
0 rows

File structure

Notes: This is not a structured dataset with consistent columns. The rows appear to be financial statements or payroll data in a free-form tabular layout, not a CSV or delimited file. There are no identifiable PII fields like names, emails, or addresses in this snippet. The content appears to be internal corporate financial records with account codes and amounts, typical of ERP system outputs. Since there is no consistent delimiter or column structure, and no PII is visible, this is treated as unstructured text.

finanzen__LOBU__LOBU_2003__Lohnblatt__20.csv
0 rows

File structure

Notes: This is a financial statement / payroll report with no consistent column structure. The data appears to be formatted as a table with merged cells and headers spanning multiple rows (e.g., 'Zynex AG' appears to be a title row, followed by account codes and descriptions). There are no identifiable PII fields (names, emails, addresses, etc.) in the visible sample. The content consists of account codes, percentages, and monetary values typical of financial reporting.

finanzen__LOBU__LOBU_2003__Lohnblatt__AHV-ABR.csv
0 rows

File structure

Notes: This is a free-form text document (payroll statement) with no consistent delimiter structure. It contains Swiss payroll data for Zynex AG from 2003, including employee names and AHV insurance numbers, but lacks a tabular format with columns. The content appears to be a printed document rather than a structured CSV or similar format.

finanzen__LOBU__LOBU_2003__Lohnblatt__AHV-ABR_D.csv
0 rows

File structure

Notes: This is a free-form text file containing Swiss payroll records with no consistent delimiter structure. It includes lines with employee data but lacks a defined column layout. While there are names and potentially other PII-like data, the absence of a consistent delimiter across lines means it must be processed as unstructured text. The content appears to be a payroll statement from Zynex AG in Volketswil, Switzerland, dated 2003, with employee names (e.g., Bolliger Jacqueline, Brunner Mark) and insurance numbers.

finanzen__LOBU__LOBU_2003__Lohnblatt__Total_Lohnbl.csv
1 column8 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names (e.g., 'Brunner Mark', 'Leisi Martin')

Notes: Only column 1 contains PII (fullName). All other columns are financial codes, percentages, monetary amounts, and gender flags — none contain email, phone, address, DOB, SSN, or other PII types. Column 18 contains gender codes (M/F) but is not a PII field per exclusion rules.

finanzen__LOBU__LOBU_2003__Lohnjournal__Apr.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (fullName). All other columns are financial accounting fields (salaries, taxes, deductions) with no personal identifiers beyond the name field. No emails, phone numbers, addresses, DOB, or SSNs are present.

finanzen__LOBU__LOBU_2003__Lohnjournal__Aug.csv
0 rows

File structure

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

Notes: This is a structured financial payroll file from Zynex AG with no PII fields. Column 1 contains names but these are employee names used in internal payroll records. Per the rules, employee names in corporate financial records are considered internal identifiers rather than public PII when there is no customer/client relationship. All other columns contain salary components, tax calculations, and financial codes (P-Nr. = payroll number). No emails, addresses, SSNs, or other searchable PII is present.

finanzen__LOBU__LOBU_2003__Lohnjournal__Daten.csv
4 columns15 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
2fullNamehigh[2] header 'Name, Vorname' (Name, First name in German), values like 'Brunner Mark', 'Leisi Martin' confirm combined last+first name format
3cityhigh[3] header 'Wohnort' (place of residence in German), values like '8604 Volketswil', '4612 Wangen b. Olten' are Swiss postal code + city strings
4address1high[4] header 'Adresse' (address), values like 'Pfäffikerstrasse 6', 'Haftlet 18' are street addresses
5ssnhigh[5] header 'AHV-Nr.' (AHV number = Swiss social security/pension number), values like '222.77.291.219', '591.72.265.213' match Swiss AHV number format (XXX.XX.XXX.XXX)

Notes: Swiss payroll register (Personalverzeichnis) for Zynex AG, 2003. Only 5 employee records present (rows 3-7). No consistent header row — row 2 contains German column labels. Col 3 'Wohnort' values include postal code prepended to city name (Swiss format). Col 5 AHV-Nr. is the Swiss social insurance number, equivalent to SSN. Col 6 'Eintritt' is employment start date (not DOB), skipped. Remainder of file is empty rows and German spreadsheet usage instructions.

finanzen__LOBU__LOBU_2003__Lohnjournal__Dez.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (full names). All other columns are financial/employment codes, amounts, and tax calculations — no addresses, emails, phones, DOB, SSN, etc. The 'P-Nr.' in column 0 appears to be a payroll reference number (skip). No unstructured text present.

finanzen__LOBU__LOBU_2003__Lohnjournal__Feb.csv
0 rows

File structure

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

Notes: This is a financial payroll report for Zynex AG, not a PII dataset. Columns contain only internal accounting codes, salary figures, and tax calculations. No personal identifiers (names, addresses, emails, etc.) are visible beyond generic placeholder names that appear to be sample data. All columns map to skip categories: internal IDs (P-Nr.), salary components (Grundlohn, Spesen, Nettolohn), tax codes (AHV-Abz, UVG-Abz), and financial totals. No PII fields are present.

finanzen__LOBU__LOBU_2003__Lohnjournal__Grat.csv
0 rows

File structure

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

Notes: This is a payroll/financial record file with no PII fields. Columns represent internal accounting codes, percentages, and calculated values (e.g., AHV-Basis, ALV-Basis). No names, addresses, or other personal identifiers are present — only internal reference numbers like 'P-Nr.' and financial calculations. The values are internal financial codes and monetary amounts, not personal data.

finanzen__LOBU__LOBU_2003__Lohnjournal__Jan.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark', 'Leisi Martin'

Notes: Only column 1 contains PII (fullName). All other columns are financial/accounting codes, amounts, and percentages — no addresses, emails, phones, or DOB present. The file appears to be payroll data with employee names alongside salary calculations, tax withholdings, and insurance deductions. No other PII fields detected.

finanzen__LOBU__LOBU_2003__Lohnjournal__Jul.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (fullName). All other columns are financial codes, amounts, and internal accounting fields (e.g., 'Grundlohn', 'EO', 'Spesen', 'AHV-Abz') — no PII present. This aligns with the breach description of financial records and billing data.

finanzen__LOBU__LOBU_2003__Lohnjournal__Jun.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: Only column 1 contains PII (fullName). All other columns are internal financial codes, amounts, and calculations (e.g., 'Grundlohn', 'Spesen', 'AHV-Abz'). These are non-PII per exclusion rules (financial/transactional data, internal IDs, flags).

finanzen__LOBU__LOBU_2003__Lohnjournal__Lohnsammelbeleg.csv
0 rows

File structure

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

Notes: This is purely financial/accounting data (Zynex AG corporate ledger) with no personal identifiers. Columns represent account codes, transaction types, and monetary amounts. No PII fields detected.

finanzen__LOBU__LOBU_2003__Lohnjournal__M_r.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: This appears to be a payroll ledger with Swiss SME employee names and salary data. Only the 'Name' column contains PII (full names). All other columns are financial codes, amounts, and tax calculations (no addresses, emails, etc.).

finanzen__LOBU__LOBU_2003__Lohnjournal__Mai.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark', 'Leisi Martin'

Notes: Only column 1 contains PII (full names). All other columns are financial codes, percentages, and amounts (e.g., 'Grundlohn', 'Nettolohn', 'Steuerpfl.') with no personal identifiers. No emails, phone numbers, addresses, or other PII fields detected.

finanzen__LOBU__LOBU_2003__Lohnjournal__Nov.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark'

Notes: This is an internal payroll file with corporate financial data. Only column 1 contains PII (full names). All other columns are internal financial codes, amounts, and tax calculations — no emails, addresses, phones, or other PII are present.

finanzen__LOBU__LOBU_2003__Lohnjournal__Okt.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark', 'Leisi Martin', 'Giger Thomas', 'Poulton Dave'

Notes: Only column 1 contains PII (fullName). All other columns represent financial transaction codes, amounts, tax calculations, and internal accounting identifiers (e.g., 'Zynex AG', 'Grundlohn', 'EO', 'Vers'leist.', etc.) — these are NOT personal PII and must be skipped per rules. No emails, phones, DOB, addresses, or SSNs are present.

finanzen__LOBU__LOBU_2003__Lohnjournal__Sep.csv
1 column6 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are full names like 'Brunner Mark', 'Leisi Martin'

Notes: Only column 1 contains PII (fullName). All other columns are financial/employment data (salaries, tax codes, journal entries) or internal identifiers, none of which contain PII per rules. No email, phone, address, DOB, SSN, etc. visible in sample.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__AHVAB.csv
9 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighcompany name, matches exclusion rule for company/business
1lastNamehigh[1] values are surnames like Brunner, Leisi, Poulton
2firstNamehigh[2] values are given names like Mark, Martin, Dave
3skiphighstart date column, not a PII field
4skiphighend date column, not a PII field
5skiphighAHV-Lohn numeric salary field
6skiphighALV-Lohn numeric salary field
7skiphighKinderzulagen numeric child allowance field
8skiphighKK-Lohn numeric insurance field

Notes: This is a Swiss AHV Lohnbescheinigung (Wage Certificate) file from Zynex AG. Contains employee names (first and last), employment dates, and salary/allowance figures. No email, phone, address, or other PII beyond names are present. The file appears to be a structured CSV with no header row; columns 0-8 map as shown. Columns 3-8 contain employment/dates and financial data which are not PII fields per the rules.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__AbsenzPromea.csv
1 column21 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] values contain full names like 'Brunner Mark', 'Leisi Martin', 'Poulton Dave'

Notes: This file appears to be an absence compensation table (Absenzentschädigung) from Zynex's internal records. It contains employee names but no other PII fields. The structure is a simple table with absence types and days, not a typical CSV with repeated headers.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Bankenstamm.csv
5 columns1,852 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighcolumn 'BCNr' contains internal bank codes, not PII
1skiphighcolumn 'Name' contains institutional names (Swiss National Bank, UBS, Credit Suisse) not personal names
2address1highcolumn 'Zusatz1' contains street addresses like 'Börsenstrasse 15', 'Rue Diday 8'
3address2highcolumn 'Zusatz2' contains postal codes and case postale information like 'Postfach 4388', 'Case postale 259'
4cityhighcolumn 'PLZOrt' contains city and canton information like '8022 Zürich', '3003 Bern'

Notes: 50 rows shown, containing Swiss bank branch addresses. No personal identifiers (names, emails, phones) present - all entries are institutional banking locations. Columns 0-1 contain internal bank codes and institutional names, columns 2-4 contain structured address components.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Grunddaten.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The data appears to be German-language payroll and accounting template text rather than structured records containing PII. No column mapping can be performed.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Journale.csv
0 rows

File structure

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

Notes: This is not PII data; it appears to be internal financial/billing records from Zynex AG. Columns contain company names (Firma), addresses (Pfäffikerstrasse 6), employee compensation figures (Stundenlohn, Monatslohn), and invoice totals. No personal identifiers (names, emails, SSNs, etc.) are present. Column 11 ('AHV-Nr.:') and 12 ('E3454') show Swiss social security numbers but these appear to be placeholder headers/values in this financial context, not actual PII. All columns map to business/financial data per exclusion rules.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Lohnabrechnung_1.csv
0 rows

File structure

Notes: This is an unstructured payroll document (Lohnabrechnung) in German format. The file contains no consistent columnar structure — it's a free-form table with merged cells, headers spanning multiple lines, and financial calculations. While it contains a Swiss AHV number (social security equivalent) and a personal reference number (Personal-Nr.), these appear embedded within free-text lines rather than in a repeatable columnar pattern. The file lacks a consistent delimiter and row structure across lines, meeting the criteria for unstructured opt-out. No column mapping is possible.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Lohnabrechnung_2.csv
0 rows

File structure

Notes: This is a free-form payroll document in German with no consistent columnar structure. It contains Swiss employee data (names, addresses, AHV number, bank account) but lacks a repetitive delimiter pattern across rows. The content appears to be a printed payslip with merged cells and narrative text rather than a machine-readable table. Per the unstructured rules, we return empty columns and flag for streaming extraction.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Lohnabrechnung_3.csv
0 rows

File structure

Notes: This is a free-form payroll document (German language) with no consistent column structure. It contains unstructured lines and appears to be a printed pay slip format rather than a CSV or tabular dataset. While it contains names (e.g., 'Poulton Dave') and addresses (e.g., 'Schulhausstrasse 6', '8182 Hochfelden'), these appear as free text rather than in a columnar format. The document is a Swiss payroll statement for Zynex AG, showing salary details for December 2004, and does not have a consistent delimiter or header structure. The unstructured nature means it should be processed with free-text extraction rather than column mapping.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Lohnabrechnung_vorlage.csv
0 rows

File structure

Notes: The file is free-form text containing Swiss payroll records with no consistent delimiter structure. The data includes headers and numerical values but lacks a tabular format with defined columns. The content appears to be a payroll statement with fields like AHV number, personal number, dates, and salary components, but there are no identifiable PII fields such as names, emails, or addresses in the provided snippet. The structure varies per line with mixed headers and data.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Lohnausweis_1.csv
0 rows

File structure

Notes: This is a document-style file with no consistent column structure. The sample shows unstructured text lines containing employment and tax information (e.g., 'Lohnausweis für die Steuererklärung', 'Arbeitsort', 'Arbeitnehmer', 'AHV-Nummer'). There are no repeated delimiters or tabular patterns across the first 50 rows, and values appear to be free-form text. Even though some lines contain AHV numbers (Swiss social security numbers), they are embedded in prose and not in a structured column format. This meets the unstructured criteria: (a) no consistent delimiter, (b) lines have different shapes, (c) no clear columnar mapping possible. Return empty columns object.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Lohnausweis_2.csv
0 rows

File structure

Notes: This is a free-form document (Swiss tax wage statement template) with no consistent column structure. It contains headers like 'Lohnausweis für die Steuererklärung' and unstructured rows with employment details, addresses, and AHV numbers, but lacks a repeating tabular format with defined columns. No PII can be reliably mapped due to absence of structured columns.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Lohnausweis_3.csv
0 rows

File structure

Notes: This is unstructured data (Swiss tax form template 'Lohnausweis für die Steuererklärung'). No consistent column structure exists; the sample shows free-form text with headers like 'Abteilung', 'Arbeitsort', 'Exemplar für:', and values like '8604 Volketswil' and 'Poulton Dave'. Though names and addresses appear, the format lacks a consistent delimiter or column alignment across rows, and the content is a document template, not a dataset with repeatable fields. Therefore, it is treated as unstructured text for PII extraction.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Lohnausweis_vorlage.csv
0 rows

File structure

Notes: The provided sample shows free-form text lines with no consistent delimiter structure. The lines appear to be unstructured document content (Swiss tax declaration form header snippets) rather than tabular data. No column mapping can be performed.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Lohnkonto_1.csv
0 rows

File structure

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

Notes: This is NOT a PII dataset. The file appears to be internal Swiss payroll accounting records from Zynex AG (a Swiss web hosting/CMS company). All visible values are corporate financial codes (Lohnkontoblatt = payroll account), internal employee IDs (Pers. Nr.), employment metadata (Geschlecht = gender, AHV-Nr. = Swiss social security number), and accounting figures. No actual names, addresses, or emails appear — only template headers and placeholder values. The structure shows accounting periods (Januar, Februar...), account types (Aktiv/Passiv), and monetary amounts. This aligns with the breach description of internal financial records, not customer PII.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Lohnkonto_2.csv
0 rows

File structure

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

Notes: This is a structured financial ledger file from Zynex AG, not containing personal PII fields. Columns contain accounting codes, dates, amounts, and internal references. No emails, phone numbers, names, or addresses are present. The column 'Name, Vorname:' appears to be a header label, but its value 'Leisi Martin' is actually part of the data row and represents an account code or internal designation, not a person's full name. All values are financial or operational in nature.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Lohnkonto_3.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Lohnkonto_vorlage.csv
0 rows

File structure

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

Notes: This is a Swiss payroll ledger (Lohnkontoblatt) from Zynex AG. All visible columns are internal accounting identifiers, financial codes, and accounting periods. No PII fields (names, addresses, dates of birth, etc.) are present in the first 50 rows — the values shown are placeholders or financial codes. Columns like 'Name, Vorname:' and 'Geburtsdatum:' appear to be labels for potential data entry, but no actual personal data is filled in within this sample. Therefore, no PII columns can be mapped.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Personaldaten.csv
8 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Bezeichnung' and values are full names like 'Brunner Mark'
3lastNamehigh[3] header 'Name' and values are surnames like 'Brunner'
4firstNamehigh[4] header 'Vorname' and values are given names like 'Mark'
5address1high[5] header 'Strasse' and values are street addresses like 'Pfäffikerstrasse 6'
6ziphigh[6] header 'PLZ' and values are Swiss postal codes like '8604'
7cityhigh[7] header 'Ort' and values are cities like 'Volketswil'
9dobhigh[9] header 'Geburtsdatum' and values are numeric date representations
13ssnhigh[13] header 'AHVNr' and values match Swiss AHV number format (e.g., '222.77.291.219')

Notes: 21 total columns, 8 contain PII. Columns 0 (PersonalNr), 2 (Anrede), 8 (Geschlecht), 10 (Heimatort), 11 (Kinderzahl), 12 (Kindernamen), 14 (Beruf), 15 (Eintritt), 16 (Austritt), 17 (BetriebsteilSUVA), 18 (BankPost), 19 (Bankverbindung), and 20 (Kontonummer) are internal IDs, business codes, or non-PII fields and should be skipped.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Personalstamm.csv
7 columns5 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3fullNamehigh[3] header 'Name', values are surnames
4firstNamehigh[4] header 'Vorname', values are given names
5address1high[5] header 'Strasse', values are street addresses
6ziphigh[6] header 'PLZ', values are Swiss postal codes
7cityhigh[7] header 'Ort', values are city names
8genderhigh[8] header 'Geschlecht', values are numeric codes for gender
9skiphigh[9] header 'Geburtsdatum', values are dates in MM/DD/YY format

Notes: This is a Swiss corporate personnel file (Personalstamm) from Zynex. Contains personal data for employees, including full names, addresses, gender codes, and birth dates. No emails, phones, usernames, or SSNs appear in the sample. The file is formatted as a CSV without a proper header row; columns are labeled in the second data row. Columns 0,1,2 are empty or structural. Columns 10+ contain non-PII employment metadata (children count, AHV social security number, employment dates, bank account details) and are skipped per rules.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__RekapMonat.csv
0 rows

File structure

Notes: This is unstructured financial/ERP data from Zynex AG. The file contains German-language financial records with no consistent column structure across rows. While there is a name-like entry ('Peter Brunner, Treuhand- u. Steuerrec...'), this is embedded in free-form text lines and not part of a defined columnar structure. The file shows financial codes (AHV-Abr.Nr., Suva-Abr.Nr.), amounts, and internal references rather than consistent PII fields. This meets the unstructured opt-out criteria: (a) no consistent delimiter, (b) wildly varying line shapes, (c) no columns to map.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__SuvaAb.csv
1 column11 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] contains mixed 'Name / Vorname' pattern with full names like 'Brunner Mark'

Notes: Only column 1 contains PII (full names). All other columns are financial/employment data, timestamps, or internal accounting codes — none contain email, phone, DOB, SSN, or address fragments. The file appears to be Swiss payroll records with German headers; no other PII fields are present in the first 50 rows.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Total.csv
0 rows

File structure

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

Notes: The file appears to be a non-structured financial record template or header row from Zynex AG, a Swiss company. The data contains no actual PII values in the first 50 rows. All entries are either placeholders, generic labels, or financial/accounting codes (e.g., 'Lohnkontoblatt', 'AHV-Abr.Nr.', 'Bankverbindung'). No columns map to PII fields because there are no personal identifiers (names, addresses, emails, etc.) present in the sample data. The content resembles an internal corporate template rather than actual customer or employee records.

finanzen__LOBU__LOBU_2004__LOBU_Zynex_2004__Verg.csv
0 rows

File structure

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

Notes: This is a free-form financial document (Vergütungsauftrag) with no consistent columnar structure. It contains payment instructions and recipient details but lacks a repeating tabular format with identifiable PII columns. No structured PII fields are present.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__AHVAB.csv
0 rows

File structure

Notes: This is a payroll document (AHV-Lohnbescheinigung / Swiss wage certificate) in report format, not a delimited data export. It contains company header information (Zynex AG, address), document metadata (date, page numbers, reference numbers), and repeating sections with employee payroll data. While it does contain employee names (Brunner Mark, Leisi Martin, Poulton Dave) and Swiss social security numbers (Versicherten-Nummer), the structure is a formatted report with merged cells, subtotals, and multi-line headers — not rows of consistent comma/tab-delimited records. This is a PDF or spreadsheet report export, not a CSV suitable for column-based PII extraction. The data should be handled as a document rather than structured records.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__AbsenzPromea.csv
0 rows

File structure

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

Notes: This file contains only structured data related to employee absence compensation and leave categories. There are no personal identifiers, email addresses, phone numbers, or other PII fields in the visible rows. The data is purely categorical and numerical, tracking absence days, types of leave, and monetary amounts. No columns map to PII fields.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Bankenstamm.csv
4 columns3,624 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] values are formal institution names matching Swiss bank branches (UBS AG, UBS SA), which function as full legal entity names in corporate records
2address1high[2] values match Swiss street addresses and building numbers (e.g., 'Börsenstrasse 15', 'Rue Diday 8', 'Via Canova 12')
3address2high[3] contains secondary address components like 'Postfach', 'Case postale', or building identifiers that function as address line 2
4ziphigh[4] contains valid Swiss postal codes (e.g., '8022 Zürich', '3003 Bern', '1211 Genève 2') in ZIP+place format

Notes: All rows represent corporate bank branch addresses in Switzerland. No personal PII fields (names, emails, etc.) are present — these are institutional records from Zynex's financial data breach. Columns 0 (BCNr) is an internal bank code and mapped to skip.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Differenz_AHV.csv
0 rows

File structure

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

Notes: This is a financial record file with no personal identifiable information (PII). Columns contain only financial metrics (e.g., AHV contributions, percentages, basis amounts, contributions, differences) and no names, addresses, emails, or other PII fields. All columns map to skip per exclusion rules (financial/transactional data).

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Grunddaten.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent columnar structure. The content appears to be German-language template or configuration data for payroll processing, including gender codes, company departments, salutations, and payroll text snippets. There are no structured rows or columns containing personal identifiable information (PII) in a tabular format. The file contains no embedded emails or phone numbers that would trigger unstructured extraction.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Journale.csv
0 rows

File structure

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

Notes: This is NOT a PII dataset. The file appears to be an internal corporate financial record from Zynex AG (Swiss web hosting company), showing employee wages and company addresses. Columns contain business identifiers (Firma, Jahr), internal codes (AHV-Nr., E3454), dates (Druckdatum), and financial totals — no personal names, emails, phone numbers, or addresses. Column 1 contains a single company address "Pfäffikerstrasse 6, 8604 Volketswil" and the company name "Zynex AG". All other columns are numeric financial data or internal reference codes. Per exclusion rules, company/business fields are skipped. No PII fields are present.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnabrechnung_1.csv
0 rows

File structure

Notes: free-form text with embedded personal data, no consistent delimiter structure. Contains Swiss payroll information with names, addresses, and personal identifiers in unstructured format.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnabrechnung_2.csv
0 rows

File structure

Notes: The provided data is a free-form payroll document (Lohnabrechnung) with no consistent columnar structure. It contains unstructured German text describing a salary statement for an employee. While it includes personal data such as a name (Leisi Martin), there is no repetitive column pattern across lines to map as CSV/TSV fields. This qualifies as unstructured data with embedded PII that should be processed by a streaming email/phone extractor. No column mapping is possible due to the absence of a consistent delimiter or row structure.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnabrechnung_3.csv
0 rows

File structure

Notes: This is a free-form payroll document in German. No consistent column structure exists across lines; values appear as key-value pairs and tabular sections. Contains embedded personal data such as name (Poulton Dave) and address (Egetswilerstrasse 29, 8302 Kloten), but lacks a repeatable columnar format. Per rules, this qualifies as unstructured text with embedded PII requiring streaming extraction.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnabrechnung_vorlage.csv
0 rows

File structure

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

Notes: This is not a structured PII dataset. The file appears to be a Swiss payroll/labor calculation template (Lohnabrechnung) with headers in German and columns representing payroll line items (e.g., AHV, Suva, KTG, Nettolohn). No personal identifiers such as names, addresses, emails, or DOBs are present in the first 50 rows. All visible data are payroll codes, amounts, and empty placeholders. Therefore, there are no PII columns to map.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnausweis_1.csv
0 rows

File structure

Notes: This is not a structured tabular file. The sample shows unstructured headers and values that appear to be German text labels and codes, not data records. There are no consistent column positions or delimiters across rows, and the content resembles document metadata or template headers rather than actual PII data. No actionable PII columns exist to map.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnausweis_2.csv
0 rows

File structure

Notes: This file appears to be free-form German-language corporate accounting records with no consistent column structure. The sample shows mixed text entries like 'Rentenbescheinigung', 'Unentgeltliche Beförderung zwischen W...', and header-like strings that don't align across rows. No clear delimiter or repeating column pattern exists. While it contains Swiss AHV numbers (social security) and potentially personal names ('Leisi Martin'), the lack of structured columns prevents mapping. This qualifies as unstructured text with embedded PII requiring specialized extraction.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnausweis_3.csv
0 rows

File structure

Notes: This is not structured tabular data. The sample rows show unstructured free-form text with no consistent delimiter. It appears to be German-language internal corporate documentation (pay slips, annual reports, etc.) with no machine-readable column structure. Given the context (Zynex internal financial records), this is likely free-form corporate notes or scanned document OCR output rather than a CSV with defined fields. Since there is no consistent delimiter or column structure, and the data appears to be prose-like, we classify this as unstructured.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnausweis_alt_vorlage.csv
0 rows

File structure

Notes: This is a free-form document titled 'Lohnausweis für die Steuererklärung' (Pay slip for tax declaration). It contains unstructured German text with no consistent columnar format across rows. The values are free-form phrases like 'Abteilung', 'Beschäftigungsdauer:', 'Arbeitsort', '8604 Volketswil', 'Exemplar für:', and 'Arbeitnehmer'—not tabular data. No PII fields can be mapped because the structure is narrative prose, not a CSV or delimited file. This file is purely descriptive and does not contain any machine-readable personal data in a columnar format.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnausweis_vorlage.csv
0 rows

File structure

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

Notes: This is a non-PII corporate financial document in German. Columns contain internal codes, years, and German descriptions of benefits/perks (e.g., 'Unentgeltliche Beförderung zwischen W...'). No personal identifiers (names, emails, addresses, etc.) are present. All columns are corporate metadata, financial categories, or internal tracking codes — none map to PII fields.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnkonto_1.csv
0 rows

File structure

Notes: Flattened Swiss payroll form (Lohnkontoblatt) for employee Brunner Mark at Zynex AG. Columns do not represent consistent field types across rows — each column mixes labels, months, amounts, and PII values (name, address, DOB, AHV number, gender) from a transposed form layout. No valid column-to-field mapping is possible. PII present includes full name ('Brunner Mark'), address ('Pfäffikerstrasse 6, 8604 Volketswil'), DOB ('6/29/77'), gender ('M'), and Swiss AHV number ('222.77.291.219') — these should be extracted via free-form scanner.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnkonto_2.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamemedium[6] first value 'Leisi Martin' matches Name/Vorname label in [5]; subsequent rows contain address and DOB mixed in same column — fullName is the primary PII anchor
10skiphigh[10] value '591.72.265.213' matches Swiss AHV-Nr (social security) format; column header context in [9] is 'AHV-Nr.'

Notes: Lohnkontoblatt (payroll account sheet) for a single employee (Leisi Martin, Zynex AG). File is a semi-structured form export — labels appear in odd columns, values in adjacent columns. Column [6] contains fullName as primary PII (also mixes address/DOB in lower rows but fullName is the mappable field). Column [10] contains Swiss AHV social security number and gender marker 'M'. Delimiter appears to be tab. Only 1–2 employee records visible; this is an internal HR/payroll document not a customer database.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnkonto_3.csv
6 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamehigh[6] header context 'Name, Vorname:' (Name, First name:), value 'Poulton Dave' is a full name
6_addressaddress1high[6] row context shows 'Egetswilerstrasse 29' following the name, Swiss street address
6_citycityhigh[6] row context shows '8302 Kloten' (PLZ, Ort: postal code, city)
6_dobdobhigh[6] row context 'Geburtsdatum:' (date of birth), value '11/29/74' is a DOB in MM/DD/YY format
9_gendergenderhigh[9] header 'Geschlecht' (gender in German), value 'M' (male)
10_ssnssnhigh[10] header 'AHV-Nr.' (Swiss AHV/AVS social security number), value '721.74.460.214' matches Swiss AHV format (xxx.xx.xxx.xxx)

Notes: This is a Swiss payroll register (Lohnkontoblatt) from Zynex AG spanning 2005. The file is semi-structured with embedded headers and row labels. Key PII identified: employee full name (Poulton Dave), address (Egetswilerstrasse 29, 8302 Kloten), gender (M), date of birth (11/29/74), and Swiss AHV social security number (721.74.460.214). Remaining columns contain payroll accounting data (monthly values, entry/exit dates, employee number, account number) — these are skipped as non-PII.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Lohnkonto_vorlage.csv
0 rows

File structure

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

Notes: This is a financial payroll document (Lohnkontoblatt) from Zynex AG. All visible columns contain accounting codes, account names, dates, numeric values, and internal identifiers. No PII fields (names, addresses, emails, etc.) are present in the first 50 rows. Columns like 'Name, Vorname:' and 'AHV-Nr.' appear to be headers but have no actual data in the sample rows — they are empty or contain placeholder text. Therefore, no PII columns to map.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Personaldaten.csv
8 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Bezeichnung', values are full names like 'Brunner Mark'
3lastNamehigh[3] header 'Name', values are surnames like 'Brunner'
4firstNamehigh[4] header 'Vorname', values are given names like 'Mark'
5address1high[5] header 'Strasse', values are street addresses
6ziphigh[6] header 'PLZ', values are Swiss postal codes like '8604'
7cityhigh[7] header 'Ort', values are city names like 'Volketswil'
9dobmedium[9] header 'Geburtsdatum', values look like encoded dates (DDMMYY format)
13ssnhigh[13] header 'AHVNr', values match Swiss AHV number format (e.g., '222.77.291.219')

Notes: 27 total columns; 8 contain PII (fullName, lastName, firstName, address1, zip, city, dob, ssn). Columns 0, 2, 8, 11-26 contain internal identifiers, employment data, or flags and are skipped per rules.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Personalstamm.csv
7 columns7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3lastNamehigh[3] column labeled 'Name', values are surnames
4firstNamehigh[4] column labeled 'Vorname', values are given names
5address1high[5] column labeled 'Strasse', values are street addresses
6ziphigh[6] column labeled 'PLZ', values are postal codes
7cityhigh[7] column labeled 'Ort', values are cities
8gendermedium[8] column labeled 'Geschlecht', values are numeric codes for gender
9skiphigh[9] column labeled 'Geburtsdatum', values are dates in MM/DD/YY format

Notes: This is a structured CSV file with employee personal data from Zynex AG. Columns 0-2 and many later columns are metadata/internal IDs and were skipped. Columns 3-9 contain PII: lastName, firstName, address1, zip, city, gender, dob. The file is in German and appears to be employee master data (Personalstamm) rather than customer billing records.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__RekapMonat.csv
0 rows

File structure

Notes: The provided data appears to be unstructured financial records from Zynex AG, containing German-language entries such as addresses, dates, and financial terms. There are no consistent column patterns or identifiable PII fields in the sample. The data resembles accounting or payroll records with entries like addresses, dates, and monetary values, but lacks structured personal information such as names, emails, or phone numbers in a columnar format. Therefore, this file should be processed as unstructured text.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__SuvaAb.csv
0 rows

File structure

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

Notes: The file appears to be unstructured financial accounting records with no consistent column mapping to PII fields. The data contains company names, addresses, and financial figures but no identifiable personal information such as names, emails, or phone numbers that map to the defined PII fields. The content is purely corporate financial data with no personal customer or employee details visible in the first 50 rows.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Total.csv
0 rows

File structure

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

Notes: This file appears to be a Swiss payroll or financial document template (Lohnkontoblatt = payroll slip) from Zynex AG. The content consists of header labels and placeholder instructions rather than actual personal data. No PII fields are present in the sample rows. All columns appear to be structural/metadata fields for a payroll system (e.g., account numbers, financial codes, date ranges). There are no email, phone, name, address, or other PII values visible in the first 50 rows.

finanzen__LOBU__LOBU_2005__Eval_LOBU_Zynex_2005__Verg.csv
0 rows

File structure

Notes: This is a free-form financial document (Vergütungsauftrag) with no consistent columnar structure. It contains payment instructions and account details but lacks delimited rows/columns. The content appears to be a Swiss corporate payment voucher from Zynex AG, including beneficiary names (Brunner Mark, Leisi Martin, Poulton Dave), bank details, and amounts. While names and bank data are visible, they are embedded in prose rather than structured fields.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__AHVAB.csv
0 rows

File structure

Notes: This is a free-form document (Swiss AHV Lohnbescheinigung forms) with no consistent tabular structure. It contains employee names and AHV insurance numbers, but lacks a consistent delimiter or repeated column structure across rows. The content appears to be Swiss social security documentation with employee names and insurance identifiers embedded in prose lines.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__AbsenzPromea.csv
0 rows

File structure

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

Notes: The provided data appears to be a free-form table with structured headers and numerical values, but no identifiable PII fields such as names, addresses, emails, or phone numbers are present. The data seems to represent absence calculations or payroll records with columns for absence days, amounts, and other numerical values. No columns map to PII fields based on the provided criteria.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Bankenstamm.csv
5 columns3,624 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphigh[0] column header 'BCNr' looks like an internal identifier
1fullNamehigh[1] header 'Name', values are organization names that may contain PII in edge cases per policy
2address1high[2] header 'Zusatz1', values are street addresses
3address2high[3] header 'Zusatz2', values are secondary address lines like 'Postfach' or 'Case postale'
4ziphigh[4] header 'PLZOrt', values are Swiss PLZ (postal code) + Ort (city)

Notes: 50 rows shown, all rows follow consistent CSV structure with 5 columns. Only columns containing address or organization name data are mapped as PII per policy. All bank branches appear to be corporate entities, but organization names are still considered PII when they may contain personal identifiers.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Grunddaten.csv
0 rows

File structure

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

Notes: This file appears to be a header-only or template file with no actual data rows containing PII. The columns represent gender codes (Geschlecht), company divisions (Betriebsteil SUVA), bank types (Bank/Post), salutations (Anreden), and payroll text templates (Texte Lohnabrechnung). None contain personal identifiers like names, addresses, or contact details. All values are generic codes, labels, or static messages rather than individual user data.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Journale.csv
0 rows

File structure

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

Notes: This file appears to be structured corporate/financial data with no personal identifiable information (PII). Columns contain business entities (Firma), addresses (Pfäffikerstrasse 6), employee compensation data (Stundenlohn, Monatslohn), and internal reference numbers (AHV-Nr., Suva-Nr.). No columns map to email, phone, name, DOB, SSN, or other PII fields. All apparent names (Brunner Mark, Leisi Martin, Poulton Dave) are likely employee or business contact references without full personal data. The file represents internal Swiss financial records from Zynex AG with no customer PII exposed in the sample.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnabrechnung_1.csv
0 rows

File structure

Notes: This is an unstructured payroll document in German. It shows employee name (Brunner Mark), address (Pfäffikerstrasse 6, 8604 Volketswil), Swiss social security number (AHV-Abr.Nr.: 222.77.291.219), and salary details for January 2005. No consistent column structure exists across rows — it's a free-form document with mixed headers and data lines. Contains embedded PII but lacks tabular structure.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnabrechnung_2.csv
0 rows

File structure

Notes: This is a free-form text file containing unstructured pay slip data with no consistent columnar structure. While it contains names (Leisi Martin) and addresses (Pfäffikerstrasse 6, Haftlet 18, 4612 Wangen b. Olten), the lack of a consistent delimiter or repeated row pattern across the first 50 rows means it must be treated as unstructured. The presence of embedded personal data like names and addresses triggers the unstructured opt-out rule.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnabrechnung_3.csv
0 rows

File structure

Notes: free-form text with embedded names (Poulton Dave) and addresses (Pfäffikerstrasse 6, Egetswilerstrasse 29, 8604 Volketswil, 8302 Kloten) but no consistent delimiter structure across rows; contains payroll calculation details and bank account fragments. This is unstructured financial document text, not a tabular dataset.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnabrechnung_vorlage.csv
0 rows

File structure

Notes: This is a free-form text file representing a Swiss payroll document (Lohnabrechnung) with no consistent column structure. The data appears to be a formatted report with lines containing labels and values rather than a delimited table. The document includes references to Swiss social security numbers (AHV-Abr.Nr.), personal identification numbers (Personal-Nr.), and payroll calculations, but lacks a consistent column-based structure required for PII mapping. Given the unstructured nature and the presence of payroll data, this should be processed through unstructured text analysis for potential embedded PII.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnausweis_1.csv
0 rows

File structure

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

Notes: This is unstructured data with no consistent column mapping. The file appears to be free-form text containing financial records and internal corporate data from Zynex. There are no clearly identifiable PII fields in the visible sample rows. The values appear to be German financial terminology, years, and codes rather than personal identifiable information. All visible columns contain generic financial/transactional data or internal codes, which per rules must be skipped.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnausweis_2.csv
0 rows

File structure

Notes: This file is a free-form document (appears to be a Swiss labor certificate/Rentenbescheinigung with header rows and blank data rows). It contains no consistent column structure across rows — values are scattered across fields with no repeating pattern. The sample shows German-language document headers like "Lohnausweis" and "Rentenbescheinigung" with no machine-readable data. Though it may contain hidden PII in prose, it lacks a consistent delimiter or column layout, so it must be processed as unstructured text.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnausweis_3.csv
0 rows

File structure

Notes: This is unstructured data from Zynex's internal financial records. The rows show a mix of financial terms, dates, and identifiers without consistent column alignment. The sample contains Swiss social security number format (AHV-Nr.) and year references, but lacks any repeating structured format across rows. No column headers exist to map fields to PII categories.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnausweis_alt_vorlage.csv
0 rows

File structure

Notes: This is a free-form document (Swiss payroll tax form) with no consistent columnar structure. The text appears to be a template or header for tax declaration forms rather than a structured dataset containing actual PII values. No importable columns are present.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnausweis_vorlage.csv
0 rows

File structure

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

Notes: This file appears to be a structured but largely empty or placeholder CSV with German header labels that do not correspond to any PII fields. Columns contain only placeholder values ('#N/A', empty strings) or generic labels ('Lohnausweis', 'Rentenbescheinigung'). No identifiable PII data (email, phone, name, address, DOB, etc.) is present in the first 50 rows. Based on the breach context (Zynex internal financial records), this may be a template or header-only file with no actual data exposed in the sample.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnkonto_1.csv
7 columns50 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamehigh[6] header 'Name, Vorname:' (Name, First Name in German), value 'Brunner Mark' is a full name
10_gendergenderhigh[10] header 'Geschlecht' (gender in German), value 'M' indicates male
6_citycityhigh[6] row contains '8604 Volketswil', Swiss city with postal code
6_addressaddress1high[6] row contains 'Pfäffikerstrasse 6' after name, Swiss street address
6_zipziphigh[6] value '8604' is Swiss postal code
6_dobdobhigh[6] header 'Geburtsdatum:' (birth date in German), value '6/29/77' is date of birth
10_ssnssnhigh[10] header 'AHV-Nr.' (Swiss AHV/social insurance number), value '222.77.291.219' matches AHV format (13-digit Swiss social security number)

Notes: Document is a Swiss payroll record sheet (Lohnkontoblatt) for employee Brunner Mark at Zynex AG. Data is structured but headers span multiple rows and columns contain mixed payroll/administrative data. Only rows with actual employee PII extracted: full name, address, city, postal code, date of birth, AHV number (Swiss social insurance), and gender. Remaining columns contain payroll deductions, monthly allowances, and administrative codes (skipped).

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnkonto_2.csv
3 columns49 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
5fullNamehigh[5] header 'Name, Vorname:', values 'Leisi Martin' clearly full name
6address1high[6] values like 'Haftlet 18', '4612 Wangen b. Olten' match street + city/zip
10genderhigh[10] values 'M' match gender code

Notes: This appears to be Swiss payroll ledger data (Lohnkontoblatt) from Zynex AG. Contains full names, addresses, Swiss AHV numbers (equivalent to SSN), birth dates, and gender. No emails or phone numbers visible in sample.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnkonto_3.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamehigh[6] value 'Poulton Dave' is a person's full name (last, first); column [5] label row confirms 'Name, Vorname:'
10skiphigh[10] value '721.74.460.214' matches Swiss AHV/AVS social security number format; column [9] label row confirms 'AHV-Nr.'

Notes: German-language Swiss payroll sheet (Lohnkontoblatt). Column [5] is a label column with field names (Name/Vorname, Strasse, PLZ/Ort, Geburtsdatum, Geschlecht); column [6] holds corresponding values. DOB ('11/29/74') and address ('Egetswilerstrasse 29', '8302 Kloten') appear as row values within column [6] rather than dedicated columns — they cannot be reliably mapped to fixed column indices in this transposed/label-value layout. Gender 'M' and entry/exit dates appear in column [10] rows alongside the AHV number. Column [14] value '811.755.40X' may be a second AHV/account number but is ambiguous.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Lohnkonto_vorlage.csv
0 rows

File structure

Notes: This is a free-form text document with no consistent columnar structure. The sample shows unstructured financial ledger entries from Zynex AG, including internal accounting codes and accounting period labels, but no identifiable personal data. No consistent delimiter or repeating field pattern exists across rows, and values are entirely business/accounting oriented.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Personaldaten.csv
8 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Bezeichnung', values contain full names like 'Brunner Mark'
3lastNamehigh[3] header 'Name', values are last names: Brunner, Leisi, Poulton
4firstNamehigh[4] header 'Vorname', values are first names: Mark, Martin, Dave
5address1high[5] header 'Strasse', values are street addresses: Pfäffikerstrasse 6, Haftlet 18
6ziphigh[6] header 'PLZ' (Swiss postal code), values are valid Swiss postal codes: 8604, 4612, 8302
7cityhigh[7] header 'Ort', values are Swiss cities: Volketswil, Wangen b. Olten, Kloten
8genderhigh[8] header 'Geschlecht' (gender), values '1' likely coded gender (needs decoding but clearly demographic)
9dobhigh[9] header 'Geburtsdatum' (birth date), values appear to be numeric date codes (likely YYYYMMDD converted)

Notes: 27 total columns; 8 contain PII (names, addresses, zip, city, gender, DOB). Columns 0 (PersonalNr), 2 (Anrede), 10–26 are internal IDs, employment data, or flags — no PII. AHVNr (col 13) is Swiss social security number but formatted with dots; values look like Swiss AHV numbers (e.g., 222.77.291.219) — this SHOULD be mapped as ssn but is omitted due to strict exclusion rules? Correction: AHVNr is Swiss National Insurance number — this IS an ssn equivalent. However, the instructions say: 'ssn, SSN, social_security' map to ssn. AHVNr matches the pattern. It must be included. Adding col 13 as ssn.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Personalstamm.csv
7 columns7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3lastNamehigh[3] column labeled 'Name', values are surnames
4firstNamehigh[4] column labeled 'Vorname', values are given names
5address1high[5] column labeled 'Strasse', values are street addresses
6ziphigh[6] column labeled 'PLZ', values are Swiss postal codes
7cityhigh[7] column labeled 'Ort', values are cities
8genderhigh[8] column labeled 'Geschlecht', values are gender codes
9skiphigh[9] column labeled 'Geburtsdatum', values are dates in MM/DD/YY format

Notes: This is a Swiss corporate personnel file from Zynex AG. Contains employee PII: names, addresses, gender, and date of birth. The file uses Swiss conventions (PLZ for postal code, AHV for Swiss social security number). The AHV number column (labeled 'AHV Nr.') was not mapped because it is a national insurance identifier, not a US SSN, and does not map to any defined PII field in the schema. All other columns are internal employee data (employment dates, bank accounts, vehicle info) and should be skipped.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__RekapMonat.csv
0 rows

File structure

Notes: This is not a structured dataset but rather free-form text lines with no consistent delimiter or column pattern. The sample lines appear to be internal financial records from Zynex AG with German labels, financial codes, and accounting entries. There are no identifiable PII fields in structured columns — values appear to be company addresses, accounting codes, amounts, and internal references. No emails, phone numbers, names, or other PII are visible in the first 50 rows. This qualifies as unstructured text per the rules.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__SuvaAb.csv
0 rows

File structure

Notes: This is not a structured dataset. The sample rows show free-form text with company names, addresses, and financial figures, but no consistent columnar structure. There are no identifiable PII columns to map.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Total.csv
0 rows

File structure

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

Notes: This is a structured financial ledger file from Zynex AG, not a customer PII dataset. Columns contain Swiss accounting codes (Lohnkontoblatt), financial periods, internal reference numbers, and bank details for corporate payroll processing. No personal identifiers (names, emails, SSNs, etc.) are present — all values are business accounting metadata, internal IDs, and financial amounts. The sample values show Swiss franc amounts, account numbers, and corporate addresses (Zynex AG, Pfäffikerstrasse 6, 8604 Volketswil). This is corporate financial data, not customer PII.

finanzen__LOBU__LOBU_2005__LOBU_Zynex_2005__Verg.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__LOBU__LOBU_2006__LOBU_2006__AHVAB.csv
0 rows

File structure

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

Notes: This file is a free-form text file with no consistent columnar structure. It appears to be a Swiss AHV Lohnbescheinigung (wage certificate) document from Zynex AG for the year 2006. The data contains company and document information rather than structured personal records. No PII fields can be mapped due to the unstructured nature of the content. The sample shows document headers, addresses, and totals rather than individual personal data fields.

finanzen__LOBU__LOBU_2006__LOBU_2006__AbsenzPromea.csv
0 rows

File structure

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

Notes: This is a free-form structured table with no identifiable PII fields. It appears to be an absence compensation schedule or policy document from Zynex's internal records, containing only codes, days, and monetary amounts related to employee absence calculations. No names, addresses, emails, or other personal identifiers are present in the visible rows.

finanzen__LOBU__LOBU_2006__LOBU_2006__Bankenstamm.csv
5 columns3,624 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighcolumn 0 is labeled BCNr and appears to be an internal identifier code
1fullNamehighcolumn 1 is labeled Name, contains full corporate names of banks and institutions
2address1highcolumn 2 is labeled Zusatz1, contains street addresses and building numbers
3address2highcolumn 3 is labeled Zusatz2, contains additional address information like Postfach/Postale/Casella postale
4ziphighcolumn 4 is labeled PLZOrt, contains Swiss postal codes (PLZ) followed by city names

Notes: The file contains Swiss bank branch addresses with internal codes. While the data appears to represent corporate entities rather than individuals, the address fields (columns 2-4) contain valid geographic PII that could be used for geolocating institutions. The BCNr column is clearly an internal identifier and has been mapped to skip.

finanzen__LOBU__LOBU_2006__LOBU_2006__Grunddaten.csv
0 rows

File structure

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

Notes: This is a non-PII structured file containing German payroll accounting metadata and templates. Columns include gender codes (M/F), company department codes (Betriebsteil SUVA), address types (Bank/Post), honorifics (Herr/Frau), and payroll text templates. No actual personal data (names, addresses, DOB, etc.) is present in the first 50 rows.

finanzen__LOBU__LOBU_2006__LOBU_2006__Journale.csv
0 rows

File structure

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

Notes: This is not structured PII data. The file appears to be a financial or accounting document from Zynex AG, a Swiss web hosting company. The columns contain company names, addresses, financial figures, and internal reference codes (e.g., AHV-Nr., Druckdatum). There are no identifiable personal fields such as email, phone, DOB, or SSN. The values represent business entities, financial data, and internal tracking numbers rather than individual customer PII. Therefore, no columns map to PII fields.

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnabrechnung_1.csv
0 rows

File structure

Notes: This is a free-form text file containing Swiss payroll records. There is no consistent delimiter structure across lines, and the data appears as human-readable tabular text without a fixed column layout. The content includes personal financial data but lacks a structured columnar format suitable for automated column mapping. The file is a payroll statement showing employee name (Brunner Mark), address (Pfäffikerstrasse 6, 8604 Volketswil), Swiss AHV number (222.77.291.219), and salary details. Because it lacks a consistent delimiter and column structure, it must be processed as unstructured text with embedded PII.

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnabrechnung_2.csv
0 rows

File structure

Notes: This is a free-form text document (Swiss payroll register in German) with no consistent column structure. Contains embedded names (e.g., Leisi Martin) and possibly addresses, but lacks delimited rows/columns. Must be processed by unstructured text extraction pipeline.

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnabrechnung_3.csv
0 rows

File structure

Notes: This is a free-form payroll document (Lohnabrechnung) in German. There is no consistent columnar structure across lines—each line contains a different data fragment. While the document includes a name "Poulton Dave" and an address "Bülacherstrasse 19c" in Embrach, these appear in free-text lines without a fixed positional pattern. The format is unstructured prose, not CSV/TSV, and should be processed through unstructured text extraction.

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnabrechnung_vorlage.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; appears to be Swiss payroll document in German with no importable tabular data

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnausweis_1.csv
0 rows

File structure

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

Notes: This is unstructured data with no consistent column mapping. The file appears to contain free-form German text entries that do not represent a structured tabular format with identifiable PII columns. Columns contain mixed header names and sample values that do not map to any PII fields. No consistent pattern or identifiable personal data fields can be extracted from the provided sample rows.

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnausweis_2.csv
0 rows

File structure

Notes: This file appears to be unstructured data with no consistent column structure. The sample rows contain German financial/HR document fragments like 'Lohnausweis', 'Rentenbescheinigung', and date ranges. While there are some numeric patterns and identifiers (e.g., '591.72.265.213', 'AHV-Nr.'), there is no consistent delimiter or repeating column pattern across the rows. The data appears to be free-form text from Swiss corporate financial records rather than a structured CSV with PII columns.

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnausweis_3.csv
0 rows

File structure

Notes: The provided data is not a structured CSV with consistent columns. Instead, it appears to be a free-form document with headers and values that do not align to a fixed column structure. The values represent titles, codes, and descriptions rather than personal identifiable information in a tabular format. No consistent delimiter or column pattern is observed across the rows. Therefore, it is classified as unstructured text.

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnausweis_alt_vorlage.csv
0 rows

File structure

Notes: This is a Swiss payroll tax document ('Lohnausweis für die Steuererklärung'). The file contains free-form text with no consistent column structure or delimiter. Values include tax reference codes, employment duration markers, and empty placeholders. No PII fields are identifiable in the structured sense; any personal data would appear in free-text blocks not represented as columnar data in this sample.

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnausweis_vorlage.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent columnar structure. The data looks like German-language financial/HR records with entries such as 'AHV-Nr.', 'Lohnausweis', and 'Rentenbescheinigung'. There is no repeating delimiter structure across rows, and the content is prose-like with scattered values rather than tabular data. While some fields like 'AHV-Nr.' (Swiss social security number) could contain PII, the lack of structured columns prevents reliable mapping. This should be processed as unstructured text for PII extraction.

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnkonto_1.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamehigh[6] value 'Brunner Mark' is a person's full name (surname + given name, German order); column [5] label confirms 'Name, Vorname:'
10skipmedium[10] value '222.77.291.219' matches Swiss AHV social insurance number format (dotted segments); column [9] label confirms 'AHV-Nr.'

Notes: This is a German-language Swiss payroll ledger (Lohnkontoblatt) for employee 'Brunner Mark' at Zynex AG. The document is a transposed label-value layout rather than a standard tabular dataset. Column [5] contains field labels (Name, Strasse, Geburtsdatum, etc.) and column [6] contains corresponding values. A DOB value '6/29/77' and gender 'M' appear in column [6] and [10] respectively but at different row positions than the header row — they are not consistently column-mapped PII fields in the traditional sense. The AHV number in column [10] and full name in column [6] are the most reliably column-addressable PII. The file represents a single employee record formatted as a printed payroll sheet rather than a multi-row database export.

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnkonto_2.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamemedium[6] first data row contains 'Leisi Martin' (Swiss LastName FirstName format); subsequent rows contain address and DOB values mixed in same column — name row is identifiable
10skipmedium[10] header row [9] shows 'AHV-Nr.' label (Swiss social insurance number); value '591.72.265.213' matches Swiss AHV-Nr format (###.##.###.###)

Notes: This is a German-language Swiss payroll ledger (Lohnkontoblatt) exported in document/form layout rather than normalized tabular format. Rows interleave field labels and values, so most columns contain mixed data types across rows. Only two columns have consistent enough PII to map: fullName in [6] and AHV-Nr (Swiss SSN equivalent) in [10]. Additional PII (DOB '6/3/72', gender 'M', address 'Haftlet 18 / 4612 Wangen b. Olten') is present in those same columns at different row positions but cannot be independently column-mapped. Column [5] contains field label 'Geburtsdatum:' (DOB label) and [9] contains 'Geschlecht' (gender label) and 'AHV-Nr.' but these are label columns.

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnkonto_3.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamemedium[6] contains 'Poulton Dave' (surname, given name per German 'Name, Vorname' label in col [5]); also contains address and DOB values in other rows — best single-column PII identifier
10skiphigh[10] contains '721.74.460.214' matching Swiss AHV/AVS social security number format; column [9] header 'AHV-Nr.' confirms this

Notes: Highly irregular pivoted/transposed German payroll ledger (Lohnkontoblatt) from Zynex AG. Not a standard row-per-person table — each column contains mixed row types (labels, values, monthly figures). Col [6] also contains address ('Bülacherstrasse 19c'), city/zip ('8424 Embrach'), and DOB ('11/29/74') in different rows but cannot be cleanly separated at column-mapping stage. Col [10] also contains gender ('M') and entry date. Only the most confidently identifiable PII fields mapped.

finanzen__LOBU__LOBU_2006__LOBU_2006__Lohnkonto_vorlage.csv
0 rows

File structure

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

Notes: This file contains only corporate financial accounting data (payroll ledger headers in German). No personal PII fields are present. Columns contain account names, numeric codes, empty placeholders, and month labels — all internal business identifiers and financial aggregates. No emails, names, addresses, or other PII appear in the first 50 rows.

finanzen__LOBU__LOBU_2006__LOBU_2006__Personaldaten.csv
9 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Bezeichnung', values are full names like 'Brunner Mark'
3lastNamehigh[3] header 'Name', values are surnames
4firstNamehigh[4] header 'Vorname', values are given names
5address1high[5] header 'Strasse', values are street addresses
6ziphigh[6] header 'PLZ', values are Swiss postal codes
7cityhigh[7] header 'Ort', values are city names
8genderhigh[8] header 'Geschlecht', values are encoded gender (1 = male)
9dobmedium[9] header 'Geburtsdatum', values are numeric dates (likely YYYYMMDD)
13ssnhigh[13] header 'AHVNr', values match Swiss AHV number format (9 digits with periods)

Notes: 27 columns total, 9 contain PII: fullName, lastName, firstName, address1, zip, city, gender, dob, ssn. All other columns are internal IDs, company codes, financial data, or employment metadata — none are personal identifiers.

finanzen__LOBU__LOBU_2006__LOBU_2006__Personalstamm.csv
7 columns5 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3lastNamehigh[3] column header 'Name', values are common surnames
4firstNamehigh[4] column header 'Vorname', values are common given names
5address1high[5] column header 'Strasse', values are street addresses
6ziphigh[6] column header 'PLZ', values are Swiss postal codes
7cityhigh[7] column header 'Ort', values are city names
8genderhigh[8] column header 'Geschlecht', values are gender codes
9skiphigh[9] column header 'Geburtsdatum', values are dates in MM/DD/YY format

Notes: This is a structured CSV file with personal data from Zynex AG. Columns 0,1,2 are empty or headers; columns 3-9 contain PII fields. Column 10+ contain internal corporate data (AHV number, bank account, etc.) and are skipped per exclusion rules.

finanzen__LOBU__LOBU_2006__LOBU_2006__RekapMonat.csv
0 rows

File structure

Notes: This is unstructured corporate financial data from Zynex AG, not personal customer PII. The file contains internal accounting records with company addresses, invoice numbers, and financial totals. No customer names, emails, or personal identifiers are present in the first 50 rows. This is purely corporate financial documentation.

finanzen__LOBU__LOBU_2006__LOBU_2006__SuvaAb.csv
0 rows

File structure

Notes: This is a free-form document (corporate financial statements from Zynex AG) with no consistent tabular structure. The sample shows unstructured text lines with mixed content (company name, address, financial figures, dates) rather than a delimited CSV/TSV format. Per rules, unstructured files with no consistent column pattern are mapped to empty columns object.

finanzen__LOBU__LOBU_2006__LOBU_2006__Total.csv
0 rows

File structure

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

Notes: This file appears to be structured financial/administrative records from Zynex AG, containing corporate accounting data and internal references. No personal PII fields (names, emails, addresses, etc.) are present in the first 50 rows. All visible columns contain corporate identifiers, financial codes, dates, and accounting values. The data structure is consistent with internal financial statements and billing records, not customer PII.

finanzen__LOBU__LOBU_2006__LOBU_2006__Verg.csv
0 rows

File structure

Notes: This is a free-form financial document (Vergütungsauftrag) with no consistent columnar structure. It appears to be a printed payment order/invoice from Zynex AG showing beneficiary names, addresses, bank details, and amounts. While it contains names and addresses, they are embedded in unstructured prose lines rather than fixed columns. The file shows repeating blocks with beneficiary details but lacks a fixed delimiter or header. Contains PII in free text form, but no structured columns to map.

finanzen__LOBU__LOBU_2007__LOBU_2007__AHVAB.csv
0 rows

File structure

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

Notes: This file appears to be structured Swiss AHV Lohnbescheinigung (Wage Certificate) records with no identifiable PII fields. Columns contain organization names (Zynex AG), addresses (Pfäffikerstrasse 6, 8604 Volketswil), document identifiers (E3454), and financial totals. No personal identifiers such as names, dates of birth, or contact information are present in the first 50 rows. All visible data relates to corporate financial reporting and document pagination.

finanzen__LOBU__LOBU_2007__LOBU_2007__AbsenzPromea.csv
0 rows

File structure

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

Notes: This file is a structured table of Swiss labor compensation absence rules and calculations, not a breach dataset. It contains no personal identifiers or PII fields—only generic absence types (e.g., marriage, death, inspection), days allowed, and monetary amounts. No email, phone, name, address, or other PII columns exist. The first row appears to be a header-like label row, but all subsequent rows are static policy definitions. No actionable PII to map.

finanzen__LOBU__LOBU_2007__LOBU_2007__Bankenstamm.csv
5 columns3,624 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphigh[0] column matches internal IDs pattern 'BCNr' and values are numeric codes
1fullNamehigh[1] header 'Name', values are full institution names (Swiss banks and financial entities)
2address1high[2] header 'Zusatz1', values are street addresses or building names with street numbers
3address2high[3] header 'Zusatz2', values are additional address lines like 'Postfach', 'Case postale', etc.
4ziphigh[4] header 'PLZOrt', values match Swiss postal code + city format (e.g., '8022 Zürich', '3003 Bern')

Notes: 50 rows shown, all rows are structured CSV data. Columns map to Swiss bank branch addresses with postal codes. No personal customer PII present in this sample - only institutional banking data. All rows follow consistent CSV format with 5 columns.

finanzen__LOBU__LOBU_2007__LOBU_2007__Grunddaten.csv
0 rows

File structure

Notes: This file appears to be a free-form text document in German, containing salary accounting templates and header labels rather than structured records. The content shows static text like "Bitte prüfen Sie die Lohnabrechnung auf ihre Richtigkeit." and month names, not actual columnar data with PII. No consistent delimiter or repeating record structure is present across the first 50 rows.

finanzen__LOBU__LOBU_2007__LOBU_2007__Journale.csv
0 rows

File structure

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

Notes: This is not structured PII data; the file appears to be internal financial/business records from Zynex AG (Swiss company). Columns contain company names, addresses, financial figures, and internal identifiers like AHV-Nr. (Swiss social security number) and Druckdatum (print date). However, these are NOT personal customer records: they represent corporate financial line items, payroll data, and internal accounting codes. AHV-Nr. appears to be an internal reference code rather than actual Swiss social security numbers. No email, phone, DOB, or identifiable personal names are present. All columns map to skip categories per rules (company names, internal IDs, financial/timestamps).

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnabrechnung_1.csv
0 rows

File structure

Notes: This is a free-form payroll document with no consistent columnar structure. It contains German payroll calculations and employee information but lacks a defined tabular format. The data appears to be a single record or template rather than a dataset with repeated rows.

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnabrechnung_2.csv
0 rows

File structure

Notes: The provided data is an unstructured Swiss payroll document (Lohnabrechnung) with no consistent columnar structure. It contains free-form text entries, calculations, and financial data. While there are names and addresses present (e.g., 'Leisi Martin', 'Kirchweg 14', '8604 Volketswil'), they are embedded in free-text lines without a fixed tabular format. The breach context indicates this is internal corporate financial data from Zynex AG, and the sample shows no repeated columnar pattern across rows — each line represents a different data element or calculation. Therefore, this qualifies as unstructured text requiring a streaming PII extractor.

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnabrechnung_3.csv
0 rows

File structure

Notes: This is an unstructured payroll document in German. The file contains free-form text with no consistent columnar structure across rows. While there are personal references (names, addresses, employee numbers, and bank account details), the data is presented as a narrative payroll statement rather than a tabular record set. The values appear as prose lines rather than aligned columns, meeting the criteria for unstructured format with embedded PII. The document includes employee name (Poulton Dave), address (Bülacherstrasse 19c, 8424 Embrach), AHV insurance number (721.74.460.214), personal number (3), and bank account (811.755.40X), but these are not in a columnar format.

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnabrechnung_vorlage.csv
0 rows

File structure

Notes: The provided text is a Swiss payroll document in German (Lohnabrechnung) showing employee compensation details, taxes, and deductions. There are no consistent columns or structured data fields — it is a free-form document with financial and tax line items, not containing any identifiable personal information such as names, emails, or addresses. The content is purely transactional (salaries, AHV/ALV/BVG deductions, net pay) with no PII present.

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnausweis_1.csv
0 rows

File structure

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

Notes: This is a non-PII structured file containing corporate financial metadata and internal codes (e.g., AHV-Nr., year markers, document types). No identifiable personal data (email, phone, name, address, DOB, SSN, etc.) is present. Columns contain document types, year markers, internal codes, and generic placeholders. All columns fall under skip rules (company/business references, internal IDs, timestamps, flags).

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnausweis_2.csv
0 rows

File structure

Notes: This is unstructured free-form text. The sample rows contain German-language corporate/financial terms (e.g., 'Lohnausweis', 'Rentenbescheinigung', 'Unentgeltliche Beförderung', 'Kantinenverpflegung') and no consistent column structure. There are no identifiable PII patterns like emails or phone numbers in the visible sample. The data appears to be internal financial records from Zynex, a Swiss web hosting company, with entries like AHV-Nr. (Swiss social security number), years ('2007'), and financial periods ('1/1/07' to '12/31/07'). However, due to the lack of a consistent delimiter and mixed content, this is classified as unstructured text.

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnausweis_3.csv
0 rows

File structure

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

Notes: This is unstructured financial/administrative document data with no consistent PII columns. Columns contain German financial terminology and internal codes (AHV-Nr. = Swiss social security number). No columns clearly map to PII fields per defined rules. All values appear to be internal reference codes, years, document titles, and date ranges rather than personal identifiers.

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnausweis_alt_vorlage.csv
0 rows

File structure

Notes: This is a free-form document titled 'Lohnausweis für die Steuererklärung' (Pay slip for tax declaration). The sample rows contain German-language tax forms with no consistent structured columns or delimiters. Values include location codes ('8604 Volketswil'), date fragments ('1/0/00'), and placeholder text ('#N/A'). There are no identifiable PII columns in the structured sense, only unstructured tax form content.

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnausweis_vorlage.csv
0 rows

File structure

Notes: The provided data is not a structured table with consistent columns and delimiters. It appears to be a free-form text document with fragmented entries that do not conform to a standard CSV or tabular format. There are no identifiable PII fields in the visible sample, and the content seems to be internal corporate notes or labels rather than actual personal or sensitive data records.

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnkonto_1.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamemedium[6] first data value is 'Brunner Mark' (German surname+firstname format); same column also contains address and DOB in other rows — pivoted payroll form, name is the primary PII anchor
10skipmedium[10] header row [9] is 'AHV-Nr.' (Swiss social security number); value '222.77.291.219' matches Swiss AHV number format XXX.XX.XXX.XXX; same column contains gender 'M' and entry date in other rows

Notes: This is a German-language Swiss payroll record (Lohnkontoblatt) for employee Brunner Mark at Zynex AG, Volketswil. The file is a pivoted/transposed payroll form — column [6] holds the employee's personal data values (name, address, DOB) in successive rows rather than a single row per person. Column [10] holds AHV-Nr (Swiss SSN equivalent), gender, and employment dates. Only one employee record is visible in 50 rows. Due to the pivoted structure, a single column contains multiple PII types across rows; standard columnar import will not cleanly separate them. The AHV number '222.77.291.219' is the Swiss equivalent of SSN and is highly sensitive.

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnkonto_2.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamehigh[6] first value 'Leisi Martin' matches Swiss 'Name, Vorname' (Last, First) label in col [5]; subsequent values are street address and city
10skiphigh[10] first value '591.72.265.213' matches Swiss AHV-Nr (social insurance number) format XXX.XX.XXX.XXX, corresponding to 'AHV-Nr.' label in col [9]

Notes: Single-employee Swiss payroll ledger (Lohnkontoblatt) for 'Leisi Martin', Zynex AG, year 2007. Form layout parsed into columns — not a relational table. Col [6] contains name/address/DOB values; col [10] contains AHV number, hire date, gender. DOB '6/3/72' and gender 'M' are present in col [6] and col [10] respectively but mixed with non-PII form values in the same column, making clean extraction unreliable. AHV-Nr is the Swiss equivalent of SSN.

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnkonto_3.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamehigh[6] first value 'Poulton Dave' is a person's full name (surname + given name); column [5] header row contains 'Name, Vorname:' confirming this is the name field
10skiphigh[10] value '721.74.460.214' matches Swiss AHV social insurance number format; column [9] header row contains 'AHV-Nr.' confirming this is the Swiss SSN equivalent

Notes: Swiss payroll account sheet (Lohnkontoblatt) for employee 'Poulton Dave'. Column [5] acts as a label column and column [6] as the corresponding value column. DOB '11/29/74' and address 'Bülacherstrasse 19c, 8424 Embrach' appear as row values within column [6] rather than distinct columns, so they cannot be mapped as separate columns. Gender 'M' appears as a row value within column [10]. AHV-Nr in column [10] is the Swiss equivalent of SSN. This file appears to be a single-employee payroll record formatted as a matrix/form rather than a multi-row dataset.

finanzen__LOBU__LOBU_2007__LOBU_2007__Lohnkonto_vorlage.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger with no identifiable personal information. Columns contain account codes, amounts, dates, and generic financial terms. No PII fields detected.

finanzen__LOBU__LOBU_2007__LOBU_2007__Personaldaten.csv
9 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Bezeichnung' (German for 'Designation'), values like 'Brunner Mark' combine first + last name
3lastNamehigh[3] header 'Name' (German for 'Name'), values are standalone surnames
4firstNamehigh[4] header 'Vorname' (German for 'First name'), values are common given names
5address1high[5] header 'Strasse' (German for 'Street'), values contain street names and house numbers
6ziphigh[6] header 'PLZ' (German postal code abbreviation), values are Swiss 4-digit postal codes
7cityhigh[7] header 'Ort' (German for 'Place/City'), values are valid Swiss municipalities
8genderhigh[8] header 'Geschlecht' (German for 'Sex/Gender'), values '1' likely coded gender
9dobhigh[9] header 'Geburtsdatum' (German for 'Date of birth'), values are numeric but likely YYYYMMDD encoded (28305 = 1928-03-05)
13ssnhigh[13] header 'AHVNr' (Swiss social security number), values match Swiss AHV number format with periods

Notes: 27 total columns, 9 contain PII. Fields 'Heimatort' (place of origin) and 'Eintritt'/'Austritt' (start/end dates) are not classified as PII per definitions. Columns like 'BetriebsteilSUVA' (SUVA insurance branch) and banking/account fields are internal identifiers or financial data, excluded.

finanzen__LOBU__LOBU_2007__LOBU_2007__Personalstamm.csv
7 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4lastNamehigh[4] header 'Name', values are common surnames
5firstNamehigh[5] header 'Vorname', values are common given names
6address1high[6] header 'Strasse', values are street addresses
7ziphigh[7] header 'PLZ', values are 4-digit Swiss postal codes
8cityhigh[8] header 'Ort', values are Swiss municipalities
9genderhigh[9] header 'Geschlecht', values are '1' likely coded gender
10skiphigh[10] header 'Geburtsdatum', value '6/29/77' matches date format

Notes: 11 columns total, 6 contain PII. This is a Swiss employee personal data record from Zynex AG. Columns 0-3 and 11 are empty headers/labels. Columns 12+ contain employment/financial data (AHV number, bank account, vehicle cost) which are NOT mapped as PII per rules.

finanzen__LOBU__LOBU_2007__LOBU_2007__RekapMonat.csv
0 rows

File structure

Notes: This file appears to be unstructured financial/ERP data from Zynex's FaktNT system. The rows contain mixed German financial terminology and Swiss accounting codes with no consistent column alignment or PII fields. Values include Swiss addresses (Pfäffikerstrasse 6, 8604 Volketswil), dates (1/16/08), and numeric amounts (201,600.00 CHF) but no personal identifiers like names, emails, or phone numbers. The format is free-form accounting records, not a delimited CSV with mappable columns.

finanzen__LOBU__LOBU_2007__LOBU_2007__SuvaAb.csv
0 rows

File structure

Notes: This file is free-form text with no consistent column structure. It appears to be a formatted financial statement document from Zynex AG, containing embedded names and addresses but lacking a tabular structure. The data includes company name, address, and what looks like customer names (Brunner Mark, Leisi Martin, Poulton Dave), but these are not in a structured column format.

finanzen__LOBU__LOBU_2007__LOBU_2007__Total.csv
0 rows

File structure

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

Notes: This is a free-form financial document with no consistent column structure or identifiable PII fields. The data appears to be internal accounting records for Zynex AG, containing account numbers, dates, and financial figures but no personal identifiers. All columns contain corporate/financial metadata, timestamps, or internal codes.

finanzen__LOBU__LOBU_2007__LOBU_2007__Verg.csv
0 rows

File structure

Notes: free-form text with embedded addresses and payment instructions, no consistent column structure

finanzen__LOBU__LOBU_2008__LOBU_2008__AHVAB.csv
0 rows

File structure

Notes: This is a free-form text file containing Swiss AHV Lohnbescheinigung (Wage Certificate) records for Zynex AG. The file consists of structured headers and totals interspersed with unstructured text lines like addresses, page numbers, and timestamps. While it contains names (e.g., 'Brunner Mark', 'Leisi Martin', 'Poulton Dave'), these appear in free-form tables without consistent delimiters across lines. The presence of irregular line structures, mixed headers/totals, and embedded text (e.g., 'Zynex AG', 'Pfäffikerstrasse 6', 'Datum:') confirms it does not conform to a uniform CSV/TSV structure. Additionally, visible names and numeric identifiers (e.g., '222.77.291.219') meet the unstructured opt-out criteria: (a) no consistent delimiter, (b) lines vary in shape/length, and (c) contains personal data in prose-like format. Thus, it must be processed as unstructured text for PII extraction.

finanzen__LOBU__LOBU_2008__LOBU_2008__AbsenzPromea.csv
0 rows

File structure

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

Notes: This is a structured CSV file, but all visible columns appear to be internal corporate financial/HR records with no PII fields. Columns include absence calculations, payroll codes, and internal reference numbers. No names, emails, addresses, or other PII are present in the first 50 rows.

finanzen__LOBU__LOBU_2008__LOBU_2008__Bankenstamm.csv
5 columns3,624 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighcolumn 'BCNr' is an internal identifier (numeric code)
1fullNamehighcolumn 'Name' contains full legal entity names, not individual PII
2address1highcolumn 'Zusatz1' contains street addresses like 'Börsenstrasse 15', 'Rue Diday 8', etc.
3address2highcolumn 'Zusatz2' contains secondary address information like 'Postfach 2800', 'Case postale', etc.
4ziphighcolumn 'PLZOrt' contains Swiss postal codes and city names like '8022 Zürich', '3003 Bern', etc.

Notes: 50 rows shown, representing Swiss bank branch addresses. Contains corporate entity names and physical addresses, not individual PII. All columns mapped appropriately with no personal identifiers present.

finanzen__LOBU__LOBU_2008__LOBU_2008__Grunddaten.csv
0 rows

File structure

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

Notes: This file appears to be a German-language template or description file for payroll processing, not actual records containing personal identifiable information. The columns represent gender codes (Geschlecht), operating units (Betriebsteil SUVA), bank/payment methods (Bank/Post), salutations (Anreden), and payroll text templates (Texte Lohnabrechnung). No actual PII fields like names, addresses, or dates are present in the sample data.

finanzen__LOBU__LOBU_2008__LOBU_2008__Journale.csv
0 rows

File structure

Notes: This is an unstructured financial report/document. The data appears to be a mix of text and numeric values with no consistent column structure across rows. Headers like 'Firma', 'Jahr', 'AHV-Nr.', and 'Druckdatum' are present in some rows but not others. The values include company names, addresses, numerical data, and dates, but they do not form a consistent tabular structure that can be mapped to PII fields. Given the unstructured nature and the presence of corporate/financial data rather than personal PII, no column mappings are possible.

finanzen__LOBU__LOBU_2008__LOBU_2008__Lohnabrechnung_1.csv
0 rows

File structure

Notes: The provided sample is a free-form text representation of a Swiss payroll document (Lohnabrechnung) for an employee at Zynex AG. The text contains structured data fields such as name, address, dates, and financial amounts, but it lacks a consistent delimiter and column structure across lines. It is formatted as a series of key-value pairs and tabular sections rather than a CSV with repeating rows. Because the data is unstructured and does not have consistent columns, it falls under the unstructured opt-out rule. However, it does not contain visible emails or phone numbers in the sample, so no extraction is needed.

finanzen__LOBU__LOBU_2008__LOBU_2008__Lohnabrechnung_2.csv
0 rows

File structure

Notes: free-form text with embedded names and addresses, no consistent delimiter structure. Contains PII like 'Leisi Martin' and 'Austrasse 43', but lacks row structure for column mapping.

finanzen__LOBU__LOBU_2008__LOBU_2008__Lohnabrechnung_3.csv
0 rows

File structure

Notes: This is a free-form text file containing Swiss payroll data for Zynex AG. The data appears to be structured as a multi-line report with no consistent delimiter or column pattern across rows. It contains employee name "Poulton Dave" and address "Bülacherstrasse 19c, 8424 Embrach" but lacks any CSV-like structure. Due to the unstructured format and prose-style presentation, it should be processed as unstructured text with embedded PII extraction.

finanzen__LOBU__LOBU_2008__LOBU_2008__Lohnabrechnung_vorlage.csv
0 rows

File structure

Notes: This is a free-form text document representing a Swiss payroll slip (Lohnabrechnung) from Zynex AG. The data contains no consistent columnar structure — it's a mixture of German text lines, numeric values, and payment details in an unstructured format. Though it contains monetary amounts and dates, it lacks identifiable PII fields such as names, emails, or addresses. The document appears to be an internal corporate financial record without customer or employee personal identifiers.

finanzen__LOBU__LOBU_2008__LOBU_2008__Lohnausweis_1.csv
0 rows

File structure

Notes: This is a free-form unstructured document containing no consistent column structure or delimiter. The sample shows fragmented German financial/HR text lines with no repeating format, and no embedded emails or phones. This is typical of internal corporate records (pay slips, assembly minutes) where data is presented in narrative tables rather than structured CSV. No PII columns can be mapped.

finanzen__LOBU__LOBU_2008__LOBU_2008__Lohnausweis_2.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__LOBU__LOBU_2008__LOBU_2008__Lohnausweis_3.csv
0 rows

File structure

Notes: This is an unstructured document (prose) containing German financial/administrative terms and no consistent column structure. It does not contain importable tabular data with PII fields. The sample shows free-form text lines with no consistent delimiter or repeating columns across rows.

finanzen__LOBU__LOBU_2008__LOBU_2008__Lohnausweis_vorlage.csv
0 rows

File structure

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

Notes: This appears to be a German-language financial/administrative document header row (Zynex internal data). The visible values ('Lohnausweis', 'Rentenbescheinigung', 'AHV-Nr.', 'von', 'bis') indicate Swiss payroll/benefit records and year references, but NO PII fields are present in the first 50 rows. All columns contain either placeholder values ('#N/A') or generic financial/administrative labels. No emails, names, addresses, DOB, SSN, or phone numbers are visible. Therefore, no PII columns can be mapped.

finanzen__LOBU__LOBU_2008__LOBU_2008__Lohnkonto_1.csv
1 column0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamemedium[6] first value is 'Brunner Mark' — a full name (surname + given name); subsequent rows contain address/DOB mixed in same column but name is the primary PII identifier here

Notes: This is a serialized Swiss payroll form (Lohnkontoblatt) for a single employee, rendered as a delimited grid rather than a proper multi-record table. Column [6] contains the employee full name 'Brunner Mark' in row 0, but subsequent rows in the same column contain street address, city, occupation, and DOB — making clean field mapping impossible for most PII. Column [10] contains what appears to be an AHV number (Swiss social security: '222.77.291.219') alongside gender 'M' and dates, but mixed across rows. The file is not suitable for bulk PII extraction via column mapping. Only the full name in column [6] is mapped with confidence.

finanzen__LOBU__LOBU_2008__LOBU_2008__Lohnkonto_2.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamemedium[6] first data value is 'Leisi Martin' (Swiss LastName FirstName format); column [5] label row contains 'Name, Vorname:' confirming this is the name field
10skipmedium[10] header row [9] contains 'AHV-Nr.' (Swiss social security number); value '591.72.265.213' matches Swiss AHV number format XXX.XX.XXX.XXX

Notes: German-language Swiss payroll ledger (Lohnkontoblatt) for Zynex AG employee 'Leisi Martin'. Document is semi-structured with label rows interleaved with value rows rather than a clean tabular layout. Column [6] contains name/address/DOB values across different rows but only the fullName is consistently identifiable at the column level. Column [10] contains AHV-Nr (Swiss SSN equivalent) and gender ('M') across rows. DOB '6/3/72' and gender 'M' appear as row values within columns [6] and [10] respectively but cannot be reliably split from the mixed-row structure. Single employee record visible in the 50-row sample.

finanzen__LOBU__LOBU_2008__LOBU_2008__Lohnkonto_3.csv
0 rows

File structure

Notes: This is an unstructured file containing internal financial records from Zynex. The data appears to be formatted as a series of account statements or payroll sheets with no consistent columnar structure across rows. The content includes Swiss company names, addresses, and financial figures, but lacks any identifiable personal PII fields like names, emails, or phone numbers in a structured format. While there are some potentially sensitive identifiers (e.g., AHV-Nr. which is a Swiss social security number), they appear mixed within free-form text lines rather than as discrete columns. According to the unstructured opt-out rules, files with no consistent delimiter and varying line shapes containing embedded PII should be processed as unstructured text.

finanzen__LOBU__LOBU_2008__LOBU_2008__Lohnkonto_vorlage.csv
0 rows

File structure

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

Notes: This is a financial ledger file (Lohnkontoblatt = payroll sheet) from Zynex AG. The columns contain accounting codes, financial figures, and internal identifiers. No PII fields are present — names appear only as placeholders ('Name, Vorname:' header with no actual values in sample). Columns like 'AHV-Nr.' (Swiss social security number) and 'Kinderanzahl:' (child count) are headers for financial calculations, not actual PII. All columns map to internal accounting or skip categories per exclusion rules.

finanzen__LOBU__LOBU_2008__LOBU_2008__Personaldaten.csv
9 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Bezeichnung', values are full names like 'Brunner Mark'
3lastNamehigh[3] header 'Name', values are last names
4firstNamehigh[4] header 'Vorname', values are first names
5address1high[5] header 'Strasse', values are street addresses
6ziphigh[6] header 'PLZ', values are Swiss postal codes (4-digit)
7cityhigh[7] header 'Ort', values are Swiss cities
8genderhigh[8] header 'Geschlecht', values are encoded gender (1 for male, likely)
9dobhigh[9] header 'Geburtsdatum', values appear to be encoded dates (e.g., 28305 = 1980-03-05)
13ssnhigh[13] header 'AHVNr', values match Swiss AHV number format (9 digits with periods)

Notes: 27 columns total, 8 contain PII. 'PersonalNr' is an internal employee ID (skip). 'Heimatort' is a secondary city of origin (not primary residence). 'BetriebsteilSUVA', 'BankPost', 'Bankverbindung', 'Kontonummer', 'FahrzG', 'FahrzKaufpreis', 'FahrzEigenverbrauch', 'ArbeitswegVerbilligung', 'MahlzeitEntschaedigung', and 'MahlzeitVerbilligung' are internal financial/workplace codes (skip).

finanzen__LOBU__LOBU_2008__LOBU_2008__Personalstamm.csv
8 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4lastNamehigh[4] column labeled 'Name', values are surnames
5firstNamehigh[5] column labeled 'Vorname', values are given names
6address1high[6] column labeled 'Strasse', values are street addresses
7ziphigh[7] column labeled 'PLZ', values are postal codes
8cityhigh[8] column labeled 'Ort', values are cities
9genderhigh[9] column labeled 'Geschlecht', values indicate gender
10skiphigh[10] column labeled 'Geburtsdatum', values match date format
13skiphigh[13] column labeled 'AHV Nr.', values match Swiss AHV number pattern

Notes: This is a Swiss employee personnel file from Zynex AG. Contains personal data including full names, addresses, gender, date of birth, and Swiss social security numbers (AHV). No email or phone numbers present in this sample.

finanzen__LOBU__LOBU_2008__LOBU_2008__RekapMonat.csv
0 rows

File structure

Notes: The provided data appears to be unstructured financial/ERP records from Zynex AG in German. The lines contain fragments of Swiss addresses (Pfäffikerstrasse 6, 8604 Volketswil), financial codes (AHV-Abr.Nr., Suva-Abr.Nr.), amounts (224,200.00), and internal accounting terms (Buchungsbeleg, Soll, Haben). There is no consistent column structure across rows — each line has a different pattern and purpose. While there are Swiss addresses present, they appear as free-form text fragments rather than tabular columns. The data represents internal corporate financial records rather than customer PII, and contains no identifiable personal email/phone fields. Per rules, this qualifies as unstructured text with no column mapping.

finanzen__LOBU__LOBU_2008__LOBU_2008__SuvaAb.csv
1 column9 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name / Vorname', values are full names like 'Brunner Mark'

Notes: This appears to be Swiss payroll/accounting records (UVG-Jahresabrechnung = annual social insurance statement). Column 1 contains full names (first+last), other columns are financial codes, dates, and amounts. No email/phone/DOB/SSN found in sample.

finanzen__LOBU__LOBU_2008__LOBU_2008__Total.csv
0 rows

File structure

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

Notes: The file appears to be unstructured financial records with no consistent PII fields. Columns contain corporate financial data (company names, addresses, account numbers, dates) and internal codes. No identifiable personal data (names, emails, phones, etc.) is present in the first 50 rows. All values are corporate/financial identifiers, timestamps, or internal codes. No PII columns detected.

finanzen__LOBU__LOBU_2008__LOBU_2008__Verg.csv
0 rows

File structure

Notes: This is a free-form financial document with no consistent column structure. It contains payment orders and account details but lacks repeating headers or delimiters. Contains embedded personal names and Swiss bank account numbers, but no structured PII fields to map.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__AHVAB.csv
0 rows

File structure

Notes: This is a free-form document (Swiss AHV Lohnbescheinigung forms) with no consistent columnar structure. The data appears to be Swiss employment/labor records with lines containing addresses, dates, and financial amounts but no identifiable personal identifiers in structured columns. No CSV-like delimiter pattern is present across rows.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__AbsenzPromea.csv
0 rows

File structure

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

Notes: The file is a Swiss corporate absence compensation record template with no personal identifiers. Columns contain generic absence categories, numeric counters, and financial placeholders. No PII fields (email, phone, name, address, etc.) are present. Values are zeros, labels, or formula errors (#REF!).

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Bankenstamm.csv
4 columns3,624 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name', values are institutional names matching Swiss bank branches
2address1high[2] header 'Zusatz1', contains street names and building numbers
3address2high[3] header 'Zusatz2', contains secondary address elements like 'Postfach' and 'Case postale'
4ziphigh[4] header 'PLZOrt', contains Swiss postal codes followed by city names

Notes: 50 rows shown; data represents Swiss bank branch addresses from UBS and related institutions. All rows follow consistent CSV format with four columns. No personal customer PII present — only institutional banking locations.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Grunddaten.csv
0 rows

File structure

Notes: free-form text with no consistent column structure — appears to be German-language payroll template or header definitions, not actual tabular data with PII fields

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Journale.csv
0 rows

File structure

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

Notes: This is an unstructured corporate financial record file with no personal identifiable information (PII). Columns appear to contain Swiss company names, financial figures, and internal codes rather than personal data. Columns 0-15 contain corporate entities (Firma), locations (Jahr), numeric codes, financial amounts, and internal reference dates - none map to PII fields per the exclusion rules. No email, phone, name, address, or other PII fields are present.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnabrechnung_1.csv
0 rows

File structure

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

Notes: This file is a Swiss payroll document (Lohnabrechnung) showing salary calculations and tax withholdings. It contains no PII fields - only employee name (Brunner Mark), address (Pfäffikerstrasse 6, 8604 Volketswil), and AHV social security number (222.77.291.219). However, these are NOT mapped as PII because: 1) The file format is unstructured payroll data without consistent columnar mapping across rows 2) Values appear in free-form positions rather than fixed columns 3) The document is clearly an internal corporate payroll statement, not customer data Per instructions, unstructured files with no consistent column structure return empty columns object {}

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnabrechnung_2.csv
3 columns31 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
5fullNamehigh[5] contains 'Leisi Martin' which is a full name
6address1high[6] contains 'Kirchweg 14' which is a street address
12cityhigh[12] contains '8604 Volketswil' which is a Swiss postal code and city

Notes: This is a Swiss payroll document (Lohnabrechnung) with personal employee data. Columns 5-6 contain full name and address. Column 12 contains city and postal code. All other columns are payroll calculations, internal IDs, or financial data not classified as PII under the rules.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnabrechnung_3.csv
0 rows

File structure

Notes: The provided data is an unstructured free-form text file containing a Swiss payroll slip (Lohnabrechnung) in German. It lacks consistent columnar structure across rows—each line represents a different part of the document (header, employee details, payroll calculations, totals, etc.). The format is not CSV or any delimited format; it's a free-form document. While it contains personal identifiers (e.g., 'Poulton Dave', 'Bülacherstrasse 19c', '8424 Embrach', '811.755.40X'), these are embedded within unstructured text rather than in a columnar format. The conditions for unstructured detection are met: (a) no consistent delimiter, (b) wildly varying line shapes, (c) visible PII. Therefore, it should be processed as unstructured with streaming PII extraction.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnabrechnung_vorlage.csv
0 rows

File structure

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

Notes: This is a structured payroll document (Lohnabrechnung) in German showing salary calculations and tax deductions for a Swiss employee. No personal identifiers (names, emails, addresses, etc.) appear in the visible rows. All columns represent internal accounting codes, amounts, and metadata — none map to PII fields. The document includes AHV insurance numbers and personal reference numbers that are internal identifiers (not public PII). Per exclusion rules, company/internal IDs and financial/timestamp columns are skipped.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnausweis_1.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnausweis_2.csv
0 rows

File structure

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

Notes: This appears to be an unstructured financial document or report from Zynex's internal records. The data contains German financial terminology (e.g., "Lohnausweis" = payroll certificate, "Rentenbescheinigung" = pension certificate) and Swiss identifiers (AHV-Nr. = Swiss social security number). The columns contain headers in German and values that are mostly labels or financial descriptors rather than personal data. No clear PII fields (email, phone, name, address, etc.) are present in the visible sample rows. Given the context of a corporate financial breach, this file likely contains aggregated financial data rather than individual customer PII. All columns map to skip due to non-PII content.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnausweis_3.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent delimiter. Sample shows mixed German phrases like 'Lohnausweis' and 'Rentenbescheinigung' alongside numeric codes and fragmented values. No row structure exists across the sample rows, and the content appears to be internal corporate notes or document headers rather than tabular PII records.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnausweis_alt_vorlage.csv
0 rows

File structure

Notes: This is an unstructured document (Swiss tax form template 'Lohnausweis für die Steuererklärung'). No consistent columnar structure exists; fields appear to be free-form text labels and placeholders rather than actual data rows. No PII columns can be mapped.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnausweis_vorlage.csv
0 rows

File structure

Notes: This file is a header-only or label file with no consistent data rows. The entries appear to be German-language labels or placeholders rather than actual data records. No PII can be mapped from this structure.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnkonto_1.csv
1 column0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamemedium[6] first value 'Brunner Mark' is a person's full name (surname + given name, German order)

Notes: This is a flattened German payroll form (Lohnkontoblatt) for employee 'Brunner Mark' at Zynex AG. The layout is a transposed HR form, not a proper tabular dataset — column semantics change by row (labels vs values mixed together). Only column 6 has a reliably mapped PII field (fullName). Other apparent PII (DOB '6/29/77' in row 5 of col 6, AHV number '222.77.291.219' in col 10, gender 'M' in col 10) cannot be safely column-mapped because the columns do not represent consistent fields across all rows. Single-employee record; bulk extraction not applicable.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnkonto_2.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamehigh[6] header value 'Leisi Martin' is a person name (Last First format per German 'Name, Vorname:' label in col [5]); subsequent rows contain street address and city confirming this is the employee data column
10skiphigh[10] header value '591.72.265.213' matches Swiss AHV-Nr. (social security/AVS number) format; column [9] label row confirms 'AHV-Nr.' header

Notes: German-language payroll sheet (Lohnkontoblatt) for Zynex AG employee. Transposed layout: col [5] and [9] are label columns, col [6] and [10] are corresponding value columns. Col [6] contains fullName, street address, city, DOB and col [10] contains AHV-Nr (SSN), hire date, gender — all mixed into different rows of the same column. Only fullName and SSN are mappable as distinct importable PII fields from the column structure; DOB and gender appear as row values within col [6] and [10] respectively but cannot be cleanly separated at the column-mapping level. Bank account number (Kontonummer) in col [14] is financial data with no standard PII field mapping.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnkonto_3.csv
2 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
6fullNamemedium[6] first value is 'Poulton Dave' — a personal name (surname, given name format); column also contains address and DOB in subsequent rows but name is the primary lead value
10skipmedium[10] first value '721.74.460.214' matches Swiss AHV-Nr (social security number) format; column [9] label confirms 'AHV-Nr.'

Notes: This is a German-language Swiss payroll form ('Lohnkontoblatt') rendered as delimited text — a transposed/form-style layout for a single employee (Poulton Dave). PII is spread across row positions within columns rather than uniform column-per-field structure. Column [6] row 0 = full name, row 1 = street address, row 2 = PLZ+city, row 4 = DOB (11/29/74). Column [10] row 0 = AHV-Nr (Swiss SSN), row 3 = gender (M). Column-level mapping is approximate due to the form layout.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Lohnkonto_vorlage.csv
0 rows

File structure

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

Notes: This appears to be a Swiss payroll ledger ("Lohnkontoblatt") with financial/accounting data. Columns contain internal accounting codes, financial figures, and internal identifiers. No personal PII fields (names, emails, addresses, etc.) are present. All columns map to internal financial or corporate data and should be skipped.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Personaldaten.csv
9 columns3 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Bezeichnung', values are full names (e.g. 'Brunner Mark')
3lastNamehigh[3] header 'Name', values are last names (e.g. 'Brunner')
4firstNamehigh[4] header 'Vorname', values are first names (e.g. 'Mark')
5address1high[5] header 'Strasse', values are street addresses (e.g. 'Pfäffikerstrasse 6')
6ziphigh[6] header 'PLZ', values are Swiss postal codes (e.g. '8604')
7cityhigh[7] header 'Ort', values are cities (e.g. 'Volketswil')
8genderhigh[8] header 'Geschlecht', values are encoded gender (e.g. '1' likely maps to male/female)
9dobhigh[9] header 'Geburtsdatum', values are encoded dates (likely YYYYMMDD format)
13ssnhigh[13] header 'AHVNr', values match Swiss AHV number format (e.g. '222.77.291.219')

Notes: 27 total columns, 9 contain PII. Columns 'PersonalNr', 'Anrede', 'Heimatort', 'Kinderzahl', 'Kindernamen', 'Beruf', 'Eintritt', 'Austritt', 'BetriebsteilSUVA', 'BankPost', 'Bankverbindung', 'Kontonummer', 'FahrzG', 'FahrzKaufpreis', 'FahrzEigenverbrauch', 'ArbeitswegVerbilligung', 'MahlzeitEntschaedigung', 'MahlzeitVerbilligung' are internal IDs, employment metadata, or financial flags — mapped to skip per exclusion rules.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Personalstamm.csv
7 columns7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
3firstNamehigh[3] header 'Vorname', values are common given names
4lastNamehigh[4] header 'Name', values are common surnames
5address1high[5] header 'Strasse', values are street addresses
6ziphigh[6] header 'PLZ', values are Swiss postal codes
7cityhigh[7] header 'Ort', values are city names
8genderhigh[8] header 'Geschlecht', values indicate gender
9skiphigh[9] header 'Geburtsdatum', values are dates in MM/DD/YY format

Notes: This is a structured CSV file with employee personal data from Zynex AG. Columns 3-9 contain PII fields including first name, last name, address, zip, city, gender, and date of birth. Other columns contain internal identifiers, employment details, and financial information which are skipped per rules.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__RekapMonat.csv
0 rows

File structure

Notes: This is internal corporate accounting data from Zynex AG (Swiss web hosting/CMS company) spanning 2001–2020. The file contains free-form German financial records (payroll, invoicing, etc.) with no consistent columnar structure. No PII fields (names, emails, etc.) are present in a repeatable format — values are addresses ('Pfäffikerstrasse 6'), dates ('11/19/07'), amounts ('17,950.00'), and Swiss social insurance numbers ('E3454', '234773'). These are not mappable to any PII field in our taxonomy because they appear as isolated lines, not as columns. Therefore, we classify this as unstructured text with embedded data and return an empty columns object.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__SuvaAb.csv
3 columns15 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Name / Vorname', values contain full names like 'Peter Brunner'
11fullNamehigh[11] contains full names like 'Peter Brunner Treuandbüro'
21fullNamehigh[21] contains full names like 'Peter Brunner Treuandbüro'

Notes: This file appears to be Swiss labor/UVG (social security) accounting records from Zynex AG, not customer PII. Contains employee names and corporate address, but no emails, phones, DOB, SSN, or other direct PII fields. All PII present is limited to full names and corporate address, which is excluded by rules. Only mapped fullName fields where values clearly show names.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Total.csv
0 rows

File structure

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

Notes: This appears to be a financial template or internal corporate form (Lohnkontoblatt = payroll sheet) with no actual PII present in the first 50 rows. All columns contain template instructions, company names, financial terms, and placeholder values. No emails, phone numbers, names, addresses, or other PII fields are visible. Columns 0-18 are all non-PII per exclusion rules (company names, internal IDs, financial codes, timestamps). No mapping required.

finanzen__LOBU__LOBU_2008__LOBU_2008_evaluation__Verg.csv
0 rows

File structure

Notes: The provided data is a free-form financial document with no consistent column structure. It contains payment instructions and bank account details but lacks a fixed tabular format with repeating columns. The data appears to be a Swiss corporate payment order from Zynex AG, including beneficiary names, addresses, bank details, and amounts, but does not present a structured dataset with identifiable column mappings to PII fields. Per the unstructured opt-out rules, no column mapping is performed.

finanzen__LOBU__LOBU_2008__Lohnkalkulation_2008__Fhz_02.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains financial data rows with no identifiable PII columns

finanzen__LOBU__LOBU_2008__Lohnkalkulation_2008__Fhz_03.csv
0 rows

File structure

Notes: This is a free-form financial report table with no identifiable personal data. The structure shows vehicle cost breakdowns (fuel, insurance, maintenance, leasing) for 2003 with no personal identifiers. No consistent column headers or PII fields present.

finanzen__LOBU__LOBU_2008__Lohnkalkulation_2008__Fhz_04.csv
0 rows

File structure

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

Notes: This is a financial summary table for vehicles (Fahrzeuge) in 2004, showing cost categories like fuel, insurance, repairs, and leasing. No PII fields are present — all columns represent aggregated monetary values (in Swiss Francs CHF) and vehicle cost categories. The data is purely corporate financial reporting with no personal customer or employee details.

finanzen__LOBU__LOBU_2008__Lohnkalkulation_2008__Fhz_05.csv
0 rows

File structure

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

Notes: This is a financial report table with vehicle cost breakdown (fuel, insurance, repairs, leasing, etc.). No PII fields present. Columns contain numeric financial data and descriptive labels, all marked for skip per exclusion rules.

finanzen__LOBU__LOBU_2008__Lohnkalkulation_2008__Fhz_06.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's a financial table in German with vehicle costs and totals. No personal identifiers present. Columns represent categories like fuel, insurance, repairs, and leasing costs for different vehicle types (MB, ML, DP), not personal fields. All values are numeric monetary amounts in CHF.

finanzen__LOBU__LOBU_2008__Lohnkalkulation_2008__Fhz_07.csv
0 rows

File structure

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

Notes: This is a financial record table showing vehicle expenses and costs for different models (MB, ML, DP). The data contains only numerical values and financial categories (fuel, insurance, repairs, leasing, etc.). There are no personal identifiers, PII fields, or structured personal data present. All columns represent internal business financial metrics and vehicle maintenance costs, which should be skipped per the exclusion rules for company/business-related data and financial/transactional information.

finanzen__LOBU__LOBU_2008__Lohnkalkulation_2008__Fhz_08.csv
0 rows

File structure

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

Notes: This file contains vehicle-related financial data (fuel, insurance, maintenance, leasing) with no personal identifiable information. All columns appear to be internal business records for vehicles ('Fahrzeuge') with numeric financial values and vehicle identifiers (MB, ML, DP). No PII fields detected.

finanzen__LOBU__LOBU_2008__Lohnkalkulation_2008__Uebersicht.csv
0 rows

File structure

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

Notes: This is a financial data file containing salary and vehicle-related figures for different individuals (MB, ML, DP) over years. There are no PII fields present in the provided columns. All columns appear to contain numerical financial data, years, and labels rather than personal identifiable information such as names, addresses, emails, etc.

finanzen__LOBU__LOBU_2016__prod_arbeitsstunden__Tabelle1.csv
0 rows

File structure

Notes: This is unstructured financial data with no identifiable PII columns. The file appears to be a raw financial ledger or accounting snapshot containing only numeric values, with no column headers or textual identifiers. Given the context of the breach (Zynex financial records), this likely represents internal financial records such as subscription billing amounts, invoice totals, or financial statement figures — not customer PII. No emails, names, addresses, or other PII fields are present in the sample rows.

finanzen__LOBU__LOBU_2022__arbeitszeiten_kw__Tabelle1.csv
0 rows

File structure

Notes: This is a financial ledger file with no identifiable personal information. The data appears to be structured financial records showing months, budget percentages, and financial figures, but contains no names, addresses, emails, or other PII fields. The format does not contain any column headers or consistent structure that would map to personal data fields.

finanzen__LOBU__LOBU_2022__eo-katrin-ramon__clickup_zeitabrechnung_kwellinger_20230209__Auswertung.csv
0 rows

File structure

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

Notes: All columns are internal financial/tracking fields: TaskCustomId (internal task ID), TaskName (task description), Datum (ISO timestamp), Jahr (year), Monat (month), Dauer (duration in days), Betrag (amount in CHF), Fixpreis (fixed-price flag), Abger. (commit flag), and two numeric columns without headers. No PII present.

finanzen__LOBU__LOBU_2022__eo-katrin-ramon__clickup_zeitabrechnung_kwellinger_20230209__Export_SQL.csv
0 rows

File structure

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

Notes: No PII columns identified. All columns appear to be internal task IDs, descriptions, timestamps, durations, amounts, and flags. Columns like TaskCustomId (VXFKSH-...), Start (timestamps), Duration (numeric values), Betrag (amounts in CHF), Description (project notes), FixpreisOfferte (fixed-price flag), and various Verrechnet fields (NULL values) are all internal operational/tracking data. No personal identifiers (names, emails, addresses, etc.) are present.

finanzen__LOBU__LOBU_2022__eo-katrin-ramon__clickup_zeitabrechnung_kwellinger_20230209__SQL_Abfrage.csv
0 rows

File structure

Notes: This is a SQL query snippet, not actual data rows. It contains no PII fields or structured records — only database column aliases and calculation logic. The breach context describes financial records, but this file is purely SQL code, so no columns to map.

finanzen__LOBU__LOBU_2022__eo-katrin-ramon__clickup_zeitabrechnung_kwellinger_20230209__Zusammenzug.csv
0 rows

File structure

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

Notes: No PII columns identified. All fields are task identifiers, descriptions, timestamps, durations, monetary values, and approval flags. No personal or sensitive data present in the sample.

finanzen__LOBU__LOBU_2022__katrin-mutterschaft__2022-03_Wellinger_K_Ferien__Tabelle1.csv
0 rows

File structure

Notes: free-form text with embedded names and dates; no consistent delimiter or row structure across lines

finanzen__LOBU__LOBU_2022__time_entires_kw__2021.csv
0 rows

File structure

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

Notes: No PII columns detected. The file contains only task identifiers, names, timestamps, durations, and descriptions related to CMS/website development tasks. No personal information such as emails, phone numbers, names, addresses, or other PII fields are present in the first 50 rows.

finanzen__LOBU__LOBU_2022__time_entires_kw__2022.csv
0 rows

File structure

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

Notes: This file contains only task identifiers, names, timestamps, and durations. No PII fields (email, phone, DOB, name, address, SSN, password, username) are present. All columns are task management metadata and should be skipped.

finanzen__LOBU__LOBU_2022__time_entires_kw__alle.csv
0 rows

File structure

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

Notes: No PII fields detected. File contains only task IDs, names, timestamps, durations, and descriptions related to CMS development and web project management. All columns map to internal project tracking data and are non-personal.

finanzen__LOBU__LOBU_2023__sva-loehne__2023.csv
0 rows

File structure

Notes: This file is a financial summary in tabular format but contains no personal identifiable information (PII). It shows monthly financial figures, totals, and Swiss social security contributions (AHV, ALV, FAK, VwKosten) for what appears to be payroll or corporate financial planning. No names, addresses, emails, phone numbers, or other PII fields are present. The data is purely numerical and fiscal.

finanzen__LOBU__LOBU_2024__loehne-sva-2024__Tabelle1.csv
0 rows

File structure

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

Notes: This is a financial statement file with columns representing employee initials (MB, ML, DR, PW), monetary values (lohn/salary, bonus), and aggregated totals. No PII fields present — all columns are internal financial metrics or generic codes. The file appears to be a payroll or financial summary report from Zynex's internal systems, not customer PII data.

finanzen__LOBU__LOBU_2025__zynex-loehne-202511__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers, no consistent column structure or header lines

finanzen__LOBU__LOBU_2025__zynex-loehne-202512__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers (Swiss bank accounts). No consistent delimiter or structured columns present across the sample lines; appears to be a list of IBAN values only

finanzen__LOBU__LOBU_2026__zynex-loehne-202601__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not email/phone). No consistent delimiter or row structure visible in the sample. This appears to be a list of Swiss bank account numbers (IBANs) rather than a CSV with PII columns. The data is unstructured and lacks any columnar format.

finanzen__LOBU__LOBU_2026__zynex-loehne-202602__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not emails/phones). No consistent delimiter or row structure visible in the sample. This is unstructured financial data (bank accounts) rather than personal PII records.

finanzen__LOBU__LOBU_2026__zynex-loehne-202603__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (Swiss bank account numbers), no consistent delimiter or header structure present

finanzen__LOBU__LOBU_2026__zynex-loehne-202604__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers, no consistent column structure

finanzen__LOBU__LOBU_2026__zynex-loehne-202605__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not emails/phones), no consistent delimiter or row structure — this is a raw list of Swiss bank account numbers in a text file

finanzen__LOBU__LOBU_Mahler__LOBU_2004__AHVAB.csv
0 rows

File structure

Notes: The provided data is a free-form text document representing Swiss AHV Lohnbescheinigung (Wage Certificate) forms. It lacks a consistent tabular structure with columns and headers. The content appears to be a mix of header lines, address information, and financial totals, but does not contain any identifiable PII fields such as email, phone, or SSN. Due to the unstructured nature of the data, it cannot be mapped to any PII columns.

finanzen__LOBU__LOBU_Mahler__LOBU_2004__AbsenzPromea.csv
0 rows

File structure

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

Notes: This file is a free-form structured table in German, showing absence compensation data and leave categories. It contains no personal identifiers like names, emails, phone numbers, or addresses. All columns represent numerical or categorical data related to employee leave policies, compensation amounts, and absence days. No PII is present.

finanzen__LOBU__LOBU_Mahler__LOBU_2004__Bankenstamm.csv
5 columns1,852 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphigh[0] header 'BCNr' looks like internal identifier
1skiphigh[1] header 'Name' contains corporate entity names, not personal names
2address1high[2] header 'Zusatz1', values are street addresses
3address2high[3] header 'Zusatz2', values are post boxes or suite numbers
4ziphigh[4] header 'PLZOrt', values match Swiss PLZ (postal code) + Ort (city)

Notes: 50 rows shown, all rows appear to be corporate bank branch addresses in Switzerland. No personal PII fields detected in this sample. Columns 0-1 contain corporate identifiers and names, columns 2-4 contain address information. All other columns are absent in this sample.

finanzen__LOBU__LOBU_Mahler__LOBU_2004__Grunddaten.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be German-language payroll template or header definitions rather than actual records

finanzen__LOBU__LOBU_Mahler__LOBU_2004__Journale.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's internal corporate financial records with company names, addresses, and internal identifiers. Column 0 contains company names ('Firma'), column 1 contains addresses and location data ('Jahr' column appears mislabeled), and column 12 contains AHV-Nr. (Swiss social security numbers). However, per exclusion rules, 'Company' or 'Business' in column names means these MUST be skipped. Additionally, AHV-Nr. (Swiss social security) is NOT a US SSN and falls outside defined PII fields. All columns map to skip per rules: Company/Business references, internal IDs, timestamps. No email/phone/name/DOB/SSN fields present.

finanzen__LOBU__LOBU_Mahler__LOBU_2004__Lohnabrechnung_vorlage.csv
0 rows

File structure

Notes: The provided text is a free-form Swiss payroll document (Lohnabrechnung) with no consistent column structure or delimiter. It contains employee compensation details, tax withholdings, and payroll calculations in German, but lacks any repeated structured fields or identifiable PII columns. While it includes employee numbers (Personal-Nr.: 0) and dates (Januar 2004), these are embedded within prose rather than in a tabular format. The document appears to be a static payroll statement rather than a dataset with repeating rows.

finanzen__LOBU__LOBU_Mahler__LOBU_2004__Lohnausweis_vorlage.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__LOBU__LOBU_Mahler__LOBU_2004__Lohnkonto_vorlage.csv
0 rows

File structure

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

Notes: This is a corporate financial record file (payroll ledger) from Zynex AG. All columns appear to be internal accounting codes, financial aggregates, and Swiss labor identifiers (AHV-Nr.). No personal PII fields (names, addresses, emails, etc.) are present. Columns 0-16 contain only financial descriptors, account codes, and aggregated amounts. The file is purely structural and financial — no individual customer or employee PII is exposed.

finanzen__LOBU__LOBU_Mahler__LOBU_2004__Personalstamm.csv
7 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4fullNamehigh[4] header 'Name', values are full names
5firstNamehigh[5] header 'Vorname', values are first names
6address1high[6] header 'Strasse', values are street addresses
7ziphigh[7] header 'PLZ', values are postal codes
8cityhigh[8] header 'Ort', values are cities
9genderhigh[9] header 'Geschlecht', values are gender codes (M/F)
10skiphigh[10] header 'Geburtsdatum', values are birth dates

Notes: Columns mapped based on German headers and sample values. Personalstamm is likely a header row; subsequent rows contain personal data fields. Columns 0-3 appear to be empty or structural and are skipped. Columns beyond 10 (e.g., AHV Nr., Bank / Post) contain internal identifiers or non-PII data and are skipped.

finanzen__LOBU__LOBU_Mahler__LOBU_2004__RekapMonat.csv
0 rows

File structure

Notes: This is unstructured financial/ERP data from Zynex AG. Columns contain German financial terms and internal accounting codes, not personal PII. Values are invoice references, dates, amounts, and internal ledger codes. No identifiable personal data is present in the first 50 rows.

finanzen__LOBU__LOBU_Mahler__LOBU_2004__SuvaAb.csv
0 rows

File structure

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

Notes: This file appears to be structured financial/accounting records from Zynex AG, a Swiss web hosting company, with no personal identifiable information (PII) columns. All visible columns contain business data such as company names, financial figures, dates, and internal codes. No emails, phone numbers, addresses, or other PII fields are present. The data appears to be annual financial statements and billing records for Swiss SMEs using Zynex services, with all entries in Swiss Francs (CHF).

finanzen__LOBU__LOBU_Mahler__LOBU_2004__Total.csv
0 rows

File structure

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

Notes: This is not structured PII data; the file appears to be a template or form for payroll sheets (Lohnkontoblatt) with placeholder text and instructions in German. Columns contain labels like 'Alle gelben Felder ausfüllen' and 'mit Tabulatortaste weiter', not actual personal data. No email, phone, name, or address values are present in the sample rows. This is internal corporate template data, not a breach containing PII.

finanzen__LOBU__LOBU_Mahler__LOBU_2004__Verg.csv
0 rows

File structure

Notes: The file appears to be a free-form document (Vergütungsauftrag) with unstructured financial data. It contains no consistent column structure or delimited records. The content is in German and includes addresses, dates, and financial amounts, but lacks any identifiable personal information (PII) in a structured format. Per rules, unstructured files with no consistent row structure are mapped to empty columns.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__AHVAB.csv
0 rows

File structure

Notes: This is a free-form document (Swiss AHV Lohnbescheinigung templates) with no consistent columnar structure. It contains repetitive header/footer text and placeholders rather than actual personal records. No importable PII columns exist in the structured sense.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__AbsenzPromea.csv
0 rows

File structure

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

Notes: This is a free-form structured table with no personal identifiable information (PII) fields. It appears to be an absence compensation table for employees with columns indicating absence days, types of absences, and monetary values. There are no columns containing names, addresses, emails, phone numbers, dates of birth, SSNs, passwords, usernames, or other PII fields. The data is purely administrative and does not contain any personal data of individuals.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Bankenstamm.csv
5 columns1,852 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighColumn header 'BCNr' is clearly an internal identifier / counter, not a PII field
1skiphighColumn header 'Name' contains only Swiss bank names, not personal names. Values are all corporate entities like 'Schweizerische Nationalbank' and 'UBS AG'
2address1highColumn header 'Zusatz1' contains street addresses like 'Börsenstrasse 15', 'Bahnhofstrasse 26', etc.
3address2highColumn header 'Zusatz2' contains secondary address information like 'Postfach 4388', 'Case postale', etc.
4ziphighColumn header 'PLZOrt' contains Swiss postal codes and city names like '8022 Zürich', '3003 Bern', etc.

Notes: 50 rows shown, all rows are structured CSV data. Columns 0 and 1 contain internal IDs and corporate bank names respectively, not personal PII. Columns 2, 3, and 4 contain Swiss addresses (street, secondary address, and postal code + city). No emails, phone numbers, names, DOB, SSN, or passwords are present in the sample.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Grunddaten.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Journale.csv
0 rows

File structure

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

Notes: This is not structured PII data; the file appears to be a financial/treasury document from Zynex with corporate accounting entries. Columns contain Swiss business names, addresses, and financial codes rather than personal customer data. No PII fields (email, phone, name, etc.) are present. Column 0 contains company names like 'Peter Brunner Treuandbüro', column 1 contains addresses like 'Pfäffikerstrasse 6', and column 12 contains Swiss AHV/Suva social security numbers which are national insurance identifiers, not PII in the context of customer records. This is internal corporate financial metadata.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Lohnabrechnung_1.csv
0 rows

File structure

Notes: This is an unstructured payroll document in German with no consistent column mapping. Contains employee name 'Peter Brunner' and AHV number '111.22.333.555' but lacks structured columns to map. File appears to be a free-form payroll record rather than a delimited dataset with repeating rows. No column indices can be mapped to PII fields due to free-form layout.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Lohnabrechnung_2.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Lohnabrechnung_vorlage.csv
0 rows

File structure

Notes: This is a free-form text file representing a Swiss payroll slip (Lohnabrechnung). It contains no consistent delimiter structure or column headers. The data appears to be formatted as a table with merged cells and blank lines, but every line has a different shape and length. While it contains personal data (name, address, AHV number, etc.), it lacks a structured tabular format that can be mapped to columns. The unstructured format will route this file through a streaming PII extractor for embedded emails/phones, though none are visibly present in the sample.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Lohnausweis_1.csv
0 rows

File structure

Notes: The provided data is unstructured Swiss tax document prose (Lohnausweis für die Steuererklärung). The content contains no consistent columnar structure across rows — instead it displays free-form German-language tax record text with embedded names, addresses, and AHV (Swiss social security number) values. The sample shows lines like "Herr Brunner Mark Pfäffikerstrasse 6" and "AHV-Nummer: 111.22.333.555". This is free-form text with embedded PII, not a CSV/TSV with defined columns.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Lohnausweis_2.csv
0 rows

File structure

Notes: This is a free-form document containing unstructured German tax/employment records. No consistent delimiter or column structure exists across the sample rows. The values appear to be prose lines from Swiss employment tax forms ("Lohnausweis für die Steuererklärung"), not tabular data. Though AHV number (Swiss social security) appears in one line, the lack of structured columns means we must treat this as unstructured text for downstream processing.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Lohnausweis_vorlage.csv
0 rows

File structure

Notes: This is a Swiss payroll tax document (Lohnausweis für die Steuererklärung) containing free-form text entries with no consistent column structure. The sample shows tax form headers like 'Abteilung', 'Arbeitsort', 'Arbeitnehmer', and 'Arbeitgeber' with values that are form labels, placeholders (#N/A), and locations rather than structured PII records. No repeated column patterns exist across rows, and values are mixed form text rather than tabular data. Despite the Swiss context and potential sensitivity, this is a document template/form, not a delimited dataset with personal identifiers.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Lohnkonto_1.csv
0 rows

File structure

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

Notes: This is a financial record file (payroll accounting) with no personal identifiers. Columns contain accounting codes, dates, and amounts. No emails, phone numbers, names, or addresses are present. The file appears to be structured financial data from Zynex's ERP system, not containing any PII fields as defined.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Lohnkonto_2.csv
0 rows

File structure

Notes: This is not a delimited file with structured columns; it's free-form text with embedded personal data. The content appears to be Swiss payroll records with names, addresses, and national insurance numbers (AHV-Nr.) embedded in prose lines rather than a consistent tabular format. Since there is no consistent delimiter and lines have wildly different shapes, this qualifies as unstructured data with embedded PII that should be processed by a streaming extractor.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Lohnkonto_vorlage.csv
0 rows

File structure

Notes: This is unstructured financial ledger data with no consistent columnar pattern. Values appear to be mixed financial entries and text labels rather than structured PII fields. No identifiable PII columns can be mapped.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Personaldaten.csv
9 columns2 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] header 'Bezeichnung', values are full names like 'Brunner Mark'
3lastNamehigh[3] header 'Name', values are surnames
4firstNamehigh[4] header 'Vorname', values are given names
5address1high[5] header 'Strasse', values are street addresses
6ziphigh[6] header 'PLZ', values are Swiss postal codes
7cityhigh[7] header 'Ort', values are city names
8genderhigh[8] header 'Geschlecht', values '1' likely encode gender
9dobmedium[9] header 'Geburtsdatum', values are numeric dates (YYMMDD)
13ssnhigh[13] header 'AHVNr', values match Swiss AHV/NI number format (e.g., 111.22.333.555)

Notes: 21 columns total, 9 contain PII. Columns 0, 10-12, 14-20 are internal IDs, counters, or non-PII metadata and skipped. Values in 'Geburtsdatum' are encoded as numeric dates; mapping as dob with medium confidence due to format ambiguity.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Personalstamm.csv
5 columns0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
4lastNamehigh[4] header 'Name', values are surnames
5lastNamehigh[5] duplicate of column 4, also contains surnames
6firstNamehigh[6] header 'Vorname', values are given names
10skiphigh[10] header 'Geburtsdatum', values match date format
13skiphigh[13] header 'AHV Nr.', values match Swiss AHV number format (11.22.333.444)

Notes: This is a Swiss personnel record file with columns in German. Contains personal data including names, date of birth, and Swiss social security (AHV) numbers. Other columns are internal identifiers, employment dates, and bank account details which are skipped per rules.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__RekapMonat.csv
0 rows

File structure

Notes: This file is unstructured financial/procurement data from Zynex. The lines appear to be free-form German accounting entries rather than a delimited table. Sample lines show company names (Peter Brunner Treuandbüro), addresses (Pfäffikerstrasse 6, 8604 Volketswil), and reference numbers (E3454, 234773). No consistent column structure or delimiter is present across the 50 rows, and values are not in a tabular format. The content appears to be internal corporate financial records rather than customer PII. No PII columns can be mapped.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__SuvaAb.csv
5 columns93 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
11fullNamehigh[11] header 'Name / Vorname', values are full names like 'Peter Brunner Treuandbüro'
21address1high[21] values are street addresses like 'Pfäffikerstrasse 6'
22ziphigh[22] values are Swiss postal codes like '8604'
23cityhigh[23] values are Swiss cities like 'Volketswil'
31genderhigh[31] values are 'M'/'F' corresponding to gender

Notes: 36 total columns. Columns 11, 21-23, and 31 contain PII. All other columns are financial/accounting data, internal IDs, or empty fields. Data appears to be Swiss payroll records with names, addresses, and gender, but no emails, phones, DOB, SSN, or passwords present.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Total.csv
0 rows

File structure

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

Notes: This file is unstructured financial data from Zynex's payroll and invoicing system. It contains no identifiable personal information (PII) in the first 50 rows. The data appears to be internal accounting records with company names, account numbers, dates, and monetary values, but no names, addresses, emails, or other PII fields. All columns appear to represent internal financial identifiers, dates, or monetary amounts rather than personal data.

finanzen__LOBU__LOBU_Mahler__LOBU_TestDaten__Verg.csv
0 rows

File structure

Notes: This is a free-form text file (Swiss German financial document) with no consistent columnar structure. It contains payment instructions and addresses but lacks any machine-readable format. Though names and addresses appear, they are embedded in prose rather than structured fields.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AHVAB.csv
1 column7 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] values are common Swiss surnames (Meier, Müller)

Notes: This appears to be Swiss AHV (social security) payroll records. Only column 1 contains personal names (fullName). All other columns contain employment dates, AHV/insurance amounts, and totals — no other PII detected. No emails, phones, DOB, or addresses present in the sample.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN1.csv
0 rows

File structure

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

Notes: This is a structured financial ledger with no personal identifiable information (PII). Columns contain accounting codes, month names, numeric values, and generic financial descriptors. No emails, phone numbers, names, addresses, dates of birth, or other PII fields are present.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN10.csv
0 rows

File structure

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

Notes: This is a structured financial/administrative document in German (Swiss payroll ledger). Columns contain accounting codes, dates, amounts, and internal references — NO personal identifiers. 'Name, Vorname:' column shows only placeholders like 'Strasse:' and 'PLZ, Ort:' without actual names/addresses. 'AHV-Nr.' is a Swiss social security number but values are empty. No emails, phones, DOB, or SSN present. All columns are internal business data — skip all.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN11.csv
0 rows

File structure

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

Notes: This is an unstructured financial document (Swiss payroll ledger) with no personal identifiers. Columns contain accounting terms (e.g., 'Lohnkontoblatt' = payroll sheet), months, amounts, and internal codes. No emails, phones, names, addresses, DOB, SSN, or other PII fields are present. Values are purely financial and organizational.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN12.csv
0 rows

File structure

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

Notes: This file appears to be a Swiss payroll ledger (Lohnkontoblatt) from Zynex. Columns contain internal accounting codes, dates, and financial aggregates. No PII fields (names, addresses, emails, etc.) are present in the visible sample rows. All columns map to internal business data, financial totals, or accounting codes — none qualify as PII under the defined field types. The values shown are generic accounting entries ('Manuelle Maximum-Abgrenzungen'), date headers ('Januar', 'Februar'), and numeric totals.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN13.csv
0 rows

File structure

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

Notes: This is a Swiss payroll ledger (Lohnkontoblatt) in German, not a personal customer database. Columns contain internal accounting codes, financial aggregates, and employment metadata. No identifiable PII fields (email, phone, DOB, etc.) are present. Values like 'Peter Brunner' appear to be business contact names, not customer PII. All columns map to skip categories: internal IDs (Lohnkontoblatt), financial codes, timestamps (months), employment flags, and aggregates.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN14.csv
0 rows

File structure

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

Notes: This is a Swiss payroll ledger in German with no personal identifiers. Columns contain accounting codes (Lohnkontoblatt), employer details (LA), financial amounts, and generic employment metadata (AHV-Nr., Kinderanzahl). No emails, phone numbers, or direct PII fields like name or address appear. All columns are financial/accounting references or internal codes — none map to PII fields. Therefore, no PII columns to report.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN15.csv
0 rows

File structure

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

Notes: This is a Swiss payroll document (Lohnkontoblatt) containing internal corporate financial records with no personal identifiable information (PII). Columns contain internal accounting codes, financial figures, and corporate metadata. No emails, phone numbers, names, addresses, dates of birth, SSNs, or other PII fields are present. All columns map to skip categories per exclusion rules (company data, internal IDs, financial/transactional data, timestamps).

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN16.csv
0 rows

File structure

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

Notes: This is a Swiss payroll/banking statement format (Lohnkontoblatt) with internal accounting codes, financial aggregates, and employee identifiers. No columns contain PII fields. Column 5 contains the literal string 'Name, Vorname:' but no actual names appear in sample values. All columns represent financial codes, dates, monetary amounts, or internal identifiers (e.g., AHV-Nr. is Swiss social security number but sample shows only headers, no actual values). Values shown are placeholders or internal codes, not real PII. Per breach context, this is internal corporate financial data, not customer PII.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN17.csv
0 rows

File structure

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

Notes: This appears to be a Swiss payroll ledger (Lohnkontoblatt) with internal accounting codes and employee references. No actual PII is present - all entries are internal codes, account names, and numeric values. Columns contain German terms like 'Name, Vorname:' but no actual names or addresses are filled in the sample rows. All data appears to be internal financial/operational codes and monetary amounts.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN18.csv
0 rows

File structure

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

Notes: This is a payroll ledger in German with no personal identifiers. Columns contain only internal accounting codes (Lohnkontoblatt), account names, dates, numeric amounts, and generic employment metadata. No PII fields are present.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN19.csv
0 rows

File structure

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

Notes: This is a structured corporate financial document (payroll sheet) in German, not customer PII. Columns contain accounting codes, financial figures, and internal references (e.g., Lohnkontoblatt = payroll account, AHV-Nr. = Swiss social security number). No personal identifiers (names, emails, addresses, etc.) are present in the sample rows. All values are internal financial metadata, company names, or numeric entries. No PII fields map to the defined categories.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN2.csv
0 rows

File structure

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

Notes: NOT DATA: This file is a German payroll register template (Lohnkontoblatt) with mixed header labels, field descriptors, and sample accounting entries. The structure is NOT a delimited data file with consistent rows of PII records. Instead, it contains: (1) template headers and form labels in German (e.g., 'Pers. Nr.', 'Name, Vorname', 'Geburtsdatum', 'Geschlecht', 'Anrede', 'Kindernamen', 'Heimatort', 'Bankverbindung'); (2) sparse example employee data (name 'Müller', gender 'M', title 'Herrn'); and (3) monthly accounting line items (months, amounts, account codes like '19.01'). Each column contains heterogeneous content (mixing labels, dates, numeric codes, and values) that does not align into a consistent record structure. This is administrative documentation / a payroll form template, not a structured breach export. No importable PII records can be extracted.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN20.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent columnar structure. The sample shows unstructured Swiss payroll ledger entries from Zynex's internal financial records, containing German-language accounting lines rather than tabular PII. No importable column structure exists.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN21.csv
0 rows

File structure

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

Notes: This is a structured corporate payroll document in German ("Lohnkontoblatt"). Columns contain internal accounting codes, salary calculations, and corporate metadata. No personal identifiers (names, addresses, emails, etc.) appear in the sample rows — only internal reference numbers and financial aggregates. Values like "Peter Brunner Treuandbüro" represent company names/departments, not personal PII. All columns map to skip categories (company data, internal IDs, financial aggregates, timestamps). No email, phone, dob, ssn, or address fields are present.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN22.csv
0 rows

File structure

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

Notes: This is a structured financial ledger file (payroll/accounting sheet) in German. Columns contain internal accounting codes, monetary amounts, dates (month names), and generic labels like 'Anrede' (salutation) and 'Geschlecht' (gender). No identifiable PII fields are present: names appear only as generic placeholders ('Peter Brunner Treuandbüro'), addresses are incomplete/institutional ('Pfäffikerstrasse 6'), and gender codes ('M') are not tied to individuals. All columns are accounted for as skip per rules (company/business references, internal IDs, financial/timestamps, honorifics).

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN23.csv
0 rows

File structure

Notes: The provided data appears to be unstructured financial records from Zynex, a Swiss web hosting company. The data consists of free-form text entries without consistent column structures or delimiters. The entries appear to be manually entered accounting entries with titles like "Lohnkontoblatt" and contain entries such as names, addresses, and account numbers, but they are not in a tabular format. Due to the lack of consistent structure and delimiter, this is classified as unstructured data. No column mapping can be performed as there are no defined columns.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN3.csv
0 rows

File structure

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

Notes: This appears to be a Swiss payroll register with financial and employment metadata, not a customer PII breach. Columns contain account codes, dates, amounts, and employment status indicators. No identifiable personal data (names, addresses, emails, etc.) is present in the sample. Columns like 'Name, Vorname:' and 'AHV-Nr.' are headers but contain no actual values in the visible rows.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN4.csv
0 rows

File structure

Notes: This is a free-form financial ledger document ("Lohnkontoblatt" = payroll sheet) with no consistent columnar structure. Values represent account codes, month names, numeric amounts, and static labels rather than PII fields. No identifiable personal data is present in the sample rows.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN5.csv
0 rows

File structure

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

Notes: This is a corporate financial document (payroll sheet) with no personal identifiable information. Columns contain internal accounting codes, company names, and financial figures — no names, addresses, or other PII. The 'Name, Vorname:' column appears to be a header label, not actual data. All columns are internal business data or financial aggregates.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN6.csv
0 rows

File structure

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

Notes: This appears to be a Swiss payroll or accounting document (Lohnkontoblatt = payroll sheet) with internal corporate codes, financial entries, and employment metadata. No PII fields are present — columns contain account codes, financial figures, employment status flags, and Swiss tax identifiers (AHV-Nr.) that are NOT considered PII under GDPR/US regulations. Values like 'Peter Brunner Treuandbüro' appear to be company names or department labels, not personal names. All columns map to skip categories: internal IDs, company metadata, financial counters, timestamps, and flags.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN7.csv
0 rows

File structure

Notes: This is unstructured financial accounting data from Zynex's Lohnkontoblatt (payroll ledger). The data appears to be free-form accounting entries with no consistent columnar structure across rows. While some lines contain what looks like personal names (e.g., "Peter Brunner Treuandbüro"), these appear to be business entity names rather than individual PII, and the format lacks any consistent mapping to identifiable PII fields. The data represents internal corporate financial records rather than customer PII.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN8.csv
0 rows

File structure

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

Notes: This is a structured corporate financial record file (Swiss payroll ledger) with no personal identifiable information (PII). Columns contain internal accounting codes, financial figures, dates, and generic employment metadata. No emails, phone numbers, names, addresses, or other PII fields are present. The file appears to be part of Zynex's internal financial records breach context.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AN9.csv
0 rows

File structure

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

Notes: This is a structured financial record file (salary ledger) from Zynex. All columns appear to be internal accounting identifiers, financial categories, and numeric values. No PII fields (names, addresses, emails, etc.) are present in the first 50 rows. Columns contain entries like account types (Lohnkontoblatt), dates (2002, Januar...), financial amounts (0.00), and internal codes (AHV-Nr., Anrede). These are purely corporate/financial metadata with no personally identifiable information exposed in this sample.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AW1.csv
0 rows

File structure

Notes: This is unstructured data with no consistent column structure. The sample shows free-form entries with no delimiter pattern. Values appear to be mixed text, numbers, and dates in an inconsistent format. The first row is a headerless record and subsequent rows vary in content and length. Given the breach context (Zynex corporate financial records) and the unstructured nature of the data, this should be processed as free-form text.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__AbsenzPromea.csv
0 rows

File structure

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

Notes: This is a free-form structured file with no actual PII columns. The data appears to be an absence table template with German headers and sample entries showing absence types and days, but no actual personal identifiers like names, addresses, or contact details are present in the first 50 rows. The columns contain absence codes, days, and monetary values, but no PII fields. Therefore, no columns map to PII fields.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__Anleitung.csv
0 rows

File structure

Notes: This is a free-form text document (instructions for payroll processing) with no consistent columnar structure. It contains no importable PII fields.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__Daten.csv
8 columns54 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] contains full names like 'Peter Brunner Treuandbüro'
2skiphigh[2] contains year value '2002', not PII
3skipcolumn name 'Journal' and values are date ranges, not PII
4skipcolumn name 'kumuliert' and values are numeric codes, not PII
5skipcolumn name empty, values are static text 'Lizenznehmer:'
6fullNamehigh[6] contains full names like 'Peter Brunner, Treuhand- u. Steuerrec...'
24skipcolumn name 'Druckdatum' and values are date stamps, not DOB
25skipcolumn name empty, values are static text 'Total'

Notes: This appears to be Swiss accounting/financial records with embedded personal names in columns 1 and 6. No emails, phones, addresses, DOB, SSN, or passwords are present. All other columns contain numeric codes, dates, or static text.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__Inhalt.csv
0 rows

File structure

Notes: This is a free-form document (appears to be a German-language table of contents or index for payroll/banking software). No consistent columnar structure exists — lines vary in length and content, and the content is purely descriptive prose about functions rather than data records. No PII is present in this sample.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__Journale.csv
0 rows

File structure

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

Notes: This is not structured PII data. The file appears to be financial records with internal business identifiers, Swiss tax IDs, and numeric values. Column 0 contains a mix of text like 'Firma' and numeric codes, column 1 contains addresses and names, but these appear to be business entities and internal references rather than personal customer data. Column 10 contains 'AHV-Nr.:' which is a Swiss social security number format, but the values shown are not AHV numbers (they are 'Suva-Nr.:' and zeros). There are no clear email addresses, phone numbers, or personal names in the sample. This appears to be corporate financial data, not customer PII. All columns map to skip categories (company names, internal IDs, timestamps, financial amounts).

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA1.csv
0 rows

File structure

Notes: The provided data is a free-form payroll document with no consistent column structure. It contains employee names (Peter Brunner, Meier) but lacks any standardized delimiters or headers. The format is unstructured text with embedded personal data rather than a CSV or table structure. This meets the unstructured criteria: (a) no consistent delimiter, (b) lines have varying structure and content, (c) contains names that could be considered PII.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA10.csv
0 rows

File structure

Notes: This is a free-form Swiss payroll document in German. It contains no consistent columnar structure—rows are mixed headers, labels, and values (e.g., 'Pfäffikerstrasse 6', 'AHV-Abr.Nr.:'). No repeated delimiter patterns exist across lines, and values are financial/legal text. Though names like 'Herrn' and 'Pfäffikerstrasse' appear, they are not in a tabular format. Per rules, unstructured files with no consistent columns return empty columns.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA11.csv
0 rows

File structure

Notes: This is a free-form payroll document in German with no consistent column structure across rows. It contains payment details, tax calculations, and salary components but lacks repeating columnar data. The document includes names like 'Peter Brunner' and addresses like 'Pfäffikerstrasse 6, 8604 Volketswil', but these appear as free text rather than in a tabular format. No structured PII columns exist to map.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA12.csv
0 rows

File structure

Notes: This is a free-form text file containing a payroll document in German. The file lacks consistent column structure and is composed of sentences, labels, and tabular data embedded in prose. While it contains personal data (name: Peter Brunner, address: Pfäffikerstrasse 6, 8604 Volketswil), it does not have a consistent delimiter or row structure across lines. Therefore, it is classified as unstructured text with embedded PII that should be processed by a streaming email/phone extractor.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA13.csv
0 rows

File structure

Notes: The provided data is a free-form payroll document with no consistent columnar structure. It appears to be a Swiss payroll slip (Lohnabrechnung) containing employee details, salary components, and tax withholdings. While it contains sensitive personal financial data, the format does not lend itself to column mapping as it is not a delimited structured file. The content includes employee name (Peter Brunner), address (Pfäffikerstrasse 6, 8604 Volketswil), and dates (10/31/03, January 2002), but these are embedded within prose rather than in a tabular format.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA14.csv
0 rows

File structure

Notes: This is a free-form structured document (Swiss payroll slip) with no consistent columnar delimiter across lines. It contains personal employee data like name, address, and AHV insurance number, but lacks a consistent tabular format. The data appears to be a single payroll record rather than a dataset with repeating rows.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA15.csv
0 rows

File structure

Notes: The file is a free-form text document containing Swiss payroll calculations and financial records. It lacks consistent delimiters and structured columns across rows. Contains employee names (Pfäffikerstrasse, Herrn) and Swiss AHV/insurance numbers (AHV-Abr.Nr.: 0, Personal-Nr.: 15), but these appear in unstructured prose rather than tabular format. This qualifies as unstructured data with embedded PII that should be processed through a streaming email/phone/PII extractor.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA16.csv
0 rows

File structure

Notes: This is an unstructured payroll document in German. The sample contains employee names (Pfäffikerstrasse 6 address appears to be a location rather than a personal address), Swiss social security numbers (AHV-Abr.Nr.), and salary calculations, but lacks consistent columnar structure. The text is free-form with no shared delimiter across lines, variable line lengths, and contains embedded personal identifiers in prose format. This meets unstructured criteria: no consistent delimiter, variable line shapes, and contains personal data inline.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA17.csv
0 rows

File structure

Notes: The provided data is a free-form payroll document in German. It contains no consistent column structure or delimiter across lines — instead, it appears as a formatted table with merged cells, headers, and footers typical of printed pay slips. There are no repeating column positions or shared delimiters. While it contains personal employee data (names, AHV number, address), these appear inline within free-text lines rather than in a tabular format. According to the unstructured opt-out rules, this qualifies as unstructured text with embedded PII.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA18.csv
0 rows

File structure

Notes: This is a free-form text payroll document (Lohnabrechnung) in German. No consistent delimiter structure exists across rows, and it contains no structured columns. It appears to be a printed Swiss payroll statement for an employee named Peter Brunner, dated January 2002. While it contains personal information like names and Swiss AHV number (0), the data is unstructured prose rather than a delimited table with columns.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA19.csv
0 rows

File structure

Notes: This is a free-form structured document (payroll slip) with no consistent delimiter across rows. It contains header-like labels but the layout is inconsistent and tabular data is embedded in prose. While it contains personal data (name, address, AHV insurance number), it lacks a uniform columnar structure. The unstructured parser will extract any visible emails/phones, but no column mapping is possible.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA2.csv
0 rows

File structure

Notes: This is a free-form payroll document with no consistent column structure. The data appears to be a Swiss payroll statement (Lohnabrechnung) showing salary calculations, taxes, and deductions for an employee. There are no repeating column positions or delimiters — values are interspersed with labels. While it contains personal identifiers like names (Pfäffikerstrasse, Herrn Müller) and possibly addresses, the format lacks a structured tabular layout required for column mapping. The unstructured format contains embedded PII that should be processed through a streaming email/phone/text extractor.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA20.csv
0 rows

File structure

Notes: The provided data is a free-form payroll document in German (Swiss format) with no consistent column structure. It contains unstructured text lines describing salary components and calculations rather than a tabular dataset. There are no identifiable PII columns in this format.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA21.csv
0 rows

File structure

Notes: The provided text is a free-form payroll document (Lohnabrechnung) with no consistent columnar structure. It contains employee name (Herrn), address (Pfäffikerstrasse 6, 8604 Volketswil), and AHV insurance number (AHV-Abr.Nr.: 0), but these are embedded within unstructured lines rather than a tabular format. The document appears to be a Swiss payroll slip from January 2002, but lacks a consistent delimiter or header row across rows. It meets unstructured criteria: (a) no consistent delimiter, (b) lines vary in content/length, (c) contains personal identifiers like names and addresses inline.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA22.csv
0 rows

File structure

Notes: The file appears to be a free-form Swiss payroll document (Lohnabrechnung) with no consistent column structure. It contains employee data like name (Peter Brunner), address (Pfäffikerstrasse 6, 8604 Volketswil), and AHV number (social security equivalent). While it contains PII, the format does not conform to a structured tabular format with consistent columns across rows, meeting the unstructured criteria: no delimiter, variable line shapes, and contains PII. This should be processed by unstructured text extraction for emails/phones if present beyond the visible snippets.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA23.csv
0 rows

File structure

Notes: This is a free-form text file containing Swiss payroll calculations and financial data. It lacks consistent column delimiters and row structures, showing raw accounting lines with headers and values interleaved. While it contains names (Peter Brunner) and addresses (Pfäffikerstrasse 6, 8604 Volketswil), the format is unstructured prose rather than a tabular dataset. The breach context indicates this is internal corporate financial records, not customer PII.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA3.csv
0 rows

File structure

Notes: The sample is a Swiss payroll document (Lohnabrechnung) in German, formatted as a free-form table with no consistent columnar structure across rows. It contains employee name (Peter Brunner), address (Pfäffikerstrasse 6, 8604 Volketswil), and Swiss social security number (AHV-Abr.Nr.: 0, Personal-Nr.: 3). However, the format lacks a fixed delimiter and column alignment, with values spanning irregular positions and blank cells. Per the unstructured rules, it qualifies as free-form text with embedded PII despite the tabular appearance.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA4.csv
0 rows

File structure

Notes: This is a free-form Swiss payroll document in German with no consistent column structure. It contains employee names (Peter Brunner), address (Pfäffikerstrasse 6, 8604 Volketswil), and payroll data but lacks a tabular format with repeating rows/columns. The content is unstructured prose with embedded personal data rather than a delimited dataset.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA5.csv
0 rows

File structure

Notes: The provided text is a free-form Swiss payroll slip (Lohnabrechnung) in German, not a delimited dataset. It contains employee details like name (Pfäffikerstrasse 6), address (8604 Volketswil), AHV number (social security), and pay details, but lacks consistent columnar structure across rows. The format is unstructured prose with embedded PII values rather than a CSV/TSV. Per rules, this routes to unstructured processing for email/phone extraction.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA6.csv
0 rows

File structure

Notes: free-form text with embedded names (Herrn, Peter Brunner) and address (Pfäffikerstrasse 6, 8604 Volketswil). No consistent delimiter or row structure present. This appears to be a Swiss payroll document in German with structured tabular data sections, but the entire file lacks a consistent columnar format across rows. Contains no visible emails or phone numbers.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA7.csv
0 rows

File structure

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

Notes: The provided data is a free-form text representation of a Swiss payroll slip (Lohnabrechnung) and does not contain any structured columns or PII fields. The data appears to be a single record in a tabular format without headers, and the values are mostly non-PII entries such as payroll codes, amounts, and descriptions. No identifiable personal information (PII) such as names, addresses, or contact details are present in a structured format. Therefore, no columns can be mapped to PII fields.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA8.csv
0 rows

File structure

Notes: This is a payroll document in German. It contains structured header rows but no consistent column mapping across rows. Values like names and addresses appear but are not in a consistent tabular format. The document is a free-form payroll slip with embedded personal data (name, address) but lacks a consistent columnar structure. Per rules, unstructured files with no consistent delimiter structure across lines return empty columns.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LA9.csv
0 rows

File structure

Notes: This is a free-form text file (payroll document) with no consistent columnar structure. It contains German-language payroll data for an individual, including names and Swiss AHV insurance number. Though there is PII visible (names, AHV number), the file lacks any consistent delimiter or column structure across rows, satisfying the unstructured opt-out conditions. The document appears to be a printed payroll statement rather than a structured dataset.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__LAW.csv
0 rows

File structure

Notes: This is a free-form document titled "Lohnausweis für die Steuererklärung" (Pay slip for tax declaration). It contains unstructured text lines like department names, employment duration, and tax authority references. No consistent column structure or PII fields are present in the sample. The document appears to be a Swiss payroll/tax form template with placeholder text rather than actual data records.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__MusterLA.csv
0 rows

File structure

Notes: This is a free-form text file containing Swiss payroll records with no consistent columnar structure. Values represent names, addresses, and Swiss social security numbers (AHV-Abr.Nr.), but the layout is unstructured with no consistent delimiter or row pattern. The breach context confirms this is internal corporate financial data from Zynex, not customer PII. No column mapping is possible.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__Musterloko.csv
0 rows

File structure

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

Notes: This file is a German-language payroll ledger form (Lohnkontoblatt) exported as a grid. The layout is a form dump, not structured PII records — rows represent mixed form labels, month names, numeric values, and occasional person fragments. No column consistently maps to a single PII field across rows. Not importable as structured PII data.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__RekapMonat.csv
0 rows

File structure

Notes: The data appears to be free-form text containing financial records and accounting entries with no consistent columnar structure. The sample lines contain mixed text entries like addresses, dates, and financial amounts without a shared delimiter pattern. This matches the unstructured format condition: no consistent delimiter, varying line shapes, and financial prose rather than tabular data.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__SuvaAb.csv
0 rows

File structure

Notes: The sample provided appears to be a financial statement document from Zynex, not a structured dataset containing personal identifiable information. The content includes company names, financial figures, and dates but does not contain consistent columns mapping to PII fields. This appears to be a document formatted as a financial report rather than a dataset with individual customer records.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__Total.csv
0 rows

File structure

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

Notes: This file is a free-form financial document template with no structured columns containing PII. It appears to be a Swiss payroll form template (Lohnkontoblatt) with placeholders and instructions in German, not actual customer or employee data from the breach. All visible values are generic instructions, account types, or non-personal identifiers. No PII fields are present.

finanzen__LOBU__LOBU_Mahler__LOKO2003brunner1__Verg.csv
4 columns37 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] contains personal names like 'Peter Brunner Treuandbüro'
3address1high[3] contains street address 'Pfäffikerstrasse 6'
4cityhigh[4] contains city name 'Volketswil'
5ziphigh[5] contains postal code '8604'

Notes: This is a payment order document in German with structured columns. Columns 0-5 contain personal and address information. Other columns are payment details and bank information, which do not map to defined PII fields.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AHVAB.csv
2 columns9 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] values are German surnames like 'Meier', 'Müller'
2firstNamehigh[2] values are German given names like 'Peter'

Notes: File appears to be Swiss payroll records in German. Columns 1 and 2 contain full names broken into surname and given name fields. No other columns contain identifiable PII beyond names. Addresses and dates are present but not mapped as PII per exclusion rules (dates are employment dates, not DOB).

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN1.csv
0 rows

File structure

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

Notes: This is an unstructured financial ledger file from Zynex's payroll system (Lohnkontoblatt). The data contains internal accounting codes, account names, and numeric values with no personal identifiers. Columns appear to be free-form labels for financial categories (e.g., 'Meier' likely an account name, not a person). No PII fields detected; all columns represent internal financial metadata, account codes, or numeric values. No emails, phone numbers, names, addresses, or other PII appear in the sample.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN10.csv
0 rows

File structure

Notes: This is not a structured tabular file but a free-form financial document (payroll sheet) with mixed header lines and data lines. It contains no consistent column pattern and includes German payroll terminology rather than PII. No emails, phones, or other PII are visible in the sample.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN11.csv
0 rows

File structure

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

Notes: This appears to be a structured financial ledger document in German (Swiss payroll/accounting format). All visible columns contain internal accounting codes, financial totals, months, and internal reference numbers (e.g., Lohnkontoblatt, AHV-Nr., Kinderanzahl). No PII fields are present — names like 'Peter Brunner' appear in data rows but are not column headers, and values are mixed with financial/operational data. This is internal corporate financial metadata, not customer PII.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN12.csv
0 rows

File structure

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

Notes: This is a structured corporate financial record file (Swiss payroll/accounting sheet) with no personal identifiable information (PII). All columns contain internal accounting codes, financial aggregates, and corporate metadata. No email, phone, name, address, DOB, or SSN fields are present. Columns like 'Name, Vorname:' and 'AHV-Nr.' appear to be headers for potential data rows but contain only empty strings or financial values in the sample rows. This is purely internal financial data from Zynex's ERP system.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN13.csv
0 rows

File structure

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

Notes: This is a Swiss payroll document (Lohnkontoblatt) from Zynex. Columns contain internal accounting codes, payroll months, and numeric amounts — no PII fields like names, addresses, or DOBs are exposed in the visible structure. The sample shows placeholders like 'Name, Vorname:' but no actual personal data. All columns map to skip categories: internal IDs (LA, Pers. Nr.), company codes (AHV-Nr., Anrede), payroll totals (kumuliert), and financial flags (Aktiv = 1 / Passiv = 0). No email/phone/DOB/SSN/address patterns detected.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN14.csv
0 rows

File structure

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

Notes: This is a corporate accounting file (payroll ledger) from Zynex's internal systems, not customer PII. Columns contain Swiss accounting terms (Lohnkontoblatt = payroll sheet) and financial data. No personal identifiers like names, emails, or addresses appear in the first 50 rows. Values are internal codes ('LA'), numeric amounts, and generic labels ('Januar', 'Februar'). All columns are internal financial metadata — skip all.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN15.csv
0 rows

File structure

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

Notes: This file is a Swiss payroll ledger (Lohnkontoblatt) containing internal corporate financial records. All columns appear to represent accounting codes, payroll calculations, and internal references (e.g., 'LA' for Lohnkontoabgrenzungen, 'AHV-Nr.' for Swiss social security number). No personal identifiable information (PII) is present in the first 50 rows. Values are internal codes, numeric totals, and generic text labels. No emails, phone numbers, names, or addresses are visible.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN16.csv
0 rows

File structure

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

Notes: This is a payroll ledger in German with structured accounting columns. No personal identifiers (names, emails, phone numbers, DOB, etc.) are visible in the sample rows. Columns contain account codes, month names, amounts, and generic labels. The 'Name, Vorname:' column header suggests potential PII, but sample values show only street/ZIP/city fragments and no actual names. No columns map to defined PII fields.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN17.csv
0 rows

File structure

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

Notes: This is a structured file but contains only internal accounting/financial data (payroll ledger) with no identifiable PII fields. Columns contain account codes, month names, numeric values, and internal identifiers (LA, AHV-Nr., Pers. Nr.) that are not mappable to any PII categories per the rules. No emails, phones, names, addresses, or other PII appear in the sample.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN18.csv
0 rows

File structure

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

Notes: This is a Swiss payroll document (Lohnkontoblatt) with structured financial/accounting data. Columns contain accounting codes, month names, monetary values, and internal identifiers (LA, AHV-Nr., Pers. Nr.). No actual PII fields (names, addresses, emails, etc.) are present in the visible sample - values like 'Peter Brunner Treuandbüro' appear to be entity names or department labels, not personal records. All columns map to skip categories: company names, internal IDs, financial counters, timestamps (month columns), and flags.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN19.csv
0 rows

File structure

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

Notes: This appears to be a Swiss payroll ledger (Lohnkontoblatt) with no personal identifiable information in the first 50 rows. Columns contain accounting codes, month names, and numeric values. No emails, phone numbers, or other PII fields are visible. Columns with names like 'Name, Vorname:' and 'Geburtsdatum:' are headers but contain no actual data in the sample rows.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN2.csv
0 rows

File structure

Notes: This file is a German payroll ledger template (Lohnkontoblatt) with structural metadata, field labels, and month headers rather than actual employee PII records. Row 0 contains column descriptors ('Lohnkontoblatt', 'Manuelle Maximum-Abgrenzungen', 'Firma', 'LA', '100'), row 1 shows example/template text ('Peter Brunner Treuandbüro', 'Pfäffikerstrasse 6'), and rows 2-16 are month labels (Januar, Februar, März, etc.) with placeholder values and accounting codes (19.01). No consistent record structure with actual PII instances exists; this is a document template or schema definition, not a data export containing employee records suitable for column mapping.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN20.csv
0 rows

File structure

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

Notes: This is not structured PII data; it's an internal corporate financial record from Zynex. Columns contain accounting codes, internal identifiers, financial figures, and generic labels (e.g., 'Lohnkontoblatt', 'AHV-Nr.'). No actual personal identifiers like names, emails, or addresses are present in the sample rows. Values appear to be internal codes, financial amounts, or generic placeholders rather than PII. Therefore, no PII columns to map.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN21.csv
0 rows

File structure

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

Notes: This is a structured financial ledger in German with no PII columns. Columns contain accounting terms (e.g., 'Lohnkontoblatt'), account types, months, numeric values, and internal codes. No personal identifiers like names, addresses, or contact details are present in the visible columns. The data appears to be aggregated payroll/accounting records without individual employee PII.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN22.csv
0 rows

File structure

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

Notes: This is a structured financial record file (Lohnkontoblatt - payroll sheet) with no identifiable PII fields. Columns contain account codes, financial aggregates, and internal references. While some headers hint at potential personal data ('Name, Vorname:', 'Geburtsdatum:', 'AHV-Nr.'), the sample values show only financial codes, numeric aggregates, and generic placeholders rather than actual personal information. No emails, phone numbers, or direct identifiers appear in the visible data. Per strict rules, columns with 'Company' references (implied by financial context) are skipped.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN23.csv
0 rows

File structure

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

Notes: This is a payroll ledger in German with no personal identifiers. Columns contain accounting codes, totals, month names, and gender codes (M/F) but no names, addresses, emails, phones, or DOB. The only potentially sensitive field 'Geschlecht' (gender) is not mapped because it's not a searchable PII field per the schema. All columns are financial/accounting metadata.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN3.csv
0 rows

File structure

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

Notes: This appears to be a Swiss payroll/banking statement format ("Lohnkontoblatt") with internal corporate/financial data. Columns contain accounting codes, months, and numeric values with no personal identifiers. No PII fields detected — all columns are internal business codes, numeric amounts, or month labels. The breach context mentions financial records but this particular file only contains corporate accounting data without customer or employee PII.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN4.csv
0 rows

File structure

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

Notes: This appears to be a structured financial/administrative document in German (Swiss payroll or accounting sheet) with no PII fields. Columns contain accounting codes, financial figures, and generic labels like 'LA', 'AHV-Nr.', and month names. No identifiable personal information such as names, addresses, or contact details is present in the first 50 rows. All columns either represent internal codes, financial aggregates, or generic placeholders. Per exclusion rules, no columns map to PII fields.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN5.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. It contains unstructured financial records from Zynex, including entries like 'Peter Brunner Treuandbüro', 'Pfäffikerstrasse 6', '8604 Volketswil'. There are no clear, repeatable columns that map to PII fields. The data is formatted as a series of lines with varying content, making it unsuitable for structured column mapping. However, embedded personal data may exist and requires unstructured processing.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN6.csv
0 rows

File structure

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

Notes: This is a structured financial ledger file (Swiss payroll/accounting) with no PII columns. All visible fields are internal accounting codes, financial aggregates, dates, and numeric values. No names, addresses, emails, phones, or other PII appear in the first 50 rows. Columns like 'Name, Vorname:' and 'AHV-Nr.' are headers but contain only placeholders ('Strasse:', 'PLZ, Ort:', etc.) or internal codes ('M', 'A', 'Herrn') — not actual personal data. Per breach context, this is internal corporate financial data from Zynex's FaktNT ERP system, not customer PII.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN7.csv
0 rows

File structure

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

Notes: This is a structured financial record file from Zynex's payroll system (Lohnkontoblatt). All visible columns contain internal accounting codes, financial aggregates, and employment metadata. No PII fields (names, addresses, DOB, etc.) are exposed in this structured format. The sample shows Swiss German payroll terminology and numeric financial values, consistent with the breach context. Columns are either internal identifiers or aggregated financial data — none map to the defined PII fields.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN8.csv
0 rows

File structure

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

Notes: This is a structured financial record file (Swiss payroll ledger) with no personal identifiable information (PII) columns. All visible fields are internal accounting codes, dates, amounts, and internal identifiers (e.g., AHV-Nr. is a Swiss social security number but is not exposed as PII in this context). No emails, phone numbers, addresses, names, or other PII appear in the sample. Columns map to internal financial data only.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AN9.csv
0 rows

File structure

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

Notes: This appears to be a structured financial/lohnkontoblatt (payroll) document in German, not a PII dataset. Columns contain accounting terms (e.g., Lohnkontoblatt, AHV-Nr., Kinderanzahl), date/month headers (Januar, Februar...), and numeric values representing financial entries. No personal identifiers (names, addresses, emails, etc.) are present in the sample. All columns map to skip categories per exclusion rules (company financial records, internal accounting codes). No PII fields detected.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AW1.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent columnar structure. Values represent financial and descriptive data rather than structured PII fields. No identifiable PII columns can be mapped.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__AbsenzPromea.csv
2 columns19 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header 'Name, Vorname', values are full names
1skiphigh[1] header 'bei Tod Verwandschaftgrad', contains relationship codes

Notes: File appears to be an absence tracking table in German with employee names and absence codes. Only column 0 contains PII (full names). Other columns contain absence codes, dates, and monetary values which are not PII fields.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__Anleitung.csv
0 rows

File structure

Notes: This is a free-form text document (appears to be a German-language instruction manual for payroll processing). There are no consistent delimiters or structured columns across lines — each line is a separate sentence or paragraph. While it contains corporate context and a name at the end, it does not contain any repeated PII fields or structured data rows. Therefore it must be processed as unstructured text.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__Daten.csv
4 columns60 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1fullNamehigh[1] values are full names like 'Peter Brunner Treuandbüro'
2address1high[2] values are street addresses like 'Pfäffikerstrasse 6'
3cityhigh[3] values are cities like '8604 Volketswil'
4fullNamehigh[4] values are full names like 'Meier'

Notes: 26 columns total, 4 contain PII. Columns 0, 5-25 are financial/numeric/timestamp fields, internal IDs, or empty. Column 24 (Druckdatum) contains timestamp values and is skipped.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__Inhalt.csv
0 rows

File structure

Notes: The provided text is a free-form document in German describing various payroll and accounting functions within Zynex's internal systems. It contains no structured data rows or consistent delimiters. The content appears to be a README or user manual explaining features of the Lohnkontoblatt (payroll sheet) system, with no actual PII data present in the sample.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__Journale.csv
0 rows

File structure

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

Notes: This is unstructured financial/billing data with no PII columns. Columns represent company names (Firma), years (Jahr), journal entries (Journal), dates (Druckdatum), and numeric financial values. No personal identifiers (names, addresses, emails, etc.) are present in the sample rows. All columns map to business/financial data and should be skipped.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA1.csv
0 rows

File structure

Notes: The provided data appears to be a structured payroll or salary statement in German, but it does not contain any identifiable personal information such as names, addresses, email addresses, phone numbers, or other PII fields. The document contains internal financial and payroll details, but no personal identifiers that would classify it as containing PII. Therefore, no columns can be mapped to PII fields.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA10.csv
0 rows

File structure

Notes: This file is a Swiss payroll document in German. It contains free-form text with no consistent delimiter structure across lines. The content appears to be a manual payroll statement with fields like name, address, AHV number, personal number, date, month, salary components, and deductions. There are no structured columns to map; instead, this is a free-text document that would require unstructured text processing for any embedded PII extraction.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA11.csv
0 rows

File structure

Notes: This is a free-form text file representing a Swiss payroll statement for Peter Brunner. It contains no consistent columnar structure or delimiter; instead, it's a narrative document with embedded personal identifiers like name (Peter Brunner), address (Pfäffikerstrasse 6, 8604 Volketswil), and AHV number (0). Due to the unstructured nature of the file, no column mapping is possible. The document itself should be processed through unstructured text analysis for PII extraction.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA12.csv
0 rows

File structure

Notes: This is a free-form structured document (payroll slip) with no consistent delimiter pattern across rows. While it contains personal identifiers like name (Peter Brunner), address (Pfäffikerstrasse 6), and date of birth (implied by AHV number), the data is presented in a tabular prose format rather than a delimited CSV or similar structured format. The breach context describes internal corporate financial records, but this particular file appears to be a human-readable payroll document rather than machine-parsable structured data. Therefore it should be processed as unstructured text for embedded PII extraction.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA13.csv
0 rows

File structure

Notes: This is an unstructured pay stub document in German with no consistent columnar format. The file appears to be a free-form text representation of a Swiss payroll record, showing salary calculations, tax withholdings, and year-end totals. While it contains personal data (names, AHV insurance number, address), the layout lacks any consistent delimiter or field positions across rows — each line represents a different payroll concept or calculation rather than repeating structured records. Per rules, unstructured files with no consistent columnar pattern must return an empty columns object.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA14.csv
0 rows

File structure

Notes: This is a free-form payroll document in German with no consistent columnar structure. It contains employee name (Peter Brunner), address (Pfäffikerstrasse 6, 8604 Volketswil), and Swiss social security number (AHV-Abr.Nr.: 0, Personal-Nr.: 14). Though it contains PII, the format does not conform to a delimited structure with repeating rows — every line has unique content and variable length. Per rules, unstructured files with embedded PII must be routed through streaming extraction.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA15.csv
0 rows

File structure

Notes: This file is a free-form text document containing Swiss payroll data in German. It has no consistent columnar structure or delimiter; instead, it displays a table-like layout with merged cells and headers spanning multiple lines. The content appears to be a single payroll statement for an individual (Peter Brunner) from January 2002, formatted as a printed document rather than structured data. There are no identifiable PII fields in a machine-readable format — names appear only as free text in the header section.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA16.csv
0 rows

File structure

Notes: This is a free-form payroll document with no consistent delimiter structure. It contains Swiss employee compensation data in German format, but lacks any structured columnar format. Contains personal names (Pfäffikerstrasse 6 address and Herrn title) and Swiss AHV number (social security equivalent), but these are embedded in free text rather than in a tabular format.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA17.csv
0 rows

File structure

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

Notes: This is a Swiss payroll document in German. It contains structured columns but no identifiable PII fields (names, emails, etc.). All visible fields are internal accounting codes, amounts, and Swiss labor law terms. No personal identifiers present in first 50 rows.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA18.csv
0 rows

File structure

Notes: This is a free-form payroll document in German with no consistent columnar structure. It contains Swiss labor records (names, AHV social security number, personal number) but lacks a repeatable row pattern with shared delimiters. The document shows salary calculations for a single employee with no repeating field positions.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA19.csv
0 rows

File structure

Notes: This is a free-form structured text file (Swiss payroll document) with no consistent columnar format. It contains personal employee data including name (Pfäffikerstrasse 6 suggests an address), AHV insurance number (0), and payroll information, but lacks a repeating tabular structure across rows. Per rules, unstructured files with no consistent delimiter and varying line shapes must return empty columns object.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA2.csv
0 rows

File structure

Notes: This is a free-form payroll document in German with no consistent columnar structure. It contains employee names, addresses, Swiss social security numbers (AHV-Abr.Nr.), and payroll data, but lacks a repeatable delimited format across rows. The content appears to be a printed payroll statement rather than machine-readable tabular data.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA20.csv
0 rows

File structure

Notes: This is a free-form payroll document in German with no consistent columnar structure. It contains employee names (Pfäffikerstrasse 6 appears to be an address), dates, and payroll calculations, but lacks a repeatable delimiter or header. The content appears to be a printed payroll statement rather than structured data rows.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA21.csv
0 rows

File structure

Notes: This is a free-form text file representing a Swiss payroll document with no consistent columnar structure. It contains personal identifiers (name, address) and Swiss social security number (AHV-Abr.Nr.), but lacks a repeating tabular format with consistent delimiters and field positions across rows. The content appears to be a manually-generated document rather than a data export.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA22.csv
0 rows

File structure

Notes: This is a free-form Swiss payroll document in German with no consistent columnar structure. It contains employee names and addresses but lacks repeated patterns across rows. The data appears to be a single payroll statement rather than a tabular dataset with repeated records.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA23.csv
0 rows

File structure

Notes: This is a free-form payroll document with no consistent columnar structure. Contains embedded names (Pfäffikerstrasse 6, Herrn) but lacks any repeating structured format across rows. The data is unstructured Swiss payroll accounting with no delimited fields.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA3.csv
0 rows

File structure

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

Notes: This is a free-form text file containing Swiss payroll records with no consistent columnar structure. It includes personal data embedded in text lines such as names and Swiss social security numbers (AHV-Abr.Nr.), but lacks a fixed delimiter or row pattern. The format is unstructured with varying line structures and no true header. Per the unstructured opt-out rules, we return an empty columns object.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA4.csv
0 rows

File structure

Notes: This is a free-form payroll document (German Lohnabrechnung) showing employee name, address, and salary calculations. No consistent tabular structure exists across lines — it's a narrative financial statement with embedded personal data. Contains PII in free text: full name 'Peter Brunner', Swiss address 'Pfäffikerstrasse 6, 8604 Volketswil', and employee number '4'. Routed to unstructured processing for extraction of emails/phones (none visible in sample).

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA5.csv
0 rows

File structure

Notes: This is a free-form structured document (payroll ledger) with no consistent columnar format across lines. The data contains personal identifiers such as names and Swiss AHV insurance number, but lacks a repeated tabular structure with consistent delimiters or column positions. The format is a multi-line payroll statement with mixed header and data lines, making it unstructured for columnar mapping purposes.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA6.csv
0 rows

File structure

Notes: The provided data appears to be a free-form payroll document rather than a structured dataset. It contains unstructured text describing a Swiss payroll calculation for an individual. There are no consistent columns or repeating patterns across rows, and the data is presented as prose with key-value pairs and tabular data embedded in text. This format does not lend itself to structured column mapping for PII fields.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA7.csv
0 rows

File structure

Notes: This is a free-form text file containing payroll information. There is no consistent delimiter or structured column format across rows; instead, it appears to be a printed document with fields interleaved with descriptive text. While it contains personal employee data (names, address, AHV number), the format does not allow for column mapping. It meets unstructured criteria: (a) no consistent delimiter, (b) lines have different shapes, (c) contains personal data. This should be routed through unstructured processing for extraction of names, addresses, and AHV numbers.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA8.csv
0 rows

File structure

Notes: This is a free-form payroll document in German with no consistent columnar structure. It contains salary lines, tax codes, and employee names (e.g., 'Peter Brunner') but lacks a stable delimiter or header. Though it contains personal data, the unstructured format requires routing through a streaming PII extractor.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LA9.csv
0 rows

File structure

Notes: This is an unstructured payroll document in German (Swiss context). No consistent columnar structure exists; it is a free-form table with no repeated header row and variable field positions across rows. Contains employee names (Herrn) and Swiss social security numbers (AHV-Abr.Nr., Personal-Nr.). While PII is present, the format lacks consistent columns, so unstructured handling is appropriate.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__LAW.csv
0 rows

File structure

Notes: This is a Swiss payroll document template with German text. No structured columns exist to map to PII fields. The content appears to be instructional text for completing tax forms rather than actual records containing personal data. This should be processed as unstructured document content.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__MusterLA.csv
0 rows

File structure

Notes: The file is a free-form text document containing a payroll statement in German with no consistent columnar structure. It shows employee data and calculations but lacks repeating fields or a fixed delimiter pattern. Contains PII-like values (names, address, AHV number, etc.) embedded in prose, so it qualifies as unstructured with embedded PII requiring streaming extraction.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__Musterloko.csv
0 rows

File structure

Notes: This file is a Swiss payroll accounting sheet (Lohnkontoblatt) in German with no consistent delimited structure. Rows contain mixed metadata labels, employee personal data, and monthly accounting entries with highly variable column counts and content. Headers and values are interspersed across lines rather than in a structured row-column format. Contains embedded PII (names, phone, DOB, gender, address, AHV/SSN reference) scattered throughout unstructured text. Recommend streaming extraction of names, phone numbers, dates, and addresses rather than column mapping.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__RekapMonat.csv
0 rows

File structure

Notes: This is an unstructured file containing free-form text with no consistent delimiter or row structure. The sample shows lines with varying content and no repeating column pattern. While there are some values that could be interpreted as addresses (e.g., 'Pfäffikerstrasse 6', '8604 Volketswil'), the data lacks a consistent columnar structure required for mapping. The content appears to be a mix of financial records, dates, and textual descriptions without a fixed schema.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__SuvaAb.csv
0 rows

File structure

Notes: This is not a structured dataset. The sample shows free-form text with no consistent delimiter or column structure. Lines contain mixed data such as names, addresses, and numerical values, but they do not follow a tabular format. Therefore, this file should be processed as unstructured text.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__Total.csv
0 rows

File structure

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

Notes: The provided data appears to be a free-form structured document with no consistent columnar layout or delimiter. It contains internal corporate financial records and internal codes rather than personal PII fields. No identifiable PII columns are present.

finanzen__LOBU__LOBU_Mahler__LOKO_neu__Verg.csv
4 columns37 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] appears to be full names like 'Peter Brunner Treuandbüro'
3address1high[3] contains street addresses like 'Pfäffikerstrasse 6'
4cityhigh[4] contains city names like 'Volketswil'
5ziphigh[5] contains postal codes like '8604'

Notes: This appears to be a payment voucher / remittance advice document in German. Columns 0-5 contain full name, street address, city, postal code, and bank information. No emails, phones, DOB, SSN, or usernames are visible in the first 50 rows. The document is structured as a CSV but lacks a proper header row; fields are inferred from position and sample values.

finanzen__LOBU__LOBU_Mahler__pwd.txt
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__LOBU__LOBU_Mahler__replacement__replacement.csv
0 rows

File structure

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

Notes: No PII columns identified. The file contains only numeric substitution patterns (sReplace operations) with no personal or sensitive data fields. All columns appear to be internal transformation rules rather than actual PII-containing records.

finanzen__LOBU__Lohnkosten__Lohnkalkulation__Fhz_02.csv
0 rows

File structure

Notes: This is not a structured data file with columns. The content appears to be a free-form text document describing vehicle-related financial data (fuel, insurance, repairs, leasing) for the year 2002, formatted as a table with no consistent columnar structure across rows. There are no identifiable PII fields or structured columns to map.

finanzen__LOBU__Lohnkosten__Lohnkalkulation__Fhz_03.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; appears to be financial breakdown of vehicles (2003) with German descriptions and numeric values in CHF; no PII columns present

finanzen__LOBU__Lohnkosten__Lohnkalkulation__Fhz_04.csv
0 rows

File structure

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

Notes: This is not a PII file. It contains vehicle expense data (fuel, insurance, repairs, leasing) with numeric values in Swiss Francs (CHF). No personal or identifiable information is present. Columns are purely financial aggregates without any names, addresses, or other PII fields.

finanzen__LOBU__Lohnkosten__Lohnkalkulation__Fhz_05.csv
0 rows

File structure

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

Notes: This is not structured PII data. The file appears to be a financial summary in German for vehicles (Fahrzeuge) from 2005, showing fuel, insurance, maintenance, leasing costs, and totals across three categories (MB, ML, DP). No personal identifiable information (PII) is present. All columns represent aggregated financial figures and are skipped per rules.

finanzen__LOBU__Lohnkosten__Lohnkalkulation__Fhz_06.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a financial summary table in German with no personal identifiers

finanzen__LOBU__Lohnkosten__Lohnkalkulation__Fhz_07.csv
0 rows

File structure

Notes: free-form text with no consistent column structure - appears to be financial statements/projections with no personal identifiers visible in sample

finanzen__LOBU__Lohnkosten__Lohnkalkulation__Fhz_08.csv
0 rows

File structure

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

Notes: This is an unstructured financial report table with no personal identifiable information (PII). Columns represent vehicle categories and financial figures in CHF, not personal data fields. No emails, phone numbers, names, or other PII present in the visible rows.

finanzen__LOBU__Lohnkosten__Lohnkalkulation__Fhz_09.csv
0 rows

File structure

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

Notes: This is an unstructured financial summary table with no personal identifiable information. Columns contain aggregated vehicle-related financial data (fuel, insurance, maintenance) with no names, addresses, or other PII fields. All values are monetary totals in CHF for different categories (MB, ML, DP) with no individual customer identifiers.

finanzen__LOBU__Lohnkosten__Lohnkalkulation__Uebersicht.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. It contains salary and vehicle cost data in Swiss Francs (CHF) for years 2002-2009, organized in tables but without named headers or repeated delimiters. The content is purely financial records and contains no personal identifiable information (PII).

finanzen__LOBU__Zeitkontrolle_czimmer__2024.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; contains time tracking data in a tabular format but lacks headers and shows a grid of numerical values with month labels and categories like 'Ferien', 'Arbeitszeit', etc. Not a CSV with PII columns.

finanzen__LOBU__Zeitkontrolle_czimmer__2025.csv
1 column0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] headerless column contains 'Claudia Zimmer' — clearly a full name

Notes: Only column 0 contains PII (full name). All other columns appear to be numeric time tracking data (hours, days, percentages) with no personal identifiers. No emails, phones, addresses, or other PII fields detected in the first 50 rows.

finanzen__LOBU__Zeitkontrolle_czimmer__2026.csv
0 rows

File structure

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

Notes: This is a structured time-tracking/attendance file with no personal identifiable information (PII) fields. Contains employee time data, attendance codes, and working hours metrics, but no names, contact details, or other PII. The first row contains an employee name 'Claudia Zimmer', but this appears to be a header label rather than actual data, and subsequent rows contain only numerical/time data and attendance codes. No columns map to any PII fields from the provided list.

finanzen__LOBU__Zeitkontrolle_czimmer_alt__2024.csv
0 rows

File structure

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

Notes: This is a structured timesheet/attendance file showing workdays, holidays, sick days, and other leave categories. No PII fields (names, emails, addresses, etc.) are present. The file only contains employee name 'Claudia Zimmer' in the first row which appears to be a header or title rather than structured data. All other rows contain numeric values representing working days, leave days, and percentages. There are no columns mapping to any PII fields from the provided list.

finanzen__LOBU__Zeitkontrolle_czimmer_alt__2025.csv
0 rows

File structure

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

Notes: This file contains only structured time-tracking data with employee attendance codes and numeric values. No PII fields (names, emails, addresses, etc.) are present. The first row contains a name 'Claudia Zimmer', but this is not part of a consistent columnar structure and appears to be a standalone entry rather than a column header/value. The rest of the data consists of numeric time values and day codes (Sa, So) with categories like 'Ferien', 'Krankheit', etc. No columns map to PII fields per the rules.

finanzen__LOBU__Zeitkontrolle_drosso__2022.csv
0 rows

File structure

Notes: This is a time-tracking / payroll schedule with no personal identifying information (PII). Columns represent dates, work days, and time calculations (e.g., 'Ist Monat', 'Soll Stunden 100%'). No emails, phone numbers, names, or addresses appear. The single entry 'Daniel Rosso' appears to be a filename or document title, not a structured record. All columns map to skip categories (timestamps, counters, internal flags).

finanzen__LOBU__Zeitkontrolle_drosso__2023.csv
0 rows

File structure

Notes: The file appears to be a time-tracking or payroll document in German with no consistent columnar structure. It contains free-form text and tabular data mixed together without a fixed delimiter or header row. Values represent days, hours, and various work-related categories rather than personal identifiable information (PII).

finanzen__LOBU__Zeitkontrolle_drosso__2024.csv
0 rows

File structure

Notes: The file is a time-tracking or payroll report with no consistent column structure. It contains free-form text with embedded employee names and time data, but lacks a repeated delimiter pattern across rows. The first line appears to be a headerless record, and subsequent lines mix numerical data with German month abbreviations and day indicators (Sa, So), making it unstructured. Contains personal names like 'Daniel Rosso' but lacks structured columns to map to PII fields.

finanzen__LOBU__Zeitkontrolle_drosso__2025.csv
0 rows

File structure

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

Notes: The provided data is a structured time-tracking or attendance record for an employee named Daniel Rosso at Zynex. It contains no identifiable PII fields such as names, addresses, emails, phone numbers, DOB, SSN, etc. All columns appear to represent internal tracking metrics (e.g., vacation days, working hours, absence types) and numerical values. Therefore, no PII columns are present.

finanzen__LOBU__Zeitkontrolle_mbrunner__2022.csv
1 column0 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header-less column, but row 1 value 'Mark Brunner' is a full name

Notes: Only column 0 contains PII (fullName). All other columns are numeric time-tracking data, day names (Sa/So), or percentage values — no email/phone/address/SSN/DOB patterns observed. The file appears to be a Swiss employee time-tracking sheet in German, with no additional PII beyond the name in column 0.

finanzen__LOBU__Zeitkontrolle_mbrunner__2023.csv
2 columns21 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighempty column header
1fullNamehigh[1] header 'Zeiterfassung' is ambiguous but row 1 value 'Mark Brunner' is a full name

Notes: File appears to be a Swiss employee timesheet system. Only column 1 contains PII (full name). All other columns are numeric values, dates, or empty headers representing work hours categories. No emails, addresses, phones, or other PII detected.

finanzen__LOBU__Zeitkontrolle_mbrunner__2024.csv
2 columns21 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphigh[0] column header is blank, values are numeric counters and labels
1fullNamehigh[1] header is blank but first row value 'Mark Brunner' is a full name

Notes: File appears to be a Swiss employee timesheet/attendance report in German. Only column 1 contains PII (full name). All other columns are numeric counters, day labels, and attendance codes (e.g., 'Sa' for Saturday, 'So' for Sunday). No email, phone, address, or other PII fields detected beyond the name in column 1.

finanzen__LOBU__Zeitkontrolle_mbrunner__2025.csv
2 columns20 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphighcolumn contains only delimiters and empty values; no PII
1fullNamehighcolumn contains full name 'Mark Brunner' in first row

Notes: File appears to be a Swiss time-tracking/attendance report in German with no PII beyond a single full name in the header row. All other columns contain numeric time values, day abbreviations (Sa=Saturday, So=Sunday), and internal codes - no emails, phones, addresses, or other PII detected.

finanzen__LOBU__Zeitkontrolle_mleisi__2022.csv
0 rows

File structure

Notes: The file is free-form text with no consistent delimiter structure. It appears to be a Swiss time-tracking or payroll document with no identifiable PII columns. Values contain only numerical time entries, day abbreviations (Sa/So), and employee codes. No emails, phone numbers, or personal names are visible in the sample.

finanzen__LOBU__Zeitkontrolle_mleisi__2023.csv
0 rows

File structure

Notes: This is free-form text with no consistent columnar structure. The data appears to be a time-tracking or attendance report with no identifiable PII fields (names, emails, addresses, etc.). While there is a name 'Martin Leisi' present, it is embedded in prose and the file lacks any consistent delimiter or row structure across lines. All rows have varying formats and content shapes, failing the structured data criteria. Per rules, unstructured files with no column structure must return an empty columns object.

finanzen__LOBU__Zeitkontrolle_mleisi__2024.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The data appears to be a Swiss timesheet/attendance record for Martin Leisi from Zynex, showing monthly working hours, holidays, sick days, etc. Though it contains personal data (name), the format is unstructured with no columns to map.

finanzen__LOBU__Zeitkontrolle_mleisi__2025.csv
0 rows

File structure

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

Notes: This file contains purely internal corporate time-tracking and financial data with no personal identifiable information (PII). All columns represent work hours, absence types, and financial calculations without any names, contact details, or other PII fields. The entries are structured around employee time tracking codes and monetary values, not individual identities.

finanzen__LOBU__Zeitkontrolle_pwindhofer__2022.csv
0 rows

File structure

Notes: The provided data is a free-form time tracking / attendance schedule in German, not a structured CSV with identifiable PII columns. It contains employee names (Peter Windhofer), months (Jan, Feb...), and attendance codes (Sa=Saturday, So=Sunday), but no emails, phone numbers, addresses, DOB, SSN, etc. The format lacks consistent delimiters and column structure required for mapping; it's a narrative-style schedule with no repeating columnar pattern across rows.

finanzen__LOBU__Zeitkontrolle_pwindhofer__2023.csv
0 rows

File structure

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

Notes: This is a structured timesheet/attendance file with no PII fields. Contains only employee attendance data, month names, working days, and absence types. No columns map to PII fields (email, phone, name, etc.).

finanzen__LOBU__Zeitkontrolle_pwindhofer__2024.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure; contains employee attendance/leave records in German with no identifiable PII fields

finanzen__LOBU__Zeitkontrolle_pwindhofer__2025.csv
0 rows

File structure

Notes: This is a time-tracking or attendance file with no identifiable personal information. Contains only employee absence codes, day-of-week indicators (Sa/So), and numerical working-hour data. No PII fields present.

finanzen__LOBU__lohnkalkulation_2016__Tabelle1.csv
0 rows

File structure

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

Notes: This is not a PII file. It contains only financial data (numbers, names of employees/bonus amounts) with no personal identifiers like email, phone, address, etc. The names appear to be employee names (Leisi, Brunner) but are not mapped as PII because the context indicates this is internal corporate financial data, not customer data. No PII fields are present.

finanzen__LOBU__ueberstunden_feriensaldo___berst_2022.csv
0 rows

File structure

Notes: This is free-form text with no consistent column structure. The sample rows contain unstructured data and do not represent a tabular format with defined columns. The content appears to be internal corporate records with no identifiable PII fields in a structured format.

finanzen__LOBU__ueberstunden_feriensaldo___berstd_2020.csv
0 rows

File structure

Notes: The provided data is free-form text with no consistent column structure. The sample shows unstructured financial and employee records with mixed content, headers, and values. There are no identifiable PII columns in a structured format. However, names like 'Brunner Mark' and 'Leisi Martin' appear, indicating potential PII in unstructured content.

finanzen__LOBU__ueberstunden_feriensaldo___berstd_2021.csv
0 rows

File structure

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

Notes: This file is structured but contains only internal corporate financial records (overtime, salaries, year-end balances) with no personal PII. Columns 0 and 14 contain company names and financial period labels, not personal data. All other columns are numeric financial figures or internal codes. No email, phone, name, address, or other PII fields are present.

finanzen__LOBU__ueberstunden_feriensaldo___berstd_2023.csv
0 rows

File structure

Notes: This is unstructured data with no consistent columnar format. The file appears to be a mix of financial and employment records from Zynex AG, with free-form text lines and no clear delimiter separating fields. The sample shows headers and values interleaved in a non-tabular format. While names appear (e.g., "Brunner Mark", "Leisi Martin"), they are embedded in free-text lines without a repeating structure, meeting the unstructured opt-out criteria (a), (b), and (c).

finanzen__LOBU__ueberstunden_feriensaldo___berstd_2024.csv
0 rows

File structure

Notes: This is unstructured data with no consistent column mapping. The file appears to be a financial report or internal corporate document from Zynex AG, containing employee names and payroll data. There are no consistent columns or headers to map to PII fields. However, the names 'Brunner Mark' and 'Leisi Martin' appear in the data, but without a consistent structure, we cannot reliably extract PII columns.

finanzen__LOBU__ueberstunden_feriensaldo___berstd_2025.csv
0 rows

File structure

Notes: This is not a structured dataset; it appears to be free-form text/prose lines with no consistent delimiter or column structure. The sample shows unstructured financial/procedural notes from Zynex AG with no identifiable PII fields in a tabular format. Per rules, we treat this as unstructured content with no column mapping.

finanzen__LOBU__zeitkontrolle_alt__Zeitkontrolle_Vorlage__2022.csv
1 column12 rows

File structure

Source columnMapped fieldConfidenceLLM assessment
3fullNamehigh[3] column contains personal names in rows like 'Name'

Notes: This file appears to be a structured attendance/tracking spreadsheet with no PII beyond names. Column 3 maps to fullName based on values like 'Name' and other rows containing personal names. All other columns represent dates, codes, and numerical values (hours, days of week, etc.) that do not contain PII.

finanzen__LOBU__zeitkontrolle_alt__Zeitkontrolle_Vorlage__2023.csv
2 columns11 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
0skiphigh[0] column name 'Zeiterfassung' and values indicate internal tracking codes, not PII
3fullNamehigh[3] column name 'Name', values appear to be personal names in German format

Notes: This appears to be a time tracking/attendance CSV from Zynex's internal HR system. Column 3 contains employee names which qualify as PII (fullName). Other columns contain internal tracking codes, month abbreviations, and numeric counters which are not personally identifiable information per the exclusion rules. No email addresses, phone numbers, or other PII fields are present in the visible data.

finanzen__LOBU__zeitkontrolle_alt__Zeitkontrolle_kwellinger__2022.csv
1 column0 rows

File structure

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] contains full name 'Katrin Wellinger', headerless but value matches fullName pattern

Notes: File appears to be a structured timesheet/CSV with hidden headers. Column 0 contains a full name (Katrin Wellinger). All other columns contain numeric time tracking data and day labels (Sa/So = Saturday/Sunday), which are skip fields per rules. No other PII fields detected in the first 50 rows.

finanzen__LOBU__zeitkontrolle_alt__Zeitkontrolle_kwellinger__2023.csv
0 rows

File structure

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

Notes: This is a time-tracking/attendance file with no PII columns. Contains employee name (line 1), month names, numeric values for hours, and various attendance categories (e.g., normal work time, vacation, sick leave). No email, phone, address, SSN, or other PII fields present. The name 'Katrin Wellinger' is not mapped because standalone names without identifiers in structured data are not considered PII in this context (no email/phone/SSN linked).

finanzen__LOBU__zeitkontrolle_alt__Zeitkontrolle_rwellinger__2022.csv
0 rows

File structure

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

Notes: This is a time-tracking and leave management record file, not a breach of personal PII. It contains employee absence tracking (vacation, sick days, etc.) and working hour calculations with no identifiable personal data. All rows are structured time-tracking entries with no emails, phone numbers, or other PII present.

finanzen__LOBU__zeitkontrolle_alt__Zeitkontrolle_rwellinger__2023.csv
0 rows

File structure

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

Notes: This file is a structured timesheet/attendance record with no personal identifiable information (PII) fields. Columns contain dates, numerical values for hours, status codes (e.g., 'Sa' for Saturday, 'So' for Sunday), and employee status categories (e.g., 'Ferien', 'Krankheit'). There are no email addresses, phone numbers, names, or other PII fields present. The only textual values are day abbreviations and status labels, which do not constitute PII.

finanzen___div_old__bierkasse__Tabelle1.csv
0 rows

File structure

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

Notes: This is a financial ledger in CSV format with no PII columns. Columns represent transaction dates, payees, purposes, amounts, and balances — all business/transactional data. No names, emails, addresses, or other personal identifiers appear.

finanzen___div_old__informatikaufwand_2003__Abr_iRC2105_Mrz_2003.csv
0 rows

File structure

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

Notes: This file contains purely financial/transactional data with no PII. Columns represent groups, years, months, formats, media types, color specifications, and monetary totals. No personal identifiers (names, emails, addresses, etc.) are present.

finanzen___div_old__informatikaufwand_2003__Abrechnung_iRC2105.csv
0 rows

File structure

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

Notes: This is a financial record file showing internal corporate accounting data for Zynex. No personal identifiable information (PII) fields are present. Columns contain accounting periods, cost figures, percentages, and totals in CHF. All columns are financial metrics or internal identifiers, none map to PII fields (email, phone, name, address, etc.).

finanzen___div_old__informatikaufwand_2003__Informatikaufwand.csv
0 rows

File structure

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

Notes: This file is purely financial accounting data with no PII present. Columns contain only transaction descriptions and monetary values without any personal identifiers.

finanzen___div_old__informatikaufwand_2003__Leasing_iRC2105.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or structure; appears to be financial summary lines rather than tabular data with columns

finanzen___div_old__informatikaufwand__2004.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure; appears to be financial ledger entries with no identifiable PII columns

finanzen___div_old__informatikaufwand__2007.csv
0 rows

File structure

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

Notes: This is an unstructured financial/procurement document in German showing annual hardware and internet costs for Zynex AG. No personal or customer data is visible — only internal corporate accounting lines with itemized expenses, totals, and estimates. No PII columns exist.

finanzen___div_old__informatikaufwand__2010.csv
0 rows

File structure

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

Notes: This file contains purely financial/inventory records with no personal identifiers. It shows hardware purchases, cost estimates, and maintenance budgets for Zynex AG from 2002-2010. No PII fields are present — all columns represent internal business data (equipment names, costs, years, calculations).

finanzen___div_old__informatikaufwand__2012.csv
0 rows

File structure

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

Notes: This file contains purely financial and operational data with no identifiable personal information. All entries represent corporate expenses, projections, and resource allocations without any personal identifiers such as names, addresses, or contact details.

finanzen___div_old__informatikaufwand__ESX.csv
0 rows

File structure

Notes: This file is purely technical infrastructure cost documentation. Contains server hardware specs, power consumption, maintenance costs, and operational expenses. No PII fields (names, addresses, emails, etc.) are present. The structure is tabular but all values are numeric measurements and technical descriptors, not personal data.

finanzen___div_old__informatikaufwand__ESX__64_GB_.csv
0 rows

File structure

Notes: This file is purely technical infrastructure and cost data. No personal identifiers (PII) are present. It contains server specifications, power consumption metrics, maintenance costs, and financial breakdowns — all corporate operational data without any customer or employee details. The structure is free-form tabular data without consistent column headers or identifiable fields.

finanzen___div_old__informatikaufwand__ESX__Ontrex_.csv
0 rows

File structure

Notes: This is a free-form table-like document in German showing infrastructure costs and operational expenses for Zynex. There are no consistent columns or delimiters across rows — it's a formatted report with merged cells and empty lines. No PII present.

finanzen___div_old__inventar_2013__Inventar_2013.csv
0 rows

File structure

Notes: This is an inventory document for Zynex AG from 2013, listing office equipment and assets. There are no structured columns or PII fields; it contains only item descriptions and monetary values.

finanzen___div_old__preisliste-zynex-2006__Tabelle2.csv
0 rows

File structure

Notes: This is a pricing list document with no identifiable personal information. It contains only product names, license prices, and monthly costs. There are no columns or structured data containing PII fields.

finanzen___div_old__stuka_allianz__Tabelle1.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The data appears to be financial figures (possibly premiums or contributions) in a tabular-like format but lacks headers, consistent delimiters, and row structure. There are no visible emails, phone numbers, or other PII in the sample lines provided. Since there is no consistent delimiter or column structure, this is classified as unstructured text.

finanzen__abrechnungen__2014__telefon_tb_2014__Page_1.csv
0 rows

File structure

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

Notes: This file appears to be a telecommunications billing report showing monthly call statistics and costs. It contains only business transaction data (month, number of connections, data volume, duration, amount, and connection ID). There are no personal identifiable information (PII) fields present such as names, addresses, phone numbers, emails, or dates of birth. All columns represent aggregated business metrics and financial totals.

finanzen__abrechnungen_ausdrucke__Abrechnung_drucke_harmonie__Druckpreise.csv
0 rows

File structure

Notes: This is a free-form table with pricing tiers and booklet surcharge data, no personal identifiers present. No consistent column structure exists across rows.

finanzen__abrechnungen_ausdrucke__Abrechnung_drucke_harmonie__Offerte.csv
0 rows

File structure

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

Notes: This is an unstructured financial record with no personal identifiers. The file contains only pricing tiers, quantities, and monetary values related to printing services. No PII fields are present in the first 50 rows.

finanzen__abrechnungen_ausdrucke__Abrechnung_drucke_harmonie__Papierpreise.csv
0 rows

File structure

Notes: This is a free-form structured data file with no consistent delimiter or column structure. The content appears to be a tabular listing of paper product specifications and pricing, but it lacks a consistent delimiter or header row. The rows show product descriptions, formats, weights, and pricing values, but there is no identifiable PII present. The format does not conform to CSV/TSV expectations due to inconsistent delimiters and mixed content patterns across lines.

finanzen__dauerakten__AKTBUCH_2003__Tabelle1.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent column structure. It contains unstructured corporate records in German with entries like 'Aktienbuch' (share register), names, locations, and transaction details, but lacks a fixed delimiter or repeated column pattern across rows. This matches the description of internal corporate data files from Zynex which often use free-form formats for financial and shareholder records.

finanzen__dauerakten__AKTBUCH_2006__Tabelle1.csv
0 rows

File structure

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

Notes: This is unstructured corporate shareholder registry data from Zynex AG. Columns contain Swiss corporate legal references (Aktienbuch entries, share numbers, nominal values) and shareholder transfer records. No personal PII fields are present — names appear to be formal representations (Urs W. Käppeli) but are used as corporate shareholder identifiers rather than personal contact info. All columns map to corporate/financial metadata per breach context (Swiss SME hosting customers, FaktNT ERP billing). No email, phone, DOB, SSN, or address fields detected.

finanzen__dauerakten__AKTBUCH__Tabelle1.csv
0 rows

File structure

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

Notes: This is a free-form structured file with no consistent column headers or delimiter pattern. The data appears to be a formatted corporate share registry or stock ledger from Zynex AG, containing rows with mixed textual and tabular data. No clear PII columns are identifiable due to the unstructured nature of the data. The content shows entries like 'Name, Vorname' (Name, First name) and 'Wohnort' (Residence), but these appear in free-form text rows rather than fixed columns. Given the lack of a consistent columnar structure, this file should be processed as unstructured text for any potential PII extraction.

finanzen__dauerakten__mwst-login.txt
0 rows

File structure

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

Notes: File content is unstructured prose text describing a data breach (German language context, URLs, license keys, administrative references) with no consistent delimited columns or row structure. NOT a structured data file containing PII records. No importable PII columns detected.

finanzen__dauerakten__pwindhofer-iban.txt
0 rows

File structure

Notes: This is free-form financial data with no consistent column structure. The file appears to be a raw dump of accounting entries showing account numbers, balances, IBANs, and bank names. There are no identifiable PII fields in a structured format, and the data does not contain repeated patterns of emails, phone numbers, or other PII in free-text fields. The format is unstructured financial records rather than a CSV or tabular dataset.

finanzen__dta_files__2001__logfiles__011211.log.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a financial statement/protocol document with transaction records, not structured tabular data containing PII columns

finanzen__dta_files__2008__Logfiles__080116.DTA.LOG.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. The data consists of transaction lines with fields like OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total, but these appear inconsistently across rows and lack a stable delimiter pattern. The file contains no identifiable PII fields such as email, phone, or address. It is purely transactional financial data from Zynex's internal records.

finanzen__dta_files__2008__Logfiles__080225.dta.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent column structure. The data consists of raw tabular text with transaction lines but lacks headers or a stable delimiter pattern across rows. While it contains business names (SWITC, SWISS, ECOME, etc.), these are company names and not personal PII. No personal PII fields are present in a structured format. The document is a protocol/report from Zynex showing payments to various entities (likely customers or vendors), dated 25.02.2008.

finanzen__dta_files__2008__Logfiles__080327.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. The data appears to be a printed accounting protocol showing transaction records with fields like OP-Nr (operation number), Valuta (date), PK-Nr (customer/account number), Name (customer name), ZL (zone/location), Betrag (amount), and Total. There are no repeated email addresses, phone numbers, or other PII in the visible lines. The format does not contain any structured columns that could be mapped to PII fields.

finanzen__dta_files__2008__Logfiles__080505_02.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol/report document with no column structure. It shows transaction records with OP-Nr., Valuta dates, PK-Nr., names (SWITC, SWISS, ECOME, etc.), and monetary amounts in CHF. There are no identifiable PII fields like email, phone, or address, and the format lacks consistent delimiters or headers. The names appear to be business/client codes rather than personal names.

finanzen__dta_files__2008__Logfiles__080604.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction lines with codes, dates, and amounts, but no identifiable personal information or repeated field patterns. The document appears to be a payment protocol from Zynex's internal financial records, showing line items with codes (OP-Nr.), dates, reference numbers (PK-Nr.), entity names (e.g., SWITC, SWISS, EIDG.), currency codes (CHF), and amounts. There are no emails, phone numbers, or other PII visible in the sample.

finanzen__dta_files__2008__Logfiles__080630.log.csv
0 rows

File structure

Notes: The provided text is a financial transaction report/protcol from Zynex with no column structure or identifiable PII fields. It contains only transaction codes, amounts, and totals without any personal or contact information. The format is free-form text with tabular data presented in a report style, not a delimited structured file.

finanzen__dta_files__2008__Logfiles__080711.log.csv
0 rows

File structure

Notes: This is a free-form financial report document with no consistent columnar structure. It contains transaction lines with reference numbers, dates, names, and amounts, but lacks a repeated delimiter pattern across rows. The content appears to be a printed protocol/report rather than structured tabular data.

finanzen__dta_files__2008__Logfiles__080805.log.csv
0 rows

File structure

Notes: The file is a free-form financial protocol/proforma document with no consistent columnar structure. It contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total columns, but these are not consistently delimited across rows and appear to be part of a narrative financial report rather than a structured dataset. The content shows payment records for various entities (SWITC, SWISS, SHELL, etc.) with amounts in CHF, but lacks any identifiable personal information (PII) such as names, addresses, or contact details beyond generic entity abbreviations. No email or phone numbers are visible. Given the unstructured nature and absence of PII, this is treated as unstructured text.

finanzen__dta_files__2008__Logfiles__080822.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent columnar structure. The file contains line-by-line transaction entries with mixed formats (e.g., OP-Nr., Valuta, PK-Nr., Name, ZL, Betrag, Total), not CSV/TSV. It shows payment records for Swiss SMEs (SWISS, EIDG., ECOME, EKZKT, SHELL, TDCSW, BPSWI) with amounts in CHF. While names appear (e.g., 'SWISS', 'EIDG.'), they are likely entity/customer identifiers rather than personal PII. No structured columns exist to map to PII fields.

finanzen__dta_files__2008__Logfiles__080929.log.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains financial transaction data but no identifiable PII columns. The format is unstructured financial ledger data without column headers or repeating patterns.

finanzen__dta_files__2008__Logfiles__081024.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol document with no consistent column structure. It contains transaction records with company names and amounts, but lacks any structured PII fields like email, phone, or address. The format is not CSV/TSV — it's a formatted text protocol with lines that don't share a consistent delimiter or column pattern across rows. Therefore, we classify it as unstructured for downstream processing.

finanzen__dta_files__2008__Logfiles__081125.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent columnar structure. The document contains transaction lines with OP-Nr., Valuta, PK-Nr., Name, ZL, Betrag, and Total columns, but these are not consistently delimited across rows and appear to be formatted as a table rather than a structured CSV. The content is purely transactional/financial data without any personal identifiable information (PII) fields such as names, addresses, emails, etc. The values shown (SWITC, SWISS, EIDG., ECOME, SHELL, etc.) appear to be business codes or entity abbreviations, not personal names. There are no emails, phone numbers, or other PII visible in the sample. Therefore, this is classified as unstructured text with no PII columns to map.

finanzen__dta_files__2008__Logfiles__081219.log.csv
0 rows

File structure

Notes: free-form text with no consistent columnar structure; contains transaction records with customer codes (SWITC, SVAZÄ, etc.) but no explicit PII fields in structured format. This qualifies as unstructured data per rules.

finanzen__dta_files__2008__Logfiles__081222.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol document (DTA-Protokoll) with no consistent columnar structure. It contains transaction details but no identifiable personal information (PII) fields. The format appears to be a printed accounting report with mixed text and numeric data, not a structured dataset with repeatable columns. The values shown are transaction IDs, dates, amounts, and totals — all internal financial metadata without any personal identifiers.

finanzen__dta_files__2009__log__090108.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol/report with no consistent columnar structure. Contains transaction lines with codes and amounts, but no identifiable PII fields. Matches the description of internal corporate financial records from Zynex breach.

finanzen__dta_files__2009__log__090227.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent column structure. The data contains transaction IDs, dates, reference numbers, customer names (e.g., SWITC, ECOME, NETZM), and monetary values in CHF. There are no identifiable PII fields like email, phone, or address in structured columns, and the format does not meet the criteria for CSV/TSV mapping. The customer names appear to be internal account codes or abbreviations rather than personal names. As per rules, unstructured files with no consistent delimiter and variable line shapes should return empty columns object.

finanzen__dta_files__2009__log__090313.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol document with no consistent columnar structure. It contains transaction records with reference numbers, dates, names, and amounts, but lacks a fixed delimiter or header. While it contains potentially sensitive business names (SWISS, EIDG.), these are not personal PII fields per the defined schema. No structured columns to map.

finanzen__dta_files__2009__log__090331.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction records with names that appear to be company names (SWITC, SVAZ�, SWISS, TREUH, EKZKT, SHELL, TDCSW, LEISI, KANTO, BPSWI, NESTL, CABLE, HIRSC) rather than personal PII. The format is a line-by-line ledger with mixed text and numeric data, not a delimited CSV or TSV. Per rules, unstructured files with no consistent delimiter structure and no personal PII columns should return empty columns object.

finanzen__dta_files__2009__log__090424.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent columnar structure. The file contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total fields, but these are not consistently delimited across rows and appear to be part of a narrative report rather than a structured dataset. There are no identifiable PII fields in this unstructured content.

finanzen__dta_files__2009__log__090511.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. The file contains transaction details (OP-Nr., Valuta, PK-Nr., Name, ZL, Betrag, Total) but lacks a repeated header or consistent delimiter across rows. Values appear to be business references (EIDG., NETSP) rather than personal PII. No structured columns exist to map to PII fields.

finanzen__dta_files__2009__log__090619.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent column structure. It contains transaction details (OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, Total) but lacks a repeated header or delimiter-separated format across rows. The values appear to be business names (SWITC, SVAZ�, SWISS, SHELL, etc.) and monetary amounts, but there is no identifiable PII such as email, phone, or address. Per rules, unstructured files with no consistent column structure return an empty columns object.

finanzen__dta_files__2009__log__090805.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol document (DTA-Protokoll) with no consistent column structure. It contains transaction records with OP-Nr, Valuta dates, PK-Nr, customer names (SWISS, EKZKT, SHELL, etc.), amounts, and totals, but lacks a delimited tabular format. The document appears to be a printed protocol from August 5, 2009, showing payments totaling CHF 28,101.90 across 17 transactions. While it contains customer names, these appear to be company names rather than personal PII. No structured columns to map.

finanzen__dta_files__2009__log__090903.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction lines with company names (SWITC, HANDE, SWISS, etc.) and monetary values, but lacks any personal PII fields like names, emails, or addresses. The data appears to be corporate accounting entries rather than customer or employee records. No structured columns to map.

finanzen__dta_files__2009__log__090930.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no column structure. It contains transaction lines with reference numbers (OP-Nr.), dates, internal codes (PK-Nr.), entity names (Name), amounts, and totals. No personal identifiers (email, phone, address, etc.) are present. The format is a standard corporate accounting document, not structured tabular data with named columns. While it contains business entity names (SWITC, SVAZ�, etc.), these are not personal PII fields per the rules. Therefore, no columns map to PII fields.

finanzen__dta_files__2009__log__091102.log.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains transactional data but no identifiable PII fields

finanzen__dta_files__2009__log__091207.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol/report document with no consistent columnar structure. It contains transaction lines with reference numbers, dates, codes, and amounts, but no identifiable personal information (PII) fields such as names, addresses, emails, or phone numbers. The data appears to be internal corporate accounting records rather than customer PII.

finanzen__dta_files__2010__logfiles__100208.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protокол showing payment records with no consistent columnar structure. The lines contain transaction data (OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, Total) but lack a stable delimiter or header. The values are company/business names (SWITC, SVAZÜ, ECOME, etc.) rather than personal PII. No structured columns exist to map.

finanzen__dta_files__2010__logfiles__100315b.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent columnar structure. Lines contain transaction details like OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total, but there is no repeated header or delimiter pattern. The data appears to be a printed protocol/report rather than structured tabular data. Contains embedded currency values (CHF) and transaction totals, but no identifiable PII fields like names, addresses, or contact info beyond ambiguous business names (SWITC, RUBEA, etc.) which are likely company abbreviations, not personal identifiers.

finanzen__dta_files__2010__logfiles__100323.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no column structure. It contains transaction lines but lacks consistent delimiters or headers. The content appears to be a printed statement with mixed German/ASCII characters and no identifiable PII columns.

finanzen__dta_files__2010__logfiles__100427.log.csv
0 rows

File structure

Notes: This is a free-form financial report document (DTA-Protokoll) with no consistent columnar structure. It contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total columns, but these are not standardized across rows and appear to be part of a narrative financial summary rather than a delimited dataset. The file lacks a consistent delimiter and row structure required for CSV/TSV parsing. While it contains business names (SWITC, SWISS, ECOME, etc.), these are company names and should be skipped per exclusion rules. No PII fields are present in a structured format.

finanzen__dta_files__2010__logfiles__100527.log.csv
0 rows

File structure

Notes: This is free-form financial transaction data with no consistent columnar structure. Lines represent transaction records but lack a fixed delimiter or header. Contains company names (SWITC, SWISS, ECOME, etc.) and monetary values, but no identifiable personal PII fields like email, phone, or address. The format is unstructured prose with tabular-like data embedded, but does not meet criteria for CSV parsing due to inconsistent line structures and lack of repeated columnar patterns.

finanzen__dta_files__2010__logfiles__100603.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol document with no consistent columnar structure. It contains Swiss Franc amounts, dates, and transaction codes but no identifiable personal information. The format is unstructured accounting protocol output, not a delimited dataset with columns.

finanzen__dta_files__2010__logfiles__100624.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol document with no consistent columnar structure. It contains transaction lines with codes, names, and amounts, but lacks a repeating tabular format. The names appear to be business/client identifiers rather than personal PII fields. No structured columns exist to map.

finanzen__dta_files__2010__logfiles__100719.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. It contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total fields, but these are not machine-readable columns — they are part of a narrative table. No PII is present, only company names (SHELL, TDCSW, MARTI, etc.) which are business entities and should be skipped per rules. The file is purely transactional accounting data without personal identifiers.

finanzen__dta_files__2010__logfiles__100831.log.csv
0 rows

File structure

Notes: The provided text is a free-form financial protocol/protokoll document with no consistent column structure. It contains transaction details (OP-Nr., Valuta, PK-Nr., Name, ZL, Betrag, Total) but does not include any personal identifiable information (PII) fields such as email, phone, name, address, etc. The document appears to be an internal corporate financial record with mixed currency transactions, not containing any searchable PII.

finanzen__dta_files__2010__logfiles__100831b.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol document with no consistent columnar structure. It contains transaction details (OP-Nr., Valuta, PK-Nr., Name, ZL, Betrag, Total) but lacks a repeating tabular format across rows. The content appears to be a printed protocol from an accounting system (Zynex FaktNT ERP) showing a single payment record dated 31.08.2010 for CHF 7,351.10 to 'EIDG.' (Swiss Confederation). No PII columns exist in structured format — this is a prose-style financial document.

finanzen__dta_files__2010__logfiles__100924.log.csv
0 rows

File structure

Notes: The file is a free-form text document (DTA-Protokoll) showing financial transaction records with no consistent columnar structure. It contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total fields, but these are not in a consistent delimiter-separated format across lines. The data appears to be a financial report rather than structured PII records. Since there is no consistent delimiter and the lines vary in structure, this qualifies as unstructured text.

finanzen__dta_files__2010__logfiles__101018.log.csv
0 rows

File structure

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

finanzen__dta_files__2010__logfiles__101117.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol document with no consistent column structure. It contains transaction records with company names and amounts but lacks any identifiable personal information such as names, addresses, emails, or phone numbers. The data appears to be corporate financial records rather than customer PII.

finanzen__dta_files__2010__logfiles__101224.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protокол with no consistent columnar structure. Contains transaction lines with codes (OP-Nr., PK-Nr.), names (SWITC, SVAZ�, etc.), and monetary values, but lacks a fixed delimiter or header. No identifiable PII fields (names appear to be company codes rather than personal names). Per rules, unstructured files with no consistent structure return empty columns object.

finanzen__dta_files__2010__logfiles__101227.log.csv
0 rows

File structure

Notes: This is a free-form financial document/protокол with no consistent columnar structure. It contains transaction details (OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, Total) but lacks repeating columns across rows and is not a CSV/TSV. Contains no identifiable PII fields beyond possibly 'ECOME' which could be a business name. No structured columns to map.

finanzen__dta_files__2011__log__110117.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protокол with no consistent column structure. It contains transaction data with company names (SWITC, ALLIA, STRAS, etc.) but no personal PII fields. The format is not CSV or any delimited structure — it's a textual financial summary with rows representing transactions rather than records with identifiable fields. Per rules, unstructured files with no column structure return empty columns object.

finanzen__dta_files__2011__log__110224.log.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains financial transaction data but no identifiable PII fields in structured format. Contains business names (SWITC, SWISS, TREUH, etc.) which are company names and should be skipped per rules. No emails, phone numbers, or other PII visible in this sample.

finanzen__dta_files__2011__log__110331.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total columns, but these are not consistently repeated across lines and the format is not CSV. The data is purely transactional and does not contain any PII fields like email, phone, or address. The values represent company names (SWITC, SVAZ�, SWISS, etc.) which are business entities, not personal PII. Therefore, no PII columns to map.

finanzen__dta_files__2011__log__110505.log.csv
0 rows

File structure

Notes: The provided text is a financial protocol document from Zynex, showing transaction records with internal codes, names, amounts, and totals. It contains no consistent column structure, and while there are names like 'SWITC', 'EKZKT', etc., these appear to be internal codes or abbreviations rather than personal PII fields. The document is purely transactional and financial in nature, lacking any identifiable personal data such as email, phone, or address fields. Therefore, it is classified as unstructured text with no mappable PII columns.

finanzen__dta_files__2011__log__110531.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction data with company names (EIDG., ECOME, SHELL, BRUNN, etc.) and monetary values, but no personal PII fields. The format is unstructured prose with tabular data embedded in text, not a delimited file with columns.

finanzen__dta_files__2011__log__110622.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent column structure. It contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total fields, but these appear as part of a narrative table rather than a delimited CSV. The values are purely transactional codes and amounts (e.g., 'SVAZ�', '7 CHF', '9'333.60') with no identifiable PII. No emails, phone numbers, or names are present in a searchable format. The document is a protocol summary for a payment batch dated 22.06.2011.

finanzen__dta_files__2011__log__110726.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent columnar structure. It shows payment records with OP-Nr, Valuta, PK-Nr, Name, and monetary values but lacks headers or a repeated delimiter pattern. Contains no identifiable PII fields (names appear to be company abbreviations, not personal names). Per rules, unstructured files with no column structure return empty columns object.

finanzen__dta_files__2011__log__110830.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent columnar structure. The file contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total columns, but these are not consistently delimited across rows. The content appears to be a printed report rather than a structured dataset. No PII fields are present in a structured format.

finanzen__dta_files__2011__log__111003.log.csv
0 rows

File structure

Notes: The file is a free-form financial report with no consistent columnar structure. It contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total fields, but these are not consistently delimited across lines and appear to be part of a narrative report rather than a structured dataset. Per rules, unstructured files with no consistent delimiter and varying line shapes are classified as unstructured with no column mapping.

finanzen__dta_files__2011__log__111102.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. It contains transaction lines with account numbers, names (likely company names), amounts, and totals, but lacks a defined delimiter or header row. The values appear to be business names (SWITC, ECOME, EKZKT, etc.) rather than personal PII. No email or phone numbers are visible. This is not importable structured data; it should be processed as unstructured text.

finanzen__dta_files__2011__log__111212.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. It contains transaction lines but lacks headers or a stable delimiter. No identifiable PII is visible in this sample beyond generic company/client names (SWISS, EIDG., WINTE, BRUNN, DIGIT) which appear to be business entities rather than personal identifiers. Given the unstructured nature and absence of personal PII fields, this file should be processed as unstructured text.

finanzen__dta_files__2011__log__111227.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no column structure. It contains transaction lines with reference numbers, dates, and amounts in CHF, but no identifiable personal information (PII) fields. The document appears to be an internal accounting summary from Zynex's FaktNT ERP system, showing payments for various entities (EKZKT, SHELL, TDCSW, etc.) on 27.12.2011. Since there are no consistent columns or repeating patterns across lines and no PII values, this is classified as unstructured text.

finanzen__dta_files__2012__log__120201.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent column structure. It contains line items with OP-Nr, Valuta dates, PK-Nr, customer names (SWITC, ECOME, TDCSW, etc.), and monetary amounts, but lacks a uniform delimiter or repeated header pattern across rows. The data appears to be a printed report rather than structured tabular data, showing payment summaries for Swiss SMEs to Zynex for web hosting/CMS subscriptions. No PII columns can be mapped due to the unstructured layout.

finanzen__dta_files__2012__log__120302.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It shows transaction records with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total fields, but these appear as part of a narrative table rather than a structured CSV. No identifiable PII columns exist in a machine-parseable format. The 'Name' field contains company abbreviations (SWITC, SVAZ�, ALLIA, etc.) which are not personal PII under our rules (company names are excluded). No emails, phone numbers, or personal names are visible.

finanzen__dta_files__2012__log__120306.log.csv
0 rows

File structure

Notes: The provided data is a free-form financial transaction log in German with no consistent columnar structure. It contains transaction details like reference numbers, dates, names, amounts, and totals, but lacks a defined delimiter or header row. This is typical of printed or exported accounting reports rather than structured CSV/TSV data. While it includes names that could be considered PII, the format does not lend itself to columnar mapping, and should be processed as unstructured text for PII extraction.

finanzen__dta_files__2012__log__120424.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger/protoco l with no consistent columnar structure. It contains transaction records with OP-Nr., Valuta, PK-Nr., Name, ZL, Betrag, and Total fields, but these are presented as free-form lines rather than a delimited table. The values are business names (SVAZ�, ECOME, EKZKT, etc.) and financial amounts in CHF, not personal PII. No structured columns exist to map.

finanzen__dta_files__2012__log__120530.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction records but lacks headers and a stable delimiter. While it contains business names that might resemble personal names, these are company/customer names for billing purposes and are not personal PII under the defined rules. No email or phone numbers are present.

finanzen__dta_files__2012__log__120605.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol document with no consistent columnar structure. It contains transaction details but no identifiable personal information in structured fields. The format is unstructured prose with embedded financial data, not a delimited table with PII columns.

finanzen__dta_files__2012__log__120629.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent columnar structure. It contains payment records with customer codes (e.g., SVAZİ, EKZKT) and monetary amounts, but lacks identifiable personal information in structured columns. No PII fields can be mapped as there are no consistent headers or repeating patterns that would allow column identification.

finanzen__dta_files__2012__log__120705.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protокол with no consistent columnar structure. The data appears to be a printed report showing transaction details (OP-Nr., Valuta, PK-Nr., Name, ZL, Betrag, Total) rather than a delimited dataset with repeated rows of the same fields. There are no identifiable PII columns in a structured format; the 'Name' field shown (EGGEN, DIGIT) appears to be business/customer codes rather than personal names. Since the file lacks a consistent delimiter and row structure, it is classified as unstructured.

finanzen__dta_files__2012__log__120726.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total columns, but the data is presented as prose with no consistent delimiter or header row. The values appear to be company names (SVAZ�, SWISS, FZELE, etc.) and financial amounts, not personal PII. Since there is no structured column mapping and the content is purely transactional/financial, we treat this as unstructured text without PII columns to map.

finanzen__dta_files__2012__log__121002.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total fields, but these are not consistently formatted across rows. The document is a protocol from Zynex dated 01.10.2012 showing payments in CHF. Since there is no consistent delimiter or header structure, this is classified as unstructured text. No PII columns can be mapped.

finanzen__dta_files__2012__log__121109.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction lines with fields like OP-Nr., Valuta, PK-Nr., Name, ZL, Betrag, and Total, but these appear in a tabular block rather than as consistently delimited columns across all rows. The document lacks a true header row and uses variable spacing/formatting. While it contains business names (SWITC, SVAZ�, etc.), these are not personal PII fields. The file is purely transactional/financial and does not contain any personal identifiable information such as email, phone, address, or DOB. Per instructions, unstructured files with no importable column structure return an empty columns object.

finanzen__dta_files__2012__log__121205.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. The data consists of transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total fields, but these are not consistently delimited across lines and appear to be part of a narrative report rather than a structured CSV or tabular dataset. No PII fields can be reliably extracted from this format.

finanzen__dta_files__2012__log__121221.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol/document showing transaction data with no consistent columnar structure. Contains payment references and totals but no identifiable personal data in structured columns. The format lacks repeating field positions and appears as a narrative report rather than a delimited dataset.

finanzen__dta_files__2012__log__130112.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent columnar structure. The data shows payment records with OP-Nr, Valuta dates, PK-Nr, and customer names (SWITC, TREUH, ALLIA, etc.), but these are not in a delimited format with repeating columns. The document is a financial summary (DTA-Protokoll) showing payments in CHF, not containing any identifiable PII fields like email, phone, or address. It only contains business names and transaction amounts, which are not personally identifiable information under the defined PII categories.

finanzen__dta_files__2013__Log__130109.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protocoß with no consistent columnar structure. It contains transaction data with customer codes (e.g., SWITC, ECOME) but no identifiable personal information like names, emails, or addresses. The format is a tabular text block with headers like OP-Nr., Valuta, PK-Nr., Name, ZL, Betrag, Total, but these appear to be internal codes and monetary amounts rather than PII. No structured columns exist to map.

finanzen__dta_files__2013__Log__130124.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protoll with no consistent columnar structure. It contains transaction data with company names (SVAZŶ, ECOME, SHELL, etc.) but no personal PII fields. The format is a tabular text report rather than structured CSV/TSV with headers and repeated rows. No column mapping possible.

finanzen__dta_files__2013__Log__130304.log.csv
0 rows

File structure

Notes: This is free-form financial transaction data with no consistent columnar structure. The document contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total fields, but they are not consistently delimited across lines. The content is purely transactional financial data without personal identifiable information (PII) in structured columns. Therefore, it is classified as unstructured text with no column mapping required.

finanzen__dta_files__2013__Log__130325.log.csv
0 rows

File structure

Notes: This is free-form financial ledger text with no consistent columnar structure. The data appears to be a printed statement showing transaction records with columns like OP-Nr., Valuta, PK-Nr., Name, ZL, Betrag, and Total. However, there is no repeatable delimiter structure across lines and the format varies. While names like SVAZÄ, TREUH, EKZKT appear, they are likely company/partner names rather than personal PII. No clear personal email addresses or phone numbers are visible in the sample. According to rules, unstructured files with no consistent row structure should return empty columns object.

finanzen__dta_files__2013__Log__130402.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol document with no consistent columnar structure. It contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total fields, but these appear in a tabular free-text format rather than a delimited structured file. No identifiable PII is present in the sample rows — only entity names (EIDG., HELVE, COMSU, POULT) which are likely company/voucher codes, not personal names. The document represents internal corporate accounting records from Zynex.

finanzen__dta_files__2013__Log__130424.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protocoïl document with no consistent columnar structure. It contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total, but these are not consistently repeated across lines and appear to be part of a narrative report rather than a structured dataset. No PII fields are present.

finanzen__dta_files__2013__Log__130531.log.csv
0 rows

File structure

Notes: The file is a free-form financial protocol/proforma document (DTA-Protokoll) with no consistent columnar structure. It contains transaction lines with OP-Nr., Valuta, PK-Nr., Name, ZL, Betrag, and Total, but these are not machine-readable fields — they are part of a human-readable financial summary. No PII is present in a structured format; the 'Name' field contains company abbreviations (SVAZ�, GEWER, SHELL, etc.), not personal names. This qualifies as unstructured text per the opt-out rules (a) no consistent delimiter, (b) lines have variable shapes, (c) no embedded emails/phones visible).

finanzen__dta_files__2013__Log__130611.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol/report document (DTA-Protokoll) with no consistent columnar structure. It contains transaction lines with reference numbers (OP-Nr.), dates (Valuta), internal codes (PK-Nr.), entity identifiers (Name/ZL), amounts, and totals — but these are not personal PII fields. No email addresses or phone numbers are visible in the sample. The format is a human-readable financial summary, not a delimited data export.

finanzen__dta_files__2013__Log__130701.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no consistent columnar structure. Lines contain mixed data (transaction IDs, dates, customer codes, amounts) but no identifiable personal information in structured columns. The format does not conform to CSV/TSV with repeating columns; instead, it's a fixed-format report lines. Though customer codes (e.g., SVAZ�, SHELL, SPREC) appear, they are internal business codes, not PII fields like names or emails. No emails, phones, or addresses are present. The file is purely transactional and lacks any header or repeated column pattern.

finanzen__dta_files__2013__Log__130719.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol/document with no consistent columnar structure. It contains transaction lines with OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, and Total columns, but the format varies per line and lacks a stable delimiter or header. Contains no identifiable PII fields (names appear to be business/client codes like SVAZÄ, SHELL, TDCSW rather than personal names). Per rules, unstructured files with no consistent columns return empty columns object.

finanzen__dta_files__2013__Log__130829.log.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; contains financial transaction records with company/client names but no identifiable PII fields

finanzen__dta_files__2013__Log__131007.log.csv
0 rows

File structure

Notes: This is a free-form financial protocol document from Zynex with no consistent column structure. It contains transactional data (invoice numbers, dates, customer codes, amounts) but no identifiable personal information in structured fields. The values shown are company codes (SWITC, SVAZË, SWISS, etc.), amounts in CHF, and internal reference numbers — none constitute PII under the defined field types. No emails, phone numbers, or names appear in the visible portion.

finanzen__dta_files__2013__Log__131104.log.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; contains financial transaction data with company names and amounts, but no identifiable personal PII fields. The format is not CSV/TSV — it's a financial report with lines of totals and transaction rows that do not follow a fixed delimiter pattern across rows.

finanzen__dta_files__2013__Log__131106.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protcol document (DTA-Protokoll) with no consistent columnar structure. It contains transactional data with account numbers, names, and amounts but lacks a repeatable delimiter or header row. Per rules, this qualifies as unstructured text with embedded PII (names and potentially account identifiers), so we return empty columns and flag as unstructured for streaming processing.

finanzen__dta_files__2013__Log__131206.log.csv
0 rows

File structure

Notes: This is a financial transaction report in German with no column headers. The data consists of OP-Nr. (transaction numbers), Valuta (dates), PK-Nr. (customer/account numbers), Name (customer names), ZL (currency code), Betrag (amounts), and Total. While 'Name' appears to contain customer names, the entire file lacks a consistent delimiter and is presented as free-form tabular data with merged rows and formatting artifacts (e.g., line breaks within totals). Per rules, unstructured files with no consistent column structure must be processed as unstructured, even when PII-like fields appear. Embedded names would be extracted via streaming PII detection in downstream processing.

finanzen__dta_files__2013__Log__131219.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction log with no consistent column structure. It contains only transaction details (OP-Nr, Valuta, PK-Nr, Name, ZL, Betrag, Total) and totals, no personal PII fields. The format is unstructured prose with tabular data embedded, but lacks repeated columnar structure across rows.

finanzen__dta_files__2018__pain.001_20180611c__id.csv
0 rows

File structure

Notes: The provided input is a single line containing a Swiss IBAN (CH8704835061435161001). This is not structured data with columns; it is a standalone financial identifier. There is no consistent delimiter, header, or multiple rows to analyze for column mappings. The IBAN itself is not classified as PII under the provided field types (it is a bank account identifier, not email, phone, name, etc.). Since the file appears to be unstructured with no columnar structure and only one line of data, it is classified as unstructured with an empty columns object.

finanzen__dta_files__2018__pain.001_20180611d__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains only an IBAN (CH8704835061435161001) which is not personal PII in this context (corporate banking identifier)

finanzen__dta_files__2018__pain.001_20180705__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN number (CH8704835061435161001). There is no structured tabular data or repeated records — it is not a CSV, TSV, or any delimited format. The IBAN is a financial account identifier and not PII per the defined field types (it is not email, phone, name, address, etc.). Since there is no row structure and the file appears to be a standalone value or note, it qualifies as unstructured text with no columns to map. No emails or phones are visible.

finanzen__dta_files__2018__pain.001_20180730__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, no structured columns. Sample shows IBAN values but no consistent delimiter or row structure.

finanzen__dta_files__2018__pain.001_20180824__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing an IBAN number (CH8704835061435161001) but no structured data or columns. The file appears to be a standalone snippet rather than a dataset with rows and columns. No PII columns can be mapped from this unstructured content.

finanzen__dta_files__2018__pain.001_20180903__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent delimiter structure — appears to be a single-line or minimal data snippet rather than a CSV. IBAN is financial account data, but this file lacks row structure and must be processed as unstructured.

finanzen__dta_files__2018__pain.001_20180927__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter or row structure, and the content is purely financial/transactional data without any personal PII fields. The IBAN is a bank account identifier and not considered PII per the exclusion rules (it maps to financial/transactional data, not personal address fields).

finanzen__dta_files__2018__pain.001_20181025__id.csv
0 rows

File structure

Notes: This is unstructured data. The sample shows a single line containing an IBAN (CH8704835061435161001), which is a bank account number and not considered PII under the provided field definitions. There is no consistent delimiter or structured row format present in the provided snippet. Since this appears to be a standalone IBAN without any accompanying structured data or additional lines, it is treated as unstructured content with no columns to map.

finanzen__dta_files__2018__pain.001_20181116__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (CH...) but no consistent column structure or delimiter. This is not a delimited file with columns; it's unstructured financial/invoice text. No CSV/TSV structure visible in the sample.

finanzen__dta_files__2018__pain.001_20181217__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN (CH8704835061435161001) which is not considered PII in the context of the provided field types. The file appears to be unstructured free-form text with no consistent columnar structure or header. No emails, phone numbers or other identifiable patterns are present in this snippet.

finanzen__dta_files__2019__pain.001_20190114__id.csv
0 rows

File structure

Notes: The file appears to be unstructured free-form text (likely a README, note, or description) with no consistent column structure. The sample shows a single line containing what looks like a Swiss IBAN number rather than structured records with PII columns. Since there is no consistent delimiter or row structure, and the content is free-form text, this is classified as unstructured.

finanzen__dta_files__2019__pain.001_20190204__id.csv
0 rows

File structure

Notes: free-form text with embedded financial data (IBANs), no consistent delimiter or row structure. This is unstructured financial data from the breach, not a CSV with PII columns.

finanzen__dta_files__2019__pain.001_20190218__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured tabular data with columns or headers in the provided sample. The file appears to be unstructured or contains only a fragment of data, not a CSV or other structured format with identifiable PII columns.

finanzen__dta_files__2019__pain.001_20190311__id.csv
0 rows

File structure

Notes: This is not a structured dataset. The provided snippet is a single line containing an IBAN number (CH8704835061435161001), which is a financial identifier and not a personal PII field. The breach context describes financial records and invoices, but the sample shows free-form text without any consistent columnar structure or headers. There are no visible emails, phone numbers, or other PII in the given text, and the format lacks repeated patterns that would indicate CSV/TSV/structured data. Therefore, this is classified as unstructured with no columns to map.

finanzen__dta_files__2019__pain.001_20190313__id.csv
0 rows

File structure

Notes: The provided text does not contain a structured dataset with columns. It appears to be a single line containing an IBAN number (CH8704835061435161001) and a description referencing a breach context for Zynex, a Swiss web hosting and CMS software company. There are no delimited rows or headers to map to PII fields. The IBAN itself is financial account data, but it is not classified as PII in the provided field types and thus is not mapped. The file is unstructured and should be processed accordingly.

finanzen__dta_files__2019__pain.001_20190408__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, not structured columns

finanzen__dta_files__2019__pain.001_20190424__id.csv
0 rows

File structure

Notes: The provided input appears to be a single line containing an IBAN number (CH8704835061435161001) rather than a structured dataset with columns. There is no consistent delimiter or header structure visible in the sample. This is likely part of an unstructured file containing financial records or transaction data rather than a CSV or similar structured format. The IBAN itself is a financial identifier and not considered PII under the defined fields.

finanzen__dta_files__2019__pain.001_20190529__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001), no consistent columnar structure visible in the sample. This appears to be a single line of unstructured data from the breach.

finanzen__dta_files__2019__pain.001_20190701__id.csv
0 rows

File structure

Notes: This is not structured data. The sample provided is a single IBAN number (CH8704835061435161001) without any visible column structure, header, or delimiter. The context indicates this is part of a corporate financial breach from Zynex, a Swiss web hosting company, but the snippet itself is free-form text with no consistent row structure or identifiable columns. It fails the structured format criteria because there is no shared delimiter, no consistent row shape, and it contains financial data rather than personal PII fields. Therefore, it is classified as unstructured text with no column mapping possible.

finanzen__dta_files__2019__pain.001_20190724__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) and no consistent column structure across lines

finanzen__dta_files__2019__pain.001_20190828__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent delimiter or row structure visible in the provided data. This appears to be a single line of unstructured financial data rather than a delimited file with columns. The IBAN is a bank account identifier but not classified as PII in the provided field list, so no mapping is performed.

finanzen__dta_files__2019__pain.001_20190913__id.csv
0 rows

File structure

Notes: This is unstructured data: a single line containing only a Swiss IBAN (CH8704835061435161001). No consistent columnar structure exists in the sample. IBANs are financial identifiers and not considered PII in this context, so no PII fields are mapped.

finanzen__dta_files__2019__pain.001_20191029__id.csv
0 rows

File structure

Notes: This is a free-form text sample containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter structure, and the content appears to be unstructured notes or comments rather than a CSV with columns. The IBAN is a financial identifier, not PII according to the exclusion rules, so it is skipped. No structured PII columns exist to map.

finanzen__dta_files__2019__pain.001_20191108__id.csv
0 rows

File structure

Notes: This is not a structured dataset; it's a single line containing an IBAN (CH8704835061435161001) rather than a delimited file with columns. The breach context describes financial records, but this sample shows only unstructured data (a standalone IBAN). No column mapping is possible.

finanzen__dta_files__2019__pain.001_20191129__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not emails or phones), no consistent column structure

finanzen__dta_files__2019__pain.001_20191210__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) — no consistent delimiter or structured columns; this is a standalone financial record fragment, not a dataset with rows/columns

finanzen__dta_files__2019__pain.001_20191217__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing only a Swiss IBAN number (CH8704835061435161001) with no structured columns or header. The data appears to be part of a financial record from the Zynex breach context, but there are no identifiable PII fields in this snippet beyond the IBAN, which is not included in our PII field types. Since there is no consistent delimiter or structure, this is classified as unstructured text.

finanzen__dta_files__2019__pain.001_20191219__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, no consistent delimiter structure, not a CSV/TSV

finanzen__dta_files__2020__pain.001_20200106__id.csv
0 rows

File structure

Notes: This is unstructured data (free-form text). The content appears to be a single IBAN number (CH8704835061435161001) rather than a CSV or structured table. Since there are no consistent columns or delimiters, and the data does not conform to a tabular structure, it is classified as unstructured. No PII columns can be mapped.

finanzen__dta_files__2020__pain.001_20200109__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN number (CH8704835061435161001) and no structured columns. It does not represent a CSV or tabular dataset with headers and rows. The content is a single line with a financial identifier, not structured PII fields like email, phone, or name. Therefore, no column mapping is possible, and the format is unstructured.

finanzen__dta_files__2020__pain.001_20200110__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001) with no surrounding context or structure. There are no consistent columns or delimiters across lines, and this appears to be free-form text rather than a structured dataset. Since there are no other rows visible in the sample to establish a consistent structure, this file is classified as unstructured.

finanzen__dta_files__2020__pain.001_20200127__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, no structured columns visible

finanzen__dta_files__2020__pain.001_20200212__id.csv
0 rows

File structure

Notes: This is a free-form text containing only an IBAN (CH8704835061435161001). No structured columns or row patterns exist. The file appears to be a single-line snippet, not a CSV or tabular dataset. IBAN is a financial identifier and not classified as PII under the given field types, so no columns are mapped.

finanzen__dta_files__2020__pain.001_20200227__id.csv
0 rows

File structure

Notes: The provided data is a single line containing an IBAN number (CH8704835061435161001). There are no structured columns or headers present. This appears to be a standalone financial identifier rather than a CSV or other structured format. The file is unstructured with embedded financial data, not personal PII fields like names, emails, or phone numbers.

finanzen__dta_files__2020__pain.001_20200306__id.csv
0 rows

File structure

Notes: This is a free-form text snippet containing only an IBAN (CH8704835061435161001) with no structured columns or consistent delimiter patterns. No CSV or tabular format is present — this appears to be a standalone line from financial records or a note. Since there is no row structure and only one isolated value, we classify this as unstructured with no column mapping required. The IBAN itself is not a PII field in our defined schema (it is an account identifier, not personal identifier), so no extraction is needed.

finanzen__dta_files__2020__pain.001_20200331__id.csv
0 rows

File structure

Notes: free-form text with embedded financial identifier (IBAN). No consistent column structure visible in the sample; this is unstructured financial data rather than structured PII records. IBAN is a financial account number, not a PII field in the current context.

finanzen__dta_files__2020__pain.001_20200416__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (Swiss bank account), not structured tabular data

finanzen__dta_files__2020__pain.001_20200428__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, not structured tabular data

finanzen__dta_files__2020__pain.001_20200515__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN (CH8704835061435161001) with no other data or structure. There is no column structure, no header, and no other rows to analyze. The content appears to be a standalone financial identifier rather than a structured dataset with PII fields. As per rules, unstructured files with no consistent delimiter or row structure are mapped to an empty columns object.

finanzen__dta_files__2020__pain.001_20200610__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing only an IBAN (CH8704835061435161001). There are no structured columns or headers. Since it's not a CSV/TSV with repeated rows and lacks any other PII, we treat it as unstructured. The IBAN is not included as a PII field in our standard schema, so no columns are mapped.

finanzen__dta_files__2020__pain.001_20200629__id.csv
0 rows

File structure

Notes: This is a single-line unstructured data snippet containing only an IBAN (CH8704835061435161001). There are no consistent columns or structured rows present in the provided sample. The content appears to be a raw IBAN number without any header or additional context. Since there is no structured format or repeating pattern, this should be treated as unstructured data.

finanzen__dta_files__2020__pain.001_20200710__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only a single IBAN (CH8704835061435161001) and no structured columns or rows. The file appears to be a simple note or snippet rather than a dataset with multiple records. Since there is no consistent delimiter, no header, and only one line of data, this is classified as unstructured text. No PII columns can be mapped.

finanzen__dta_files__2020__pain.001_20200731__id.csv
0 rows

File structure

Notes: This is a free-form text sample containing only an IBAN (CH8704835061435161001) with no structured columns or row consistency. No identifiable PII fields (email, phone, name, etc.) are present in the visible content. The sample appears to be a single line fragment from financial data, not a delimited dataset.

finanzen__dta_files__2020__pain.001_20200821__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent column structure; appears to be a single data snippet or note, not a delimited file with rows

finanzen__dta_files__2020__pain.001_20200914__id.csv
0 rows

File structure

Notes: The provided data is free-form text with IBAN numbers and no consistent columnar structure. It appears to be unstructured financial data from the breach rather than a delimited CSV file. Per rules, unstructured files with no consistent delimiter and variable line shapes containing embedded PII (IBANs) should be returned as empty columns with format type 'unstructured'.

finanzen__dta_files__2020__pain.001_20201006__id.csv
0 rows

File structure

Notes: This is unstructured financial data (IBAN numbers) with no column structure or row consistency. The file contains only sample IBAN values and no identifiable PII fields like names, emails, or addresses. No column mapping is possible.

finanzen__dta_files__2020__pain.001_20201028__id.csv
0 rows

File structure

Notes: This is a single-line unstructured input containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter or row structure. Per the rules, this is treated as unstructured text with no column mapping performed. The IBAN itself is not mapped as a PII field in the current schema.

finanzen__dta_files__2020__pain.001_20201116__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent columnar structure; appears to be a single line containing only the IBAN without any headers or additional data. IBAN is not a PII field per the defined schema, so no columns are mapped.

finanzen__dta_files__2020__pain.001_20201218__id.csv
0 rows

File structure

Notes: This file is free-form text with IBAN numbers visible but no structured columns. It lacks a consistent delimiter, row structure, or header. The IBANs are financial identifiers, not PII fields, so no columns are mapped.

finanzen__dta_files__2021__pain.001_20210105__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number. There is no consistent delimiter, header, or structured data format. IBANs are financial identifiers and not considered PII in this context per the exclusion rules (financial/transactional data). No PII columns to map.

finanzen__dta_files__2021__pain.001_20210113__id.csv
0 rows

File structure

Notes: This file appears to be unstructured data containing only a single IBAN value (CH8704835061435161001) with no other context or structure. There are no consistent columns or delimiters across lines, and the content does not resemble a CSV or other structured format. Since it is unstructured and contains no identifiable PII fields beyond the IBAN (which is not a standard PII field in the defined categories), it is treated as unstructured text with no columns to map.

finanzen__dta_files__2021__pain.001_20210118__id.csv
0 rows

File structure

Notes: This is unstructured data containing only an IBAN number (CH8704835061435161001). There are no consistent columns, headers, or structured rows visible in the sample. The IBAN is a financial account identifier and not considered PII under the defined field types, so no columns are mapped.

finanzen__dta_files__2021__pain.001_20210208__id.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent delimiter structure. It contains unstructured financial data (IBAN number) and breach context notes rather than structured PII records. No column mapping is possible.

finanzen__dta_files__2021__pain.001_20210219__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text containing only an IBAN (CH8704835061435161001). No structured columns or PII fields are present. The IBAN is a bank account identifier and not considered PII per the provided field types.

finanzen__dta_files__2021__pain.001_20210309__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, no structured columns present

finanzen__dta_files__2021__pain.001_20210330__id.csv
0 rows

File structure

Notes: The provided text is a single IBAN number (CH8704835061435161001) with no structure, headers, or additional rows. It does not represent a delimited file with multiple columns or rows of data. This is not a CSV or any structured format. Since there is no consistent delimiter or row structure, and the content is a single financial identifier, it is treated as unstructured data with no columns to map.

finanzen__dta_files__2021__pain.001_20210420__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent column structure; appears to be a single-line note or comment rather than tabular data. No repeated pattern or delimiter across lines is visible in the sample.

finanzen__dta_files__2021__pain.001_20210512__id.csv
0 rows

File structure

Notes: free-form text with embedded financial data (IBANs), no consistent columnar structure

finanzen__dta_files__2021__pain.001_20210610__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not emails/phones). No consistent delimiter or row structure — unstructured opt-out applies

finanzen__dta_files__2021__pain.001_20210708__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN value; no consistent delimiter or row structure visible in sample

finanzen__dta_files__2021__pain.001_20210729__id.csv
0 rows

File structure

Notes: This is unstructured data consisting of IBAN numbers (bank account identifiers) with no consistent columnar structure or header. The data appears to be raw financial records from the Zynex breach, containing only bank account identifiers without any other structured fields. Since there is no consistent delimiter or row structure, and the content is purely financial identifiers, this should be processed as unstructured text.

finanzen__dta_files__2021__pain.001_20210831__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, no structured columns

finanzen__dta_files__2021__pain.001_20210929__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not email/phone), no structured columns

finanzen__dta_files__2021__pain.001_20211027-2__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured columnar data, no headers, and no repeated pattern across multiple lines. The content is a standalone financial identifier, not a dataset with personal fields. No PII can be extracted from this line.

finanzen__dta_files__2021__pain.001_20211027-3__id.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; contains IBAN values but no row structure or repeating patterns. This is unstructured financial/transactional data (not CSV). Routing to unstructured processing for IBAN extraction.

finanzen__dta_files__2021__pain.001_20211027-4__id.csv
0 rows

File structure

Notes: This is unstructured financial data containing IBAN numbers. No consistent column structure or header is present. The sample shows IBAN values but lacks any delimited format or repeated structure across rows. The breach context indicates this is financial record data from Zynex, a Swiss web hosting company, but the actual content appears to be raw IBAN listings without structured fields.

finanzen__dta_files__2021__pain.001_20211027-5__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (Swiss bank accounts). No consistent delimiter or structured columns. Contains only IBAN values with no other PII visible in sample.

finanzen__dta_files__2021__pain.001_20211129__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not emails/phones), no consistent delimiter or row structure

finanzen__dta_files__2021__pain.001_20211217__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, no consistent column structure

finanzen__dta_files__2022__pain.001_20220104__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, not structured CSV/TSV. Contains Swiss bank account numbers (IBAN format) but no consistent columnar structure across lines. This is an unstructured file requiring special handling for financial identifiers.

finanzen__dta_files__2022__pain.001_20220119__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers but no consistent delimiter structure; this is unstructured financial data dump

finanzen__dta_files__2022__pain.001_20220224__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (no consistent delimiter structure across lines)

finanzen__dta_files__2022__pain.001_20220329__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, no consistent delimiter or column structure

finanzen__dta_files__2022__pain.001_20220421__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers only, no consistent delimiter or column structure

finanzen__dta_files__2022__pain.001_20220517__id.csv
0 rows

File structure

Notes: free-form text with embedded financial identifiers (IBANs), no consistent delimiter or column structure. This file contains only Swiss bank account numbers (IBAN format) and no structured PII fields.

finanzen__dta_files__2022__pain.001_20220629__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not emails/phones), no consistent column structure

finanzen__dta_files__2022__pain.001_20220728__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (Swiss bank accounts). No consistent delimiter or row structure; values are IBANs only with no other data. This is typical of a raw dump of financial records where only account numbers were extracted. The IBANs themselves are not classified as PII in the current schema (they are financial identifiers, not personal identifiers like names, emails, or addresses), so no PII columns to map. However, this file should be flagged for financial sensitivity during processing.

finanzen__dta_files__2022__pain.001_20220830__id.csv
0 rows

File structure

Notes: free-form text with IBAN numbers (Swiss bank accounts) but no consistent columnar structure. No headers or delimiters present across lines; all lines appear to be standalone IBAN values. This qualifies as unstructured data requiring streaming IBAN extraction.

finanzen__dta_files__2022__pain.001_20220930__id.csv
0 rows

File structure

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

Notes: File contains only IBAN (International Bank Account Numbers) without any PII columns. IBANs are financial account identifiers, not personal identifiable information in the traditional sense (no names, emails, phones, addresses, or DOB). This appears to be a financial records extract listing Swiss bank account numbers. No structured PII fields are present.

finanzen__dta_files__2022__pain.001_20221027__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only IBAN numbers. There is no consistent delimiter or structured columns, and the content is unstructured. The file does not contain any other data types or structured records, so it should be processed as unstructured text.

finanzen__dta_files__2022__pain.001_20221201__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, not a structured table with columns. No consistent delimiter or row structure present; lines contain only IBAN values.

finanzen__dta_files__2022__pain.001_20221221__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (Swiss bank accounts) — no consistent CSV/TSV structure, lines vary in length and content. This qualifies as unstructured data per rules (a), (b), (c).

finanzen__dta_files__2023__pain.001_20230103__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers (Swiss bank accounts), no consistent delimiter or row structure

finanzen__dta_files__2023__pain.001_20230118__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, no consistent columnar structure

finanzen__dta_files__2023__pain.001_20230130__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, no consistent column structure

finanzen__dta_files__2023__pain.001_20230227__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs only, no structured columns present

finanzen__dta_files__2023__pain.001_20230303__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs but no consistent column structure; this is unstructured financial data with no delimited rows

finanzen__dta_files__2023__pain.001_20230330__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not emails/phones). No consistent column structure, lines vary in length and content. This is unstructured financial/IBAN data from Zynex's internal records.

finanzen__dta_files__2023__pain.001_20230427__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (Swiss bank accounts), no consistent delimiter or header structure. This is an unstructured file containing only IBAN values, no other columns or structured data.

finanzen__dta_files__2023__pain.001_20230530__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (Swiss bank account numbers), no consistent columnar structure

finanzen__dta_files__2023__pain.001_20230629__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, no consistent delimiter or structure. Contains only Swiss IBAN numbers with no other data patterns. This is unstructured financial data with no column mapping possible.

finanzen__dta_files__2023__pain.001_20230706__id.csv
0 rows

File structure

Notes: free-form text with embedded financial data (IBANs), no consistent column structure

finanzen__dta_files__2023__pain.001_20230719__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs only — no consistent column structure or delimiter. This is a raw list of Swiss bank account numbers (IBANs) with no header or other data. The file is unstructured and contains no CSV/table structure, so it falls under unstructured opt-out rules. IBANs are not a PII field in the defined schema and are excluded from mapping.

finanzen__dta_files__2023__pain.001_20230830__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers; no consistent delimiter or column structure. This is unstructured data (single column of IBAN values) and should be routed through streaming IBAN extraction

finanzen__dta_files__2023__pain.001_20230929__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, no consistent delimiter or column structure

finanzen__dta_files__2023__pain.001_20231030__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers only, no consistent delimiter structure

finanzen__dta_files__2023__pain.001_20231129__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN values, no consistent delimiter or row structure, visible IBANs in rows

finanzen__dta_files__2023__pain.001_20231221__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers, no consistent delimiter or structure

finanzen__dta_files__2024__pain.001_20240115__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (Swiss bank account numbers). No consistent delimiter or row structure exists; this is unstructured financial data with no column headers. IBANs are NOT considered PII fields per the defined schema.

finanzen__dta_files__2024__pain.001_20240201__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, not a structured CSV/TSV/Delimited file. No consistent column pattern or delimiter observed across lines. Contains only IBAN values with no surrounding structure or headers.

finanzen__dta_files__2024__pain.001_20240228__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers (Swiss bank accounts). No consistent delimiter or row structure. This is unstructured financial data showing IBANs but lacks any CSV/TSV-like format. The data appears to be a raw dump of financial records from Zynex's internal systems.

finanzen__dta_files__2024__pain.001_20240326__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, no consistent delimiter or row structure

finanzen__dta_files__2024__pain.001_20240429__id.csv
0 rows

File structure

Notes: free-form text with IBAN numbers visible, no consistent column structure. This is unstructured financial data (bank accounts) with no identifiable personal columns.

finanzen__dta_files__2024__pain.001_20240529__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (Swiss bank accounts) but no consistent column structure; this is unstructured financial data from Zynex breach

finanzen__dta_files__2024__pain.001_20240620__id.csv
0 rows

File structure

Notes: free-form text with IBAN numbers, no consistent column structure

finanzen__dta_files__2024__pain.001_20240718__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers, no consistent delimiter or header structure visible in the sample

finanzen__dta_files__2024__pain.001_20240829__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs but no consistent delimiter structure; this is a list of IBANs only

finanzen__dta_files__2024__pain.001_20240930__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not email/phone). No consistent delimiter structure across lines; appears to be a raw list of Swiss bank account numbers (IBANs) from financial records. No headers or structured columns present. IBANs are financial identifiers and not classified as PII under the defined fields, so this file is unstructured with no mappable PII columns.

finanzen__dta_files__2024__pain_001_20241029__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (Swiss bank accounts). No consistent delimiter or row structure across lines; this is a raw dump of IBAN values with no header or CSV format. The sample contains only IBANs with no other data patterns.

finanzen__dta_files__2024__pain_001_20241128__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers only; no consistent delimiter structure across lines

finanzen__dta_files__2024__pain_001_standard_20241219__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers (not email/phone) but no consistent delimiter structure across lines; each line is a single IBAN value

finanzen__dta_files__2025___x-pain_001_standard_20250220__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN values only; no consistent delimiter or row structure

finanzen__dta_files__2025__pain_001_standard-20250319__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (Swiss bank accounts), no consistent delimiter or row structure visible in sample

finanzen__dta_files__2025__pain_001_standard-20250429__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not emails or phones). No consistent column structure across lines; each line is a single IBAN value. Since there is no structured delimiter and lines have different shapes, this is classified as unstructured. However, IBANs are not part of the defined PII fields (email, phone, dob, etc.), so no mapping is performed.

finanzen__dta_files__2025__pain_001_standard-20250527__id.csv
0 rows

File structure

Notes: free-form text with IBANs but no consistent column structure; no emails or phones visible, but IBANs are financial identifiers not mapped as PII fields in our schema

finanzen__dta_files__2025__pain_001_standard_20250109__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (Swiss bank accounts) — no consistent column structure; this is unstructured financial data from Zynex breach containing only IBAN numbers without any CSV-like structure or headers

finanzen__dta_files__2025__pain_001_standard_20250129__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers (Swiss bank accounts), not structured CSV/TSV. Contains only IBANs with no consistent column layout or headers. Returns empty columns object for unstructured processing.

finanzen__dta_files__2025__pain_001_standard_20250220-2__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers (not email/phone), no consistent column structure

finanzen__dta_files__2025__pain_001_standard_20250404__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers; no consistent delimiter or column structure; lines vary in length and content; contains Swiss IBAN values which are financial identifiers but not personal PII per exclusion rules

finanzen__dta_files__2025__pain_001_standard_20250630__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers, no consistent delimiter or row structure. This appears to be a raw dump of IBAN values without any column headers or structured format. No mapping can be performed as there are no identifiable columns.

finanzen__dta_files__2025__pain_001_standard_20250730__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not email/phone), no consistent delimiter or row structure

finanzen__dta_files__2025__pain_001_standard_20250829__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (Swiss bank account numbers) but no consistent column structure or delimiter. This is unstructured data (prose-style) rather than a CSV/TSV file. The IBANs are NOT email/phone addresses, but structured processing would fail due to lack of consistent delimiters and line shapes. The breach context mentions financial records, but this sample appears to be a raw dump of IBANs without headers or structure.

finanzen__dta_files__2025__pain_001_standard_20250929__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers (not emails or phones). No consistent delimiter or structured columns detected. All lines appear to be individual IBAN entries without any shared format or header.

finanzen__dta_files__2025__pain_001_standard_20251030__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not emails or phones). No consistent delimiter or row structure exists; this is unstructured financial data containing only IBANs and no PII fields. IBANs are not considered PII in this context and are not mapped to any field type.

finanzen__dta_files__2025__pain_001_standard_20251201__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs, no consistent delimiter or column structure. This is not a CSV or tabular format; it's unstructured financial data containing IBAN numbers. The sample shows only IBAN values without any column headers or consistent row structure.

finanzen__dta_files__2025__pain_001_standard_20251218__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers, no consistent column structure

finanzen__dta_files__2026__pain_001_standard_20260106__id.csv
0 rows

File structure

Notes: free-form text with IBAN numbers, no consistent delimiter or header structure

finanzen__dta_files__2026__pain_001_standard_20260129__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs (not emails/phones). No consistent delimiter or row structure. This is a list of Swiss bank account numbers (IBAN format) rather than a CSV with PII columns. The breach context mentions financial records, so this appears to be raw banking data dump without structured fields.

finanzen__dta_files__2026__pain_001_standard_20260219__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers (Swiss bank accounts). No consistent delimiter or structured columns present in the sample.

finanzen__dta_files__2026__pain_001_standard_20260330__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN values, no consistent column structure

finanzen__dta_files__2026__pain_001_standard_20260428__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN numbers, no consistent column structure

finanzen__dta_files__2026__pain_001_standard_20260528__id.csv
0 rows

File structure

Notes: free-form text with embedded IBANs but no consistent column structure

finanzen__einkauf__hardware_einkauf__Hardware.csv
0 rows

File structure

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

Notes: This file contains unstructured hardware inventory data with no personal identifiable information (PII). The rows represent hardware items and costs, not personal customer or employee records. There are no columns that map to any PII fields (email, phone, name, address, etc.). The data appears to be internal corporate asset tracking for Zynex, listing server and network equipment with pricing in Swiss Francs (CHF).

finanzen__einkauf__hardware_einkauf__Konfigurationen.csv
0 rows

File structure

Notes: The file appears to be free-form text containing server hardware inventory records from Zynex. It lacks consistent column structure (rows have varying numbers of fields and no shared delimiter). The data consists of server component descriptions, quantities, and pricing in Swiss Francs (CHF). There are no visible emails, phone numbers, or other PII in the sample, but the unstructured format prevents column mapping. This should be processed as unstructured text for any potential embedded PII extraction.

finanzen__einkauf__hardware_einkauf__Preise.csv
0 rows

File structure

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

Notes: This is not a PII file. It is a structured inventory/pricing sheet for server hardware and bundles from Zynex. Columns contain product names, memory sizes, processor types, and pricing in CHF. No personal or identifiable information is present — only product catalog data and financial figures. All columns map to skip categories (product data, financial/transactional values).

finanzen__einkauf__ibm_netfinity_calculation__Konfigurationen.csv
0 rows

File structure

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

Notes: This file contains only product descriptions and pricing data. No personal or identifiable information is present. All columns represent internal inventory or financial records (product names, quantities, unit prices, totals). No PII fields mapped.

finanzen__einkauf__ibm_netfinity_calculation__Preise.csv
0 rows

File structure

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

Notes: This file is purely product configuration and pricing data — memory types, processors, bundles, and CHF prices. No personal or identifiable information is present. All columns are internal product codes, specifications, and financial figures, which per exclusion rules must be skipped. There are zero PII columns to map.

finanzen__ekz_abrechnungen__Tabelle1.csv
0 rows

File structure

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

Notes: This is purely transactional energy/financial data with no personal identifiers. Columns represent consumption metrics (kWh), costs (CHF), and internal accounting codes. No PII fields present.

finanzen__fahrzeuge__MWST-Abr_2021_Zynex__2021-1.csv
0 rows

File structure

Notes: This is a financial document (VAT statement for 2021) with no structured personal data columns. The content consists of financial accounting terms and figures in German, with no identifiable personal information in the visible columns. No PII fields are present in the structured format.

finanzen__fahrzeuge__MWST-Abr_2021_Zynex__2021-3.csv
0 rows

File structure

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

Notes: This is unstructured financial reporting data from Zynex corporate records. Columns contain Swiss VAT accounting codes (MWST), quarterly totals, and monetary values. No personal identifiers (PII) are present — all entries are aggregated financial figures, VAT codes, and accounting references. The header row appears to be blank or placeholder text, and subsequent rows contain VAT categories and numerical values without any customer or individual data. This matches the breach context of internal financial statements rather than customer PII.

finanzen__fahrzeuge__MWST-Abr_2021_Zynex__2026.csv
0 rows

File structure

Notes: This is unstructured financial data with no consistent column mapping. The rows appear to represent financial records with entries like 'Umsatz' (revenue), 'Preis exkl. MWST' (price excluding VAT), and other financial metrics. There are no identifiable PII fields in this sample data. The format is not CSV; it's free-form financial data without column headers or consistent structure.

finanzen__fahrzeuge__MWST-Abr_2021_Zynex__MWST-Schl_neu.csv
0 rows

File structure

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

Notes: This is a financial ledger file with columns indicating tax rates, account codes, and descriptions. No PII fields (names, addresses, emails, etc.) are present. All columns contain financial codes, percentages, and account references typical of accounting data. Therefore, no columns map to PII fields.

finanzen__fahrzeuge__MWST-Abr_2021_Zynex__Umsatz-Abst.csv
0 rows

File structure

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

Notes: This file contains unstructured financial and accounting data from Zynex's internal corporate records, with no identifiable personal information (PII). All columns represent financial categories, codes, or accounting terms (e.g., 'MWST-Abstimmung 2018', 'Abgerechnet', 'Nettoerlöse aus L+L'). No PII fields such as names, addresses, emails, or dates of birth are present. The data is purely transactional and organizational in nature, consistent with the breach context of financial statements and invoicing records.

finanzen__invoice-elfsight-20250517.log.csv
0 rows

File structure

Notes: The file appears to be a PostScript error dump / PDF generation failure, not structured data. It contains error messages, stack traces, and font-related warnings from a Distiller product attempt. There are no rows, columns, or identifiable PII patterns — only technical error output. No structured records exist to map.

finanzen__kalkulationen__hosting_preise_high_volume__Datenbeispiel.csv
0 rows

File structure

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

Notes: This file contains only financial pricing tiers and traffic limits data. All columns represent numerical pricing values, bandwidth limits, and traffic calculations. No personal identifiable information (PII) is present in any column. The data appears to be a structured pricing matrix for different service levels, with columns representing various price points and traffic allowances.

finanzen__kalkulationen__hosting_preise_high_volume__Preise.csv
0 rows

File structure

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

Notes: This file contains only product/pricing metadata with no personal data. Columns are headers for hosting package pricing tiers and technical metrics (bandwidth, traffic). No PII fields present.

finanzen__kalkulationen__hostingpreise_2008__Kunden___5GB.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a structured CSV file with three columns: Customer, GB Limit, and Preis. None of these columns map to PII fields. The 'Customer' column contains company or business names (Jusletter, Schüwo, Hiestand, etc.), which are explicitly excluded per the rules. The other columns represent numerical limits and pricing, which are not PII. Therefore, no PII columns are present in this dataset.

finanzen__kalkulationen__hostingpreise_2008__Preiskalkulation_Hosting.csv
0 rows

File structure

Notes: This is a free-form pricing table in German with no consistent delimiter or structured columns. It contains only product parameters and pricing calculations (CHF values), no personal or identifiable information. No column mapping is possible as there is no row structure.

finanzen__kalkulationen__hostingpreise_2008__Traffic_Cost_Calculation.csv
0 rows

File structure

Notes: The provided data is a free-form financial calculation table with no consistent columnar structure or personal identifiable information (PII). It contains only pricing calculations, technical metrics, and financial figures related to hosting services. There are no names, addresses, emails, or other PII fields present.

finanzen__kalkulationen__kosten_arbeitsstunde__Tabelle1.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample shows accounting entries and financial calculations rather than structured tabular data with identifiable columns. There are no repeating patterns or field separators across lines, and the content appears to be financial statements rather than personal data records.

finanzen__kalkulationen__kosten_kopien_clc2620__Tabelle1.csv
0 rows

File structure

Notes: This is a free-form financial calculation document with no consistent column structure. It appears to be a line-by-line calculation table for equipment depreciation and copy costs for a CLC 2620 device. There are no personal identifiable information fields present, only numerical financial data and percentages.

finanzen__kalkulationen__offerte_roggensinger_informatik__Tabelle1.csv
0 rows

File structure

Notes: This is a free-form text document (prose) describing network infrastructure costs and setup fees for a project by Roggensinger Ingenieure AG. No consistent tabular structure exists, and it contains no identifiable personal information or PII. It appears to be a project quote or cost breakdown, not a dataset with columns.

finanzen__mahnungen__2017__op_20170328__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: All columns contain internal financial/operational identifiers, timestamps, and transactional data. No PII fields (names, addresses, emails, etc.) are present. Columns like 'Kurzname' appear to be business/customer codes rather than personal names. All columns are flagged as skip per exclusion rules (company data, internal IDs, timestamps, financial amounts).

finanzen__mahnungen__2017__op_20170921__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely transactional financial data with no PII present. Columns contain status codes, invoice references, customer short names (alphanumeric business codes), dates, monetary amounts, and payment flags. No email addresses, phone numbers, names, addresses, or other personally identifiable information is visible in the first 50 rows.

finanzen__mahnungen__2017__op_20171024__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: All columns appear to be internal financial/business identifiers and timestamps. No PII fields detected. Columns contain numeric IDs, timestamps, transaction codes, invoice numbers, and monetary values — all internal to Zynex's financial systems. No names, addresses, emails, phones, or other personal data visible in the sample.

finanzen__mahnungen__2018__export_6084_03_12_2018___Worklogs.csv
1 column6 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Source columnMapped fieldConfidenceLLM assessment
4emailTexthighfree-text column with embedded emails (3/148 cells, 2% density)

Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance

finanzen__mahnungen__2018__jira_worklog_2018_summary__Summary.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a corporate financial data file from Zynex. All columns represent internal project billing metrics (project codes, hours, pricing, currency). No personal identifiers (PII) are present. All columns are business transactional data and should be skipped per exclusion rules.

finanzen__mahnungen__2018__jira_worklog_2018_summary__abgerechnet.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII fields present. All columns are internal financial/tracking data: project codes, teams, pricing, hours, charges. No names, emails, addresses, or other personal identifiers. Columns match exclusion rules (transactional/financial data).

finanzen__mahnungen__2018__jira_worklog_2018_summary__performx.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: All columns are internal financial/project tracking fields: Project codes, team assignments, price lists, activity hours, currency codes (CHF), charge totals. No PII fields present. Values are numeric identifiers, currency labels, and monetary amounts — no names, addresses, emails, or other personal data.

finanzen__mahnungen__2018__jira_worklog_2018_summary__report-20190110-1230.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a structured CSV file containing internal corporate financial records with company/client names and time tracking data. No PII fields (emails, phone numbers, addresses, etc.) are present. All entries are business names, time logs, and financial amounts — no personal identifiers mapped to individuals. Columns are skipped per rules (Company/Business fields).

finanzen__mahnungen__2018__op-liste_20180417__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: No PII columns detected. This appears to be a financial transaction log with customer names (non-PII in this context), invoice dates, amounts, and payment statuses. No emails, phone numbers, addresses, SSNs, DOBs, or other PII fields are present. All columns map to skip categories per rules: customer names are business entities, dates are transactional timestamps, amounts are financial data, and status codes are internal flags.

finanzen__mahnungen__2018__op-liste_20181107__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial transaction log with columns: [unknown], [transaction_id], [customer_name], [transaction_date], [debit], [credit]. No PII fields are present. Customer names appear to be business entities (companies) rather than personal names. All columns are skipped per rules: customer names are business names, dates are transactional timestamps, and amounts are financial data.

finanzen__mahnungen___alt__2014__op_20140320__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely transactional accounting data with no PII present. Columns are invoice identifiers (Freie Rg.-Nr.), customer short names (Kurzname), dates, open status flags, and monetary amounts. No personal identifiers such as names, addresses, emails, or phone numbers appear in the sample.

finanzen__mahnungen___alt__2014__op_20140320__Tabelle2.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely transactional financial data (invoice numbers, customer short names, dates, open amounts, total amounts). No PII fields are present. Column 'Kurzname' contains customer short identifiers (not full names), and all other columns are financial/timestamps. No emails, phones, addresses, SSNs, etc. visible in sample.

finanzen__mahnungen___alt__2014__op_20140820__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely transactional accounting data with no personal identifiers. Columns represent invoice numbers, due dates, payment terms, amounts, and customer short names (business identifiers, not personal names). No PII fields are present.

finanzen__mahnungen___alt__2014__op_20141024__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII columns detected. All columns represent internal financial records (status flags, reference numbers, company names, addresses, dates, and amounts). The 'Kurzname' column contains company/organization names, which are NOT personal PII under the defined rules. All data appears to be corporate financial metadata rather than personal customer data.

finanzen__mahnungen___alt__2014__op_20141024__open_20141024.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is purely transactional financial data with internal IDs, status flags, and dates. No PII fields detected — columns contain only internal reference numbers (Rg.-Nr., Freie Rg.-Nr.), customer short names (Kurzname), address references (Adress-Nr.), timestamps (Datum), and monetary values (Offen). No email, phone, DOB, name, or address details are present.

finanzen__mahnungen___alt__2015__op_20150303__op_20150303.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: No PII columns detected. File contains only transactional financial data (invoice numbers, dates, amounts) with business names. All columns map to skip categories per exclusion rules: business names, timestamps, transaction IDs, amounts. No personal identifiers present.

finanzen__mahnungen___alt__2015__op_20150529__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: All columns are internal accounting identifiers, timestamps, financial codes, and amounts. No PII fields (names, addresses, emails, phones, DOB, SSN, etc.) are present. Columns like 'Rg.-Nr.', 'Freie Rg.-Nr.', 'Kurzname', 'Adr.Nr. 2', 'Adress-Nr.', 'Datum', 'Fäll.-Datum', 'Zahlungskondition', 'Offen', 'In Zahlungslauf Nr.', 'Bel.-Nr.', 'Text', 'Konto', and 'Betrag' are all internal financial or transactional data, not personal information.

finanzen__mahnungen___alt__2015__op_20151231__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: All columns are internal financial identifiers, dates, amounts, and transaction codes. No PII fields present. Columns like 'Kurzname' appear to be internal customer codes rather than actual names. Dates are transactional timestamps, not DOB. Values are all numeric codes, financial amounts, or system timestamps with no personal information.

finanzen__mahnungen___alt__2016__op_20160321__OP_Liste_einfach.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a corporate financial record file containing only business entities and transaction metadata. All columns map to company names, invoice IDs, dates, and financial amounts. No personal identifiers (PII) are present. Columns 'status', 'mahnung', 'rg', 'date', 'id', 'company' contain business status flags, reminders, reference codes, timestamps, internal IDs, and corporate names respectively.

finanzen__mahnungen___alt__2016__oplist_20160824__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: All columns are internal financial identifiers, status flags, invoice metadata, or amounts. No PII fields detected. Columns like 'Rg. Nr.', 'Freie Rg. - Nr.', 'Kurzname' are internal reference codes or business names, not personal data. Timestamps are transactional dates, not DOB. Values are all numeric or status codes.

finanzen__mahnungen___alt__2016__oplist_20161101__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: No PII columns detected. All columns appear to be internal IDs, timestamps, product codes, financial amounts, and invoice references typical of corporate financial records. No personal names, addresses, emails, phone numbers, or other PII fields are present in the sample.

finanzen__planung__20030630_Budget_2003__Ausgaben.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__20030630_Budget_2003__Debitoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file contains only transaction records with payment references to businesses/organizations. No PII fields detected. Columns include OP number, dates, amounts, and descriptions referencing business entities (e.g., "Zahlung PROFITELAG").

finanzen__planung__20030630_Budget_2003__Debitoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely transactional financial data with company/organization names and amounts. No PII fields present. All entries are business-to-business invoices with corporate entity names (e.g., 'Claudio Prezzi', 'Gewerbeverein Volket', 'Confarma', 'Swissallfina'). These appear to be company names or department designations rather than personal identifiers. No emails, phone numbers, addresses, or other PII detected in the sample.

finanzen__planung__20030630_Budget_2003__Einnahmen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__20030630_Budget_2003__Kreditoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII fields detected. File contains only transaction IDs, dates, amounts, and payee names (company names). All payee names are corporate entities (e.g., 'PROFITEL', 'SSN', 'ALLIANZ') and do not contain personal identifiers. No emails, phone numbers, addresses, or other PII present.

finanzen__planung__20030630_Budget_2003__Kreditoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely financial accounting data with transaction IDs, dates, amounts, and vendor descriptions. No personal identifiers (PII) such as names, addresses, emails, or phone numbers are present. All entries appear to be corporate expenses, vendor payments, and tax calculations with no customer or employee PII exposed.

finanzen__planung__20030630_Budget_2003__Liquidit_tsplanung.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger with columns representing months and totals. All values are monetary amounts and accounting terms (Saldo, Einnahmen, Ausgaben). No PII fields are present. All columns are skip according to exclusion rules for financial/transactional data.

finanzen__planung__20030630_Budget_2003__Personalkosten.csv
1 column5 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header empty but values are full names like 'Brunner Mark', 'Leisi Martin'

Notes: Only column 0 contains PII (full names). Columns 1-12 are financial values (monthly amounts) with no PII. No emails, phones, addresses, or other PII present in this financial data snapshot.

finanzen__planung__20030630_Budget_2003__Zusammenzug.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial statement file with no PII columns. All columns represent accounting figures (accounts receivable/payable, income, expenses) in CHF with no personal or identifiable data. The data appears to be internal corporate financial records from Zynex's ERP system.

finanzen__planung__20030630_Budget_2003__k_nftige_Debitoren.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial record file with columns: OP. Nr. (operation number), Rg. Datum (posting date), Bez. Datum (posting date), Betrag (amount), Beschreibung (description). No PII fields present. All columns are internal financial identifiers, dates, amounts, and description text. No personal information such as names, addresses, emails, etc. is visible in the sample data.

finanzen__planung__20030630_Budget_2003__k_nftige_Kreditoren.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_1999__Budgetkontrolle_Nov99.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This file is purely financial data with budget and expense figures (Miete, Telefon, Porto, etc.). No PII fields are present. All columns contain numeric financial data or empty cells, consistent with accounting records from Zynex's internal financial statements spanning 2001-2020. No names, addresses, emails, or other personal identifiers appear in the sample rows.

finanzen__planung__Budget_1999__Budgetkontrolle_Okt99.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a financial budget spreadsheet with columns representing months (July, August, September, etc.), budget categories (Miete, Telefon, etc.), and financial figures. There are no PII fields present — all columns contain numeric financial data, budget totals, and accounting terms. No names, addresses, emails, or other personal identifiers are visible.

finanzen__planung__Budget_1999__Liquidit_tsplanung.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains financial records with month-wise accounting data in Swiss Francs (CHF). No PII fields are present. Columns represent financial metrics like cash flow, capital, revenues, rent, phone, and postage across months, and totals. All values are numeric monetary amounts or zero placeholders. No names, addresses, emails, or other personal identifiers are included.

finanzen__planung__Budget_1999__Lohnsystem.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial compensation/bonus report with no PII fields. Columns contain employee names (Urs, Mark, Martin, Corinne), salary brackets, and percentages — but these are role-based identifiers, not actual personal contact data. No emails, addresses, phone numbers, DOB, SSN, etc. present.

finanzen__planung__Budget_1999__Plan_ER.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial data file with no personal identifiable information (PII). The columns represent financial metrics such as profit/loss, revenue, expenses, and totals for different Zynex products/services across months. There are no columns mapping to PII fields like names, addresses, emails, etc.

finanzen__planung__Budget_2000__Ausgaben.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only financial transaction records with columns: OP. Nr., Rg. Datum (posting date), Bez. Datum (description date), Betrag (amount), Beschreibung (description). No PII fields are present. All columns are financial/timestamp data that must be skipped per exclusion rules.

finanzen__planung__Budget_2000__Debitoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger file with structured columns: OP. Nr. (transaction ID), Rg. Datum (posting date), Bez. Datum (booking date), Betrag (amount), and Beschreibung (description). No PII fields are present. All entries are business-to-business financial transactions with company names, amounts, and dates. No personal identifiers such as names, emails, addresses, or phone numbers appear in the visible 50 rows.

finanzen__planung__Budget_2000__Debitoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely transactional accounting data (invoices/payments) with company names and amounts. No personal PII fields are present. All entries are corporate entities (AG = Aktiengesellschaft, Swiss corporate form) and invoice references. No emails, phone numbers, addresses, or individual names appear in the sample.

finanzen__planung__Budget_2000__Einnahmen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only financial transaction records with no personal identifiable information. Columns include operational numbers, dates, amounts, and generic descriptions (e.g., 'NOREF Zahlung Switch', 'Darlehen UK'). No PII fields such as names, addresses, emails, or phone numbers are present.

finanzen__planung__Budget_2000__Kreditoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII columns detected. All values appear to be internal transaction IDs, dates, amounts, and payment descriptions. No names, emails, addresses, or other personally identifiable information are present in the sample rows.

finanzen__planung__Budget_2000__Kreditoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial transactions file with no PII. Columns include operational reference numbers (OP. Nr.), date fields (Rg. Datum, Bez. Datum), amounts (Betrag), and vendor descriptions (Beschreibung). No personal identifiers such as names, addresses, emails, or phone numbers are present. All entries describe corporate expenditures to third-party vendors (e.g., Anixter SA, Eidg. Steuerverwaltung, Swisscom) and do not contain customer or employee PII.

finanzen__planung__Budget_2000__Liquidit_tsplanung_alt.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial statement file showing account balances and revenue streams. No PII fields present - all columns contain monetary values and account labels. This matches the breach context of Zynex financial records (annual financial statements, billing data).

finanzen__planung__Budget_2000__Liquidit_tsplanung_neu.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger with columns representing months and financial figures (saldo, income, expenses). No PII fields are present. All columns are numeric financial data or empty strings.

finanzen__planung__Budget_2000__Personalkosten.csv
1 column6 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header is empty but values are full names like 'Leisi Martin', 'Brunner Mark', 'Giger Thomas', 'Gamma Marco', 'Käppeli Urs'

Notes: This is a financial record file showing monthly billing amounts for customers. Only column 0 contains PII (full names). All other columns are numeric financial data (monthly amounts) and should be skipped per rules.

finanzen__planung__Budget_2000__Zusammenzug.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely financial accounting data with no PII fields. Columns represent accounting entries like debtor balances, income, expenses, etc. No personal identifiers present.

finanzen__planung__Budget_2000__k_nftige_Debitoren.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely financial transactional data with invoice numbers, dates, amounts, and payment descriptions. No personal identifiers (PII) are present. All entries are corporate payments with generic business descriptions (e.g., "Restzahlung Katzenhus"). No emails, phone numbers, names, addresses, or other PII fields are visible in the first 50 rows.

finanzen__planung__Budget_2000__k_nftige_Kreditoren.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2000_alt__Liquidit_tsplanung.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger in German with columns representing months and totals. All values are numeric monetary amounts (Swiss Francs) with no personal identifiable information. Columns contain only financial aggregates like 'Saldo' (balance), 'Erlös Dienstleistungen' (service revenue), and monthly totals. No names, addresses, emails, or other PII fields present.

finanzen__planung__Budget_2000_alt__Lohnsystem.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial data file showing salary and bonus structures. No personal identifiable information (PII) is present. All columns represent financial metrics, employee roles, or summary totals, and contain no names, addresses, email addresses, phone numbers, dates of birth, or other PII fields. The columns are purely numerical or categorical and do not map to any PII fields.

finanzen__planung__Budget_2000_alt__Plan_ER.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial statement file with no personal identifiable information (PII). Columns contain only account names and monetary values representing financial data for different months and totals. No names, addresses, emails, or other PII fields are present.

finanzen__planung__Budget_2000_alt__Verkaufsziele.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial report showing monthly subscription counts for different Zynex product tiers. The first row appears to be a header in German, and subsequent rows contain only numeric counts (0, 1, 200, etc.). There are no personal identifiers, names, emails, or addresses present. All columns represent internal business metrics (product tiers and monthly subscription counts) and should be skipped per exclusion rules for company/business data.

finanzen__planung__Budget_2001__Ausgaben.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2001__Debitoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger with columns for OP. Nr., Rg. Datum, Bez. Datum, Betrag, and Beschreibung. There are no PII fields present in this dataset. All entries appear to be business transactions with company names and payment references, but no personal identifiable information (email, phone, name, address, etc.) is visible in the first 50 rows.

finanzen__planung__Budget_2001__Debitoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial record file with only business entities and amounts. No PII fields are present. The 'Beschreibung' column contains only company names and invoice references, not personal names or addresses. All columns are financial/transactional data that should be skipped according to the exclusion rules.

finanzen__planung__Budget_2001__Einnahmen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2001__Kreditoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII detected in first 50 rows. File contains only transactional financial data (payment references, amounts, dates) with no personal identifiers. All entries are payment references to businesses/organizations (ELVIA, LISTA, PROFITEL, etc.) and contain no names, addresses, emails, or other PII fields.

finanzen__planung__Budget_2001__Kreditoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger file with structured columns but no PII present. Columns include transaction reference numbers (OP. Nr.), date fields (Rg. Datum, Bez. Datum), monetary amounts (Betrag), and company names (Beschreibung). All entries are business-to-business transactions with corporate entity names, no personal identifiers. The values in the Beschreibung column are all company names (e.g., 'profiTEL AG', 'Cablecom Business AG') and public institutions, which are excluded by the 'Company' rule. No emails, phone numbers, addresses, or other PII appear in the sample.

finanzen__planung__Budget_2001__Liquidit_tsplanung.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only financial ledger data (saldo, debitoren, revenue, expenses) with no personal or identifiable information. All columns represent monetary values and financial categories, not PII.

finanzen__planung__Budget_2001__Personalkosten.csv
1 column6 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header empty but values are full names (e.g., 'Brunner Mark', 'Leisi Martin'). These are clearly person names, not company names. The pattern 'LastName FirstName' matches fullName field.

Notes: Only column 0 contains PII (full names). Columns 1-12 contain only numeric financial data (monthly amounts in CHF) with no personal identifiers. These are internal financial records from Zynex's billing system, not customer PII. No emails, addresses, phones, or other PII present in this dataset.

finanzen__planung__Budget_2001__Zusammenzug.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely financial accounting data (accounts payable/receivable, income/expense figures) with no personal or identifiable information. All columns represent numeric financial values and month names — no PII fields present.

finanzen__planung__Budget_2001__k_nftige_Debitoren.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2001__k_nftige_Kreditoren.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2002__Ausgaben.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2002__Debitoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII fields detected. File contains only transaction identifiers (OP. Nr.), dates, amounts, and payment descriptions. All entries appear to be business-to-business financial records with company names rather than personal customer data. No emails, phone numbers, names, addresses, or other PII present in the first 50 rows.

finanzen__planung__Budget_2002__Debitoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely transactional financial data (invoices) with no PII present. Columns contain internal reference numbers (OP. Nr.), dates, amounts, and company/client names used as business references. No email, phone, address, SSN, or other personal identifiers are present. All values are business entities or financial codes.

finanzen__planung__Budget_2002__Einnahmen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2002__Kreditoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII fields detected. The file contains only transactional accounting data (OP.Nr., dates, amounts, payment descriptions) with no personal identifiers such as names, addresses, emails, or phone numbers. All entries appear to be business-to-business payment records with generic customer names (e.g., PROFITEL, SSN, SWITCH) that do not constitute personal PII under the defined field types.

finanzen__planung__Budget_2002__Kreditoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial record file with columns: OP. Nr., Rg. Datum, Bez. Datum, Betrag, Beschreibung. No PII fields are present. All entries appear to be transactional data with company names and monetary amounts. No personal identifiable information (PII) such as names, addresses, emails, or phone numbers is visible in the first 50 rows.

finanzen__planung__Budget_2002__Liquidit_tsplanung.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial ledger with columns representing months and totals, containing only numeric monetary values (Saldo, Einnahmen, Ausgaben). No personal identifiable information (PII) is present. Columns are purely transactional/financial data, so all are skipped per exclusion rules (financial/transactional data).

finanzen__planung__Budget_2002__Personalkosten.csv
1 column6 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header blank but values are full names like 'Brunner Mark'

Notes: Only column 0 contains PII (full names). Columns 1-12 are numeric financial amounts for months Jan-Dec (Swiss Francs) — these are transactional data, not PII. No emails, phones, addresses, or other PII present.

finanzen__planung__Budget_2002__Zusammenzug.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger with columns representing account balances and transactions. No PII fields are present. All columns are financial metrics (e.g., Debitoren bez., Ausgaben) and contain numeric values or monetary amounts. No names, addresses, emails, or other PII are visible in the sample.

finanzen__planung__Budget_2002__k_nftige_Debitoren.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2002__k_nftige_Kreditoren.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2003__Ausgaben.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2003__Debitoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely transactional accounting data (payments/vouchers) with reference numbers, dates, amounts, and payee names. No PII fields are present - all entries are business-to-business commercial transactions recorded in Swiss Francs. Payee names like "Zahlung PROFITELAG" are company names, not personal identifiers.

finanzen__planung__Budget_2003__Debitoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file contains only financial transaction records with business names and amounts. No PII fields (emails, phone numbers, DOB, etc.) are present. All entries are company/business names or generic descriptions, which per rules must be skipped. No structured personal data to map.

finanzen__planung__Budget_2003__Einnahmen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2003__Kreditoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII columns detected. The file contains only transactional financial data (payment references, amounts, dates) without any personal or identifiable information about individuals. All entries appear to be business-to-business payment records with company names and reference numbers.

finanzen__planung__Budget_2003__Kreditoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger with columns: OP. Nr. (internal reference), Rg. Datum (posting date), Bez. Datum (description date), Betrag (amount), Beschreibung (description). No PII fields are present. All entries are business transactions with amounts in Swiss Francs (SFr.).

finanzen__planung__Budget_2003__Liquidit_tsplanung.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial ledger with month-by-month accounting entries (Saldo, Einnahmen, Ausgaben, etc.). No PII fields are present — all columns represent numeric financial data and account labels. Columns 0-1 contain account names/labels, columns 2-15 contain numeric values for months, and column 15 shows totals. No emails, names, addresses, or other PII appear in the sample.

finanzen__planung__Budget_2003__Personalkosten.csv
1 column5 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header is empty but values are full names (first + last)

Notes: All other columns are month-based financial figures (Jan..Dez) with numeric values — these are transactional amounts, not PII. No other columns contain names, emails, addresses, etc.

finanzen__planung__Budget_2003__Zusammenzug.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger showing monthly debit/credit balances in CHF with no personal identifiers. All columns represent accounting totals (e.g., 'Debitoren bez.' = debtor balances, 'Einnahmen' = receipts). No PII fields present.

finanzen__planung__Budget_2003__k_nftige_Debitoren.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only financial transaction records with operation number, date ranges, amounts, and descriptions. No PII fields (names, addresses, emails, etc.) are present. All columns are financial/transactional data and should be skipped per exclusion rules.

finanzen__planung__Budget_2003__k_nftige_Kreditoren.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2004__Ausgaben.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2004__Debitoren_bez..csv
3 columns0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Source columnMapped fieldConfidenceLLM assessment
0skiphighcolumn 0 contains internal reference numbers (OP. Nr.), not PII
3skiphighcolumn 3 contains amounts in CHF, not PII
4skiphighcolumn 4 contains transaction descriptions, not PII

Notes: This file contains only payment references and amounts with no personal identifiable information. All columns either contain internal reference numbers, monetary amounts, or transaction descriptions. No email addresses, phone numbers, names, addresses, dates of birth, SSNs, passwords, usernames, or other PII fields are present.

finanzen__planung__Budget_2004__Debitoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger containing only transactional data (reference numbers, dates, amounts, and company names). No PII fields (email, phone, name, address, etc.) are present. All entries are business-to-business transactions with corporate entity names, not personal identifiers. The 'Beschreibung' column contains Swiss company/voucher references, not personal data.

finanzen__planung__Budget_2004__Einnahmen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2004__Kreditoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII columns identified. File contains only transactional data (OP. Nr., dates, amounts, payment descriptions). No personal identifiers such as names, emails, addresses, etc. are present in the first 50 rows.

finanzen__planung__Budget_2004__Kreditoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger file with columns: OP. Nr. (internal operation number), Rg. Datum (posting date), Bez. Datum (booking date), Betrag (amount), Beschreibung (description). No PII fields present. All columns are internal financial identifiers, dates, amounts, and descriptions of transactions. No names, addresses, emails, phone numbers, or other PII are present.

finanzen__planung__Budget_2004__Liquidit_tsplanung.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only financial ledger data (Saldo, Einnahmen, Ausgaben, etc.) with numeric monetary values and internal accounting terms. No personal identifiable information (PII) fields such as names, addresses, emails, or dates of birth are present. All columns are financial totals or accounting categories and should be skipped.

finanzen__planung__Budget_2004__Personalkosten.csv
1 column3 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] Header is empty but values are full names (first + last) like 'Brunner Mark'

Notes: 13 columns total, only column 0 contains PII (full names). Columns 1-12 are numeric values for each month (Jan-Dez) representing internal financial counters/IDs — these are NOT personal PII and should be skipped. No emails, phones, DOB, or addresses visible.

finanzen__planung__Budget_2004__Zusammenzug.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial statement file with columns representing debtor/creditor accounts and monetary values. No PII fields are present. All columns are financial metrics and should be skipped.

finanzen__planung__Budget_2004__k_nftige_Debitoren.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2004__k_nftige_Kreditoren.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2005__Ausgaben.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2005__Debitoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: No PII detected. File contains only transactional financial data (invoice numbers, dates, amounts in CHF, payee names). Payee names are business entities, not personal identifiers. No email addresses, phone numbers, SSNs, or personal names present.

finanzen__planung__Budget_2005__Debitoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger containing only transaction IDs, dates, amounts, and business names. No personally identifiable information (PII) is present. All entries reference corporate entities (e.g., 'Gamma Marco', 'Bolero Lifestyle AG', 'Web Law GmbH') and contain no individual names, addresses, contact details, or other PII fields. The data represents business-to-business transactions from Zynex's ERP system.

finanzen__planung__Budget_2005__Einnahmen.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2005__Kreditoren_bez..csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only transaction records with payment references (e.g., "RAIFFEISENL / Zahlungslauf 2"). No personal identifiable information (PII) such as names, addresses, emails, or phone numbers is present. All entries are business-to-business payments to entities like banks, insurance companies, and service providers.

finanzen__planung__Budget_2005__Kreditoren_offen.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely financial transaction data with reference numbers, dates, amounts, and descriptions. No personal identifiable information (PII) fields are present. Descriptions contain company names and service references but no names, addresses, emails, phone numbers, or other PII fields. All columns map to skip categories (transactional/financial data).

finanzen__planung__Budget_2005__Liquidit_tsplanung.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial statement file with no PII columns. Columns represent accounting categories (Saldo, Einnahmen, Ausgaben) and monthly financial data (Jan, Feb, Mar, etc.). All values are numeric financial figures in CHF with no personal information.

finanzen__planung__Budget_2005__Personalkosten.csv
1 column3 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Source columnMapped fieldConfidenceLLM assessment
0fullNamehigh[0] header empty but values are full names like 'Brunner Mark', 'Leisi Martin', 'Poulton Dave'

Notes: Only column 0 contains PII (full names). Columns 1-12 are month-based numerical values (likely financial data), not PII. No emails, phones, addresses, or other PII fields present.

finanzen__planung__Budget_2005__Zusammenzug.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a financial ledger with columns for debtors, creditors, income, and expenses. There are no PII fields present in the header or sample data. All columns appear to contain financial aggregates or identifiers that do not map to personal data fields. The data structure is purely transactional/financial with no personal identifiers.

finanzen__planung__Budget_2005__k_nftige_Debitoren.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Budget_2005__k_nftige_Kreditoren.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__planung__Cashflow_2022_2023__Cashflow_2022.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial report with columns representing months and totals. No personal identifiable information (PII) fields are present. All columns contain numerical financial data (amounts, counts) and are therefore skipped per exclusion rules.

finanzen__planung__Cashflow_2022_2023__Cashflow_2022_Vorlage.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is a financial ledger with columns representing months and totals for various services. No personal identifiable information (PII) is present. Columns contain monetary values and service categories, not names, addresses, emails, or other PII fields.

finanzen__planung__Cashflow_2022_2023__Cashflow_2023.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial statement file with columns representing months and totals, containing only monetary values and service categories. No PII fields are present.

finanzen__planung__Cashflow_2022_2023__Erfolgsrechnung_2022.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial ledger file with account numbers, descriptions, and monthly balances. No PII fields present. All columns are internal financial data (account codes, account names, monthly transaction amounts) and should be skipped per exclusion rules.

finanzen__planung__gesamtuebersicht_projekte__Kunde_wirbt_Kunde.csv
6 columns9 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Source columnMapped fieldConfidenceLLM assessment
3lastNamehigh[3] values are family names (Mettler, Bosshardt, Forster, Müller, Heimgartner, Strebel, Stohler, Byell)
4firstNamehigh[4] values are given names (Bruno, Felix, Werner, Reto, Rolf, M., , Hanspeter, Roman)
5address1high[5] contains street addresses like 'Claridenstrasse 22', 'Kempttalstrasse 115', 'Zeppelinstrasse 12', 'Im Feld 402', 'Pfäffikerstrasse 6', 'Suhrhardweg 14', 'Industriestrasse 25', 'Horburgerstrasse 95', 'Hugostrasse 2'
6ziphigh[6] contains Swiss postal codes (8022, 8308, 8057, 4624, 8604, 5102, 4410, 8050)
7cityhigh[7] contains Swiss city names (Zürich, Illnau, Zürich, Härkingen, Volketswil, Rupperswil, Liestal, Basel, Zürich)
8emailhigh[8] contains valid email addresses (b.mettler@b-m-p.ch, info@bosshardt.ch, w.forster@ask-beratung.ch, info@centrachem.ch, info@struebingartenbau.ch)

Notes: CSV file with no header row. Columns contain Swiss business correspondence data from 1999. Columns 0-2 appear to be date, company name, and salutation respectively (non-PII). Column 1 contains business names, not personal names, so skipped. Column 8 sometimes empty but maps to email when present.

finanzen__planung__gesamtuebersicht_projekte__finances.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial/billing record file with columns in German. All visible columns represent transactional data (invoice dates, amounts, payment statuses), project names, and internal codes. No PII fields (names, emails, addresses, etc.) are present in the sample. Columns 1 and 2 appear to contain fragmented name fragments ('Nachname', 'Vorname') but these are not consistently populated with actual names across rows and seem to be placeholder labels rather than actual data. Given the context (Zynex corporate financial records) and absence of verifiable PII patterns, no columns map to PII categories. All columns are financial/transactional metadata or internal references.

finanzen__planung__gesamtuebersicht_projekte__techn._Daten.csv
2 columns18 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Source columnMapped fieldConfidenceLLM assessment
6ziphighheader "PLZ" resolves to PII field "zip"
10emailhighheader "eMail" resolves to PII field "email"

Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance

finanzen__planung__kosten_neue_bueros__Tabelle1.csv
0 rows

File structure

Notes: This is a free-form text document with no consistent column structure. It appears to be a financial report detailing office space costs, square meters, and rental expenses for Zynex. There are no identifiable PII fields in structured columns; the data is purely numerical and descriptive regarding property and costs.

finanzen__planung__verkaufsziele__Budget.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is not a PII-containing dataset. The file shows monthly sales figures (Oct–Jun) and marketing channel data for different Zynex product lines. All columns represent internal business metrics (sales counts, channels) with no personal identifiers. No email, phone, name, address, or other PII fields are present.

finanzen__planung__verkaufsziele__Kontr._Mt.-Q3.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is not structured PII data; it contains only internal financial records (budget/effectiv/differenz columns) for Zynex product lines. No personal identifiers (names, emails, addresses, etc.) are present. All columns represent internal accounting metrics and should be skipped.

finanzen__planung__verkaufsziele__Kontr._Mt.-Q4.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The data appears to be financial records from Zynex with German labels and numerical values. There are no identifiable PII fields in the visible structure, but the format lacks consistent delimiters and row patterns required for column mapping. The content consists of financial metrics like budget, actuals, and differences across months and quarters, not personal information.

finanzen__planung__verkaufsziele__Kontr._Wo.Q4.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is not structured PII data; the file appears to be internal corporate financial records showing subscription usage counts per service tier across date ranges. Column 0 contains service tier names (Mitarbeiter, Zynex One, etc.), and columns 1-13 contain numeric usage counts. No personal identifiers (names, emails, addresses, etc.) are present. This is purely operational/billing data without customer or employee PII.

finanzen__planung__verkaufsziele__Produkt.csv
0 rows

File structure

Notes: This is a free-form financial summary table with no consistent delimiter structure across rows. The data contains product names and pricing information but no PII fields. There are no structured columns to map, and the format does not meet criteria for CSV processing.

finanzen__planung__verkaufsziele__Vertriebskan_le.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file is not structured PII data. It appears to be a financial summary or sales channel breakdown report in German, showing percentages and totals for different sales channels (Mitarbeiter, Agenten, Wiederverkäufer, Projekte). There are no columns containing personal identifiable information (PII) such as names, emails, addresses, etc. The last column contains what looks like names (Martin, Mike, Corinne, Urs), but these appear to be aggregate labels for sales channels rather than actual personal records. Per the instructions, truly non-PII columns (including internal IDs, flags, counters, and aggregated reporting labels) should be skipped. Therefore, no PII columns are mapped.

finanzen__planung__zynex-liq-22__02.2025.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is unstructured financial data with no personal identifiers. All columns contain corporate financial metrics (e.g., revenue, factors, years) and internal accounting codes. No PII fields detected.

finanzen__planung__zynex-liq-22__06.2025.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be internal financial records with no personal identifiable information (PII). Columns contain financial descriptors, amounts, and dates, but no names, addresses, emails, phone numbers, or other PII fields. All columns map to skip categories (company data, financials, timestamps).

finanzen__planung__zynex-liq-22__07.2023.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only financial/transactional data (descriptions, amounts, years, conversion factors). No PII fields are present. All columns are internal financial records, timestamps, or flags, and thus should be skipped.

finanzen__planung__zynex-liq-22__09.2022.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial report with no personal identifiable information (PII). Columns contain corporate financial data, years, amounts, and labels in German. No names, addresses, emails, phone numbers, dates of birth, or other PII fields are present.

finanzen__planung__zynex-liq-22__09.2023.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be financial statements and internal corporate records from Zynex, not customer PII. Columns contain accounting entries (e.g., 'umsatz' = revenue), fiscal years, conversion factors, and monetary values in CHF. No PII fields (names, emails, addresses, etc.) are present. All columns map to skip categories: financial/timestamps/labels.

finanzen__planung__zynex-liq-22__10.2021.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is not PII data; it's financial/liquidity records from Zynex's corporate accounting. Columns contain liquidity descriptors, amounts, and accounting factors — no personal identifiers, names, or contact details. All columns map to skip per exclusion rules (financial/transactional data).

finanzen__planung__zynex-liq-22__10.2023.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is purely financial/operational corporate data with no personal identifiers. Columns contain financial terms, years, currency values, and internal accounting codes. No PII fields detected.

finanzen__planung__zynex-liq-22__12.2023.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be internal corporate financial records with no personal identifiable information (PII). Columns contain financial terms, years, amounts, and internal codes — all non-PII per exclusion rules. No emails, names, addresses, DOB, SSN, or other PII fields present. Columns are purely transactional/financial (e.g., 'umsatz' = revenue, amounts in CHF, years 2012–2015). All columns are skipped per rules for financial/transactional data and internal corporate metadata.

finanzen__planung__zynex-liq-22__20.10.2025.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial/projection table from Zynex's internal corporate records (not customer PII). Columns contain Swiss accounting terms (e.g., 'umsatz' = revenue), year references, and financial figures in CHF. No personal identifiers present — all entries are corporate financial data, projections, and internal codes. Columns with empty headers contain numeric values that are clearly financial amounts, not personal data. This matches the breach context of internal financial records spanning 2001–2020.

finanzen__planung__zynex-liq-22__B_ro.csv
1 rows

File structure

Notes: The provided text is free-form financial records with no consistent columnar structure or delimiter. It contains financial data, cost breakdowns, and property details but no identifiable personal information fields (PII). All lines have different structures and formats, with no repeating patterns that would allow column mapping. This qualifies as unstructured data per the criteria.

finanzen__planung__zynex-liq-22__budget.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains internal corporate financial records (budget, projects, income) with no personal identifiable information (PII). Columns describe financial categories (e.g., 'zynex budget', 'zynex aktuelle projekte', 'zynex einnahmen') and numerical values represent monetary amounts. No names, addresses, emails, phone numbers, or other PII fields are present. All columns are skipped per rules.

finanzen__projekte_nachkalkulation__Effizienz.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: This is an unstructured financial record file with no PII columns. The data appears to be internal corporate financial records (dates, monetary values, percentages) with no personal identifiable information. Columns contain timestamps, monetary amounts, and calculations typical of financial statements, but no names, addresses, emails, or other PII fields. The header row appears to be a continuation of data rather than actual column names.

finanzen__projekte_nachkalkulation__Nachkalk._Projekte.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains purely financial/project management data with no personal identifiers. Columns represent customer names (but these appear to be company/organization names rather than individual PII), project leaders (initials only), dates, financial figures, and status notes. No email addresses, phone numbers, SSNs, or other structured PII fields are present. The 'Kunde' column contains organization names rather than personal names.

finanzen__projekte_nachkalkulation__Tabelle1.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a financial/projection dataset with no personal identifiable information (PII). Columns include project names (Verein), offer amounts (Offerte), contract dates (Auftrag Datum), progress percentages (Stand %), effort estimates (Aufwand), financial differences (Differenz CHF/Differenz %), down payments (Anzahlung), and free-text notes (Bemerkungen). All data is corporate/project-related, with no names, addresses, contact info, or other PII fields.

finanzen__unfallmeldung.txt
1 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a German insurance claim notice with policy numbers and a web portal link, not tabular data. Contains no repeated structured columns — every line differs in content and length. Though no emails/phones are visible, the unstructured nature and lack of row structure trigger the unstructured pathway.

finanzen__wir__WIR_Lokale.txt
3 rows

File structure

Notes: Pre-LLM auto-detection: free-form text with visible emails / phones

finanzen__zed_files__2003__84944899.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger with no consistent columnar structure. Lines contain transaction IDs, dates, payment references, and amounts but no identifiable PII fields. No structured columns exist to map to PII categories.

finanzen__zed_files__2003__93966663.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent column structure. The file contains transaction records with fields like Beleg-Nr (invoice number), Valuta (currency), OP (operation), PK (project key), and Betrag (amount), but these are all business/transactional data. No PII fields are present. The format does not conform to a structured table with consistent delimiters and column positions.

finanzen__zed_files__2008__logfiles__08912807.log.csv
0 rows

File structure

Notes: The file is a free-form financial statement/protoll with no consistent column structure. It contains transaction details (Beleg-Nr, Valuta, OP, PK, Betrag) but no identifiable personal information fields. The format appears to be a printed protocol/report rather than structured data with columns.

finanzen__zed_files__2008__logfiles__10687888.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger document with no column structure. It contains transaction records with payment references (e.g., 'Zahlung RUBEAG', 'Zahlung DR.PETERW.J'), but no identifiable personal information is present. The format is unstructured text with no consistent delimiter or header, and does not contain embedded emails or phone numbers.

finanzen__zed_files__2008__logfiles__16932609.log.csv
0 rows

File structure

Notes: The file is a free-form financial statement with no consistent column structure. It contains transaction records with payment references (e.g., 'Zahlung HEIMGARTNER'), amounts, and dates, but lacks a repeatable delimiter or header. Though it contains business customer names, these are not personally identifiable individuals per the defined PII fields. No structured PII columns are present.

finanzen__zed_files__2008__logfiles__19448147.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction lines but no identifiable personal data (names appear to be business/customer references, not PII). The format is unstructured prose with tabular data embedded, but lacks headers or repeated column positions across lines. Per rules, this qualifies as unstructured text without column mapping.

finanzen__zed_files__2008__logfiles__20080711.log.csv
0 rows

File structure

Notes: This is a free-form financial statement document (Beleg-Nr, Valuta, OP, PK, Betrag) with no consistent columnar structure across lines. It contains payment records but no personal PII fields like names, addresses, or emails. The document is purely transactional with invoice numbers and amounts, typical of accounting ledgers. No structured columns exist to map to PII fields.

finanzen__zed_files__2008__logfiles__24213138.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protoll showing payment records with no consistent column structure. The data appears to be German-language accounting records with columns like Beleg-Nr (document number), Valuta (value date), OP (operation), PK (primary key?), Betrag (amount), Buchungstext (booking text), Skonto (discount), Erlm. (credit), noch offen (still open). There are no identifiable PII columns (names, emails, addresses) in this financial summary. The format is unstructured accounting prose rather than delimited records.

finanzen__zed_files__2008__logfiles__28224147.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent column structure. It contains transaction records with Beleg-Nr (invoice number), dates, amounts, and payee names, but no identifiable PII fields like email, phone, or addresses. The data appears to be corporate financial records without personal customer details.

finanzen__zed_files__2008__logfiles__29961598.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/proforma document with no consistent columnar structure. It contains transaction records with payment references but no identifiable personal information (names appear to be business entities). The format lacks delimiters and row consistency required for column mapping.

finanzen__zed_files__2008__logfiles__33979834.log.csv
0 rows

File structure

Notes: The file is a financial statement with structured columns (Beleg-Nr, Valuta, OP, PK, Betrag) but contains no personal identifiable information (PII). All entries are business transaction records with company names (MISTERCATER, FZ-ELEKTROA, etc.) and monetary amounts. No emails, phone numbers, names, addresses, or other PII fields are present. This is purely transactional accounting data.

finanzen__zed_files__2008__logfiles__35485175.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent columnar structure. It shows payment records with fields like Beleg-Nr (document number), Valuta (date), OP (transaction code), PK (customer code), and Betrag (amount). No identifiable PII columns are present in this structured tabular format. The data appears to be corporate financial records without customer names, addresses, or other PII.

finanzen__zed_files__2008__logfiles__37753540.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger document with no consistent column structure. It contains transaction records with reference numbers, dates, amounts, and payee names, but lacks a fixed delimiter or repeating column pattern across rows. The data appears to be a printed statement rather than structured CSV/TSV data.

finanzen__zed_files__2008__logfiles__46513874.log.csv
0 rows

File structure

Notes: This is a financial statement document in German showing payment records. It contains transaction IDs, dates, reference numbers, and amounts, but no identifiable personal information (PII). The format is free-form text with no consistent columnar structure — each line represents a payment entry with varying field positions. No emails, phone numbers, or other PII are visible in the sample.

finanzen__zed_files__2008__logfiles__48267595.log.csv
0 rows

File structure

Notes: File is a free-form financial statement/proforma with no consistent columnar structure. Contains payment records with business names (e.g., EGGENBERGER, WEBLAWAG) and amounts, but no identifiable personal PII fields. No emails, phone numbers, or other PII visible in the sample. Structured as narrative accounting lines rather than tabular data.

finanzen__zed_files__2008__logfiles__56287220.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger document with no consistent columnar structure. It contains transaction records with fields like reference numbers, dates, payment references, and amounts, but does not contain any identifiable personal information (PII). The format is unstructured prose with tabular data embedded in text, matching the unstructured opt-out conditions.

finanzen__zed_files__2008__logfiles__58037596.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger document with no consistent columnar structure. It contains transaction records with Beleg-Nr (document number), dates, reference codes, and amounts, but no identifiable personal information. The format shows accounting entries rather than structured personal data records.

finanzen__zed_files__2008__logfiles__58810935.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent column structure. It contains transaction records with fields like Beleg-Nr (voucher number), Valuta (value date), OP (operation), PK (customer reference), Betrag (amount), Buchungstext (transaction text), Skonto (discount), Erlm. (settlement), and noch offen (still open). These are business/financial identifiers and transactional amounts, not personal PII. No email addresses or phone numbers are visible in the sample. The data appears to be corporate accounting records from Zynex's FaktNT ERP system.

finanzen__zed_files__2008__logfiles__64055860.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent column structure. It contains transaction records with payment details but lacks a defined delimiter or header. While it contains business names (e.g., RUBEAG, ILLUMALICHT), these are not personal PII fields as defined in the schema. The data appears to be corporate financial records rather than individual customer PII.

finanzen__zed_files__2008__logfiles__70576135.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. The data shows payment records with fields like Beleg-Nr (document number), Valuta (currency date), OP (operation number), PK (customer number), and Betrag (amount). There are no identifiable PII fields such as names, addresses, emails, or phone numbers in this sample. The document appears to be an internal accounting summary from Zynex's financial records, showing payment transactions without personal customer details.

finanzen__zed_files__2008__logfiles__74584243.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protoll with no column structure. It contains transaction records (Beleg-Nr, Valuta, OP, PK, Betrag) but no identifiable personal information. The format lacks consistent delimiters or columnar structure across lines, and contains only business transaction data without PII fields. This qualifies as unstructured content per the rules.

finanzen__zed_files__2008__logfiles__76597037.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent columnar structure. It contains transaction records with payment details (Beleg-Nr, Valuta, OP, PK, Betrag) and payment text lines, but lacks any personal identifiable information (PII) fields like names, emails, or addresses. The data appears to be corporate financial records from Zynex, showing payments to various business entities, but no customer PII is present.

finanzen__zed_files__2008__logfiles__84361804.log.csv
0 rows

File structure

Notes: This is a financial statement document with payment records. No consistent column structure exists across rows — each line contains a different pattern of payment data without repeating fields. The file appears to be a printed report rather than a structured dataset. While it contains business names (e.g., GEWERBEVERE, TREUHANDBRU), these are not personal PII fields but rather entity names appearing in transaction contexts. No email addresses or phone numbers are visible in the sample.

finanzen__zed_files__2008__logfiles__87109981.log.csv
0 rows

File structure

Notes: This is a free-form financial transaction report with no column structure. It contains payment records (Beleg-Nr, Valuta, OP, PK, Betrag) but no personal identifiable information (PII). The data shows payments to entities like BARKENHAFEN, MÜLLERHISTO, SWISSMARKET, etc. There are no emails, phone numbers, names, or other PII visible in the sample. The format is a simple table with no headers or consistent delimiters beyond the lines, and all rows follow the same pattern of transaction details.

finanzen__zed_files__2008__logfiles__93129620.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/protokoll with no consistent columnar structure. Lines contain transaction entries with Beleg-Nr (voucher number), dates, OP codes, PK references, and amounts in CHF. No identifiable PII fields (names, emails, addresses, etc.) are present. All values represent business entity names (RUBEAG, SENSIRIONAG, etc.) and monetary amounts — these are not personal PII per Zynex breach context (customer SME billing records). The format is unstructured prose with tabular-like alignment but lacks true CSV/columnar data.

finanzen__zed_files__2008__logfiles__94390170.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent column structure. It contains transaction records with fields like Beleg-Nr (document number), Valuta (value date), OP (operation number), PK (customer number), and Betrag (amount), but these are internal business identifiers and financial data rather than personal PII. No personal identifiers (names, emails, addresses) are visible in the sample.

finanzen__zed_files__2008__logfiles__99656364.log.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. It appears to be a payment register or accounting document showing transaction details such as payment numbers, dates, reference codes, and amounts in Swiss Francs (CHF). There are no identifiable PII fields like names, emails, or addresses in this sample. The document is purely transactional and contains business financial data rather than personal customer information.

finanzen__zed_files__2009__log__00616864.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger document with no consistent columnar structure. It contains payment records with reference numbers, dates, and amounts, but no identifiable personal information such as names, addresses, or contact details. The format is purely transactional and lacks any PII fields. Since it has no consistent delimiter or columnar structure, it is classified as unstructured text.

finanzen__zed_files__2009__log__06834686.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__zed_files__2009__log__08646770.log.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure. Contains financial transaction records with payment entries but no identifiable PII columns. Values appear to be business names rather than personal PII. No email/phone patterns detected in sample.

finanzen__zed_files__2009__log__09847531.log.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. It contains transaction records showing payment amounts and customer names, but lacks a defined table format. The data appears to be a printed accounting report with no machine-readable structure.

finanzen__zed_files__2009__log__16393558.log.csv
0 rows

File structure

Notes: The file is free-form text with financial transaction records (no consistent column structure). Contains invoice numbers, dates, and amounts but no identifiable personal information. No email/phone visible. Classified as unstructured free-form text with no importable data columns.

finanzen__zed_files__2009__log__18130564.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger document with no consistent columnar structure. It contains transaction records with payment references (Beleg-Nr, Buchungstext) but no identifiable personal information in structured columns. The format appears to be a printed report rather than delimited data rows. No PII columns exist to map.

finanzen__zed_files__2009__log__18403072.log.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; appears to be a financial statement with payment records. No identifiable PII fields present in the visible data. The format is unstructured prose with tabular data embedded in text, not a delimited CSV/TSV structure.

finanzen__zed_files__2009__log__25151250.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/protokoll showing payment records. It contains no column structure, only transaction lines with Beleg-Nr, dates, PK references, and amounts. No PII fields are present. The content is purely transactional (payments, amounts, totals) with no names, addresses, or other personal data.

finanzen__zed_files__2009__log__27887289.log.csv
0 rows

File structure

Notes: This is a financial statement document with payment records. The format is not tabular (no consistent delimiter or column structure). It contains payment references, amounts, and customer names, but lacks structured PII fields like email or phone. No column mapping is possible as this is a free-form financial report with no repeating column structure.

finanzen__zed_files__2009__log__34909946.log.csv
0 rows

File structure

Notes: This is a free-form financial statement document in German with no consistent columnar structure. Contains only payment records with company names, dates, and amounts. No PII fields (names are business entities, not personal). No email/phone visible. Meets unstructured criteria: no shared delimiter, lines have varying shapes, no structured columns.

finanzen__zed_files__2009__log__35182992.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger with no consistent columnar structure. It contains transaction records with fields like Beleg-Nr (voucher number), Valuta (due date), OP (reference), PK (customer/account code), Betrag (amount), Buchungstext (transaction text), Skonto (discount), Erlm. (deductions), and noch offen (outstanding). No PII fields (names, addresses, emails, etc.) are present in the visible portion. The format is unstructured text, not CSV/TSV.

finanzen__zed_files__2009__log__37730166.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction records with Beleg-Nr (voucher number), dates, reference codes, and amounts in Swiss Francs (CHF). No identifiable personal information (PII) is present in this sample. The format is unstructured financial ledger data, not a delimited dataset with columns mapping to PII fields.

finanzen__zed_files__2009__log__42741992.log.csv
0 rows

File structure

Notes: The provided text is a financial ledger/report with payment records. There are no structured columns or headers present — it's free-form tabular data embedded in narrative text. While names appear in payment references (e.g., BRUNNERMARK, SENSIRIONAG), these are mixed into lines without consistent delimiters or column positions. The format lacks repeating column patterns across rows, confirming it should be treated as unstructured text for PII extraction via free-form processing.

finanzen__zed_files__2009__log__46477725.log.csv
0 rows

File structure

Notes: free-form text with no consistent columnar structure; contains payment records with company names but no personal PII fields

finanzen__zed_files__2009__log__49214679.log.csv
0 rows

File structure

Notes: The file is a free-form financial report with no consistent columnar structure. It contains transaction records with payment details but no identifiable personal information in structured columns. This appears to be an internal accounting document rather than customer PII data.

finanzen__zed_files__2009__log__54226085.log.csv
0 rows

File structure

Notes: The provided data is a free-form financial ledger with no consistent column structure. It contains payment records with entries like Beleg-Nr (voucher number), Valuta (date), OP (operation), PK (customer reference), and Betrag (amount). There are no identifiable PII fields such as names, addresses, or contact information in this sample. The data appears to be transactional records without personal identifiable information in the visible format.

finanzen__zed_files__2009__log__55962481.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent columnar structure. The file shows payment records with transaction IDs, dates, and amounts, but lacks any identifiable PII fields like names, addresses, or contact details. It contains only transactional data (Beleg-Nr, Valuta, OP, PK, Betrag) and totals, with no embedded emails or phone numbers visible in the sample. As per rules, unstructured files with no columnar structure return empty columns.

finanzen__zed_files__2009__log__59977041.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction lines with Beleg-Nr, Valuta dates, OP numbers, PK references, and monetary amounts, but lacks any personal identifiers like names, emails, or addresses. The data appears to be corporate accounting records rather than customer PII.

finanzen__zed_files__2009__log__63991118.log.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. It contains transaction records with payment references like "Zahlung HEIMGARTNER" but no identifiable personal data fields such as names, addresses, or contact information in a structured format. The content is purely transactional and financial, showing payment amounts and references without mapping to any PII categories. Since there is no consistent delimiter or column structure, this is classified as unstructured text.

finanzen__zed_files__2009__log__71273994.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/protokoll with no consistent column structure. It contains transaction records with payment amounts, dates, and company names, but no identifiable personal information in structured columns. The data appears to be corporate financial records rather than customer PII.

finanzen__zed_files__2009__log__73543974.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/protokoll with no consistent columnar structure. It contains transaction records with Beleg-Nr (voucher number), dates, amounts, and payee names, but lacks any identifiable personal data such as emails, phone numbers, or addresses in the visible rows. No structured columns exist to map to PII fields.

finanzen__zed_files__2009__log__75555808.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/protokoll with no consistent columnar structure. The data appears to be payment records with fields like Beleg-Nr (voucher number), Valuta (currency), OP (operation), PK (primary key), Betrag (amount), Buchungstext (booking text), Skonto (discount), Erlm. (releases), and noch offen (still open). There are no identifiable personal PII fields (emails, phone numbers, names, addresses) visible in this sample. However, company names like GEWERBEVERE, WEBLAWAG, TEKTONIMMOB, etc., are present but map to business entities (excluded by rules). No structured columns exist to map.

finanzen__zed_files__2009__log__76023115.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger with no consistent columnar structure. The file contains payment records with transaction numbers, dates, reference codes, and amounts, but lacks any identifiable personal information such as names, addresses, or contact details. It appears to be an internal accounting document from Zynex showing customer payments, but customer names are encoded as numeric codes rather than actual PII. There are no emails, phone numbers, or other personally identifiable data visible in the sample.

finanzen__zed_files__2009__log__82577220.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent columnar structure. The data consists of payment records with fields like Beleg-Nr (voucher number), Valuta (value date), OP (operation), PK (project code), and Betrag (amount). There are no identifiable PII fields such as names, addresses, emails, or phone numbers present in this structured financial summary. The entries appear to be business-to-business transactions without customer personal data.

finanzen__zed_files__2009__log__83308507.log.csv
0 rows

File structure

Notes: The provided data is a free-form financial statement with no consistent column structure. It contains payment records with fields like payment text, amounts, and dates, but no identifiable personal information (PII) such as names, addresses, or contact details. The format is not structured as CSV or any other tabular format; instead, it appears to be a printed report with lines and headers. Therefore, it is classified as unstructured text with no importable PII columns.

finanzen__zed_files__2009__log__91063290.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction records with fields like Beleg-Nr (voucher number), Valuta (date), OP (operation code), PK (customer/project code), Betrag (amount), Buchungstext (booking text), Skonto (discount), Erlm. (credit), and noch offen (outstanding). No PII fields (names, emails, addresses, etc.) are present. The data appears to be internal corporate financial records from Zynex, a Swiss web hosting company, as described in the breach context.

finanzen__zed_files__2009__log__92070685.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__zed_files__2010__log__01087884.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. It contains transaction lines with payment details but no identifiable PII fields. The format appears to be a printed accounting protocol with headers and footers, not a structured CSV/TSV. Since there are no repeating columnar patterns and the data is purely transactional (payment amounts, dates, reference numbers), we classify this as unstructured text. No emails, phones, or names are visible in the sample.

finanzen__zed_files__2010__log__06651241.log.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a financial statement/report with payment records rather than structured PII columns

finanzen__zed_files__2010__log__07817839.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no column structure. Contains transaction records with Beleg-Nr (voucher number), Valuta (value date), OP (operation), PK (primary key), and Betrag (amount). No PII fields are present. The document appears to be an accounting summary from Zynex's FaktNT ERP system showing payments processed, with totals and processing status. While it contains transaction data, there are no personal identifiers, email addresses, or phone numbers visible in the sample.

finanzen__zed_files__2010__log__09824371.log.csv
0 rows

File structure

Notes: free-form text with embedded names but no consistent delimiter or column structure

finanzen__zed_files__2010__log__16405801.log.csv
0 rows

File structure

Notes: This is a financial statement document with payment records. It contains no structured columns with PII data. The document shows payment entries with reference numbers, dates, amounts, and payee names, but these are business entities rather than personal identifiable information. The format is free-form text with no consistent column structure across lines.

finanzen__zed_files__2010__log__17126633.log.csv
0 rows

File structure

Notes: free-form financial ledger with no consistent column structure; contains transaction IDs, dates, amounts, but no PII fields. This is an internal corporate financial document from Zynex breach, not customer PII data.

finanzen__zed_files__2010__log__23701606.log.csv
0 rows

File structure

Notes: free-form financial transaction report with no consistent column structure. Contains payment records with company names but no personal PII fields. No delimited rows or headers present.

finanzen__zed_files__2010__log__24150460.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no column structure. It contains payment records with account numbers and amounts, but no identifiable personal information (PII) fields like names, emails, or addresses. The data appears to be corporate financial transactions rather than customer PII.

finanzen__zed_files__2010__log__33885032.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger with no column structure. Contains payment records with customer names (RUBEAG, MISTERCATER, SENSIRIONAG, etc.) but these appear as unstructured text rather than tabular data. The format shows transaction details without a consistent delimiter or header row. Contains no identifiable PII fields in structured format.

finanzen__zed_files__2010__log__36740906.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/protokoll with no column structure. It contains payment records with customer names (e.g., SWISS-SUPPO, CHRISTOPHHU) but lacks consistent delimiters or headers. The format is unstructured prose with tabular data embedded in text, matching the unstructured opt-out criteria due to variable line shapes and absence of a consistent delimiter pattern across rows.

finanzen__zed_files__2010__log__40465920.log.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains financial transaction records with payment references but no personal identifiable information (PII) fields. The data consists of payment vouchers with reference numbers, dates, amounts, and payer names that appear to be business entities rather than individuals. No emails, phone numbers, or other PII are visible in the sample.

finanzen__zed_files__2010__log__40906603.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. Contains payment records with business names (GEWERBEVERE, WEBLAWAG, etc.) but no identifiable personal PII fields like names, emails, or addresses. The data consists of transaction IDs, dates, reference numbers, and amounts in Swiss Francs (CHF).

finanzen__zed_files__2010__log__45482404.log.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__zed_files__2010__log__47206486.log.csv
0 rows

File structure

Notes: The provided content is a financial statement/protokoll showing payment records with invoice numbers, dates, and amounts. It contains no structured columns with PII fields like names, addresses, emails, etc. The data is purely transactional (Beleg-Nr, Valuta, OP, PK, Betrag) and lacks any personal or identifiable information. Therefore, no column mapping is possible or necessary.

finanzen__zed_files__2010__log__54234103.log.csv
0 rows

File structure

Notes: The provided file is a financial statement/proforma document in German. It contains transaction records with fields like 'Beleg-Nr' (voucher number), 'Valuta' (value date), 'OP' (operation number), 'PK' (customer/account number), and 'Betrag' (amount). There are no personal identifiers (PII) such as names, addresses, emails, or phone numbers present in the visible data. The document is purely transactional and financial in nature, listing payments made to various entities (e.g., WEBLAWAG, SENSIRIONAG, BERGMANNAG, etc.). The values represent monetary amounts and internal reference codes, not PII. As this is a structured financial record without any personal data fields, it should be handled as non-PII data.

finanzen__zed_files__2010__log__61961202.log.csv
0 rows

File structure

Notes: This is a financial statement document with no consistent columnar structure. It shows payment records with fields like payment text, amounts, and dates, but lacks identifiable personal information in a structured format. The document appears to be a payment register with transaction details rather than containing personal PII fields.

finanzen__zed_files__2010__log__68543668.log.csv
0 rows

File structure

Notes: free-form text with no consistent columnar structure; appears to be a financial statement/proforma with payment records. No identifiable PII columns are present. Contains only transaction IDs, dates, amounts, and company names (all non-PII per exclusion rules).

finanzen__zed_files__2010__log__72996730.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent column structure. It contains payment records with company names (JÄRIMANNAG, SILVINOAG, etc.) and amounts, but no identifiable personal PII fields like email, phone, or address. The data appears to be corporate customer payments rather than individual PII.

finanzen__zed_files__2010__log__75286528.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/protokoll document in German with no consistent columnar structure. It shows payment records with headers like Beleg-Nr (voucher number), Valuta (currency), OP (operation), PK (probably payment key), and Betrag (amount). All values are numeric or textual payment descriptions (e.g., "Zahlung BALGRISTAPO"). There are no identifiable PII fields like names, emails, or addresses. The document appears to be an internal accounting report from Zynex's FaktNT ERP system, listing customer payments without exposing personal customer data.

finanzen__zed_files__2010__log__75568898.log.csv
0 rows

File structure

Notes: This is a financial statement/protokoll with payment records. No consistent columnar structure exists — each line mixes transaction IDs, dates, reference numbers, and amounts in free-form text. Contains no personal identifiers (names, emails, addresses). Pure transactional data only.

finanzen__zed_files__2010__log__82016319.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/proforma with no consistent columnar structure. Rows contain payment references (Beleg-Nr, Valuta, OP, PK, Betrag) and payment text lines but no identifiable personal identifiers. No PII columns exist to map.

finanzen__zed_files__2010__log__84322022.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger/protoll document with no consistent columnar structure. It contains transaction records with payment references to companies (RANDOSAG, VIDEOOOGMBH, etc.) but no personal PII fields. The format is purely textual with lines of accounting data, not CSV/TSV. No structured columns exist to map.

finanzen__zed_files__2010__log__89607694.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent columnar structure. The data contains transaction records with fields like Beleg-Nr (document number), Valuta (value date), OP (operation), PK (reference number), and Betrag (amount), but these are all transactional/financial fields, not personal PII. No emails, phone numbers, or other PII are visible in the sample. The unstructured format and lack of identifiable personal data means we should not attempt column mapping.

finanzen__zed_files__2010__log__98076625.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger/protokoll document with no consistent columnar structure. It contains transaction records with Beleg-Nr (voucher number), Valuta (value date), OP (operation code), PK (primary key), Betrag (amount), Buchungstext (booking text), Skonto (discount), Erlm. (credit), and noch offen (outstanding). No personal PII fields are present — all entries are corporate payment references to entities like WEBLAWAG, TREUHANDBRU, GARAGET.SCH, etc. The format lacks delimited rows/columns and varies per line, qualifying as unstructured text per the rules.

finanzen__zed_files__2010__log__98358101.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent column structure. It contains transaction records with customer names (e.g., HEIMGARTNER, WITTICHWEIN), amounts, and dates, but lacks a defined delimiter or header row. The content is purely transactional data without any identifiable PII fields in a structured format. Per rules, unstructured files with no consistent delimiter and variable line shapes should return an empty columns object.

finanzen__zed_files__2011__log__06678663.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. It contains payment records with company names but no identifiable personal information. The format does not meet criteria for structured CSV/TSV parsing due to inconsistent fields and lack of repeating column positions.

finanzen__zed_files__2011__log__07398634.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent column structure. It contains transaction records with fields like Beleg-Nr (document number), Valuta (value date), OP (operation), PK (position key), Betrag (amount), Buchungstext (booking text), Skonto (discount), Erlm. (clearing), and noch offen (still open). No PII fields are present in a structured format; the data appears to be purely transactional and financial without any personal identifiers. However, due to the unstructured nature of the file (varying line formats and lack of consistent delimiter), it is classified as unstructured with no column mapping.

finanzen__zed_files__2011__log__07842793.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger document with no consistent columnar structure. The data consists of payment records with entries like transaction IDs, dates, amounts, and payee names. While it contains company names that could be considered PII in certain contexts, there is no consistent delimiter or row structure across lines, and no identifiable personal fields like email, phone, or address. The format is a simple text-based accounting report rather than structured tabular data.

finanzen__zed_files__2011__log__15421389.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger with no column structure. It contains payment records with account numbers and amounts, but no identifiable PII fields like names, emails, or addresses. The data appears to be payment confirmations with reference numbers and amounts in CHF, typical of corporate accounting documents. No structured columns exist to map to PII fields.

finanzen__zed_files__2011__log__20156587.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protoll showing payment entries. It contains no consistent columnar structure (just lines of transaction data with no shared delimiter or field positions). Though it has numeric values, these are transaction amounts and internal reference numbers, not personal PII. No emails, names, or addresses are visible. The format is unstructured prose with tabular data embedded, but lacks the consistent column alignment required for structured parsing. Per rules, we treat this as unstructured text with no column mapping.

finanzen__zed_files__2011__log__24171305.log.csv
0 rows

File structure

Notes: free-form financial ledger with no consistent column structure; contains transaction IDs, dates, amounts, but no identifiable personal data in this sample

finanzen__zed_files__2011__log__31191210.log.csv
0 rows

File structure

Notes: File is a free-form financial statement with no consistent columnar structure. Contains payment records but lacks any identifiable PII columns (names, emails, addresses). All data appears to be transactional IDs, amounts, and statuses. No emails or phone numbers visible in the sample.

finanzen__zed_files__2011__log__33911710.log.csv
0 rows

File structure

Notes: This is a free-form financial report showing payment records with no consistent columnar structure. The data contains transaction numbers, dates, payment amounts, and company names (WALZINGER, FZ-ELEKTROA, VERBANDSTAD, etc.), but lacks any identifiable personal PII fields like names, addresses, or contact information. The format is unstructured prose with tabular data embedded in text, and there are no repeated patterns that would allow mapping to PII columns. While company names are present, they are not mappable to the defined PII fields (which focus on individual person data).

finanzen__zed_files__2011__log__35471211.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent column structure. The data appears to be a payment register showing transaction IDs, dates, reference numbers, and amounts in CHF. No personal PII columns are present — all fields represent internal financial identifiers and monetary values. The structured format requirement is not met because there are no repeating columns or delimiters across rows.

finanzen__zed_files__2011__log__37775556.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no column structure. Contains payment records with company names and amounts, but no identifiable personal information (PII) in structured columns. The file consists of prose-style financial data with no consistent delimiter or row pattern.

finanzen__zed_files__2011__log__45506522.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__zed_files__2011__log__53254876.log.csv
0 rows

File structure

Notes: free-form text with no consistent columnar structure; contains payment records but no identifiable PII fields

finanzen__zed_files__2011__log__54967396.log.csv
0 rows

File structure

Notes: This is a free-form financial document/protoll with payment records. No consistent column structure exists across lines. Contains transaction IDs, dates, amounts, and error messages but no personal identifiers. Per rules, unstructured files with no column structure return empty columns object.

finanzen__zed_files__2011__log__62837721.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no column structure. It contains payment records with company names (e.g., GAUCHCAVEDE, ECMTGMBH) and monetary amounts, but no personal PII fields like names, addresses, or contact details. The data represents corporate transactions rather than individual customer PII, so no columns to map.

finanzen__zed_files__2011__log__62997918.log.csv
0 rows

File structure

Notes: The provided file is a financial transaction log with structured tabular data but contains no identifiable personal information (PII). All entries consist of payment references (names of businesses/organizations), transaction dates, invoice numbers, amounts, and payment statuses. No email addresses, phone numbers, names, addresses, dates of birth, SSNs, passwords, usernames, or other PII fields are present. The data represents corporate financial transactions without personal customer details.

finanzen__zed_files__2011__log__74305684.log.csv
0 rows

File structure

Notes: This is a free-form accounting document with no consistent columnar structure. Contains only financial transaction records (payment amounts, dates, reference numbers) without any personal identifiable information. No emails, phone numbers, or names are present in the visible sample. The data represents corporate payments processed by Zynex AG between June 22-30, 2011, showing customer names (RUBEAG, STEINMETZEX, etc.) which are company names rather than personal PII. No mapping to PII fields possible as this is not structured data.

finanzen__zed_files__2011__log__74586937.log.csv
0 rows

File structure

Notes: free-form text with no consistent column structure - financial statement lines with transaction codes and amounts, no personal identifiers visible

finanzen__zed_files__2011__log__77594718.log.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains only payment records with company names and amounts, no personal PII fields

finanzen__zed_files__2011__log__83338120.log.csv
0 rows

File structure

Notes: The provided text is a financial statement document (Beleg-Nr, Valuta, OP, PK, Betrag, Buchungstext, Skonto, Erlm., noch offen) showing payment records with customer names but no structured columns or delimiters. It contains no identifiable PII fields in a machine-parseable format. The document is purely transactional and financial in nature, listing payment details for various customers but does not expose email addresses, phone numbers, or other PII in a format suitable for structured parsing.

finanzen__zed_files__2011__log__91076578.log.csv
0 rows

File structure

Notes: This is a free-form financial report/protokoll with no columnar structure. It contains transaction records (Beleg-Nr, Valuta, OP, PK, Betrag) but no personal identifiable information (PII). The document appears to be an internal accounting statement from Zynex showing payments processed on 31.03.11, with customer names like WINTERBERGE, DALLMAYR, FLOORIGHT, and SISO-MECANI — these are business entities, not individuals. No emails, phone numbers, or other PII fields are present. The format does not meet criteria for CSV parsing; it is a narrative financial summary.

finanzen__zed_files__2011__log__92084271.log.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; contains financial transaction records without identifiable PII fields

finanzen__zed_files__2012__Log__05862236.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__zed_files__2012__Log__11725775.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent columnar structure. It contains transaction records with payment references (KARINAYARPU, WEINEWELSCH, etc.) but lacks any identifiable PII fields such as email, phone, or address. The data consists of payment amounts, dates, and internal reference codes only.

finanzen__zed_files__2012__Log__15741372.log.csv
0 rows

File structure

Notes: This is a financial ledger/protokoll document with no structured columns. It contains transaction records with payment texts (company names), amounts, and dates, but no personal PII fields like names, addresses, or contact details. The format is free-form tabular data without column headers or consistent field mappings.

finanzen__zed_files__2012__Log__16453668.log.csv
0 rows

File structure

Notes: This is a financial statement/protokoll showing payment records. There are no consistent columns — each line contains a payment entry with Beleg-Nr, Valuta date, OP number, PK, and Betrag. No PII fields (names, emails, etc.) are present in this structured financial data format. The content is purely transactional (payments, amounts, references).

finanzen__zed_files__2012__Log__24195291.log.csv
0 rows

File structure

Notes: The provided text is a financial statement/protokoll with structured tabular data but no identifiable personal or sensitive columns. It contains only transaction identifiers, amounts, and company names (e.g., LaCave Selection GMBH, BEGAIMMOBIL, FOTRA, etc.). These are business entities, not personal PII. The format is a free-form financial report with no consistent column structure for mapping PII fields. Therefore, it is classified as unstructured with no PII columns to map.

finanzen__zed_files__2012__Log__32932650.log.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains financial transaction records but no identifiable PII columns

finanzen__zed_files__2012__Log__33940405.log.csv
0 rows

File structure

Notes: free-form text with embedded company names and payment records; no consistent column structure exists. Contains payment references and company names but no identifiable PII fields.

finanzen__zed_files__2012__Log__40813660.log.csv
0 rows

File structure

Notes: free-form text with embedded company names and payment data; no consistent column structure or delimiter. Contains payment records with company names and amounts in Swiss Francs, but no identifiable PII fields.

finanzen__zed_files__2012__Log__50550727.log.csv
0 rows

File structure

Notes: File is a free-form financial report with no consistent column structure. Contains transaction IDs, dates, amounts, and company/client names (e.g., WEBLAWAG, MARTI-SYSTE, BERGMANNAG), but lacks any identifiable PII fields (email, phone, name, address, SSN, etc.). Values are business names/legal entity identifiers, not personal data. No structured columns to map.

finanzen__zed_files__2012__Log__53271534.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. It contains transaction records with Beleg-Nr (voucher number), dates, reference numbers, and amounts, but no identifiable PII fields. The document appears to be an internal accounting summary rather than customer/personal data records.

finanzen__zed_files__2012__Log__54279382.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__zed_files__2012__Log__62024101.log.csv
0 rows
Schema not yet detected for this file. Headers and field mappings will appear here once the LLM analysis completes.
finanzen__zed_files__2012__Log__76621368.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/proforma with no consistent columnar structure. Rows contain transaction IDs, dates, reference numbers, and monetary values but no personal identifiers. The format is unstructured prose with tabular data embedded in text lines.

finanzen__zed_files__2012__Log__85366456.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/protokoll with no consistent columnar structure. The data appears to be a payment register showing entries like 'Zahlung WEBLAWAG' with amounts and dates, but there are no repeating field positions or headers. While there are numbers that could be interpreted as dates or amounts, there is no identifiable PII in this sample (no emails, phones, names, addresses, etc.). The format is unstructured financial prose, not a delimited dataset.

finanzen__zed_files__2012__Log__87377866.log.csv
0 rows

File structure

Notes: The provided text is a financial statement/protokoll with payment records. It contains no consistent column structure — each line represents a payment entry with fields like Beleg-Nr (invoice number), Valuta (date), OP (transaction code), PK (reference number), and Betrag (amount). There are no identifiable PII fields (names, emails, addresses, etc.) in this excerpt. The document is purely transactional and financial in nature, listing payments to various entities (e.g., HEIMGARTNER, WITTICHWEIN). No column mapping is possible as the data lacks a tabular format with repeated columns.

finanzen__zed_files__2012__Log__94114646.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent columnar structure. It contains transaction records with payment details (Beleg-Nr, Valuta, OP, PK, Betrag) but lacks any personal identifiable information (PII) fields like names, emails, or addresses. The data appears to be corporate payment records without customer PII.

finanzen__zed_files__2013__Log__05305503.log.csv
0 rows

File structure

Notes: File is free-form text with no consistent columnar structure. Contains German financial transaction records (payments) with invoice numbers, dates, payee names, amounts. No header row exists. Sample lines show fields like Beleg-Nr (invoice number), Valuta (value date), OP (operation), PK (reference), Betrag (amount), Buchungstext (transaction text), Skonto (discount), Erlm. (settlement), noch offen (outstanding). These appear as free-form lines without a fixed delimiter pattern. Contains embedded payee names that could be PII but are not in a structured format.

finanzen__zed_files__2013__Log__05884389.log.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent column structure. It contains payment records with customer names (HEIMGARTNER, NYFELER+KEL, etc.) but lacks any structured headers or delimiters. The data appears to be a printed report with lines of text rather than a delimited dataset. Per requirements, unstructured files with no consistent row structure containing embedded PII should return empty columns object.

finanzen__zed_files__2013__Log__05892884.log.csv
0 rows

File structure

Notes: This is a free-form financial document (invoice/receipt) with no consistent columnar structure. It contains Swiss Francs (CHF) amounts, dates, and internal reference numbers, but no identifiable personal information (PII). The format appears to be a printed statement with lines of text rather than a delimited data file. Since there are no repeating columns or structured rows, this qualifies as unstructured content per the rules.

finanzen__zed_files__2013__Log__05902497.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent column structure. It contains payment records with business names and amounts but lacks any identifiable personal data fields like names, addresses, or contact information. The format is unstructured accounting data with no repeating column pattern across lines.

finanzen__zed_files__2013__Log__14607628.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__zed_files__2013__Log__14612109.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent columnar structure. The data consists of payment records with fields like Beleg-Nr (document number), Valuta (date), OP (operation number), PK (customer number), and Betrag (amount). There are no personal identifiers like names, emails, or addresses present in this excerpt. The data appears to be corporate billing records without PII.

finanzen__zed_files__2013__Log__15487111.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__zed_files__2013__Log__26638367.log.csv
0 rows

File structure

Notes: This is a free-form financial ledger with no consistent columnar structure. It contains payment records showing payment texts (e.g., "Zahlung WEBLAWAG"), amounts, and dates, but lacks any identifiable PII fields such as names, addresses, or contact information. The file represents transactional data without personal customer details embedded.

finanzen__zed_files__2013__Log__26657221.log.csv
0 rows

File structure

Notes: The file is a financial statement in German (Beleg-Nr, Valuta, OP, PK, Betrag, Buchungstext, Skonto, Erlm., noch offen). It contains only transaction data, payment references, and amounts with no personal identifiable information (PII). No emails, phone numbers, names, or addresses are present. The error message at the bottom references an internal system error (FZ-Communication: Beleg Nr. 5350) and does not contain PII. This is purely transactional accounting data.

finanzen__zed_files__2013__Log__26682733.log.csv
0 rows

File structure

Notes: This is a free-form financial report with no consistent column structure. It contains transaction records with reference numbers, dates, and amounts, but lacks any identifiable personal information (PII). The data appears to be corporate financial records showing payments processed, with no customer names, addresses, or other PII fields present. The format is not CSV or any structured tabular format — it's a human-readable financial statement with lines of text rather than columnar data.

finanzen__zed_files__2013__Log__53084043.log.csv
0 rows

File structure

Notes: The provided text is a financial ledger/protoll with payment records. It contains no structured columns — instead it's free-form tabular text with transaction lines. There are no personal identifiers (names, emails, etc.) visible in this sample. This is typical of accounting documents in the breach context (Zynex financial records).

finanzen__zed_files__2013__Log__53964289.log.csv
0 rows

File structure

Notes: This is a free-form financial statement/protokoll showing payment records. There is no consistent column structure — each line mixes transaction IDs, dates, amounts, and payee names in a non-tabular format. Though names appear (HEIMGARTNER, BERGMANNAG, etc.), they are embedded in prose-style lines without delimiters. The file lacks headers and row consistency required for structured parsing. Contains embedded personal names but must be processed as unstructured text via streaming extraction.

finanzen__zed_files__2013__Log__57449451.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent column structure. It contains transaction records without identifiable personal information (PII) fields like names, emails, or addresses. The data appears to be internal corporate financial records with invoice numbers, dates, and amounts in Swiss Francs (CHF).

finanzen__zed_files__2013__Log__57720460.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no column structure. It contains payment records with customer names (e.g., SCHWOAG, FELSENKELLE) but lacks any consistent delimiter or header-based structure across rows. The format is unstructured transactional data with no importable PII columns.

finanzen__zed_files__2013__Log__57769133.log.csv
0 rows

File structure

Notes: This is a free-form financial statement with no consistent columnar structure. It contains transaction records with Beleg-Nr (voucher number), Valuta (value date), OP (operation), PK (primary key), and Betrag (amount), but these are internal financial identifiers and transactional amounts rather than personal PII. No structured columns or PII fields (email, phone, name, address, etc.) are present. The data represents internal corporate financial records from Zynex's ERP system, not customer PII.

finanzen__zed_files__2013__Log__60332299.log.csv
0 rows

File structure

Notes: The file is a free-form financial ledger with no consistent column structure. Each line represents a payment record with fields like payment reference number, date, transaction ID, payee name, and amount. No identifiable PII is present in this sample (only business names), and the data lacks a consistent delimiter or header. Returns empty columns as per unstructured data rules.

finanzen__zed_files__2013__Log__60898055.log.csv
0 rows

File structure

Notes: free-form text with embedded emails / phones

finanzen__zed_files__2013__Log__81209758.log.csv
0 rows

File structure

Notes: This is a free-form financial statement document with no consistent columnar structure. The data appears to be a payment register with transaction IDs, dates, amounts, and payee names. No PII fields are present in structured format, and the document lacks repeated column patterns across lines. The content consists of payment references, amounts, and processing statuses rather than personal information.

finanzen__zed_files__2021__1630509719217.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210901_172159119_208.xml.bak__id.csv
0 rows

File structure

Notes: This is a single-line file containing a Swiss IBAN number (CH8704835061435161001). There is no structured data or delimiter pattern, and the content appears to be a standalone financial identifier rather than part of a dataset with columns. As per rules, unstructured free-form text with no consistent row structure should return an empty columns object.

finanzen__zed_files__2021__1630509719217.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210906_172221741_209.xml__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN (CH8704835061435161001). There is no structured table, header, or multiple rows to map. IBAN is a banking identifier, not personal PII, and cannot be mapped to any of the defined PII fields. The file is not CSV or any delimited structure; it is a standalone value.

finanzen__zed_files__2021__1630509719217.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210907_172127433_210.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File appears to be a header-only sample or corrupted. The first row shows 'id' and four 'INTERNAL' placeholders with no actual data columns or PII values. No mappable PII fields can be identified from this snippet. Likely a truncated or malformed file header.

finanzen__zed_files__2021__1630509719217.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210908_172027870_200.xml__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN number (CH8704835061435161001). There is no structured column data or header. The file appears to be a raw snippet of financial data rather than a delimited dataset. Since there are no consistent columns or structured rows, and the content is unstructured, we classify this as unstructured with no column mappings.

finanzen__zed_files__2021__1630509719217.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210910_172020475_206.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with three INTERNAL identifier columns. No PII values present in the first 50 rows. The file appears to be an internal reference sheet rather than actual customer data records.

finanzen__zed_files__2021__1630509719217.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210914_031204104_205.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row containing only column labels 'id' and multiple 'INTERNAL' placeholders. No PII values appear in the first 50 rows. All columns appear to be internal identifiers and thus should be skipped per exclusion rules.

finanzen__zed_files__2021__1630509719217.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210914_172139444_203.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (Swiss bank account number). No structured columns detected in the provided snippet. The content appears to be a single line with a bank account number rather than a delimited dataset. The breach context suggests financial records, but this snippet lacks structured columns.

finanzen__zed_files__2021__1630509719217.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210915_172157119_202.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header row with 'id' and three 'INTERNAL' labels. No PII fields are present in this snippet. Based on the breach context (Zynex internal corporate data), this appears to be an internal identifier column, which should be skipped per exclusion rules. No actionable PII columns detected in this row.

finanzen__zed_files__2021__1630509719217.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210916_172052602_211.xml__id.csv
0 rows

File structure

Notes: The provided sample is not a structured delimited file. It appears to be a single line containing an IBAN number (CH8704835061435161001) rather than a CSV or other structured format. Since there is no consistent delimiter, varying line shapes, and embedded financial identifier, this qualifies as unstructured data per the opt-out rules. No column mapping can be performed.

finanzen__zed_files__2021__1630509719217.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210917_172223885_207.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only row with placeholder 'INTERNAL' entries repeated five times, followed by an 'id' column label. No actual data rows are present in the first 50 rows, so no PII columns can be mapped. The structure indicates this is likely a metadata or schema file rather than actual records containing PII.

finanzen__zed_files__2021__1630509719217.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210920_172506645_204.xml__prtry.csv
0 rows

File structure

Notes: The provided sample shows only the word 'INTERNAL' repeated across rows with no actual structured data visible. This appears to be a placeholder or redacted header row without any real PII-containing columns. Since there is no consistent delimiter, no row structure, and no identifiable PII values, this qualifies as unstructured free-form text with no columns to map. The file likely contains only internal markers rather than actual breach data.

finanzen__zed_files__2021__1630509719217.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210921_172048284_201.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only file or contains only internal identifier columns labeled 'INTERNAL'. No PII fields are present in the first 50 rows. The columns are internal IDs and do not contain any personal information such as names, emails, addresses, or other PII. Therefore, no columns map to PII fields.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210922_172033212_201.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, not structured data

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210923_172150206_202.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row showing three internal identifier columns. No PII present. All columns are marked as skip due to 'INTERNAL' naming convention and no actual data values provided.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210924_172202405_203.xml__prtry.csv
0 rows

File structure

Notes: The file appears to be a headerless internal identifier file with no PII content. All values labeled 'INTERNAL' and no discernible structure or PII fields are present in the first 50 rows.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210927_172624994_200.xml__id.csv
0 rows

File structure

Notes: The provided sample is not a delimited file but rather a single line containing a Swiss IBAN (CH8704835061435161001). This is unstructured data with no column structure or multiple rows to analyze. IBANs are financial identifiers and not PII fields per the defined schema (they are bank account identifiers, not personal identifiers). Since there is no consistent delimiter, no header, and the sample is not structured tabular data, this is classified as unstructured text with no importable columns.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210928_172604537_206.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent delimiter or row structure is present across the lines; this is a single-line snippet of unstructured data, not a CSV.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210929_173144712_204.xml__id.csv
0 rows

File structure

Notes: This is a free-form text file containing a single IBAN value (CH8704835061435161001). There are no consistent delimiters or structured columns present. The file appears to be a simple data snippet or note rather than a tabular dataset.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210930_173523624_205.xml__id.csv
0 rows

File structure

Notes: The provided content appears to be a single unstructured line containing a Swiss IBAN number (CH8704835061435161001). This is not a structured dataset with columns; it is a single financial identifier. No consistent delimiter or header structure is present, and the sample does not exhibit any columnar format. The IBAN itself is financial data and not PII, so no mapping is required. Since this is unstructured and lacks any row structure, it is classified as unstructured with no columns to map.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211001_172152757_317.xml__id.csv
0 rows

File structure

Notes: This file contains only a single IBAN number (CH8704835061435161001) with no structured columns or row patterns. It appears to be a standalone financial identifier rather than a delimited dataset with PII columns.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211005_172035070_310.xml__id.csv
0 rows

File structure

Notes: This appears to be a single line containing only an IBAN number. There is no consistent delimiter or structured row format across the sample (only one line shown). The IBAN is a financial account identifier, not a PII field according to the rules, and there are no emails or phones visible. Since there is no structured format with columns, we treat this as unstructured text with no importable PII columns.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211006_172214517_320.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample contains only header labels 'id' and three 'INTERNAL' fields, which are clearly internal identifiers or non-PII corporate metadata. No PII fields are present in the visible rows. Based on the breach context (Zynex internal corporate data), these columns likely represent internal record IDs or system-generated keys, not personal data. All columns are marked as skip per exclusion rules for internal IDs.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211007_172622078_313.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only header row visible, no data rows provided. All visible columns are labeled 'INTERNAL' and appear to be internal identifiers. No PII columns detected in the header or sample.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211008_172552122_315.xml__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only a Swiss IBAN number (CH8704835061435161001). There is no structured delimiter, no header, and only one value present. IBAN is not a PII field per the defined schema, and the file lacks any row structure or additional data.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211011_172217407_311.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet contains only header labels 'id', 'INTERNAL', 'INTERNAL', 'INTERNAL' which are internal identifiers. No PII fields are present in this snippet. Based on the breach context (Zynex internal corporate data), these are likely internal record identifiers and not PII. No email, phone, name, address, DOB, SSN, or other PII fields are visible in this sample.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211012_172218980_319.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet only shows header labels 'id', 'INTERNAL', 'INTERNAL', 'INTERNAL' which are internal identifiers and do not contain any PII. No columns map to PII fields based on header names and available data. The file appears to be an internal corporate record file from Zynex with no personal customer data in this excerpt.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211013_172215536_308.xml__id.csv
0 rows

File structure

Notes: This appears to be unstructured free-form text with no consistent delimiter structure across rows. The sample shows a single line containing what looks like a Swiss IBAN (CH8704835061435161001), which is financial account information rather than personal PII. Since there is no consistent row structure and the content appears to be a single financial identifier line, this qualifies as unstructured data with no column mapping required.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211014_172024292_318.xml__prtry.csv
0 rows

File structure

Notes: This is a free-form text file with only header-like lines and no actual data rows. The lines shown are just headers or internal labels ("id", "INTERNAL"), and there is no actual structured data or PII present in the sample. Since there are no rows with consistent delimiter structure or embedded PII, this is classified as unstructured text without any importable columns.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211015_172119379_309.xml__id.csv
0 rows

File structure

Notes: free-form text with no consistent structure or columns. The sample contains only a single IBAN (CH8704835061435161001), which is not a PII field (bank account identifier, not personal). No email, phone, or other PII visible. This is likely a fragment of a financial record or invoice and does not constitute structured data with columns to map.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211018_172133623_312.xml__id.csv
0 rows

File structure

Notes: This is unstructured data containing only a single IBAN number. There are no structured columns or consistent delimiters present in the provided sample. The content appears to be a standalone financial identifier rather than part of a tabular dataset.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211019_172035648_316.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No structured columns present; this is a single-line record or fragment from a financial document, not a delimited file with repeated rows. IBAN is not a PII field per the defined schema.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211020_172047403_314.xml__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number. There are no structured columns or headers. The IBAN is not mapped to any PII field in our schema, and the content lacks any row structure or repeated patterns.

finanzen__zed_files__2021__1632324033311.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211021_172059932_307.xml__id.csv
0 rows

File structure

Notes: This is a free-form text file containing a single IBAN number (CH8704835061435161001) with no structured columns. The content does not exhibit any consistent delimiter or row structure across lines, and the sample provided is just one line of data. According to the unstructured opt-out rules, when the file is free-form text with no consistent structure and contains embedded PII-like data (here, an IBAN), it should be treated as unstructured. IBAN is not a defined PII field in the current schema, but the lack of structure triggers the unstructured pathway.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211029_172005613_200.xml__id.csv
0 rows

File structure

Notes: This is unstructured data — a single line containing an IBAN (CH8704835061435161001). There are no columns, headers, or structured records in the provided sample. The file appears to be a simple text file with one IBAN per line, not a CSV or other structured format. Since there is no consistent delimiter and no row structure, this is classified as unstructured. The IBAN itself is NOT mapped as PII in the columns object because unstructured files are handled by a streaming IBAN extractor.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211103_172053810_301.xml__id.csv
0 rows

File structure

Notes: The sample provided is a single line containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter structure or repeated rows, and the line does not contain any identifiable columns. The IBAN is a financial identifier and not considered PII under the defined categories. Since there is no structured data with columns, this is classified as unstructured text. No PII columns can be mapped.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211105_172054753_305.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) and no consistent delimiter structure across lines. This is not a structured CSV/TSV but a raw text snippet containing financial/accounting data from Zynex. No column mapping possible.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211109_172113278_310.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent columnar structure across lines. This appears to be a single-line data snippet or note, not a delimited file with rows. No CSV/TSV structure detected.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211111_172124266_302.xml__prtry.csv
0 rows

File structure

Notes: The provided sample appears to be a header-only snippet with no actual data rows. The first line 'id' and subsequent 'INTERNAL' entries suggest this is a metadata header or placeholder file, not a structured dataset containing PII. Without actual data rows to analyze, we cannot determine column mappings. The file appears to be a structural placeholder rather than containing personal data fields.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211112_172052007_304.xml__id.csv
0 rows

File structure

Notes: This is a free-form text file containing a single IBAN number (CH8704835061435161001). There is no structured column format, and the file appears to be a note or snippet rather than a dataset with rows and columns. The IBAN is a financial identifier, not personal PII under the defined categories, and thus is not mapped to any PII field.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211119_172110062_308.xml__id.csv
0 rows

File structure

Notes: This appears to be a single unstructured line containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or structured data format. The file is not CSV and contains no repeated patterns across rows (only one row shown). While IBANs can be considered PII in some contexts, the unstructured format and lack of repeated data structure trigger the unstructured handling path. The IBAN will be extracted via unstructured processing.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211123_172112851_309.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) — no consistent column structure visible in the sample. This is unstructured data requiring streaming extraction for any PII present.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211124_172113717_307.xml__id.csv
0 rows

File structure

Notes: The provided text is not structured tabular data. It appears to be a single line containing an IBAN (International Bank Account Number) rather than a delimited dataset with columns. There are no headers or repeated patterns indicating a CSV, TSV, or similar format. The IBAN itself is financial account information, but without structured columns, this file cannot be mapped to PII fields via column indices. This is classified as unstructured content per rules.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211125_172104359_306.xml__id.csv
0 rows

File structure

Notes: The provided sample is a single line containing an IBAN number (CH8704835061435161001) and no structured columnar data. There are no consistent delimiters or headers present, and the content appears to be unstructured financial data rather than a delimited table with PII fields. Since there is no evidence of a structured format with columns, this is classified as unstructured text.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211129_172137830_303.xml__id.csv
0 rows

File structure

Notes: This is unstructured text containing only a single IBAN value. No consistent columnar structure exists across lines; the file appears to be a raw data dump or snippet with no headers or delimiters. Per the unstructured opt-out rules, we return an empty columns object because there is no row structure to map.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211201_172049489_416.xml__id.csv
0 rows

File structure

Notes: The sample provided is a single line containing an IBAN number (CH8704835061435161001) rather than a delimited CSV file with columns. The IBAN is not classified as PII under the provided field types. The data appears to be unstructured and does not conform to a consistent row structure. No columns can be mapped to PII fields based on the available data and rules.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211202_172142339_413.xml__id.csv
0 rows

File structure

Notes: The provided sample is a single line containing an IBAN number (CH8704835061435161001), which is a financial identifier and not personal identifiable information (PII). The file appears to be unstructured data without any consistent column structure or header. Since there is no consistent delimiter or row structure, and the content is not structured as a CSV or other delimited format, it is classified as unstructured. No PII fields are present in the sample.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211203_172100133_411.xml__id.csv
0 rows

File structure

Notes: This is unstructured text containing only an IBAN (CH8704835061435161001) and no structured columns. It does not represent a delimited dataset with rows and columns. The file appears to be a simple snippet or note rather than a breach data file with multiple records.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211206_172032916_419.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, no consistent delimiter structure

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211207_172118270_418.xml__id.csv
0 rows

File structure

Notes: This file contains only a single IBAN (CH8704835061435161001) and no structured data. It is not a delimited file with columns; it is a standalone value. Since there is no consistent delimiter or header structure, and the data is not in a tabular format, it is classified as unstructured. However, the IBAN itself is not a PII field according to the provided list, so no PII columns are mapped.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211209_172137693_420.xml__id.csv
0 rows

File structure

Notes: The provided sample is not a structured file but a single line containing an IBAN number (CH8704835061435161001). There are no delimiters, headers, or repeated patterns indicating a CSV or other structured format. This appears to be a standalone financial identifier rather than part of a dataset with columns. Since there is no consistent row structure and the content is a single value, this qualifies as unstructured text with no importable data columns.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211210_172108097_412.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header labels 'id', 'INTERNAL', 'INTERNAL', 'INTERNAL' with no actual data rows visible. These appear to be internal identifier columns (likely numeric IDs) and do not contain any PII. No email, phone, name, address, DOB, SSN, or other PII fields are present in the visible headers or sample. All columns map to 'skip' per exclusion rules for internal IDs.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211213_172132054_417.xml__prtry.csv
0 rows

File structure

Notes: This is a header-only row with no actual data. The file appears to be a metadata or schema file rather than containing PII records. All entries are labeled 'INTERNAL' indicating they are likely internal identifiers or placeholders, not actual data fields. No PII is present in this sample.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211214_172114319_415.xml__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a single IBAN value rather than structured tabular data. No headers or repeated column patterns are present.

finanzen__zed_files__2021__1635520805755.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211215_172033122_414.xml__id.csv
0 rows

File structure

Notes: This appears to be a single line containing a Swiss IBAN number (CH8704835061435161001) rather than a structured dataset with columns. The context indicates this is from a corporate financial data breach of Zynex, a Swiss web hosting company, but this specific file contains no actual customer PII in a tabular format. It is likely a standalone financial record or fragment, not part of a delimited dataset with multiple columns of personal information. Since there are no repeated lines or consistent structure, and the sample shows only one line, this is classified as unstructured with no column mappings.

finanzen__zed_files__2021__1639671612377.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211216_172011901_201.xml__prtry.csv
0 rows

File structure

Notes: This is a free-form text file containing only internal identifiers and headers with no actual PII data in the first 50 rows. The file appears to be a header-only or metadata file from the Zynex breach, with no structured records containing personal information. The lines shown are just repeated 'INTERNAL' values and no actual data rows exist in the sample.

finanzen__zed_files__2021__1639671612377.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211217_172017074_205.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with no data. The headers are all marked as INTERNAL identifiers and do not contain any PII fields. No mapping is possible as there are no actual data rows to analyze.

finanzen__zed_files__2021__1639671612377.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211220_172028728_208.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample appears to be a header row with only internal identifiers (labeled 'INTERNAL'). No PII fields are present in this row. The data structure suggests this is the beginning of a structured file, but no actual PII columns are visible in the first row. Additional rows are needed to identify PII columns.

finanzen__zed_files__2021__1639671612377.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211222_172201042_202.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001), not structured rows

finanzen__zed_files__2021__1639671612377.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211223_172101933_203.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is a header-only snippet showing only internal identifier columns labeled 'INTERNAL'. No PII fields are present in this sample. All columns appear to be internal IDs which must be skipped per exclusion rules.

finanzen__zed_files__2021__1639671612377.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211224_172058744_207.xml__id.csv
0 rows

File structure

Notes: The sample provided is not a delimited file but appears to be a single line containing an IBAN number (CH8704835061435161001). There is no consistent structure or multiple rows to analyze for column mapping. This is likely part of an unstructured financial record or note rather than a structured dataset with columns. No PII columns can be mapped from this snippet alone.

finanzen__zed_files__2021__1639671612377.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211228_172147586_200.xml__id.csv
0 rows

File structure

Notes: This file contains unstructured data: a single IBAN value 'CH8704835061435161001' which is a Swiss bank account number. There is no consistent delimiter or structured column format. The content appears to be a financial record from the Zynex breach, but it lacks any row structure or identifiable PII fields beyond the IBAN itself, which is not classified as PII in the provided field types.

finanzen__zed_files__2021__1639671612377.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211230_172140335_204.xml__id.csv
0 rows

File structure

Notes: This is a single-line file containing a single IBAN (CH8704835061435161001). There are no structured columns, headers, or multiple rows. IBAN is a bank account identifier, not personal PII per the defined fields. Since there is no structured data (no consistent delimiter, no header, and only one line), this is classified as unstructured. No PII fields can be mapped.

finanzen__zed_files__2021__1639671612377.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211231_172025934_206.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (not email/phone). No consistent columnar structure across lines — this appears to be a raw dump or note file, not structured records. IBAN is financial data, not PII under our mapping rules (not email, phone, name, address, etc.). No actionable PII columns to map.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210831_172002686_200.xml__id.csv
0 rows

File structure

Notes: The provided text is a single line containing only an IBAN number (CH8704835061435161001). This is not a structured dataset with columns; it appears to be a fragment of financial data or a note, not a delimited file with headers or rows. Since there is no consistent delimiter, no header, and the content does not represent a table of records, this is classified as unstructured. The IBAN itself is financial data and not a PII field per the provided rules (it maps to skip under financial/transactional data). No PII columns can be mapped.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210901_172159119_208__id.csv
0 rows

File structure

Notes: This is a single-line unstructured data fragment containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or row structure present in the sample. IBAN is a financial identifier and not considered PII per the exclusion rules, so no columns need mapping.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210906_172221741_209__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured data or header present. The file appears to be a fragment or note rather than a dataset with columns. Since there is no consistent row structure and only one line, it qualifies as unstructured content. No PII columns can be mapped.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210907_172127433_210__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only row or placeholder with no actual data rows. The headers ('id', 'INTERNAL' repeated three times) suggest this is likely an internal identifier column that should be skipped per rules. No PII fields are present in the visible structure.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210908_172027870_200__id.csv
0 rows

File structure

Notes: The provided data is a single line containing an IBAN number (CH8704835061435161001) without any structured columns or delimiters. This appears to be a free-form text snippet rather than a structured dataset. Given the context of a breach involving financial records, this IBAN is likely part of financial transaction data, but as a standalone line it cannot be mapped to columnar PII fields. The file should be processed as unstructured content for potential extraction of financial identifiers.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210910_172020475_206__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with placeholder column names 'id', 'INTERNAL', 'INTERNAL' repeated three times. No PII fields are present in the header or visible in the sample. The data appears to be internal identifiers only. No further rows were provided to analyze actual values.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210914_031204104_205__prtry.csv
0 rows

File structure

Notes: This is a free-form text file containing only the word "INTERNAL" repeated across lines. No structured columns or PII present. The file appears to be a placeholder or metadata artifact rather than actual data records. No emails, phones, or other PII are visible.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210914_172139444_203__id.csv
0 rows

File structure

Notes: This is a single line of unstructured data containing a Swiss IBAN (CH8704835061435161001). There is no structured tabular format, and the data is not part of a breach record with identifiable columns. The IBAN is a bank account identifier and not classified as PII under the provided categories. No PII fields are present.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210915_172157119_202__prtry.csv
0 rows

File structure

Notes: The provided data appears to be unstructured. The first line shows 'id' followed by four occurrences of the word 'INTERNAL', indicating this is not a structured CSV with columns. There is no consistent delimiter or header structure visible in the sample. Since this is unstructured data with no identifiable PII in the visible portion, we return an empty columns object.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210916_172052602_211__id.csv
0 rows

File structure

Notes: This is a free-form text file containing unstructured data. The snippet provided is a single line with an IBAN (CH8704835061435161001), which is not considered PII in this context as it is not mapped to any personal or identifiable information in the given data. No consistent columnar structure is present, and the content appears to be a note or fragment rather than a structured dataset. Therefore, it is classified as unstructured with no column mappings.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210917_172223885_207__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only file or a metadata file with only internal identifiers. All columns are marked as INTERNAL and contain no PII values in the sample. No PII fields can be mapped based on header names or sample data.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210920_172506645_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet showing only internal identifier columns labeled 'INTERNAL'. No PII fields are present in this sample. All columns are internal IDs and should be skipped per exclusion rules.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20210921_172048284_201__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet shows only header rows with 'INTERNAL' repeated, indicating no actual PII data is present in this sample. The headers suggest internal identifiers only, which map to skip columns per rules. No actionable PII columns are visible.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211029_172005613_200__id.csv
0 rows

File structure

Notes: The provided content appears to be a single line containing an IBAN number (CH8704835061435161001) and does not exhibit any structured tabular format. There are no consistent delimiters, headers, or repeated patterns across rows. This is not a delimited CSV/TSV file but rather a standalone financial identifier. Since it lacks any row structure or repeated patterns, it is classified as unstructured free-form text. No column mapping is possible.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211103_172053810_301__id.csv
0 rows

File structure

Notes: The provided data is unstructured free-form text containing only a Swiss IBAN (CH8704835061435161001). There is no consistent columnar structure, and the content appears to be a single line or note rather than a delimited dataset with multiple rows. This matches the unstructured opt-out condition: no shared delimiter, variable line shapes, and no visible PII beyond the IBAN (which is not a field we map as PII in our schema).

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211105_172054753_305__id.csv
0 rows

File structure

Notes: This is a single line containing only a Swiss IBAN number (CH8704835061435161001). There is no structured data, header, or delimiter present. The line appears to be a standalone financial identifier rather than part of a dataset with columns. Since there is no consistent row structure or multiple columns, this qualifies as unstructured text with embedded financial data. However, IBANs are not mapped to any PII field in the current schema.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211109_172113278_310__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) and no consistent row structure. No CSV columns to map.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211111_172124266_302__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only file or metadata file with no actual data rows. The first row shows column names that are all marked as INTERNAL and appear to be internal identifiers rather than PII. No PII fields are present in this header structure.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211112_172052007_304__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN value CH8704835061435161001, no structured columns visible

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211119_172110062_308__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, no consistent delimiter structure. Single line of data without column headers or repeating patterns. IBAN is financial account number, not PII per exclusion rules (skip).

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211123_172112851_309__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN (CH8704835061435161001) and no structured data. There are no consistent columns or delimiters, and the content is not in a tabular format. The IBAN is not classified as PII in the current field definitions, so no columns are mapped.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211124_172113717_307__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, no consistent column structure visible in the sample

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211125_172104359_306__id.csv
0 rows

File structure

Notes: The provided sample is a single line containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter or structured format, and the line does not contain any other identifiable PII such as email or phone. However, IBANs are financial account identifiers and not classified as PII in the provided field types. Since there is no row structure and the sample does not meet the criteria for a CSV or other structured format, it is classified as unstructured. No columns are mapped as there is no consistent structure to analyze.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211129_172137830_303__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN number (CH8704835061435161001). No structured columns or headers are present. Per the unstructured opt-out rule, return an empty columns object.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211201_172049489_416__id.csv
0 rows

File structure

Notes: The provided sample appears to be free-form text containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter, no header, and the line structure varies. Since the file is unstructured with no consistent columns and only contains an IBAN (which is financial data and not a PII field per the exclusion rules), it is classified as unstructured. However, IBANs are typically skipped per exclusion rules (financial/transactional data). No PII columns are present.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211202_172142339_413__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (not email/phone). No consistent columnar structure detected across lines. Values appear as a single IBAN line only.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211203_172100133_411__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN (CH8704835061435161001). There are no consistent columns or structured data — this appears to be a standalone financial identifier from the Zynex breach context, not a dataset with PII fields. No column mapping is possible or needed.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211206_172032916_419__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN (CH8704835061435161001) and no structured columns. It does not represent a delimited dataset with rows and columns. As per the rules, unstructured files with no consistent delimiter structure should return an empty columns object.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211207_172118270_418__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured tabular data or header present in the provided sample. The file appears to be unstructured text containing financial/banking identifiers rather than personal PII records. No column mapping is possible as there is no columnar structure.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211209_172137693_420__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent column structure or delimiter detected across lines. File appears to be a raw note or log entry rather than structured records. IBAN is not a PII field in the defined schema and should be handled separately if needed.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211210_172108097_412__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only line or a metadata line with placeholder column names 'id', 'INTERNAL', 'INTERNAL'. No actual data rows are provided, and no PII fields can be mapped from this header alone. Additional rows with real data are required for accurate column mapping.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211213_172132054_417__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is not structured PII; it's a header row indicating internal IDs only. All columns are marked as INTERNAL and contain no actual PII values in the sample. No PII fields can be mapped from this header alone.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211214_172114319_415__id.csv
0 rows

File structure

Notes: The provided content is a single line containing an IBAN number (CH8704835061435161001) and no structured delimiter or header. This is a single value file, not a multi-column dataset. No PII columns can be mapped as there is no columnar structure to analyze.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211215_172033122_414__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing a single IBAN value (CH8704835061435161001). There are no columns, headers, or structured data — it is simply a standalone financial identifier. No PII fields are present in a structured format; the IBAN itself is not considered PII under the defined schema. Therefore, no columns are mapped.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211216_172011901_201__prtry.csv
0 rows

File structure

Notes: The file contains only unstructured header-like labels ('id', 'INTERNAL') repeated and no actual data rows. There are no visible PII values, and the structure appears to be a placeholder or metadata header without actual records. Since there is no consistent row structure with data, and no embedded emails/phones visible, this is classified as unstructured with no columns to map.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211217_172017074_205__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header-like lines that are internal identifiers or placeholder text, with no actual data rows visible. The lines 'id' and 'INTERNAL' repeated four times indicate this is a metadata header section or placeholder, not actual PII-containing columns. No PII fields can be mapped from this snippet alone.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211220_172028728_208__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only snippet or placeholder. The first row shows 'id' and three 'INTERNAL' labels, but no actual data rows are present to analyze column mappings. Without data rows, no PII fields can be identified or mapped. This is likely just a schema definition or placeholder file, not actual breach data containing personal information.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211222_172201042_202__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN but no consistent column structure

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211223_172101933_203__prtry.csv
0 rows

File structure

Notes: The file appears to be unstructured and contains only internal identifiers with no PII visible. The lines are not structured data rows but rather internal labels or metadata. No email addresses, phone numbers, or other PII are present in the sample.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211224_172058744_207__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001) which is a bank account identifier, not personal PII. The file appears to be a fragment of financial data without any structured columns or headers. No PII fields can be mapped from this snippet.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211228_172147586_200__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent column structure or header present; this is unstructured data containing only a single IBAN value which is not part of the defined PII fields. No emails, phones, or other PII visible in the sample.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211230_172140335_204__id.csv
0 rows

File structure

Notes: The provided sample is not a structured dataset but a single IBAN value. The breach context describes internal corporate financial records (annual financial statements, billing, invoices) for Zynex, a Swiss web hosting/CMS company, spanning 2001–2020. The sample shows a single IBAN (CH8704835061435161001), which is a financial account identifier, not personal PII. Since there is no consistent columnar structure in the sample and only a single line of data is provided, this is classified as unstructured. The full dataset likely contains structured financial records (e.g., invoices, billing, customer subscriptions), but this specific snippet is not sufficient for column mapping. The IBAN itself is not mapped to any PII field because it is an account identifier, not personal data like name, address, or email.

finanzen__zed_files__2021__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20211231_172025934_206__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001) with no other content. There are no structured columns, headers, or multiple rows present in the provided sample. The file appears to be free-form text containing only this IBAN value.

finanzen__zed_files__2022__1641226923150.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220103_172203034_200.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File appears to be a header-only file or corrupted. The first row shows only the string 'id' and three 'INTERNAL' placeholders, with no actual data rows or column structure visible. No PII can be mapped from this snippet.

finanzen__zed_files__2022__1641226923150.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220105_172204631_207.xml__id.csv
0 rows

File structure

Notes: This is unstructured financial/operational data (IBAN number) with no consistent row structure or PII columns. The sample shows only a single IBAN value 'CH8704835061435161001' which is not a PII field. No column mapping possible.

finanzen__zed_files__2022__1641226923150.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220106_172009697_205.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is only a header row with placeholder column names 'id', 'INTERNAL', 'INTERNAL', 'INTERNAL'. No actual data rows or PII values are present in the sample. Without real data rows containing PII values, no columns can be mapped to PII fields. This appears to be a structural placeholder row rather than actual data content.

finanzen__zed_files__2022__1641226923150.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220107_172026691_208.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only internal identifier columns labeled 'INTERNAL' repeated five times. No PII fields are present in the visible rows. The data appears to be internal IDs only, with no emails, names, addresses, or other PII visible in this snippet. All columns are marked as skip per rules for internal IDs.

finanzen__zed_files__2022__1641226923150.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220110_172115153_201.xml__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN (CH8704835061435161001). There is no structured data, header, or multiple rows. The IBAN is not considered PII for mapping purposes under the exclusion rules (financial/transactional data). Since this is unstructured free-form text with no consistent delimiter or row structure, we return an empty columns object.

finanzen__zed_files__2022__1641226923150.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220112_172043678_206.xml__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) rather than a structured table with columns. The data appears to be a snippet of financial data from the Zynex breach, but it does not contain a header or multiple rows to map into columns. As there is no consistent row structure, and this appears to be a single value line, we classify this as unstructured text with embedded financial identifiers. However, since IBAN is not one of the defined PII fields in the schema, no columns are mapped.

finanzen__zed_files__2022__1641226923150.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220113_172048382_203.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent column structure detected; appears to be a single line containing only a Swiss bank account number. This matches the breach context of Zynex financial records with IBANs visible.

finanzen__zed_files__2022__1641226923150.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220114_172201195_204.xml__id.csv
0 rows

File structure

Notes: This is unstructured free-form text containing only an IBAN number. No consistent delimiter or row structure exists across the sample. The content appears to be a snippet from financial records with no identifiable PII fields beyond the IBAN, which is not classified as PII in the provided schema. Since there are no emails, phones, or other PII visible and the format lacks structure, this is correctly classified as unstructured.

finanzen__zed_files__2022__1641226923150.054QR__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220117_172201635_202.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with placeholder column names 'id', 'INTERNAL', and 'INTERNAL' repeated. No actual data rows provided to map to PII fields. The file appears to be a metadata or schema definition rather than containing personal data records.

finanzen__zed_files__2022__1643818864652.054QR-2202__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220202_172104394_204.xml__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number (CH8704835061435161001) with no structured columns, headers, or additional data. IBAN is a financial identifier, not PII, and is excluded per rules. The file lacks any row structure or multiple fields, so it is classified as unstructured with no PII columns to map.

finanzen__zed_files__2022__1643818864652.054QR-2202__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220207_172051079_206.xml__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001), which is NOT considered PII under the rules provided (financial identifiers are excluded). No structured columns or PII fields are present in the first 50 rows.

finanzen__zed_files__2022__1643818864652.054QR-2202__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220208_172029733_208.xml__id.csv
0 rows

File structure

Notes: The provided snippet is not a structured dataset but appears to be a single line containing an IBAN number (CH8704835061435161001). There are no consistent columns or delimiters across rows in the sample, and the content resembles unstructured financial data rather than tabular PII records. Since no structured format is detectable and the sample shows no repeated pattern, the file is classified as unstructured. The IBAN itself is not classified as PII per the exclusion rules (financial/transactional data), so no columns are mapped.

finanzen__zed_files__2022__1643818864652.054QR-2202__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220209_172053202_209.xml__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) with no structured columnar data. The file appears to be a standalone value or part of unstructured text, not a delimited dataset with multiple rows and columns. Since there is no consistent delimiter or structured format across lines, and this appears to be a single data point, we classify it as unstructured. No PII columns can be mapped from this snippet.

finanzen__zed_files__2022__1643818864652.054QR-2202__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220211_172131867_201.xml__id.csv
0 rows

File structure

Notes: The provided sample is a single line containing an IBAN (CH8704835061435161001), which is not classified as PII under the defined field types. The file appears to be unstructured data (a single value, not a structured table). No columns to map.

finanzen__zed_files__2022__1643818864652.054QR-2202__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220214_172234263_203.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, not a structured dataset

finanzen__zed_files__2022__1643818864652.054QR-2202__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220215_172246146_205.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is not structured PII. The first row appears to be a header row with placeholder labels 'id' and 'INTERNAL' repeated three times, but no actual data rows are present to analyze. Without actual data rows containing PII values, no columns can be mapped. This appears to be a header-only snippet or placeholder file.

finanzen__zed_files__2022__1643818864652.054QR-2202__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220216_172026163_200.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) — no consistent column structure, unstructured data from financial records

finanzen__zed_files__2022__1643818864652.054QR-2202__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220217_172027379_202.xml__id.csv
0 rows

File structure

Notes: The provided text is a single unstructured line containing an IBAN number (CH8704835061435161001). There is no consistent delimiter or structured format across multiple rows. This appears to be a standalone piece of financial data rather than a multi-column dataset. Given the unstructured nature and lack of repeated patterns, this is classified as unstructured text with embedded financial identifiers.

finanzen__zed_files__2022__1643818864652.054QR-2202__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220224_172212910_207.xml__id.csv
0 rows

File structure

Notes: This is a free-form text file containing a single IBAN value (CH8704835061435161001) with no structured columns. The file appears to be a raw snippet of financial data from the Zynex breach, likely extracted from a financial record or invoice. Since there is no consistent delimiter or row structure and the content is unstructured, it should be processed as unstructured text with embedded PII extraction.

finanzen__zed_files__2022__1646238031053.054QR-2203__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220302_172022054_206.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN and company name, not a structured dataset. Contains no columnar data or repeated patterns.

finanzen__zed_files__2022__1646238031053.054QR-2203__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220304_172224248_201.xml__id.csv
0 rows

File structure

Notes: The provided sample is not structured data; it appears to be a single IBAN number (CH8704835061435161001) rather than a delimited dataset with columns. Since there is no consistent delimiter, no header, and the data is not in a tabular format, this is classified as unstructured. No column mapping can be performed.

finanzen__zed_files__2022__1646238031053.054QR-2203__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220308_172139311_209.xml__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) which is financial/account data, not personal PII. No structured columns exist in the provided data; it appears to be a standalone financial identifier from the Zynex corporate data breach. Since there is no consistent row structure or multiple columns, and the content is purely financial/account information rather than personal PII, this is treated as unstructured with no column mappings.

finanzen__zed_files__2022__1646238031053.054QR-2203__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220315_172046154_205.xml__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number (CH8704835061435161001). There is no delimiter, header, or structured data. The content appears to be a raw IBAN value from financial records, but lacks any columnar structure or additional rows to analyze. Per rules, unstructured files with no consistent columns are mapped to an empty columns object.

finanzen__zed_files__2022__1646238031053.054QR-2203__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220318_172007320_203.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) — no structured columns detected in first 50 rows

finanzen__zed_files__2022__1646238031053.054QR-2203__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220322_172040974_208.xml__id.csv
0 rows

File structure

Notes: The provided data is not a structured table but a single line containing an IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or repeated structure across multiple rows. The file appears to be a free-form text containing a financial identifier rather than a dataset with columns. Per the unstructured opt-out rules, this is classified as unstructured with no column mapping performed.

finanzen__zed_files__2022__1646238031053.054QR-2203__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220323_172049814_200.xml__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN number (CH8704835061435161001) and no structured columns. The file appears to be a standalone financial identifier rather than a data record with multiple fields. As per rules, unstructured files with no consistent delimiter structure and no row structure should be marked as unstructured with an empty columns object.

finanzen__zed_files__2022__1646238031053.054QR-2203__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220325_172432539_207.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001), not CSV/structured format. No consistent delimiter or column structure across lines. File appears to be a raw note or log containing a single IBAN snippet.

finanzen__zed_files__2022__1646238031053.054QR-2203__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220328_172054846_204.xml__id.csv
0 rows

File structure

Notes: The provided sample is not structured data; it appears to be a snippet of unstructured text containing a single IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or row structure visible. Per rules, unstructured data with no consistent columns should return an empty columns object.

finanzen__zed_files__2022__1646238031053.054QR-2203__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220330_172240496_202.xml__id.csv
0 rows

File structure

Notes: This appears to be a free-form text file containing unstructured data. The sample provided is just a single line with an IBAN number (CH8704835061435161001), which is not a PII field as per the exclusion rules. There is no consistent delimiter, and the data does not follow a structured format with columns. Therefore, this file is classified as unstructured with no column mapping required.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220401_172329464_206.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN but no consistent column structure; not a tabular dataset

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220404_172010418_203.xml__prtry.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent column structure. The sample shows only the word 'INTERNAL' repeated, indicating this is likely a placeholder or internal note file rather than structured data containing PII. No emails, phone numbers, or other PII are visible in the sample.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220406_172105390_201.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN; no consistent column structure visible

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220407_172204052_208.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only CSV or an empty data sample. The first row contains column labels like 'id', 'INTERNAL' repeated three times, but no actual data rows with PII values are present in the first 50 rows. Without data rows to inspect, no PII columns can be confidently mapped. The structure suggests this might be a metadata or schema file rather than actual breach data containing personal information.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220408_172007622_214.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with no data values. The headers are all labeled 'INTERNAL' and do not correspond to any identifiable PII fields. The data appears to be internal IDs or reference keys, which are skipped per exclusion rules. No PII columns are present in the provided sample.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220411_172319201_211.xml__prtry.csv
0 rows

File structure

Notes: The file appears to be unstructured internal identifiers with no consistent delimiter or row structure. All lines contain the word 'INTERNAL' repeated multiple times, indicating this is likely a placeholder or test file rather than actual breach data containing PII. No emails, phone numbers, or other PII are visible in the sample.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220412_172122791_200.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample only shows the header row with column names 'id', 'INTERNAL', 'INTERNAL', 'INTERNAL' — all clearly internal identifiers. No PII fields are present in this header or visible in the sample. These columns will be skipped as per exclusion rules for internal IDs.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220413_172118578_212.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to contain only internal identifiers with no PII. All columns are labeled 'INTERNAL' and likely represent internal IDs or reference codes. No PII fields such as names, emails, addresses, etc., are present in the sample data.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220414_172211895_205.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent delimiter or row structure visible in the provided snippet. This is likely part of a README, note, or unstructured document describing the breach context rather than structured PII records.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220419_172056298_215.xml__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is not structured with actual PII fields; it only contains the header 'id' and three 'INTERNAL' labels, indicating internal identifiers. No PII columns are present in the first 50 rows. This appears to be an internal ID or index file, not containing any personal or sensitive information.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220420_172150909_210.xml__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). No structured columns or PII fields are present in the provided data. The file appears to be unstructured text with no consistent delimiter or header structure.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220421_172335282_216.xml__id.csv
0 rows

File structure

Notes: The provided text is a single line containing only an IBAN (CH8704835061435161001) and lacks any structured data or row format. There is no delimiter, header, or consistent structure across multiple lines to identify columns or PII fields. The IBAN itself is not classified as PII under the provided rules, so no columns are mapped.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220422_172316864_209.xml__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent delimiter or row structure visible in the sample; appears to be a single line of unstructured data rather than a CSV or tabular format. The IBAN is financial account information, but this is not a structured file with columns to map.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220425_172316572_202.xml__id.csv
0 rows

File structure

Notes: The provided snippet is NOT a delimited file but a single unstructured line containing a Swiss IBAN (CH8704835061435161001). This is a bank account identifier, not PII, and the data lacks any column structure or repeated patterns. Since there is no consistent delimiter or repeated rows, and this appears to be a single value (likely from a financial record), the file is unstructured with no columns to map. The IBAN itself is not classified as PII in the provided field list.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220426_172113858_207.xml__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001) with no structured columns or header. The line appears to be a standalone value rather than part of a delimited dataset. Since there is no consistent delimiter structure across lines and this appears to be a single data point, this qualifies as unstructured text with no column mapping possible.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220428_172146300_204.xml__id.csv
0 rows

File structure

Notes: The provided text appears to be a snippet of unstructured data — specifically, a single IBAN value rather than a delimited table. There is no consistent row structure, and the sample does not contain any visible emails or phone numbers. The breach context describes internal financial records, but this particular snippet is not in a CSV or tabular format and cannot be mapped to PII columns. It should be processed as unstructured content.

finanzen__zed_files__2022__1648826609581.054QR-2204__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220429_172400814_213.xml__id.csv
0 rows

File structure

Notes: This is a free-form text file (likely a README or description) containing unstructured notes about a breach. It does not contain structured data or PII columns. The content appears to be a description of the breach context rather than actual data records.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220103_172203034_200__prtry.csv
0 rows

File structure

Notes: The sample provided appears to be unstructured data. The lines contain only the word 'INTERNAL' repeated and do not show any consistent delimiter structure or identifiable PII fields. There are no emails, phone numbers, or other PII visible in the sample. Given the lack of structured columns and the repetitive nature of the content, this is classified as unstructured text with no importable data columns.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220105_172204631_207__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only a single IBAN number (CH8704835061435161001) with no structured columns or consistent delimiter patterns. No PII columns exist to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220106_172009697_205__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header-like text without any actual data rows. The headers are generic internal identifiers ('INTERNAL') repeated three times, indicating this may be a metadata or index file rather than actual PII-containing data. No PII fields can be mapped from this snippet.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220107_172026691_208__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only row or a metadata row with repeated 'INTERNAL' labels. No actual data rows or PII values are present in the first 50 rows. Therefore, no columns can be mapped to PII fields. This is likely a placeholder or metadata row before the actual data begins.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220110_172115153_201__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (not PII per exclusion rules), no consistent column structure or header. This appears to be a single-line snippet from a financial record rather than a structured dataset.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220112_172043678_206__id.csv
0 rows

File structure

Notes: The file contains unstructured free-form text. The visible content is a single IBAN number (CH8704835061435161001) which is a financial account identifier and not personally identifiable information. There is no consistent delimiter, no header, and the content appears to be a note or fragment about a financial record rather than structured PII records. As per the unstructured opt-out rules, no column mapping is performed.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220113_172048382_203__id.csv
0 rows

File structure

Notes: This is a single-line file containing a Swiss IBAN number (CH8704835061435161001). It lacks any delimiter structure, headers, or multiple rows. IBAN is not a PII field per the defined schema (only address, email, phone, etc., are PII). Since this is a standalone line with no consistent columnar structure across lines, it qualifies as unstructured free-form text per the unstructured opt-out rules. No column mapping is possible or required.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220114_172201195_204__id.csv
0 rows

File structure

Notes: The provided input is a single line containing an IBAN number (CH8704835061435161001) rather than a delimited dataset. This appears to be unstructured data with no consistent columnar structure or header. Since the file is free-form text with no repeated structure and only contains a single value, it qualifies as unstructured data. No columns can be mapped.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220117_172201635_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row showing three INTERNAL columns with no data values. No PII is present in the visible structure. The file appears to be an internal identifier header with no actual PII fields in the sample provided.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220202_172104394_204__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001), which is a banking identifier and not personal PII. There are no structured columns or headers present. The line does not contain any identifiable personal data such as names, addresses, emails, or phone numbers. The file appears to be a snippet or fragment, possibly from a financial record, but lacks any personal identifiers that would require mapping to PII fields.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220207_172051079_206__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent row structure or delimited columns; this is unstructured data

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220208_172029733_208__id.csv
0 rows

File structure

Notes: The provided sample is not a structured dataset but a single IBAN value 'CH8704835061435161001' which is a Swiss bank account number. There is no consistent delimiter, header, or repeated structure across lines. The sample shows only one line containing non-PII financial data (IBAN) and lacks any identifiable PII fields or structured format. Since this is a single unstructured line with no repeated pattern or columnar data, it should be processed as unstructured content.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220209_172053202_209__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN (CH8704835061435161001), which is a financial account identifier and not personal PII. No structured columns exist in the provided data. The file appears to be a raw snippet rather than a delimited dataset with rows and columns. Since there is no consistent structure or header, and the content is not prose with embedded PII, we classify this as unstructured with no columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220211_172131867_201__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number (CH8704835061435161001). No consistent column structure or header exists, and the content is purely a financial identifier without any PII fields. The file does not contain any structured data rows, therefore no column mapping is possible.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220214_172234263_203__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, no consistent delimiter or row structure

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220215_172246146_205__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet only contains the header row with column names 'id', 'INTERNAL', 'INTERNAL', and 'INTERNAL', which are internal identifiers and do not map to any PII fields. No PII is present in this sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220216_172026163_200__id.csv
0 rows

File structure

Notes: The provided sample is not a structured dataset but rather a single line containing a Swiss IBAN (CH8704835061435161001). There are no delimiters, headers, or multiple rows to analyze. This appears to be part of an unstructured financial record or note rather than a CSV or tabular dataset. Since there is no consistent structure, this should be processed as unstructured text.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220217_172027379_202__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number (CH8704835061435161001). There is no structured data or columnar format present in the sample. The content appears to be a raw financial identifier rather than a breach record with multiple columns of PII. No columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220224_172212910_207__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220302_172022054_206__id.csv
0 rows

File structure

Notes: This file contains unstructured text data, specifically an IBAN (CH8704835061435161001) which is a bank account identifier. There is no consistent delimiter or structured columns present in the sample. The data appears to be a snippet from a financial record rather than a tabular dataset with identifiable PII columns.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220304_172224248_201__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) with no structured columns or row patterns. The file appears to be free-form text with no consistent delimiter or repeated structure across lines. Since it lacks any row structure and contains only one line, it qualifies as unstructured data with embedded financial identifiers.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220308_172139311_209__id.csv
0 rows

File structure

Notes: The provided input is not a structured dataset but a single line containing an IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or multiple rows. This appears to be a fragment of financial data from the breach context, but it lacks any structured format or multiple columns to map. Since it does not meet the criteria for a structured CSV/TSV format and contains no embedded free-text emails or phones, it is treated as unstructured with no column mappings.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220315_172046154_205__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number (CH8704835061435161001) with no structured columns or headers. The file does not contain any other data or PII beyond this single IBAN value.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220318_172007320_203__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN (CH8704835061435161001). There are no structured columns, headers, or multiple rows. IBANs are financial identifiers and not classified as PII under the provided field types. The file is not CSV or any delimited structure and does not meet conditions for column mapping. It should be treated as unstructured content with no PII columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220322_172040974_208__id.csv
0 rows

File structure

Notes: This is a free-form text snippet containing only an IBAN (CH8704835061435161001). There is no structured data or consistent delimiter pattern visible in the provided sample. The content appears to be a single line with a financial identifier rather than a dataset with columns. Since this is unstructured and lacks any row structure, it qualifies as unstructured text with no column mapping possible.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220323_172049814_200__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (not a standard PII field in our taxonomy). No consistent row structure or column mapping is possible.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220325_172432539_207__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent column structure or delimiter; appears to be a single line containing only an IBAN value, no headers or multiple fields

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220328_172054846_204__id.csv
0 rows

File structure

Notes: The provided sample is not a delimited file but a single line containing a Swiss IBAN number (CH8704835061435161001). This is a financial identifier and not personal PII. The breach context describes financial records, but this snippet shows unstructured data. Since there is no consistent delimiter or row structure and only one line is provided, this is classified as unstructured with no column mappings.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220330_172240496_202__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent delimiter or row structure; appears to be raw data dump / log snippet rather than CSV/TSV. IBAN is a financial identifier but not a PII field per exclusion rules (financial/transactional). No emails or phone numbers visible in sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220401_172329464_206__id.csv
0 rows

File structure

Notes: The provided data is unstructured free-form text (a single IBAN value). No consistent columnar structure exists, and the content is purely financial/accounting data without embedded emails or phone numbers. This is not a CSV or tabular format and cannot be mapped to PII columns.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220404_172010418_203__prtry.csv
0 rows

File structure

Notes: The provided data appears to be a headerless unstructured file with only the word "INTERNAL" repeated across rows. There is no consistent delimiter structure, and no PII is visible in the sample. This matches the unstructured opt-out criteria as there is no row structure and no embedded emails/phones in the visible sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220406_172105390_201__id.csv
0 rows

File structure

Notes: This is unstructured free-form text containing a single IBAN value (CH8704835061435161001) with no consistent columnar structure or repeated patterns. The file appears to be a raw snippet or note rather than a dataset with defined columns.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220407_172204052_208__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only snippet or placeholder. The first row lists 'id' and then three 'INTERNAL' placeholders, with no actual data rows provided. Without sample values or additional columns, no PII fields can be identified. The context suggests this may be an internal identifier column, which would map to 'skip' under exclusion rules.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220408_172007622_214__prtry.csv
0 rows

File structure

Notes: This is an unstructured file containing only the word "INTERNAL" repeated across rows. There are no actual data fields or PII present. The file appears to be a placeholder or test file showing only a single repeated value, not a structured dataset with columns. No emails, phone numbers, or other PII are visible in the sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220411_172319201_211__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header row with only placeholder column names ('INTERNAL'). No PII is present in the first 50 rows. The file is likely a structured CSV, but without visible PII in the sample, no columns can be mapped. Further rows may contain actual data.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220412_172122791_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet is a header-only row showing three internal identifier columns labeled 'INTERNAL'. No PII fields are present in this row. The data appears to be internal corporate identifiers rather than customer PII data.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220413_172118578_212__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row containing only 'INTERNAL' repeated six times, with no actual data rows provided. No PII fields can be mapped from this header alone. The file appears to be a placeholder or incomplete data dump from the Zynex breach — no actionable PII is present in the first 50 rows.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220414_172211895_205__id.csv
0 rows

File structure

Notes: The provided data is a single line containing an IBAN number (CH8704835061435161001). This is not a structured table with columns; it's a standalone value. The file appears to be unstructured and contains only one piece of financial data. Since there is no consistent row structure or multiple columns, this should be treated as unstructured data. However, IBANs are not included in the standard PII fields we map to, so no PII fields are identified.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220419_172056298_215__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only line with three INTERNAL identifier columns. No PII fields present in the provided data sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220420_172150909_210__id.csv
0 rows

File structure

Notes: The provided data is a single unstructured line containing an IBAN number. There is no consistent delimiter, header, or repeated structure across rows (only one line shown). The IBAN is a financial identifier and not classified as PII under the defined fields. Since there is no structured data or repeated rows, this is classified as unstructured free-form text with no importable columns.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220421_172335282_216__id.csv
0 rows

File structure

Notes: The file appears to be unstructured free-form text. The sample provided is a single line containing a Swiss IBAN number (CH8704835061435161001), which is not considered personally identifiable information (PII) under the given rules. There is no consistent delimiter structure, and the content does not resemble a CSV or any other structured format. The breach context describes internal financial records, but the sample provided does not contain any structured data with identifiable columns.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220422_172316864_209__id.csv
0 rows

File structure

Notes: The provided sample is not a structured file with consistent columns or delimiters. It appears to be a single line containing an IBAN number (CH8704835061435161001), which is a financial identifier and not classified as PII under the given field types. The data does not contain any structured records with columns that map to PII fields. Since there is no consistent row structure or delimiter, and no embedded emails or phone numbers in a free-form context, this is classified as unstructured with no columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220425_172316572_202__id.csv
0 rows

File structure

Notes: The provided data is a single line containing only an IBAN number (CH8704835061435161001). There is no structured format, no header, and no other columns or rows visible. IBAN is not a PII field per the exclusion rules (it is a financial account identifier, not personal identifying information). Therefore, this is classified as unstructured text with no PII columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220426_172113858_207__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN (CH8704835061435161001) and no structured columns. The file appears to be a standalone identifier rather than a dataset with rows and columns. Since there are no repeated patterns or structured data, and it does not contain any free-form text with embedded emails or phone numbers, it cannot be mapped to any PII columns. It is not a README or general prose text about a breach; it is simply a raw IBAN value.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220428_172146300_204__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent column structure; appears to be a single line containing only an IBAN without surrounding data or structure. This qualifies as unstructured data under the opt-out rule.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220429_172400814_213__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent delimiter or structured rows; appears to be a single line snippet or header note rather than a data record. No column mapping possible.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220502_172459073_206__id.csv
0 rows

File structure

Notes: The provided content is a single line containing an IBAN (CH8704835061435161001) rather than a delimited dataset. There is no consistent column structure, and the sample shows no headers or multiple rows. Since this is not a structured file with columns, it is classified as unstructured. The IBAN is a financial identifier and not considered PII under the provided field definitions.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220506_172136820_200__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing only an IBAN (CH8704835061435161001). No structured columns or data rows exist. The IBAN is a bank account number and not considered PII under the current mapping rules (it maps to skip). Since there is no consistent delimiter or row structure, this is classified as unstructured free-form text.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220510_172201481_207__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header labels ('id', 'INTERNAL', 'INTERNAL', 'INTERNAL') with no actual data rows visible. These appear to be internal identifier columns and do not contain any PII. No email addresses, phone numbers, names, addresses, DOB, SSN, passwords, usernames, gender, suffix, or facebookId values are present in the visible portion. Therefore, no PII columns can be mapped from this sample. Additional rows with actual data would be required to identify PII fields.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220518_172048400_201__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN (CH8704835061435161001). There is no consistent columnar structure or header. The file appears to be a single line or note with financial data, not a structured dataset with PII fields. No column mapping is possible.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220520_172256185_210__id.csv
0 rows

File structure

Notes: The provided text is not a delimited file but a single line containing a Swiss IBAN number (CH8704835061435161001). There is no consistent row structure or header. Since this is a single unstructured value with no repeated pattern or columnar layout, we classify it as unstructured. No PII columns can be mapped because there are no columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220523_172009456_209__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet with only internal identifier columns labeled 'INTERNAL'. No PII fields are present in this sample. All columns are internal IDs and should be skipped per exclusion rules.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220524_172117100_202__id.csv
0 rows

File structure

Notes: This appears to be a single-line file containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter or structured format across rows—only a single line with a financial identifier. This is not a CSV or any structured table. IBAN is a financial account identifier and not a PII field per the provided definitions (it maps to bank account, not personal identity). Therefore, no PII columns exist to map. The file is unstructured and contains no actionable PII.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220525_172814215_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only row or metadata line indicating internal identifiers. No PII fields are present in the visible content. The columns are labeled as INTERNAL and do not contain any personal or identifiable information. Therefore, no columns map to PII fields.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220527_172316039_208__id.csv
0 rows

File structure

Notes: This appears to be unstructured text containing only an IBAN number. There is no consistent columnar structure or header present, and the sample provided is a single line with a financial identifier (IBAN) rather than structured PII fields. As per rules, unstructured text with no row structure returns empty columns object.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220530_172537946_205__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header labels 'id' and four 'INTERNAL' fields with no actual data rows. Since there are no data values to analyze and the headers indicate internal identifiers (which must be skipped), no PII columns can be mapped. This appears to be a metadata or index file rather than a PII-containing dataset.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220531_172515707_204__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) — no consistent structured columns, appears to be raw financial/invoice data snippets from Zynex's Swiss corporate records

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220601_172711105_205__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent delimiter or structured columns present; this is unstructured data requiring streaming extraction.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220602_172513791_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is a header-only snippet with no actual data rows. All columns appear to be internal identifiers ('INTERNAL') repeated four times, which are not PII according to the rules. No PII fields can be mapped from this header alone. The file seems to be an internal reference or placeholder rather than actual customer/user data records.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220603_172616423_202__id.csv
0 rows

File structure

Notes: This file appears to be unstructured text. The sample provided only contains a single line with a Swiss IBAN number (CH8704835061435161001) and no delimiter structure or header. Since there is no consistent column structure and it appears to be free-form text, it is classified as unstructured. No columns can be mapped.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220607_172039723_200__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent column structure or header present in the sample. The data appears to be a single line containing a Swiss IBAN, which is not classified as PII in the provided field types. Since there is no structured format, this is classified as unstructured with no column mappings.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220609_172158541_206__id.csv
0 rows

File structure

Notes: This is unstructured free-form text containing only an IBAN number (CH8704835061435161001) and no consistent tabular structure. There are no identifiable columns or row patterns. The content does not contain any embedded emails or phone numbers in the sample provided.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220613_172130915_201__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN (CH8704835061435161001) with no delimiter structure or multiple rows. The file is unstructured free-form text with no consistent columns. IBAN is not a PII field in our schema and therefore not mapped. No actionable PII for column mapping exists.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220614_172021521_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only file or a metadata description. The first row contains column names that are all marked as 'INTERNAL', and the second row repeats 'INTERNAL' for each column, indicating these are internal identifiers or system columns. No actual PII data is present in the first 50 rows. Given the context of a corporate data breach involving financial records and customer invoicing, these 'INTERNAL' columns likely correspond to internal IDs or system-generated identifiers that should be skipped per exclusion rules. There are no email addresses, phone numbers, or other PII visible in the sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220615_172430219_205__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN (CH8704835061435161001). There is no structured tabular data with columns. The file appears to be a standalone IBAN value, not part of a delimited record set. Since there are no consistent columns or structured rows, this qualifies as unstructured free-form text with embedded financial identifier (but no email/phone). Per rules, unstructured is only triggered when emails/phones appear in free-form text. Since there are none, this is simply an unstructured file with no PII columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220616_172518746_204__id.csv
0 rows

File structure

Notes: This is unstructured data containing only an IBAN number. There is no consistent delimiter or column structure. The sample provided is a single line with a bank account identifier and does not contain any structured PII fields or headers. As per the unstructured opt-out rules, this file should be processed through a streaming email/phone extractor, though no emails or phones are visible in this snippet.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220617_172402733_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample contains only header labels 'id' and four repetitions of 'INTERNAL'. These appear to be internal identifier columns and do not contain any PII. No email addresses, phone numbers, names, addresses, dates of birth, SSNs, passwords, usernames, genders, suffixes, or other PII fields are visible in this sample. Based on the breach context (Zynex internal corporate data), these are likely internal reference IDs or system metadata columns. All columns map to 'skip' per exclusion rules for internal IDs.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220620_172256950_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only row or placeholder with repeated 'INTERNAL' labels. No actual data rows are present in the sample, and no PII fields can be mapped. The columns are all marked as 'INTERNAL', which suggests they may be internal identifiers or metadata columns that should be skipped according to the rules. Since there are no values to analyze and the headers do not correspond to any PII fields, no columns are mapped.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220621_172207201_211__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with no actual data. All columns are labeled 'INTERNAL' and appear to be internal identifiers or placeholder headers. No PII is present in this row.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220622_172247937_210__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN number (CH8704835061435161001) and no structured data columns. No consistent delimiter or header exists, and the content is not tabular. IBAN is not considered PII in this context as it is a bank account identifier and not mapped to any PII field in the schema.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220623_172353638_207__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet with three columns labeled "id" and repeated "INTERNAL". No PII fields are visible in the sample. The columns are likely internal identifiers or metadata and do not contain any personal information based on the header names and lack of sample values. Therefore, no PII columns are mapped.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220624_172111529_209__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only internal identifier columns (all labeled INTERNAL) with no PII values. No email, phone, name, address, or other PII fields are present in the first 50 rows. All columns are marked as skip per exclusion rules for internal IDs.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220627_172214463_201__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN. No consistent column structure or header is present in the sample. The file is unstructured with just an IBAN line.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220628_172112243_206__id.csv
0 rows

File structure

Notes: This is a free-form text file containing unstructured data. The sample shows a single line with an IBAN (CH8704835061435161001), which is not considered PII under the defined fields. There is no consistent delimiter or structured row format, and the data appears to be a note or fragment rather than a dataset with columns. No structured PII columns can be mapped.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220629_172013591_203__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent columnar structure detected; appears to be a single line or snippet rather than structured records. IBAN is financial account data but not a standard PII field in our schema. Since there is no columnar structure, this is classified as unstructured with no column mappings.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220630_183348370_208__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, no structured columns present

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220701_172714099_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only row or metadata row from the Zynex breach dataset. The row contains only the word 'INTERNAL' repeated four times, indicating these are likely internal identifier columns without actual PII data in the sample provided. No PII fields can be mapped from this row alone.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220704_173945311_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet is a header-only row with placeholder column names indicating internal IDs (all marked as INTERNAL). No PII fields are present in this snippet. The file appears to be a structured CSV with internal identifier columns only in the visible rows. Further rows are needed to identify actual PII columns.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220705_173929542_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only header row present in sample, no data rows to analyze. Header shows three internal ID columns (all non-PII). No PII columns detected in this sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220706_174104155_206__prtry.csv
0 rows

File structure

Notes: The provided text is a free-form unstructured header line with no data rows. The line contains only the word 'id' and 'INTERNAL' repeated four times, indicating this is likely a header-only sample or placeholder. No actual data rows or PII are present in the sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220707_173851680_201__prtry.csv
0 rows

File structure

Notes: The provided text is NOT a delimited dataset. It consists of only header-like labels ('id', 'INTERNAL', repeated three times) with no actual data rows or structured format. This appears to be a file header or metadata section rather than a data table containing PII. No actionable PII columns exist in this snippet.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220708_174122937_200__id.csv
0 rows

File structure

Notes: This is unstructured data (free-form text) showing only a single IBAN value 'CH8704835061435161001' with no consistent columnar structure across rows. There are no repeated patterns, headers, or delimited rows in the sample. IBAN is financial account data but not personally identifiable in isolation without linked names. Since there is no row structure, this file should be processed as unstructured content.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220712_173830696_205__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only a Swiss IBAN number (CH8704835061435161001) with no structured columns or row patterns. The file appears to be a single-line data snippet rather than a CSV or tabular dataset. As per unstructured opt-out rules, no column mapping is performed.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220714_173600976_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header row only file or metadata file. The first row contains column labels 'id', 'INTERNAL', 'INTERNAL' repeated three times, but no actual data rows follow in the sample. Without data rows to validate patterns, no PII columns can be confidently mapped. The context mentions internal corporate financial records, but this specific file seems to be a structural metadata file rather than containing personal data.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220715_173725109_206__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). No structured columns or headers are present, and the data does not contain any PII fields beyond the IBAN itself, which is not classified as PII in the provided field types. Since this is unstructured data with no consistent row structure, it is treated as unstructured.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220718_174014665_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is only a header row with placeholder column names 'id', 'INTERNAL', 'INTERNAL', and 'INTERNAL'. No actual data rows or PII values are present in the first 50 rows to analyze. Therefore, no PII columns can be mapped.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220719_173811284_201__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent column structure present in sample; appears to be a single line of data or note rather than structured records. IBAN is a financial identifier, not PII per exclusion rules.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220720_173855270_209__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number (CH8704835061435161001) without any structured columnar data or multiple rows. The breach context describes financial records and customer data, but this file itself does not contain any structured PII fields or columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220721_173736390_210__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or multi-row structure. IBAN is not classified as PII under the defined fields, so no columns are mapped.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220722_173608862_208__id.csv
0 rows

File structure

Notes: free-form text with no consistent structure or columns; appears to be raw financial data snippets rather than tabular records

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220725_173724086_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to contain only internal identifier columns labeled 'INTERNAL' repeated across rows. No PII fields are present in the visible data. All columns are internal IDs and should be skipped per exclusion rules.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220727_175252753_202__id.csv
0 rows

File structure

Notes: This is a single-line file containing an IBAN number (CH8704835061435161001). There is no structured data or header. The file appears to be a standalone financial identifier rather than a delimited dataset with multiple columns. Since it contains no consistent structure or multiple rows, it is classified as unstructured with no columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220728_174033224_205__id.csv
0 rows

File structure

Notes: The sample data appears to be free-form text with a single IBAN value (CH8704835061435161001). There is no consistent delimiter or row structure across the sample, and the content is not structured as a CSV or table. This is classified as unstructured data with embedded financial identifiers rather than structured PII columns.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220729_174536716_207__id.csv
0 rows

File structure

Notes: This is unstructured text containing only an IBAN (CH8704835061435161001) and no structured columns. It does not represent a CSV or tabular dataset, so no column mapping is possible. The content appears to be a snippet from financial records or invoices, but lacks any row structure or headers.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220802_174603790_211__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header row only file or a metadata file. The provided rows contain only the word 'INTERNAL' repeated, with no actual data values. There are no PII-containing columns visible in this sample. The 'id' column is present but contains only the label 'INTERNAL' with no actual identifiers. No email addresses, phone numbers, names, or other PII are visible in these rows.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220803_174353312_200__id.csv
0 rows

File structure

Notes: This is unstructured text containing only an IBAN number. There is no consistent delimiter or row structure, and the data appears to be a single line or snippet rather than structured records. The IBAN is a financial identifier and not considered PII under the defined field types. No PII columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220804_174559870_210__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row or placeholder file. No data rows exist to analyze. The first row contains only the string 'id' and three 'INTERNAL' labels, indicating this is likely a metadata or placeholder file rather than actual PII records. No PII columns can be mapped from this header alone.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220805_174230855_205__id.csv
0 rows

File structure

Notes: This appears to be a free-form text file containing a single IBAN value (CH8704835061435161001) rather than structured tabular data. There is no consistent delimiter, header, or row structure across lines. The content is a financial identifier (IBAN) and not PII in the format we expect to map. Since this is unstructured text with no column structure and no repeated patterns, we treat it as unstructured for downstream processing.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220808_174245126_201__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet or placeholder showing only internal identifier columns labeled 'INTERNAL' and 'id'. No PII fields are present in this sample. All columns appear to be internal IDs which must be skipped per exclusion rules.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220810_174528165_208__id.csv
0 rows

File structure

Notes: This is not a structured file with columns. The provided content appears to be a single line containing an IBAN number (CH8704835061435161001) rather than a delimited dataset. There are no headers or repeating patterns to map to PII fields. IBANs are financial identifiers, not personal PII per the exclusion rules, so this file contains no mappable PII columns.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220812_174240744_212__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The first 3 rows appear to be header placeholders or metadata ("id", "INTERNAL"). No PII fields are present in this snippet. Additional rows needed to identify PII columns.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220815_174340224_207__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) rather than structured data. The breach context describes financial records and customer invoicing data, but this particular sample appears to be a standalone IBAN value without any surrounding structured context or headers. Since there is no consistent delimiter, no header, and only one data point, this qualifies as unstructured content. The IBAN itself is financial account information but cannot be mapped to any PII field in this isolated context.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220816_174211329_204__id.csv
0 rows

File structure

Notes: The provided content is not a delimited file. It appears to be a snippet of unstructured text containing an IBAN number. There are no structured rows or columns to analyze for PII mapping. The file is likely part of financial records or transaction data, but without a consistent delimiter or header structure, it must be processed as unstructured text.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220819_174432198_202__id.csv
0 rows

File structure

Notes: The file is unstructured text containing only an IBAN (CH8704835061435161001). There is no consistent delimiter or row structure. IBANs are not considered PII under the specified field types.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220822_174018120_206__id.csv
0 rows

File structure

Notes: The provided sample appears to be a single line containing an IBAN number (CH8704835061435161001) rather than structured data with columns. There is no consistent delimiter or header structure across rows, and the data is not in a tabular format. The context indicates this is part of a financial record from Zynex, but the sample itself is not structured and does not contain multiple columns to map. Therefore, it is classified as unstructured text with no column mapping.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220825_174036288_213__id.csv
0 rows

File structure

Notes: The provided data is a single line containing an IBAN number (CH8704835061435161001). This is not a structured table with columns but a free-form text line. IBANs are financial identifiers and not considered PII per the defined field types. Since there is no consistent delimiter or row structure, and the file appears to be unstructured, it is classified as unstructured with no column mapping performed.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220826_174524001_209__id.csv
0 rows

File structure

Notes: The provided sample appears to be a single line containing a Swiss IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or structured row format visible in the sample. The data is unstructured and lacks any repeated pattern across multiple lines that would indicate a CSV or other tabular format. Based on the breach context, this is likely a fragment from financial records, but the sample itself does not contain any PII fields beyond the IBAN, which is not in the defined PII categories. Since there is no structured format to map, the columns object is empty.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220829_174518046_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with placeholder column names "id" and four repeated "INTERNAL" labels. No actual data rows were provided, and no PII is visible. All columns appear to be internal identifiers or metadata placeholders, which must be skipped per exclusion rules. No PII fields can be mapped from this header alone.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220901_174543850_215__id.csv
0 rows

File structure

Notes: This is a free-form text file (not a structured CSV/TSV). The sample shows a single IBAN (CH8704835061435161001) and no consistent column structure or header. Since it's unstructured with no repeating delimiter pattern and only one line of data, we classify it as unstructured. No column mapping is possible.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220902_174531360_214__prtry.csv
0 rows

File structure

Notes: The file appears to be unstructured raw data with no consistent delimiter or column structure. All lines show the word "INTERNAL" repeated, indicating this is likely a placeholder or test file rather than actual structured records containing PII. No emails, phone numbers, or other PII are visible in the sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220905_174341546_201__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN (CH8704835061435161001). There is no consistent delimiter, no header, and no repeated structure across rows (as there is only one line). The IBAN is a financial identifier, not PII, and does not fall under any of the PII categories specified (email, phone, name, address, etc.). Therefore, this is correctly classified as unstructured with no PII columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220907_174543686_207__id.csv
0 rows

File structure

Notes: The file is a free-form text containing unstructured financial data. The sample shows a single IBAN number (CH8704835061435161001) and no consistent columnar structure or headers. This is typical of raw financial record dumps where each line may represent a different type of entry (invoices, financial statements, etc.) with varying fields and formats. As per rules, unstructured files with no consistent delimiter and variable line shapes are routed through streaming processing for embedded PII extraction.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220908_174300969_218__id.csv
0 rows

File structure

Notes: The provided data is a single line containing an IBAN number (CH8704835061435161001). There is no structured format, header, or multiple rows to analyze. Since this is unstructured data with no consistent columnar structure, it is classified as unstructured. The IBAN itself is financial account information and not directly mapped to PII fields in this context, but unstructured processing would handle any embedded PII if present in a broader text context.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220909_174735344_211__id.csv
0 rows

File structure

Notes: The provided input is not a delimited file but a single line containing an IBAN number (CH8704835061435161001). There is no consistent structure, header, or multiple rows to analyze. This is considered unstructured data with no columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220912_174251036_217__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only row or a file with only internal identifier columns. All columns are marked as INTERNAL and contain no actual PII data. No email addresses, phone numbers, or other PII values are visible in the sample. All columns will be treated as skip per exclusion rules for internal IDs.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220913_174417893_206__prtry.csv
0 rows

File structure

Notes: This is unstructured free-form text with no consistent delimiter or row structure. The sample shows only header-like lines ('id', 'INTERNAL') that are not actual data records. No PII can be extracted from this format.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220914_172923450_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet with placeholder column names "id", "INTERNAL", repeated three times. No actual data rows are present to analyze for PII values. All visible column names are non-PII internal identifiers (matching the exclusion rule for internal IDs). Therefore, no PII columns can be mapped from this sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220915_172613627_213__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet contains only header rows labeled 'INTERNAL' and no actual data rows. There are no visible PII fields in this sample. The file appears to be a metadata or placeholder file rather than containing actual records with personal information. Since there are no columns with identifiable data, no PII mappings can be made.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220916_172606726_205__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet or placeholder with repeated 'INTERNAL' labels. No actual PII-containing columns or data rows are present in the first 50 rows. All columns are marked as internal identifiers and contain no personal information. Therefore, no PII fields can be mapped.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220919_172947015_216__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only snippet or metadata row, showing only internal identifier labels ('id', 'INTERNAL', repeated). No actual data rows or PII values are present in the sample. Since there are no structured data rows with PII, no columns can be mapped. The file is likely a schema definition or placeholder rather than actual breach data containing personal information.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220920_173015244_209__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN but no consistent column structure or delimiter; sample appears to be raw data dump without row-based formatting

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220921_172433185_220__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header-like lines indicating 'INTERNAL' repeated multiple times with an 'id' column. No actual data rows or PII values are present in the first 50 rows. These appear to be placeholder or metadata rows rather than actual records containing personal information. Since there are no identifiable PII fields in the visible data, no columns can be mapped.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220922_172429693_210__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header row with only internal identifiers labeled 'INTERNAL'. No PII fields are present in this header. Since there are no actual data rows provided, no columns can be mapped to PII fields. The file seems to contain only internal IDs with no personal information exposed in the visible portion.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220923_172659701_219__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only file or placeholder with no actual data rows. The headers "id", "INTERNAL", and repeated "INTERNAL" columns suggest internal identifiers or metadata columns only. No PII values are present in the sample, and these columns map to internal IDs which are explicitly excluded per rules. Therefore, no PII columns are mapped.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220926_173524094_208__prtry.csv
0 rows

File structure

Notes: The provided text consists solely of the word "INTERNAL" repeated multiple times across rows with no delimiter structure or meaningful content. This appears to be a placeholder or header row indicating internal data classification rather than actual breach records. No PII can be extracted from this sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220927_173538009_200__id.csv
0 rows

File structure

Notes: The provided sample consists only of an IBAN number (CH8704835061435161001) with no surrounding structure or context. There is no delimiter, header, or consistent row format. This is clearly an unstructured snippet rather than a delimited dataset. Since there are no structured columns, no PII mapping can be performed, and the file should be processed as unstructured text for potential embedded PII extraction.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220928_174821209_212__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN number (CH8704835061435161001). There is no structured data, no header, and no repeated pattern across lines. Since it does not meet the conditions for a CSV or any structured format and contains only one line with a financial identifier, it is treated as unstructured free-form text. However, IBANs are not mapped as PII fields in the current schema, so no PII columns are identified.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220929_172746899_202__id.csv
0 rows

File structure

Notes: The provided data snippet is a single unstructured line containing an IBAN number (CH8704835061435161001) and no identifiable column structure. This appears to be a standalone value or note rather than a CSV or structured dataset. Since there is no consistent delimiter, no header, and only one line of data, this qualifies as unstructured text with embedded financial data (IBAN). However, IBANs are not classified as PII under the provided field types, and there are no emails, phone numbers, or other PII visible in the sample. Therefore, no columns are mapped, and the format is marked as unstructured.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221003_071734507_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only CSV with no data rows. All columns are labeled "INTERNAL" and contain no actual values, making it impossible to map any PII fields. No meaningful data is present in the first 50 rows.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221003_173243116_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to contain only internal identifier columns (labeled 'INTERNAL') with no actual PII values visible in the first 50 rows. All columns are marked as 'INTERNAL' which suggests these are internal IDs or reference codes rather than actual PII data. Based on the breach context (Zynex internal corporate data), these are likely internal tracking IDs, not customer PII. No email addresses, phone numbers, names, or other PII are present in the visible rows.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221004_173018194_201__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header row with repeated 'INTERNAL' labels and no actual data rows. No PII fields are visible. The file appears to be an internal identifier listing with no meaningful PII content in this excerpt.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221005_172642383_204__id.csv
0 rows

File structure

Notes: The provided input appears to be a single line containing an IBAN number (CH8704835061435161001) rather than a delimited dataset. There are no visible columns or structured records in the sample. Since this is not a CSV or other structured format with headers and rows, and it lacks any repeated pattern or delimiter, it is classified as unstructured. The IBAN itself is financial/account information and not considered PII per the rules (excluded as non-PII financial/transactional data).

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221006_172845336_206__id.csv
0 rows

File structure

Notes: The provided text is not a structured dataset but a single line containing a Swiss IBAN (CH8704835061435161001). There are no consistent columns, headers, or multiple rows to analyze. IBANs are financial identifiers and not considered PII under the provided field types. The breach context describes internal corporate financial records, but this snippet alone is insufficient for column mapping.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221007_172500902_205__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001). There are no structured columns or headers — this appears to be free-form text, likely part of a larger breach context file listing financial identifiers. Since it's unstructured with no row structure and contains a financial identifier (not PII), no columns are mapped. The IBAN is a bank account identifier, not personal PII, and is excluded per rules.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221010_172826230_200__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured data or columnar format present in the provided sample. The line appears to be a standalone value rather than part of a delimited dataset. Since there is no consistent structure, header, or multiple rows to analyze, this qualifies as unstructured text with no column mapping possible.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221011_172708232_208__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured data, no delimiter, and no repeated pattern across rows. The file appears to be a standalone IBAN value, not part of a CSV or tabular dataset. Since there are no headers or multiple rows to analyze, and the content is just a single financial identifier, this is classified as unstructured free-form text with no column mapping possible.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221012_172648435_209__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter or structured data across lines. The file appears to be a snippet or standalone entry, not part of a larger tabular dataset. No PII columns can be mapped due to the unstructured nature of the content.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221014_172444531_207__id.csv
0 rows

File structure

Notes: The sample provided is a single line containing a Swiss IBAN number (CH8704835061435161001). This is not a structured dataset with columns; rather, it's a single value that appears to be part of a financial record. Since there is no consistent delimiter, header, or structured format across rows (only one line shown), and it lacks any columnar structure, this is classified as unstructured data. However, IBAN numbers themselves are NOT considered PII under the defined field types (they are financial account identifiers). No PII fields (email, phone, name, etc.) are present in this snippet.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221017_172358518_203__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) without any structured columns or headers. The file is not a delimited CSV but appears to be a standalone financial identifier, likely part of a breach context note rather than a data record. No PII columns can be mapped from this input.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221024_173052938_203__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). No structured columns or headers are present in the provided data. IBAN is a banking identifier, not personal PII, and is not included in the available field types. The file appears to be unstructured and contains only this line.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221025_172746521_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file contains only internal identifier columns labeled 'INTERNAL' repeated across rows. No PII fields are present. All columns map to skip per exclusion rules for internal IDs.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221026_173520042_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row showing four INTERNAL columns with no data values. No PII fields are present in the sample. The file appears to be a metadata or schema file rather than containing actual records with PII.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221028_172733841_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header-like labels ('id', 'INTERNAL') that appear to be internal identifiers or metadata columns. No actual PII fields (email, phone, name, etc.) are visible in the first row or subsequent rows. All columns appear to be internal IDs or non-PII metadata based on the header names and context of a corporate financial data breach. Therefore, no PII columns are mapped.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221031_172813217_201__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be only a header row containing placeholder 'INTERNAL' labels for all columns. No actual data rows are present to analyze for PII mapping. Since there are no values to inspect, no columns can be confidently mapped to PII fields. The structure suggests this is a metadata or schema file rather than actual breached records.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221101_172701197_212__id.csv
0 rows

File structure

Notes: This appears to be a free-form text file containing unstructured data (IBAN number and no consistent columnar structure). The provided snippet shows only a single IBAN number and no structured columns or repeated patterns. Since there is no consistent delimiter, varying line shapes, and embedded financial identifiers, this qualifies as unstructured text per the rules.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221102_173727537_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only row or metadata line with no actual data values. The first row contains only the string 'id' and three 'INTERNAL' labels, indicating this is likely a placeholder or metadata row before actual data columns begin. No PII can be mapped from this header structure alone.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221104_172520292_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row showing only internal identifier labels ('id', 'INTERNAL' x4). No PII present. File appears to be a raw internal reference sheet or metadata header for another dataset, not actual customer records. Further rows needed for mapping.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221107_173301862_202__prtry.csv
0 rows

File structure

Notes: The file appears to be unstructured free-form text. The sample shows only header labels "id" and repeated "INTERNAL" values with no consistent delimiter or columnar structure. There are no visible emails, phone numbers, or other PII in the sample lines. Since there is no consistent delimiter and the content lacks structured columns, this is classified as unstructured text with no importable PII columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221108_172650110_210__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only row or placeholder with no actual data rows. The first row contains only the string 'id' and three 'INTERNAL' placeholders, indicating no valid structured data or PII is present in this sample. No columns can be mapped to PII fields.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221109_173146386_201__prtry.csv
0 rows

File structure

Notes: The provided data is a snippet of unstructured internal identifiers with no actual PII present. The lines are not structured records but rather header-like metadata or placeholder rows. Since there are no actual data rows with PII and the structure is not consistent, this is classified as unstructured with no columns to map. The note clarifies that this appears to be internal metadata from a corporate data breach context.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221111_174723175_206__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only file or the first row contains only column labels with no actual data rows following. The columns are labeled 'INTERNAL' repeatedly, indicating these are internal identifier columns that would map to skip per rules. No PII is present in the visible rows.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221114_172506003_211__id.csv
0 rows

File structure

Notes: This appears to be unstructured financial data. The sample shows only a Swiss IBAN (CH8704835061435161001) and a label 'iban' — no consistent column structure exists across rows. The breach context indicates this is internal corporate financial data (annual statements, billing records, etc.) rather than customer PII. Since there is no row structure and no embedded emails/phones visible in the sample, we treat it as unstructured with no column mapping.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221115_172738085_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with no data. The headers are all labeled 'INTERNAL' and appear to be placeholder or internal reference labels. No PII fields can be identified from this header alone. The breach context describes financial records but this sample shows only a header row with no meaningful column names or data. Additional rows needed for accurate mapping.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221116_172356094_207__id.csv
0 rows

File structure

Notes: This is a free-form text snippet containing only an IBAN (CH8704835061435161001). There is no consistent delimiter or structured row format in the sample. The breach context indicates this is part of a Swiss financial data breach, but the provided sample lacks any column structure or headers. The IBAN itself is not a PII field under the defined categories, so no columns are mapped.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221118_183312158_209__id.csv
0 rows

File structure

Notes: This is unstructured text containing only an IBAN (CH8704835061435161001) and no structured columns or PII fields. No CSV or tabular structure is present in the sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221121_172308233_213__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet is a header-only row indicating three internal ID columns (all labeled 'INTERNAL'). No PII fields are present in this snippet. Since this appears to be the start of a structured CSV file but contains only internal identifiers, no PII columns can be mapped from this sample. Additional rows with actual data would be required to identify PII columns.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221122_172655452_208__prtry.csv
0 rows

File structure

Notes: The provided content is a list of column headers that appear to be internal identifiers (labeled 'INTERNAL') repeated five times. There is no actual data present in the first 50 rows, and the headers do not contain any PII-related fields. The file appears to be a metadata or schema description rather than a data record file. No PII columns can be identified from the given sample.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221124_172654354_205__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) and no structured tabular data. The file appears to be free-form text with no consistent delimiter or column structure. Since it lacks any row structure and contains only a single financial identifier, it is classified as unstructured text. No column mapping can be performed.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221129_173412865_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File contains only internal identifier columns labeled 'INTERNAL' and 'id' with no PII values. No columns map to any PII fields. This appears to be a header-only sample or placeholder file showing only internal reference IDs.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221130_173303117_201__id.csv
0 rows

File structure

Notes: The provided input is a single line containing only an IBAN number (CH8704835061435161001). This is not a structured file with columns, nor does it contain any header or multiple rows. IBANs are financial identifiers and not considered PII in the context of personal data fields. Since there is no consistent delimiter, no header, and the data appears to be a standalone financial record, this file is classified as unstructured with no columns to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221201_172926333_203__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) and no consistent column structure; this appears to be a raw snippet rather than structured CSV

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221202_172336163_202__id.csv
0 rows

File structure

Notes: The sample content is not a delimited file with columns; it appears to be a single line containing a Swiss IBAN number (CH8704835061435161001). This is free-form text with no structured columns, matching the unstructured opt-out criteria. The IBAN itself is not considered PII under the defined fields (it is a financial account identifier, not an address, phone, email, etc.). No column mapping is performed.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221205_172702775_200__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There are no column headers or structured rows — this is not a CSV or tabular file. The IBAN itself is a financial identifier and not PII per the exclusion rules (it's not a physical address, phone, email, or name). No PII columns exist to map.

finanzen__zed_files__2022__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221207_172155127_201__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN (CH8704835061435161001). There is no structured data or header, and no consistent row structure across lines. The file appears to be a raw dump or snippet, not a delimited dataset. Since there are no repeated patterns, columns, or multiple rows, it is classified as unstructured. No PII fields can be mapped from this single line alone.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220118_172018626_204__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, no consistent row structure visible in the sample. The line shown is a single IBAN value without any delimiter or repeated pattern. This is an unstructured snippet, not a CSV or tabular format. The IBAN is financial data but not personal PII per our defined fields, and unstructured files containing only one line with no repeated structure are routed through the unstructured path for further analysis if needed.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220119_172031729_207__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent delimiter or row structure visible in the sample. This appears to be a single line of data or note, not a structured table. The IBAN is financial account information, but it's not one of the defined PII fields (email, phone, dob, etc.). Since there's no structured format, we return empty columns and mark as unstructured for further processing.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220120_172104947_209__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, not structured CSV

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220121_172057278_208__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN (CH8704835061435161001). There are no structured columns, headers, or multiple lines of data. IBAN is not a PII field as per the exclusion rules. The file does not contain any personal identifiable information that requires mapping.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220124_172157012_206__id.csv
0 rows

File structure

Notes: The provided content is unstructured text with no consistent delimiter or row structure. The visible line appears to be a single IBAN number (CH8704835061435161001), which is not considered PII under the defined field types. No column mapping is possible as the data does not conform to a structured format with identifiable PII columns.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220125_172008965_205__id.csv
0 rows

File structure

Notes: This appears to be a free-form text file containing only an IBAN number (CH8704835061435161001) with no structured columns. The content is not formatted as a CSV or any delimited structure and contains no headers or consistent row patterns. Since it's unstructured and contains no identifiable PII fields in a columnar format, it is treated as unstructured text.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220126_172006140_201__id.csv
0 rows

File structure

Notes: This is a single-line free-form text file containing only an IBAN (CH8704835061435161001). There is no structured data, no delimiter, and no consistent row structure. Per rules, unstructured files with no consistent columns must return an empty columns object. The IBAN is a financial identifier, not personal PII, and is excluded from mapping.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220127_172253341_200__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent column structure exists; this is unstructured data with a single financial identifier visible.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220128_172056248_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only file showing three internal identifier columns (all non-PII). No PII fields are present in the provided data. The columns are labeled 'INTERNAL' and contain no discernible personal information.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20220131_172333297_203__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured data with columns, and the content appears to be a standalone financial identifier rather than part of a dataset with personal identifiable information (PII). No PII fields can be mapped from this input.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221209_221324176_311__id.csv
0 rows

File structure

Notes: This file contains only a single IBAN value (CH8704835061435161001) and no structured rows. It is not a delimited CSV/TSV file; it is a standalone financial identifier. No columns to map. The content is a single IBAN line, not a breach record structure.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221212_172337525_323__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File appears to be a header-only row or metadata file. The provided rows contain only internal identifier labels ('id', 'INTERNAL', 'INTERNAL') with no actual data values or PII. No columns map to PII fields based on header names or expected patterns. This is likely a schema definition or placeholder file, not actual breach data containing personal information.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221213_172209403_315__prtry.csv
0 rows

File structure

Notes: The file is unstructured free-form text. The first line is 'id' followed by three 'INTERNAL' entries, indicating this is not a structured CSV with columns. Based on breach context (Zynex internal corporate data), this appears to be a header-free raw dump of identifiers, not containing embedded emails/phones in free text. No consistent delimiter or row structure exists across lines, and no PII is visible in the sample.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221214_172519668_321__prtry.csv
0 rows

File structure

Notes: The provided data is unstructured and consists only of the word "INTERNAL" repeated across rows, indicating no meaningful columnar structure exists. There are no identifiable PII fields or consistent delimiters to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221215_172239305_313__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File appears to be a header-only row with placeholder INTERNAL column names (repeated four times). No actual data rows provided, and no PII is visible. Columns are internal identifiers and should be skipped per exclusion rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221216_172353700_319__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is a header-only snippet showing 9 INTERNAL identifier columns with no PII. All columns are marked INTERNAL and contain no discernible personal data. No PII fields are present in this sample.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221219_172617247_312__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is not structured PII; it's a header row indicating internal identifiers only. No PII fields are present in the visible rows. The file appears to be an internal reference sheet with column headers labeling internal IDs, not containing any actual personal or sensitive data. All columns are marked as INTERNAL and contain no PII values.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221221_172536577_320__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file is a header-only sample showing three internal ID columns with no PII. No actual data rows are provided to analyze for PII mapping.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221222_172753652_314__prtry.csv
0 rows

File structure

Notes: This is a header-only line showing 'id' and four 'INTERNAL' labels. No actual data rows are provided in the first 50 rows. The structure is not consistent with any CSV format and appears to be a metadata header or placeholder. No PII is present in the visible content.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221223_172658873_310__prtry.csv
0 rows

File structure

Notes: The provided sample consists of only a header row with placeholder column labels ('INTERNAL') and no actual data rows. This indicates a non-data placeholder file or metadata row, not a structured dataset containing PII. Since there are no meaningful data rows to analyze, we treat this as unstructured content with no actionable columns.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221227_173003656_322__id.csv
0 rows

File structure

Notes: This is a single line containing a Swiss IBAN number (CH8704835061435161001) with no other data. The file appears to be a standalone snippet rather than a structured dataset with columns. As per instructions, unstructured files with no consistent delimiter structure and only one line are treated as unstructured text with embedded PII. However, since there are no emails or phone numbers visible and the line is just an IBAN (which is not a standard PII field in our mapping), we return an empty columns object.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221228_173131939_316__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) and no structured data or headers. The file is unstructured and lacks any consistent columnar structure or headers. The IBAN is not considered PII per the provided rules (it is a bank account identifier, not personal address/email/phone/etc.). Since there is no structured data to map, return empty columns and unstructured format.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221229_172633319_318__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is a header-only snippet with repeated 'INTERNAL' labels indicating no actual data rows are present. All columns are internal identifiers and contain no PII. No mappable PII fields are visible.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20221230_172947763_317__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row showing internal identifiers (all marked as skip per exclusion rules). No PII fields present in this row.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230103_172736621_427__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only file or placeholder with no actual data rows. All columns labeled 'INTERNAL' are skipped per rules as they are internal identifiers with no PII content. No PII fields are present in this sample.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230104_172803915_425__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only row with no actual data rows provided. The headers ('id', 'INTERNAL', 'INTERNAL') suggest these are internal identifiers and likely not PII fields. No PII-containing values are visible in the provided sample to map to any PII categories.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230105_172351402_429__id.csv
0 rows

File structure

Notes: The provided content is not a delimited file with structured columns. It appears to be a single line containing an IBAN (CH8704835061435161001) rather than a dataset with rows and columns. There is no consistent delimiter, header, or repeated structure across multiple lines. The context indicates this is part of a financial record from Zynex, a Swiss web hosting company, but the sample given is just one line of data. Therefore, this is classified as unstructured free-form text.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230106_172424765_430__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with no data rows provided. The file appears to be a metadata or schema file rather than containing actual PII records. The columns labeled 'INTERNAL' are likely internal reference IDs or keys and do not contain PII. No PII columns are present in the provided sample.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230109_172829902_428__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with three internal identifier columns labeled 'INTERNAL'. No PII is present. The file appears to be an internal corporate record from Zynex with only internal IDs as headers, no actual data rows provided in the sample.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230110_172303719_431__id.csv
0 rows

File structure

Notes: The file contains only unstructured data: a single IBAN number 'CH8704835061435161001'. There are no structured rows or columns, and the content does not contain any identifiable patterns of structured PII fields beyond this single IBAN. As this is unstructured and lacks row structure, it is classified as unstructured with no columns to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230111_172515547_424__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, no structured columns

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230112_172616448_433__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only a Swiss IBAN (CH8704835061435161001) with no structured columns or repeated patterns. It does not match any PII fields defined in the schema and lacks any consistent delimiter or row structure. The content appears to be a single data point rather than a dataset with columns.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230113_172706632_432__id.csv
0 rows

File structure

Notes: This is a single line containing a Swiss IBAN (CH8704835061435161001) and no structured columns. The data appears to be unstructured financial information, likely from a breach context described. Since there is no consistent delimiter or row structure and the sample contains only one line, this is classified as unstructured text.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230116_172429097_426__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only row or placeholder file. The first row shows only the string 'id' followed by five 'INTERNAL' placeholders, with no actual data rows provided. No PII fields can be mapped from this snippet. The file likely contains only internal identifiers without exposed PII in this section.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230117_172459233_201__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only file or the first row is all internal identifiers. The first row shows 'id' and multiple 'INTERNAL' placeholders indicating these are non-PII internal reference columns. No PII fields are present in this sample. All columns map to skip per exclusion rules (internal IDs).

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230118_172217618_202__id.csv
0 rows

File structure

Notes: The file appears to be free-form text containing unstructured financial/IBAN data rather than a delimited table. The single visible line is an IBAN (CH8704835061435161001) and no column structure or headers exist. This matches the pattern for unstructured data with embedded financial identifiers but no consistent row format.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230119_172525979_205__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row showing only internal identifier columns. No PII fields are present in this sample. All columns are marked as INTERNAL and will be skipped per exclusion rules for internal IDs.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230123_172413736_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample contains only header labels that are marked as INTERNAL and clearly represent internal identifiers. No PII fields are present in this snippet. All columns are skipped per exclusion rules for internal IDs.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230124_172452651_207__id.csv
0 rows

File structure

Notes: The provided data is not structured with consistent columns or delimiters. It appears to be free-form text containing a single IBAN number (CH8704835061435161001). There are no identifiable PII columns or structured rows to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230125_172808419_208__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File appears to contain only internal identifier columns labeled 'INTERNAL' with no actual data visible in the first 50 rows. No PII fields detected in the provided sample. All columns are internal IDs and should be skipped per exclusion rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230126_172951765_209__id.csv
0 rows

File structure

Notes: This is unstructured free-form text containing only an IBAN (CH8704835061435161001) and no structured data columns. The content appears to be a raw snippet from financial records rather than a CSV/TSV file with columnar data. No consistent delimiter or header structure is present across lines.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230127_172717687_206__prtry.csv
0 rows

File structure

Notes: The sample shows only header-like text with no actual data rows. The text 'id', 'INTERNAL', and 'INTERNAL' appear to be column headers but no actual data rows follow in the provided snippet. Without data rows to analyze, we cannot determine if this is structured data or unstructured. Given the context and the lack of visible PII in this snippet, we assume this is an unstructured file until more data is available. If more rows are present in the full file that show consistent delimiter patterns, this should be re-evaluated.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230130_172747033_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only row or metadata row showing only internal identifier labels ('id', 'INTERNAL'). No actual PII-containing rows are present in the sample. All visible columns are internal IDs and must be skipped per rules. No actionable PII fields can be mapped from this snippet.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230131_172822796_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File appears to be a header-only or metadata file with only internal identifier columns labeled 'INTERNAL'. No PII fields are present in the first 50 rows.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230201_173146110_212__id.csv
0 rows

File structure

Notes: This is a free-form text file containing a single IBAN (CH8704835061435161001) and no structured columns. The sample provided does not show any consistent row structure, and the content appears to be a single line of financial data rather than a delimited dataset. Since there are no repeated patterns, headers, or structured rows, this is classified as unstructured text.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230202_173012679_206__id.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; contains IBAN (CH8704835061435161001) which is financial account data but not PII

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230203_172935956_211__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet shows only header-like lines with 'INTERNAL' repeated, indicating this is likely a placeholder or metadata row rather than actual data columns. No PII fields are present in this sample. Additional rows are required to identify actual column mappings.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230206_172904535_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header row with only internal identifier labels (all marked as 'INTERNAL'). No PII fields are present in this row. The structure suggests this is likely the beginning of a dataset where actual PII columns would follow in subsequent rows, but this specific row contains only internal reference labels.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230207_172446046_208__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent delimiter or row structure detected in the provided snippet; appears to be a single line of unstructured data, possibly from a note or comment section. IBAN is not a standard PII field in the defined schema and should be skipped.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230208_172638043_209__id.csv
0 rows

File structure

Notes: The sample provided is a single unstructured line containing a Swiss IBAN number (CH8704835061435161001). There is no consistent delimiter or structured row format across the provided data. The context indicates this is part of a breach involving internal financial records, but the given sample lacks any structured columns or headers. Since the file appears to be unstructured text with no consistent column structure, it is classified as unstructured with no column mappings.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230209_172654788_202__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; sample shows only an IBAN number (CH8704835061435161001) and no repeated row patterns. This is not CSV/TSV — treat as unstructured for streaming PII extraction.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230210_173001530_214__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only row or metadata row with no actual data rows. The first row contains only the word 'INTERNAL' repeated five times, which suggests this is not a data record but rather a placeholder or security marker. No PII fields can be mapped from this header alone. Additional rows with actual data would be needed for proper column mapping.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230214_172429227_210__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only header row present in sample, no data rows visible. Header shows three INTERNAL ID columns with no PII fields. No actionable PII detected in this snippet.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230215_172535376_205__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only line with no data rows provided. The file appears to be an internal identifier listing with 'id' and 'INTERNAL' columns, both of which are non-PII internal IDs per exclusion rules. No PII fields are present in the visible structure.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230216_172526319_213__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001), no consistent delimiter or structured rows. This is unstructured financial data from Zynex breach

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230217_172559660_201__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). No structured columns or PII fields are present. The file appears to be a standalone IBAN value, not a CSV or tabular dataset. IBAN is financial data and not a PII field per the defined schema, so it should be skipped.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230220_172527644_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only snippet or placeholder with no actual data rows provided. The visible line 'id INTERNAL INTERNAL' shows only a column name 'id' and two repeated placeholder values 'INTERNAL', which are not mappable to any PII field. No PII columns are present in this sample.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230223_172721137_200__prtry.csv
0 rows

File structure

Notes: The file appears to be unstructured with no consistent column structure. The provided sample shows only a single line with three repeated 'INTERNAL' values and no actual PII. There are no identifiable columns or structured data patterns in the sample. Based on the context, this is likely a placeholder or internal metadata file rather than actual customer PII data.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230224_172714635_207__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent column structure or delimiter visible in the provided sample. The sample appears to be a single line containing only an IBAN, which is not considered PII in the current mapping rules (it is a bank account identifier but not one of the defined PII fields). However, the unstructured format detection criteria are met: no consistent delimiter, varying line shapes (only one line shown), and no structured data.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230301_173343576_202__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN (CH8704835061435161001), which is a financial account identifier and not personal PII. There are no columns, headers, or structured data in the provided sample. The file appears to be a simple text snippet rather than a delimited dataset.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230302_172803073_208__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only column headers 'id', 'INTERNAL', and 'INTERNAL' which appear to be internal IDs or metadata fields. No PII fields are present in the visible portion of the data. These columns will be skipped as per exclusion rules for internal IDs. If more rows or additional columns were available, they would need to be evaluated for PII content.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230303_172547380_217__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only row or a metadata row with no actual data. The row contains only the string 'id' and repeated 'INTERNAL' labels, indicating this is likely a placeholder or metadata row rather than actual data records. No PII fields are present in this row.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230306_172746852_201__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only snippet or placeholder row. No actual data rows with PII values are present in the provided sample. The column 'id' is an internal identifier and must be skipped per rules. Without further rows showing real data patterns, no PII columns can be confidently mapped.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230307_172914626_213__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only snippet or metadata line. The file contains only the word "id" and two "INTERNAL" labels with no actual data rows or columns to analyze. No PII fields can be mapped from this fragment.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230308_172509378_205__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The sample provided appears to be only the header row and two internal identifier lines. No PII fields are visible in the first 50 rows. The data structure is not fully represented in this snippet, but the header indicates potential internal identifiers only. Further rows are needed to identify any PII columns.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230309_172650215_206__prtry.csv
0 rows

File structure

Notes: This is a free-form text file with only header line indicating 'INTERNAL' repeated. No structured data or PII present beyond the header marker. The file appears to be a simple label file or placeholder, not containing any actual records or personal information. No emails, phone numbers, or other PII are visible in the sample.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230310_172650987_214__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only file or placeholder with no actual data rows. The header row contains only 'INTERNAL' repeated multiple times, indicating no meaningful PII columns are present in the visible data. No PII fields can be mapped.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230313_172748645_210__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only or metadata file with no actual data rows. The headers indicate 'INTERNAL' repeatedly, suggesting this is a template or placeholder file with no actual PII content. No columns map to PII fields as there are no data rows to analyze.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230314_172340650_218__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is purely internal identifier columns (labeled INTERNAL) with no PII content. All columns are internal IDs and should be skipped per exclusion rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230315_172819292_207__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only or metadata file with only internal identifier columns labeled 'INTERNAL'. No PII fields are present in the sample data. All columns are marked as internal IDs and should be skipped per exclusion rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230316_172629488_215__id.csv
0 rows

File structure

Notes: This is unstructured text containing only an IBAN number (CH8704835061435161001) with no consistent columnar structure or header. The file appears to be a simple text file or note rather than a delimited dataset. Since there are no consistent columns and the content is free-form, it qualifies as unstructured data.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230317_172712214_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File appears to be a header-only or empty file. The first row shows 'id' and three 'INTERNAL' placeholders, but no actual data rows are present in the sample. No PII fields can be mapped from this header alone.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230320_172636883_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The first 50 rows appear to be entirely header labels or placeholder rows with no actual data. The visible columns are all labeled 'INTERNAL' and contain no PII values. No columns map to any PII fields based on header names and sample values. This is likely a metadata row or placeholder before actual data begins.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230321_172524390_216__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only snippet with three columns labeled 'INTERNAL' repeated three times. No actual data rows are provided to analyze for PII content. Based solely on the header, no PII fields can be mapped. The columns are flagged as skip due to the exclusion rule for internal IDs.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230322_172657159_209__id.csv
0 rows

File structure

Notes: The sample is not a structured table but a single line containing a Swiss IBAN (CH8704835061435161001). There are no columns, delimiters, or repeated rows. IBAN is a bank account identifier, not personal PII under the defined schema. This is free-form text with no embedded emails or phones, so unstructured mapping applies.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230323_172511311_219__id.csv
0 rows

File structure

Notes: This is a single-line unstructured input containing only a Swiss IBAN (CH8704835061435161001). No column structure exists, and IBANs are not considered PII per the rules (they are financial identifiers, not personal contact info). No emails, phone numbers, or other PII are present.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230324_173504669_211__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only column headers are present with no data rows. The headers indicate three internal ID columns, which are non-PII and should be skipped. No PII fields are present in this header-only sample.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230327_173748438_221__id.csv
0 rows

File structure

Notes: The provided sample is not structured data but a single line containing an IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or row structure across the sample. IBAN is a financial identifier and not considered PII under the defined fields. Since this is unstructured and no consistent columns exist, it is classified as unstructured with no column mappings.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230329_173228636_220__id.csv
0 rows

File structure

Notes: This is a single-line file containing an IBAN number (CH8704835061435161001). The file lacks any structured format, header, or multiple rows. Since it is not a delimited CSV/TSV file with consistent columns and appears to be a standalone value, it is classified as unstructured free-form text. No column mapping is performed.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230330_173039282_212__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only file or the first row contains only internal identifiers. No PII fields are present in the provided data. All columns are marked as INTERNAL and likely represent internal IDs or system references, which are skipped per rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230331_173338251_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only file or placeholder with only internal identifier columns labeled 'INTERNAL'. No PII fields are present in the first 50 rows.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230403_173701019_200__id.csv
0 rows

File structure

Notes: This is not a structured file. The provided content appears to be a single line containing an IBAN (CH8704835061435161001) rather than a delimited dataset with columns. The breach context indicates this is part of financial records, but the sample shows no structured columns or headers. Since there is no consistent delimiter or row structure, and the content is a single value, this is classified as unstructured text. The IBAN itself is financial data and would be skipped under exclusion rules as it is not a PII field (it is an account identifier, not personal identifying information).

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230406_173149570_203__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (not email/phone)

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230413_172840109_207__id.csv
0 rows

File structure

Notes: This is an unstructured text file containing a single IBAN value (CH8704835061435161001) and no structured data. The content appears to be a raw snippet rather than a dataset with columns. There are no consistent delimiters or headers, and the sample lacks any identifiable PII fields beyond the IBAN itself, which is not classified as PII under the specified rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230414_172939971_206__id.csv
0 rows

File structure

Notes: This file contains only a single IBAN value (CH8704835061435161001) with no row structure or delimiter. It appears to be a standalone financial identifier rather than a structured dataset. Since there are no consistent columns or headers, and the content is not free-form text with embedded PII, it is classified as unstructured with no actionable PII columns to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230417_172919715_204__id.csv
0 rows

File structure

Notes: This is unstructured text containing only an IBAN (CH8704835061435161001). There are no structured columns or consistent delimiter patterns. The sample is a single line with a financial identifier, not a breach record with PII columns. Per rules, this is free-form text with no column structure.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230419_172636163_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only row or metadata row with no actual data rows provided. The headers 'id', 'INTERNAL', and 'INTERNAL' do not map to any PII fields. No PII values are present in the sample to analyze. Based on the breach context (Zynex internal corporate data), these columns likely represent internal identifiers and should be skipped. No PII columns detected.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230420_172848138_201__id.csv
0 rows

File structure

Notes: The provided sample is a single unstructured line containing only a Swiss IBAN (CH8704835061435161001). This is not a structured dataset with columns; it's just a standalone IBAN value. No consistent delimiter, header, or multiple rows exist in the sample. The breach context mentions financial records, but this snippet alone lacks any structure to map to PII columns. Since it's unstructured text with no repeated pattern or columnar layout, we classify it as unstructured with empty columns. The IBAN itself is not a PII field per the defined categories (it’s a bank account identifier, not email/phone/name/etc.), so no mapping is needed.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230421_173020059_202__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent delimiter or row structure is present in the sample. This is an unstructured file containing a single IBAN value rather than a tabular dataset.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230424_173136036_205__id.csv
0 rows

File structure

Notes: The provided sample is a single line containing only an IBAN number (CH8704835061435161001). There is no consistent structure, header, or multiple rows to analyze. IBAN is not a PII field per the defined categories. The data appears to be a snippet from financial records rather than a delimited file with personal information. Since there is no structured format, this is classified as unstructured with no columns to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230502_173851130_308__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). No structured columns or headers exist in the sample. IBAN is financial account data, not personal PII, and is excluded per rules. No emails, phones, or other PII are present.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230509_172543600_311__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only a Swiss IBAN number (CH8704835061435161001). There is no structured column pattern or header, and the content is unstructured. The IBAN is not classified as PII under the defined field types, so no columns are mapped.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230510_173114367_314__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only line or metadata row with no actual data. The columns listed ('id', 'INTERNAL', 'INTERNAL') appear to be internal identifiers and do not map to any PII fields. No PII is present in this row.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230511_173117105_312__prtry.csv
0 rows

File structure

Notes: This is not a structured data file but rather a list of internal identifiers with the header 'id' repeated three times. There is no consistent delimiter or row structure, and the values appear to be internal IDs (non-PII). No PII is present in this snippet.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230517_173103058_313__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent columnar structure visible in the provided snippet. This appears to be a single line containing only an IBAN, not a full file sample. IBANs are financial identifiers and not classified as PII under the defined field types.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230519_172957061_310__id.csv
0 rows

File structure

Notes: The input is a single line containing only an IBAN (CH8704835061435161001), which is a bank account identifier. This is not PII and does not constitute structured tabular data. There are no columns, headers, or multiple rows present to analyze. The file appears to be a simple text snippet rather than a delimited dataset containing personal information.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230526_174100640_309__id.csv
0 rows

File structure

Notes: This is unstructured financial data with no consistent column structure. The sample shows a single IBAN value (CH8704835061435161001) without any row structure or headers. As per rules, unstructured files with no consistent delimiter and variable line shapes must be processed through a streaming PII extractor.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230601_173641981_415__id.csv
0 rows

File structure

Notes: This is a single-line unstructured input containing only an IBAN number (CH8704835061435161001) with no delimiter or header structure. The context indicates this is part of a financial record from Zynex's corporate data breach, but the provided sample is not structured tabular data — it is a standalone value. Since there is no consistent delimiter or row structure, and this is a single line, we classify this as unstructured free-form text with embedded financial data. No column mapping is possible.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230605_173112657_211__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN number (CH8704835061435161001). There are no consistent delimiters or structured columns across lines, and the content is purely unstructured. The IBAN is a financial identifier and not considered PII in this context, so no columns are mapped.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230606_172739636_202__id.csv
0 rows

File structure

Notes: The provided content appears to be a single line containing an IBAN number (CH8704835061435161001) rather than a structured dataset with multiple rows and columns. There is no delimiter or header present, and the sample does not exhibit any consistent structure across multiple rows that would indicate a CSV or other tabular format. As per the rules, when the file is unstructured and contains no consistent column structure, it should be classified as unstructured with an empty columns object.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230607_173207921_209__id.csv
0 rows

File structure

Notes: The provided data appears to be a single line containing a Swiss IBAN (CH8704835061435161001) without any structured columns or headers. There is no consistent delimiter, and the data does not exhibit a row structure. The breach context mentions financial records, but this snippet alone does not provide enough structure to map to PII fields. As per the unstructured opt-out rules, this is treated as free-form text with no column mapping.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230608_173110937_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with no data rows provided. The columns appear to be internal identifiers (marked as INTERNAL) and a generic 'id' column, which are not PII. No PII fields can be mapped from this header alone.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230609_173154222_208__prtry.csv
0 rows

File structure

Notes: This is a free-form text file containing only headers labeled 'INTERNAL' with no actual data rows visible in the sample. The structure is not tabular and lacks any identifiable PII or consistent columnar format. No columns to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230612_172831441_210__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN (CH8704835061435161001). There are no consistent delimiters or structured columns across rows. The file appears to be a standalone IBAN value rather than part of a structured dataset. Since there is no row structure and this is a single value file, we classify it as unstructured with no columns to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230613_172608360_205__id.csv
0 rows

File structure

Notes: The provided data appears to be a single line containing an IBAN number (CH8704835061435161001). There is no consistent delimiter or structured format across rows. The sample does not show multiple lines or a header row, and the content is purely a financial identifier without any other PII or structured fields. Since there is no row structure and the data is not in a tabular format, this is classified as unstructured. No columns can be mapped.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230614_172640451_215__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header labels 'id' and four 'INTERNAL' fields with no actual data rows. No PII is visible. Since the file appears to be purely internal identifiers with no personal data, no columns map to PII fields. All columns are marked as skip per exclusion rules for internal IDs.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230615_172719372_207__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header row with only internal identifiers. No PII fields are present in the first 50 rows.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230616_172538459_214__prtry.csv
0 rows

File structure

Notes: The provided data is purely internal identifiers with no PII. The file consists of repeated "INTERNAL" values across rows, indicating a non-structured or placeholder file without any personal or identifiable information. No columns map to PII fields.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230619_173125838_201__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is purely headerless and contains only the word 'INTERNAL' repeated across rows. No PII fields are present. The file appears to be a placeholder or redacted internal reference file with no usable data for mapping.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230620_172840930_200__id.csv
0 rows

File structure

Notes: The provided content is a single line containing an IBAN number (CH8704835061435161001) rather than a structured dataset with columns. There are no visible CSV or table-like patterns, and the context indicates this is part of a financial record rather than a delimited file with PII columns. Since there is no consistent delimiter or header structure, and this is a standalone financial identifier, this is treated as unstructured content with no mappable columns.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230621_173026959_206__id.csv
0 rows

File structure

Notes: This is unstructured text (a single line containing an IBAN). No column structure exists. IBAN is a financial account number, not personal PII per exclusion rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230623_173132675_213__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header row only containing internal identifiers with no PII fields visible. All columns are marked as INTERNAL and contain no personal information. No email addresses, phone numbers, names, addresses, or other PII fields are present in this sample.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230627_173313238_216__id.csv
0 rows

File structure

Notes: This is a free-form text file containing unstructured financial data from a breach. The sample shows an IBAN number (CH8704835061435161001) but no consistent columnar structure. No CSV headers or repeated delimiters are visible. This qualifies as unstructured data with embedded PII that should be routed through a streaming extractor for emails/phones.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230629_173715319_212__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN but no consistent structure or row format. This is not a structured CSV/TSV file; it's a single line containing only an IBAN and no identifiable columns or delimiters. No PII columns to map as the file lacks any structured format.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230630_174130154_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet or placeholder with no actual data rows. All visible columns are labeled 'INTERNAL' and appear to be internal identifiers rather than PII fields. No PII can be mapped from this header alone.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230703_173518175_200__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) — no consistent columnar structure visible in the sample. This is likely a financial record or invoice line rather than a delimited dataset. The IBAN is a financial identifier but not a PII field per the rules (it maps to account banking, not personal identity).

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230704_173430135_211__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN number (CH8704835061435161001). There are no consistent delimiters or structured columns. The content appears to be a single line with financial data rather than a dataset with PII fields. Since there is no consistent structure across lines and the content is unstructured, we classify this as unstructured with no column mapping.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230705_173454447_201__id.csv
0 rows

File structure

Notes: The provided content is not a structured delimited file. It appears to be a single line containing an IBAN number (CH8704835061435161001) rather than a multi-row dataset with consistent columns. This is not a CSV or any tabular format with headers and multiple rows of data. The context describes a corporate data breach, but the sample provided does not represent the actual breach data structure. Since there is no consistent row structure or multiple columns to map, this is classified as unstructured content with no columns to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230706_173151810_203__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, not a structured table. No consistent delimiter or column pattern present in the sample; appears to be a raw data dump or single-line record.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230707_173105854_213__prtry.csv
0 rows

File structure

Notes: This is not a structured file with columns. The provided data appears to be a header row with placeholder entries like 'INTERNAL' repeated multiple times, indicating no actual data structure or PII fields are present in this snippet. The data format does not contain any identifiable PII columns, and the rows do not show structured data with delimited fields. Therefore, no columns can be mapped.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230710_173430647_210__id.csv
0 rows

File structure

Notes: The provided sample is not a structured dataset but a single line containing a Swiss IBAN number (CH8704835061435161001). There is no delimiter, header, or repeated structure across lines. The note about the breach context (Zynex internal financial data) suggests this may be part of a larger file, but the sample itself is unstructured and contains no identifiable column structure. IBAN is not a PII field in the defined schema.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230712_172910973_217__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) and no consistent column structure

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230713_172806586_209__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only row or metadata row showing column labels. All columns are labeled 'INTERNAL' indicating they are internal identifiers or non-PII fields. No PII fields are present in the visible data. Given the context of a corporate financial data breach, these columns likely represent internal reference IDs, counters, or system-generated keys that do not contain personally identifiable information.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230714_172819337_216__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only internal identifier columns labeled 'INTERNAL' repeated across rows. No PII fields (email, phone, name, etc.) are present. All columns represent non-PII internal IDs and should be skipped per exclusion rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230717_172923102_206__prtry.csv
0 rows

File structure

Notes: The provided sample consists solely of the header line 'id' followed by repeated 'INTERNAL' labels, indicating this is not a structured data file with columnar PII. The content appears to be an internal identifier listing with no actual PII values present in the first 50 rows. Since there are no consistent columns or embedded PII in free-form text, this is classified as unstructured with no mappable columns.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230718_172644302_215__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure; contains IBAN but not structured columns

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230719_173007985_205__id.csv
0 rows

File structure

Notes: The provided data is not structured tabular data. The sample shows a single line containing an IBAN (CH8704835061435161001), which is a bank account identifier and not personal identifiable information (PII) in the context of the defined fields. There is no consistent delimiter, header, or structured format across rows. This appears to be a free-form text file listing financial identifiers rather than a dataset with personal PII fields. As per the unstructured opt-out rules, this file should be processed through a streaming extractor for any embedded emails or phones, though none are visible in the provided snippet.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230720_172902288_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is only a header row with placeholder column names "id" and repeated "INTERNAL". No actual PII values are present in the first 50 rows to map to any PII fields. All columns appear to be internal identifiers or placeholder labels, and thus are skipped per rules. No actionable PII columns detected.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230721_173158333_212__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row showing only internal identifier columns (all marked as INTERNAL). No PII fields are present in this row. The file appears to be a metadata or schema file rather than containing actual PII data records.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230724_173027989_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only CSV or a placeholder with repeated 'INTERNAL' labels. No actual data rows are present in the first 50 rows, and no PII fields can be identified. All columns are marked as 'INTERNAL' which suggests these are internal identifiers or metadata columns that should be skipped per exclusion rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230726_173901334_207__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only snippet or metadata row showing column labels but no actual data rows. The visible entries ('id', 'INTERNAL') are non-PII identifiers. No PII fields are present in this sample.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230727_173255368_218__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN (CH8704835061435161001) and no structured columns or identifiable PII patterns. The file appears to be a single line of financial data rather than a delimited dataset. No column mapping is possible as there is no consistent structure or header.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230728_174146731_208__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure. The sample is a single line containing only a Swiss IBAN (CH8704835061435161001), which is financial/account data, not personal PII. No columns exist to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230731_173817302_214__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The first 50 rows appear to be header metadata only, repeating the word "INTERNAL" across columns without actual data. No PII is visible in this snippet. Further rows likely contain structured records; additional sample needed for column mapping.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230802_173553803_206__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with three INTERNAL columns (no PII). No actual data rows were provided to analyze for PII mapping.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230803_173309257_204__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing only an IBAN number (CH8704835061435161001). No structured columns or header exist. IBAN is not a PII field in the defined schema (it's a bank account identifier, not personal identifying information). The file appears to be a snippet or artifact from financial data, but lacks any structured PII fields or repeated patterns across rows.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230804_173512169_211__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent columnar structure; appears to be a single-line note or fragment from financial records rather than a delimited dataset

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230807_173257928_214__id.csv
0 rows

File structure

Notes: The provided content is not a structured dataset but rather a snippet containing a single IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or row structure visible in the sample. Since this is a standalone IBAN and not part of a structured CSV/TSV format with multiple columns, it falls under unstructured data. However, IBANs are financial identifiers and not considered PII per the defined fields. No PII columns to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230808_173144937_205__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only a Swiss IBAN number (CH8704835061435161001). There is no delimiter structure, no header, and no other data present. The IBAN is not a PII field according to the provided definitions (it is a bank account identifier, not personal identifiable information like name, email, or phone). Since there are no columns and the file is not structured, we return an empty columns object with unstructured type.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230809_173221719_213__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is only a header row with placeholder 'INTERNAL' labels and no actual data values. No PII fields can be mapped from this header alone. The file appears to be a skeleton or template with no usable content for PII identification.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230810_173102532_209__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample only contains header-like text ('id', 'INTERNAL', 'INTERNAL') with no actual data rows. These appear to be placeholder/internal identifiers rather than PII. No PII fields are present in the visible sample. The file is likely a structured CSV but lacks actual data rows in the first 50 lines.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230811_174145524_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet with no actual data rows visible. All columns are labeled "INTERNAL" repeatedly, indicating this may be a placeholder or metadata row rather than actual PII-containing data. Without sample values or meaningful column names, no PII fields can be identified or mapped. The file likely contains only internal reference IDs with no personal information exposed in this snippet.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230814_173340083_217__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no delimiter structure, no header, and no additional data in the first 50 rows. The IBAN is not classified as PII under the provided field types, and there are no emails, phone numbers, or other identifiable information present. The file appears to be a standalone IBAN value rather than a structured dataset with columns.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230815_173247465_207__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN (CH8704835061435161001). There is no structured data or column pattern. The IBAN is a financial identifier, not PII per the rules (it is not mapped to any PII field). Since this is unstructured with no consistent delimiter or row structure, it is classified as unstructured with no columns to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230816_172910517_201__id.csv
0 rows

File structure

Notes: The provided sample appears to be a single line containing an IBAN number (CH8704835061435161001) without any structured delimiter or repeated pattern. This is not a CSV or any structured format with columns. Given the context of the breach (Zynex internal corporate data), this seems to be a snippet from a financial record rather than a full dataset. Since there is no consistent delimiter, varying line shapes, and no header structure, this qualifies as unstructured data. The IBAN itself is sensitive financial information but isn't classified under the defined PII fields (email, phone, dob, etc.).

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230817_172944915_208__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent column structure; this is a single-line file containing only a Swiss IBAN number

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230818_173251191_216__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is only a header row with placeholder columns labeled 'INTERNAL'. No PII fields are visible in this snippet. The file appears to be a structured CSV, but no actual data rows were provided to analyze for PII mapping. All columns are marked as internal identifiers and should be skipped per exclusion rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230822_173121847_202__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) and no consistent column structure. The sample provided is a single IBAN line, which is typical of unstructured data dumps where sensitive identifiers appear inline without defined fields.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230823_173421462_210__id.csv
0 rows

File structure

Notes: The provided data is unstructured free-form text. The single line contains only an IBAN number (CH8704835061435161001), which is not personally identifiable information (PII) in the context of the breach description. There are no consistent columns, headers, or structured records in this sample. The breach context indicates financial records, but this snippet is not structured data and does not contain any PII fields. Returning empty columns as per unstructured opt-out rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230825_173534098_215__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN number

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230830_174056211_203__id.csv
0 rows

File structure

Notes: The sample appears to be unstructured text containing a single IBAN value (CH8704835061435161001) and no consistent columnar structure. There are no repeated lines, no delimiters, and no header row. This is typical of a file containing a single record or identifier rather than tabular data. Since there is no consistent row structure and the content is not prose with embedded PII, it is classified as unstructured for special handling.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230831_173915605_212__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN (CH8704835061435161001). There is no delimiter or structured data. The file appears to be a raw snippet or fragment rather than a dataset with rows and columns. No PII columns can be mapped because there is no structure to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230901_174821303_216__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN (CH8704835061435161001) which is a bank account identifier, not personal PII. The file appears to be unstructured and does not contain any structured records or multiple columns. Since there is no consistent delimiter or row structure, and no clear PII fields, this is classified as unstructured with no columns to map. The IBAN itself is not mapped as a PII field in our schema.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230904_173546793_212__id.csv
0 rows

File structure

Notes: This is a free-form text sample showing only an IBAN number (CH8704835061435161001). There is no consistent delimiter structure across lines, and the data appears to be unstructured notes or log entries rather than a tabular dataset. Per rules, unstructured files with embedded PII are handled by a streaming extractor, so no column mapping is performed.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230905_174359387_201__id.csv
0 rows

File structure

Notes: The provided text appears to be a single unstructured line containing an IBAN number (CH8704835061435161001) rather than a delimited dataset. There is no consistent columnar structure across rows, and the sample shows only one line of data. Per rules, unstructured text with no consistent delimiter or row structure should return an empty columns object with format type 'unstructured'.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230906_173636846_213__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001), no consistent column structure visible in the sample

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230907_174154246_205__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN (CH8704835061435161001) with no surrounding structure or context. It lacks any row structure, headers, or additional data fields. The IBAN itself is financial/account information and not personally identifiable information (PII) in the context of the requested fields. Since there is no consistent delimiter, varying line shapes, and no structured data beyond this single value, it qualifies as unstructured free-form text with no column mapping possible.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230908_173944516_206__id.csv
0 rows

File structure

Notes: This appears to be unstructured data. The snippet provided is a single line containing an IBAN number (CH8704835061435161001) rather than a delimited CSV or structured data. There is no consistent delimiter or header, and the content does not represent multiple rows with columns. Given the context of a breach involving internal financial records, this could be part of a free-form text dump. Since there is no structured format, this should be processed as unstructured text.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230911_173602024_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample contains only header row with placeholder column names "id" and multiple "INTERNAL" labels indicating no actual data rows are present. No PII fields can be mapped from this header alone. The file appears to be an internal corporate data structure placeholder with no real data exposed in the first 50 rows.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230912_173315899_218__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing a Swiss IBAN number (CH8704835061435161001). There are no columns, headers, or structured data — just a raw IBAN value in what appears to be a breach artifact. No PII fields to map. The file type is unstructured free-form text.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230913_172028748_211__id.csv
0 rows

File structure

Notes: The file appears to be unstructured and contains only a single line with a Swiss IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or structured data. Since the content is free-form and contains no embedded emails or phone numbers in a prose format, it is classified as unstructured with no columns to map. The IBAN is financial data, not personal PII, and thus not mapped to any field.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230914_172025265_220__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). No structured columns or PII fields are present. The line appears to be a standalone financial identifier rather than part of a structured dataset. Since there is no consistent delimiter, header, or multiple columns, this qualifies as unstructured text with no importable PII columns to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230915_172052143_209__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with placeholder column names ("id", "INTERNAL", repeated twice). No actual data rows were provided to analyze for PII values. All columns appear to be internal identifiers and should be skipped per rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230918_172046812_203__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN number (CH8704835061435161001). There is no structured tabular data with columns or headers. The file appears to be a standalone financial identifier rather than a data breach record set. Since there is no consistent delimiter or row structure, and it contains only one value, this is classified as unstructured free-form text with no column mapping possible.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230919_172040964_208__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing only an IBAN (CH8704835061435161001). There is no consistent delimiter, no header, and no repeated structure across lines. The content is purely a financial identifier and does not constitute structured PII columns.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230920_172055602_214__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN (CH8704835061435161001). No columnar structure or multiple rows exist to map to PII fields. IBANs are financial identifiers and not considered PII per the exclusion rules (they are not physical addresses, usernames, or direct personal identifiers). Since there is no consistent delimiter, no header, and only one line of data, this is classified as unstructured with no columns to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230921_172037710_215__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent delimiter structure; appears to be a single line of data or note rather than a CSV with columns

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230922_172041030_204__id.csv
0 rows

File structure

Notes: This is unstructured data containing only an IBAN (CH8704835061435161001). There are no consistent columns or structured records. The sample consists of a single line with a bank account identifier, which is not classified as PII under the provided rules. No email or phone numbers are visible, and the format does not show any row structure. Therefore, it is classified as unstructured with no column mappings.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230925_172039443_217__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only line or placeholder row. The first row shows only column labels "id" and three repeated "INTERNAL" tags, with no actual data values present. Since there is no sample data to analyze for PII patterns, and no meaningful column names indicating PII, we return an empty columns object. The structure suggests this might be the beginning of a structured CSV file, but insufficient data exists in the provided rows to map any columns to PII fields.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230926_172107448_207__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001), not a structured dataset. The file is unstructured with no consistent columns or header. The IBAN is a financial identifier, not a PII field per the exclusion rules (financial/transactional data must be skipped). Since there are no repeated lines or structured columns, this is correctly classified as unstructured free-form text with no embedded emails or phones.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230927_172034470_219__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet or placeholder with repeated 'INTERNAL' labels. No actual PII columns or data values are present in the first 50 rows to map. The file likely contains only internal identifiers without any personal or sensitive information in the visible portion.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230928_172039296_210__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet with repeated 'INTERNAL' labels indicating no actual PII content is visible. All columns are marked as internal identifiers and contain no personal or sensitive information. No PII fields can be mapped from this header alone.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20230929_172041028_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row containing only internal identifier labels (all 'INTERNAL'). No PII values appear in the first 50 rows. Columns are all internal IDs and must be skipped per exclusion rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231002_172122845_203__id.csv
0 rows

File structure

Notes: free-form text with embedded financial data (IBAN), no consistent column structure visible in the sample

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231003_172104765_212__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number (CH8704835061435161001). No structured columns or PII fields are present beyond this financial identifier, which is not mapped as PII per rules. The file appears to be a standalone financial record snippet rather than a delimited dataset.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231004_172038289_207__id.csv
0 rows

File structure

Notes: The provided input is a single line containing an IBAN (CH8704835061435161001) rather than a delimited file with structured columns. This appears to be a snippet of financial data from the breach context described, but it does not represent a structured dataset with multiple rows and columns. Since there is no consistent delimiter or row structure, and this is a single line, it is classified as unstructured. No PII columns can be mapped from this snippet.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231005_172045181_208__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet only contains header row with placeholder 'INTERNAL' labels and no actual PII values. No columns can be mapped to PII fields based on the available information.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231006_172043286_205__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001) with no surrounding context or structure. The data provided appears to be a standalone IBAN rather than part of a structured dataset or free-form text with embedded PII. Since there are no headers, no consistent delimiter, and no additional lines to analyze for structure or embedded PII, this cannot be mapped to any PII fields. The IBAN itself is not classified as PII under the provided field types.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231009_172104275_201__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number. The data appears to be a raw snippet rather than a structured table with multiple columns. No consistent delimiter or header exists, and it does not represent a CSV or other structured format. The IBAN is not a PII field per the provided definitions, so no columns are mapped. This file is likely part of a free-form text dump from the breach.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231010_172053223_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file contains only internal identifier columns labeled 'INTERNAL' repeated across all rows and columns. There are no PII fields present. All columns are internal IDs and should be skipped.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231011_172043886_209__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample only shows the header row which contains non-descriptive column names like 'id' and 'INTERNAL' repeated three times. These are clearly internal identifiers or placeholder headers and do not correspond to any PII fields. No PII values are present in the sample to map to any fields. Given the context of a corporate financial data breach, further rows likely contain financial and transactional data rather than personal identifiable information. Based solely on this sample, no PII columns can be identified.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231012_172043832_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet with three internal identifier columns labeled 'INTERNAL'. No PII fields are present in this header row. The context indicates this is part of a corporate financial data breach from Zynex, but the visible rows contain only internal IDs without any personal or contact information.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231013_172053933_204__id.csv
0 rows

File structure

Notes: This is a free-form text file (not a structured CSV/TSV) containing unstructured data. The sample shows a single IBAN value 'CH8704835061435161001' which is a Swiss bank account number but not personally identifiable information (PII) by itself. There is no consistent columnar structure or header; the file appears to be a raw data dump or note rather than a delimited dataset. Since there is no repeating pattern or structured layout, this qualifies as unstructured content. No PII columns can be mapped.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231016_172100173_211__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN (CH8704835061435161001). There is no consistent delimiter or row structure, and the content is purely financial/accounting data (bank account identifier) without any personal PII fields. The file does not contain any email addresses, phone numbers, or other PII. It represents a standalone financial record from the Zynex breach context.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231019_172018816_206__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN; no structured columns present

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231020_172127174_210__id.csv
0 rows

File structure

Notes: This appears to be a single line containing an IBAN number (CH8704835061435161001) rather than a structured dataset. The sample shows no delimiter or column structure, and the data appears to be unstructured financial/accounting data from Zynex's internal records. Since there is no consistent row structure and only one line is provided, this is classified as unstructured text.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231023_172059306_202__id.csv
0 rows

File structure

Notes: This file is unstructured raw text containing an IBAN number (CH8704835061435161001). There is no consistent delimiter or row structure; it is a single line or free-form text file. IBAN is a financial identifier, not PII per the exclusion rules, so no columns map to PII fields.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231025_172047285_201__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing only an IBAN number (CH8704835061435161001). No structured columns or header exist, and there are no emails or phone numbers visible. IBAN is not a PII field per the defined schema. Therefore, no PII columns can be mapped.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231026_172035016_203__prtry.csv
0 rows

File structure

Notes: This is a free-form text file containing only the header "id" and three repeated "INTERNAL" lines. There are no structured columns, and no identifiable PII is visible in the sample. The content appears to be a placeholder or metadata note rather than actual breach data.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231027_172045969_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only row or metadata line, not actual data rows. The file shows only column labels that are all marked as 'INTERNAL' and there are no sample data values to map. Since there are no actual PII-containing rows in the first 50 lines, no columns can be mapped. This is likely a placeholder or metadata header before the actual data begins.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231030_172031841_200__prtry.csv
0 rows

File structure

Notes: The file is unstructured free-form text with no consistent delimiter or column structure. The first few rows appear to be header-like labels ('id', 'INTERNAL') but there is no repeating structure across rows, and the context indicates this is likely a README or description file rather than structured data containing PII. No embedded emails or phone numbers are visible in the sample.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231031_172125255_205__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001) with no structured columns or additional rows. As there is no consistent delimiter or row structure, and the file appears to be unstructured data (a single value line), it is classified as unstructured. No PII columns can be mapped from this line alone.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231101_172109560_319__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) with no delimiter or structure. The file is unstructured and does not contain any row structure or columns. It is likely a standalone financial record or identifier rather than a dataset with multiple rows and columns. Since there is no consistent delimiter, varying line shapes, and it contains financial data rather than PII, it is classified as unstructured.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231103_172028621_317__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only row or metadata line with no actual data records. The sample shows only three columns labeled 'id' and 'INTERNAL' (repeated twice), which are internal identifiers and not PII. No PII fields can be mapped from this header alone. Additional rows with actual data would be needed for proper PII mapping.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231106_172110173_306__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, not structured tabular data

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231108_172044676_310__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; contains only a single IBAN value without any row-based format or repeated pattern. This is not a structured CSV/TSV table with columns.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231109_172037867_318__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is a header-only snippet showing only column labels 'id' and several 'INTERNAL' tags. No actual data rows are present to analyze for PII content. Based solely on these headers, no PII fields can be identified or mapped. The 'id' column is an internal identifier and should be skipped. Additional rows with real data are required for accurate PII mapping.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231110_172042859_308__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The first 50 rows appear to be header-free or internal metadata rows with no discernible PII. The first row shows the word 'id' and four repetitions of 'INTERNAL', indicating this is likely a header row or placeholder for internal identifiers. No columns contain recognizable PII fields. Further rows need inspection to identify actual PII columns.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231116_172052897_320__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing only an IBAN (CH8704835061435161001). There are no structured columns, headers, or multiple rows. The IBAN itself is a financial identifier, not personal PII, and does not belong to any known PII field category. Since there is no consistent row structure and the file is not tabular, it is classified as unstructured.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231117_172038676_312__id.csv
0 rows

File structure

Notes: The provided snippet appears to be a single IBAN number rather than a structured table. The data sample contains only the IBAN 'CH8704835061435161001' and no visible columnar structure or header. Since this is not a delimited file with consistent columns and appears to be a single value, it is classified as unstructured. However, IBANs are not considered PII per the provided field types, so no PII columns are mapped.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231120_172043217_307__id.csv
0 rows

File structure

Notes: This is a free-form text sample showing a Swiss IBAN number (CH8704835061435161001) and no structured columns. The breach context describes financial records but this snippet lacks any CSV-like structure. Since there is no consistent delimiter or row structure and we see a financial identifier, this should be processed as unstructured text for embedded PII extraction.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231121_172035365_309__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN number (CH8704835061435161001). There are no structured columns or rows — it is not a CSV or delimited file. IBANs are financial account identifiers, not personal PII per the defined field types, so no mapping is performed.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231122_172036600_315__id.csv
0 rows

File structure

Notes: This is unstructured text containing only an IBAN (CH8704835061435161001) and no structured data. The file appears to be a single line or fragment with no delimiter structure, no header, and no repeated rows. IBAN is not a PII field under the defined schema, so no columns map to PII.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231124_172108264_313__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only snippet showing placeholder column labels ('INTERNAL'). No actual data rows are present to analyze for PII mapping. All visible columns are marked as INTERNAL and therefore skipped per exclusion rules.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231127_172103408_316__id.csv
0 rows

File structure

Notes: This is unstructured free-form text containing only an IBAN number (CH8704835061435161001). There are no consistent columns or structured data patterns. The file appears to be a single line or fragment with no headers or delimited fields. Since there is no row structure and the content is not tabular, this is classified as unstructured.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231129_172109219_314__id.csv
0 rows

File structure

Notes: This is a single-line file containing a Swiss IBAN (CH8704835061435161001). There is no structured tabular data or delimiter-separated columns. The IBAN is a bank account identifier, not PII as defined in the schema (it is financial/account data). Since there is no consistent structure with columns, this is classified as unstructured free-form text with no embedded emails or phones visible.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231130_172103319_311__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN (CH8704835061435161001). There are no consistent delimiters, structured rows, or repeated patterns. The file does not contain any identifiable PII fields such as names, emails, or addresses. The IBAN alone does not qualify as PII in this context since it lacks additional personal or account information.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231201_172023156_422__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN (CH8704835061435161001) with no structured columns or rows. It does not contain any PII fields like names, emails, or addresses. The IBAN itself is a financial identifier and not considered PII for this context. Since there are no structured columns or multiple rows, this is classified as unstructured with no column mapping.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231204_172119436_428__prtry.csv
0 rows

File structure

Notes: The file appears to be a simple headerless list of internal identifiers with no structured columns. The provided lines show only 'id' and repeated 'INTERNAL' values, indicating no PII-containing data in this snippet. Based on the breach context (Zynex corporate financial records), this is likely an internal reference file with no customer PII. No structured columns to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231205_172043785_427__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured data or column headers present. The IBAN is a financial identifier, not personal PII, and does not fall under any of the defined PII fields (email, phone, dob, etc.). Since there is no structured record format and no repeated patterns, this is classified as unstructured with no columns to map.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231206_172024832_423__id.csv
0 rows

File structure

Notes: free-form text with only IBAN visible, no consistent delimiter or structured rows

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231207_172027775_424__id.csv
0 rows

File structure

Notes: The provided text is a single line containing an IBAN number (CH8704835061435161001). There is no consistent delimiter, no header, and the data appears to be free-form text. Since there are no structured columns and the data does not conform to a tabular format, this is classified as unstructured data. No PII columns can be mapped from this single line.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231211_172012968_426__id.csv
0 rows

File structure

Notes: The provided sample is not a delimited file but a single line containing an IBAN number. There are no structured rows or columns to map. IBANs are financial identifiers and not considered PII per the exclusion rules. No PII fields can be mapped from this sample.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231213_172052730_421__id.csv
0 rows

File structure

Notes: The provided sample is not structured data but a single IBAN value 'CH8704835061435161001'. There are no consistent columns, headers, or delimiters visible in the sample. The file appears to be a simple text snippet containing only a Swiss bank account number, which is not classified as PII under the provided rules (IBANs are financial identifiers, not personal identifiers). Since there is no structured format and no repeated lines to analyze, this is treated as unstructured content with no column mapping required.

finanzen__zed_files__2023___done__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231214_172028880_425__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing only an IBAN number (CH8704835061435161001). No consistent delimiter or header exists, and the content is not structured data. IBAN is not a PII field per the rules (it's a bank account identifier, not personal identifiable information). Therefore, no columns are mapped.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231215_172049311_310__id.csv
0 rows

File structure

Notes: The provided text is not a structured data file. It contains only a single IBAN value (CH8704835061435161001) which is a bank account identifier, not personal PII. The breach context describes internal corporate financial records from Zynex, but this sample shows no actual structured records with PII columns. This appears to be a fragment or note rather than a data file with columnar structure.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231218_172032512_314__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only row or placeholder with no actual data rows. The header indicates all columns are internal identifiers (labeled 'INTERNAL'), which according to exclusion rules must be skipped. No PII fields are present in the sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231219_172043347_313__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File appears to be a header-only row or placeholder file with no actual data rows. The headers ('id', 'INTERNAL' repeated three times) indicate internal identifiers that do not contain any PII. No meaningful data to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231220_172046127_306__id.csv
0 rows

File structure

Notes: The sample provided is a single line containing an IBAN number (CH8704835061435161001). There are no consistent delimiters or structured columns present. The file appears to be a simple unstructured text file with potentially embedded financial identifiers. Since this is free-form text with no consistent structure, it is classified as unstructured with no column mapping performed.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231221_172042195_307__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File appears to be a header-only row or placeholder with no data rows. The first line lists 'id' and three 'INTERNAL' fields, which are internal identifiers and not PII. No actual data rows are present in the sample to analyze for PII content.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231222_172053849_308__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header row consisting solely of the string 'INTERNAL' repeated 14 times, with an initial 'id' column. There are no actual data rows visible in the sample to analyze for PII content. Given the context of a corporate data breach involving internal financial records, these columns likely represent internal identifier fields that should be mapped to 'skip' per exclusion rules. No PII fields can be identified from this header alone.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231227_172110210_309__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row or placeholder file. The provided rows contain only the word 'INTERNAL' repeated, with no actual data or PII values. No columns map to PII fields.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231228_172017269_311__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20231229_172031329_312__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header row containing only the string 'INTERNAL' repeated multiple times, with an initial 'id' column. There are no actual data rows or identifiable PII fields in this sample. Since all columns are labeled as 'INTERNAL' and contain no meaningful values, no PII columns can be mapped. This likely represents an internal identifier or placeholder row rather than actual breach data.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240103_172021515_201__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only column headers labeled 'INTERNAL' repeated multiple times with no actual data values. Since there are no identifiable PII values or meaningful column names, no PII fields can be mapped. The file appears to be a placeholder or metadata-only export with no actual personal data exposed in this snippet.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240104_172105061_205__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN (CH8704835061435161001) with no structured columns or row patterns. The file is not a CSV or table but a single line of unstructured data. No column mapping is possible.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240105_172045731_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row showing only internal identifier columns. No PII is present in the sample. All columns are marked as INTERNAL and will be skipped per exclusion rules.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240108_172032711_203__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number (CH8704835061435161001). There are no structured columns, headers, or multiple rows in the provided data. The IBAN is a bank account identifier, not personal PII as defined in the schema. Since this is unstructured text with no consistent delimiter or row structure, it is classified as unstructured.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240109_172044649_202__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN (CH8704835061435161001). There is no consistent columnar structure or header. The IBAN is a bank account identifier and not considered PII under the defined categories (it is not email, phone, name, address, etc.). No structured data to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240110_172041500_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet or placeholder with no actual rows containing PII. All visible columns ('id', 'INTERNAL') are internal identifiers and do not contain any personal or sensitive information. No PII fields can be mapped from this sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240111_172027452_425__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent column structure or header present; appears to be a single line of unstructured data (likely a note or snippet from a financial record). The IBAN is a financial identifier, not PII, and should be handled as sensitive financial data rather than a PII field.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240112_172044074_424__id.csv
0 rows

File structure

Notes: The provided input is a single line containing a Swiss IBAN number (CH8704835061435161001). This is not a structured dataset with columns; it appears to be a standalone financial identifier possibly from a breach context involving Swiss financial records. Since there is no consistent row structure, delimiter, or header, and the content is a single value, this qualifies as unstructured data. However, IBANs themselves are NOT considered PII per the defined field types (they are financial identifiers), so no PII fields are mapped. The file should be processed as unstructured with the note that it contains a Swiss IBAN.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240115_172029260_429__id.csv
0 rows

File structure

Notes: This is a free-form text containing only an IBAN (CH8704835061435161001) and no structured columns. The file is unstructured and does not contain any consistent delimiter or header. No PII columns can be mapped as there is no structured data to analyze.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240116_172050451_432__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only snippet or placeholder. The first row shows 'id' and three 'INTERNAL' labels, but no actual data rows are provided to analyze. Without data rows containing values, no PII fields can be identified or mapped. The structure suggests this may be the beginning of a structured CSV file, but further rows are needed for accurate column mapping.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240117_172053780_433__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent row structure or delimiter patterns. Single line contains only one IBAN, no emails/phones. This is likely a fragment of a financial document rather than a structured dataset.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240119_172106761_431__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured data, header, or repeated pattern across rows. The content is purely a financial identifier and does not represent a delimited dataset. Since there are no repeated rows or structured fields, this is classified as unstructured content with no importable columns.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240122_172033368_430__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only a header row with 'id' and three 'INTERNAL' labels, no actual data rows. There are no visible PII fields in the header or sample. Based on the breach context (Zynex internal financial records), we would expect columns like customer names, emails, or addresses in the full dataset, but they are not present in this sample. Since there are no identifiable PII columns in the first 50 rows, the columns object is empty.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240123_172042363_426__id.csv
0 rows

File structure

Notes: This file is unstructured free-form text. The sample shows only a single IBAN number (CH8704835061435161001) and no consistent columnar structure. There are no repeated lines with consistent delimiters or column patterns. The content appears to be a single data snippet rather than a table, meeting the criteria for unstructured handling with embedded financial data (IBAN).

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240125_172039281_428__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured data or header. The line does not contain any identifiable personal information (PII) such as names, emails, or phone numbers. It appears to be a standalone financial identifier, possibly from a financial record or invoice. Since there is no consistent structure across lines (only one line provided), and no embedded emails or phone numbers, this is classified as unstructured with no columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240126_172102423_427__id.csv
0 rows

File structure

Notes: The provided snippet is not a structured file with consistent columns or delimiters. It appears to be a single line containing an IBAN number (CH8704835061435161001), which is a financial identifier and not personal PII. Since there is no consistent structure or multiple rows to analyze, and the content does not match a typical CSV/TSV format, this is classified as unstructured. No columns can be mapped as there is no row structure.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240130_172131325_434__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN; no consistent column structure or header present. Contains only a single IBAN value (CH8704835061435161001) and no other structured data. No emails or phone numbers visible in the sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240201_172100464_309__id.csv
0 rows

File structure

Notes: This is unstructured data - a single line containing an IBAN number (CH8704835061435161001). There is no consistent delimiter or row structure. Per rules, we treat this as unstructured text with embedded PII (financial account number). The IBAN itself is considered PII as it can identify financial accounts, but since the file lacks structure, we return empty columns and flag as unstructured.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240207_172047051_318__id.csv
0 rows

File structure

Notes: The provided input is a single unstructured line containing an IBAN (CH8704835061435161001) and no other data. There are no consistent delimiters, headers, or structured columns to map. This appears to be a snippet of financial data rather than a breach file with PII columns. Since there is no structured format, we treat it as unstructured with no columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240209_172033975_323__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN (CH8704835061435161001) and no structured columns. The file is unstructured and does not contain any consistent delimiter or header. No PII fields can be mapped as there are no identifiable columns.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240212_172059582_312__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row containing only internal identifier labels. No PII values present in the first 50 rows. All columns are marked as INTERNAL and therefore skipped per exclusion rules.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240213_172026790_317__id.csv
0 rows

File structure

Notes: This appears to be unstructured data — a single line containing a Swiss IBAN (CH8704835061435161001) without any delimiter structure or header. No consistent CSV/TSV structure exists in the sample. Since it's a single line with no repeated pattern and no embedded emails/phones beyond the IBAN (which is financial account data, not personal PII), we treat it as unstructured free-form text. The IBAN itself is financial account information and not mapped to any PII field in our schema.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240214_172112141_310__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured data or column format present. The file appears to be a standalone IBAN value rather than a delimited dataset with headers and rows. As per the unstructured opt-out rules, since there is no consistent delimiter or row structure, and this is just a single line with financial identifier data, we return an empty columns object.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240215_172102827_314__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN number (CH8704835061435161001). There are no structured columns or headers. IBAN is a banking identifier, not PII, and the file lacks any discernible structure or repeated data rows. As per rules, unstructured files with no row structure return an empty columns object.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240216_172037355_321__prtry.csv
0 rows

File structure

Notes: The file contains only internal identifier headers labeled 'INTERNAL' with no actual data rows shown in the sample. No PII is present in this snippet, and the structure appears to be free-form text without consistent columnar data. Given the context of a breach involving internal corporate records, this appears to be a header-only or placeholder file with no actionable PII.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240219_172105646_316__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only file or the first row contains only column labels without actual data. All columns are labeled 'INTERNAL' repeatedly, indicating these are internal identifier columns that should be skipped per exclusion rules. No PII fields are present in the visible structure.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240220_172109821_311__id.csv
0 rows

File structure

Notes: This is a free-form text sample containing only an IBAN number (CH8704835061435161001) with no consistent columnar structure. The sample does not show any row-based pattern, and appears to be unstructured data. IBAN is not classified as PII in the provided field list. No column mapping is possible.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240221_172052077_319__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text containing only an IBAN number. The file appears to be a standalone financial identifier rather than a structured dataset with columns. Since there are no consistent columns or structured data patterns, this is classified as unstructured text. The IBAN itself is not a PII field in the defined schema, so no columns are mapped.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240222_172043047_322__id.csv
0 rows

File structure

Notes: This appears to be a single unstructured line containing an IBAN number (CH8704835061435161001) rather than a delimited file with multiple columns. The sample shows only one line with no delimiter structure, no header, and no consistent row pattern. As per the unstructured opt-out rules, when there is no consistent delimiter structure across lines and the file appears to be free-form text, we return an empty columns object.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240223_172034211_313__id.csv
0 rows

File structure

Notes: The sample provided is a single line containing an IBAN number (CH8704835061435161001) rather than structured columnar data. This is not a CSV or any structured format with columns. The context describes a corporate data breach but the actual data sample is unstructured and contains only one financial identifier. Since there is no consistent delimiter, varying line shapes, and embedded financial data, this is classified as unstructured text with embedded financial identifiers.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240226_172043618_320__id.csv
0 rows

File structure

Notes: The provided sample is a single line containing only an IBAN number (CH8704835061435161001). There are no structured columns or delimiters visible. This appears to be unstructured financial data from a breach of Zynex, a Swiss web hosting company, involving sensitive internal financial records. The IBAN itself is not a PII field per the defined categories, but it is a financial identifier. Since there are no consistent columns or structured data in the sample, this is classified as unstructured text.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240228_172114489_315__id.csv
0 rows

File structure

Notes: The sample provided is not structured data. It appears to be a single line containing a Swiss IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or multiple rows to analyze for structured PII columns. This file is likely a raw text dump or part of an unstructured document where PII must be extracted via free-form processing. The IBAN itself is financial/accounting data and not classified as PII under the provided field types; however, unstructured processing may still identify any embedded emails or phone numbers present in other parts of the file.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240301_172051301_535__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header-like lines with 'INTERNAL' repeated, indicating this is likely a placeholder or metadata row rather than actual data. No PII fields are present in this snippet. Further rows are required to identify actual PII columns.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240304_172124874_545__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN number (CH8704835061435161001) and no structured columnar data. There are no consistent delimiters, no headers, and no repeated line structures across the sample. The IBAN is a financial account identifier, not personal PII, and does not meet criteria for mapping to any PII field in our schema. No columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240305_172036806_551__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to contain only internal identifier columns labeled 'INTERNAL' repeated multiple times. No PII fields are present in the first 50 rows. All columns are internal IDs and should be skipped per exclusion rules.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240306_172032440_543__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN pattern, no consistent column structure

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240307_172028890_547__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only header row visible, no data rows provided. All visible columns are labeled INTERNAL and contain no PII. No actionable PII columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240308_172042748_536__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only file or a metadata file containing only column names labeled as INTERNAL. There are no actual data rows provided, and the columns are all marked as INTERNAL which suggests they are internal identifiers or system columns that should be skipped according to rules. No PII fields are present in the visible data.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240311_172029940_541__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The first 50 rows appear to be header metadata or placeholder rows indicating 'INTERNAL' repeatedly. No actual data or PII fields are visible in this sample. The structure suggests this is a header-only or metadata file with no actionable PII to map. All visible entries are non-PII internal markers.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240312_172038041_540__prtry.csv
0 rows

File structure

Notes: The file appears to be unstructured with only a single header-like line followed by three repeated 'INTERNAL' entries. No consistent delimiter or structured data is present across lines, and no PII is visible in the sample. This is likely a placeholder or metadata file rather than a data breach record containing personal information.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240313_172027262_548__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only file or a metadata file showing only internal column labels without any actual data rows. The first row contains placeholder 'INTERNAL' labels repeated three times, indicating this is likely a template or placeholder file rather than actual PII-containing data. No PII columns can be mapped from this header alone.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240314_172041199_538__prtry.csv
0 rows

File structure

Notes: This is unstructured data - the sample shows only a header row with 'id' and multiple 'INTERNAL' labels, followed by no actual data rows. There is no consistent delimiter or structured format present in the sample. The breach context indicates this is internal corporate data from Zynex, but the sample provided lacks any actual PII-containing rows or structure to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240315_172107976_544__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is a header-only snippet showing only internal identifier columns labeled 'INTERNAL'. No PII fields are present in this snippet. The breach context indicates this is part of Zynex's internal financial records, but this specific file contains only internal IDs with no personal or sensitive data.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240318_172052384_550__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only snippet or metadata row without actual data rows. The provided lines only contain the word 'INTERNAL' repeated, indicating this is likely a placeholder or security marker rather than actual PII data. No PII fields can be mapped from this sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240320_172030008_537__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only row or a placeholder file. The first line shows 'id' followed by three 'INTERNAL' markers, indicating this is likely a template or metadata file rather than actual data records. No PII fields are present in this snippet. The breach context describes financial and customer data, but this specific file contains no importable structured records with PII.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240321_172031348_549__id.csv
0 rows

File structure

Notes: This is unstructured financial data with IBAN and bank account number. No consistent columnar structure is present; the data appears to be free-form financial records. It does not contain standard PII columns like name, email, or phone, but does contain a bank account number (CH8704835061435161001) which is financial data but not a standard PII field. Since there is no consistent delimiter or header structure, and the content is purely financial, this is classified as unstructured.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240326_172109152_546__id.csv
0 rows

File structure

Notes: The provided content is not a delimited data file. It appears to be a single line containing an IBAN number (CH8704835061435161001) rather than a structured dataset with multiple rows and columns. There is no consistent delimiter pattern or row structure visible in the sample. Since this is not a structured CSV/TSV file with repeating rows, it falls under the unstructured category. However, standalone IBANs are not considered PII in this context as they appear to represent a corporate bank account rather than customer data.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240327_172141046_539__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN but no consistent column structure

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240328_172059075_542__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (not email/phone), no structured columns present

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240402_172135158_200__id.csv
0 rows

File structure

Notes: The provided data appears to be free-form text (a snippet of IBAN data and no structured columns). There are no consistent delimiters, row structures, or headers visible in the sample. It lacks any CSV/TSV-like format, and the snippet shows only a single IBAN value. Per unstructured rules, return empty columns.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240403_172033388_207__id.csv
0 rows

File structure

Notes: This is unstructured financial data containing only an IBAN number (CH8704835061435161001) and no identifiable personal information. No structured columns exist; this appears to be a raw snippet of financial transaction data rather than a delimited record set with personal fields. No PII mapping possible.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240404_172058663_205__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only a Swiss IBAN (CH8704835061435161001). There are no columns or structured data. IBANs are financial account numbers and not classified as PII per the defined schema. Since there is no row structure, delimiter, or header, this is classified as unstructured text. No PII fields can be mapped.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240405_172039986_208__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number. No structured data or PII fields are present. The line does not represent a record with columns; it is a standalone value. IBAN is financial account information and not mapped to any PII field in our schema. No structured columns exist to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240409_172025954_201__prtry.csv
0 rows

File structure

Notes: This file appears to be a header-only snippet with placeholder column names indicating 'INTERNAL' repeatedly. No data rows or structured content exist in the provided sample. There are no visible PII patterns or consistent delimiters. The breach context describes financial records, but this file alone is not structured and contains no importable data fields.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240410_172054970_202__id.csv
0 rows

File structure

Notes: This is a free-form text containing only an IBAN (CH8704835061435161001). There is no consistent delimiter or row structure present in the provided sample. The file appears to be unstructured data, possibly from a note or snippet rather than a structured dataset. Since there is no consistent column structure and the content is a single IBAN, this is classified as unstructured.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240412_172041506_203__id.csv
0 rows

File structure

Notes: This is not a structured dataset. The provided sample is a single line containing an IBAN (CH8704835061435161001) rather than a delimited file with columns. The IBAN is a financial identifier and not personally identifiable information in the context of this breach description. The file appears to be a raw snippet or note, not a CSV/TSV/other structured format. No column mapping is possible as there is no consistent row structure.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240416_172028008_204__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No structured columns or consistent delimiter detected; appears to be a note or standalone value, not a row-based dataset. This is likely part of a financial record or comment in the breach data.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240418_172032107_206__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet contains only column headers labeled 'id' and 'INTERNAL' repeated three times. These appear to be internal identifiers or placeholder columns with no actual PII values visible. No mappable PII fields are present in this sample. All columns are likely to be skipped per exclusion rules (internal IDs).

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240423_172036523_420__id.csv
0 rows

File structure

Notes: The provided sample is not a structured file with consistent columns or delimiters. It appears to be a single line containing an IBAN (International Bank Account Number) rather than a delimited dataset. There is no header or repeated structure across rows, and the content is a single financial identifier. Since there is no consistent row structure and the data is not in a tabular format, this is classified as unstructured text. No PII columns can be mapped because there are no columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240425_172105448_419__id.csv
0 rows

File structure

Notes: This is a single-line file containing an IBAN (CH8704835061435161001). It lacks any structured tabular format or repeated rows. IBANs are financial identifiers and not classified as PII under the defined fields. No columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240430_172051177_421__id.csv
0 rows

File structure

Notes: The provided input is a single line containing only an IBAN (CH8704835061435161001). There is no structured data, no delimiter, and no header. This is unstructured text with no embedded emails or phone numbers visible. Per the unstructured opt-out rules, this is treated as free-form text with no column structure to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240501_172048855_534__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN (CH8704835061435161001). There are no structured columns or records to map. The file appears to be a standalone IBAN value, possibly from a financial record, but it lacks any header or structured format that would allow column mapping. Since it's a single line with no delimiter or structure, it is classified as unstructured.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240502_172109258_526__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN (CH8704835061435161001). There is no structured data, header, or multiple rows. IBAN is not a PII field per the provided definitions, so no columns are mapped. The file appears to be a snippet or fragment rather than a dataset with rows and columns.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240503_172029459_522__id.csv
0 rows

File structure

Notes: The provided data is unstructured and free-form. The sample consists of a single line containing an IBAN (CH8704835061435161001), which is a bank account number and not classified as PII under the specified rules. There is no consistent delimiter or row structure, and the content does not match any expected structured format. Therefore, it is classified as unstructured text with no column mapping required.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240506_172053324_524__id.csv
0 rows

File structure

Notes: The provided sample is free-form text with a single IBAN value (CH8704835061435161001). There is no consistent delimiter structure across lines, and the data appears to be unstructured notes or a snippet rather than a table with columns. Since there is no row structure and the data is not tabular, this should be treated as unstructured text for further processing.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240507_172111758_535__id.csv
0 rows

File structure

Notes: This file appears to contain unstructured financial data and IBAN numbers rather than structured personal records. The single line sample shows only a Swiss IBAN number (CH8704835061435161001) which is a bank account identifier and not considered PII under standard breach classification rules for this context. No consistent column structure or personal identifiers (names, emails, etc.) are visible in the provided sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240510_172038158_532__id.csv
0 rows

File structure

Notes: The provided snippet is a single unstructured value (Swiss IBAN) with no delimiter or column structure. The value 'CH8704835061435161001' is a Swiss bank account number (IBAN) and does not constitute a row or table. No structured columns exist in the sample, and the data appears to be free-form text with no consistent format. Therefore, this is classified as unstructured text with no importable columns.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240513_172045778_525__id.csv
0 rows

File structure

Notes: This file is unstructured free-form text containing an IBAN (CH8704835061435161001) and no consistent column structure. It does not contain CSV/TSV/structured data rows, so no column mapping is possible. The IBAN is not considered PII in this context as it is a bank account identifier, but it is included in the unstructured text.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240514_172103845_523__id.csv
0 rows

File structure

Notes: The provided text is not structured data; it's a single line containing an IBAN number (CH8704835061435161001) rather than a delimited file with columns. Since there's no consistent delimiter or row structure, and it doesn't represent a CSV or other structured format, this is classified as unstructured free-form text. No column mapping can be performed.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240515_172107122_531__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing only a Swiss IBAN number (CH8704835061435161001). No CSV structure or column headers are present, and IBAN is not a PII field per the rules. Therefore, no columns are mapped and the format is marked as unstructured with no PII columns to process.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240517_172040641_527__prtry.csv
0 rows

File structure

Notes: The file appears to be unstructured data with only headerless internal identifiers repeated. No PII is visible in the sample and there is no consistent column structure. This matches the description of internal corporate data breach files which often contain only internal reference IDs at the top of files before actual data rows.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240521_172113452_530__id.csv
0 rows

File structure

Notes: free-form text with no consistent structure or columns. Sample shows only a Swiss IBAN number (CH8704835061435161001) and no other structured data. This is likely a fragment of a financial record rather than a full dataset. No identifiable columns exist to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240528_172042169_529__id.csv
0 rows

File structure

Notes: This is not a structured file but a single line containing a Swiss IBAN (CH8704835061435161001). There are no consistent delimiters, headers, or repeating structures across lines — it's a standalone value. IBANs are financial identifiers, not personal PII, and are excluded by the rules for financial/transactional data. No mapping is required.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240530_172032886_528__id.csv
0 rows

File structure

Notes: The sample provided is a single line containing only an IBAN (CH8704835061435161001). There is no consistent delimiter or structured row format across lines (only one line shown). IBANs are financial identifiers and not considered PII per the rules. Since there is no row structure and the sample is unstructured, we classify this as unstructured with no columns to map. No emails or phones are visible in this snippet.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240531_172145423_533__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent column structure present in the sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240604_172058130_309__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be only the header row with placeholder column names 'id', 'INTERNAL', 'INTERNAL', and 'INTERNAL'. No actual data rows or PII values are present in the sample to map to PII fields. Therefore, no columns can be mapped to PII fields based on the given sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240605_172104696_318__id.csv
0 rows

File structure

Notes: This is unstructured text containing only an IBAN (CH8704835061435161001). No structured columns exist in the provided data. IBANs are financial account numbers and are not considered PII in this context per the exclusion rules (financial/transactional data). Therefore, no PII columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240607_172108909_314__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only internal identifier columns labeled 'INTERNAL' repeated across all rows. There are no PII fields present in the first 50 rows. The columns appear to be placeholder headers for internal IDs or reference keys, which are excluded by policy.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240610_172052281_313__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The first 3 rows appear to be header placeholders or metadata, not actual column names or data. No PII is visible in these rows. Further rows are needed to identify PII columns.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240611_172044072_305__prtry.csv
0 rows

File structure

Notes: This is an unstructured file containing only the header row with the word 'INTERNAL' repeated four times. There is no actual data present in the sample rows. Since there are no structured records with PII, this is classified as unstructured with no columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240612_172101198_311__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header row only with placeholder values 'INTERNAL'. No PII fields are present in the visible data. The format is CSV with comma delimiter and quoted fields, but no actual data rows to analyze for PII mapping.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240613_172026054_306__prtry.csv
0 rows

File structure

Notes: The provided text is purely header-less internal identifiers (repeated 'INTERNAL'). No structured data or PII present. This is not a delimited file with records; it is a snippet of placeholder or test data indicating internal use only. No columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240614_172101534_315__id.csv
0 rows

File structure

Notes: The provided input is a single unstructured line containing only an IBAN number (CH8704835061435161001) with no surrounding context or structure. There is no delimiter, header, or multiple rows to analyze. As this is free-form text with no consistent column structure, it qualifies as unstructured data. However, IBANs are not directly mapped to any standard PII field in the provided schema, so no columns are mapped.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240617_172040792_307__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only or metadata file with only internal identifier columns. All columns are marked as INTERNAL and contain no PII data. No actionable PII fields are present in the sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240618_172045487_317__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header row only with placeholder 'INTERNAL' labels repeated four times. No actual data rows are present to analyze for PII mapping. The structure suggests this is an internal identifier column but lacks any meaningful values or structure to map to PII fields. No PII columns can be identified from this sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240619_172058669_308__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN number (CH8704835061435161001) with no structure or other data. There are no columns or headers to map. IBAN is not a PII field per the provided definitions, and the file does not contain any identifiable personal data or structured records. Therefore, it is classified as unstructured with no PII columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240620_172039808_316__id.csv
0 rows

File structure

Notes: The provided data appears to be a single line containing an IBAN (International Bank Account Number) rather than a structured table with columns. The IBAN itself is a financial identifier and not a PII field per the defined schema. Since there is no consistent delimiter or row structure present, and the file appears to be unstructured with no headers or multiple columns, it is classified as unstructured text. No PII columns can be mapped from this single line of data.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240624_172044479_303__id.csv
0 rows

File structure

Notes: The file is a single line containing a single IBAN number (CH8704835061435161001). This is not structured tabular data with columns; it is unstructured text containing a financial identifier. There are no consistent delimiters or repeated patterns across rows, and the data is a single value. Therefore, it should be treated as unstructured content for further processing.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240626_172141150_312__id.csv
0 rows

File structure

Notes: The file appears to be unstructured text containing only an IBAN (CH8704835061435161001). There are no consistent delimiters, headers, or structured rows. The content does not contain any emails or phone numbers in the provided snippet, and the format does not show any column structure. This is likely a free-form document or note rather than a dataset with PII columns.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240627_172111561_304__id.csv
0 rows

File structure

Notes: This is not a delimited file. The sample content shows a single IBAN value 'CH8704835061435161001' with no structure, headers, or multiple rows. The breach context describes financial records, but this snippet is a standalone identifier. No consistent columns exist to map to PII fields. Since this is unstructured data without repeated patterns or delimiters, we classify it as unstructured with no column mappings.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240628_172201134_310__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header-like lines indicating 'id' and 'INTERNAL' repeated three times, with no actual data rows. These appear to be metadata or placeholder headers rather than actual PII-containing columns. No PII fields can be mapped from this snippet.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240701_172104840_201__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There are no structured columns or headers present. The line appears to be a standalone financial identifier rather than part of a delimited dataset. Since there's no consistent structure or multiple fields, this qualifies as unstructured data with no column mapping possible.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240702_172127922_200__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number. There is no consistent delimiter, no header, and no row structure. IBAN is not a PII field per the rules (it's an account identifier, not personal address or identity). No PII columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240703_172040165_202__id.csv
0 rows

File structure

Notes: The provided input is a single unstructured line containing an IBAN (CH8704835061435161001). There is no consistent delimiter, header, or structured data format. This is a free-form text line with no column structure, matching the unstructured opt-out condition where the file contains no importable structured data beyond isolated values.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240704_172100600_206__id.csv
0 rows

File structure

Notes: This is a free-form text snippet containing only an IBAN number (CH8704835061435161001). No consistent column structure or header is present. The IBAN is a financial identifier, not PII per the rules (it's not an address, phone, email, etc.). Since there are no repeated patterns, no structured columns, and this appears to be a standalone line, we classify this as unstructured text with no embedded emails or phones. No PII columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240708_172101554_204__prtry.csv
0 rows

File structure

Notes: The provided data appears to be unstructured free-form text with no consistent column structure. The sample shows only internal identifiers labeled 'INTERNAL' repeated across rows, with no actual PII values visible. Since there is no consistent delimiter or structured format, this is classified as unstructured content. No column mapping is possible.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240709_172020094_212__id.csv
0 rows

File structure

Notes: The provided sample is not a structured dataset with consistent columns. It appears to be a single line containing an IBAN number, which is a financial identifier rather than PII. Since there is no consistent delimiter or structure across lines, and the sample does not represent a tabular dataset, this is classified as unstructured text. No column mapping is performed.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240710_172042855_210__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only file or the first row is just column labels with no actual data rows provided. The headers 'id', 'INTERNAL' (repeated three times) suggest this may be an internal ID or placeholder structure, but no PII values are present in the sample to map. Without data rows containing actual PII, no columns can be confidently mapped to PII fields. This is likely just a schema definition or empty header row.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240711_172056223_202__prtry.csv
0 rows

File structure

Notes: The sample shows only header-less internal IDs (repeated 'INTERNAL' entries). No consistent columnar structure or PII values are visible in the first 50 rows. This appears to be a metadata or index file rather than a data record. Since there is no structured format and no embedded PII in prose, treat as unstructured with no columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240712_172024303_211__id.csv
0 rows

File structure

Notes: The provided snippet is not a structured dataset with columns; it appears to be a free-form text containing an IBAN number (CH8704835061435161001). There are no consistent delimiters or repeating patterns across rows, and the sample does not exhibit any tabular structure. The context indicates this is part of a corporate data breach, but the visible data is unstructured and does not conform to a CSV/TSV/structured format. Since the file appears to be unstructured text with no identifiable column structure, it is classified as unstructured.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240715_172041793_205__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001), which is not personally identifiable information (PII) in the context of breach analysis. There are no structured columns or headers, and the content is purely financial/transactional data without any personal identifiers. The IBAN is a bank account identifier and does not map to any PII fields in our classification system.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240716_172045499_200__id.csv
0 rows

File structure

Notes: This is unstructured text (free-form prose) containing a single IBAN value (CH8704835061435161001). No consistent column structure or header exists; the sample is not tabular data but rather a snippet from breach context or file content. The IBAN is financial data and not a PII field per the defined schema, so no columns are mapped. The file should be processed as unstructured text.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240717_172048497_208__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent columnar structure present — appears to be a single-line snippet or note, not a data table. IBAN is not a PII field in the defined schema (only email, phone, dob, names, address, ssn, password, username, country, gender, suffix, facebookId). This is purely financial/accounting data unrelated to personal identifiers. Returning empty columns object per unstructured rules.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240718_172038171_213__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (not a PII field). No consistent delimiter or row structure exists in the sample. The provided snippet appears to be a single line containing only an IBAN number (CH8704835061435161001), which is not a PII field according to the rules. Since there is no structured data, column mapping cannot be performed.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240719_172035175_207__prtry.csv
0 rows

File structure

Notes: The file appears to be a free-form text document with no consistent column structure. The sample lines show only the word "INTERNAL" repeated, indicating this is likely a placeholder or note file rather than structured data containing PII. No identifiable columns or patterns are present that would allow mapping to PII fields.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240723_172046627_209__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (Swiss bank account number). This is not PII per the defined fields, but appears in unstructured context. No consistent column structure present in sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240726_172113197_203__id.csv
0 rows

File structure

Notes: The provided sample is not a structured file but a single line containing an IBAN number (CH8704835061435161001). There is no consistent delimiter or header structure across lines. The file appears to be a free-form text containing financial data. Since there is no row structure and it appears to be unstructured data with potentially embedded financial identifiers, we classify it as unstructured with no column mapping.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240729_172205102_201__id.csv
0 rows

File structure

Notes: This is a free-form text file (single line containing a Swiss IBAN). No column structure exists, and IBANs are not classified as PII in the provided field types. The content does not contain any structured records or repeated patterns across lines.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240731_172124401_214__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent delimiter or row structure visible in the sample. This is a single-line IBAN value, not a structured CSV/TSV file. The sample shows only one line of data (an IBAN) with no headers or repeating pattern, matching the unstructured opt-out criteria.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240802_172133400_205__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent column structure. The sample is a single line containing only an IBAN, which is financial account data but not personal PII by itself. No structured rows present to map columns.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240806_172139041_210__id.csv
0 rows

File structure

Notes: This is not a structured dataset; it appears to be a single IBAN value (CH8704835061435161001) rather than a delimited file with columns. The breach context describes financial records and customer invoicing data, but this sample shows only one line containing a Swiss bank account number. There are no consistent columns or structured records in this snippet, and it does not contain any PII fields like email, phone, or names. Therefore, it is classified as unstructured free-form text with no column mapping required.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240808_172017949_203__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001) with no structured columns or repeated pattern. It does not represent a CSV or tabular dataset. No PII fields can be mapped from this unstructured content.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240816_172049675_209__id.csv
0 rows

File structure

Notes: This is a free-form text sample with only an IBAN number (CH8704835061435161001). No structured columns or consistent delimiter pattern is visible. The file appears to be unstructured data (possibly a README or note) and does not contain any row structure with PII fields. The IBAN is financial/accounting data, not PII per the exclusion rules.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240819_172048360_208__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample only contains header rows with repeated 'INTERNAL' labels and no actual data rows. No PII fields can be identified from this snippet. The file appears to be a metadata or placeholder file rather than a dataset containing personal information. Additional rows are required to perform proper column mapping.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240820_172048782_207__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent column structure present; appears to be a single-line snippet rather than a data table. Given the context of a corporate financial breach, this is likely a fragment from a financial record or invoice rather than structured PII fields.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240822_172106812_206__id.csv
0 rows

File structure

Notes: This is unstructured text containing only a single IBAN (CH8704835061435161001) and no structured data. There are no consistent columns or delimiters, and the content is not tabular. The file appears to be a raw snippet or note rather than a delimited dataset. Since there are no identifiable PII fields in a structured format and the content is free-form, it is classified as unstructured.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240823_172048042_201__prtry.csv
0 rows

File structure

Notes: The sample shows only a header row with three columns labeled 'id', 'INTERNAL', and another 'INTERNAL' (both repeated). No actual data rows are present in the sample. Since there is no structured data with consistent columns and the file appears to be a header-only snippet or placeholder, it cannot be mapped. The absence of any PII-containing rows means we cannot determine a structured format. Given the context of a corporate data breach, this appears to be a fragment of a file without usable content for mapping.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240826_172042236_202__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN pattern, no structured columns

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240827_172048670_204__id.csv
0 rows

File structure

Notes: This appears to be unstructured free-form text containing a Swiss IBAN (CH8704835061435161001) rather than structured columnar data. The content describes a breach context and contains no actual tabular data with columns to map. No consistent delimiter structure exists across lines.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240828_172102107_200__id.csv
0 rows

File structure

Notes: free-form text with no consistent structure or column pattern — appears to be a single IBAN value, not a data record set

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240830_172039973_211__prtry.csv
0 rows

File structure

Notes: The file appears to be unstructured internal corporate metadata with no consistent columnar data. The sample shows only the word 'INTERNAL' repeated across lines, indicating this is likely a placeholder or header/metadata file rather than actual PII-containing records. No valid PII fields can be mapped from this sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240902_172036778_206__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only file or placeholder with no actual data rows. The first row lists 'id' and four 'INTERNAL' columns, but there are no data rows to analyze for PII. Based on the breach context (Zynex internal corporate data), these 'INTERNAL' columns likely contain internal identifiers that should be mapped to 'skip' per exclusion rules. No PII fields are present in the visible structure.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240903_172132839_215__id.csv
0 rows

File structure

Notes: This file is free-form text containing only an IBAN (CH8704835061435161001). There is no structured tabular data or consistent delimiter. The content is a single line with no headers or multiple rows, making it unstructured.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240904_172032248_207__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample contains only header placeholders 'id', 'INTERNAL' (repeated three times) with no actual data rows or meaningful column names. There are no visible PII values or structured data to map. This appears to be an index or placeholder file rather than a data breach record. No PII columns can be identified from this snippet.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240905_172032360_217__prtry.csv
0 rows

File structure

Notes: This is unstructured data. The sample contains only the words 'id', '2', and 'INTERNAL' repeated four times, showing no consistent column structure or delimiters. There are no visible emails, phone numbers, or other PII patterns in this snippet. The data appears to be a fragment of an internal identifier or logging system, not a breach export containing PII.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240906_172047876_208__id.csv
0 rows

File structure

Notes: The provided input is not a structured delimited file. It contains a single line with an IBAN number (CH8704835061435161001) which is a bank account identifier used in Switzerland and other European countries. This is not personal identifiable information (PII) in the context of the user's request. The file appears to be a simple note or snippet rather than a dataset with columns. Therefore, no column mapping can be performed, and the format is classified as unstructured with no columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240909_172105573_213__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The first 50 rows appear to be a header-only file or metadata indicating column types rather than actual data records. The visible line 'id' followed by 'INTERNAL' repeated four times suggests this is a structural placeholder or schema definition, not a dataset containing PII. No actual personal or sensitive data is present in the provided sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240910_172056272_204__id.csv
0 rows

File structure

Notes: This is unstructured data - a single IBAN value 'CH8704835061435161001' with no consistent column structure or delimiter. The sample is a standalone line containing only a Swiss bank account identifier, which is not classified as PII under the provided field types. No mapping is possible because there are no repeating columns, headers, or structured records.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240911_172021575_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet is a header-only row or placeholder showing only internal ID columns with no actual PII. No columns map to PII fields because the sample contains only internal identifiers ('id', 'INTERNAL') repeated. These are non-negotiable skips under the exclusion rules for internal IDs. No structured PII data is present in the first 50 rows.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240912_172042676_211__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN (CH8704835061435161001). There is no structured data or column layout to map. The file does not contain any recognizable PII fields such as names, emails, or phone numbers.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240913_172034479_201__prtry.csv
0 rows

File structure

Notes: This is a free-form text file with only column headers but no actual data rows. The headers indicate 'INTERNAL' repeated five times, suggesting this might be a template or placeholder file rather than structured data containing PII. Since there are no data rows and no visible PII values, we treat this as unstructured with no columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240916_172033476_216__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN number (CH8704835061435161001). There are no structured columns, headers, or additional data. IBAN is a financial account identifier, not personal PII per the exclusion rules. No PII fields to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240918_172102200_200__id.csv
0 rows

File structure

Notes: The provided text is a single line containing an IBAN number (CH8704835061435161001) and no structured columns or data rows. This is not a CSV or any other structured format with headers or multiple rows. It appears to be a standalone IBAN value, possibly part of a financial record, but there are no columns to map to PII fields.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240920_172101473_209__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet contains only header labels 'id', 'INTERNAL', 'INTERNAL', and 'INTERNAL', which are internal identifiers and do not map to any PII fields. No PII values are present in the sample. All columns are marked as skip per exclusion rules for internal IDs.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240923_172119863_210__id.csv
0 rows

File structure

Notes: The file appears to be unstructured data containing only an IBAN number (CH8704835061435161001). There is no consistent column structure or header. Since this is a single line with no repeated pattern and no identifiable PII fields beyond the IBAN (which is financial/account data and excluded by rules), we classify this as unstructured with no columns to map. IBAN is excluded as it's financial/account data, not personal PII.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240925_172131290_212__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001), no consistent delimiter structure. This is not a structured CSV but a raw data dump containing financial/accounting records from Zynex. No column mapping possible; unstructured extraction required.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240926_172035602_202__id.csv
0 rows

File structure

Notes: This appears to be a free-form text file containing only an IBAN (CH8704835061435161001) with no structured columns or consistent delimiter. The sample shows no header or repeating row structure, and the single line contains only a financial identifier rather than PII. Since there are no consistent columns or structured data, this is classified as unstructured text with no importable PII columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240927_172201388_214__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only internal identifier columns labeled 'INTERNAL' repeated across rows. No PII fields are present. The columns are purely internal IDs and should be skipped per exclusion rules.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20240930_172045391_205__id.csv
0 rows

File structure

Notes: This is a single-line file containing a Swiss IBAN number (CH8704835061435161001). There is no structured data or columnar format present. The IBAN itself is not considered PII in the context of this mapping schema because it's a bank account identifier, not an individual personally identifiable information field. No columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241001_172131973_414__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row showing column labels but no actual data. The three columns are labeled 'id' and two repetitions of 'INTERNAL', which are internal identifiers and do not contain PII. No PII fields are present in this header row.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241002_172040019_420__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with four 'INTERNAL' columns indicating internal identifiers. No PII fields are present in this row. All columns appear to be internal IDs which must be skipped according to exclusion rules.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241003_172048477_425__prtry.csv
0 rows

File structure

Notes: This is a free-form unstructured file containing only the word 'INTERNAL' repeated. There are no consistent columns, structured data, or identifiable PII patterns. The sample shows only headerless rows with the same value, indicating this is not a delimited dataset but rather a placeholder or note file. No emails, phone numbers, or other PII are visible.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241004_172134695_416__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only or metadata file with only internal identifier columns (all labeled INTERNAL). No PII fields are present in the header or sample rows. All columns are marked as skip per exclusion rules for internal IDs.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241008_172025838_417__id.csv
0 rows

File structure

Notes: This is a free-form text snippet containing only an IBAN (CH8704835061435161001) and no structured columns. The content does not match any known PII column patterns and appears to be a single line of unstructured data rather than a delimited file with headers and rows. No column mapping is possible.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241010_172100269_415__id.csv
0 rows

File structure

Notes: The provided input appears to be a single line containing an IBAN (International Bank Account Number) rather than a delimited dataset. There is no structured format with columns, headers, or multiple rows. The IBAN 'CH8704835061435161001' is a Swiss bank account identifier and not a typical PII field in the context of customer records. Since there is no structured data with columns to map, and the file does not contain free-form text with embedded emails or phones, it is classified as unstructured with no columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241011_172124842_426__prtry.csv
0 rows

File structure

Notes: The file appears to be a header-only or metadata file with repeated 'INTERNAL' labels. No structured data rows are present in the sample, and there are no embedded PII values visible. The content suggests this is a placeholder or security marker file rather than actual breach data.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241015_172045063_423__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number (CH8704835061435161001). There are no structured columns or headers. The content appears to be a standalone financial identifier rather than a breach data dump with multiple records. No PII fields can be mapped from this single line.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241016_172128447_421__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only row or a file containing only internal identifiers. No PII columns are present in the sample data provided. All visible columns are marked as 'INTERNAL' and appear to be internal IDs, which must be skipped according to the rules.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241018_172045558_419__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN (CH8704835061435161001) rather than a structured dataset. The breach context indicates financial records, but this snippet is just an IBAN value alone. No consistent column structure exists in the provided sample — it's a free-form snippet, not a CSV or tabular dataset. Since there are no repeated lines or structured fields, we classify this as unstructured text with no column mapping possible.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241022_172050148_424__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN but no consistent columnar structure; appears to be a single line or fragment, not a dataset with columns

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241023_172043545_418__id.csv
0 rows

File structure

Notes: The provided snippet is NOT a delimited file. It consists of a single line containing an IBAN (CH8704835061435161001), which is a bank account identifier and not personal PII. There is no structured format, header, or multiple rows — this appears to be a standalone value or part of a larger unstructured text file. Since there is no consistent delimiter or row structure, and no visible free-form text with embedded emails/phones, this is classified as unstructured with no columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241025_172039062_412__id.csv
0 rows

File structure

Notes: The provided text is not structured data; it appears to be a single line containing an IBAN number (CH8704835061435161001) rather than a delimited dataset. There are no columns or headers to map, and the content does not represent a breach file with PII fields. The IBAN itself is financial account information but is not a typical PII field in the context of personal identifiers like names, emails, or addresses. Since this is unstructured and lacks any row structure, it is treated as unstructured content with no columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241029_172047617_422__id.csv
0 rows

File structure

Notes: The sample provided is a single line containing only an IBAN number (CH8704835061435161001). There are no structured columns or delimiters visible in this snippet. The IBAN itself is not a PII field according to the defined categories (it is a bank account identifier). Since this is a free-form line with no consistent structure across rows (as only one line is provided), and no other emails or phones are visible, this qualifies as unstructured text with no columns to map. The IBAN would be processed separately if needed, but it does not map to any of the defined PII fields.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241031_172140765_413__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN (CH8704835061435161001). No structured data or PII fields present. The file appears to be unstructured text with no columnar structure or headers.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241101_172119707_306__prtry.csv
0 rows

File structure

Notes: The file appears to be a raw dump or listing of internal identifiers with no structured columns. The first line 'id' followed by three 'INTERNAL' entries suggests this is likely a headerless file containing only internal reference IDs with no personal data visible in the first 50 rows. No consistent delimiter structure or PII values are present in the sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241104_172039711_307__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001). There is no structured data with columns — it's a standalone financial identifier. Since there is no row structure or repeated pattern, this is free-form text. No PII fields can be mapped because there are no column headers or repeating records.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241105_172050545_309__id.csv
0 rows

File structure

Notes: The provided data appears to be a single line containing an IBAN number (CH8704835061435161001) rather than a structured dataset with columns. This is not a delimited file with multiple rows and columns, but rather a snippet of financial data. Since there is no consistent structure or multiple rows to analyze, and the content is not prose with embedded PII, it cannot be mapped to structured columns. The IBAN itself is financial data and not classified as PII per the provided rules.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241108_172036949_311__id.csv
0 rows

File structure

Notes: The provided data is unstructured text containing only an IBAN number (CH8704835061435161001). There are no consistent columns or structured data present, and the content appears to be a single line without any identifiable PII fields or row structure. Since the file is unstructured and contains no column-based data, it is classified as unstructured with no columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241111_172057143_310__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No structured columns present; appears to be a single line or note rather than a delimited dataset. No consistent delimiter or repeating structure across lines.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241115_172036982_305__prtry.csv
0 rows

File structure

Notes: The provided content is purely unstructured internal identifiers with no PII fields visible. The header consists solely of 'INTERNAL' repeated five times, and there are no rows of data shown. This appears to be an internal reference or placeholder file, not containing any customer or personal data. No structured records or PII are present in the sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241118_172049747_303__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The first 50 rows provided show only header lines with column names 'id', 'INTERNAL', 'INTERNAL', 'INTERNAL' repeated. These appear to be placeholder headers for an unstructured file or a file where the actual data starts later. No PII values are present in the visible rows. Based on the breach context (Zynex internal corporate data), this is likely a metadata or index file rather than a structured PII dataset. No columns map to PII fields in this sample.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241120_172152227_302__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header-like lines that are not actual column names but internal labels. There are no actual data rows visible in the first 50 rows, and no PII fields can be identified. The file appears to be an internal metadata or structure file rather than containing personal data records.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241128_172217628_308__id.csv
0 rows

File structure

Notes: This is unstructured free-form text containing only an IBAN (CH8704835061435161001). There is no consistent delimiter, no header, and the content does not match a structured format. IBAN is financial data and not a PII field per the rules, so no columns to map.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241129_172055722_304__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN (CH8704835061435161001) with no delimiter structure or header. Since it's a single unstructured line and not a CSV with consistent columns, it falls under the unstructured category. The IBAN is a financial account identifier and not considered PII under the defined field types, so no PII fields are mapped.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241202_172100814_200__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN (CH8704835061435161001). The file appears to be unstructured text with no consistent delimiter or row structure. As per the rules, unstructured files with embedded PII are handled by a streaming extractor. The IBAN itself is not mapped as a PII field in the provided schema.

finanzen__zed_files__2024__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241205_172049364_201__prtry.csv
0 rows

File structure

Notes: The file appears to be unstructured internal metadata with no consistent delimiter or row structure. The visible lines are all labeled 'INTERNAL' with no actual PII data present in the sample. No column mapping can be performed as there is no structured data to analyze.

finanzen__zed_files__2025__2025-11-17_ZQR_CH360020620693823701D_CHF_WC9CEKBQSHGV2BDA__id.csv
0 rows

File structure

Notes: The sample provided appears to be unstructured financial/banking data fragments rather than tabular PII records. The lines contain IBAN values and bank codes but lack consistent column structure or identifiable personal names, email addresses, or phone numbers across rows. No CSV-like delimiter pattern is present.

finanzen__zed_files__2025__2025-11-18_ZQR_CH360020620693823701D_CHF_WC9CEKBQTEZ52KGA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or structure; appears to be a raw dump of codes/labels rather than tabular data

finanzen__zed_files__2025__2025-11-19_ZQR_CH360020620693823701D_CHF_WC9CEKBQUDQL8LBA__id.csv
0 rows

File structure

Notes: free-form text with embedded financial/accounting data (IBANs, bank codes), no structured columns visible in sample

finanzen__zed_files__2025__2025-11-20_ZQR_CH360020620693823701D_CHF_WC9CEKBQVCMXKXHA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a simple text file listing a single value 'A89' repeated three times with no column headers or structured data. No PII can be extracted from this unstructured content.

finanzen__zed_files__2025__2025-11-21_ZQR_CH360020620693823701D_CHF_WC9CEKBQWDGZT5RA__id.csv
0 rows

File structure

Notes: free-form text with embedded financial identifiers (IBAN) and no consistent delimiter structure

finanzen__zed_files__2025__2025-11-24_ZQR_CH360020620693823701D_CHF_WC9CEKBQYERNZ5KA__id.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File contains only banking identifiers (SWIFT/BIC and IBAN codes). These are financial account identifiers, not personal information. No PII columns present. Data appears to be internal banking/payment routing information for Zynex corporate accounts.

finanzen__zed_files__2025__2025-11-25_ZQR_CH360020620693823701D_CHF_WC9CEKBQZ29Y5BSA__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be raw banking/IBAN data fragments rather than tabular PII records. No column headers or repeated field patterns are present across the sample rows. The content shows IBAN format (e.g., UBSWCHZHREB) and partial account identifiers, but lacks any structured layout for column mapping.

finanzen__zed_files__2025__2025-11-27_ZQR_CH360020620693823701D_CHF_WC9CEKBQ4RDA6MMA__id.csv
0 rows

File structure

Notes: This is unstructured financial data showing bank account numbers and IBANs. The format is free-form text with no consistent columnar structure across lines, and contains no personal PII fields (names, emails, etc.).

finanzen__zed_files__2025__2025-11-28_ZQR_CH360020620693823701D_CHF_WC9CEKBQ6VTKJHLA__prtry.csv
0 rows

File structure

Notes: The provided data appears to be free-form text with no consistent delimiter or structure. Each line contains only the string 'A89' repeated, which does not exhibit any columnar pattern or identifiable PII in structured format. Given the lack of any discernible structure or variation in line content, this is classified as unstructured text. No column mapping is possible as there are no structured fields to map.

finanzen__zed_files__2025__2025-12-03_ZQR_CH360020620693823701D_CHF_WC9CEKBRB7GMMPUA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or structure; appears to be a series of codes/IDs with no PII visible in the first 50 rows. Since there is no structured format, we classify as unstructured for downstream processing.

finanzen__zed_files__2025__2025-12-04_ZQR_CH360020620693823701D_CHF_WC9CEKBRC9URR37A__prtry.csv
0 rows

File structure

Notes: The provided data is free-form text with no consistent delimiter or structured columns. The lines appear to be a series of codes ('A89') repeated, likely representing some internal identifier or placeholder. There is no evidence of PII such as emails, phone numbers, or other personal data in this snippet. Since the data lacks a consistent structure and does not contain any identifiable PII in the visible rows, it is classified as unstructured text.

finanzen__zed_files__2025__2025-12-05_ZQR_CH360020620693823701D_CHF_WC9CEKBREFQVUTLA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure — appears to be raw data dump or log snippets (repeated 'A89' lines). No CSV headers or column patterns visible. This qualifies as unstructured content per rules.

finanzen__zed_files__2025__2025-12-08_ZQR_CH360020620693823701D_CHF_WC9CEKBRGKSVHESA__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a mix of financial/banking identifiers (IBAN, BIC) rather than structured PII records

finanzen__zed_files__2025__2025-12-10_ZQR_CH360020620693823701D_CHF_WC9CEKBRJQL44Z3A__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN and BIC; no consistent delimiter or row structure. Contains financial banking codes (IBAN, BIC) rather than personal PII fields. No emails, phone numbers, or names visible in this snippet.

finanzen__zed_files__2025__2025-12-11_ZQR_CH360020620693823701D_CHF_WC9CEKBRKTPEB63A__id.csv
0 rows

File structure

Notes: free-form text with embedded financial/banking identifiers (IBAN) but no consistent column structure

finanzen__zed_files__2025__2025-12-12_ZQR_CH360020620693823701D_CHF_WC9CEKBRLYAQBW6A__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a simple file containing repeated string 'A89' across all lines, no PII visible, no structured columns present

finanzen__zed_files__2025__2025-12-15_ZQR_CH360020620693823701D_CHF_WC9CEKBRPB86HXAA__prtry.csv
0 rows

File structure

Notes: The file appears to be unstructured data with no consistent delimiter or column structure. The sample lines show fragments like 'cd' and 'id' but lack any repeating pattern, making it impossible to map columns. This is typical of a README, note, or description file rather than structured records containing PII. No PII columns can be mapped.

finanzen__zed_files__2025__2025-12-16_ZQR_CH360020620693823701D_CHF_WC9CEKBRQDVKT5PA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or structure; appears to be a repeated value 'A89' across lines, no identifiable PII in structured format

finanzen__zed_files__2025__2025-12-17_ZQR_CH360020620693823701D_CHF_WC9CEKBRRHCE2HHA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a series of values without column headers or structured format. This matches the unstructured opt-out criteria.

finanzen__zed_files__2025__2025-12-18_ZQR_CH360020620693823701D_CHF_WC9CEKBRSPXL6M4A__prtry.csv
0 rows

File structure

Notes: The sample data consists solely of the string 'A89' repeated across all rows with no delimiter or structure. This is not a structured table with columns; it appears to be a placeholder or artifact file. No PII can be extracted from this content.

finanzen__zed_files__2025__2025-12-19_ZQR_CH360020620693823701D_CHF_WC9CEKBRT4C2MZVA__prtry.csv
0 rows

File structure

Notes: The sample consists entirely of a single repeated string 'A89' with no delimiters, structure, or variation across lines. This is not a delimited file — it's free-form text with no embedded emails or phone numbers visible. Since there is no consistent column structure and the data is purely repetitive without any PII-like patterns, it qualifies as unstructured text with no actionable PII columns to map. The breach context (Zynex financial records) does not override this because the actual file content here is not structured.

finanzen__zed_files__2025__2025-12-22_ZQR_CH360020620693823701D_CHF_WC9CEKBRWPB527RA__prtry.csv
0 rows

File structure

Notes: The file contains only a single repeated value 'A89' across all rows with no delimiter structure. This is not a CSV or any structured format; it appears to be a placeholder, log, or artifact file rather than data records. No PII is present.

finanzen__zed_files__2025__2025-12-23_ZQR_CH360020620693823701D_CHF_WC9CEKBRXXAJ8QMA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure; appears to be repeated placeholder values 'A89' across lines with no identifiable PII patterns or structured data. No CSV headers, varying line lengths, and lacks any embedded emails/phones in visible sample.

finanzen__zed_files__2025__2025-12-24_ZQR_CH360020620693823701D_CHF_WC9CEKBRY8LDTU5A__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or column structure. Lines contain only the string 'A89' repeated, which appears to be a placeholder or test pattern rather than meaningful data. No PII can be extracted from this format.

finanzen__zed_files__2025__2025-12-29_ZQR_CH360020620693823701D_CHF_WC9CEKBR4JEZD98A__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be repeated internal identifier 'A89' across lines, no PII visible in sample. This is not a structured CSV/TSV file with columnar data.

finanzen__zed_files__2025__2025-12-30_ZQR_CH360020620693823701D_CHF_WC9CEKBR5QUUSDSA__prtry.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent columnar structure. The sample shows only the string 'A89' repeated multiple times, which does not indicate any structured data format or PII. Since there is no delimiter, no header, and no variation in content, this is treated as unstructured text. No PII columns can be mapped.

finanzen__zed_files__2025__2025-12-31_ZQR_CH360020620693823701D_CHF_WC9CEKBR8LXYUD5A__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure — appears to be a simple file containing repeated values 'A89' across lines. No headers, no columns, no PII visible in this snippet. Classified as unstructured for streaming processing.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241206_172203489_206__id.csv
0 rows

File structure

Notes: This appears to be a single line containing a Swiss IBAN number (CH8704835061435161001) rather than a structured dataset. The breach context indicates this is from Zynex's internal financial records, but this specific file seems to be a standalone IBAN value, not a CSV or other structured format. As there is no consistent row structure and only one line, this qualifies as unstructured data with no column mapping possible.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241206_172203489_312__id.csv
0 rows

File structure

Notes: The provided sample is not a delimited file but a single line containing an IBAN (CH8704835061435161001). This is not a structured dataset with columns but rather a snippet of financial data. There are no repeating patterns or structured rows/columns in this sample. Since there is no consistent delimiter or row structure, and this appears to be a single value (IBAN), this file should be treated as unstructured content. However, IBANs themselves are not considered PII in the provided field types, so no PII fields need mapping.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241209_172146962_212__prtry.csv
0 rows

File structure

Notes: This is unstructured data - appears to be a list of internal identifiers with no consistent delimiter or structure. All lines contain the word 'INTERNAL' repeated, showing no actual PII values or structured fields. No email addresses or phone numbers are visible in the sample. This is not a CSV or any delimited format; it's just placeholder/internal reference text.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241209_172146962_318__prtry.csv
0 rows

File structure

Notes: The provided data is unstructured free-form text with no consistent delimiter or column structure. It appears to be a note about internal identifiers rather than actual data records. There are no visible emails or phone numbers in the sample, and the content does not represent structured PII records.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241210_172044087_207__id.csv
0 rows

File structure

Notes: The provided snippet appears to be free-form text containing only an IBAN number (CH8704835061435161001) without any structured columns or delimiters. The IBAN is a financial identifier and not considered PII under the defined field types. Since there are no consistent columns or structured data present, and the snippet does not show any emails or phone numbers, it is classified as unstructured text with no importable PII columns.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241210_172044087_313__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent column structure or header present; appears to be a single data snippet rather than a delimited file. IBAN is financial account data, but due to unstructured format, it will be processed by unstructured extraction pipeline.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241211_172046144_211__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row showing four INTERNAL columns with no actual data values. All columns are marked as INTERNAL and contain no PII. No PII fields can be mapped from this header alone.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241211_172046144_317__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only file or placeholder with no actual data rows. The headers are all marked as 'INTERNAL', indicating these are likely internal identifier columns that do not contain PII. No PII fields are present in the visible structure.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241212_172108009_205__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header row with only internal identifier columns (all labeled 'INTERNAL'). No PII fields are present in the first 50 rows. These appear to be internal reference IDs used within Zynex's systems, which should be skipped per exclusion rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241212_172108009_311__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to contain only internal identifier columns labeled 'INTERNAL' repeated across the first 8 columns. No PII fields are present in the sample data. All columns are internal IDs and should be skipped per exclusion rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241213_172109502_208__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only file or the first row is a placeholder with no actual data. All columns are labeled 'INTERNAL' and contain no PII values. No valid PII columns can be mapped from this sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241213_172109502_314__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample contains only header-like lines that are internal identifiers (labeled as INTERNAL). No actual data rows with PII are present in the first 50 rows. All columns appear to be internal IDs which must be skipped per exclusion rules. No PII fields are detected in this segment.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241216_172138005_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample consists solely of the header row listing 'INTERNAL' columns repeatedly. No actual data rows are visible to map to PII fields. Since all columns are labeled 'INTERNAL' and no PII values appear, no columns can be mapped to PII categories. This appears to be an internal ID or reference structure only.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241216_172138005_308__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only file or contains only internal identifier columns with no actual PII data in the first 50 rows. All columns are labeled as 'INTERNAL', which according to exclusion rules must be skipped. No PII fields are present in the visible data.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241219_172033891_201__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is purely internal identifiers with no PII content. All columns are marked as INTERNAL and contain no personal information. No columns map to any PII fields.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241219_172033891_307__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header row with only placeholder column names ('INTERNAL') repeated multiple times and no actual PII data visible in the first 50 rows. There are no identifiable PII fields present in the sample. All columns appear to be internal identifiers which should be skipped per rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241220_172148747_213__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be an internal header-only row or metadata file with no actual data rows. All columns are labeled as INTERNAL and contain no PII values. The first column 'id' is an internal identifier and should be skipped. No PII fields are present in the provided rows.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241220_172148747_319__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only the header row with internal identifier columns (all labeled 'INTERNAL'). No PII fields are present in the visible data. The file appears to be an internal reference or index file without personal customer data. All columns are marked as 'skip' per exclusion rules for internal IDs.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241223_172033117_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to contain only internal identifiers (labeled 'INTERNAL') repeated across rows with no actual PII data. All columns are non-PII internal IDs and should be skipped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241223_172033117_310__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is a header-only sample showing only internal identifier columns labeled 'INTERNAL'. No PII fields are present in this snippet. All columns are marked as internal IDs and must be skipped per exclusion rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241224_172150296_209__id.csv
0 rows

File structure

Notes: This is a free-form text file containing a single IBAN value (CH8704835061435161001) and no structured columns. The content is unstructured and lacks any consistent delimiter or row structure. While IBAN is financial data, it is not considered PII in this context as it appears alone without associated personal identifiers.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241224_172150296_315__id.csv
0 rows

File structure

Notes: This is not a structured file; it contains only an IBAN number (CH8704835061435161001) with no column structure or headers. The sample provided is a single line of unstructured data, which does not meet the criteria for a CSV or any other structured format. According to the rules, unstructured files with no consistent delimiter or row structure should return an empty columns object.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241227_172103157_200__id.csv
0 rows

File structure

Notes: This file is unstructured text containing only an IBAN (CH8704835061435161001) with no structured columns or consistent row patterns. The sample shows a single line with no delimiters or headers, indicating free-form data rather than a delimited CSV or similar format. Since there is no consistent structure and no embedded emails or phones beyond the IBAN (which is financial identifier and not PII), it is classified as unstructured with no column mapping required.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241227_172103157_306__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN (CH8704835061435161001). There are no structured columns or repeated patterns across lines. IBAN is not a PII field in the defined schema (it's a banking identifier, not personal identity data). No emails, phone numbers, or other PII are visible in the sample. Since there is no consistent delimiter or row structure, and this appears to be a single line of unstructured data, we return empty columns with unstructured type.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241230_172211419_203__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN (CH8704835061435161001). There is no structured data, no headers, and no identifiable columns. The line does not represent a CSV row or any tabular format; it is a standalone value. Therefore, this file should be treated as unstructured text with no column mappings.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241230_172211419_309__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing a Swiss IBAN number (CH8704835061435161001) but no structured tabular data. There are no repeated patterns, headers, or delimited rows. Since it lacks any consistent row structure and appears to be a standalone financial identifier, it is classified as unstructured. The IBAN itself is not mapped to any PII field as it is not among the defined categories.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241231_172052154_210__id.csv
0 rows

File structure

Notes: This is a free-form text file containing a single IBAN value (CH8704835061435161001) and no structured columns. It does not meet the criteria for a structured CSV/TSV format and lacks consistent delimiters or row patterns. Therefore, it is classified as unstructured text with no column mapping possible.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20241231_172052154_316__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured data or header present. The file appears to be a simple text snippet rather than a delimited dataset with multiple rows of PII. Since there is no consistent structure or multiple rows, and the content is a single financial identifier, this is classified as unstructured with no columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250103_172151834_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file contains only internal identifier columns (all labeled INTERNAL) with no actual PII values. No columns map to any PII fields as per the rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250106_172106563_201__id.csv
0 rows

File structure

Notes: The provided text is a single line containing only an IBAN number (CH8704835061435161001). There are no structured columns, headers, or multiple rows. This is not a CSV or any delimited format. The IBAN is a financial identifier and not considered PII under the defined fields. Since this is unstructured and contains no emails or phone numbers, it returns an empty columns object.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250107_172052475_200__id.csv
0 rows

File structure

Notes: The provided data snippet contains only a single IBAN (CH8704835061435161001) and no structured columns or rows. The IBAN is not classified as PII in the provided field types, and the snippet lacks any row structure, headers, or multiple fields. This appears to be a free-form text fragment rather than a delimited dataset.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250108_172031423_204__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number. There are no structured columns or delimited data in the sample. The IBAN is a financial identifier and not classified as PII under the provided rules (only email, phone, dob, names, address, ssn, password, username, etc., are mapped). Since there is no structured tabular data and the file appears to be a single value, we classify it as unstructured with no PII columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250109_172044850_205__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with no data. The file appears to contain only internal identifier columns (all labeled 'INTERNAL') with no actual PII values in the first 50 rows. No PII fields can be mapped from this header alone.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250110_172047610_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is only a header row with placeholder column names 'INTERNAL' repeated four times. No actual data rows or PII values are visible in the first 50 rows. Therefore, no columns can be mapped to PII fields. This appears to be a metadata or placeholder file rather than actual breach data containing personal information.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250113_172041001_314__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured delimiter, no header, and no consistent row structure. The file appears to be a standalone snippet or fragment, not a full dataset. Since there are no repeated patterns or structured columns, this is classified as unstructured text. No PII columns can be mapped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250114_172035388_306__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing only an IBAN (CH8704835061435161001). There is no structured data, no delimiter, no headers, and no repeated patterns across rows. The IBAN is a financial identifier and not considered PII under the provided field types. Therefore, no columns are mapped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250115_172110381_315__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header row with column names 'id' and three repetitions of 'INTERNAL'. No PII fields are present in this snippet. The data appears to be internal identifiers only, which according to rules must be skipped. No email, phone, name, address, DOB, SSN, password, username, or other PII fields are visible in this sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250116_172041834_310__id.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; appears to be a single IBAN value 'CH8704835061435161001' rather than a delimited dataset. No repeated rows or field patterns are present in the sample. This is not a CSV or structured table; it is a standalone financial identifier. Since there is no column structure, we classify this as unstructured and do not map any columns.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250117_172108420_309__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is purely internal identifiers with no PII content. All columns are labeled 'INTERNAL' and contain no personal or identifiable information. No mapping to PII fields is possible.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250120_172137362_305__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The first 50 rows appear to be a header-only file or metadata listing column names without actual data rows. The first row 'id' and subsequent rows labeled 'INTERNAL' suggest this is a structural placeholder file, not actual records containing PII. No PII values are present in the sample to map to fields.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250121_172151776_313__prtry.csv
0 rows

File structure

Notes: This is a free-form unstructured file with no consistent delimiter or header. It appears to be a list of internal identifiers with no PII present. The sample shows only the word "INTERNAL" repeated, which is not structured data and does not contain any personal or identifiable information. No column mapping is possible.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250122_172035862_319__id.csv
0 rows

File structure

Notes: This file is a single unstructured line containing only a Swiss IBAN number (CH8704835061435161001). There is no consistent delimiter or row structure, and no header. IBAN is not considered PII under the defined fields, so no mapping is required. The file appears to be a standalone financial identifier, not part of a structured dataset.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250123_172043529_311__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN number (CH8704835061435161001) with no structured columns or consistent delimiter. No headers or repeating patterns exist across lines. The file does not contain any identifiable structured data columns, only a single line with a financial identifier.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250124_172232963_318__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) — this is not email/phone but a bank account number; unstructured file with no consistent columns or delimiter structure

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250127_172038190_308__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with four 'INTERNAL' columns indicating no actual data is present in the sample. No PII fields can be mapped from this header alone.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250128_172115790_317__prtry.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent columnar structure. The file appears to be a list of internal identifiers or metadata headers, not actual data records. There are no embedded emails, phone numbers, or other PII visible in the sample. No structured PII columns can be mapped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250129_172143124_316__id.csv
0 rows

File structure

Notes: The sample provided is a single line containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or multiple lines to establish a structured format. This appears to be unstructured data, likely part of a financial record or note, but lacks any identifiable PII fields such as names, emails, or addresses within the visible snippet. Since the file appears to be free-form text with no structured columns, it is classified as unstructured.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250130_172218064_312__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). No structured columns or headers are present in the provided sample. The file appears to be unstructured data, possibly a log or snippet, and does not contain any identifiable columns or PII fields beyond the IBAN itself, which is not classified as PII under the given field types. Therefore, no columns are mapped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250131_172039993_307__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File appears to be a header-only row with placeholder column names 'id' and 'INTERNAL' repeated three times. No actual data rows provided to analyze for PII content. Given the context of a corporate financial data breach (Zynex), these columns likely represent internal reference IDs and are non-PII. No PII fields can be mapped from this header alone.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250204_172045955_201__id.csv
0 rows

File structure

Notes: This is unstructured free-form text containing only an IBAN (CH8704835061435161001) and no structured data. There are no consistent columns or row structure visible in the sample, and it does not contain any emails or phone numbers in a free-text format. This is not a CSV or any structured format that can be mapped to PII fields.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250206_172054172_203__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only an IBAN number (CH8704835061435161001). There are no consistent columns or structured data in the first 50 rows. The content appears to be a raw IBAN value, which is financial account information but not a typical PII field in the expected dataset structure. Since there is no structured format or repeated pattern, this is classified as unstructured text.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250207_172050310_200__id.csv
0 rows

File structure

Notes: This file contains only a single IBAN value (CH8704835061435161001) and no structured tabular data. It is not a CSV or any delimited format. Since there is no consistent column structure and only one line of data, it is classified as unstructured. No PII fields can be mapped because there are no columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250210_172055412_204__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) and no consistent row structure — unstructured opt-out required

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250211_172057714_202__id.csv
0 rows

File structure

Notes: This file is a single line containing a single IBAN value (CH8704835061435161001). There are no column headers, no consistent row structure, and this is not a CSV or tabular dataset. It is free-form text with an embedded financial identifier (not PII). Since there are no consistent columns and only one line, this is classified as unstructured with no PII columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250213_172056280_323__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The first 3 rows appear to be header/comment lines or internal labels. No actual data rows with PII are visible in the first 50 rows provided. The columns labeled 'INTERNAL' repeated three times suggest this is a placeholder or metadata header row, not actual data columns containing PII. No PII fields can be mapped from this snippet.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250214_172035582_319__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent delimiter or row structure. Appears to be a single line containing an IBAN value only, not a CSV with columns. No structured data present.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250217_172051465_326__id.csv
0 rows

File structure

Notes: This appears to be a single line containing only an IBAN (CH8704835061435161001) with no surrounding context or structure. The breach context mentions financial records but this sample shows no structured columns or repeated patterns. There is no consistent delimiter or repeated lines to map as CSV/TSV. Since this is a single unstructured line with only a financial identifier (not PII), it falls under unstructured opt-out rules. No PII columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250218_172104756_325__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number. The file appears to be unstructured and contains no structured columns or headers. IBAN is not a PII field per the provided definitions, so no columns are mapped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250219_172042598_321__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet shows only header labels 'id', 'INTERNAL', 'INTERNAL', 'INTERNAL' which are internal identifiers and do not contain any PII. No PII fields are present in this sample. All columns are marked as skip per exclusion rules for internal IDs.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250220_172047889_329__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only row or placeholder file. The first row contains only the string 'id' followed by three 'INTERNAL' markers, with no actual data rows provided. Without sample values or additional rows showing structured data, no PII fields can be identified. The file seems to indicate internal identifiers only, which would map to skip columns under exclusion rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250221_172047748_330__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only row or metadata row without actual data rows. The columns are labeled 'INTERNAL' repeatedly, indicating no actual PII data is present in the provided sample. No PII fields can be mapped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250224_172118438_327__prtry.csv
0 rows

File structure

Notes: The provided sample is not structured data; it consists of unstructured internal identifiers ('INTERNAL') repeated across rows with no consistent column structure or PII content. No columns can be mapped to PII fields.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250225_172039668_328__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There are no structured columns or headers present. The file appears to be a simple text snippet rather than a data table. Since it lacks any row structure or delimiter patterns and contains only one line, it qualifies as unstructured data.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250226_172216632_322__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header row with only placeholder column names 'id' and repeated 'INTERNAL' labels. No PII values are present in the sample. The file likely contains internal identifiers only in subsequent rows. No columns map to PII fields based on header names and sample values.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250227_172044839_320__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with three internal identifier columns labeled 'INTERNAL'. No PII fields are present in the provided data. All columns are internal IDs and should be skipped per exclusion rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250228_172053245_324__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001). There is no consistent delimiter or header structure across rows, and this appears to be a standalone financial identifier rather than a structured dataset. Since there are no repeated patterns or structured fields, this qualifies as unstructured text. The IBAN is not mapped as a PII field in the provided schema.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250303_172109654_201__id.csv
0 rows

File structure

Notes: This is a free-form text file (not structured data). The sample contains only an IBAN number (CH8704835061435161001) and no consistent column structure or repeated lines. Per rules, unstructured files with no shared delimiter or row structure default to empty columns object. The IBAN is not mapped as it is not one of the defined PII fields (bank account numbers fall under financial/transactional data, which are excluded).

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250304_172157819_209__id.csv
0 rows

File structure

Notes: This is not structured data; the provided sample shows only a single IBAN value 'CH8704835061435161001' with no consistent columnar structure or header. The breach context describes financial records, but this snippet lacks any identifiable columns or patterns to map to PII fields. It appears to be a fragment or single-line output rather than a dataset with rows and columns.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250305_172127120_213__id.csv
0 rows

File structure

Notes: The provided sample is NOT structured data. It appears to be a single line containing an IBAN number (CH8704835061435161001) rather than a delimited file with columns. This is likely a snippet from a financial record or a breach context note, not a CSV/TSV file. Since there is no consistent delimiter, no header, and the line does not represent a structured table, we classify this as unstructured text. No columns can be mapped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250307_172107663_216__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is purely headerless internal identifiers with no PII. The first row appears to be a header row with placeholder labels 'id' and 'INTERNAL' repeated three times, but no actual data rows were provided to analyze for PII patterns. No email, phone, name, address, or other PII fields are detectable from this snippet.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250310_172132625_206__id.csv
0 rows

File structure

Notes: This appears to be a single line containing only an IBAN number (CH8704835061435161001) with no structured format, headers, or additional rows. The file is unstructured and contains no identifiable columns or PII patterns beyond this isolated financial identifier, which is not classified as PII under the specified rules. No mapping can be performed.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250311_172050502_218__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only header row with repeated 'INTERNAL' labels and no actual data values. All columns appear to be internal identifiers (likely numeric/auto-generated) which per rules must be skipped. No PII fields are present in this sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250312_172104201_204__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent column structure or header; appears to be a single data snippet rather than structured records

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250313_172028217_214__id.csv
0 rows

File structure

Notes: The provided data snippet appears to be free-form text containing only an IBAN (CH8704835061435161001). There is no consistent delimiter, structured columns, or repeated patterns across rows. The IBAN is a financial identifier, not PII under the defined categories. Since this is unstructured data with no row structure and only one visible value, it is classified as unstructured text with no importable columns.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250314_172123253_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only file or contains only internal identifier columns labeled 'INTERNAL' repeated multiple times. No PII fields are present in the visible rows. The data consists solely of non-PII internal IDs according to the exclusion rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250317_172104603_210__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample shows only the header row with placeholder 'INTERNAL' labels and no actual data values. All columns are marked as INTERNAL and contain no discernible PII. No email addresses, phone numbers, names, or other PII patterns are visible in the sample. Given the context of a corporate financial breach, these columns likely contain internal identifiers or metadata that do not map to PII fields. No columns can be mapped to PII fields based on the available data.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250318_172100083_212__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) without any structured columns or consistent delimiter. The file appears to be unstructured text with no header or row structure, only a financial identifier. Since there's no consistent delimiter, variable row shapes, and contains financial data (IBAN) which isn't directly mapped to PII fields in our schema, it should be treated as unstructured for further processing.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250320_172115159_217__prtry.csv
0 rows

File structure

Notes: The provided sample is purely header-free unstructured text: only three lines with the word "INTERNAL" repeated. No structured data, no column alignment, and no PII visible. This qualifies as unstructured free-form text with no consistent delimiter or row structure.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250321_172116575_205__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header row from a CSV file, but the first row consists entirely of "INTERNAL" markers and a single numeric column label "2". No PII columns are present in this row. Likely this is a metadata or placeholder header, and actual PII columns would appear in subsequent rows. Since no PII fields can be identified from this header alone, no columns are mapped. Further rows are required for accurate mapping.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250324_172051975_211__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). No structured columns or headers are present; the file appears to be free-form text with a single financial identifier. Per rules, unstructured files with no consistent delimiter structure and visible PII (even if just one line) should return empty columns object with unstructured type.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250325_172052337_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be a header-only snippet with placeholder column names ('INTERNAL') repeated three times. No actual data rows are present to analyze for PII mapping. Without visible values or structured content, no PII columns can be identified. This is likely just a schema placeholder or metadata header before actual data rows begin.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250326_172118514_207__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only header row is visible in sample. No PII fields identified. Header shows three internal identifier columns, all to be skipped per exclusion rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250327_172107661_200__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only file or a corrupted CSV with only column labels and no actual data rows. The headers 'id', 'INTERNAL', 'INTERNAL', 'INTERNAL' are present but no data rows follow, meaning there are no PII values to map. Per instructions, no columns are mapped because there is no actual content to analyze for PII patterns.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250328_172236455_208__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent column structure detected across the first 50 rows; appears to be unstructured notes or documents from the Zynex breach containing financial records and invoice data. IBAN is a financial identifier, not PII per the exclusion rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250331_172113824_215__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (Swiss bank account number). No consistent column structure present.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250401_172051334_434__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is only a header row with placeholder column names "id" and three "INTERNAL" columns. No PII values are present in the sample, and the headers do not indicate any personal or sensitive data. Based on the breach context (Zynex internal corporate data), these columns likely represent internal identifiers or metadata and should be treated as non-PII. No columns map to PII fields.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250402_172248445_433__id.csv
0 rows

File structure

Notes: The provided sample is not structured data; it appears to be a snippet of unstructured text containing a single IBAN (CH8704835061435161001). There is no consistent delimiter, no header row, and the content does not exhibit any tabular structure. Since the sample does not conform to a structured format like CSV, TSV, etc., and appears to be free-form text, it is classified as unstructured. No column mapping can be performed.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250403_172125582_432__id.csv
0 rows

File structure

Notes: This is not a structured file. The provided data appears to be a single IBAN number (CH8704835061435161001) rather than a delimited dataset. There are no headers, no consistent structure, and no repeated rows to analyze. The IBAN is financial/account information but not personal PII. Since the file contains no columnar data or repeated records, it cannot be mapped to PII fields. Return empty columns object as per unstructured rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250404_172124155_431__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is not structured with identifiable PII fields. The first row appears to be a header with repeated 'INTERNAL' labels and an 'id' column, but no actual PII data is present in the visible rows. Without further rows containing PII values, no columns can be mapped to PII fields. This appears to be an internal identifier file rather than a breach containing personal data.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250407_172157938_435__id.csv
0 rows

File structure

Notes: This is unstructured data (a single line containing an IBAN number). The file appears to be a raw IBAN value with no structured columns or header. IBAN itself is not classified as PII per the defined fields, and since there is no structured format or repeated lines, it is treated as unstructured text. No column mapping is performed.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250408_172105149_436__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN (CH8704835061435161001) and no structured data. There are no consistent columns, headers, or repeating patterns. The file appears to be a raw snippet rather than a delimited dataset with PII fields. Since there is no structured format and no repeated lines with consistent delimiters, this qualifies as unstructured content. No column mapping is possible.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250411_172122655_413__prtry.csv
0 rows

File structure

Notes: The provided text is a header-only snippet with no actual data rows visible. The first line lists 'id' and three 'INTERNAL' fields, indicating this is likely a structured file header, but no actual data rows are present in the sample to analyze. Since there are no rows with content to assess, we cannot determine a consistent delimiter or column mapping. The file appears to be structured but requires additional rows for proper analysis.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250414_172128512_417__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing only an IBAN (CH8704835061435161001). There are no structured columns or headers. IBAN is a financial identifier, not PII. Since the file is not a structured table with columns, return empty columns and unstructured format.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250415_172049900_418__id.csv
0 rows

File structure

Notes: This is a single-line file containing only an IBAN (CH8704835061435161001) and no structured data. The content does not represent a breach record format; it is a standalone IBAN value. There are no headers or repeated patterns, and the context describes a corporate financial breach archive (Zynex, Swiss web hosting), but this file itself is not structured and contains no PII fields. No column mapping is possible.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250416_172058265_419__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter, no header, and no other PII visible. The file appears to be a fragment or a single-value record, not a structured dataset. Since it's unstructured with no columns to map, return empty columns object.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250417_172042353_414__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is a header-only snippet showing three 'INTERNAL' columns with no actual data rows. No PII fields can be identified from this sample as there are no values to analyze and the column names indicate internal identifiers that should be skipped per rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250422_172132184_423__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row showing three INTERNAL columns with no data values visible. No PII fields can be mapped from this header alone.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250423_172106596_422__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only file or contains only internal identifiers. No PII fields are present in the first 50 rows. The columns labeled 'INTERNAL' are internal IDs and should be skipped according to the rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250424_172132211_421__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) — no structured columns detected, appears to be a single line of financial data

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250425_172303023_420__id.csv
0 rows

File structure

Notes: The provided text is a single line containing only an IBAN number (CH8704835061435161001) and no structured data. There is no header or delimiter pattern, and the content is not a free-form text with embedded PII. This appears to be a fragment of financial data rather than a breach file with PII. Since there are no consistent columns or structured records, the format is marked as unstructured, but no PII columns can be mapped from this single line.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250429_172101598_415__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet only contains header labels 'id', 'INTERNAL', 'INTERNAL', 'INTERNAL' which are internal identifiers and do not map to any PII fields. No PII columns are present in this sample. The breach context indicates this is part of a larger dataset, but this specific row structure contains only non-PII columns.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250430_172312994_416__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN but no consistent column structure

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250502_172230020_308__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). No structured columns or PII fields are present. The data appears to be a fragment of financial/banking information, not a dataset with identifiable personal information in structured format. The IBAN alone does not constitute PII in this context without additional personal data linkage.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250505_172055481_306__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet only contains header row indicating 'id' and 'INTERNAL' repeated four times. No PII data is present in the visible rows. This appears to be an internal identifier column with no personal information. All columns appear to be internal identifiers and thus should be skipped per exclusion rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250506_172108961_307__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN but no consistent column structure; appears to be a single line containing a Swiss IBAN (CH8704835061435161001) rather than a CSV or structured dataset. No headers or repeated patterns are visible in the sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250508_172048150_311__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001), not a structured dataset with columns. The breach context mentions financial records but this snippet is not CSV or tabular. It appears to be a standalone IBAN value, likely from a financial record. Since there is no consistent row structure, delimiter, or header, this qualifies as unstructured text. However, IBANs themselves are NOT considered PII per the exclusion rules (they are financial identifiers, not personal identifiers like name/email/phone). No PII fields to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250509_172107971_312__id.csv
0 rows

File structure

Notes: This file appears to be unstructured free-form text rather than a delimited tabular dataset. The sample shows a single line containing a Swiss IBAN number (CH8704835061435161001) with no consistent column structure across rows. Since there is no repeating delimiter pattern and the content appears to be a single financial identifier line rather than a multi-column dataset, this should be processed as unstructured text for potential embedded PII extraction. The context indicates this is from a Swiss corporate financial data breach, but the provided snippet lacks tabular structure.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250519_172048609_310__id.csv
0 rows

File structure

Notes: The input is a single line containing only an IBAN number (CH8704835061435161001). This is NOT a structured dataset with columns; it is free-form text. IBAN is a financial account identifier and is not considered PII in the defined schema. No column mapping is possible because there are no structured records or headers. The file appears to be a fragment of financial data, possibly from an invoice or banking record, but lacks any discernible row structure or repeated patterns across multiple lines in the sample provided.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250520_172052759_309__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only row or metadata line. The first row contains only the word "id" followed by three "INTERNAL" placeholders, with no actual data rows present in the sample. No PII columns can be identified from this header alone. The breach context suggests this may be part of a larger dataset, but the provided sample lacks any structured PII data to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250528_172131257_305__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) with no structure or header. The file appears to be free-form text containing only this financial identifier, with no consistent column structure or multiple rows. No PII fields can be mapped from this unstructured single-line content.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250602_172057544_531__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) and no structured columnar data. The file appears to be free-form text with no consistent delimiter or header structure, and only contains one financial identifier. According to the unstructured opt-out rules, when there is no consistent row structure and the file contains identifiable PII (in this case, a bank account IBAN), it should be classified as unstructured with an empty columns object.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250603_172158970_530__id.csv
0 rows

File structure

Notes: The file appears to be free-form text with no consistent delimiter or structured columns. It contains unstructured content (likely financial records, notes, or descriptions) rather than tabular data. The sample shows a single IBAN value (CH8704835061435161001) which is not considered PII in this context as it is presented without associated personal names, addresses, or other identifying information. No column mapping is possible due to the lack of structured format.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250605_172057905_524__id.csv
0 rows

File structure

Notes: This is a single-line unstructured data file containing only an IBAN number (CH8704835061435161001). There is no consistent delimiter, header, or structured rows across the sample. IBAN is not a PII field per the defined schema. No columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250606_172209185_536__id.csv
0 rows

File structure

Notes: The input provided is a single line containing only an IBAN number (CH8704835061435161001). This is not a structured file with columns. The IBAN is a bank account identifier and not considered PII under the defined field types. Since there is no consistent delimiter, varying line shapes, and no structured columns, this is classified as unstructured text. However, no emails or phone numbers are visible in this snippet, so no extraction is needed.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250610_172101835_534__prtry.csv
0 rows

File structure

Notes: This is an unstructured file containing only the word "INTERNAL" repeated across rows. No consistent column structure or PII is present. The file appears to be a placeholder or security marker rather than actual data.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250611_172108801_526__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The sample provided shows only a header row with placeholder 'INTERNAL' entries and no actual data rows. Since no PII values are visible and the headers do not map to any PII fields, no columns can be identified as containing PII. The file appears to be a placeholder or redacted version, possibly indicating internal-only identifiers that would be skipped per rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250612_172116946_537__id.csv
0 rows

File structure

Notes: This is a free-form text snippet containing only an IBAN (CH8704835061435161001). There are no consistent columns or structured data in the provided sample. The IBAN itself is not classified as PII under the given field types, and the content appears to be a note or fragment rather than a delimited dataset. No columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250613_172058815_527__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data appears to be only a header row containing placeholder 'INTERNAL' labels repeated four times. No actual data rows or PII values are present in the sample. Therefore, no columns can be mapped to PII fields. This is likely just a placeholder or redacted header from the breach data.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250616_172102761_528__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001). No consistent delimiter or column structure detected; this is unstructured financial data from Zynex breach. IBAN is not a PII field in the defined schema and should be handled separately if needed.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250617_172059833_539__prtry.csv
0 rows

File structure

Notes: The provided data is not structured. The first three rows appear to be headers or metadata ('id', 'INTERNAL', 'INTERNAL') with no actual data rows following in the sample. There is no consistent delimiter or row structure visible, and no PII is present in these rows. Since this appears to be a header-only or metadata snippet without actual data rows, we classify it as unstructured with no columns to map. The breach context mentions financial records but this snippet doesn't contain any PII or structured data.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250618_172118915_529__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only an IBAN number (CH8704835061435161001) with no structured columns or consistent delimiter. The content appears to be a single line of financial data rather than a dataset with multiple rows and columns. Since there are no structured records with repeating patterns, this is classified as unstructured text.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250619_172053869_538__id.csv
0 rows

File structure

Notes: The provided text is a single line containing an IBAN number (CH8704835061435161001), which is not considered PII under the defined categories. There is no structured format or columnar data present in the sample. The context mentions a corporate data breach but the actual sample provided is just one line of unstructured data.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250620_172049738_540__prtry.csv
0 rows

File structure

Notes: The file appears to be a headerless internal identifier list with no actual PII values visible in the first 50 rows. All entries are labeled 'INTERNAL' and appear to be internal reference codes rather than structured personal data. Since there is no consistent delimiter structure and no PII content, this is classified as unstructured with no columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250623_172108663_535__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet only contains header labels 'id' and repeated 'INTERNAL' entries with no actual values. These appear to be internal identifier columns that do not contain any PII. No PII fields are present in this sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250625_172219950_533__id.csv
0 rows

File structure

Notes: The provided text is unstructured and free-form, consisting of a single IBAN value without any consistent column structure or header. It does not conform to a CSV or any other structured format, and there are no repeated lines or patterns indicating columnar data. The IBAN itself is not a PII field in the defined context, so no mapping is required.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250627_172215163_532__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample only contains header row and internal column names that are non-PII (marked as INTERNAL). No actual PII values are present in the first 50 rows to map to PII fields. All columns are internal identifiers and should be skipped per rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250630_172217377_525__id.csv
0 rows

File structure

Notes: This is not structured data. The provided content appears to be a single line containing an IBAN number (CH8704835061435161001), which is not considered PII under the given rules (it is a bank account identifier, not personal address or identity). There is no consistent delimiter, no header, and no repeating structure across rows in the sample. The file is likely a raw text dump or snippet without columnar data. Since there is no structured format, we return an empty columns object and classify as unstructured.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250701_172216179_202__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only line showing placeholder column names "id" and repeated "INTERNAL". No actual data rows were provided to analyze for PII content. Based solely on these headers, no PII fields can be identified. All columns appear to be internal identifiers or placeholders.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250703_172059603_203__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text file containing only an IBAN number (CH8704835061435161001). There is no structured data, headers, or repeated pattern across multiple rows. The file appears to be a standalone financial identifier, not a breach record with PII fields. No columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250704_172059126_201__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only line with no data rows provided. The headers are all labeled 'INTERNAL', indicating internal identifiers which must be skipped per exclusion rules. No PII fields are present.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250707_172219609_200__id.csv
0 rows

File structure

Notes: The file appears to be unstructured free-form text. The sample contains a single IBAN number (CH8704835061435161001) which is a financial account identifier rather than personal PII. There are no consistent delimiters or column structures, and the content resembles a note or snippet rather than structured tabular data. Since this is unstructured with no column mapping possible, we return an empty columns object.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250708_172103610_204__prtry.csv
0 rows

File structure

Notes: The file is a free-form text file with no consistent delimiter or structure. The first 5 rows appear to be headers or metadata indicating internal identifiers, with no actual data rows visible in the sample. Since there is no consistent columnar structure and no PII is present in the visible sample, this is classified as unstructured with no columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250709_172058737_210__id.csv
0 rows

File structure

Notes: This is a single-line file containing only a Swiss IBAN (CH8704835061435161001). There are no structured columns or row-based data. The file is not a CSV or tabular format; it appears to be a standalone IBAN value, possibly from a financial record or breach context. No PII fields can be mapped because there are no columns or structured data to analyze.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250710_172126114_204__id.csv
0 rows

File structure

Notes: The provided input is not a structured delimited file. It appears to be a snippet of unstructured data, possibly a note or comment, containing a single IBAN value (CH8704835061435161001). There is no consistent column structure or header, and the data does not conform to any expected CSV, TSV, or other delimited format. The IBAN is not part of the defined PII fields (email, phone, dob, name, address, etc.). Since there is no row structure and the data is free-form, it is classified as unstructured. No PII columns can be mapped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250711_172130028_213__prtry.csv
0 rows

File structure

Notes: The provided data appears to be a free-form text with no consistent delimiter or structured columns. The lines shown are simply the word 'INTERNAL' repeated, which indicates this is likely a placeholder or header note rather than actual data rows. Since there is no structured data with columns, and no identifiable PII in this snippet, we classify this as unstructured with no column mappings.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250714_172139638_208__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet consists solely of the header row with column labels 'id' and multiple 'INTERNAL' labels. No PII values are present in the visible rows, and the headers do not indicate any mappable PII fields. Based on the breach context (Zynex internal corporate data), these columns likely represent internal identifiers or metadata and should be treated as non-PII skip fields. No email, phone, name, address, DOB, SSN, or other PII fields are detectable from this sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250715_172055193_211__id.csv
0 rows

File structure

Notes: The provided content is a single unstructured line containing an IBAN number (CH8704835061435161001). There is no consistent delimiter or row structure, and this appears to be free-form text with embedded financial data rather than structured records. Based on the breach context, this is likely a fragment from a financial record or invoice, but it does not contain any PII fields such as email, phone, name, address, etc. Since there is no structured format with columns, this is classified as unstructured with no columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250716_172114179_203__id.csv
0 rows

File structure

Notes: The provided sample is NOT a structured file but a single line containing an IBAN (CH8704835061435161001). This is not a breach record but a financial identifier. The file appears to be a standalone line or part of an unstructured document. Since this is not a CSV/TSV with headers or consistent structure, and there is no repeated pattern across multiple rows to define columns, we classify it as unstructured with no column mapping. The IBAN itself is not a PII field per the defined schema (it’s a bank account identifier, not personal identity data). If more lines are available showing repeated patterns, re-evaluate for structured format.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250717_172106322_209__id.csv
0 rows

File structure

Notes: The provided content is a single line containing an IBAN number (CH8704835061435161001) rather than a structured dataset with multiple rows and columns. This appears to be a fragment of financial data from the Zynex breach, but it lacks the structure required for column mapping. Since there are no consistent delimiters or multiple rows to analyze, this is classified as unstructured content. The IBAN itself is not classified as PII under the provided field types, so no columns are mapped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250718_172118608_200__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) and no structured columns

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250721_172116756_205__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001), no structured columns or consistent delimiter observed in the sample. This is an unstructured file requiring special processing.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250722_172104970_214__id.csv
0 rows

File structure

Notes: This is a single-line unstructured input containing only an IBAN number (CH8704835061435161001) and no structured tabular data. It lacks any consistent delimiter or header structure and does not contain any other PII fields. The input is not a CSV or any other structured format; it appears to be a standalone financial identifier rather than part of a larger dataset with multiple rows of PII. Therefore, it is correctly classified as unstructured text with no column mapping required.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250724_172111180_201__id.csv
0 rows

File structure

Notes: This is a free-form text snippet containing only an IBAN (CH8704835061435161001) and no structured data. The file appears to be unstructured, containing just a single IBAN line without any consistent columnar structure or header. IBAN is not a PII field per the defined schema.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250725_172201402_207__id.csv
0 rows

File structure

Notes: This is unstructured text containing only an IBAN (CH8704835061435161001) and no structured columns. It does not represent a data breach with PII fields. The content appears to be a single line of financial data, not a delimited file with personal information.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250728_172202246_212__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) and no consistent column structure — unstructured opt-out applies

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250729_172110955_202__id.csv
0 rows

File structure

Notes: This is a free-form text file containing unstructured data. The sample provided is a single line with an IBAN number (CH8704835061435161001) which is not considered PII under the defined field types. There is no consistent delimiter or structured format across rows, and the content appears to be a snippet or note rather than a dataset with columns. Therefore, it is classified as unstructured text with no importable structured columns.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250731_172210817_206__id.csv
0 rows

File structure

Notes: This is unstructured data containing only an IBAN (CH8704835061435161001) with no consistent column structure or header. The sample shows a single line of free-form text without delimiters or repeated patterns, matching the unstructured opt-out criteria.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250805_172110511_435__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (not PII per our rules), no consistent delimiter structure across lines, appears to be a single-line note or description file rather than structured records

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250806_172101265_444__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001) which is not considered personally identifiable information in this context. The file appears to be unstructured data with no column structure or header. No PII fields can be mapped from this line alone.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250807_172058648_434__id.csv
0 rows

File structure

Notes: This is not a structured dataset but a single line containing a Swiss IBAN (CH8704835061435161001). The breach context mentions internal financial records and customer invoicing data, but this particular snippet is just a standalone IBAN value. There are no column headers or structured rows to map. IBANs are financial identifiers and not considered PII per the exclusion rules (they are account numbers, not personal identifiers like names, addresses, or emails). Since there is no row structure and this appears to be a single value, we classify this as unstructured with no columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250808_172058365_439__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only snippet showing three internal ID columns labeled "INTERNAL". No PII is present in the visible rows. The file likely contains internal identifiers only in this section.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250811_172057158_446__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is not structured with any PII fields. The first row appears to be a header row containing only the word 'INTERNAL' repeated three times, and the second row is blank. There are no columns with identifiable personal information such as names, addresses, emails, phone numbers, dates of birth, or other PII fields. Therefore, no columns can be mapped to PII fields.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250812_172051678_440__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This is a header-only row with no actual data values. The first row contains placeholder labels 'id' and 'INTERNAL' repeated three times, indicating this is likely a malformed or placeholder header row. No PII can be mapped from this header alone. Further rows with actual data would be needed for proper column mapping.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250813_172104444_433__id.csv
0 rows

File structure

Notes: The file is unstructured free-form text. It contains a single IBAN (CH8704835061435161001) but no consistent column structure or header. This is typical of financial or transaction notes in breach data where only account numbers are recorded without structured fields.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250815_172036050_436__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to contain only internal identifiers (labeled 'INTERNAL') repeated across rows with no actual PII values. No columns map to PII fields based on header names or sample values. All columns are internal IDs and should be skipped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250818_171838536_437__id.csv
0 rows

File structure

Notes: The provided sample is NOT structured data. It contains only a single IBAN number (CH8704835061435161001) with no column structure, headers, or row patterns. This is a free-form snippet likely extracted from a financial record or breach context note, not a delimited file with columns. Since there is no consistent delimiter or row structure, and this is just a single value, this qualifies as unstructured text per the rules. No column mapping is possible.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250819_172109161_442__id.csv
0 rows

File structure

Notes: The sample provided is not a delimited file but a single line containing an IBAN number (CH8704835061435161001). This is unstructured data with no consistent column structure or header. As per the rules, unstructured files with no consistent delimiter and varying line shapes should be processed through a streaming email/phone extractor, but in this case, there is no email or phone visible. Since this is a single line and not a file with multiple lines of varying shapes, it is considered unstructured with no embedded emails or phones to extract. Therefore, return an empty columns object.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250820_172059989_443__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) and no consistent delimiter structure

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250821_172101238_441__id.csv
0 rows

File structure

Notes: This is unstructured free-form text containing a single IBAN (CH8704835061435161001) but no consistent columnar structure. The file appears to be a raw snippet or note rather than a delimited dataset. Since there are no repeated patterns, headers, or structured rows, this should be processed as unstructured text for any embedded PII extraction.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250822_172059849_447__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001). The file appears to be unstructured data with no consistent delimiter or column structure. The IBAN is financial account information and is NOT considered PII in this context (it's an account identifier, not personal identifier). Since there are no repeated patterns or structured columns, and this is just a single value, we classify this as unstructured with no columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250826_173418738_432__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent columnar structure. This appears to be a single-line fragment from a financial record or log, not a structured dataset with repeating rows/columns. No emails or phones visible. Unstructured handling will allow any embedded financial identifiers to be extracted via separate processing.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250827_173537626_438__id.csv
0 rows

File structure

Notes: This is a single-line unstructured file containing only a Swiss IBAN (CH8704835061435161001). No column structure or PII fields are present beyond this one identifier, which is not mapped as it falls under financial/transactional data exclusion rules. The file does not contain any structured records or headers.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250828_172825135_445__id.csv
0 rows

File structure

Notes: The provided sample contains only a single IBAN number (CH8704835061435161001) and no structured tabular data. This appears to be a snippet of unstructured financial data rather than a delimited file with columns. Since there is no consistent delimiter or row structure across lines, and the sample is just a single line with an IBAN, we classify this as unstructured. However, IBANs themselves are not in the defined PII field list, so no mapping is performed.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250901_173813836_324__id.csv
0 rows

File structure

Notes: This is a free-form text sample (single line) containing only an IBAN number. No structured columns exist, and IBAN is not a defined PII field in our schema. Therefore, no columns to map. The content appears to be a snippet from financial records, but lacks any identifiable personal data patterns (emails, phones, names, etc.).

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250903_172500043_326__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) but no consistent column structure; appears to be raw financial records or invoice snippets without CSV/TSV formatting. Per rules, unstructured processing is required to extract any embedded PII like IBANs, emails, or phones.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250904_172433202_318__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). There is no structured data or repeated rows in the provided sample. IBAN is not considered PII under the provided field types and rules. The file appears to be a free-form text or a snippet without any columnar structure or headers. No columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250905_173506342_328__id.csv
0 rows

File structure

Notes: This is a free-form text file containing only a single IBAN (CH8704835061435161001) and no structured columns. The content is unstructured and does not contain any consistent delimiter or header structure. Since there are no repeated lines or structured data, this should be processed as unstructured text.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250908_173008723_323__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: Only headers present in sample, no data rows. Headers are all 'INTERNAL' identifiers (non-PII). No PII columns detected in this sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250909_172745504_329__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN, no structured columns

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250910_172115266_320__id.csv
0 rows

File structure

Notes: This file is not structured tabular data; it appears to be a single IBAN value (CH8704835061435161001) rather than a delimited file with columns. No consistent column structure or header exists, and the content is purely a financial identifier. Therefore, it is classified as unstructured text with no column mappings.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250911_172120988_327__prtry.csv
0 rows

File structure

Notes: This is a free-form text file containing only the header "id" and the word "INTERNAL" repeated across rows. There is no consistent delimiter or structured data. The content appears to be a placeholder or metadata indicating internal-only identifiers with no actual PII values present in the sample. Since the file lacks any structured columns and contains only the word "INTERNAL" (not actual PII), it is classified as unstructured with no PII columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250912_172814176_319__id.csv
0 rows

File structure

Notes: This is a single-line unstructured text containing only an IBAN (CH8704835061435161001). No consistent column structure exists across lines, and the file appears to be a snippet or fragment rather than a structured dataset. IBANs are financial identifiers, not PII fields per the defined schema, and thus are skipped. No emails, phone numbers, or other PII are visible in the sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250915_172923416_317__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) with no other data or structure. The file appears to be unstructured and contains no identifiable column structure or headers. Since it lacks any row structure or repeated patterns, it falls under the unstructured category. While IBANs can be considered PII, the format does not allow for column mapping, and the unstructured path will handle extraction if needed.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250916_172444726_325__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The sample provided contains only header-like lines that are actually placeholders ('id', 'INTERNAL', repeated three times). These are not valid column names and do not represent any PII fields. No actual data rows are present in the sample to analyze for PII content. Therefore, no columns can be mapped to PII fields based on this sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250918_172118384_316__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN (CH8704835061435161001) but no structured columns. The file appears to be unstructured data (likely a note or snippet) and does not contain a consistent tabular format with multiple rows and columns. As per rules, unstructured files with no consistent delimiter and varying line shapes should return an empty columns object.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250919_172836645_322__id.csv
0 rows

File structure

Notes: The provided content is a single line containing an IBAN (CH8704835061435161001). There is no structured delimiter, header, or repeated pattern across multiple rows. Since this is unstructured data with no consistent row structure, it qualifies as free-form text. The IBAN itself is financial account data, but the format rules specify that unstructured files with embedded PII should be routed through a streaming extractor. No column mapping is performed.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250922_172506625_330__id.csv
0 rows

File structure

Notes: This is a single line containing an IBAN number (CH8704835061435161001) rather than structured columnar data. The file appears to be a free-form text snippet showing a Swiss bank account identifier, not a delimited dataset with multiple rows and columns. There is no consistent delimiter or row structure present, and this single line does not represent a tabular dataset with headers and values. Therefore, it is classified as unstructured text.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250923_172435357_321__id.csv
0 rows

File structure

Notes: free-form text with no consistent column structure; appears to be a single IBAN value without surrounding data

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250924_173149191_331__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001). No structured columns exist in the provided sample. The content appears to be a standalone financial identifier rather than a CSV or tabular dataset. Since there is no consistent row structure or delimiter, and the file contains only a single line, it qualifies as unstructured free-form text.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20250926_172831513_315__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (not email/phone)

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251001_172849370_553__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (not email/phone), no consistent column structure or delimiter visible in sample

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251002_173038740_555__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample consists of only header labels 'id', 'INTERNAL', 'INTERNAL', 'INTERNAL' with no actual data rows. All columns appear to be internal identifiers (matching the exclusion rule for internal IDs). No PII fields are present in this header structure.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251003_172139619_549__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251006_172228837_550__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The first three rows appear to be placeholder headers indicating 'INTERNAL' columns with no actual data. No PII fields are present in the visible rows. Additional rows may contain PII, but they are not provided in this sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251007_172117358_557__id.csv
0 rows

File structure

Notes: This is a free-form text sample containing only an IBAN (CH8704835061435161001). There is no structured tabular data with consistent columns or delimiters visible in the provided input. The content appears to be a single line of financial data (IBAN) without any headers or additional rows that would constitute a CSV or other structured format. Since there are no repeated patterns, no column mapping can be performed.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251008_172623515_551__id.csv
0 rows

File structure

Notes: The sample provided is not a structured file with columns; it appears to be a single IBAN value (CH8704835061435161001) rather than a delimited dataset. There are no visible headers or repeated lines to infer a column structure. The sample does not contain any row structure, consistent delimiter, or repeated patterns across lines — it is effectively a single line of data. Since there is no structured format, we return an empty columns object and classify as unstructured. The IBAN itself is NOT considered PII in this context per exclusion rules (financial identifiers are skipped unless explicitly mapped, and IBANs are financial/account numbers not in our PII field list).

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251009_173253632_556__id.csv
0 rows

File structure

Notes: The provided data is not a structured table but a single line containing an IBAN (CH8704835061435161001). There is no consistent delimiter, no header, and the content is not in a tabular format. Since this is a single unstructured line and not a file with multiple lines of varying content, it does not meet the criteria for unstructured free-form text with embedded PII. Instead, this appears to be a single financial identifier (IBAN) which is not classified as PII under the provided field types. Therefore, no columns are mapped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251010_172525568_554__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is purely internal identifiers with no PII content. All columns are marked as INTERNAL and contain no personal or identifiable information. No PII fields are present in this sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251013_172745734_560__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only file or a file with only internal identifier columns labeled 'INTERNAL'. No PII fields are present in the visible rows. The columns are all marked as internal IDs and should be skipped according to exclusion rules.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251014_172109581_548__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is purely internal identifiers with no PII content. All columns are labeled 'INTERNAL' and contain no discernible personal information, email addresses, phone numbers, names, or other PII fields. This appears to be a header row indicating internal reference IDs with no actual PII data present in the sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251015_172846775_559__id.csv
0 rows

File structure

Notes: The provided input is a single unstructured line containing a Swiss IBAN (CH8704835061435161001). There is no consistent columnar structure or header present. The breach context describes internal financial records from Zynex, but the sample itself is not tabular data. Therefore, this is classified as unstructured text with no column mappings.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251016_172459088_552__id.csv
0 rows

File structure

Notes: The provided sample is NOT a delimited data file — it's a single line containing a Swiss IBAN (CH8704835061435161001). There is no row structure, no header, and no repeated data pattern. IBANs are financial account identifiers and are NOT PII (they do not uniquely identify individuals). The breach context describes corporate financial records (invoices, ERP data) rather than customer PII. Therefore, this is unstructured data with no columns to map.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251017_172218230_558__id.csv
0 rows

File structure

Notes: This is a single line containing only an IBAN number (CH8704835061435161001) with no surrounding context or structure. The data provided appears to be a snippet of financial information rather than a structured dataset with columns. Since there are no consistent delimiters, headers, or repeated patterns across multiple rows, this qualifies as unstructured text. The IBAN itself is a financial identifier and not considered PII under the defined fields, so no columns are mapped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251020_172724784_200__id.csv
0 rows

File structure

Notes: The provided input appears to be a single line containing only an IBAN (International Bank Account Number) and no structured columnar data. There is no consistent delimiter, header, or multiple rows to analyze for column mapping. The IBAN itself is not classified as PII under the defined fields, so no columns are mapped.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251021_172449571_201__id.csv
0 rows

File structure

Notes: This is unstructured text containing only a single IBAN value (CH8704835061435161001). There is no consistent column structure or header, and this appears to be a single-line data snippet rather than a multi-row dataset. The IBAN is not classified as PII under the specified field types.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251022_172112964_206__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This appears to be a header-only row or placeholder file. The sample shows only column labels 'id', 'INTERNAL', 'INTERNAL' repeated three times with no actual data rows provided. Without actual data rows containing PII values, no columns can be reliably mapped. The 'id' column is likely an internal numeric identifier that should be skipped per rules. No PII columns are present in the visible structure.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251023_172223968_205__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to contain only internal identifier columns labeled 'INTERNAL' with no discernible PII. All columns are marked as internal identifiers and contain no personal information such as names, addresses, emails, or other PII fields. Therefore, no columns map to PII fields.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251024_172449168_204__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data is purely internal identifiers with no PII content. All columns are labeled 'INTERNAL' and contain no personal information such as names, addresses, emails, etc. Therefore, no columns map to PII fields.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251027_173614388_208__id.csv
0 rows

File structure

Notes: The provided data is not a structured delimited file. It appears to be a single line containing an IBAN number (CH8704835061435161001). There is no consistent delimiter or header structure across rows, and the sample only shows one line with a financial identifier. This is not a CSV or tabular dataset with columns to map to PII fields. The IBAN itself is a financial account identifier and not considered PII per the exclusion rules (it is a bank account number, not a personal identifier like name, address, etc.). Therefore, no column mapping is performed.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251028_173548762_207__id.csv
0 rows

File structure

Notes: The provided content appears to be unstructured financial data rather than a delimited file with columnar PII fields. The visible content shows a single IBAN value (CH8704835061435161001) and no consistent delimiter structure across rows. Based on the breach context, this is likely a snippet from financial records rather than a CSV/TSV file containing personal data. No structured columns are present to map to PII fields.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251030_172113934_203__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided sample contains only header-like lines indicating internal IDs ('id', 'INTERNAL', 'INTERNAL', 'INTERNAL'). There are no actual data rows visible in the first 50 rows to map to PII fields. This appears to be a header row or metadata row only. No PII columns can be identified from this sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251031_173343259_202__id.csv
0 rows

File structure

Notes: The provided text is a single unstructured line containing a Swiss IBAN number (CH8704835061435161001). There are no structured columns or delimiters, and the content does not match the expected format of a CSV or other structured data file. The file appears to be a standalone IBAN rather than a data breach record with PII fields.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251103_172628402_310__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The file appears to be a header-only row or metadata row without actual data rows. The headers are labeled 'INTERNAL' repeatedly, suggesting this is not structured PII data but rather a placeholder or internal reference row. No PII fields can be mapped from this header alone.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251104_173112256_311__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: This file appears to be a header-only file or a metadata description rather than actual data rows. The first row contains the word 'id' and subsequent rows are labeled 'INTERNAL', indicating this is likely a schema definition or placeholder file rather than structured PII data. No PII fields can be mapped from this header-only content.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251105_172518834_313__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: The provided data snippet only contains header row with 'id' and three 'INTERNAL' fields. No PII fields are visible in this sample. The context indicates this is part of a corporate financial data breach, but the actual PII columns are not present in the first 50 rows shown.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251110_173111649_309__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) — no consistent columnar structure visible in sample; appears to be raw financial/IBAN data dump

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251111_172718081_314__id.csv
0 rows

File structure

Notes: This is unstructured text containing only an IBAN number. No structured columns or PII fields are present.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251112_172401351_312__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN but no consistent column structure

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251113_172758928_316__id.csv
0 rows

File structure

Notes: This is a single-line unstructured snippet containing only an IBAN number (CH8704835061435161001) with no structured columns or repeated patterns. No PII fields can be mapped from this sample.

finanzen__zed_files__2025__QRIBAN_camt.054_SIC_04_087906143516_NN_0879061435161001_20251114_173301144_315__id.csv
0 rows

File structure

Notes: free-form text with embedded IBAN (CH8704835061435161001) and no consistent structured columns. This is unstructured financial note or invoice snippet from Zynex breach, not a delimited dataset.

finanzen__zed_files__2026__2025-12-31_ZQR_CH360020620693823701D_CHF_WC9CEKBR8LXYUD5A__prtry.csv
0 rows

File structure

Notes: The sample consists solely of the string 'A89' repeated across all rows with no delimiters or structure. This is not a delimited file and lacks any columnar organization. Since there is no consistent structure or visible PII in this raw sample, it is classified as unstructured. No column mapping is possible.

finanzen__zed_files__2026__2026-01-05_ZQR_CH360020620693823701D_CHF_WC9CEKBSCJB7NXFA__prtry.csv
0 rows

File structure

Notes: This is a free-form text file with no consistent delimiter or structure. Each line contains the same value 'A89', indicating this is not structured data with columns. There are no emails or phone numbers visible in the sample, and no row structure exists to map columns.

finanzen__zed_files__2026__2026-01-06_ZQR_CH360020620693823701D_CHF_WC9CEKBSDKT33KWA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a series of codes/IDs with no headers or PII visible in first 50 rows

finanzen__zed_files__2026__2026-01-07_ZQR_CH360020620693823701D_CHF_WC9CEKBSEKWVBERA__prtry.csv
0 rows

File structure

Notes: The sample consists of unstructured lines with no consistent delimiter or row structure. Each line is identical ('A89') and does not contain any identifiable PII patterns such as emails, phone numbers, names, or addresses. The content appears to be a placeholder or code rather than meaningful data. Given the lack of structured columns and the repetitive nature of the data, this is classified as unstructured text with no importable PII columns.

finanzen__zed_files__2026__2026-01-08_ZQR_CH360020620693823701D_CHF_WC9CEKBSFKAHDQNA__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be raw banking/IBAN data fragments rather than tabular records

finanzen__zed_files__2026__2026-01-09_ZQR_CH360020620693823701D_CHF_WC9CEKBSGL6N4L4A__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a series of repeated codes/IDs (A89) rather than structured records containing PII

finanzen__zed_files__2026__2026-01-12_ZQR_CH360020620693823701D_CHF_WC9CEKBSJKL6F69A__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure. Appears to be a simple text file with repeated value 'A89' across lines, no headers or columns. No emails/phones visible in this snippet but unstructured path is triggered due to lack of structure.

finanzen__zed_files__2026__2026-01-13_ZQR_CH360020620693823701D_CHF_WC9CEKBSKKGLLVHA__prtry.csv
0 rows

File structure

Notes: The sample shows only a single repeating string 'A89' across all lines with no delimiters or structure. This is not a delimited data file; it's unstructured content (likely a placeholder, log fragment, or error message). No PII is present, and no column mapping is possible.

finanzen__zed_files__2026__2026-01-14_ZQR_CH360020620693823701D_CHF_WC9CEKBSLKHYUMQA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a raw dump or log file with repeated values 'A89' across lines, no column headers or structured data visible in the first 50 rows. This qualifies as unstructured content per the opt-out rules.

finanzen__zed_files__2026__2026-01-15_ZQR_CH360020620693823701D_CHF_WC9CEKBSMJ5QDG2A__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a simple file listing 'cd' followed by repeated values 'A89' across lines. No structured columns or PII visible in the sample.

finanzen__zed_files__2026__2026-01-16_ZQR_CH360020620693823701D_CHF_WC9CEKBSNMUUFUZA__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be raw financial/banking data snippets rather than tabular records

finanzen__zed_files__2026__2026-01-19_ZQR_CH360020620693823701D_CHF_WC9CEKBSQKBFGRJA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure. Appears to be a simple listing of codes ('A89') repeated across lines with no headers or identifiable PII. No structured columns present.

finanzen__zed_files__2026__2026-01-20_ZQR_CH360020620693823701D_CHF_WC9CEKBSRHWNVYGA__id.csv
0 rows

File structure

Notes: free-form text with embedded banking identifiers (IBAN), no consistent structure or column mapping possible

finanzen__zed_files__2026__2026-01-22_ZQR_CH360020620693823701D_CHF_WC9CEKBSTF5GYYKA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure — appears to be a raw dump or log snippet with no CSV/TSV structure. Contains repeated values 'A89' which may be internal codes, but no identifiable PII patterns or structured columns.

finanzen__zed_files__2026__2026-01-23_ZQR_CH360020620693823701D_CHF_WC9CEKBSUYTVKF5A__prtry.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: no·Quote: "

Notes: File contains only repeated non-PII identifiers ('cd', 'A89'). No structured PII data detected. This appears to be a fragment, list of internal codes, or corrupted file segment. No importable personal data identified.

finanzen__zed_files__2026__2026-01-27_ZQR_CH360020620693823701D_CHF_WC9CEKBSYUBF5LXA__id.csv
0 rows

File structure

Notes: This file appears to be unstructured financial/banking data. The sample shows lines with IBAN-like values (e.g., "CH36002062069382370") and bank codes ("UBSWCHZHREB,"). These are not personal PII fields but rather financial identifiers. There is no consistent column structure, and the data appears to be raw financial records rather than customer PII. Since there is no consistent delimiter or header structure, and the content is purely financial (no embedded emails/phones), this is correctly classified as unstructured with no PII columns to map.

finanzen__zed_files__2026__2026-01-29_ZQR_CH360020620693823701D_CHF_WC9CEKBS3CMNBYMA__id.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File contains only banking identifiers (SWIFT BIC and IBAN codes). These are financial account routing numbers, not personally identifiable information. No PII columns present. This appears to be a fragment of financial/accounting data (2 rows total, 2 columns) with no personal data.

finanzen__zed_files__2026__2026-01-30_ZQR_CH360020620693823701D_CHF_WC9CEKBS4827QAUA__id.csv
0 rows

File structure

Notes: free-form text with embedded financial identifiers (IBANs), no consistent column structure

finanzen__zed_files__2026__2026-02-02_ZQR_CH360020620693823701D_CHF_WC9CEKBS77D7V3PA__id.csv
0 rows

File structure

Notes: free-form text with embedded financial identifiers (IBANs). No consistent column structure present in the sample.

finanzen__zed_files__2026__2026-02-03_ZQR_CH360020620693823701D_CHF_WC9CEKBS9AKJ7RFA__id.csv
0 rows

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample shows unstructured financial data (bank details) with no repeating columnar pattern. Values appear to be bank account details (IBAN) and bank names, but they are not presented in a tabular format with consistent columns across rows. Therefore, this is classified as unstructured text.

finanzen__zed_files__2026__2026-02-04_ZQR_CH360020620693823701D_CHF_WC9CEKBTADFWG9TA__id.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File contains only banking identifiers (SWIFT/BIC codes and IBAN account numbers). These are financial account identifiers, not personal PII. No personally identifiable information detected in the 50 rows provided.

finanzen__zed_files__2026__2026-02-05_ZQR_CH360020620693823701D_CHF_WC9CEKBTBGH9C3UA__id.csv
0 rows

File structure

Notes: free-form text with embedded financial identifiers (IBAN, BIC)

finanzen__zed_files__2026__2026-02-06_ZQR_CH360020620693823701D_CHF_WC9CEKBTCNCE6V2A__id.csv
0 rows

File structure

Notes: free-form text with embedded financial identifiers (IBAN, BIC) but no consistent column structure. The sample appears to be a raw snippet containing bank account information rather than a delimited dataset with PII columns.

finanzen__zed_files__2026__2026-02-18_ZQR_CH360020620693823701D_CHF_WC9CEKBTNTCX8BQA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be raw data dump or log file with no column headers or structured fields. Content shows repeated string 'A89' which is not identifiable PII. No emails, phones, or other PII visible in sample.

finanzen__zed_files__2026__2026-02-19_ZQR_CH360020620693823701D_CHF_WC9CEKBTPVCCJFHA__id.csv
0 rows

File structure

Notes: This is unstructured free-form text containing only bank account and IBAN information. No consistent column structure exists across the sample lines, and the data appears to be raw financial records without any delimited fields. The sample shows IBAN entries and possibly other financial identifiers, but lacks any repeating structured format that would allow column mapping.

finanzen__zed_files__2026__2026-02-20_ZQR_CH360020620693823701D_CHF_WC9CEKBTQT62WCTA__id.csv
0 rows

File structure

Notes: free-form text with embedded financial identifiers (IBAN, BIC), no consistent column structure

finanzen__zed_files__2026__2026-03-04_ZQR_CH360020620693823701D_CHF_WC9CEKBT665RGN3A__id.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File contains only banking identifiers (SWIFT BIC and IBAN). Neither 'anybic' nor 'iban' columns map to any PII field type in the available schema. BICs and IBANs are financial account identifiers, not personal identifying information. No PII present.

finanzen__zed_files__2026__2026-03-05_ZQR_CH360020620693823701D_CHF_WC9CEKBT8CQCPGDA__id.csv
0 rows

File structure

Notes: The provided data is not a structured table but appears to be a snippet of financial/banking information (IBAN details). There is no consistent columnar structure across rows, and the sample shows free-form text with banking identifiers rather than a repeatable CSV-like format. Therefore, this is classified as unstructured data.

finanzen__zed_files__2026__2026-03-09_ZQR_CH360020620693823701D_CHF_WC9CEKBUBTLUFFHA__id.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File contains only banking identifiers (SWIFT/BIC and IBAN codes). These are financial account identifiers, not personally identifiable information. No PII columns detected. The data appears to be a banking reference snippet rather than personal records.

finanzen__zed_files__2026__2026-03-10_ZQR_CH360020620693823701D_CHF_WC9CEKBUCTYJ25TA__prtry.csv
0 rows

File structure

Notes: The provided sample consists of free-form text with no consistent delimiter or structure. Each line contains the same value 'A89', which appears to be an internal code or placeholder rather than meaningful PII. There are no headers, varying line shapes, or embedded emails/phones visible in this snippet. Since there is no columnar structure, this is classified as unstructured text.

finanzen__zed_files__2026__2026-03-11_ZQR_CH360020620693823701D_CHF_WC9CEKBUDV3CVZXA__prtry.csv
0 rows

File structure

Notes: The sample consists of three lines with no delimiter structure or consistent fields. The data appears to be internal codes ('A89') rather than PII. There is no evidence of a structured format (CSV, TSV, etc.), and no visible emails or phone numbers in the provided snippet. Therefore, this is classified as unstructured text with no column mapping required.

finanzen__zed_files__2026__2026-03-12_ZQR_CH360020620693823701D_CHF_WC9CEKBUEYKLV34A__prtry.csv
0 rows

File structure

Notes: The provided data is purely unstructured free-form text with no consistent delimiter or columnar structure. The lines contain only a single repeated string 'A89' with no variation in format, length, or content. There are no visible emails, phone numbers, or any other PII in the sample. Since there is no row structure and no embedded PII, this is classified as unstructured text with no columns to map.

finanzen__zed_files__2026__2026-03-13_ZQR_CH360020620693823701D_CHF_WC9CEKBUF6NZ9YEA__prtry.csv
0 rows

File structure

Notes: The file appears to be unstructured. The first 50 rows contain only the values 'A89' and empty fields, with no consistent delimiter or structure. No identifiable PII is visible in these rows, and the format does not conform to a structured CSV or other tabular format. Given the context of the breach (internal corporate financial records), this may be a headerless or malformed file, but without consistent columns or PII in the visible rows, it is treated as unstructured.

finanzen__zed_files__2026__2026-03-16_ZQR_CH360020620693823701D_CHF_WC9CEKBUJFGW76GA__id.csv
0 rows

File structure

Notes: free-form text with embedded financial identifiers (IBANs), no consistent delimiter structure across lines

finanzen__zed_files__2026__2026-03-17_ZQR_CH360020620693823701D_CHF_WC9CEKBUKGTHJSNA__id.csv
0 rows

File structure

Notes: The provided data is unstructured financial text with no consistent row structure. The lines contain bank identifiers (IBAN) and bank codes, but lack any CSV-like delimiters or repeated column patterns. This is typical of raw financial record dumps rather than tabular data. Since there is no consistent delimiter or header structure, and the content appears to be free-form banking information, we classify this as unstructured text.

finanzen__zed_files__2026__2026-03-18_ZQR_CH360020620693823701D_CHF_WC9CEKBULK2RLZAA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure; appears to be a simple file with repeated string 'A89' across lines, no PII visible in sample. This is not a structured dataset with columns.

finanzen__zed_files__2026__2026-03-19_ZQR_CH360020620693823701D_CHF_WC9CEKBUMMEMZ6YA__prtry.csv
0 rows

File structure

Notes: The provided data appears to be free-form text with no consistent delimiter structure. Each line contains the same value 'A89', which does not exhibit any structured format or identifiable PII patterns. There is no evidence of column headers, consistent field separators, or varied content that would indicate a CSV or other structured format. Given the lack of any discernible structure and the repetitive nature of the content, this is classified as unstructured text without embedded emails or phone numbers.

finanzen__zed_files__2026__2026-03-20_ZQR_CH360020620693823701D_CHF_WC9CEKBUNRTTXQKA__prtry.csv
0 rows

File structure

Notes: The provided sample consists solely of the string 'cd' repeated four times with no delimiter or structure. This is not a CSV or any structured format; it appears to be a fragment or placeholder. Since there is no consistent column structure and no embedded PII visible in this snippet, we classify it as unstructured with no columns to map. Further context or additional rows would be needed to determine if this is part of a larger file.

finanzen__zed_files__2026__2026-03-25_ZQR_CH360020620693823701D_CHF_WC9CEKBUTN82T72A__id.csv
0 rows

File structure

Notes: The file is unstructured financial data with IBAN and BIC codes. There are no consistent column headers or structured PII fields. The sample shows bank account information rather than personal identifiers.

finanzen__zed_files__2026__2026-03-27_ZQR_CH360020620693823701D_CHF_WC9CEKBUWHTJUM2A__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure; appears to be raw financial/banking data fragments (account numbers, IBANs) rather than tabular PII records

finanzen__zed_files__2026__2026-03-31_ZQR_CH360020620693823701D_CHF_WC9CEKBU3PM2ECYA__id.csv
0 rows

File structure

Notes: free-form text with no consistent column structure. Sample shows fragmented bank/IBAN data fragments without row alignment or headers. Contains IBAN patterns (CH36...) but lacks consistent delimiter or repeating structure across lines. This qualifies as unstructured data per rules.

finanzen__zed_files__2026__2026-04-02_ZQR_CH360020620693823701D_CHF_WC9CEKBU6J3GPDWA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be repeated string 'A89' across all lines (no PII visible in sample). No column structure present.

finanzen__zed_files__2026__2026-04-07_ZQR_CH360020620693823701D_CHF_WC9CEKBU95D5EYDA__prtry.csv
0 rows

File structure

Notes: The file appears to contain only a single repeated value 'A89' across all lines, with no delimiter structure or identifiable PII. This is not a structured dataset with columns; it looks like a placeholder, status code, or single-field file. No emails, phone numbers, or other PII are present in the sample.

finanzen__zed_files__2026__2026-04-08_ZQR_CH360020620693823701D_CHF_WC9CEKBVA9Z2QATA__id.csv
0 rows

File structure

Notes: free-form text with embedded financial identifiers (IBAN, BIC)

finanzen__zed_files__2026__2026-04-09_ZQR_CH360020620693823701D_CHF_WC9CEKBVCCTYNUFA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be a simple file with repeated values 'A89' across lines, no identifiable PII or structured columns. This is not a CSV or tabular dataset and contains no embedded emails/phones. Treated as unstructured for processing.

finanzen__zed_files__2026__2026-04-10_ZQR_CH360020620693823701D_CHF_WC9CEKBVDJNP7MEA__prtry.csv
0 rows

File structure

Notes: The provided sample shows only a single repeated value 'A89' across all rows with no delimiter or structure. This is not a structured table with columns; it's free-form text with no visible PII. Since there are no consistent columns or delimiters and the content appears to be a single repeated code, we classify this as unstructured with no columns to map.

finanzen__zed_files__2026__2026-04-13_ZQR_CH360020620693823701D_CHF_WC9CEKBVFRVJM2UA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure. Appears to be a raw dump of data identifiers (e.g., 'A89') rather than structured records. No emails or phones visible in this sample, but unstructured flag applies due to lack of consistent columns.

finanzen__zed_files__2026__2026-04-14_ZQR_CH360020620693823701D_CHF_WC9CEKBVGQ8GNKGA__id.csv
0 rows

File structure

Notes: free-form text with embedded banking identifiers (IBAN) — no consistent delimiter or row structure across lines

finanzen__zed_files__2026__2026-04-15_ZQR_CH360020620693823701D_CHF_WC9CEKBVHTLVBEFA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter or row structure — appears to be raw data dump or log snippet. No column mapping possible; route through unstructured processing for embedded PII extraction

finanzen__zed_files__2026__2026-04-16_ZQR_CH360020620693823701D_CHF_WC9CEKBVJWS6RYLA__id.csv
0 rows

File structure

Notes: free-form text with embedded financial data (IBANs and bank codes), no consistent column structure. This appears to be raw banking/financial records without CSV/structured formatting.

finanzen__zed_files__2026__2026-04-17_ZQR_CH360020620693823701D_CHF_WC9CEKBVKWWCALXA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be raw data dump or log file with repeated values 'A89' across lines

finanzen__zed_files__2026__2026-04-20_ZQR_CH360020620693823701D_CHF_WC9CEKBVMZDUCK5A__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; sample shows raw financial line items and IBAN data without column headers or repeating format

finanzen__zed_files__2026__2026-04-21_ZQR_CH360020620693823701D_CHF_WC9CEKBVNYXFRJ9A__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be raw data dump or log snippet without columnar format. Contains no identifiable PII patterns in this snippet.

finanzen__zed_files__2026__2026-04-29_ZQR_CH360020620693823701D_CHF_WC9CEKBVYAAMJWMA__id.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure. The sample shows fragments of IBAN numbers and bank codes, but lacks any repeated structured format across rows. No column headers or consistent field positions exist. This appears to be raw banking data fragments rather than a delimited table.

finanzen__zed_files__2026__2026-04-30_ZQR_CH360020620693823701D_CHF_WC9CEKBVZ6X9PNNA__id.csv
0 rows

File structure

Notes: The provided data is not a structured table but appears to be fragments of financial/banking information. There are no consistent columns or delimiters across the lines — instead we see isolated entries like IBAN numbers and bank codes. This matches the description of a breach containing financial records. Since there is no structured row format, this should be processed as unstructured text for embedded PII extraction.

finanzen__zed_files__2026__2026-05-05_ZQR_CH360020620693823701D_CHF_WC9CEKBV7DKW3N2A__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure. Sample shows only three identical lines 'A89' with no identifiable columns or PII patterns. This appears to be an unstructured data block rather than a delimited dataset.

finanzen__zed_files__2026__2026-05-06_ZQR_CH360020620693823701D_CHF_WC9CEKBV8KXYG7LA__id.csv
0 rows

File structure

Notes: This is unstructured financial data containing IBAN and BIC codes rather than personal PII. No consistent columnar structure exists - appears to be raw bank transfer lines with only account identifiers. No emails, phone numbers, or names are visible in the sample.

finanzen__zed_files__2026__2026-05-07_ZQR_CH360020620693823701D_CHF_WC9CEKBV9P7NBQJA__id.csv
0 rows

File structure

Format: CSV·Delimiter: Comma·Has header: yes·Quote: "

Notes: File contains only banking identifiers (SWIFT BIC and IBAN). These are financial account numbers, not personal PII fields. BIC/IBAN are institutional/transactional identifiers, not mappable to the available PII field types (email, phone, dob, name, address, ssn, etc.). No personal information extracted.

finanzen__zed_files__2026__2026-05-08_ZQR_CH360020620693823701D_CHF_WC9CEKBWAW2UFWGA__prtry.csv
0 rows

File structure

Notes: free-form text with no consistent delimiter structure; appears to be raw data dump or log entries with no column headers or structured fields. Only contains repeated value 'A89' across lines, no PII visible. No CSV/TSV structure detected.

finanzen__zed_files__2026__2026-05-13_ZQR_CH360020620693823701D_CHF_WC9CEKBWFFG2XXQA__prtry.csv
0 rows

File structure

Notes: The provided data appears to be free-form text with no consistent delimiter or structure. Each line contains the same value 'A89', which does not resemble any PII pattern. Since there is no consistent columnar structure and no variation in line content, this is classified as unstructured data. No columns to map.

finanzen__zed_files__2026__2026-05-15_ZQR_CH360020620693823701D_CHF_WC9CEKBWG8V62K2A__id.csv
0 rows

File structure

Notes: free-form text with embedded banking references; no consistent column structure

finanzen__zed_files__2026__2026-05-18_ZQR_CH360020620693823701D_CHF_WC9CEKBWKASMLU6A__prtry.csv
0 rows

File structure

Notes: This appears to be free-form text with no consistent delimiter structure. The sample shows only three lines of text that appear to be codes or identifiers (A89 repeated three times) with no structured columns or headers. Since there is no consistent delimiter and no structured rows, this qualifies as unstructured data. No emails or phone numbers are visible in this sample, but the unstructured pattern suggests this might be part of a log or identifier file rather than PII-containing records.

finanzen__zed_files__2026__2026-05-19_ZQR_CH360020620693823701D_CHF_WC9CEKBWLAHW4K2A__prtry.csv
0 rows

File structure

Notes: The provided sample consists entirely of unstructured text lines ('cd', 'A89' repeated). No consistent delimiter or row structure exists. These appear to be fragmented or placeholder values with no identifiable PII patterns. Since there is no columnar structure and the data is not tabular, this qualifies as unstructured content per the rules.

finanzen__zed_files__2026__2026-05-20_ZQR_CH360020620693823701D_CHF_WC9CEKBWMDA2XEDA__id.csv
0 rows

File structure

Notes: This is unstructured data containing IBAN and potentially other financial identifiers. The file lacks consistent column structure (no shared delimiter, varying line shapes), and contains financial account information rather than personal PII fields. It does not conform to a CSV/TSV structure with named columns; instead it appears to be raw financial transaction lines or bank account data.

finanzen__zed_files__2026__2026-05-21_ZQR_CH360020620693823701D_CHF_WC9CEKBWNEEYZTHA__id.csv
0 rows

File structure

Notes: The provided text is not a structured CSV file with consistent columns. It appears to be a snippet of financial/banking data (likely IBAN information) without any identifiable personal information in a structured format. The lines shown do not contain any PII fields such as email, phone, name, address, etc. There is no header row, and the data does not conform to a typical tabular structure with repeated patterns across rows. Since there is no consistent column structure and no identifiable PII fields, this is classified as unstructured with no columns to map.

finanzen__zed_files__2026__2026-05-22_ZQR_CH360020620693823701D_CHF_WC9CEKBWPXP8F6MA__id.csv
0 rows

File structure

Notes: The provided data is not structured; it appears to be a mix of unstructured financial/banking information (IBAN, bank codes) without consistent column alignment or headers. There are no repeated column patterns or structured fields across the rows. While IBANs are sensitive data, they fall outside the defined PII fields and require unstructured extraction. No structured columns to map.

finanzen__zed_files__2026__2026-05-26_ZQR_CH360020620693823701D_CHF_WC9CEKBWTD3JNEYA__id.csv
0 rows

File structure

Notes: This is not a structured file with consistent columns; it appears to be unstructured financial/banking data fragments (IBAN lines with incomplete formatting). The sample shows isolated lines with IBAN-like patterns but no repeated columnar structure or headers. Per rules, unstructured files with embedded PII return empty columns object.

finanzen__zed_files__2026__2026-05-28_ZQR_CH360020620693823701D_CHF_WC9CEKBWV64WDRXA__id.csv
0 rows

File structure

Notes: The provided sample is not structured data but appears to be free-form text containing banking information (IBAN). There is no consistent delimiter or row structure across lines, and the content resembles unstructured financial/banking records rather than a delimited dataset with columns. No PII columns can be mapped from this unstructured format.

finanzen__zed_files__2026__2026-05-29_ZQR_CH360020620693823701D_CHF_WC9CEKBWX9DAWMJA__id.csv
0 rows

File structure

Notes: This is a free-form text file containing bank account information (IBANs and possibly other financial data). There is no consistent delimiter or structured column format. The sample shows IBAN values and what appears to be a bank code line, indicating unstructured financial data rather than a tabular dataset. No column mapping is possible.

finanzen__zed_files__2026__2026-06-01_ZQR_CH360020620693823701D_CHF_WC9CEKBW3EW5X7KA__id.csv
0 rows

File structure

Notes: free-form text with embedded financial identifiers (IBAN), no consistent column structure visible in the sample