cambridgemgmt.net

File structure

Notes: The file is a free-form text containing only zeros and placeholder paths. There is no consistent delimiter structure, and the content appears to be dummy data or placeholder paths with no actual PII. No emails, phones, or other PII are visible. This is not a CSV or any structured format with columns.

File structure

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

Notes: This is a chart of accounts document, not a dataset containing personal records. It lists financial GL codes, titles, and definitions for accounting purposes. No personal identifiers (PII) are present in this sample. The content is purely structural and financial — account numbers, titles, and definitions — with no employee names, addresses, or other personal data.

File structure

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

Notes: All columns are internal financial/accounting metrics (transaction counts, costs, fees). No PII fields present. Column 0 contains the company name repeatedly, which is excluded by the CompanyName rule. All other columns are numeric financial data (transaction counts, monetary values) that are explicitly excluded by the rules for financial/transactional data.

File structure

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

Notes: All columns represent internal financial and operational metrics (ACH/IRD transactions, costs, fees). No PII fields are present. Values are numeric/cost figures and fixed strings identifying the company. Columns matching patterns like 'Company', 'Business', or internal IDs are excluded per rules.

File structure

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

Notes: No PII columns detected. All columns represent financial metrics, transaction counts, and cost figures related to ACH and IRD processing. Column 0 contains a static company identifier, column 1 contains property names, and columns 2-19 contain numeric transaction and cost data. None of these contain personal identifiable information per the defined PII categories.

File structure

Notes: free-form text with no consistent delimiter structure; contains internal notes about utilities timing and accounting questions. Not a structured dataset with columns. Contains no visible emails or phone numbers in this snippet.

File structure

Notes: The provided text is free-form prose containing operational notes and accounting adjustments with no consistent column structure or delimiter. It does not represent structured tabular data with columns, and contains no visible emails or phone numbers in a structured format.

File structure

Notes: This is free-form text with no consistent delimiter structure. The sample consists of operational notes and accounting entries rather than structured tabular data with columns. While there are no visible emails or phone numbers in this specific snippet, the unstructured nature of the content means it should be processed through a streaming email/phone extractor rather than column mapping.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH/payroll file format. Bank routing/account numbers at [15-32] and [32-56] omitted (financial account data, not standard PII field). Record type indicators and sequence numbers classified as skip. No email, phone, DOB, SSN, or other PII fields present in this extract.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH file format (NACHA standard). Lines 1-2 are file/batch headers. Lines 3+ are detail records with employee names embedded. Bank routing/account numbers (columns 0-54) are financial data but not PII field types in the provided taxonomy; only firstName and lastName extracted as PII.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file format (NACHA standard). Record types 101/520/622/623/632 indicate bank/company/transaction headers and employee ACH entries. Only lastName and firstName are PII fields present in visible columns. Routing numbers, account numbers, and transaction amounts are present but not mapped as they are financial transaction data, not traditional PII fields. The file contains sensitive banking details for employee direct deposits.

File structure

Format: FIXED·Has header: no·Columns: 6

Notes: ACH payroll file format (NACHA standard). Record types 101, 520, 622, 623 indicate file headers and detail records with banking/payroll data. Only full names extracted as PII; routing/account numbers and transaction amounts treated as financial non-PII skip fields per breach context (payroll ACH processing data).

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file format (NACHA). Bank account/routing numbers present in columns [0-48] are internal banking details, not mapped as standard PII fields per schema. Employee names extracted from character positions 50-82. Columns before position 50 contain routing/account numbers and transaction codes (skip). Columns after position 82 contain sequence/reference numbers (skip).

File structure

Format: FIXED·Has header: no·Columns: 6

Notes: ACH payroll file (NACHA format). Bank routing/account numbers (columns 1-2) and transaction amounts/codes (column 3) are not PII fields per standard definitions. Employee names extracted from employee detail records (record type 622/623). Columns 0 and 5 contain record type codes and sequence numbers (skip).

File structure

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

Notes: All columns contain internal business/financial metrics (ACH/Lockbox volumes, costs, fees). No PII present — PMC column is a corporate identifier, Site Name is a property name, numeric columns are transactional counts and monetary values. This is a financial reporting file, not employee PII.

File structure

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

Notes: No PII columns detected. All columns are internal financial/transactional metrics (ACH/IRD costs, fees, site names, and originations/returns counts). The 'PMC' column contains a static company name and identifier, not personal data. No emails, names, addresses, or other PII are present.

File structure

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

Notes: All columns contain financial/transactional data (ACH/Lockbox originations, costs, fees), internal identifiers (PMC), and site names. No PII fields present — values are business metrics, numeric transaction counts, and cost figures. 'PMC' values are company identifiers, not personal names.

File structure

Notes: The provided text is unstructured operational notes and accounting instructions rather than a delimited dataset. It contains no consistent row structure or columns — instead it's a mix of accounting updates, GL spreadsheet instructions, and notes about utility invoice timing. There are no identifiable PII columns to map.

File structure

Notes: free-form text with no consistent delimiter structure; appears to be operational notes and memos rather than structured records

File structure

Notes: The provided content is free-form text containing operational notes, financial adjustments, and internal commentary. There is no consistent columnar structure, and the data appears to be prose-style notes rather than structured records with PII fields. No column mapping can be performed.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file format (NACHA standard). Bank routing/account numbers present at [6-24] and [24-54] but excluded as they are financial account data, not PII field types in the specified list. Employee names are the only PII fields matching the provided taxonomy. Record types (622/623/632/101/520) and sequence numbers are non-PII and skipped.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file (NACHA format). Lines 1-2 are file/batch headers. Lines 3+ are detail/debit entries (PPD records) containing employee names. Columns 0-49 contain routing numbers, account numbers, and transaction amounts (non-PII). Employee firstName and lastName are the only PII fields present in the detail records. No email, phone, DOB, SSN, or other PII are included in this extract.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH file format (NACHA). Lines 1-2 are batch headers. Lines 3+ contain employee detail records with routing/account numbers (columns 0-54, non-PII) followed by employee names (columns 54-84). No other PII fields (SSN, DOB, address, phone) present in data rows.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file format (NACHA standard). Bank account/routing numbers present in columns [0-52] are NOT extracted per instructions (only PII fields listed). Employee names appear in fixed positions within detail records (type 6 lines). No other PII fields (SSN, DOB, email, phone, address) are present in this extract.

File structure

Format: FIXED·Has header: no·Columns: 6

Notes: ACH payroll file from Cambridge Management Inc. Employee names extracted from fixed-width payroll detail records (type 622/623/632). Bank routing and account numbers redacted as financial infrastructure rather than direct PII per standard practices, though highly sensitive in breach context.

File structure

Format: FIXED·Has header: no·Columns: 6

Notes: ACH payroll file format (NACHA standard). Lines 1-2 are batch/file headers. Data lines 3+ contain employee names with banking routing/account numbers. First and last names are space-padded and separated at position 68. Only firstName and lastName are PII; banking details, routing numbers, and transaction amounts are excluded per instructions.

File structure

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

Notes: All columns contain financial/transactional data (ACH/Lockbox costs, originations, returns) and company/site identifiers. No PII fields present. The 'PMC' column contains the company name repeated, which is excluded per business/company rule. All other columns are numeric financial metrics or internal counters.

File structure

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

Notes: No PII columns present. All columns are financial/transactional metrics (ACH/IRD originations/returns/costs, fees) and organizational identifiers (PMC name, site names). No personal identifiers (names, emails, addresses, etc.) detected.

File structure

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

Notes: No PII columns present. All columns are internal financial/transactional data (company name, site name, ACH/IRD statistics, cost metrics). Values are business identifiers, numeric counters, and monetary amounts — none map to personal PII fields. "PMC" column contains only the company name repeated, not individual employee data.

File structure

Notes: The sample is free-form text with operational notes about financial transfers and account updates. No consistent delimiter structure exists across lines, and the content is entirely prose with no embedded PII columns. This qualifies as unstructured text requiring a streaming extractor.

File structure

Notes: This file contains free-form operational notes and accounting instructions without any consistent column structure. Each line represents a different property code (CHA, CH2, CHS, etc.) with narrative entries about financial adjustments, accruals, and transactions. There are no identifiable PII columns or structured data fields — only descriptive text. While the content references financial adjustments, it does not contain any personal identifiers like names, emails, or addresses.

File structure

Notes: This is unstructured operational notes/free-form text containing internal commentary, not structured data with columns. No consistent delimiter or column structure exists across the lines. Contains no identifiable PII columns.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file format (NACHA standard). Bank routing/account numbers in positions 0-54 are financial data but not classified as PII fields per schema. Employee names appear in positions 54-84. Remaining columns contain transaction amounts, record types, and sequence numbers (all non-PII).

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH file format (NACHA standard). Bank routing/account numbers at positions 4-21 are financial data but not PII per se. Employee names appear consistently at positions 51-81 across all transaction records. No email, phone, DOB, SSN, or address fields present in this extract.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file (NACHA format). Columns 0-53 contain routing/account numbers and transaction codes (non-PII). Employee names appear at positions 54-84. No other PII fields (email, phone, DOB, SSN, password) present in visible columns.

File structure

Notes: The provided sample consists of free-form text lines with no consistent delimiter structure. The lines contain banking and financial codes rather than human-readable PII fields. This matches the expected format of payroll ACH files containing bank account and routing numbers, which are typically unstructured. Since there is no column-based structure and no headers, this is classified as unstructured data. The values appear to be banking identifiers, not human PII like names, emails, or addresses.

File structure

Format: FIXED·Has header: no·Columns: 5

Notes: ACH payroll file format (NACHA standard). Records contain employee names extracted as fullName PII. Bank routing and account numbers present but treated as skip per instructions (financial transaction data, not personal identifier fields in the defined schema). No email, phone, DOB, SSN, address, or other listed PII fields detected in visible columns.

File structure

Format: FIXED·Has header: no·Columns: 6

Notes: ACH payroll file format (NACHA standard). PII extracted: employee first and last names. Routing numbers, account numbers, and transaction amounts are financial data but not traditional PII fields per schema. No DOB, SSN, phone, email, or address data present in fixed columns.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file (NACHA format). Columns contain employee names extracted from payroll records. Bank routing/account numbers and transaction amounts present but not PII fields per schema. No email, phone, DOB, SSN, or other PII types visible in fixed positions.

File structure

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

Notes: No PII columns identified. All columns contain company identifiers, transaction counts, and monetary values related to ACH/IRD processing fees. No names, addresses, emails, phone numbers, DOB, SSN, or other PII fields present.

File structure

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

Notes: All columns are internal financial/transactional metrics (ACH/IRD counts, costs, fees). No PII present. Columns contain company identifiers, site names (business locations), and monetary values — all excluded by rules.

File structure

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

Notes: All columns are financial/transactional metrics or company identifiers. No PII fields present. 'PMC' column contains company name prefix only, not individual names. All other columns are numeric financial figures or cost metrics.

File structure

Notes: This file is free-form text with no consistent delimiter structure. It appears to be a notes or commentary file with entries for different property codes (ALLPROPS, BEE, RCC, etc.), containing account numbers and status updates rather than tabular data. There are no repeated column patterns or structured rows.

File structure

Notes: free-form text with embedded emails / phones

File structure

Notes: The provided content is free-form text with notes and financial calculations rather than structured tabular data. There are no consistent columns or delimiters, and the text appears to be operational notes, calculations, and comments rather than a dataset with PII fields. Therefore, this is classified as unstructured text.

File structure

Notes: This is a free-form text file with operational notes and accounting discussions. No consistent column structure exists across lines. While it contains financial references, it does not contain structured PII fields in a columnar format. The content appears to be internal accounting notes rather than structured records with personal data.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file format. Bank routing/account numbers at [0-50] are financial data (not PII field type available). Sequential record IDs at [82-95] are internal identifiers (skip). Only name fields extracted as PII.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file format (NACHA standard). Bank routing numbers and account numbers appear in columns 0-50 but are not PII field types in the available schema. Name fields extracted from employee payroll records. Columns before position 50 contain routing/account data (skip); columns after position 80 contain sequence/batch numbers (skip).

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH file format (NACHA standard). Columns 0-53 contain routing/account numbers and transaction codes (non-PII). Employee names appear in detail records (transaction type 622/623). Banking details are present but not mapped as separate columns due to their integration within account number fields. Only clearly delimited name fields extracted as PII.

File structure

Format: FIXED·Has header: no·Columns: 7

Notes: ACH payroll file format (NACHA standard). Column 5 contains full names in 'LastName FirstName' format (e.g., 'Hinz Karie', 'Neill Andre'). No other PII fields present — bank routing/account numbers are internal financial identifiers used in context of ACH processing, not classified as standalone PII in this schema. All other columns are transaction metadata and sequence controls.

File structure

Format: FIXED·Has header: no·Columns: 6

Notes: ACH payroll file format. Columns 3-4 contain employee names (PII). All other columns contain routing numbers, account numbers, transaction IDs, and internal banking identifiers that are not mapped to standard PII field types but are highly sensitive financial data.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file (NACHA format). Routing numbers and account numbers present in columns [0-65] but not PII fields per schema. Employee names are the only PII fields present.

File structure

Notes: This is unstructured financial/ACH data with no column headers or consistent delimiter. It contains employee names (e.g., "Hinz Karie", "Mcclellan Trisha") but lacks any email, phone, or address fields. The format is a raw transaction dump, not a CSV. No PII columns to map.

File structure

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

Notes: No PII columns identified. All columns represent financial transaction metrics, costs, and fees related to ACH, IRD, and other operational metrics. No personal identifiable information such as names, emails, addresses, or other sensitive fields are present.

File structure

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

Notes: All columns are financial/transactional data or internal identifiers (e.g., ACH Originations, ACH Returns, costs, fees). No PII fields present. "PMC" column contains a company name and identifier, not personal names.

File structure

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

Notes: No PII columns present. All columns are financial/transactional metrics (ACH originations/returns, IRD costs, fees), internal business identifiers (PMC, Site Name), and operational counters. Values are numeric or static company names without any personal identifiers.

File structure

Notes: free-form text with embedded emails / phones

File structure

Notes: free-form text with embedded emails / phones

File structure

Notes: free-form text with no consistent delimiter or row structure; contains operational notes and financial adjustments rather than structured PII records

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file (NACHA format). Only lastName and firstName are PII fields present in this data. Bank routing/account numbers (positions 0-20 approx) are financial account data but not classified as PII field type in the available schema. Employee names extracted from positions 50-80 across all employee records.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file format (NACHA standard). Lines 1-2 are file/batch headers. Lines 3+ are detail records with employee names. Bank routing numbers (columns 3-11) and account numbers (columns 12-29) are present but excluded as they are financial account data, not PII field types in the specification. Employee names at positions 51-81 are the only PII fields matching available types.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file format (NACHA standard). Bank routing/account numbers visible in columns [24-48] are numeric identifiers (skip). Record type codes, amounts, and sequence numbers are non-PII. Only firstName and lastName extracted as PII per available field types. Employee names appear consistently in positions 54-82 across all detail records (622x lines).

File structure

Format: FIXED·Has header: no·Columns: 6

Notes: ACH payroll file format (NACHA standard). Contains banking information (routing/account numbers) alongside employee names. Only name fields extracted as PII; banking details flagged as skip per standard practice but context indicates high sensitivity.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file format. Columns 0-49 contain routing/account numbers and transaction data (skipped as non-PII). Positions 50-80 contain employee names. Bank account numbers (columns 15-32 approx) and routing numbers (columns 0-15 approx) are skipped per instructions—they are financial identifiers, not PII field types in the standard list. Only firstName and lastName extracted as PII.

File structure

Format: FIXED·Has header: no·Columns: 2

Notes: ACH payroll file format (NACHA standard). Lines 1-2 are file/batch headers. Lines 3+ are detail records (type 6) containing employee names. Bank routing/account numbers present in columns 0-50 but not PII field types. Sequence numbers in final columns are skip (internal record tracking).

File structure

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

Notes: All columns represent internal financial/transactional data (ACH/IRD origination/return counts and costs, fees), internal identifiers (PMC codes), and site names. No PII fields present. All columns are skipped per exclusion rules for company data, internal IDs, and financial/transactional metrics.

File structure

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

Notes: All columns are financial/transactional metrics or company identifiers (PMC, Site Name, ACH Originations/Returns, IRD metrics, costs, fees). No personal PII fields (names, emails, addresses, etc.) are present. 'PMC' is a company identifier, not an individual name. All columns are skipped per exclusion rules (company data, financial metrics, internal counters).

File structure

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

Notes: All columns contain financial/accounting data and internal codes (e.g., ACH/IRD transaction counts and costs). No PII fields detected. Columns like 'PMC' and 'Site Name' contain company names and property identifiers, not personal names. All values are numeric or represent internal business metrics.

File structure

Notes: free-form text with no consistent delimiter structure; appears to be operational notes/comments rather than structured records. Contains no repeated column patterns or PII fields in structured format.

File structure

Notes: The provided text is free-form notes/prose with no consistent columnar structure. It contains operational commentary and accounting instructions rather than tabular data with PII fields. No structured columns exist to map.

File structure

Notes: This is a free-form text file with operational notes and accounting codes. No consistent columnar structure exists — each line is a different message or note format. While there are no visible emails or phone numbers in this sample, the unstructured nature and lack of shared delimiters meet the unstructured opt-out criteria.

File structure

Notes: free-form text with embedded emails / phones

File structure

Notes: The file appears to be a financial report with row labels and financial sums rather than structured PII records. Columns contain account names and numeric financial data, not personal identifiers. No PII columns mapped.

File structure

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

Notes: This file is purely financial reporting with no PII present. All columns represent account labels and monetary sums across quarters, with no personal identifiers, names, or contact details. The data structure is strictly transactional and organizational, containing only property names, department categories, and financial totals.

File structure

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

Notes: This file contains financial data (management incentive fees) with no personal identifiable information (PII). Columns include ID, LOCATION, FEE TYPE, and various financial figures across months, but no names, addresses, emails, phone numbers, DOB, SSN, etc. All columns are financial/transactional and therefore mapped to 'skip' per exclusion rules.

File structure

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

Notes: No PII columns detected. The file contains only property IDs, maintenance fee data, and financial projections. No personal information such as names, addresses, or contact details appears in the first 50 rows.

File structure

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

Notes: This file contains financial data for management fees across apartment complexes. No PII fields are present in the first 50 rows. All columns either contain internal IDs, location names, or constant fee type values.

File structure

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

Notes: This is a financial report file showing property management revenue summaries across multiple properties and categories. Contains only business category names, property names, and financial totals — no personal identifiable information (PII) present. All columns represent internal accounting codes and monetary values, which are excluded by the skip rules.

File structure

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

Notes: This file contains only financial accounting data (property-level revenue summaries) with no personal identifiers. All columns represent property names, accounting categories, and monetary values. No PII fields (email, phone, name, address, etc.) are present in the first 50 rows.

File structure

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

Notes: The file is a financial report containing accounting data with no personal identifiable information (PII). All columns represent property names, accounting categories, and monetary sums across different time periods. No columns map to any PII fields such as email, phone, name, address, or date of birth. The data is purely transactional and organizational.

File structure

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

Notes: This is a financial report showing property management accounting summaries. All columns contain property names, accounting categories, and financial totals — no personal identifiable information (PII) present. No email addresses, phone numbers, names, addresses, or other PII fields are visible in the sample data.

File structure

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

Notes: The file is a financial report containing only accounting codes, property names, and numerical sums. No PII fields are present — all rows describe budget categories and monetary values for different apartment complexes.

File structure

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

Notes: No PII fields present. All columns represent internal accounting/financial data: IDs, location names, fee types, monetary values (monthly/yearly totals), and comments. No names, emails, addresses, or other personal identifiers appear in the sample.

File structure

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

Notes: This is a structured CSV file containing property management data with no PII fields. Columns include property names, affiliations, voucher counts, billing totals, and timestamps. No columns map to PII categories (email, phone, dob, names, addresses, etc.). All data appears to be property-level aggregates and operational metrics rather than individual resident or employee information.

File structure

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

Notes: This file contains only property names, billing statuses, and numerical values. No PII fields are present. All columns map to internal property management data and financial totals, which are excluded by the skip rules (company/business-related fields and financial/transactional data).

File structure

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

Notes: No PII fields detected. This appears to be a property management summary report showing property names, voucher status, and billing totals. All columns contain property identifiers, counts, and financial totals with no personal identifying information. The 'PD' value in column 7 appears to be a status flag rather than PII.

File structure

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

Notes: No PII columns detected. File contains property management data (property names, billing totals, dates) but no personal identifiers like names, emails, or addresses. All columns represent business operational data, not individual resident PII.

File structure

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

Notes: This is a structured CSV file containing property management data with property names, affiliations, and billing information. There are no personal identifiable information (PII) fields present in the visible columns. All columns relate to property names, affiliations, and financial totals, which do not contain any PII according to the provided field type definitions.

File structure

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

Notes: The file appears to be a financial report or property management summary containing property names, affiliations, and billing amounts. There are no identifiable personal information fields (PII) present in the first 50 rows. All columns contain property-related data, counts, and financial totals, none of which qualify as PII under the defined categories.

File structure

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

Notes: This is a financial/property management report with property names, billing amounts, and voucher counts. No PII fields are present in the sample rows — all columns are property identifiers, status flags, and numeric totals. No emails, names, addresses, or other personal data visible.

File structure

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

Notes: This file is a property management report with no PII fields. Columns contain property names, billing statuses, and numerical totals — all non-personal operational data. No emails, names, addresses, or other PII present in the first 50 rows.

File structure

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

Notes: This file contains property management data with property names, HUD affiliations, and billing information. No PII fields are present in the first 50 rows. All columns map to skip categories (company names, internal flags, financial/totals data).

File structure

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

Notes: This file contains only property names, affiliations, and financial totals — no PII fields. All columns map to internal property identifiers, billing status flags, and numeric totals. No names, addresses, emails, or other personal data appear in the first 50 rows.

File structure

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

Notes: This file contains property management data with no PII fields. Columns represent property names, affiliations, voucher counts, billing totals, and other operational metrics. No email addresses, phone numbers, names, dates of birth, or other PII are present.

File structure

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

Notes: No PII columns identified. The file contains property management data with property names, affiliations, and billing amounts. No personal identifiers (names, emails, addresses, etc.) are present in the first 50 rows.

File structure

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

Notes: This is a structured CSV file, but it contains no PII fields. The columns represent property names, requests, RFTA counts, and totals — all business metadata with no personal information. All rows are property-level aggregates, not individual records.

File structure

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

Notes: This file contains property management data with property names, HUD affiliations, and billing information. There are no PII fields present in the visible columns. All columns are property-related metadata and numerical totals, which do not contain personal identifiable information.

File structure

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

Notes: This is a structured CSV file with property management data. No PII fields are present. Columns contain property names, billing statuses, voucher counts, and financial totals. All values are property identifiers, counts, or monetary amounts with no personal identifying information. Timestamps present are system timestamps unrelated to individuals.

File structure

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

Notes: This file contains property management data with property names, affiliations, and billing information. No PII fields (names, addresses, emails, etc.) are present in the visible columns. All entries are property identifiers and numerical totals, which do not qualify as personally identifiable information under the defined field types.

File structure

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

Notes: This file contains property management data with no PII fields. All columns represent property names, affiliations, and billing figures. No personal identifiable information is present in the first 50 rows.