azazie.com
Jul 8, 2026
Database dump from Azazie, an online retailer specializing in bridesmaid dresses and formal wear. The archive contains a full SQL database export with approximately 2,576 data files totaling ~973 MB, including order/shipment records, admin users, access tokens, customer data, product pricing, and internal operational tables. The credit file attributes the leak to Telegram channel @weleakdatabases and actor @GuntherMagnuson.
Data found in this dataset
Source files
Expand any file to inspect its column headers and the LLM's field-mapping reasoning, recorded during ingestion.
Credit.txt12 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | firstName | high | [0] header 'first_name', values are common given names |
| 1 | lastName | high | [1] header 'last_name', values are common surnames |
| 2 | skip | high | [2] header 'email', values contain '@' symbols |
| 3 | skip | high | [3] header 'phone', values are 10-digit numbers |
| 4 | address1 | high | [4] header 'address1', values are street addresses |
| 5 | city | high | [5] header 'city', values are city names |
| 6 | state | high | [6] header 'state', values are US state abbreviations |
| 7 | zip | high | [7] header 'zip', values are 5-digit zip codes |
| 8 | skip | high | [8] header 'dob', values match YYYYMMDD date pattern |
| 9 | gender | high | [9] header 'gender', values are 'M'/'F' |
| 10 | password | high | [10] header 'password', values appear to be hashed passwords |
| 11 | username | high | [11] header 'username', values are alphanumeric usernames |
Notes: 12 columns total, 11 contain PII. The data appears to be customer account information from Azazie, including personal identifiers and login credentials. The password column likely contains hashed passwords.
azazie__B1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a shipment/order tracking file with only internal identifiers and operational flags. No personal customer data (PII) is present. All columns are internal IDs, timestamps, and status codes. shipment_id appears to be a constant placeholder value, dispatch_sn is a tracking code, CREATED_STAMP is a timestamp, is_process and goods_number are status counters, and abs_id is likely an internal reference number.
azazie__B2.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal shipment identifiers (abs_id, shipment_id, goods_number, dispatch_sn, erp_sku) with no personal or sensitive data. All columns are internal operational IDs and product SKUs, therefore no PII fields are present.
azazie__DATABASECHANGELOG.csv1 column531 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__DATABASECHANGELOGLOCK.csv0 rows
File structure
Notes: This file appears to be a raw SQL dump or database export rather than a delimited data file. The lines shown are SQL statements or database records ("ID,LOCKED,LOCKGRANTED,LOCKEDBY" with binary data). There is no consistent delimiter structure across rows, and the content represents internal database metadata (IDs, lock status) rather than customer PII. The format is unstructured and does not contain any extractable PII in a columnar format.
azazie__JJsow_out_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal operational/transactional fields: abs_id (internal ID), source_num (product/source code), facility_id (facility identifier), quantity, price, currency, order_sn (order number), create_stamp (timestamp), action_user (internal staff username), is_dispatch (flag). None map to personal PII fields.
azazie__MY_TABLE_to.csv1 column1,530 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__PROVIDER_PRICE.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal product/pricing data (provider IDs, goods IDs, prices, creation metadata). No PII fields present. Columns like CREATED_BY contain system usernames, not customer PII. This is a product catalog/pricing table from Azazie.
azazie__QRTZ_CRON_TRIGGERS.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only scheduler configuration data with no PII fields. All columns (sched_name, trigger_name, trigger_group, cron_expression, time_zone_id) are internal system identifiers and scheduling parameters — no personal information present.
azazie__QRTZ_JOB_DETAILS.csv3 rows
File structure
Notes: free-form text with embedded emails / phones
azazie__QRTZ_LOCKS.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a configuration or scheduler metadata file, not customer PII. Contains scheduler names and lock names with no personal data.
azazie__QRTZ_SCHEDULER_STATE.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a scheduler status log, not customer PII. Columns represent internal scheduler metadata (scheduler name, instance identifier, timestamps). No PII fields present.
azazie__QRTZ_TRIGGERS.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal scheduler metadata (triggers, job states, timestamps). No PII present. Columns are system identifiers, timestamps (non-DOB), and status flags — all explicitly skipped per rules. File appears to be Quartz scheduler configuration, not customer data.
azazie__README.csv24 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__SELECT___FROM_ecshop_ecs_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to contain internal identifiers, counters, flags, or placeholder values (e.g., '0', '1', 'N'). Columns like C3 contain image path patterns, and others are numeric constants or empty. No emails, names, addresses, phones, DOB, SSN, or passwords are present in the sample.
azazie__SELECT___FROM_ecshop_ecs_attribute_1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal IDs, counters, or flags (e.g., numeric constants, 'N' values). No PII fields detected. Likely an internal reference or inventory table unrelated to customer data.
azazie____dispatch_attribute_old_old.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The data appears to be product metadata with attribute names and values, URLs, and numeric IDs. All columns contain product-related information such as image URLs, style measurements, and attribute values, but no personal identifiable information (PII) is present.
azazie___dispatch_attribute_old.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The data appears to be product attribute records with image URLs, sizes, and style details. All columns contain product metadata, not personal information.
azazie___dispatch_location_history_new.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to contain only internal tracking IDs (dispatch_sn, order_id), creator usernames, timestamps, and status flags. All columns fall under exclusion rules for internal IDs, timestamps, or non-PII status indicators.
azazie___facility_location_old.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal inventory/location identifiers, timestamps, and capacity counters. No PII fields detected. Columns like LOCATION_SEQ_ID, FACILITY_ID, CREATED_STAMP, etc., are internal system identifiers and operational metadata, not personal data.
azazie___glc1_new.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All visible columns appear to be internal IDs, numeric codes, transaction amounts, and timestamps. No names, emails, phone numbers, addresses, or other PII fields are present in the sample.
azazie___supplier_dispatch_list_old.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, status flags, timestamps, product codes, and operational data. No customer names, emails, addresses, or other personal data appear in the first 50 rows.
azazie__a.csv1 column0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | gender | high | [1] column name 'sex', values '男' (Chinese for male) indicate gender |
Notes: Only one PII column present: gender. The 'id' column is an internal identifier and should be skipped.
azazie__a_copy.csv1 column0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | gender | high | [1] header 'sex', values '女'/'男' map to gender |
Notes: Only two columns present: id (internal ID, skip) and sex (gender). No other PII fields in sample.
azazie__abnormal_order_memo.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a memo table with operational notes, not customer PII. Columns contain internal IDs, order references, and timestamps. No PII fields are present.
azazie__abnormal_order_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal tracking IDs, status flags, timestamps, and JSON order details. No PII fields (email, phone, name, address, DOB, SSN, etc.) are present in this structured dataset.
azazie__abnormal_order_monitor_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only operational monitoring rules and status tracking. Columns represent internal workflow identifiers (id), status flags (monitor_key), container references (container_id), configuration JSON blobs (run_config), user identifiers (action_user), and timestamps (create_time, last_update_time). No PII fields are present. All columns are system metadata and internal IDs per exclusion rules.
azazie__abnormal_order_monitor_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a structured order/fulfillment log containing only order IDs, timestamps, and product details. No personal information (names, emails, addresses, etc.) is present in the visible columns.
azazie__abnormal_picking_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, product SKUs, shipment tracking codes, timestamps, and status flags. No PII fields present. Columns like create_user/update_user contain internal system usernames, not customer identifiers. Timestamps (create_time/update_time) and status codes are operational metadata, not personal data.
azazie__abnormal_picking_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal shipment identifiers, barcodes, location sequences, status codes, user IDs, and timestamps. No personal data such as names, emails, addresses, or contact details is present in the first 50 rows.
azazie__access_tokens.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the provided rows. The data appears to be authentication tokens (likely hashed/encoded) with numeric user identifiers and timestamps. None of the columns contain email addresses, phone numbers, names, addresses, dates of birth, SSNs, passwords, usernames, or other PII fields. The token column contains opaque strings that do not resemble email addresses or other searchable identifiers.
azazie__accessories_sale_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional/operational data with no PII fields. Columns represent internal IDs, product references, pricing, party names (which are business entities), and timestamps. All columns are excluded by the rules for company/business names and internal IDs/timestamps.
azazie__accessories_sale_price_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and product references with no PII. Columns are abs_id, external_goods_id, product_id, and party_id — all internal identifiers or product IDs, no personal data present.
azazie__accounting_dissent.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, flags, transaction amounts, or JSON audit data — no PII fields present. Columns like dissent_sn, batch_sn, external_goods_id are internal reference codes; audit_time, create_time, last_update_time are timestamps; action_user is an internal username; account_types and is_finished are flags; order_price and supplier_target_price are transactional amounts; dissent_status, start_status, reject_reason are status codes; audit_data is JSON blob without PII; provider_id is an internal identifier. No PII fields detected.
azazie__action_data_log.csv1 column153 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 8 | username | high | [8] header 'username', values appear to be alphanumeric usernames |
Notes: All other columns are internal database tracking fields (log IDs, timestamps, operation types, table names, etc.) and do not contain PII. The 'username' column maps to the username field as it contains user identifiers.
azazie__active_rule_parameters.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File appears to be configuration rules for a code linter or static analysis tool. All columns contain technical parameters, regex patterns, and thresholds for code quality checks, with no personal or identifiable data fields.
azazie__active_rules.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, numeric codes, timestamps, and status flags. No personal data such as names, emails, phone numbers, addresses, or DOB present in the first 50 rows.
azazie__admin_action_product_line.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction identifiers and timestamps. No PII fields present. Columns: aapl_id (internal ID), created_stamp (timestamp), last_update_stamp (timestamp), cat_id (internal category ID), action_code (transaction type), is_delete (flag). All columns are non-PII per exclusion rules.
azazie__admin_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an administrative log file tracking role and permission changes. Columns contain internal user IDs, log messages in Chinese, usernames (non-PII as they are internal system accounts), IP addresses, and timestamps. No PII fields (emails, phones, names, addresses, etc.) are present. All columns map to skip categories: user_id (internal ID), log_info (descriptive messages), ip_address (network identifier), created_at/updated_at (timestamps).
azazie__admin_menu.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. File contains menu/permission structure data with IDs, titles, icons, URIs, and timestamps. All columns are internal system identifiers or non-personal metadata.
azazie__admin_operation_log.csv4 columns19,705 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | high | [3] values consistently 'TPTE' which appears to be a username/handle rather than a true name, but mapped as fullName due to admin user context |
| 4 | password | high | [4] contains hashed password strings like '$2y$10$3FnE6tj\/5XLGZXGhJKu.o.SCYRZmO4w66g6fMXeK4\/WSLAUGqpOua' |
| 5 | ip | high | [5] contains IPv4 address values like '192.168.3.40', '127.0.0.1' |
| 6 | username | high | [6] contains JSON structures with '_pjax' and other tokens, interpreted as user session data |
Notes: File appears to be admin access logs rather than customer PII. Contains system IPs, hashed passwords, and session tokens. Only maps fields with clear PII patterns despite limited visible personal data.
azazie__admin_permissions.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an access control / permissions configuration file, not customer data. All columns represent system roles, endpoints, and timestamps. No PII is present.
azazie__admin_role_menu.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only role_id, menu_id, created_at, and updated_at columns. All columns are internal identifiers, timestamps, or flags and contain no PII. No email, phone, name, address, DOB, SSN, password, or username data is present. The values are purely numeric IDs and empty strings for timestamps.
azazie__admin_role_permissions.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only role and permission mappings with timestamps. All columns are internal system identifiers and timestamps, none contain PII. No email, name, address, or other personal data is present in the first 50 rows.
azazie__admin_role_users.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only role and user identifiers, timestamps, and internal IDs. No PII is present. Columns: role_id (internal role identifier), user_id (internal user identifier), created_at (timestamp), updated_at (timestamp). All columns are non-PII per exclusion rules.
azazie__admin_roles.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns appear to be internal identifiers, names, slugs, and timestamps. No PII fields (email, phone, DOB, etc.) are present in the first 50 rows. The 'name' column contains role names like 'Administrator' and '工厂' (factory), not personal names. Timestamps are internal dates and not DOB. Therefore, no PII columns to map.
azazie__admin_user.csv3 columns13 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | username | high | [4] header 'user_name', values are alphanumeric usernames |
| 6 | high | [6] header 'email', contains valid email address | |
| 7 | password | high | [7] header 'password', contains hash values |
Notes: Only 3 PII columns present: username, email, and password. All other columns are internal IDs, timestamps, IP addresses, or non-PII flags and should be skipped per rules.
azazie__admin_user_permissions.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present. The columns 'user_id' and 'permission_id' are internal identifiers, and 'created_at' and 'updated_at' are timestamps which must be skipped per rules.
azazie__admin_users.csv3 columns28 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | username | high | header 'username', values are alphanumeric strings |
| 2 | password | high | header 'password', values are hashed strings |
| 3 | fullName | high | header 'name', values are single words or alphanumeric strings |
Notes: CSV file with 7 columns, 3 contain PII: username, password, and fullName. Passwords are hashed but still considered PII.
azazie__affiliate_transactions.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction identifiers and operational data. No PII fields are present. Columns include internal IDs (at_id, au_id, order_id), order reference numbers (order_sn), transaction details (commission_detail, transaction_operation, transaction_type), monetary values (transaction_amount, transaction_balance), and timestamps (transaction_time). All columns are non-PII per exclusion rules.
azazie__affiliate_users.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, coupon codes, and timestamps. No PII fields are present. Columns: au_id (internal ID), user_id (internal ID), coupon_code (internal code), commission (financial value), sale_amount (financial value), create_time (timestamp), last_update_time (timestamp). All columns are marked as skip per exclusion rules.
azazie__alibaba_purchase_account.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all visible columns are internal IDs, system tokens, usernames, and timestamps. No PII fields (email, phone, name, address, DOB, SSN, etc.) are present in the first 50 rows. The column 'account_name' contains what appears to be a company or business name ('波罗鲉网络科技') rather than a personal name, and is therefore skipped per the exclusion rules for company/business-related fields. All other columns are internal IDs, tokens, timestamps, or system users — none qualify as PII under the defined field types.
azazie__alibaba_purchase_children_account.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be an internal account hierarchy table with no PII. Columns contain account relationships (parent/child names), action users, and timestamps. All values are internal identifiers or generic names (e.g., '孔子', '孟子') that do not constitute personal identifiable information per our definitions. No emails, phones, addresses, or other PII fields present.
azazie__alibaba_purchase_logistics_in.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction/operational identifiers and timestamps. No PII columns are present. All columns are internal IDs, counters, and timestamps which must be skipped per exclusion rules.
azazie__alibaba_purchase_order_info.csv4 columns4,845 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | high | header "seller_contact_name" resolves to PII field "fullName" |
| 12 | address1 | high | header "address" resolves to PII field "address1" |
| 13 | zip | high | header "zip" resolves to PII field "zip" |
| 14 | phone | high | header "mobile" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__alibaba_purchase_order_info_raw.csv1 column1,306 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | emailText | high | free-text column with embedded emails (39/175 cells, 22% density) |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__alibaba_purchase_order_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII fields detected in this structured data. The file appears to be an internal transactional or logging table containing only internal IDs (abs_id, id), batch IDs, usernames (non-PII as they are internal system users), timestamps, and status flags. No personal information such as names, emails, addresses, or other PII is present in the visible data.
azazie__alibaba_purchase_order_shipping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a structured CSV containing logistics/shipping records. However, none of the columns map to PII fields as defined in the rules. Columns such as logistics_company_no, logistics_company_name, logistics_bill_no, status, action_user, create_at, and update_at are all internal operational/tracking fields or timestamps, which are explicitly excluded by the rules. No PII data is present in this dataset.
azazie__allocate_delivery_country_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, flags, or numeric codes. No PII present. Columns like 'id', 'country_id', 'shipping_id', 'facility_id', 'sm_id', 'price_group_name', 'box_ids', 'weight', 'is_deleted', 'created_time', 'created_user', 'last_updated_time', and 'last_updated_user' are all internal system identifiers, operational flags, or timestamps — none contain personal or identifiable information. This matches the expected schema for an internal order/shipment table in an e-commerce database.
azazie__allocate_delivery_prior_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only rule definitions for logistics allocation with no personal customer data.
azazie__allocate_delivery_prior_rule_new.csv1 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__allocate_delivery_result.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the first 50 rows. The file contains only order/shipping identifiers, courier service names, allocation comments, user initials, and timestamps. All columns are internal operational data with no personal information.
azazie__allocate_provider_candidate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file but contains only three columns: dispatch_list_id, order_id, and external_goods_id. None of these columns map to PII fields. dispatch_list_id and order_id are internal IDs, while external_goods_id appears to be a product or inventory identifier. No personal information is present in the first 50 rows.
azazie__allocate_provider_limit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal provider identifiers and quantity data. No PII fields are present. All columns are internal operational data and must be skipped according to exclusion rules.
azazie__allocate_provider_result.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible columns contain internal system identifiers, transaction statuses, numeric values, and timestamps — none map to personal data categories (names, emails, addresses, etc.). The data appears to be purely operational/transactional logs for order allocation and supplier management.
azazie__alteration_refund.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, transaction metadata, timestamps, or status flags. No PII fields present. Columns like 'user_id' are internal numeric identifiers (not usernames), and 'create_time' is a timestamp. 'refund_apply_id' and 'order_sn' are internal reference numbers. No emails, names, addresses, phones, or other PII detected.
azazie__alteration_refund_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transactional IDs and quantities (refund_detail_id, refund_apply_id, quantity, goods_id, oiid). No PII fields are present. All columns are internal identifiers or counters and are mapped to 'skip' per exclusion rules.
azazie__analyze_order_delivery.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order/shipment identifiers and flags. All columns map to internal IDs, business codes, or status flags. No PII fields are present.
azazie__api_log.csv613 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__app_config.csv1 column1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | high | [6] header 'erp_group_email', value 'tech@i9i8.com' is clearly an email address |
Notes: Only column 6 contains PII (email). All other columns are internal system flags, IDs, or configuration settings and do not contain any personally identifiable information. The file appears to be system configuration or operational settings rather than customer data.
azazie__app_registration_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and timestamps. Columns: id (numeric internal ID), user_id (numeric internal ID), device_id (internal UUID), type (login/register flag), create_time (timestamp). No PII fields present. All columns are excluded per rules: user_id/account_id are internal IDs, device_id is an internal UUID, create_time is a timestamp, and type is a status flag.
azazie__app_safari_view.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only IP addresses, device types, OS versions, and timestamps. No PII fields are present. Columns map to skip categories (ip_address, internal flags, timestamps).
azazie__apply_action_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only operational metadata (IDs, actions, timestamps) with no PII. All columns map to skip categories: internal IDs (apply_id), action tracking (ope_name, action_name, action_type), free-text content field, and timestamps. No personal data is present.
azazie__aqua_shipping_data.csv1 column116 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 7 | username | high | [7] column 'updated_by', values are usernames (alphanumeric with dots) |
Notes: Only column 7 (updated_by) contains PII (username). All other columns contain order IDs, status codes, quantities, and timestamps — no personal data. The values in column 7 are clearly usernames used for audit trails.
azazie__area_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a pure geographic/region reference table with only administrative region codes and names. No PII fields present.
azazie__assign_cat_map_cat.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product/category table with no PII. Columns contain category IDs, names in English/Chinese, validity flags, action users (internal usernames), and timestamps. No email, phone, address, name, DOB, SSN, password, or other PII fields present. Action users like 'jjwang' are internal system accounts, not customer usernames.
azazie__assign_cat_map_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal product/category metadata with no PII fields. Columns include IDs, category names in English and Chinese, validity flags, user identifiers (non-unique internal handles), and timestamps — all non-PII per exclusion rules. No emails, names, addresses, or other personal data present.
azazie__attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product attributes (e.g., silhouette types, dress styles). No PII fields present. Columns like attr_id, parent_id, sort_order, timestamps, and flags contain only internal database identifiers and operational metadata. No emails, names, addresses, or other personal data.
azazie__attribute_languages.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. File appears to be a product attribute reference table containing dress design specifications (silhouette types, neckline styles, fabric types, etc.). All columns contain product metadata rather than customer or personal information.
azazie__attribute_review.csv5 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | skip | high | [3] column 'attr_name' contains non-PII values like 'Color' |
| 4 | skip | high | [4] column 'attr_value' contains non-PII values like 'Ivory', 'White' |
| 5 | skip | high | [5] column 'is_delete' contains non-PII values like '0' |
| 6 | skip | high | [6] column 'data' contains JSON blobs, not direct PII |
| 7 | skip | high | [7] column 'last_update_time' contains timestamps |
Notes: This appears to be a product attribute table for wedding dress colors. While customer names appear within JSON review data, these are embedded within a data structure and not direct column values. No direct PII fields map to columns.
azazie__auto_adjust_finance_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a structured CSV but contains only operational/transactional fields (order IDs, timestamps, status codes). No PII is present in the visible columns. All values appear to be internal reference numbers, numeric order IDs, timestamps, and status flags.
azazie__auto_confirm_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a structured data export containing order metadata and validation flags, but no personal identifiers such as names, emails, addresses, or phone numbers are present in the visible columns. All fields appear to be internal order references, status flags, and system-generated validation results.
azazie__auto_confirm_order_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The provided data is not structured with identifiable column headers. Each line appears to be a single descriptive string indicating order validation criteria, not a row of delimited fields. There are no repeating patterns of PII values (emails, phone numbers, names, etc.) visible in this sample, and the content describes address verification rules rather than containing actual personal data. Therefore, no columns can be mapped to PII fields.
azazie__auto_delivery_candidate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is not a PII-containing file. It only contains an order_id column which is an internal identifier and should be skipped. No personal information is present in the first 50 rows.
azazie__auto_dispatch_cat_size.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product catalog file with no PII. Columns are abs_id (internal ID), cat_id (category ID), cat_name (category name), and max_size (max quantity). All columns are non-PII per exclusion rules.
azazie__auto_exec_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only operational metadata (IDs, action types, timestamps, user handles) with no identifiable personal information. All columns represent internal system tracking rather than customer PII. The 'action_user' field contains short alphanumeric handles that appear to be system accounts rather than actual user identifiers.
azazie__auto_lunar_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, numeric counters, and timestamps. The file appears to be an internal analytics or inventory table from Azazie with no personal customer data.
azazie__auto_replenishment_result.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. The file appears to be operational logs tracking purchase order creation and inventory replenishment status, containing only internal transaction IDs, timestamps, and status flags. No personal data (names, emails, addresses, etc.) is present in the visible columns.
azazie__auto_ship.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (action tracking) with no PII. Columns are: abs_id (internal ID), exec_action (action type), order_id (internal order ID), state (status), action_user (system user), create_time (timestamp), last_update_time (timestamp). All columns are non-PII per exclusion rules (internal IDs, timestamps, flags).
azazie__auto_sync_JJS_France_order_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a log file containing internal operational messages and shipment IDs. No PII fields are present. Columns are: abs_id (internal ID), shipment_id (internal ID), operation_date (timestamp), memo (log message). All columns are non-PII per exclusion rules.
azazie__auto_sync_jjs_bird_order_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal operational/logistics data: abs_id (internal ID), shipment_id (internal ID), operation_date (timestamp), memo (Chinese-language shipment sync log messages), facility_id (internal ID), facility_name (warehouse name), shipment_extend (internal ID duplicate). No names, emails, phones, addresses, or other personal identifiers found.
azazie__auto_task_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns identified. File appears to be a dispatch/allocation log containing only internal IDs (abs_id), timestamps (create_time), function codes (func), and numeric keys (key_word). No personal information present.
azazie__auto_tmp_al_apa_sale_info_20210303.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal IDs and numeric counters — no PII fields present. All columns represent auto-incrementing identifiers, flags, and timestamps which must be skipped per exclusion rules.
azazie__auto_tmp_assign_list_20210309.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal order identifiers, product codes, timestamps, and operational flags. No names, addresses, emails, phone numbers, or other PII fields present in the first 50 rows.
azazie__auto_tmp_assign_list_20210309_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, product codes, timestamps, and operational data. No personal information such as names, emails, phone numbers, or addresses is present in the first 50 rows.
azazie__auto_tmp_bsc_20200813.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal shipment identifiers and timestamps. No PII fields are present. All columns are internal IDs, barcodes, or timestamps, which are excluded per rules.
azazie__auto_tmp_dispatch_due_date_07_20210206.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, or system fields. 'action_user' appears to be a username but follows exclusion rules for internal identifiers (likely system-generated or role-based). The breach context indicates this is an operational table, not customer data.
azazie__auto_tmp_dispatch_due_date_09_20210206.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, or operational flags. No PII fields detected. Columns like 'action_user' contain system usernames, not customer PII. Timestamps and IDs are non-sensitive operational metadata.
azazie__auto_tmp_dispatch_due_date_20210206.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, or system fields. No PII present. Columns like 'action_user' contain usernames but these appear to be system/internal users (e.g., 'maggie.shi', 'canola.ge') rather than customer identifiers. Timestamps and IDs are excluded per rules.
azazie__auto_tmp_dispatch_list_07_20210206.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII fields. All columns represent internal order/shipment identifiers, timestamps, product codes, pricing, and dispatch logistics — no personal customer data is present in this dataset.
azazie__auto_tmp_dispatch_list_09_20210206.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns are internal IDs, timestamps, transaction metadata, product identifiers, or status flags. No names, emails, addresses, or other personal data present in the sample.
azazie__auto_tmp_dispatch_list_20210206.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain order/shipping/tracking identifiers, product details, timestamps, and internal system IDs. No PII fields (email, phone, name, address, DOB, SSN, etc.) are present. The data appears to be purely transactional and operational.
azazie__auto_tmp_pp_sales_20201204.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal inventory identifiers, product codes, timestamps, and operational flags. No PII fields (email, phone, name, address, DOB, SSN, etc.) are present. Columns like 'id', 'inventory_item_detail_id', 'container_id', 'uniq_sku', 'product_id', 'external_goods_id', 'short_goods_name', 'quantity_on_hand_diff', 'color', 'size', 'unit', 'is_unit', 'unit_num', 'container_name', 'last_update_time', and 'create_time' are all internal business data and do not contain personally identifiable information.
azazie__auto_tmp_sample_sync_err_20210128.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. Columns appear to be internal identifiers (dispatch_sn) and timestamps (last_update_time, create_time). Values are alphanumeric codes and empty timestamps, typical for operational/internal tracking records.
azazie__auto_tmp_test_20210331.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory and stock management data with no PII fields. All columns represent internal IDs, stock quantities, timestamps, and status codes. No personal information is present.
azazie__auto_tmp_tmp_lunar_data_20210302.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and timestamps. No PII fields are present. Columns map to internal IDs, lunar dates, year counts, and auto timestamps — all skip per exclusion rules.
azazie__auto_tmp_to_fix_20200813.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All 11 columns are internal operational/inventory data: IDs, quantities, order/product/container references, shipping status flags, and timestamps. No PII fields present.
azazie__auto_tmp_to_fix_20200814.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory/transaction data with no PII fields. All columns are internal IDs, quantities, timestamps, or product references — none map to any PII categories. No emails, names, addresses, or other personal data present.
azazie__auto_unique_key.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an unstructured file containing only internal IDs and counters. No PII fields are present. The data appears to be internal database identifiers and counters from Azazie, with no personal or sensitive information exposed in these rows.
azazie__az_D30_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, flags, counters, or timestamps. Example values: abs_id (numeric IDs), return_type (category), statistics_year (2017), action_user (cronJob), create_time (ISO timestamps).
azazie__az_abnormal_order_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This is an internal inventory/transfer operations table containing order IDs, shipment IDs, batch/container IDs, quantities, internal action usernames, and timestamps. The 'action_user' column contains internal system/employee usernames (not customer-facing), which are operational identifiers in this context rather than customer PII.
azazie__az_adjust_delivery_date_near_year.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an operational/production configuration file, not customer PII. All columns contain system timestamps, configuration settings, and internal identifiers. No personal data fields (email, phone, names, etc.) are present. Columns like 'id', 'type', 'cat_name', and JSON config blobs are internal system metadata.
azazie__az_ads_cost.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal operational data with no PII. Columns include IDs, dates, categories, costs, channels, and timestamps. No columns map to PII fields.
azazie__az_aging_rate_day.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal IDs, timestamps, numeric counters, or location codes (country IDs and names). No email, phone, name, address, DOB, SSN, or other personal identifiers are present.
azazie__az_aging_rate_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns are internal IDs, order references, timestamps, shipping details, or company-related data. No personal information such as names, emails, addresses, or dates of birth is present.
azazie__az_aging_rate_month.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal operational metrics, timestamps, and identifiers (e.g., IDs, counts, rates, times). No email, phone, name, address, DOB, SSN, or other PII fields present.
azazie__az_assign_provider_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order metadata and system identifiers (id, provider_id, size_type, order_type, rush_type, provider_type, action_user, timestamps). No PII fields are present. Columns like action_user contain only system usernames (e.g., test108, hyhuang1, yzhang14) and are not mapped to username because they are internal system identifiers, not public-facing user identifiers. Timestamps and numeric IDs are excluded per rules.
azazie__az_auto_activity_holiday_replenishment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, flags, timestamps, or operational codes. The 'action_user' column contains usernames, but these are internal system accounts, not customer PII. Timestamps and numeric codes are not PII.
azazie__az_auto_batch_replenishment_plan_execute_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file is not structured data but rather a log of database operations. It contains no columns or PII fields. The entries are JSON strings describing product categories and inventory management configurations, not personal information.
azazie__az_auto_batch_replenishment_plan_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal system identifiers, configuration data, and timestamps. No PII is present — 'action_user' contains system/service account names, not customer usernames or personal identifiers. 'title' and 'config' hold product/sku codes and JSON configuration blobs, not human names or addresses. All columns are excluded by exclusion rules (internal IDs, company/product data, timestamps).
azazie__az_base_refund_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, transaction references, and timestamps. No PII fields are present.
azazie__az_base_return_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, transactional data, timestamps, or static flags. No PII fields are present. Columns like user_id are internal numeric identifiers, not usernames. ship_date is a timestamp, return_type is a static string, and others are order/shipment references.
azazie__az_batch_daily_shipping_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (product SKUs, dates, timestamps) with no PII fields. All columns map to internal IDs, timestamps, or counters which must be skipped per rules.
azazie__az_batch_delivery.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, batch/serial numbers, and timestamps. No PII fields are present. All columns are flagged for skipping per exclusion rules (internal IDs and timestamps).
azazie__az_batch_delivery_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and timestamps. No PII fields present. Columns: abs_id (internal ID), batch_sn (batch serial), order_sn (order serial), deliver_number (delivery counter), deliver_user (delivery user code), create_time (timestamp), last_update_time (timestamp). All columns are non-PII per exclusion rules.
azazie__az_batch_inventory_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal inventory and operational data (stock levels, timestamps, IDs). No PII fields detected. Columns like abs_id, external_goods_id, and timestamps are internal identifiers or operational dates, which must be skipped per exclusion rules.
azazie__az_batch_label.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a structured CSV but contains no PII fields. All columns (id, cat_no, batch_part_remark, is_delete, created_time, rn, updated_time) contain internal identifiers, timestamps, flags, or unstructured remarks with material compositions and internal codes. No emails, names, addresses, phone numbers, dates of birth, SSNs, passwords, usernames, or gender indicators are present.
azazie__az_batch_lend.csv2 columns791 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | state | high | header "state" resolves to PII field "state" |
| 10 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__az_batch_operation_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal tracking IDs, transaction flags, timestamps, and operational codes. No PII fields are present in this file.
azazie__az_batch_purchase.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, flags, or operational tracking fields (batch_id, batch_sn, check_status, check_user, check_time, print_num, shipping_fee, action_user, party_id, create_time, last_update_time, factory_status, produce_type, confirm_produce_time, track_evidence_file_path, track_evidence_upload_time, prepare_status, finish_prepare_time, prepare_return_reason, receipt_status, material_prepare_status, finish_material_prepare_time, withdraw_reason, template_reason, materials_reason, old_batch_sn, return_num, status, snapshot, unshipped_repair_batch_id, tracer_staff, buyer_staff, expect_return_time, actual_return_time, send_last_time, tracer_report_remark, feed_back_file_path, provider_id, origin_provider_id, is_auto_assign). None contain personal or sensitive data.
azazie__az_batch_purchase_action_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a log of database actions rather than a structured dataset containing PII. Columns contain action timestamps, user identifiers, log messages, and action types. No identifiable PII fields (names, emails, addresses, etc.) are present in the header or sample values. The content consists of system actions and purchase order references rather than personal customer data.
azazie__az_batch_purchase_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional metadata (purchase attributes) with internal IDs, order numbers, and amounts. No PII fields are present. Columns map to internal system codes, order identifiers, and monetary values — all excluded by rules (company/business references, financial/transactional data, and internal IDs).
azazie__az_batch_purchase_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal operational fields (batch IDs, timestamps, status codes, numeric counters). No PII fields detected. Columns like 'action_user' contain internal system usernames, not customer identifiers. Timestamps and status flags are non-PII operational data.
azazie__az_batch_purchase_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal configuration/purchase type records with no PII fields. Columns include config_id (internal ID), purchaser_type (category code), purchaser (descriptive text or test data), percent (numeric value), and audit fields (create_user, create_time, update_user, update_time). No email, phone, name, address, or other PII is present. All columns are marked as skip per rules (company/business references, internal IDs, timestamps).
azazie__az_batch_purchase_config_record.csv2 columns60 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | high | [3] values are full names like "vicki.zhou", "Kucan", "jacky.hu,jacky" |
| 4 | fullName | high | [4] values are full names like "vicki.zhou,leopard", "jacky.hu,jacky,owen.li" |
Notes: This file appears to be a purchase log with purchaser names embedded in columns 3 and 4. No other PII fields detected. All other columns are internal IDs, percentages, counts, and dates which are excluded by rules.
azazie__az_batch_purchase_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The provided rows contain only internal transactional identifiers (abs_id, batch_id, purchase_id), user initials (action_user), and timestamps (create_time, last_update_time). None of these fields represent identifiable personal information (PII) according to the defined categories. All columns are operational metadata used for system tracking and do not contain names, contact details, or other protected data types.
azazie__az_batch_purchase_mapping_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with 211 rows and 7 columns. The columns represent internal transaction identifiers and timestamps, with no PII fields present. All columns map to internal IDs, batch identifiers, user references, and timestamps, which are explicitly excluded per the rules. No email addresses, phone numbers, names, addresses, dates of birth, SSNs, passwords, usernames, or other PII are detectable in the header or sample values.
azazie__az_batch_purchase_order_material.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, product metadata, timestamps, or flags. No PII fields present. 'action_user' appears to be internal system usernames (alphanumeric handles), not customer-facing usernames.
azazie__az_batch_reference_pricing.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, inventory tracking codes, pricing information, timestamps, and system users — none contain personal identifiable information. This appears to be an inventory management table from the Azazie database.
azazie__az_batch_replenishment_plan.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, or flags (id, party_id, cat_codes, top, top_sort, is_delete, state, batch_id, config, action_user, remark, create_time, last_update_time). No PII fields present.
azazie__az_batch_replenishment_plan_batch_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only numeric identifiers and timestamps with no PII fields. All columns represent internal database IDs (abs_id, plan_id, batch_id) and timestamp fields (create_time, last_update_time) which are excluded per rules. No personal information is present in the first 50 rows.
azazie__az_batch_replenishment_plan_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to contain only internal operational data (IDs, timestamps, notes, and user actions) with no personal information. All columns are mapped to skip per exclusion rules (internal IDs, timestamps, notes, action_user).
azazie__az_batch_replenishment_plan_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain internal product IDs, inventory metrics, timestamps, configuration data, and status flags. No personal identifiable information such as names, emails, addresses, or phone numbers present in the sample.
azazie__az_batch_replenishment_plan_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File appears to be product configuration data containing internal IDs, color codes, sale dates, and JSON structures of color mappings. All columns are internal identifiers, timestamps, or product attributes with no personal information.
azazie__az_batch_sale_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal product/sales identifiers, timestamps, and counters. No PII present. Columns like id, date_us, sale metrics, and timestamps are internal operational data only.
azazie__az_batch_sale_style_heat.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal identifiers, timestamps, product attributes, or flags. This is consistent with product/order data from an e-commerce retailer.
azazie__az_batch_sale_style_heat_ext.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a product catalog or inventory dump containing dress color codes, descriptions, and timestamps. There are no personal identifiable information (PII) fields such as names, emails, phone numbers, addresses, or other sensitive data in the visible columns. All columns appear to be related to product attributes (external_goods_id, goods_color, hot_cat_extra_attr) and timestamps (created_time, updated_time), none of which qualify as PII under the provided field types. The JSON-like strings in the hot_cat_extra_attr column contain design notes and material descriptions rather than user data.
azazie__az_batch_supplier.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but ALL columns appear to be internal identifiers, timestamps, or non-PII metadata. The values are numeric IDs, user handles (not usernames), and ISO timestamps. No PII fields (email, phone, name, address, etc.) are present in the first 50 rows. Columns are skipped per rules: 'action_user' contains internal user handles, 'create_time' and 'last_update_time' are timestamps, and ID columns are internal identifiers.
azazie__az_batch_supplier_capacity.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, numeric counters, percentages, timestamps, or system flags — no PII present. 'action_user' appears to be a system username placeholder, not a real user identifier. Timestamps and numeric values are non-PII per exclusion rules.
azazie__az_batch_unsalable_in.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains inventory data with no personal identifiable information. Columns represent product IDs, quantities, timestamps, and internal codes. All columns are skipped per exclusion rules (vehicle/product data, internal IDs, timestamps).
azazie__az_batch_unsalable_in_and_sale.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only inventory and product data columns — all columns are internal IDs, product SKUs, color/size codes, inventory quantities, and timestamps. No PII fields present.
azazie__az_batch_unsalable_remain.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal product/inventory identifiers, timestamps, and operational flags. No PII fields (names, emails, addresses, etc.) are present. Columns like 'id', 'us_ymd', 'create_time' are internal identifiers or timestamps and must be skipped per rules. No email, phone, dob, name, address, ssn, password, username, country, gender, suffix, or facebookId columns detected.
azazie__az_batch_virtual_inv_deliverytime_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns appear to be product/category codes, delivery metrics, timestamps, and system flags. No email, phone, name, address, or other PII fields detected in the first 50 rows.
azazie__az_batch_warning_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, flags, timestamps, or configuration settings. No PII fields detected.
azazie__az_big_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a category listing file, not customer data. Columns contain category IDs and names in Chinese (e.g., '面料' = fabric). No PII fields present.
azazie__az_bill_plan.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, dates, status codes, and country codes. No names, emails, addresses, phone numbers, or other personal data are present in the first 50 rows.
azazie__az_bill_plan_approve.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal transactional identifiers, timestamps, and codes related to billing and purchasing processes. No PII fields are present in this dataset.
azazie__az_bill_plan_purchase.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, status codes, timestamps, or numeric IDs typical of transactional/order systems. No names, emails, addresses, phone numbers, or other PII fields appear in this sample.
azazie__az_black_five_due_date_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational identifiers and timestamps. No PII fields are present. Columns like id, batch_id, external_cat_id, parent_cat_id, action, due_date, real_large_sale, large_sale_limit, real_rush_sale, rush_sale_limit, status, effective_time, create_time, and last_update_time are all internal business identifiers, flags, or timestamps and must be skipped per exclusion rules.
azazie__az_black_five_due_date_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data is structured as a CSV file but contains only configuration and metadata related to product categories, sales limits, and internal timestamps. There are no columns containing PII fields such as email, phone, name, address, DOB, SSN, etc. The columns present are IDs, timestamps, status flags, and JSON configuration objects. Therefore, no PII columns are mapped.
azazie__az_bom_material_calculate_daily.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product inventory data (IDs, SKU, colors, quantities, timestamps). No PII fields are present. All columns are internal product identifiers, business metrics, or timestamps — none map to personal data categories.
azazie__az_bom_material_calculate_daily_item.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order/transaction identifiers (id, bom_calculate_daily_id, dd_id), quantity, material_number, and timestamps. No PII fields are present. All columns are internal IDs, numeric quantities, or timestamps — none map to email, phone, name, address, DOB, SSN, etc. Therefore, no PII columns to report.
azazie__az_cache.csv5 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__az_cancel_dispatch_in.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal operational data (dispatch serial numbers, product IDs, inventory counts, timestamps). No PII fields detected. The 'action_user' column contains system usernames (e.g., 'WebService', 'xiaoguang.zhang') but these are internal system accounts, not customer-facing usernames, and should be skipped per rules. All other columns are numeric counters, timestamps, or factory location codes.
azazie__az_d30_factory_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers and metadata (factory_id, department, factory_name, sort order, user actions, timestamps). No PII fields are present. The data appears to be internal operational records for factory/department management, not customer data.
azazie__az_d30_factory_group_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal identifiers, codes, and timestamps. Columns like 'action_user' contain usernames but these are likely system/internal user accounts, not customer PII. No emails, phone numbers, names, addresses, DOB, SSN, or passwords are present.
azazie__az_delayed_return_sample_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal IDs, timestamps, and non-PII flags. No PII fields (email, phone, name, etc.) are present in the sample data.
azazie__az_delivery_in_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All 12 columns are internal operational/inventory data: IDs, facility codes, SKUs, delivery/order serial numbers, transaction IDs, quantities, status flags, and timestamps. No PII fields present.
azazie__az_develop_procedure.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The file appears to be an internal order/procedure tracking system with numeric IDs, timestamps, and status flags. No personal information such as names, emails, addresses, or phone numbers is present in the visible data.
azazie__az_develop_procedure_edit_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in this structured file. Columns appear to be internal IDs, style IDs, actions, party IDs, and timestamps. No email, phone, name, address, or other PII fields are present in the visible data.
azazie__az_dispatch_bill.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, flags, or non-PII metadata. No PII fields present. Columns like dispatch_bill_id, provider_id, party_id are internal identifiers. Timestamps (create_time, last_update_time) and status flags are operational metadata, not personal data.
azazie__az_dispatch_bill_detail.csv1 column299 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 16 | username | high | [16] header 'action_user', values appear to be alphanumeric usernames |
Notes: This dataset appears to be internal financial/operational records from Azazie (order/billing system). It contains no personal customer data such as names, emails, addresses, or DOB. The only PII-like field is a username used for internal actions ('action_user'). All other columns are internal IDs, timestamps, financial figures, product attributes, and status flags — none contain searchable PII. No emails, phone numbers, or names appear in the sample.
azazie__az_dispatch_bill_settings.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains operational data about purchase subsidies, dispatch costs, and order types with JSON-encoded rules and timestamps. All values are internal business identifiers, numeric codes, and structured JSON blobs without personal information.
azazie__az_dispatch_bill_sku.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, transactional data, or internal flags. No PII present.
azazie__az_dispatch_designer.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal operational identifiers, status flags, timestamps, or counters. No PII fields present. Columns like dispatch_sn, dispatch_status, dispatch_designer_time, comfirm_time, and dispatch_list_id contain internal tracking codes, statuses, timestamps, or numeric IDs — none map to personal PII fields.
azazie__az_dispatch_designer_log.csv2 columns343 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | fullName | high | [4] values appear to be full names, e.g., '老周', 'daniel', 'peter' |
| 5 | username | high | [5] values are usernames, e.g., 'yzhang', 'yyxiong', 'pxing' |
Notes: Identified 2 PII columns: fullName (column 4) and username (column 5). All other columns contain internal IDs, file paths, timestamps, counters, and non-PII remarks.
azazie__az_dispatch_designer_standard.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal IDs, codes, flags, and timestamps with no PII. 'confirm_user' contains short alphanumeric strings that are likely internal usernames, not customer PII. No emails, phone numbers, names, addresses, DOB, SSN, or passwords detected in the sample.
azazie__az_dispatch_designer_standard_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data related to file management and product specifications. All columns represent internal IDs, file paths, notes, user identifiers, timestamps, and counters — none contain PII. The 'upload_user' field appears to be a system username rather than a personal identifier. No email addresses, phone numbers, names, addresses, or other PII are present.
azazie__az_dispatch_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a structured record of order adjustments and measurements, containing only numerical measurements (in inches), size codes, and color changes. There are no fields containing personal identifiers such as names, email addresses, phone numbers, or other PII types. The values contain measurement data, size codes (e.g., A0, A2, J6), and color names, but no personal contact information.
azazie__az_dispatch_progress.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified in the first 50 rows. The data appears to be order management records with IDs, statuses, timestamps, and estimated days — no personal identifiers, contact details, or sensitive information present.
azazie__az_dispatch_push_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only internal IDs (dispatch_sn), user identifiers (push_user), and timestamps (push_time). No PII fields are present. All columns are marked as skip per exclusion rules: push_user is an internal user identifier (not a username/email), timestamps are excluded, and dispatch_sn is an internal tracking code.
azazie__az_dress_color.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal identifiers, color codes, and timestamps. Columns include: abs_id (internal ID), dress_color_id (product color ID), color_en (English color name), color_cn (Chinese color name), created_stamp (timestamp), last_update_stamp (timestamp), party_id (internal party/group ID). None contain personal identifiable information.
azazie__az_fd_lack_warning.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. Columns include identifiers (id), sorting keys (web_sort), product codes (external_goods_id), color descriptions (goods_color), user identifiers (action_user), and timestamps (create_time, last_update_time). No personal information such as names, emails, phone numbers, or addresses are present in the provided rows.
azazie__az_fd_lack_warning_activity.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, sort order, product identifiers, color codes, usernames, and timestamps. No email, phone, address, DOB, SSN, or name fields are present.
azazie__az_file.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data is NOT structured PII records. It appears to be a log of file operations or database entries related to file caching/saving within an ERP system. Columns contain technical metadata (file paths, sizes, timestamps) and filenames — no personal identifiable information (PII) fields like names, emails, addresses, etc., are present. All columns map to 'skip' per exclusion rules (internal IDs, timestamps, counters, etc.).
azazie__az_goods_delivery_days.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (IDs, delivery stats, user identifiers). No PII fields are present. All columns map to skip categories: internal IDs (id, external_goods_id, provider_id), delivery metrics (delivery_days, extra_delivery_days, is_used, check_status), and timestamps/user identifiers (last_update_user, last_update_time). No emails, names, addresses, or other personal data appear in the sample.
azazie__az_goods_delivery_days_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, delivery tracking, status flags, and timestamps. No PII fields (email, phone, name, address, etc.) are present. Columns like 'check_user' and 'create_user' appear to be internal system usernames, not customer identifiers.
azazie__az_goods_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product catalog file with no PII fields. Columns include internal IDs (abs_id, goods_id), category names, product names, sizes, prices, and photo paths. All columns are internal product data or transactional — no personal information is present. Therefore, no PII columns to map.
azazie__az_goods_languages.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product catalog file containing dress names and descriptions. There are no PII fields present in this dataset. All columns represent product attributes (IDs, names, descriptions, timestamps) rather than personal information.
azazie__az_goods_on_sale_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product metadata and pricing data (color, sale status, timestamps, etc.). No PII fields are present. All columns are internal product attributes or operational flags, which per rules must be skipped.
azazie__az_goods_on_sale_info_copy.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal product identifiers, timestamps, and flags (id, external_cat_id, external_goods_id, color, sale timestamps, sale flags, discount, stage). These are typical e-commerce product catalog fields with no personal customer data.
azazie__az_goods_on_sale_info_country.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, timestamps, product attributes, sales flags, and operational counters. No email, phone, name, address, DOB, SSN, password, or username fields detected.
azazie__az_goods_purchase_price_multiple_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transactional data: abs_id (internal order ID), external_goods_id (product reference), quantity_head/tail (stock counts), provider_id (vendor reference), price (monetary value), note (optional comment), is_used flag, created_at (timestamp), created_by (user identifier). None contain personal or identifiable information about customers. All columns fall under exclusion rules (internal IDs, timestamps, financial/transactional data, flags).
azazie__az_goods_purchase_price_multiple_provider_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, and operational flags. No PII present. Columns like 'created_by' and 'last_update_user' contain system usernames, not personal user identifiers. The file appears to be an order/inventory log table from Azazie, containing only business process metadata.
azazie__az_goods_reserved_quick_ship.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers (external_goods_id), flags (is_forbidden), and timestamps (create_time, last_update_time, party_id). These match the exclusion rules for internal IDs and timestamps.
azazie__az_goods_sales_statistics_by_size.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order and product data (IDs, dates, sizes, quantities). No personal identifiable information (PII) is present. All columns represent internal business/transactional data (order IDs, product SKUs, sizes, dates, counts) and should be skipped per exclusion rules.
azazie__az_goods_sales_statistics_by_sku.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order/sales metadata columns (IDs, dates, SKU, color, size, quantities). No PII fields present. All columns are internal identifiers, timestamps, or product attributes which must be skipped per exclusion rules.
azazie__az_goods_spare_situation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal product identifiers, color codes, status flags, and timestamps. The data represents product catalog information with no customer or personal data present.
azazie__az_goods_spare_situation_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational IDs and timestamps. No PII fields are present. Columns map to internal identifiers (id, spare_id, provider_id, number, on_the_way_number), status codes, usernames (action_user), and timestamps (create_time, last_update_time). All columns fall under the exclusion rules for internal IDs, flags, and timestamps.
azazie__az_goods_style.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/operational identifiers (IDs, flags, timestamps). No PII fields present. This appears to be an inventory/goods metadata table rather than customer data.
azazie__az_group_weight_volume_times.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain internal IDs, measurements (length/width/height), counters, state flags, and timestamps. No names, emails, phone numbers, addresses, or other personal data appear in the first 50 rows.
azazie__az_holidays.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a system log or holiday calendar table with no personal identifiable information (PII). Columns represent internal identifiers (holiday_id), dates (date), groups (group), and timestamps (create_time, last_update_time). No PII fields are present.
azazie__az_ignore_alloc_email.csv6 columns11 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | [0] internal numeric ID 'abs_id' |
| 1 | high | [1] header 'email', values contain '@' | |
| 2 | skip | high | [2] internal numeric ID 'user_id' |
| 3 | username | high | [3] header 'user_name', values are short alphanumeric strings |
| 4 | skip | high | [4] timestamp 'create_stamp' |
| 5 | skip | high | [5] internal numeric ID 'party_id' |
Notes: 6 columns total, 2 contain PII (email, username). All other columns are internal IDs or timestamps.
azazie__az_init_batch_color.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product color information and timestamps. No PII fields are present. Columns are: id, color_en, color_cn, goods_type, note, action_user, create_time, last_update_time. All columns are non-PII per exclusion rules (internal product data, timestamps).
azazie__az_init_dispatch_attribute_combination.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/attribute IDs and timestamps. No PII fields are present. Columns map to product combinations, color/fabric selections, dress types, and creation/update timestamps — all operational data for the e-commerce platform.
azazie__az_init_dispatch_attribute_combination_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/color combination IDs and timestamps. No PII fields are present. All columns are internal identifiers or timestamps which must be skipped per exclusion rules.
azazie__az_init_dispatch_color.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns represent product color data (names, codes, types) with timestamps and internal IDs. No personal information present in this sample.
azazie__az_init_dispatch_fabric.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only fabric/product metadata (fabric names, IDs, timestamps). No PII fields are present. All columns are internal product identifiers or timestamps, which must be skipped per rules.
azazie__az_intercept_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file is structured but contains only system metadata and audit logs (attribute_id, attr_name, attr_value, create_time, description). No PII fields are present. The attr_value column contains JSON strings with internal codes, UUIDs, and thresholds — none map to personal data. All columns are system operational and should be skipped per exclusion rules.
azazie__az_inventory_color.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only color IDs and color names in multiple languages. No PII fields are present. All columns map to skip due to being product/color metadata only.
azazie__az_inventory_goods_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The data appears to be inventory records for dress sizes and colors, containing only product codes, size indicators, inventory counts, and timestamps. No personal information such as names, emails, addresses, or other PII fields is present in the visible columns.
azazie__az_invoice_money.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. This file contains only internal transactional IDs (invoice_money_id, shipment_id), monetary values (invoice_money), and timestamps (created_stamp). No columns map to any defined PII categories.
azazie__az_kpi_statistics.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All visible fields appear to be internal IDs, timestamps, status codes, or numeric identifiers with no personal data. The sample shows only system-generated identifiers (abs_id, scan_number), action types, party IDs, user identifiers (czsuo, xmwang, jjwang), and timestamps — none contain email, phone, name, address, DOB, SSN, or other PII per the defined field types. No columns map to any PII categories.
azazie__az_kpi_workload.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, shipment tracking, timestamps, and operational flags — no PII fields detected. The file appears to be purely transactional/shipment tracking data.
azazie__az_label_change_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal tracking fields (id, carrier, tracking codes, status flags, timestamps). Values contain only transaction IDs, carrier codes, status indicators, and timestamps with no personal information.
azazie__az_lack_warning_activity.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product data (IDs, categories, colors, timestamps) with no personal identifiable information. Columns like id, web_sort, main_category, external_goods_id, goods_color, action_user, create_time, and last_update_time are all internal product/operational fields. No PII fields present.
azazie__az_large_shipping.csv1 column3 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 13 | username | high | [13] header 'action_user', values are alphanumeric strings resembling usernames |
Notes: Only column 13 (action_user) contains PII (username). All other columns are internal IDs, operational flags, timestamps, or system paths and therefore skipped per exclusion rules.
azazie__az_large_shipping_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and timestamps. No PII fields are present. Columns like 'action_user' contain usernames but appear to be system/internal users (e.g., 'liwuxie1', 'xiaoguang.zhang') and are not customer PII based on the context and values. All columns are marked as skip per exclusion rules.
azazie__az_lend_dispatch_box.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational IDs and timestamps. No PII fields are present. Columns: abs_id (internal ID), dispatch_sn (dispatch serial number), box_id (box identifier), operator (operator username), operate_time (timestamp). All columns are internal tracking data and do not contain any personally identifiable information.
azazie__az_lend_dispatch_box_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (dispatch records) with no PII fields. Columns are: abs_id (internal ID), dispatch_sn (tracking number), previous_box_id/current_box_id (internal box identifiers), operator (username), and operate_time (timestamp). All columns are excluded per rules (internal IDs, timestamps).
azazie__az_loose_measure.csv1 column72 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 7 | username | high | [7] column 'action_user', values appear to be usernames (alphanumeric strings without spaces) |
Notes: File appears to be a product sizing table with measurements. Only column 7 (action_user) contains PII as usernames. All other columns contain numeric measurements, IDs, timestamps, and internal codes which are not PII per exclusion rules.
azazie__az_mannequin_deposit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, transaction codes, amounts, timestamps, and status flags. The 'provider_payer' column contains short alphanumeric strings that do not match typical names (e.g., 'Steve', 'John', 'Harry' appear but are likely internal codes or truncated values, not full names). No emails, phones, addresses, DOB, or SSN detected.
azazie__az_material_color.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the provided rows. The dataset appears to be a color catalog or inventory table with color codes, names in English and Chinese, timestamps, and a numeric party_id. None of the columns contain identifiable personal information such as names, addresses, contact details, or sensitive identifiers. The 'party_id' appears to be an internal reference number rather than a PII field.
azazie__az_new_dispatch_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data consists entirely of numeric IDs and timestamp fields with no personal identifiable information (PII) present. Columns 'id', 'external_goods_id', and 'is_new' are internal identifiers or flags. Columns 'worker', 'created_time', and 'last_update_time' contain system timestamps or internal user identifiers (e.g., 'yzhang', 'yyxiong') that are not personally identifiable in this context. No columns map to any PII fields (email, phone, name, address, etc.).
azazie__az_notice.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal system notices/tracking records with no PII. Columns are identifiers, status flags, timestamps, and unstructured content. No email, phone, name, address, DOB, SSN, or other PII fields are present.
azazie__az_notice_browse.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, numeric codes, and timestamps. Values are purely numeric or date/time formats with no personal information.
azazie__az_notice_file.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is a log or inventory table tracking file notices and metadata. All columns contain internal IDs, status flags, timestamps, and file paths/filenames. No PII is present — filenames contain random strings, dates, and document types, but no names, emails, addresses, or other personal data. All columns map to skip per rules (internal IDs, timestamps, file paths).
azazie__az_oc_approve.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains operational/payment tracking records with internal IDs, status flags, timestamps, and system paths. No PII fields (names, emails, addresses, etc.) are present. All columns are system metadata or internal references.
azazie__az_oc_common_approve.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal operational/tracking data for purchase price adjustments with no PII fields. All columns are internal IDs, status flags, timestamps, paths, and location codes.
azazie__az_operation_shop.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, cost tracking fields, timestamps, or flags. No PII present. 'name' column contains non-personal store names in Chinese/English (e.g., '店咆1').
azazie__az_operation_shop_ids.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. Columns: id (internal ID), shop_id (internal ID), external_goods_id (internal ID), create_time (timestamp), update_time (timestamp), in_use (flag). No PII present. All columns are skipped per exclusion rules (internal IDs and timestamps).
azazie__az_operation_shop_manager.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. Columns are internal IDs, manager usernames, and timestamps. All columns are marked as skip due to exclusion rules: manager is an internal username, timestamps are non-DOB dates, and IDs are internal identifiers.
azazie__az_order_address_cheat.csv2 columns391 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | high | header "email" resolves to PII field "email" | |
| 4 | address1 | high | header "address" resolves to PII field "address1" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__az_order_attribute.csv1 column0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | city | high | [3] header 'city_text', values are diverse city names including 'Olathe', 'Fairbanks', 'San Angelo', etc. |
Notes: Only column 3 maps to a PII field (city). Other columns are order IDs, timestamps, source codes, and coupon-related fields which contain no personal information.
azazie__az_order_cat_cheat_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only internal order IDs, setting IDs, quantity counts, and timestamps. No personal information such as names, emails, addresses, or phone numbers is present.
azazie__az_order_cat_cheat_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product catalog file with no personal identifiable information. Columns include product IDs, category names, goods numbers, deletion flags, user actions, and timestamps. No PII fields detected.
azazie__az_order_dispatch_relation_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a transactional log with order/dispatch IDs, timestamps, and status codes. All columns represent internal operational data (dispatch IDs, order numbers, status flags, service timestamps). No personal identifiers, contact details, or sensitive fields present.
azazie__az_order_header.csv1 column0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 24 | skip | high | [24] header 'email', values contain '@' symbol |
Notes: Only column 24 (email) contains PII. All other columns are internal IDs, transaction codes, timestamps, financial amounts, or flags — none contain personal information. The dataset appears to be order records with no direct customer details beyond email addresses.
azazie__az_over_dispatch_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal IDs (detail_id) and timestamps (create_time) or dispatch_list_id which refers to internal dispatch lists. No personal information such as names, emails, addresses, etc. is present in the first 50 rows.
azazie__az_over_period_dispatch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, counters, timestamps, or flags. No PII present. Columns like over_period_info_id, create_stamp, and provider_id are internal identifiers or operational timestamps, not personal data.
azazie__az_overseas_provider_stock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified in the provided rows. The data appears to consist of internal product/stock identifiers, timestamps, and numerical values, with no personal or sensitive information present.
azazie__az_overseas_provider_stock_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal inventory/order management data (IDs, stock numbers, timestamps, product codes). 'action_user' contains system user handles, not personal usernames.
azazie__az_overseas_provider_stock_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. All visible data pertains to inventory records (provider IDs, color IDs, stock numbers, product names). No personal identifiers such as emails, phone numbers, names, addresses, or dates of birth are present in the sampled data.
azazie__az_overseas_provider_stock_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product inventory table with no PII. Columns contain product IDs, names, units, types, rates, and timestamps. No personal identifiable information present.
azazie__az_pb_dispatch_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. The file contains only order/shipping identifiers (abs_id, status, shipping_id, tracking_number, shipping_num, last_shipping_at) with no personal information. Values are numeric IDs, status flags, and timestamps.
azazie__az_pb_dispatch_shipment_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal tracking data (order status changes, timestamps, user IDs). No PII fields are present. All columns map to skip categories (internal IDs, timestamps, status flags).
azazie__az_performance_monitoring.csv1 column2,700 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | fullName | high | [6] values are human-readable names like 'xiaoguang.zhang', 'qymeng2', 'ghtang' |
Notes: 50 rows analyzed. Only column 6 (fullName) contains PII. All other columns are internal process/timestamps/shipment IDs and should be skipped.
azazie__az_print_log.csv4 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 8 | skip | high | [8] header 'mobile' or 'tel', values are 10-digit phone numbers |
| 10 | address1 | high | [10] header 'address', values are street addresses |
| 11 | fullName | high | [11] header 'consignee', values are person names |
| 12 | zip | high | [12] header 'zipcode', values are 5-digit zip codes |
Notes: CSV file with 6 columns, 4 contain PII. Columns 0-7 are internal IDs, timestamps, or non-PII flags and therefore skipped.
azazie__az_profit_report_finance.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, or transactional data. No PII fields present. Columns like id, party_id, report_date, and JSON payloads contain shipping/income metrics but no personal information. This is consistent with operational reporting tables from an e-commerce platform.
azazie__az_profit_report_finance_ajust.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal IDs, transaction codes, timestamps, or JSON financial payloads. No PII fields (names, emails, addresses, etc.) are present in this structured dataset.
azazie__az_profit_report_finance_online.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All values are numeric financial metrics and internal IDs. The data appears to be aggregated financial reports with no personal information exposed.
azazie__az_profit_report_setting_finance.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, configuration keys/values, date types, timestamps, and notes in Chinese. This appears to be a system configuration or reporting table rather than customer data.
azazie__az_provider.csv2 columns4 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | high | [4] header 'email', values contain '@' symbols | |
| 5 | phone | medium | [5] header 'phone', values are numeric sequences of 11 digits |
Notes: Only email and phone contain PII. All other columns are internal provider/accounting fields, identifiers, or flags.
azazie__az_provider_action_log.csv1 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__az_provider_beneficiary.csv9 columns83 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | lastName | high | [3] header 'last_name', values are names |
| 4 | firstName | high | [4] header 'first_name', values are names |
| 6 | phone | high | [6] header 'personal_mobile_number', values are 11-digit numbers (Chinese mobile format) |
| 12 | lastName | high | [12] header 'legal_rep_last_name', values are names |
| 13 | firstName | high | [13] header 'legal_rep_first_name', values are names |
| 18 | state | high | [18] header 'state', values are Chinese provinces |
| 19 | city | high | [19] header 'city', values match '北京市' (Beijing) |
| 20 | address1 | high | [20] header 'street', contains location-like strings |
| 21 | zip | high | [21] header 'postcode', values are numeric postal codes |
Notes: 33 columns total, 9 contain PII. Columns 10 ('company_name'), 11 ('business_registration_number'), and others with 'company'/'business' prefixes are excluded by exclusion rules. Timestamps and internal IDs are skipped.
azazie__az_provider_big_category_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers (abs_id, provider_id, big_category_id) with no PII. All columns map to skip categories (internal IDs). No email, phone, name, address, or other PII fields present.
azazie__az_provider_capacity.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file contains no PII columns. All visible columns represent internal business identifiers (provider_id, group codes), timestamps (record_date, create_time, last_update_time), and capacity targets — none contain personal data such as names, addresses, emails, or phone numbers. The dataset appears to be operational records rather than customer data.
azazie__az_provider_capacity_and_production_cycle_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal operational metrics (IDs, dates, capacity tracking, production cycles). No PII fields present. Columns like abs_id, record_date, create_time, last_update_time are internal IDs and timestamps — these must be skipped per rules. The group_id contains non-PII product grouping labels in Chinese.
azazie__az_provider_capacity_and_production_cycle_target.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only internal operational data (IDs, dates, provider codes, capacities). All columns represent internal business metrics and timestamps, with no personal identifiable information present.
azazie__az_provider_chat_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. Columns 'abs_id' and 'provider_id' are internal numeric identifiers. Column 'action_user' contains usernames that are likely internal system users, not customer PII. All columns are non-PII per exclusion rules (internal IDs and timestamps). No PII fields are present.
azazie__az_provider_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with three columns: id, provider_id, and provider_group. None of these columns contain PII data. The values appear to be internal identifiers and group names, which are not considered personally identifiable information according to the rules provided. Therefore, no columns are mapped to PII fields.
azazie__az_provider_group_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a log or audit table containing internal system operations, not customer PII. Columns include identifiers, groups, actions, and timestamps. No PII fields (email, phone, name, address, etc.) are present. All columns map to skip per rules (internal IDs, company groups, timestamps, flags).
azazie__az_provider_group_user.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal group management data (provider groups, group leaders, timestamps). No PII fields are present. All columns are internal identifiers, timestamps, or non-personal group metadata. No emails, names, addresses, or other PII are visible in the first 50 rows.
azazie__az_provider_order_limit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (provider IDs, limits, notes, users, timestamps). No PII fields are present. All columns are internal IDs or operational metadata and should be skipped per exclusion rules.
azazie__az_provider_package.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns are internal IDs, timestamps, status codes, and other non-PII data. 'address' contains Chinese location strings but appears to be business locations rather than personal addresses; mapped to skip per context. 'action_user' contains short alphanumeric strings that look like internal usernames, not actual user identifiers.
azazie__az_provider_package_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be an internal administrative log or metadata table for managing providers/categories. It contains no personal identifiable information (PII) fields. All columns represent internal system identifiers, status flags, timestamps, and user action logs related to business operations rather than customer data.
azazie__az_provider_price_adjustment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain internal IDs, numeric codes, monetary values, timestamps, and user identifiers that do not qualify as PII per the defined field types. Columns like 'action_user' contain usernames that appear to be internal system accounts rather than customer identifiers.
azazie__az_provider_price_adjustment_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/pricing metadata and internal system timestamps. No PII fields detected. Columns map to product IDs, pricing tiers, status flags, and audit timestamps — all internal operational data. User identifiers (modify_user/check_user) are internal system usernames, not public PII.
azazie__az_provider_price_sku_adjustment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transactional data (IDs, SKU codes, timestamps, price adjustments). No PII fields are present. All columns map to internal business identifiers, timestamps, or numeric values.
azazie__az_provider_price_sku_adjustment_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product codes, prices, states, usernames (non-PII internal users), and timestamps. No emails, phones, names, addresses, DOB, SSN, passwords, or other PII fields are present.
azazie__az_provider_statistics_daily.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains transactional data with numeric IDs and return values, no personal information such as names, emails, phone numbers, or addresses. Columns map to internal business metrics only.
azazie__az_purchase_payment_application_config.csv2 columns4 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | username | high | [3] values are alphanumeric strings that appear to be usernames or internal IDs, not purely numeric IDs |
| 4 | high | [4] values contain @ signs and domain structures, confirmed by JSON email_list containing the same addresses |
Notes: File appears to be an internal configuration or payroll settings table. Column 3 (action_user) contains usernames rather than numeric IDs, while column 4 (create_time) is a timestamp that should be skipped. The JSON config field contains an email_list array with valid email addresses matching the action_user values, confirming the mapping.
azazie__az_purchase_payment_application_prepay_goods.csv1 column76 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 17 | username | high | [17] header 'action_user', values are alphanumeric strings that appear to be usernames/login handles |
Notes: Only column 17 (action_user) contains PII (username). All other columns contain internal order IDs, product codes, timestamps, and transactional data that do not qualify as PII under the defined rules. The values in action_user appear to be usernames/login handles used within the system.
azazie__az_purchase_payment_application_prepay_to_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, financial amounts, timestamps, and user identifiers. No PII fields are present.
azazie__az_purchase_payment_application_prepay_to_provider_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction identifiers, amounts, statuses, and timestamps. No PII fields are present. Columns like 'action_user' appear to be internal system usernames, not actual user identifiers, and are excluded per rules.
azazie__az_purchase_payment_application_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, currency codes, status flags, timestamps, and provider/account identifiers. No PII fields present.
azazie__az_purchase_payment_application_provider_prepay.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a financial transactions log containing internal IDs, monetary amounts, timestamps, and internal user references. No PII fields are present — columns like 'action_user' are likely internal system usernames or employee IDs, not customer-facing PII. All columns fall under skip rules (transactional data, internal IDs, timestamps).
azazie__az_purchase_payment_application_provider_prepay_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, financial/temporal data, or status flags. The 'action_user' column contains system-generated usernames ('webService') not actual user identifiers. Timestamps, amounts, and status codes are operational metadata.
azazie__az_purchase_payment_application_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, dates, and numeric rates. No PII fields (email, phone, name, address, DOB, SSN, password, username) are present. Timestamps and counters are explicitly excluded per rules.
azazie__az_purchase_proportion.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, financial amounts, and non-PII operational data (e.g., goods_amount, provider_id, update_time). This matches expected schema for Azazie order/shipment records — no customer PII is present in this particular dump.
azazie__az_qc_inspector.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers and timestamps. No PII is present in the first 50 rows. Columns user_name contains usernames, but these are non-standard identifiers and not typical usernames. According to exclusion rules, user_id is an internal ID and must be skipped. Timestamps create_time and last_update_time are not PII fields.
azazie__az_qc_photo.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal tracking IDs, timestamps, and filenames. No PII present. Columns like dd_dispatch_sn are internal dispatch serial numbers, qc_datetime/sd_datetime/create_time/last_update_time are timestamps, and filenames contain no personal data.
azazie__az_qc_photo_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an operational log file tracking dispatch records (dd_dispatch_sn), user actions (update/delete), and JSON payloads. No PII fields are present — all values are internal IDs, timestamps, and JSON structures containing file paths and system metadata. The 'user' field contains system usernames (zhangll, simon, cjwan), which are not considered PII under the defined rules.
azazie__az_qm_personal_info.csv2 columns6 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | phone | high | header "mobile" resolves to PII field "phone" |
| 4 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__az_quality_inspector.csv2 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | skip | high | [2] header 'mobile', values are 10-digit numbers |
| 3 | skip | high | [3] header 'email', values contain @ signs |
Notes: Only columns 2 (mobile) and 3 (email) contain PII. The 'quality_inspector_name' column appears to contain a name, but the sample value is empty. Other columns are timestamps or internal IDs and are skipped.
azazie__az_quick_ship_inventory_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product inventory table with no PII fields. All columns represent internal inventory IDs, product codes, dates, pricing, and status flags. No customer or personal data is present.
azazie__az_receipt_images.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, file paths, timestamps, and metadata. 'action_user_name' appears to be an internal system username, not a customer-facing username, and is therefore skipped per policy.
azazie__az_remake_dispatch_question.csv1 column0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | fullName | high | [2] non-empty values like '肖小仔', 'QAaaa', 'QAhuqingniu', 'QA01' match full name pattern |
Notes: Only column 2 contains PII (fullName). All other columns (question_id, day_date, type, status, create_time, last_update_time) are internal IDs, dates, or status flags and do not contain personally identifiable information.
azazie__az_remake_dispatch_question_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, product codes, flags, or status fields. No PII detected. Columns like 'action_user' contain system usernames, not customer identifiers. Timestamps and numeric IDs are non-PII per exclusion rules.
azazie__az_repertory_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only inventory and operational data columns: style_id, current date, inventory levels, adjustments, and notes. No PII fields (email, phone, name, address, etc.) are present. The 'note' column contains non-PII Chinese characters. All columns are skipped per exclusion rules.
azazie__az_repertory_main.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains product parameters (colors, locations), clothing types, and timestamps — all non-personal operational data. No emails, names, addresses, or other PII appear in the first 50 rows.
azazie__az_repertory_style.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file containing only internal inventory identifiers (location_index, clothes_index, etc.) and safe_inventory flags. No PII fields are present. All columns map to internal product/warehouse data and should be skipped per exclusion rules.
azazie__az_report_return_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain internal IDs, product codes, timestamps, return tracking numbers, and operational flags. No names, emails, addresses, phone numbers, DOB, SSN, passwords, or usernames are present.
azazie__az_report_return_special_style.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a product catalog listing, not customer PII. Columns contain product IDs, types, names, timestamps, and internal remarks. No personal identifiers (email, phone, name, address, etc.) are present.
azazie__az_report_shipping_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product inventory table with order/shipment records. All columns are internal identifiers, product details, timestamps, and operational flags. No PII fields are present.
azazie__az_reserve_result.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, status flags, timestamps, or empty values. No PII fields present. Columns like 'id', 'order_id', and time stamps are excluded per rules. 'action_user' contains system identifiers ('WebService'), not usernames.
azazie__az_restocking_fee_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transaction IDs, monetary values, and timestamps. No PII fields are present. All columns are internal IDs, financial amounts, or timestamps, which are excluded by the rules.
azazie__az_return_or_refund_rate_lock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction identifiers and timestamps. No PII fields are present. Columns map to internal IDs (lock_id, user_id), status flags (is_locked), transaction types (return_refund_type), and timestamps (create_time, last_update_time). All columns are non-PII per exclusion rules.
azazie__az_return_rate_target.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected - all columns represent internal statistics (stat_type codes, order_type categories, year/month counters, refund rates, timestamps). No personal identifiers, contact info, or account details present in this dataset.
azazie__az_return_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal IDs, counters, flags, timestamps, or numeric codes. Columns like abs_id, data, return_type, goods_number, return_number, statistics_year/date/type, report_type, is_single, party_id, action_user, create_time, and last_update_time contain no personal information.
azazie__az_return_report_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns appear to be internal IDs, transaction references, product SKUs, timestamps, and flags. No names, addresses, emails, phones, or other PII fields are present.
azazie__az_return_report_new.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product codes, timestamps, or flags (e.g., id, year, stat_type, is_batch). No names, emails, addresses, or other personal data present in the first 50 rows.
azazie__az_return_white_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal operational table with no PII. Columns contain internal IDs (return_apply_id) and status flags (is_used), no personal information.
azazie__az_sample_clearance_location.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and location codes. No PII fields present. The column 'abs_id' is an internal numeric identifier and 'location_seq_id' contains location codes (e.g., 'jzm_loc', 'US-A-1'), which are not personally identifiable information. These are internal system identifiers and not mappable to any PII field types.
azazie__az_sample_designer.csv2 columns5 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | phone | high | header "mobile" resolves to PII field "phone" |
| 4 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__az_sample_dress_email.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order IDs, synchronization flags, and timestamps. No PII fields are present. The columns represent internal order tracking data and synchronization status, which are not personally identifiable information.
azazie__az_sample_in_warehouse_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in this dataset. The file appears to contain internal order identifiers, dispatch serial numbers, operator names, timestamps, and status flags. All columns represent internal business identifiers or operational metadata rather than personal information. Operator names like 'pxing' and 'yyxiong' are likely internal employee identifiers rather than genuine personal names in this context.
azazie__az_sample_replenishment_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only operational/transactional data (product IDs, coefficients, color rates, inventory flags, timestamps). No PII fields detected. Columns map to product metadata, internal IDs, and audit timestamps — all excluded by policy.
azazie__az_sample_replenishment_plan_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/inventory identifiers, counters, timestamps, and flags. No PII present. Columns like 'action_user' contain internal system usernames (not customer-facing), which are excluded per rules. Timestamps (create_time, last_update_time) are skipped. No emails, names, addresses, phones, DOB, SSN, or passwords detected.
azazie__az_sample_replenishment_plan_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, status flags, timestamps, or action metadata. No PII fields are present. Column 8 'action_user' appears to be a system username, not a customer username, and is excluded per policy (internal IDs).
azazie__az_sample_sale_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII present in this sample. All columns are order identifiers, timestamps, status codes, and internal system notes. No personal information such as names, emails, addresses, or phone numbers are visible.
azazie__az_shipping_label_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal shipment/order tracking fields (ids, codes, dimensions, statuses, timestamps). No PII present. Columns like 'party_id' appear to be internal customer grouping IDs, not actual personal identifiers.
azazie__az_shipping_label_tracking.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal tracking IDs, URLs, and timestamps which fall under the skip rules. The data appears to be logistics/tracking information from EasyPost rather than customer PII.
azazie__az_shipping_tracking_event.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal identifiers, shipment/tracking details, timestamps, and system metadata. No names, emails, addresses, or other personal data appear in the first 50 rows.
azazie__az_single_assign_provider_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be an internal actions log table with IDs, timestamps, and user identifiers. Columns contain internal IDs (dd_id, provider_id), action_user (likely internal username), notes, and timestamps. No PII fields (email, phone, name, address, etc.) are present. action_user values like 'pxing' and 'ywang7' are likely internal system usernames, not actual user identifiers containing PII. All columns map to skip categories: internal IDs, usernames, timestamps.
azazie__az_size_chart.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains sizing and measurement data for dress patterns. All columns represent product attributes (sizes, measurements, timestamps) and worker identifiers. No PII fields are present. The 'worker' column appears to be an internal employee identifier rather than a username.
azazie__az_spot_check.csv2 columns4,455 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | firstName | high | [3] header 'apply_user', values are common given names like 'yyxiong', 'hzhang', 'jo', 'jjj', 'vip', 'pxing', 'xmwang', 'cjwan', 'able.wang', 'zhangll', 'robot' |
| 4 | fullName | high | [4] header 'inspector', values are names like 'yyxiong', 'yzhang', 'jo', 'pxing', 'xmwang', 'cjwan', 'able.wang', 'zhangll', 'robot' |
Notes: Only columns 3 (apply_user) and 4 (inspector) contain PII - they hold names. All other columns are internal system fields (check IDs, statuses, timestamps), which are skip per rules. No emails, phones, addresses, or other PII appear in the sample.
azazie__az_spot_check_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, status flags, timestamps, or product-related data. 'apply_user' contains a username-like value but is an internal system account (not a customer), mapped to skip per rules.
azazie__az_stock_up_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal IDs, rule names, timestamps, status flags, and action user identifiers. This appears to be a system configuration or scheduling table rather than customer data.
azazie__az_stock_up_rule_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, counters, timestamps, or product metadata. 'action_user' contains a single repeated username-like string (zhaoyong) but this is an admin account, not customer PII. Timestamps and numeric counters are explicitly excluded per rules.
azazie__az_stock_up_rule_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only system-generated rule management records with internal IDs, usernames, timestamps, and JSON payloads. No personal identifiable information is present in the visible columns or sample values.
azazie__az_sync_return.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, status flags, timestamps, or unstructured JSON responses. No PII is present in the first 50 rows.
azazie__az_sync_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, status flags, timestamps, and tracking codes. No names, emails, addresses, phones, DOB, SSN, or other PII fields detected.
azazie__az_sync_shipment_from_cms.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, transaction references, timestamps, flags, or unstructured JSON responses. No PII fields are present.
azazie__az_sync_shipment_from_ff.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal IDs, tracking codes, timestamps, and system flags — no PII fields present. Columns like id, shipped_signed_id, taobao_order_sn, waybill_no, tracking_number are internal tracking identifiers. logistics_order_sn and response contain system codes or JSON fragments. is_used, create_time, last_update_time, and tracking_type are status flags or timestamps. None map to PII categories.
azazie__az_sync_shipment_from_ff_copy1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal logistics/order identifiers and tracking metadata. No PII columns (email, phone, name, address, DOB, SSN, etc.) are present. Columns map to internal IDs, tracking numbers, timestamps, and status flags — all excluded per rules.
azazie__az_sync_shipment_from_ff_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a logistics tracking file with no PII fields. All columns represent internal order tracking data (IDs, statuses, timestamps), none contain personal or sensitive information. Per exclusion rules, all columns are skipped.
azazie__az_tax_change_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order/transaction identifiers and timestamps. No PII fields present. Columns include order IDs, status codes, tax ratios, refund IDs, party IDs, and action timestamps — all internal business data with no personal customer information.
azazie__az_tax_change_order_ca.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns (id, order_id, tax_rates, is_latest, create_time, last_update_time) contain internal order identifiers, tax rate structures, flags, and timestamps — none qualify as PII under defined categories.
azazie__az_test.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, numeric values, and timestamps. No PII fields are present. The columns are: id (internal ID, skip), value (numeric, skip), create_time (timestamp, skip).
azazie__az_ticket.csv1 column362 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 7 | username | high | [7] header 'user_name', values are alphanumeric usernames |
Notes: Only column 7 (index 7) contains PII (username). All other columns are internal IDs, timestamps, status codes, or numeric references — none qualify as PII under the defined schema. No emails, phone numbers, names, addresses, DOB, SSN, passwords, or gender appear in the sample.
azazie__az_ticket_message.csv1 column385 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | username | high | [4] header 'user_name', values are usernames like 'yzhang', 'yyxiong' |
Notes: Only column 4 (user_name) contains PII. All other columns are internal IDs, timestamps, or content fields without personal data.
azazie__az_transfer_fee.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal business data (shipping fee tiers, weights, pricing, timestamps), no PII present. Columns like transfer_fee_id, weight bounds, price ranges, and timestamps are operational metrics only.
azazie__az_transfer_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, timestamps, operational flags, or non-personal logistics data (e.g., transfer IDs, timestamps, shipping weights, carrier names). No email, phone, name, address, DOB, SSN, or other PII fields are present.
azazie__az_transfer_info_base.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No identifiable PII columns detected. All columns appear to be internal transaction IDs, numeric codes, and reference numbers typical of database keys and operational tracking fields. No names, emails, addresses, phone numbers, dates of birth, SSNs, passwords, usernames, or other personal data are present in the first 50 rows.
azazie__az_transfer_info_send.csv3 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__az_transfer_label_address.csv3 columns6 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | phone | high | header "sender_phone" resolves to PII field "phone" |
| 7 | high | header "sender_email" resolves to PII field "email" | |
| 8 | zip | high | header "sender_zipcode" resolves to PII field "zip" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__az_transfer_package.csv14 columns3,603 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 11 | fullName | high | [11] values appear as personal names, header suggests shipper contact |
| 12 | fullName | high | [12] identical to column 11, also personal names |
| 13 | address1 | high | [13] contains full street addresses with building numbers and road names |
| 14 | city | high | [14] contains city names |
| 15 | zip | high | [15] contains postal codes |
| 16 | country | high | [16] contains country codes (CN) |
| 17 | phone | high | [17] contains phone numbers with area code |
| 19 | fullName | high | [19] contains personal names |
| 20 | address1 | high | [20] contains full street addresses |
| 21 | city | high | [21] contains city names |
| 22 | state | high | [22] contains state abbreviations |
| 23 | zip | high | [23] contains postal codes |
| 24 | country | high | [24] contains country codes (US) |
| 25 | phone | high | [25] contains phone numbers without area code |
Notes: 38 columns total, 15 contain PII (names, addresses, phone numbers, postal codes, countries). All PII fields are related to shipper/consigner contact information rather than customer data, suggesting this is shipping/fulfillment records rather than customer profiles.
azazie__az_transfer_package_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file contains only numeric IDs and flags (Y/N). No PII fields are present. Columns are: id, package_id, group_sn, is_use. All values are internal identifiers or status flags.
azazie__az_transfer_service.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only service/payment configuration data (service codes, carrier names) with no customer PII. All columns are internal business codes and flags, matching the exclusion rules for company/business-related fields and internal IDs.
azazie__az_uncomfirmed_order_memo.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order identifiers and timestamps. No PII fields are present. Columns: order_id (internal ID), order_sn (order reference), memo (optional note), memo_user (user who added memo, but not a PII field), memo_stamp (timestamp). All columns are internal operational data and do not contain any personally identifiable information.
azazie__az_unsale_inventory_sales_ratio_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal IDs, categories, inventory metrics, timestamps, and user identifiers (test101). No personal information such as names, emails, addresses, or dates of birth is present.
azazie__az_unsale_monthly_sales_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal business metrics and system IDs. No PII fields are present. Columns like 'action_user' contain internal usernames (test101) but these are not user-facing identifiers and should be skipped per rules. Timestamps and numerical sales data are also non-PII.
azazie__az_unsale_moving_pin_rate_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data with no PII fields. Columns include IDs, categories, sales metrics, and timestamps. All columns are non-PII per exclusion rules (internal IDs, timestamps, transactional data).
azazie__az_unsale_stock_age_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/inventory metadata (category, stock age, container IDs, user action timestamps). No PII fields are present. All columns are internal operational data or identifiers (id, category, stock_age_lower, container_id_list, beyond_stock_age_lower_rate, action_user, create_time, last_update_time) and must be skipped per exclusion rules.
azazie__az_unsale_summary_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file is structured as a CSV but contains only transactional metadata (IDs, categories, JSON payloads, timestamps). No PII fields such as names, emails, addresses, or phone numbers are present in the visible data. All columns represent internal system identifiers, action users, timestamps, and JSON-encoded product/inventory metrics.
azazie__az_unshelve_order_temp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal operational data: id (record ID), order_id (order reference), type (type code), container_id (internal ID), note (empty), action_user (system service name 'WebService'), create_time and last_update_time (timestamps).
azazie__az_unshipped_order_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only two columns: a numeric ID field and a taobao order number string. No PII fields are present. The values are internal reference numbers and do not contain any personal or sensitive information.
azazie__az_unuse_provider_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal transaction IDs, stock flags, monetary values, timestamps, and status codes. The 'shipping_name' column contains generic tracking labels, not personal names. The 'note' column contains JSON strings with internal user references (not actual usernames or emails).
azazie__az_us_spot_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, status flags, timestamps, or business codes (check_id, dispatch_sn, order_type, quality metrics, acceptance status, region codes, creation/updates). No PII fields present.
azazie__az_us_spot_check_file.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational records (file IDs, PDF paths, timestamps, regions). No PII fields are present. Columns map to internal IDs, filenames, paths, inspectors, regions, and timestamps — all excluded by rules.
azazie__az_us_spot_check_note.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal tracking IDs, notes, and timestamps. No PII fields are present. Columns are: note_id (internal ID), dispatch_sn (internal tracking number), note (internal notes), inspector (username-like internal identifier), region (geographic label), is_read (flag), create_time (timestamp), last_update_time (timestamp). All columns are non-PII per exclusion rules.
azazie__az_vietnam_provider_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The data appears to be inventory or stock management records with columns for IDs, quantities, and timestamps. All values are numeric IDs, zero-based quantities, and ISO timestamps - none contain personal information.
azazie__az_vietnam_provider_setting_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal configuration data and timestamps. No PII fields are present. Columns like 'action_user' contain internal usernames ('leopard') which are not mapped to the username field because they are internal system identifiers, not user-facing identifiers. All columns are skipped per exclusion rules.
azazie__az_virtual_inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, product attributes, timestamps, or action metadata. No PII is present in this sample (id, check_id, party_id, external_goods_id, color, size, uniq_sku, virtual_quantity, delivery_days, is_used, open_time, action_user, created_time, updated_time, note).
azazie__az_virtual_inventory_replenishment_plan.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All visible fields (plan_id, external_goods_id, color, is_delete, state, batch_id, action_user, create_time, last_update_time) are internal identifiers, product attributes, status flags, or timestamps — none contain personal identifiable information per the defined PII categories.
azazie__az_virtual_inventory_replenishment_plan_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal operational data with no PII columns. All columns are internal IDs, timestamps, or notes that do not contain any personal information. The 'note' column contains cryptic codes and short strings, while 'action_user' contains short alphanumeric strings that appear to be internal system usernames, not actual user identifiers. All timestamps are in standard format and do not represent DOB. There are no emails, phone numbers, names, addresses, or other PII fields in this dataset.
azazie__az_virtual_inventory_replenishment_plan_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent product inventory data (IDs, SKU, sizes, colors, stock levels, timestamps). 'action_user' is an internal username, not customer PII. No emails, phones, names, addresses, or DOB fields present.
azazie__az_zipper_batch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain internal batch IDs, sequential numbers, user identifiers (action_user), and timestamps. None map to any defined PII fields.
azazie__az_zipper_batch_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (abs_id, batch_id, purchase_id) with no personal or identifiable information. All columns are skip per exclusion rules.
azazie__az_zipper_buy_request.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional/order data columns: request_id, provider_id, timestamps, order statuses, SKU numbers, quantities, amounts, and order references. No PII fields are present. All columns map to skip categories (internal IDs, timestamps, transactional data).
azazie__az_zipper_buy_request_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal product/price identifiers, timestamps, and numeric IDs. The data represents inventory/sku tracking without personal customer information.
azazie__az_zipper_sku.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent product color attributes (names, codes, inventory counts). This aligns with the dataset description of an online dress retailer's color inventory dump.
azazie__azazie_auto_assign_fail_reason.csv0 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__azazie_auto_dispatch_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The file appears to be a log of operational limits and stock changes for providers, with no personal identifiable information present in the visible columns.
azazie__azazie_dispatch_assign_ok_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal tracking IDs and service flags; no personal or identifiable information present. Columns map to internal dispatch/serial numbers, manual flags, provider IDs, and service timestamps.
azazie__azazie_dispatch_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. All columns appear to contain internal tracking IDs, timestamps, and status flags. Values are order references (e.g., ROM11, MTFxx), status codes, and system timestamps. No personal identifiers (emails, names, addresses, etc.) are present in this dataset segment.
azazie__azazie_goods_assign.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, timestamps, and non-PII data. Columns include: id (internal ID), dd_goods_id (internal product ID), difficulty_coefficient (code), party_id (internal party ID), action_user (username-like string but not a real username), create_time (timestamp), last_update_time (timestamp). No PII fields are present.
azazie__azazie_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, status flags, timestamps, and numeric counters. No PII fields are present in this structured data set.
azazie__azazie_group_delay.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only shipment tracking IDs, timestamps, and status flags. No PII fields are present. Columns map to: id (internal ID, skip), shipment_id (internal ID, skip), is_package (flag, skip), delay_date (date, skip), note (free-text, skip), action_user (username-like but likely internal system account, skip), create_time (timestamp, skip), last_update_time (timestamp, skip). All columns are non-PII per rules.
azazie__azazie_name_change.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/relational IDs and non-PII naming mappings. No columns map to PII fields. The data appears to be internal product SKU mappings and legacy name tracking, with no customer or personal data exposed.
azazie__azazie_name_change_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, product codes, and timestamps. No PII fields are present. Columns are: abs_id (internal ID, skip), external_goods_id (internal product ID, skip), old_name (product name, skip), new_name (product name, skip), create_stamp (timestamp, skip).
azazie__azazie_provider_alloc.csv1 column128 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 14 | emailText | high | free-text column with embedded emails (85/85 cells, 100% density) |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__azazie_provider_alloc_copy1.csv1 column41 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 15 | emailText | high | free-text column with embedded emails (41/41 cells, 100% density) |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__azazie_provider_color_default.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present. Columns: id (internal ID), az_init_dispatch_color_id (internal ID), provider_id (internal ID), create_time (timestamp), update_time (timestamp). All columns are non-PII per exclusion rules.
azazie__azazie_provider_limit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, flags, or operational metrics. No PII present. Columns like 'create_user' and 'update_user' hold system account names, not customer usernames.
azazie__azazie_provider_manage.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transactional data (IDs, prices, timestamps, flags). No PII fields are present. Columns map to internal IDs, product references, pricing rates, sorting logic, user action tracking, and status flags — all excluded per rules.
azazie__azazie_provider_manufacturing_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in this dataset. The columns appear to represent internal product codes, weights, and timestamps, with no personal or identifiable information present in the first 50 rows.
azazie__azazie_purchase_assign.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns map to PII fields. All columns are internal IDs, flags, timestamps, or non-personal metadata. No emails, names, addresses, DOB, SSN, or phone numbers are present.
azazie__azazie_purchase_assign_20210201_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, flags, timestamps, or non-PII metadata. No PII fields present in the first 50 rows. Columns like abs_id, provider_id, party_id are internal IDs; action_user is a username but is an internal system account (xyzhou) not a customer identifier; create_stamp is a timestamp; others are flags or constants.
azazie__azazie_purchase_assign_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal operational data with no PII fields. Columns are IDs, flags, timestamps, and usernames that do not qualify as PII under the defined schema. 'action_user' contains usernames which are internal system accounts, not public-facing identifiers, and are excluded per rules.
azazie__azazie_purchase_assign_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a log of factory selection changes rather than containing personal identifiable information (PII). The columns contain operational data such as record IDs, factory codes (e.g., 'mtf', 'GT', 'aztestaaa'), user actions, and timestamps. No PII fields (email, phone, name, address, etc.) are present in the visible data.
azazie__azazie_purchase_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a transactional table with product IDs, prices, and internal user identifiers. No PII fields are present. The 'action_user' column contains short alphanumeric strings that appear to be internal system usernames, not actual personal identifiers.
azazie__azazie_purchase_price_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, or transaction codes with no PII. Columns like action_user contain usernames, but they are internal system users, not customer PII. Therefore, no PII columns to map.
azazie__azazie_purchase_price_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transaction metadata (product IDs, old/new values, user actions, timestamps). No PII fields (names, emails, addresses, etc.) are present. All columns map to internal IDs, numeric values, action types, and timestamps — all excluded by policy.
azazie__azazie_purchase_price_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, numeric codes, timestamps, action flags, and operational counters. The file appears to be a transactional audit log tracking price changes or inventory adjustments, not customer data.
azazie__azazie_purchase_price_new.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product codes, pricing data, timestamps, and operation identifiers. Columns like 'action_user' contain usernames but these are internal system accounts, not customer PII. No emails, names, addresses, phones, or other PII present.
azazie__azazie_realtime_tracking_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal tracking and operational data (shipment IDs, tracking numbers, statuses, timestamps). No PII fields are present. All columns are marked as skip per exclusion rules (internal IDs, timestamps, status flags).
azazie__azazie_special_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational IDs and timestamps. No PII fields are present. All columns are internal identifiers, operator names, and timestamps, which are mapped to 'skip' per exclusion rules.
azazie__azazie_style.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII present. All columns are internal product/style identifiers, flags, and timestamps. Values are numeric IDs, static strings ("Color", "select"), and non-sensitive metadata. No emails, names, addresses, or other personal data.
azazie__azazie_style_name.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, names that appear to be test entries or placeholders, and timestamps. There are no identifiable PII fields such as emails, phone numbers, DOB, or addresses. The 'name' column contains values that are either generic placeholders (Test, test2, test4), company-specific names (Azazie Ginger), or non-personal strings (Sash, ¡@#￥%……&*（）——+、】‘、。，’“：”；|=-·). No columns map to any PII field types.
azazie__azazie_style_name_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be purely product metadata (item IDs, product names, timestamps). There are no PII fields present. Columns contain internal IDs, product names in various languages/iterations, and creation/update timestamps. No emails, phone numbers, names, addresses, or other personal data detected in the first 50 rows.
azazie__azcms_refund_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, statuses, timestamps, or financial amounts. No PII present in the first 50 rows.
azazie__back_amount.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, amounts, statuses, timestamps, or serialized data structures. 'apply_username' and 'back_username' appear to be system-generated or non-personal usernames, and are excluded per policy. No emails, phone numbers, names, addresses, DOB, SSN, or passwords are present.
azazie__back_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, status flags, timestamps, and operational logs. Columns containing identifiers (back_goods_id, service_id, order_id, user_id, order_goods_id, erp_goods_sn) are internal system references or product SKUs. Timestamps (back_datetime) and logs (back_log) contain operational metadata but no personal data. This appears to be a warehouse/returns tracking table, not customer-facing PII.
azazie__backup_ecs_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product attribute metadata (e.g., 'Designer', 'goodsStyle_sash_size'). All columns are internal product data or flags (attr_id, cat_id, attr_type, etc.). No PII present. All columns are marked as skip per exclusion rules for internal IDs, product data, and flags.
azazie__backup_ecs_attribute_1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product attributes table from Azazie. All columns are internal product metadata (attribute IDs, category IDs, attribute names like 'Designer', attribute types, values, and status flags). No PII fields are present. Columns like attr_id, cat_id, attr_name, attr_values, and status flags (is_linked, is_delete, is_show, etc.) are internal identifiers and product configuration data, not personal information.
azazie__bank_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only bank institution data (names, codes, types) with no personal identifiable information. All columns represent banking entities, not individual customer PII.
azazie__basket_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal inventory identifiers (abs_id, bar_code), shelf codes (shelf_sn, shelf_box), shipment IDs, status flags, and processing indicators. No names, emails, addresses, phone numbers, or other personal data present in the first 50 rows.
azazie__basket_shipment_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product codes, timestamps, or status flags. The data appears to be inventory/shipment records from Azazie, containing no customer personal information.
azazie__basket_shipment_detail_check_result.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and notes about basket shipment details. No PII fields are present in the first 50 rows. The columns 'abs_id' and 'order_goods_id' are internal identifiers and the 'note' column contains descriptive text about order goods IDs. All columns should be mapped as skip per exclusion rules.
azazie__basket_shipment_detail_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns represent internal identifiers, product codes, timestamps, status flags, and operational data. No email, phone, name, address, DOB, SSN, or other personal data is present.
azazie__basket_shipment_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal inventory identifiers (abs_id), barcode values (bar_code), serial numbers (shelf_sn), box identifiers (shelf_box), shipment references (shipment_id), status flags (status), and process flags (is_process). No PII fields present.
azazie__basket_status_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in first 50 rows. File appears to be internal inventory/operations tracking with codes, statuses, timestamps, and user initials. No email, phone, name, address, or other PII fields present in visible columns.
azazie__batch_allocate_provider_lock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns present. The file contains only internal IDs (abs_id), timestamps (create_time, update_time), request IDs, action users (xmwang, fxie, etc.), and a lock status flag (is_locked). All columns are non-PII per the exclusion rules.
azazie__batch_apply.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns are internal IDs, product codes, timestamps, statuses, and internal flags. No personal information such as names, emails, addresses, or phone numbers are present in the first 50 rows.
azazie__batch_apply_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal identifiers, product SKUs, sizes, and timestamps. No email addresses, phone numbers, names, addresses, DOB, SSN, passwords, usernames, or other PII fields are present in the first 50 rows.
azazie__batch_apply_mapping_purchase.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. The file appears to contain only internal IDs (apply_id, batch_sn), timestamps (create_time), and batch types — no names, emails, addresses, or other personal data. All columns are non-PII per exclusion rules.
azazie__batch_cat_due_date_effective_time.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. All visible columns appear to be internal IDs, timestamps, or numeric codes with no personal information. The values contain only numeric IDs, dates/times, and short alphanumeric codes that don't resolve to any known PII fields.
azazie__batch_deliver_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, product codes, timestamps, and system metadata. Columns like 'id', 'batch_sn', 'external_goods_id', 'color', 'deliver_num', 'purchase_goods_index', 'create_user', 'create_time', 'update_user', and 'last_update_time' are all internal operational data and do not contain personal identifiable information.
azazie__batch_dispatch_print_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, or internal codes (batch_id, dd_id, action_user, print_number, note, created_time, last_update_time). No PII fields present in this dataset.
azazie__batch_dispatch_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, financial/transactional data, or flags (abs_id, provider_id, party_id, price_region_id, exchange_rate, currency, audit_price_region_id, audit_currency, audit_exchange_rate, is_used, in_price_audit). None map to PII fields.
azazie__batch_due_date_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction/status records with no PII. Columns are check_id, data_type, check_status, party_id, action_user, create_time, last_update_time. All values are numeric IDs, status codes, and timestamps — no names, emails, addresses, or other personal data present. The action_user field contains short alphanumeric strings (e.g., 'ywang7') that appear to be internal system usernames, not actual user identifiers. Per rules, internal IDs and timestamps are skipped.
azazie__batch_due_date_check_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal audit/check tracking columns (IDs, timestamps, user actions). No PII fields are present. All columns are internal identifiers or timestamps and should be skipped.
azazie__batch_due_date_config.csv1 column61 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | username | high | [6] header 'action_user', values appear to be usernames |
Notes: Only column 6 contains PII (username). All other columns are internal IDs, timestamps, or category codes. No emails, phones, names, addresses, DOB, SSN, or passwords are present in the first 50 rows.
azazie__batch_due_date_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only rule configuration data with internal IDs, usernames, and timestamps. No PII fields are present. All columns are internal system identifiers or metadata and are skipped per exclusion rules.
azazie__batch_due_date_rule_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/SKU identifiers and timestamps. No PII fields are present. All columns map to internal IDs or timestamps which must be skipped per rules.
azazie__batch_due_date_rule_sync_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product codes, inventory flags, timestamps, and error messages. No personal identifiable information present in the first 50 rows.
azazie__batch_due_date_rule_time.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal rule/timing data with numeric IDs and timestamps. No PII fields are present. All columns are internal identifiers, effect times, and delay counters — none map to personal data categories.
azazie__batch_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product inventory data (IDs, names, status flags, timestamps). No PII fields are present. Columns like create_user/update_user contain internal system usernames, not customer PII. All values are product identifiers, status flags, and timestamps — none map to email, phone, name, address, etc.
azazie__batch_goods_convert_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, numeric measurements, timestamps, or usernames that do not contain personal identifiable information. 'action_user' appears to be internal system usernames, not customer usernames. 'id', 'type', 'party_id', 'container_id', 'external_goods_id', 'uniq_sku', 'operation_after_length', 'operation_before_length', 'loss_length', 'loss_rate', 'price', 'remark', 'created_time', and 'last_update_time' are all internal operational or transactional fields.
azazie__batch_goods_inv_setting.csv1 column11 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | username | high | [6] column 'action_user', values are alphanumeric strings that likely represent usernames |
Notes: 50 rows shown, 504 total rows expected. Only column 6 (action_user) contains PII (username). Other columns are internal IDs, timestamps, and product codes with no personal data. No emails, names, addresses, or other PII fields are present in this sample or expected context.
azazie__batch_goods_inv_setting_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. The dataset appears to be an inventory or stock management table with IDs, user references, and timestamps. No personal information such as names, emails, addresses, or phone numbers is present in the first 50 rows.
azazie__batch_goods_purchase_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, counters, or inventory tracking fields. No PII present in this sample. Columns like 'id', 'order_id', 'order_sn', 'goods_id', etc., are strictly operational and contain no personal data. The breach context mentions customer data exists elsewhere in the dump, but this specific file is purely transactional/operational.
azazie__batch_goods_purchase_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/order identifiers, pricing data, timestamps, or flags. No PII present. Columns like abs_id, external_goods_id, price, provider_id, and timestamps are internal operational fields. action_user is likely an internal username but lacks sufficient context to confidently map as username PII.
azazie__batch_goods_purchase_price_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, product/pricing data, timestamps, or status flags. No PII is present in the first 50 rows.
azazie__batch_goods_purchase_price_check_ddid.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product attributes, pricing data, status flags, timestamps, and user handles that do not contain personal information. The 'action_user' column appears to be an internal system username, not a public-facing username or searchable identifier.
azazie__batch_goods_purchase_price_check_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only numeric price data and internal IDs (batch_goods_purchase_price_check_id, from_number, to_number). All columns map to financial/transactional or internal identifiers which must be skipped per rules.
azazie__batch_goods_purchase_price_clothes.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal identifiers and flags (abs_id, category_id, pk_cat_id, is_delete). No PII fields are present. Columns map to internal database keys and status flags, which must be skipped per exclusion rules.
azazie__batch_goods_purchase_price_ddid.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/pricing metadata and internal system IDs. No PII fields are present. Columns include product IDs, color codes, pricing tiers, status flags, timestamps, and user action logs. All columns are internal identifiers, pricing data, or system timestamps which must be skipped per policy.
azazie__batch_goods_purchase_price_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a pure transactional data file with no PII columns. All columns relate to product pricing, batch IDs, and numeric ranges. No names, emails, addresses, or other personal data are present in the first 50 rows or structure.
azazie__batch_goods_purchase_price_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product and transactional data (IDs, prices, timestamps, actions). No PII fields such as names, addresses, emails, or phone numbers are present. All columns are internal identifiers, pricing data, timestamps, or flags, which are excluded per rules.
azazie__batch_goods_purchase_qc.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in this dataset. The file appears to contain only transactional order data fields (batch_id, order_id, quantities, timestamps, and user identifiers). The 'action_user' column contains short alphanumeric strings that appear to be internal system usernames rather than actual personal usernames or email addresses.
azazie__batch_goods_purchase_qc_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the first 50 rows. The file appears to contain only order/transaction metadata (IDs, quantities, timestamps, user initials) with no personal identifying information. All columns map to skip categories per rules (internal IDs, timestamps, transactional counters).
azazie__batch_goods_purchase_request.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns appear to be internal IDs, timestamps, product identifiers, inventory flags, and operational metadata. No names, emails, addresses, phone numbers, DOB, SSN, or passwords detected.
azazie__batch_goods_purchase_request_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, product codes, quantities, statuses, and other operational metadata. No personal identifying information (names, emails, addresses, etc.) is present in the first 50 rows.
azazie__batch_goods_purchase_request_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order quantity updates and internal tracking fields. No PII (personally identifiable information) is present in any column. Columns like 'action_user' contain internal usernames/roles, not public identifiers. Timestamps and IDs are internal tracking data. All values represent quantity adjustments and status codes.
azazie__batch_goods_purchase_spare.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, numeric counters, and timestamps — no PII fields present. All columns map to skip categories (internal IDs, counters, timestamps).
azazie__batch_goods_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains no PII columns. All columns appear to be internal identifiers (sku_rule), timestamps (create_time, update_time), status flags (is_batch, is_active), and a generic action_user field with consistent 'computer' values. No personal information such as names, emails, addresses, or phone numbers is present in the first 50 rows.
azazie__batch_goods_sale_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only internal product IDs, pricing data, colors, and other non-personal identifiers. All columns are excluded by rules (company/business references, internal IDs, timestamps, transactional data, and product attributes).
azazie__batch_group_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified in the provided columns. The dataset appears to contain only transactional and operational data (order IDs, goods IDs, quantities, prices, timestamps, and user identifiers). There are no columns containing email addresses, phone numbers, names, dates of birth, SSNs, passwords, or other PII categories as defined in the instructions.
azazie__batch_or_dispatch_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only product/warehouse operational data: IDs, timestamps, category codes, SKU references, inventory flags. No personal identifiers, contact details, or customer information are present. The columns represent internal tracking fields, not PII.
azazie__batch_or_dispatch_rule_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified. All columns appear to be internal transaction IDs, timestamps, and status flags (abs_id, cat_id, goods_id, type, action_time, action_user, action_type, party_id). No personal data such as names, emails, addresses, or identifiers present in the first 50 rows.
azazie__batch_profit_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain purely transactional/financial data (IDs, monetary values, inventory stats, timestamps) and operational flags. No names, contact info, or identifiers present.
azazie__batch_profit_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal configuration or timestamp fields (id, config_date, fee rates, is_delete, party_id, setting_type, action_user, create_time, last_update_time). No PII present.
azazie__batch_purchase_alert.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (category IDs, purchase periods, coefficients, timestamps) with no PII fields. All columns map to skip categories (internal IDs, timestamps, transactional data).
azazie__batch_purchase_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal order identifiers, statuses, JSON payloads, and timestamps. No names, emails, addresses, or other personal data appear in the first 50 rows.
azazie__batch_purchase_print.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, batch numbers, timestamps, and user action logs. No PII fields are present. Columns 'id', 'batch_sn', 'print_sku_times', 'print_wash_label_times', 'action_user', 'create_time', and 'last_update_time' are all internal identifiers, counters, or timestamps and must be skipped per rules.
azazie__batch_purchase_request.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, product/quantity data, or status flags. Columns like 'action_user' and 'check_user' appear to be usernames but follow internal ID patterns and are not mapped as PII per exclusion rules for auto-generated identifiers.
azazie__batch_report_inventory_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, inventory metrics, status codes, or non-personal remarks. Values in columns like 'category_status' and 'remark' appear to be internal notes or encoded strings, not personal data. This aligns with inventory/order management data typical of an e-commerce retailer.
azazie__batch_sample_dress_lend_AZ.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal IDs, timestamps, status flags, or company/business references. The 'request_username' and other username fields appear to be system/internal usernames, not personal user identifiers, and are excluded per policy.
azazie__batch_sheet.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a product specification or design document rather than customer data. It contains detailed measurements and fabric descriptions for dress sizes but lacks any identifiable personal information such as names, emails, or addresses. All visible data relates to product attributes (size measurements, fabric properties) and timestamps, none of which qualify as PII under the defined categories. No columns map to available PII fields.
azazie__batch_sku_purchase_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/price metadata, timestamps, or operational flags. No PII present. Columns like action_user contain internal system usernames, not customer identifiers. All numeric/price/timestamp fields are business operational data.
azazie__batch_sku_purchase_check_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction IDs, user handles for actions, and timestamps. No PII is present. Columns: id (internal ID), external_goods_id (product reference), remark (optional note), party_id (internal customer/reference ID), action_user (username/handle of actor), created_time (timestamp), last_update_time (timestamp). All columns are non-PII per exclusion rules.
azazie__batch_sku_purchase_check_memo_log.csv2 columns124 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | low | [3] values contain names and numbers; typical of full name fields in breach data |
| 4 | username | high | [4] header 'action_user', values are alphanumeric strings likely representing usernames |
Notes: CSV with 6 columns; only columns 3 and 4 contain PII. Column 3 appears to be a fullName field containing mixed names and numbers, while column 4 contains usernames. Other columns are IDs, timestamps, or internal codes and have been skipped per rules.
azazie__batch_sku_purchase_oc_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (IDs, timestamps, JSON action logs) with no PII fields. The 'action_user' field contains usernames but these are internal system accounts, not customer PII. All columns fall under the exclusion rules (internal IDs, timestamps, internal flags).
azazie__batch_sku_purchase_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be a product/inventory table with IDs, prices, timestamps, and internal flags. Columns like abs_id, uniq_sku, external_goods_id, price, and timestamps are all internal product identifiers or operational metadata, not personal data. action_user contains short alphanumeric strings that do not resemble usernames or human names.
azazie__bathc_refund_checkout_currency.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a simple CSV file with four columns: id, currency, type, taobao_order_sn. None of these columns contain PII. The columns appear to be internal identifiers, transaction metadata, and an external order reference. No PII fields such as email, phone, name, address, DOB, SSN, etc. are present in the first 50 rows.
azazie__bd_lack_warning_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product identifiers, timestamps, or operational metrics. No names, emails, addresses, phone numbers, or other PII fields are present in the sample.
azazie__bd_lack_warning_rules.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a configuration file containing business rules, not customer PII. All columns relate to inventory management parameters and system metadata. No PII fields present.
azazie__bench.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal operational data: numeric IDs, bench/container codes, internal usernames, facility IDs, and timestamps. No customer PII present.
azazie__bench_shipment_relation.csv1 column127 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | fullName | high | [4] header 'action_user', values are full names like 'xmwang', 'ghtang', 'Roland.Xiong', 'xiaoguang.zhang' |
Notes: Identified one PII column containing full names. Other columns appear to be internal shipment/transaction IDs, weights, timestamps, and non-PII flags like 'section321' — these are skipped per rules. No emails, phones, addresses, or other PII detected in this sample.
azazie__benchmark_time_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/tracking data (abs_id, external_goods_id, type, provider_id, handover_time, benchmark_time, create_user, created_stamp). No PII fields are present. All columns are internal IDs, timestamps, or flags and must be skipped per exclusion rules.
azazie__benchmark_time_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, timestamps, system users, quantities, and other non-PII data. 'create_user' and 'update_user' contain system usernames, not customer PII.
azazie__best_sellers.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product attributes, timestamps, status flags, or system-generated identifiers. No personal information such as names, emails, addresses, or dates of birth are present.
azazie__bi_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data appears to be a JSON-like string embedded within a CSV row, containing product inventory details rather than personal identifiable information. No PII fields (email, phone, dob, names, addresses, ssn, password, username) are present in the visible data. The content consists of product attributes like size, color, stock levels, and category names. All columns map to skip per exclusion rules (product/vehicle/financial/timestamp data).
azazie__bid_action_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal system identifiers, timestamps, business codes, and system messages. No PII fields are present.
azazie__bid_detail_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be transactional/operational data (bid IDs, prices, ranks, timestamps). No PII fields detected. Values contain only numeric identifiers, monetary amounts, ranks, and generic timestamps. No names, emails, addresses, or other personal data present.
azazie__bid_detail_summary.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional data (bid IDs, prices, ranks, timestamps) with no personal identifiable information (PII). All columns are internal identifiers, pricing metrics, and counters.
azazie__bid_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, status flags, or business data. 'create_user' is a username but appears to be an internal system user (yzhang) rather than customer PII. No emails, phones, names, addresses, or DOB present.
azazie__bid_lock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers (bid_id), lock status flags (is_lock), provider IDs, and timestamps. No PII fields are present. All columns are internal IDs, status flags, or timestamps and must be skipped per exclusion rules.
azazie__bid_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (rec_id, bid_id, provider_id) with no PII fields present. All columns are non-PII identifiers according to the exclusion rules.
azazie__bid_provider_alloc_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transactional data (IDs, prices, timestamps). No PII fields present. All columns are internal IDs, numeric values, or system timestamps.
azazie__bill_batch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the provided sample. All columns appear to be transactional data (amounts, timestamps) and contain no personal information such as names, emails, addresses, or other PII fields.
azazie__bill_batch_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns appear to be internal transaction identifiers, numeric adjustment amounts, and free-form notes without personal identifiers. Values contain transaction codes, numeric adjustments, and unstructured text without email/phone/address patterns.
azazie__bl_alert_config.csv1 column6 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | emailText | high | free-text column with embedded emails (6/13 cells, 46% density) |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__bl_alert_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain only internal business metrics and numerical data. No PII fields are present in this structured dataset.
azazie__bl_back_in_stock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal identifiers (uniq_sku), validity flags (is_valid), and timestamps (created_at, updated_at). No personal data such as names, emails, addresses, or other PII fields are present in this dataset.
azazie__bl_batch_sale_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/sales identifiers, timestamps, or counters. No PII is present in the first 50 rows of this file.
azazie__bl_capacity_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal operational metrics and identifiers (id, report_date, provider_id, etc.). No PII fields such as names, emails, addresses, or other personal data are present in the first 50 rows. All columns are skipped per exclusion rules (internal IDs, timestamps, counters).
azazie__bl_color.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. The file appears to be a product catalog listing color options and codes, with no personal information present.
azazie__bl_daily_operate_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory and operational metrics (IDs, quantities, timestamps). No PII fields are present. All columns are internal identifiers, timestamps, counters, or flags and must be skipped per exclusion rules.
azazie__bl_fabric_color.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains product color and fabric specifications, timestamps, and internal codes, but no personal information such as names, emails, phone numbers, addresses, or other sensitive data.
azazie__bl_goods_preferred_supplier.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only product IDs, color codes, provider IDs, user identifiers (non-unique system user), and timestamps. All columns fall under internal IDs, product data, or timestamps which must be skipped per rules.
azazie__bl_gross_profit_rate_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional data (order IDs, category IDs, category names, dates, monetary values). No PII fields are present. All columns are internal business identifiers, dates, and financial aggregates.
azazie__bl_lack_warning.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The data appears to be product inventory records with IDs, sorting metrics, category references, color descriptions, and timestamps. All columns relate to product metadata rather than personal information.
azazie__bl_lack_warning_copy1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to contain only product catalog data (IDs, categories, colors, timestamps) with no personal information. All columns map to internal product identifiers, color codes, and service timestamps which are excluded by policy.
azazie__bl_provider_step_adjust_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible fields are internal IDs (id, provider_id), numeric codes (step_price_id), monetary values (adjust_price), timestamps (create_time, last_update_time), and a non-PII status code (party). No names, emails, addresses, phone numbers, or other personal identifiers appear in the sample.
azazie__bl_provider_step_adjust_price_check_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, prices, timestamps, and usernames (action_user). action_user appears to be system usernames, not customer usernames, so it is skipped per rules.
azazie__bl_purchase_operation_record.csv4 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | lastName | high | [5] header 'status' is ambiguous but values match known surnames like Kucan, jacky.hu |
| 6 | fullName | high | [6] header 'action_user', values are full names like zhuo.zhang, jacky.hu, vicki.zhou |
| 10 | username | high | [10] values match username patterns (gz102, lytest26, blgz08, testtestvk01) |
| 11 | status | high | [11] header 'status', values are numeric flags (0/1) - mapped to skip per rules but included for completeness; this is actually non-PII |
Notes: CSV file with 166 rows of order/shipment records. PII includes usernames, full names, and last names. 'status' is a numeric flag and should be skipped per rules, but included here for transparency. No emails, phones, DOB, addresses, SSNs, or passwords are present in this sample.
azazie__bl_purchase_operation_record_detail.csv2 columns463 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | fullName | high | [5] values are names like 'zhuo.zhang' and 'Kucan', header suggests user identity |
| 6 | timestamp | high | skipped per rules - timestamps are explicitly excluded |
Notes: Only column 5 (fullName) contains PII. Column 6 is a timestamp and excluded per rules. Other columns are order IDs, batch numbers, quantities, and operation IDs — none contain PII.
azazie__bl_purchase_step.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in first 50 rows. File appears to contain only internal transaction/operational IDs, timestamps, and numeric values. All columns map to skip categories (internal IDs, timestamps, transaction codes, etc.).
azazie__bl_report_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the provided rows. The data consists of numerical IDs, JSON strings with batch order numbers, quantities, and other operational metrics, but no personal identifiers such as names, emails, phone numbers, or addresses are present.
azazie__bl_scm_sync_goods_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified in the provided rows. The data appears to be internal inventory records for clothing items with codes, names, prices, and timestamps. No personal information such as names, addresses, emails, or phone numbers is present in these rows.
azazie__bl_scm_sync_goods_provider_copy1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/supplier data (prices, quantities, provider names) and timestamps. No personal identifiable information (PII) fields such as names, emails, addresses, or phone numbers are present. All columns map to non-PII categories: product identifiers, supplier names (company names), price fields, and timestamps.
azazie__bl_step_purchase_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, product attributes, timestamps, or flags. The file appears to be an order processing or inventory management table from Azazie, containing no customer personal data.
azazie__bl_step_purchase_price_check.csv2 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | actionUser | high | [2] column name 'action_user', values are usernames (e.g., ywang7, xiaoguang.zhang) |
| 3 | checkUser | high | [3] column name 'check_user', values are usernames (e.g., ywang7, xiaoguang.zhang) |
Notes: This CSV file appears to be a transaction log or audit table, not containing direct PII fields such as emails, phone numbers, or addresses. Columns 2 and 3 contain usernames which are considered PII as they can be linked to individual identities.
azazie__bl_step_purchase_price_check_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided rows. The data appears to contain only product IDs, size types, steps, cost metrics, and timestamps — all transactional and non-personal data. No emails, phone numbers, names, addresses, DOBs, SSNs, passwords, or usernames are present in the visible columns.
azazie__bl_step_purchase_price_check_detail_old.csv1 column7,632 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 7 | username | high | [7] header 'action_user', values appear to be alphanumeric usernames |
Notes: Only column 7 contains PII (username). Other columns contain order IDs, sizes, statuses, prices, and timestamps which are operational data and not PII. No emails, phone numbers, addresses, DOB, or SSN detected in the sample.
azazie__bom_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the provided rows. The file appears to be a transactional/order data dump containing only order IDs, category IDs, prices, and timestamps. No personal information such as names, emails, or addresses is present in the visible data.
azazie__bom_list_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/bom identifiers, inventory codes, timestamps, and operational metadata. No PII present. Columns like bom_detail_id, external_goods_id, party_id are internal IDs. action_user contains system usernames, not customer-facing identifiers. All other columns are product attributes, pricing, and timestamps.
azazie__bom_list_detail_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/billing identifiers, timestamps, and codes. No PII fields detected. Columns like 'action_user' contain system usernames, not customer PII. The data represents inventory management records from Azazie's order/shipment system.
azazie__bom_list_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided rows. The columns appear to contain only internal system identifiers, transaction types, numeric values, and timestamps. None of the columns map to the defined PII categories (email, phone, dob, names, addresses, ssn, password, username, etc.).
azazie__bom_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product codes, timestamps, business codes, and operational flags. Columns like provider_phone contain codes (T55, T46) not actual phone numbers. This is a product inventory table from Azazie, not customer data.
azazie__bom_price_20220214_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent product data (IDs, prices, units, colors, provider info). No PII fields detected. Columns like provider_phone contain codes ('T55') not actual phone numbers. Timestamps and internal IDs are non-PII per exclusion rules.
azazie__bom_price_20220215_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal product/operational identifiers, pricing, timestamps, and provider codes. No names, addresses, emails, phones, DOB, SSN, or passwords detected. This appears to be an inventory/product management table rather than customer data.
azazie__bom_price_expect.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns represent product data, internal IDs, timestamps, business codes, and operational flags. No emails, names, addresses, phone numbers, or other personal identifiers are present.
azazie__bom_price_temp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data consists of product catalog entries with columns for absolute ID, external goods ID, pricing, units, goods type, and color codes with descriptions in Chinese. There are no personal identifiable information (PII) fields present in this dataset. All columns contain product-related data such as identifiers, prices, units, and color codes, which are not classified as PII according to the provided field type definitions.
azazie__bom_process.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII columns. All entries are process names, units, timestamps, and numerical values related to manufacturing or operational tracking. No personal identifiable information (PII) such as names, addresses, emails, phone numbers, or dates of birth is present.
azazie__bom_process_expect.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain internal process identifiers, timestamps, numeric values (prices/flags), and non-personal text labels. No emails, phone numbers, names, addresses, or other PII fields are present in the sample.
azazie__bom_process_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional data (IDs, prices, timestamps) with no PII fields. All columns map to internal IDs, numeric values, or timestamps which must be skipped per exclusion rules.
azazie__bom_process_price_20210415_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, numeric codes, timestamps, and monetary values unrelated to personal identifiable information.
azazie__bom_process_price_expect.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. The file appears to be a transactional ledger with IDs, region codes, prices, and timestamps. No names, contact info, or personal identifiers are present in the visible data.
azazie__bom_quotation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The data appears to be internal order/transaction IDs and timestamps, with no personal information such as names, emails, phone numbers, addresses, or dates of birth visible in this sample.
azazie__bom_quotation_category_rate_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain only operational metrics: IDs, rates, timestamps, and region codes. No personal identifiers, contact information, or demographic data present in the first 50 rows.
azazie__bom_quotation_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, status flags, timestamps, and audit metadata. No PII fields present. Columns like check_id, party_id, and user identifiers are internal references, not personal data. Timestamps (check_time, create_time, last_update_time) are system logs. No emails, names, addresses, or other PII detected.
azazie__bom_quotation_expect.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided rows. The data appears to be internal system identifiers, version numbers, and timestamps with no personal information. All columns are non-PII according to the exclusion rules (internal IDs, counters, timestamps).
azazie__bom_quotation_price_adjust_higher.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product codes, pricing data, and timestamps. This appears to be a product pricing/availability table from Azazie's database.
azazie__bom_quotation_price_adjust_lower.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent product pricing and inventory metadata (IDs, size types, price adjustments, timestamps). No PII present — purely operational data about product variants and pricing history.
azazie__bom_quotation_price_adjust_tmp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent product pricing, inventory, and timestamps. No PII fields present. Columns like id, cp_goods_id, region_id, size_type, material_adjust_price, material_old_price, material_new_price, old_price, new_price, create_time, and last_update_time are internal product/operational data and do not contain any personally identifiable information.
azazie__bom_quotation_version.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be purely transactional/audit data with no PII fields present. All columns represent internal system identifiers, timestamps, and status flags. No names, emails, addresses, or other personal data are detectable in the sample.
azazie__bom_quotation_version_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, business metrics, timestamps, or flags (e.g., id, version_id, category, unit_price, create_time, is_main_fabric). No email, phone, name, address, DOB, SSN, or password fields present.
azazie__bom_quotation_version_detail_20210113_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal product/process identifiers, numeric values, timestamps, and flags. No names, addresses, emails, phones, or other personal data present in the first 50 rows.
azazie__bom_quotation_version_detail_20210415_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal product/process identifiers, numeric values, timestamps, and flags (id, version_id, category, pp_id, process_id, region_id, unit_price, size consumption metrics, create_time, last_update_time, color, calculate_loss, is_main_fabric, loss_rate). These are operational/internal fields per Azazie database context.
azazie__bom_quotation_version_detail_20220214_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, process metadata, pricing data, timestamps, flags, and operational metrics. No personal or sensitive customer information is present in the first 50 rows.
azazie__bom_quotation_version_detail_20220215_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal identifiers, product metadata, timestamps, and flags (id, version_id, category, pp_id, process_id, region_id, unit_price, size consumption metrics, create_time, last_update_time, color, calculate_loss, is_main_fabric, loss_rate). None map to PII fields per the exclusion rules.
azazie__bom_quotation_version_detail_bak_20220214.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, financial data, timestamps, or flags. No PII fields detected. Columns like 'id', 'version_id', 'category', 'process_id', 'region_id', 'unit_price', 'small_size_consumption', 'large_size_consumption', 'create_time', 'last_update_time', 'color', 'calculate_loss', 'is_main_fabric', and 'loss_rate' are all non-PII per exclusion rules.
azazie__bom_quotation_version_detail_expect.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/process metrics (loss rates, size consumption, timestamps, color codes). No PII present. Columns like id, version_id, process_id, region_id are internal numeric IDs. Timestamps (create_time, last_update_time) are skip per rules. Color and ingredient are product attributes. No emails, names, addresses, phones, DOB, SSN, passwords, usernames, or gender values detected.
azazie__bom_quotation_version_expect.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided rows. All columns appear to be internal audit/tracking IDs, timestamps, and status flags (e.g., 'state', 'oc_audit_id', 'pass_time'). There are no names, emails, addresses, phone numbers, dates of birth, SSNs, passwords, usernames, or other PII fields in this dataset.
azazie__bom_quotation_version_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a log of database operations with columns: id, version_id, action_user, operation, memo, create_time, last_update_time. All columns contain internal system identifiers, operation types, and timestamps—no personal data present.
azazie__bom_quotation_version_log_expect.csv2 columns4,310 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header 'action_user', values are usernames (e.g., wswan, jjwang) |
| 4 | password | high | [4] column 'operation' contains password-like values such as 'pass', '2222', '3333', and actual passwords like 'qqqqqqq' |
Notes: Only columns 2 (username) and 4 (password) contain PII. The 'memo' column (index 4) contains passwords and other sensitive data, mapped accordingly. All other columns are timestamps, version IDs, or operation types and contain no PII.
azazie__box_management.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, dimensions, and timestamps. The 'action_user' column contains usernames but these appear to be system accounts/internal identifiers (architect, jxie, ywang7, vicki.zhou, qymeng2, architect-test) rather than customer PII. Values represent system actors, not end-user personal data.
azazie__box_volume.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product packaging dimensions and weights. No PII fields are present. Columns are: uniq_sku (internal product identifier), goods_name (product name), length, width, height, dimension_weight. All columns are non-PII per exclusion rules (product data, internal IDs).
azazie__braintree_refund.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. The file appears to be a transaction log containing only reference IDs, status codes, and timestamps. No names, emails, addresses, or other personally identifiable information is present in the first 50 rows.
azazie__brand.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is a simple two-column lookup table mapping brand IDs to brand names. No PII fields are present. The values appear to be internal reference data, not customer or user information.
azazie__brand_words.csv0 rows
File structure
Notes: free-form text with no consistent delimiter structure; appears to be a note or description rather than structured data containing PII
azazie__business_execution_time.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal operational identifiers (business_execution_time_id), timestamps (create_date), business process names (business_name, sub_business_name), and numeric durations (spend_time). No personal data such as names, emails, addresses, or other PII is present in the first 50 rows.
azazie__business_execution_time_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal system identifiers (business_execution_time_id), timestamps (create_date), business process names (business_name, sub_business_name), and numeric durations (spend_time). None contain personal information such as names, emails, addresses, or other protected fields.
azazie__cache.csv2 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__calendar.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only date and week information - no PII fields present. All columns represent calendar data (e_date, e_week, e_week_name, lunar_date) and do not contain any personal identifiable information according to the defined field types.
azazie__cancel_dispatch_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal operational table containing only system IDs, dispatch codes, and timestamps. No PII fields are present. All columns are internal identifiers, status flags, or timestamps, which are excluded by the mandatory skip rules.
azazie__cancel_order_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains only order cancellation records with internal IDs, order numbers, cancellation reasons, and timestamps. No personal identifiable information such as names, emails, addresses, or phone numbers is present.
azazie__cancelled_detail_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only cancellation reason codes and timestamps. No PII fields are present. All columns represent internal business flags, timestamps, and identifiers (parent_id). These are explicitly non-PII per exclusion rules.
azazie__cancelled_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible columns are internal operational data (cancellation IDs, timestamps, status flags, notes, order IDs, and action users). None contain personal identifiers such as names, emails, phone numbers, addresses, or other sensitive data.
azazie__cancelled_order_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order cancellation records with internal IDs, timestamps, and notes. No PII fields (email, phone, name, address, etc.) are present. All columns map to internal operational data or free-text notes that do not contain identifiable personal information. The notes column contains only order cancellation messages in Chinese/English without any personal details.
azazie__cancelled_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal IDs, timestamps, and user codes with no PII fields. All columns are non-PII per exclusion rules (internal IDs, timestamps, internal flags).
azazie__cancelled_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a lookup table for cancellation types, not customer PII. Columns are internal codes ('cancelled_type_id'), display values in Chinese ('cancelled_type_value'), and a flag ('is_used'). No PII fields are present.
azazie__carrier.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only carrier IDs and names, no PII fields present. All columns are internal logistics identifiers and should be skipped.
azazie__carrier_bill_template.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal system configuration data with no PII. Columns represent UI element positions and sizes (cbt_title, cbt_data), internal IDs (cbt_id, romeo_party_id, facility_id, carrier_id), and status flags (cbt_disabled). No personal or sensitive data is present.
azazie__carrier_bill_template_log.csv1 column26 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | fullName | high | [4] header 'admin_name', values are alphanumeric strings likely names |
Notes: This is a system log table tracking CBT actions. Only column 4 (admin_name) contains PII in the form of full names. All other columns are internal IDs, timestamps, or empty data arrays.
azazie__carrier_refund_apply.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal identifiers, timestamps, transaction metadata, and dispute tracking fields. 'action_user' appears to be a system username (not a customer username) and is therefore skipped per exclusion rules.
azazie__carton_content.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only internal transaction identifiers (carton IDs), size/quantity codes, SKU references, and timestamps. The 'action_user' field appears to be an internal system identifier (TPTE/gtky) rather than a human username.
azazie__cat_due_date_effective_time.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the provided sample. All visible columns appear to be internal identifiers, timestamps, or system-generated codes. Values contain only numeric IDs, usernames like 'webService' (likely system accounts), and timestamps — none map to personal PII fields per the defined categories. The dataset seems to represent internal transaction or audit logs rather than customer records.
azazie__cat_style.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/style metadata (IDs, categories, colors, pricing flags). No PII fields present. All columns are internal product attributes, business identifiers, or timestamps.
azazie__category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent product/category metadata (names, IDs, configuration parameters, timestamps). No PII fields present. Columns like cat_name and cat_desc contain product descriptions, not personal data. Timestamps (last_update_time) are non-DOB timestamps and are skipped per rules.
azazie__category_attr_value.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured product attributes table containing only size mappings (e.g., 'A0', 'L', 'WD16'). No PII fields are present — all columns represent internal product catalog data (attribute IDs, size values, batch flags). The values are size codes, not personal information.
azazie__category_attr_value_prod.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product attribute table with no PII. Columns contain product IDs, attribute categories (尺寸 = size), size values (numeric, alphanumeric), and batch flags. No personal information present.
azazie__category_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product attribute metadata (guarantee, buynote, pay, shipping) with timestamps. No PII fields are present.
azazie__category_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal IDs and purchase status codes. No PII fields are present. Columns map to internal identifiers (abs_id, cat_id) and purchase categories (cat_type, remark_type). All values are numeric codes or static strings indicating purchase types and statuses, with no personal information.
azazie__category_d30_goal.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, numeric codes, dates, monetary values, and user flags. No names, emails, addresses, or other personal data present in the first 50 rows.
azazie__category_daily_pageviews.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file containing web analytics data with no PII fields. All columns (visit_date, cat_id, site_code, country_code, language_code, pageviews, visits, visitors, cat_level, visit_type) are operational metrics and internal identifiers. No email addresses, phone numbers, names, addresses, or other personal data appear in the sample.
azazie__category_display_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a configuration or settings file, not customer data. All columns (project_name, location, cat_id, sort_order, is_display, last_update_time) are internal metadata and contain no PII. No mapping required.
azazie__category_erp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. File contains only product/brand names, IDs, and category metadata. All columns map to internal product codes, brand names, and timestamps which are explicitly excluded by policy.
azazie__category_languages.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The dataset contains only product catalog information (category IDs, names, descriptions) and timestamps. No personal identifiers, contact details, or sensitive data appear in the first 50 rows.
azazie__category_product.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal category IDs and timestamps. No PII fields are present. Columns 'cpl_id' and 'cpl_name' are internal product category identifiers and descriptions, not personal data. Timestamps 'created_at' and 'updated_at' are excluded per rules.
azazie__category_product_line.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs (numeric identifiers) and timestamps, which are excluded by policy. The data consists of numeric IDs and date-time values with no personal information.
azazie__category_provider_location_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (category, location ID, rate, user, timestamps) with no PII fields. All columns are internal identifiers, flags, or timestamps which must be skipped per exclusion rules.
azazie__category_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided file contains only product catalog metadata (descriptions, URLs, categories) and marketing content in multiple languages. There are no customer records, user data, or PII fields present in the first 50 rows. All entries are product-related category descriptions and search terms.
azazie__category_return_rate_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a structured CSV with headers, but all visible columns (id, project, report_type, report_date, cat_id, ship_number, return_number, create_time, last_update_time) contain only internal IDs, timestamps, and counters. No PII fields (email, phone, names, addresses, etc.) are present in the first 50 rows. The data represents operational metrics rather than customer or user details.
azazie__category_sale_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal sales counters and timestamps. No PII present. Columns like external_cat_id are internal product identifiers, and timestamps are creation/update logs.
azazie__category_weight.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and system metadata. Columns 'cat_id' (numeric category ID), 'max_weight' (numeric weight value), 'action_user' (system account), and 'last_update_time' (timestamp) are all internal operational data. No PII fields present.
azazie__change_location.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal logistics/warehouse movement records (abs_id, from_loc_id, to_loc_id, action_user, created_stamp, location_type). All columns are internal IDs, timestamps, or location codes — no PII present. The 'action_user' column contains short alphanumeric strings that appear to be internal system usernames, not actual user accounts. No emails, phone numbers, names, addresses, or other PII fields are present in the sample.
azazie__chargeback_auto_generate_file_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, timestamps, and file metadata. No PII fields are present. Columns are: id (internal record ID), chargeback_order_id (internal reference), order_id (internal order ID), file_tag (evidence category), file_path (internal storage path), create_time (timestamp), last_update_time (timestamp). All columns are non-PII per exclusion rules.
azazie__chargeback_intercept.csv2 columns1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | high | [1] header 'email', values contain '@' with domain patterns | |
| 2 | username | high | [2] header 'user_name', values are alphanumeric strings |
Notes: Only 3 columns present; email and username are clear PII. Other columns are internal flags/timestamps (skip).
azazie__chargeback_order_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in this dataset. All columns represent internal transaction IDs, timestamps, status codes, monetary values, and processing metadata — none contain names, contact info, or other personally identifiable information.
azazie__chargeback_sync.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a purely transactional table tracking order synchronization status. All columns are internal identifiers (abs_id, order_id), flags (is_synced, try_times), status messages (message), and timestamps (create_time, last_update_time). No PII is present.
azazie__check_address_order_cache.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction identifiers and timestamps — no PII fields present. All columns map to skip categories: internal IDs (cache_id, order_id, shipping_id), JSON payload status (check_result), and timestamps (created_time, updated_time).
azazie__check_import_attr_failed_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/operational data (IDs, timestamps, SKU codes, test names, and measurement notes). No PII fields are present. All columns map to internal identifiers, timestamps, or product metadata — none qualify as personal data under the defined PII categories. The 'memo' column contains generic measurement placeholders, not personal information.
azazie__check_inventory_children_task.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified in the first 50 rows. The data appears to be internal task tracking with IDs, status codes, timestamps, and usernames (vicki.zhou, morty, Kucan, zhuo.zhang). None of these contain personally identifiable information per the defined rules.
azazie__check_inventory_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, flags, or product/operational data. 'action_user' is a fixed username, not per-user identifier. All columns fall under skip rules.
azazie__check_inventory_detail_delete.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, product SKUs, stock counts, timestamps, or flags. No PII fields present. 'action_user' contains a username but this is an internal system account, not customer PII.
azazie__check_inventory_task.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal task tracking metadata (IDs, statuses, timestamps, user actions). No PII fields present. Columns like 'first_check_user' and 'second_check_user' contain system usernames, not customer identifiers, and are excluded per exclusion rules.
azazie__check_out_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be transactional/payment data fields (IDs, currencies, timestamps, codes). No PII fields detected. Columns like abs_id and charge_id are internal identifiers, charge_date_origin and create_time are timestamps, and others are payment processing metadata. No emails, names, addresses, or other personal identifiers present in the sample.
azazie__check_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal identifiers, product metadata, and JSON fragments from order processing. No PII fields (email, phone, name, address, DOB, SSN) are present. The values are order IDs, batch numbers, color codes, size details, timestamps, and system operators — none qualify as personally identifiable information per the defined PII categories.
azazie__check_report_copy1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal IDs, product codes, timestamps, and JSON fragments. No PII fields present. The data appears to be order/shipment metadata and product specifications, not customer personal information.
azazie__check_rma_upload.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The file appears to contain only internal transaction identifiers (taobao_order_sn), filenames, statuses, timestamps, and return IDs — all non-PII operational data. No names, emails, addresses, or other personal data visible in this sample.
azazie__check_slave_db.csv14 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | fullName | high | [0] header 'full_name', values contain full names like 'Jane Smith' |
| 1 | skip | high | [1] header 'email', values contain valid email addresses |
| 2 | skip | high | [2] header 'phone', values are 10-digit numbers |
| 3 | address1 | high | [3] header 'address1', values contain street addresses |
| 4 | city | high | [4] header 'city', values contain city names |
| 5 | state | high | [5] header 'state', values contain US state abbreviations |
| 6 | zip | high | [6] header 'zip', values contain 5-digit zip codes |
| 7 | country | high | [7] header 'country', values contain country names |
| 8 | skip | high | [8] header 'dob', values match YYYYMMDD date pattern |
| 9 | gender | high | [9] header 'gender', values are 'M'/'F' |
| 10 | username | high | [10] header 'username', values contain alphanumeric usernames |
| 11 | password | high | [11] header 'password', values contain hashed passwords |
| 12 | facebookId | high | [12] header 'facebook_id', values contain numeric Facebook IDs |
| 13 | skip | high | [13] header 'ssn', values contain 9-digit SSNs |
Notes: 14 columns total, 13 contain PII. This is a customer data export from Azazie, containing full names, contact information, dates of birth, and authentication details.
azazie__china_post_tracking_number.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal shipment tracking IDs and flags (abs_id, tracking_number, shipment_id, is_printed, print_stamp, is_avaliable, facility_id). No PII fields present in this dataset.
azazie__claim_delivery.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal IDs, transaction identifiers, shipping/tracking codes, monetary values, timestamps, and action metadata. No names, emails, addresses, or other personal data appear in the sample.
azazie__clearance_cat_name.csv1 column106 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | high | [3] header 'action_user', values appear to be usernames or system users, but given the breach context (Azazie customer data), these likely represent customer names or usernames. Values like 'jacky.hu', 'peter', 'peter1', 'peter2' suggest human identifiers rather than system accounts. |
Notes: This appears to be a product category table rather than customer PII. Column 3 ('action_user') contains values that look like usernames or system users, but given the breach context (Azazie customer data), these likely represent customer names or usernames associated with product categories. No clear PII fields (email, phone, dob, etc.) are present in the first 50 rows. Further analysis of other files in the breach is recommended to identify actual customer PII.
azazie__clearance_dress_retire_rules.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system identifiers and timestamps - no PII present. Columns: id (internal ID), months (duration), action_name (action code), is_delete (flag), create_time (timestamp), last_update_time (timestamp). All values are system metadata with no personal information.
azazie__client_id_white_list.csv0 rows
File structure
Notes: The file is a simple two-column list of UUID-like client identifiers and a binary flag. No PII is present; all columns are internal IDs or status flags. The first column appears to be an auto-generated client_id (UUID or numeric), and the second is a boolean flag indicating usage status. Neither contains personal or sensitive information.
azazie__close_order_apply.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, status flags, timestamps, or product metadata. No PII fields present. Columns like apply_id, provider_id, batch_sn, external_goods_id are internal identifiers. color contains product color/text. status and reason are operational flags. apply_info appears to be JSON size data. check_user is likely an internal username (not customer-facing). All timestamps are creation/update times. No emails, names, addresses, phones, DOB, SSN, passwords, usernames, or other PII detected.
azazie__cms_editor_link.csv1 column0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 12 | username | high | [12] header is 'username', values are alphanumeric strings typical of usernames |
Notes: Only column 12 (username) contains PII. All other columns are internal IDs, timestamps, status codes, or paths — none hold personal information.
azazie__cms_order_review.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only order IDs, status codes, rule IDs, and timestamps — no PII fields present. All columns map to internal IDs, flags, or timestamps which are excluded by policy.
azazie__cms_order_review_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in this file. Contains only internal order IDs (or_id), status codes, system operator, notes, and timestamps. All columns are internal IDs, status flags, or timestamps, which are excluded per rules.
azazie__cms_page.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a static page content table with no PII. All columns represent multilingual page content fields and identifiers. No email, phone, name, address, or other PII fields present.
azazie__cms_sample_operating_authorization.csv1 column3 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | [1] header 'operate_user_name', values include alphanumeric strings and an email address, typical for usernames |
Notes: Only column 1 contains PII (username). All other columns are internal IDs, flags, or timestamps and should be skipped per exclusion rules.
azazie__cms_sample_order_details.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product data, order status, timestamps, and placeholder dates. 'consignee' appears to be a generic placeholder or test value, not a real customer name.
azazie__cnaps_code.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only bank branch identifiers and names - no personal identifiable information (PII). Columns 'cnaps_code' (numeric bank codes) and 'branch_name' (branch names) are business identifiers, not PII. No mapping to PII fields possible.
azazie__color_family.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a structured color palette database with product categories (family), color names, and sorting metadata. No personal identifiers, contact details, or sensitive data are present in the first 50 rows.
azazie__color_provider_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be an internal reference table mapping IDs and status flags (id, color_abs_id, provider_id, is_enabled, create_time, last_update_time, tab). All columns contain internal identifiers, timestamps, or status flags, with no personal data such as names, emails, addresses, or other PII fields present in the sample. The values are numeric IDs, status codes (Y/n), and ISO-style timestamps, typical of database metadata or operational logs rather than customer data.
azazie__common_use_words.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in first 50 rows. File appears to be a log or test records table with status codes, timestamps, and non-PII identifiers. All values are system codes, numeric IDs, or status messages. No personal data fields present.
azazie__complaint_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns are internal IDs, timestamps, flags, or free-text notes unrelated to personal information. The column 'track_user' appears to be a static placeholder value ('pangou') and not actual usernames.
azazie__complaint_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal codes and flags (reason IDs, names, limits, status). No PII fields present. All columns are non-PII operational metadata used for dispute/transaction reason tracking.
azazie__complete_craft_notes.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns relate to product specifications (goods IDs, material descriptions, design attributes) and internal tracking (user action, timestamps). No personal customer data appears in the first 50 rows.
azazie__compress_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only pricing/rate data with country_id and shipping_id references. No PII fields detected. All columns are internal business identifiers, rate levels, and timestamp placeholders.
azazie__config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be configuration settings with no PII present. All columns are internal configuration identifiers, keys, values, remarks, and timestamps. No personal identifiable information detected.
azazie__configs.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a configuration or metadata file (not user data). Columns are: id, type, name, content_type, content, remarks, created_at, updated_at. None of these contain PII. The 'content' column holds system values like 'ERP' and file paths, not personal data. All columns are skipped per rules (internal IDs, timestamps, non-PII descriptors).
azazie__confirmed_order.csv1 column8 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header 'user_name', values appear to be alphanumeric usernames (e.g., 'Roland.Xiong', 'xiaoguang.zhang') |
Notes: Only column 2 (user_name) contains PII (username). Columns 0 (abs_id) and 3 (order_id) are internal IDs; column 1 (created_time) is a timestamp and should be skipped.
azazie__const_config.csv0 rows
File structure
Notes: This file appears to be a free-form text dump containing only SKU codes (e.g., SFP123159, SFP122984, etc.) with no identifiable personal information or structured columns. The content consists entirely of product identifiers and lacks any PII fields such as names, emails, addresses, or other personal data. There are no consistent delimiters or structured rows, confirming this is unstructured data.
azazie__consumable_stock_out_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal operational/logistics fields: so_id, batch, facility_id, receiver (short operator codes/initials, not full names), create_date, stock_out_user (internal system usernames), stock_out_date, order_sn (order serial numbers). None map to personal PII fields.
azazie__consumable_stock_out_order_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and counters (sog_id, so_id, uniq_sku, number). No PII fields are present. The data appears to be order/shipment identifiers and product SKU quantities, which are non-personal operational data.
azazie__consumables_inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (abs_id), product identifiers (uniq_sku), facility IDs, and amounts. No PII fields are present. Columns map to internal operational data and financial values, which are explicitly excluded by the rules.
azazie__consumables_inventory_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File appears to be a shipment tracking log containing only shipment IDs, SKU references, and action timestamps. No PII fields (names, emails, addresses, etc.) are present in the first 50 rows. Columns 'action_user' contain only generic usernames like 'wmzhen' and 'memory', which are not considered PII under the provided rules.
azazie__consumables_inventory_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only shipment and transaction data. Columns include internal IDs (abs_id, detail_abs_id), tracking numbers, shipment IDs, SKU codes, facility IDs, monetary amounts, action user identifiers, timestamps, and transaction types. None of these columns contain personal identifiable information (PII) as defined in the rules. All columns are internal system identifiers, operational data, or transactional metadata, which must be skipped per exclusion rules.
azazie__container.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, flags, or codes. No PII fields present. Column names and values indicate warehouse/container management data, not customer personal information.
azazie__container_data_set.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present. Columns: abs_id (internal ID), created_stamp (timestamp), insert_stamp (timestamp), operator (internal user identifier), facility_id (internal facility ID). All columns are non-PII per exclusion rules.
azazie__container_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a metadata table with container types and timestamps. No PII fields present. All columns represent internal system data (container type IDs, descriptions, timestamps, flags) and should be skipped per exclusion rules.
azazie__contract_seller_information.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal business identifiers, timestamps, or flags. No PII present. seller_name and seller_address appear to be business entities, not personal names or addresses. phone_number values are invalid/inconsistent and appear to be placeholder data. All other columns are internal system metadata.
azazie__country_allocate_facility_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal identifiers, country codes, allocation rules, and inventory status flags. No personal data such as names, emails, phone numbers, addresses, or DOB values are present in the first 50 rows.
azazie__country_default_delivery.csv9 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | internal absolute ID field |
| 1 | country | high | header 'country_name', values are full country names in English and Chinese |
| 2 | skip | high | internal country ID code |
| 3 | skip | high | internal Chinese translation field |
| 4 | skip | high | shipping provider internal ID |
| 5 | skip | high | shipping method name (no PII) |
| 6 | skip | high | facility/warehouse internal ID |
| 7 | skip | high | delivery type code (no PII) |
| 8 | skip | high | party/recipient internal ID |
Notes: This is a logistics/shipping reference table with no personal customer data. Contains only country names, shipping methods, and internal IDs. No PII fields present.
azazie__country_gst_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a purely transactional table containing country identifiers and tax rates with no PII fields. All columns are internal identifiers, numeric tax rates, or timestamps — none contain personal data such as names, addresses, emails, or other identifiable information. Therefore, no columns map to PII fields.
azazie__country_zone.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers (country_id, zone_id), a generic user label ('system'), and timestamps. No PII is present. All columns are internal IDs or timestamps and are skipped per exclusion rules.
azazie__coupon_white_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal coupon codes and country IDs. No PII is present. Columns: id (internal ID), country (numeric country code), coupon_code (internal coupon identifier), coupon_amount_limit (monetary value), currency (currency code). All columns are non-PII per exclusion rules.
azazie__craftwork_worker_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (id, worker, provider_id). No PII fields present. worker appears to be an internal username/identifier, not a genuine username. provider_id is a numeric internal reference. All columns are marked as skip per rules.
azazie__create_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file but contains no PII fields. All columns represent internal refund codes, reasons, and system metadata (IDs, timestamps, user roles). No email, phone, name, address, or other PII is present in the first 50 rows.
azazie__credits_app_users.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns appear to be internal IDs and timestamps. No PII fields are present in the sample data. Columns: rec_id (internal ID), user_id (internal ID), website_user_id (internal ID), application (internal identifier), last_update_time (timestamp). Per rules, all internal IDs and timestamps are skipped.
azazie__credits_store_credit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present. Columns: rec_id (internal ID, skip), user_id (internal ID, skip), credits (financial value, skip), credits_type (internal flag, skip), expire_date (timestamp, skip), create_time (timestamp, skip), last_update_time (timestamp, skip).
azazie__credits_users.csv3 columns1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | [1] header 'user_name', values are alphanumeric handles |
| 2 | skip | high | [2] header 'user_email', values contain '@' and domain |
| 3 | password | high | [3] header 'user_pswd', values are stored credentials |
Notes: Only 4 columns present. user_id is an internal ID (skip). user_info and timestamps are non-PII (skip).
azazie__cron_sync_download.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system metadata (IDs, codes, timestamps, paths). No PII present. The 'action_user' field appears to be a system username, not a customer PII field.
azazie__cron_sync_download_item.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal tracking IDs, timestamps, and status flags. No PII fields are present. All columns map to skip categories (internal IDs, timestamps, status flags).
azazie__cronjob.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal job scheduling information (cronjob IDs and timestamps). No PII fields present. All columns are internal identifiers or timestamps and should be skipped per rules.
azazie__crontab_execute_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal system identifiers, command paths, timestamps, and flags. action_user contains usernames but appears to be system service accounts rather than customer PII. All columns are marked as skip per exclusion rules.
azazie__crontab_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The provided data appears to be a log of scheduled tasks or reports, with columns indicating an ID, a task name/code, and timestamps (start_time, end_time, etc.). There are no personal identifiable information (PII) fields present in this dataset. All columns represent internal system operations and timestamps, which are excluded per the rules. Therefore, no PII columns are mapped.
azazie__crontab_log_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns represent internal system identifiers, action codes, and timestamps. The data appears to be operational logs for order inventory reservation processes, containing no personal or sensitive information.
azazie__crontab_monitor_config.csv1 column1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | high | [5] header 'alert_mail', value contains '@' symbol and domain structure, matches email pattern |
Notes: Only column 5 contains PII (email). All other columns are internal system identifiers, timestamps, and codes that do not contain personal information. The file appears to be a system alert configuration table rather than customer data.
azazie__cs_dept_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs (abs_id, cs_id), names (cs_name) that appear to be internal codes rather than real names, department codes, and timestamps. No emails, phones, addresses, DOB, SSN, or other PII fields are visible in the sample.
azazie__cs_tracking_result.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII fields. It only includes reason codes and flags for order processing (e.g., '订单继续', '顾客要求取消'). All columns are internal business flags and should be skipped.
azazie__csqc_check_item.csv1 column78 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | fullName | high | [4] column 'item_user_name' contains human-readable names like 'pangou', 'lmzheng', 'Henry Tong', 'James Chen' |
Notes: CSV file with 10 columns. Only column 4 (item_user_name) contains PII - human-readable names used as identifiers. All other columns are order metadata (item IDs, timestamps, statuses, languages) and contain no personal data. Values in column 4 include both real names ('Henry Tong') and likely pseudonymized identifiers ('pangou').
azazie__csqc_check_item_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (abs_id, item_id, party_id) with no PII present. All columns are numeric identifiers mapping to internal systems and should be skipped.
azazie__csqc_check_result.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File appears to be a control/check log with internal IDs, status flags, and timestamps. No personal or sensitive data present in the first 50 rows.
azazie__csqc_check_result_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only categorical metadata about content types, statuses, and weights. No personal identifiable information (PII) fields are present. All columns represent internal classification data (type_id, type_category, type_name, type_description, error_weight, status) and do not contain any customer or user data.
azazie__csqc_check_task.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only task metadata (IDs, timestamps, creator names, statuses, and language codes). No PII fields are present. All columns are internal identifiers, timestamps, or flags, which must be skipped per exclusion rules.
azazie__csqc_check_task_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs (abs_id, task_id, party_id) with numeric values. No PII present in the sample. Columns match exclusion rules for internal identifiers.
azazie__csqc_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an unstructured file containing only internal finance/credit card metadata (cc_id, cc_name, cc_value, cc_note). No PII fields are present. The sample row shows 'finance' as the name and 'ppp' as the value, which are internal codes, not personal data. All columns are internal identifiers or notes and must be skipped per exclusion rules.
azazie__csqc_item_type_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal item type mapping data with no PII fields. Columns are: item_type_mapping_id, item_id, type_id, error_weight. All values are numeric IDs and weights, no personal information present.
azazie__csqc_result_type_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal mapping IDs and weights - no PII present. All columns represent internal system identifiers (result_type_mapping_id, result_id, type_id, error_weight) and should be skipped.
azazie__currency.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a currency reference table with no personal or identifiable information. All columns are metadata about currency codes, symbols, and timestamps. No PII fields are present.
azazie__currency_conversion.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, timestamps, currency conversion metadata, and flags. No PII fields are present in this table.
azazie__currency_conversion_copy1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. This is a currency conversion rate table with internal IDs, timestamps, exchange rates, and currency codes. All columns are non-PII operational/financial data.
azazie__currency_conversion_with_party.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal currency conversion metadata (IDs, codes, rates, timestamps). No PII present. Columns like 'action_user' contain system account names, not customer identifiers. This is purely operational/financial data.
azazie__currency_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only currency exchange rate data (currency_id, base_id, base, exchange, last_update_time, operator). No PII fields are present. All columns are internal financial/temporal data and are skipped per exclusion rules.
azazie__customer_complaint_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only complaint categories and internal codes — no PII present. Columns are complaint_reason_id (internal ID), reason_name (text description), create_stamp (timestamp), and is_used (status flag). All columns are non-PII per exclusion rules (internal IDs, timestamps, flags).
azazie__customize_dispatch_number.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in this structured dataset. All visible fields are internal identifiers (abs_id, dispatch_list_id), timestamps (create_date, create_time, last_update_time), and user action logs (action_user). No personal data such as names, emails, addresses, or other PII categories appear in the first 50 rows.
azazie__d30_categorys.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only category identifiers and names (external_cat_id, big_cat_name, big_cat_name_cn). No PII fields present. All columns are internal category data and should be skipped.
azazie__daily_dispatch_allocation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal operational metrics, timestamps, and flags (abs_id, provider_id, statistice_date, d30_weight, shipment_number, total_shipment, daily_overdue, morning_total/limit/allocation, noon_total/limit/allocation, night_total/limit/allocation, manual_allocation, created_stamp, is_ranking). These are internal tracking fields and not personally identifiable information.
azazie__daily_dispatch_allocation_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (allocations, operators, timestamps) with no PII fields. All columns map to skip categories: abs_id (internal ID), daily_dispatch_allocation_id (internal ID), operator (username-like but appears to be system/operator codes), original_value / modified_value (numeric transaction values), operate_time (timestamp), note (comment). No emails, names, addresses, or other PII are present.
azazie__daily_purchase_num_statement.csv3 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | high | [3] contains comma-separated names like 'jacky,jacky.hu,Kucan' in multiple rows |
| 4 | fullName | high | [4] contains comma-separated names like 'jacky,jacky.hu,Kucan,architect' consistently |
| 5 | fullName | high | [5] contains comma-separated names like 'jacky,jacky.hu,Kucan' in multiple rows |
Notes: Only columns containing comma-separated personal names were identified as PII. All other columns appear to contain order metadata, configuration IDs, and numeric values unrelated to personal information.
azazie__daily_sale_category_statement.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided rows. The file appears to be a structured dataset containing only numeric IDs, dates, and category IDs. There are no fields that map to any PII categories (email, phone, name, address, DOB, SSN, etc.). The columns 'id', 'date', 'cat_id', 'sale_number', 'created_at', and 'updated_at' are all internal identifiers or timestamps and should be skipped according to the rules.
azazie__databasechangeloglock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This is an unstructured block representing database metadata/locking records, not customer PII. No columns map to PII fields. The file appears to be an internal database lock table with binary flags and numeric IDs.
azazie__db.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a MySQL user privileges table showing database access permissions. All columns represent internal system flags (privileges) and identifiers (host, database name, user account) rather than customer PII. No personal information is present.
azazie__dePost_package_tracking_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, and status flags. Columns like abs_id, shipment_id, tracking_num, file_name, action_user, created_stamp, and is_szx do not contain personal identifiable information per the exclusion rules.
azazie__declared_rate_country.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided rows. The file appears to be a reference table mapping country/continent IDs to numeric codes and names. All columns (abs_id, country_id, continent_id, continent_name, total_level, shipping_id) are internal identifiers, geographic codes, or non-personal metrics. No personal data (names, emails, etc.) is present in the sample.
azazie__declared_rate_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the provided rows. The data appears to contain only internal IDs (abs_id), country codes, and rate levels with timestamps and user identifiers, none of which qualify as PII under the defined categories.
azazie__declared_rate_detail_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns contain internal IDs (abs_id), country codes (country_id), rate levels, timestamps (operate_time), usernames (operate_user), and shipping IDs — all excluded by policy.
azazie__declared_rate_detail_history_v2.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. This appears to be a pricing/tariff table with IDs, timestamps, and numeric rate bands. Columns 'operate_user' contains a short alphanumeric string (ywu/memory) that is likely an internal operator code, not a username. No emails, phones, names, addresses, or other PII fields detected.
azazie__declared_rate_detail_v2.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only rate tier data (minimum/maximum/rate_level) and operational timestamps. No PII present. Columns: id, country_id, shipping_id, rate_level, minimum, maximum, declared_rate, operate_user, operate_time. All values are numeric or system-controlled timestamps.
azazie__default_qprofiles.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and technical metadata (organization UUIDs, language codes, profile UUIDs, and timestamps). No PII fields are present. All columns are flagged for skipping per exclusion rules (internal IDs, timestamps).
azazie__delete_goods_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, status codes, SKU references, timestamps, and exception messages. No email, phone, name, address, or other PII fields present.
azazie__delete_goods_to_cancel_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order IDs, statuses, error messages, and timestamps. No PII fields are present. Columns: abs_id (internal ID), order_id (order number), status (order status code), exception_message (error log), create_time (timestamp), last_update_time (timestamp). All columns are excluded per rules (internal IDs, timestamps).
azazie__delicate_goods_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers or timestamps: user_id (numeric ID), user_name (username but internal), create_stamp (timestamp), external_goods_id/dd_external_goods_id (product IDs), party_id (customer grouping). No PII fields (email, phone, name, address, etc.) are present in this structured table. The username column contains system-generated handles, not public usernames, and is excluded per rules.
azazie__deliver_contract_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, flags, or company/business names (express, seller_id, party_id, etc.). No PII present in this structured data file. Columns like 'create_by' and 'update_by' contain usernames but appear to be system-generated/internal roles rather than actual user identifiers.
azazie__delivery_candidate_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified in the first 50 rows. The data consists solely of order IDs, shipping IDs, allocation comments, and timestamps. No names, emails, addresses, or other PII appear in this sample.
azazie__delivery_change_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains only action logs regarding shipping configuration changes (abs_id, action_type, action_note, action_user, created_stamp). All columns are operational metadata with no personal information.
azazie__delivery_daily_statistics.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only shipping method identifiers, dates, and quantities. No personal identifiers (names, emails, addresses, etc.) are present in the sample.
azazie__delivery_less_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, shipment/tracking codes, timestamps, and flags. No PII fields are present.
azazie__delivery_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, timestamps, status flags, and operational tracking fields. No personal information such as names, emails, addresses, or phone numbers is present in the first 50 rows.
azazie__delivery_list_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, product attributes, order status counters, or timestamps — none contain PII. No email, phone, name, address, or DOB fields present in this sample.
azazie__delivery_process_change_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided data. The columns contain only internal transaction identifiers (delivery_sn, order_sn), status codes (type), numeric values (old_value, new_value), timestamps (created_time, created_at, updated_at), and user identifiers (created_user) that do not qualify as PII per the defined field types. All columns map to skip categories (internal IDs, flags, counters, timestamps).
azazie__delivery_process_submit_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified. All columns represent internal order tracking numbers (delivery_sn, order_sn), status codes (type), timestamps (created_time, created_at, updated_at), and user identifiers (created_user) which are considered internal system metadata per exclusion rules. No email addresses, phone numbers, names, addresses, DOB, SSN, passwords, or usernames appear in the first 50 rows.
azazie__delivery_quantity_limit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and operational tracking data (abs_id, shipping_id, shipping_name, quantity, is_used, facility_id). No PII fields are present. shipping_name contains logistics provider identifiers (jjshouse-UPS, jjshouse-DHL, jjshouse-Fedex) and is not a person name. All columns map to skip per exclusion rules.
azazie__delivery_return.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be an internal logistics/delivery tracking table with shipment serial numbers, facility/provider IDs, status flags, timestamps, and return metadata. All 20 columns are operational/internal data.
azazie__delivery_return_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only internal transaction IDs (delivery_sn), timestamps (action_time, created_at, updated_at), user actions (action_user, action_note). All columns fall under exclusion rules for internal IDs, timestamps, and flags.
azazie__delivery_return_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided rows. All columns appear to be internal identifiers (delivery_sn, order_sn), SKU codes, quantity counters, timestamps, and other non-PII operational data. No emails, phone numbers, names, addresses, DOBs, SSNs, passwords, or usernames are present in the visible data.
azazie__delivery_service_country.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains only shipping method codes, country names, and IDs — no personal identifiers such as names, emails, or addresses. Columns are internal logistics identifiers and country metadata.
azazie__dev_action.csv2 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__dhl_question_code.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns appear to be internal status codes and descriptions for shipment tracking (code_id, code_description, is_used). No PII fields are present in the first 50 rows. The data represents DHL shipping status codes and descriptions, not customer or recipient personal information.
azazie__dhl_region.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains geographical reference data (regions, cities, postcodes) without any personal identifiable information (PII). All columns represent location metadata rather than user-level data. No fields map to email, phone, name, address, DOB, SSN, password, or other PII categories.
azazie__dispatch_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected. All columns contain internal operational data (action IDs, timestamps, user actions, factory codes). No email addresses, phone numbers, names, addresses, dates of birth, SSNs, passwords, usernames, or other PII fields are present.
azazie__dispatch_assign_batch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns appear to be internal identifiers, timestamps, and status flags. No names, emails, phone numbers, addresses, or other PII are present in the provided rows.
azazie__dispatch_assign_batch_20210623_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, timestamps, and batch identifiers. No PII fields are present. All columns are excluded per rules: id, batch_id, sub_batch_id, dispatch_list_id, note, label_download_times, action_user, create_time, last_update_time are internal IDs, timestamps, or flags.
azazie__dispatch_assign_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, product codes, timestamps, and status flags. The data appears to be order/shipment records from Azazie, with no customer personal information exposed in this sample.
azazie__dispatch_assign_group_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible columns are internal IDs, product references, or timestamps. The 'pp_goods_ids' column contains numeric product IDs, and timestamps are non-PII. No email addresses, phone numbers, names, or other personal identifiers appear in the sample.
azazie__dispatch_assign_group_goods_tag.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a product inventory table with IDs, tags, status flags, and timestamps. No personal information is present in the visible columns.
azazie__dispatch_assign_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, batch identifiers, timestamps, status flags, and operational metadata. No PII fields are present. Columns like id, order_id, batch_sn, due_date, and timestamps are internal tracking numbers and system timestamps — explicitly excluded per rules. No email, phone, name, address, DOB, SSN, or password fields are detectable.
azazie__dispatch_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the first 50 rows. The data appears to be product attributes and image URLs, with no personal information such as names, emails, phone numbers, or addresses present.
azazie__dispatch_attribute_move_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal date tracking fields (abs_id, action_date, move_end_date). No PII is present. These appear to be internal operational timestamps rather than customer data.
azazie__dispatch_auto_provider_bl.csv1 column12 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header is 'username', values are alphanumeric strings used for login |
Notes: This file contains only provider_id (internal ID), username, and created_time (timestamp). Only username maps to a PII field. All other columns are internal IDs or timestamps and should be skipped per rules.
azazie__dispatch_auto_provider_bl_history.csv1 column32 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | [1] header 'username', values are alphanumeric strings that resemble usernames |
Notes: Only column 1 (username) contains PII. All other columns are internal IDs (provider_id), timestamps (created_time), and status flags (action) — these are skipped per exclusion rules. No emails, phone numbers, names, addresses, DOB, SSN, or passwords are present in the sample.
azazie__dispatch_bill.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, order metadata, product specifications, timestamps, and financial/transactional data. None map to any of the defined PII fields.
azazie__dispatch_change.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present. The columns are: id (internal ID, skip), external_goods_id (internal ID, skip), operator (username candidate but values appear to be system operator initials, skip), created_at (timestamp, skip), updated_at (timestamp, skip).
azazie__dispatch_delivery_consult.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, status flags, or non-personal identifiers. 'consult_user' appears to be a system username (yzhang) not a personal user identifier. 'party_name' contains business names (Azazie, jjshouse).
azazie__dispatch_due_date.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file appears to contain only internal IDs, tracking codes, and timestamps with no personal information. Columns like 'dispatch_list_id', 'dispatch_sn', 'cat_due_date', and 'action_user' are operational data, not PII.
azazie__dispatch_finish_data_current.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns detected. This appears to be a product catalog listing external IDs, category names in Chinese, and dispatch flags. No personal information is present in the first 50 rows.
azazie__dispatch_finish_data_previous.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product catalog data (external_goods_id, external_cat_id, etc.) with no personal information. All columns relate to product categories, inventory, and dispatch status. No PII fields present.
azazie__dispatch_in_warehouse_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns appear to be internal identifiers (dispatch_sn), numeric counters (time), and timestamps (create_time). No personal information such as names, emails, phone numbers, or addresses is present in the first 50 rows.
azazie__dispatch_intercept.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal IDs, status flags, timestamps, and system users. No personal or sensitive information present in the first 50 rows.
azazie__dispatch_intercept_condition.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain internal IDs, usernames, timestamps, status flags, and product/style identifiers. No emails, phone numbers, addresses, DOB, SSN, or passwords present in the sample. The 'key_word' column contains product/style descriptors and generic terms, not personal data.
azazie__dispatch_lend.csv1 column305 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header 'operator', values match known user identifiers (e.g., cjwan, yfliu, gfjin) |
Notes: No other columns contain PII. The 'operator' column contains usernames used to track internal users handling dispatch operations. All other columns represent internal logistics tracking IDs, timestamps, status codes, and operational notes.
azazie__dispatch_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, transaction codes, product codes, status flags, and inventory metadata. No names, addresses, emails, phones, or other personal data appear in the first 50 rows.
azazie__dispatch_list_changed.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields are internal IDs (dispatch_sn, provider_id), timestamps (created_stamp, sent_stamp), status flags (has_sent, attempt_times), and empty mobile_list. No personal data exposed in this dataset.
azazie__dispatch_location.csv1 column1,996 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | fullName | high | [2] values appear to be full names (e.g., dshao, xzhong, yzhang) |
Notes: The dataset appears to be a structured CSV with 5 columns. Column 2 contains user identifiers that look like full names based on pattern and context. No other columns contain obvious PII fields such as email, phone, dob, or ssn. All other columns represent internal IDs, timestamps, or location codes which are not PII.
azazie__dispatch_location_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data appears to be a structured CSV file with consistent columns and rows. However, the columns do not contain any PII fields. The columns present are 'id', 'dispatch_sn', 'location_seq_id', 'creater', 'created_stamp', 'order_id', 'up_down', and 'bar_code'. These columns contain internal IDs, timestamps, and status flags, none of which qualify as PII according to the provided field types. Therefore, no PII columns are mapped.
azazie__dispatch_location_history_back.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to contain only internal order tracking IDs (dispatch_sn), location codes, creator usernames, timestamps, order numbers, and status flags. All columns are internal identifiers or operational metadata with no personal information.
azazie__dispatch_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only dispatch identifiers and timestamps—no personal identifiable information (PII) fields such as names, emails, phone numbers, or addresses are present. All columns represent internal operational IDs and datetime stamps, which are excluded per the skip rules.
azazie__dispatch_material.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product metadata (IDs, color names, URLs, timestamps, and internal flags). No PII fields are present. All columns are internal product or operational identifiers, timestamps, or flags and are skipped per rules.
azazie__dispatch_material_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (dispatch material attributes) with no PII fields. All columns are internal IDs, amounts, and flags — none map to PII categories. No emails, names, addresses, or other personal data are present.
azazie__dispatch_material_expend.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product catalog data (dress types, sizes, rates). All columns are internal product identifiers, timestamps, and operational flags. No PII fields present.
azazie__dispatch_normal_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product attributes, URLs, timestamps, and generic backup fields. No names, emails, addresses, or other PII appear in the sample. The data represents dress measurements, styles, and internal tracking.
azazie__dispatch_order_stock_reserve.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, flags, and system-generated values (id, group_number, order_goods_id, dispatch_sn, is_lock, lock_time, is_reserve, reserve_time, note, action_user, create_time, last_update_time). None contain personal or sensitive data.
azazie__dispatch_package_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in this file. The data appears to be transactional records containing product IDs, pricing information, and system-generated user identifiers. All columns map to internal IDs, product codes, pricing values, and system timestamps which are excluded by policy.
azazie__dispatch_package_sn.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible columns are internal IDs (batch_id, goods_id), action_user codes, timestamps, and numeric counters — none contain personal data. The dataset appears to be purely transactional/order tracking metadata.
azazie__dispatch_profit_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only financial and inventory metrics (sales, costs, profits, inventory levels) with no PII fields. All columns represent transactional data, internal IDs, timestamps, or business analytics metrics which are not personally identifiable information.
azazie__dispatch_quality_inspection.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, status flags, or operational codes. No PII fields are present in the sample. Columns like 'insert_user_name' appear to be internal usernames (not public-facing), and all timestamps are excluded per rules. No emails, phones, names, addresses, DOB, SSN, passwords, or other PII are detectable.
azazie__dispatch_quality_inspection_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a quality control / inspection table from Azazie. All columns are internal IDs, status flags, timestamps, and user names that are not PII. No emails, phone numbers, addresses, or other personal identifiers are present. The 'action_user_name' column shows a system username (yzhang) which is not a public username or searchable identifier and should be skipped per policy.
azazie__dispatch_reason_record.csv2 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | reason_detail | low | [4] contains free-text reasons like '衣服太薄' (garment too thin) |
| 5 | action_user | high | [5] header 'action_user', values are usernames like 'mark', 'jxie', 'morty' |
Notes: Only columns 4 (reason_detail) and 5 (action_user) contain PII. Column 4 contains free-text reasons that may include PII but are not strictly structured fields. Column 5 contains usernames. All other columns are internal IDs, numeric dispatch_list_id, cancel_reason codes, and timestamps — these are skip per rules.
azazie__dispatch_receive.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible fields are internal IDs (numeric identifiers), action users (non-PII system accounts), timestamps, and status codes. No emails, names, addresses, phone numbers, or other personal data appear in the first 50 rows.
azazie__dispatch_reserve_control.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns are internal IDs, timestamps, flags, or status codes. The 'update_user' column contains usernames, but these appear to be system users/technical accounts rather than customer PII. The 'forbidden_reserve' and 'memo' columns contain status flags and notes, not personal data.
azazie__dispatch_rework_init.csv3 columns358,577 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | emailText | high | free-text column with embedded emails (6/199 cells, 3% density) |
| 5 | fullName | high | header "customer_name" resolves to PII field "fullName" |
| 6 | high | header "customer_email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__dispatch_rework_init12.csv3 columns358,578 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | emailText | high | free-text column with embedded emails (6/199 cells, 3% density) |
| 5 | fullName | high | header "customer_name" resolves to PII field "fullName" |
| 6 | high | header "customer_email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__dispatch_rush_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This is not a PII-containing file. It contains only internal operational data (order IDs, timestamps, status flags) with no personal information fields. The 'operate_user' column contains internal usernames (e.g., 'lmzheng', 'simon') which are not considered public PII in this context as they appear to be internal system accounts rather than customer identifiers. No emails, phone numbers, names, addresses, or other PII fields are present.
azazie__dispatch_sale_num.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns appear to be internal IDs, numeric codes, timestamps, or non-personal metadata. The file contains order/shipment identifiers, ranks, notes, and system timestamps, but no names, emails, addresses, phone numbers, or other personally identifiable information.
azazie__dispatch_sampling.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/tracking data (sampling IDs, receipt batches, dispatch serial numbers, operators, timestamps, check results). No PII fields are present. All columns are internal IDs, timestamps, or status flags and should be skipped per exclusion rules.
azazie__dispatch_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a shipment tracking log with IDs, statuses, carriers, tracking numbers, and timestamps. All values are either internal shipment IDs, generic status codes, carrier names, alphanumeric tracking numbers, or placeholder dates/timestamps. No personal information such as names, emails, addresses, phone numbers, or dates of birth are present.
azazie__dispatch_shipment_query.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only shipping and tracking information. No PII fields are present. Columns like 'shipping_name' contain generic carrier names ('FEDEX', 'USPS', 'fedex') rather than personal names. All columns are internal identifiers, tracking numbers, or timestamps and must be skipped per rules.
azazie__dispatch_sn_check_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, test codes, timestamps, and status flags. No email, phone, name, address, DOB, SSN, password, or username fields present.
azazie__dispatch_sn_outer_provide_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in first 50 rows. All columns appear to be internal identifiers, timestamps, and flags. Columns: id (internal ID), dispatch_sn (tracking code), outer_provide_id (internal reference), create_time (timestamp), create_user (username), last_update_time (timestamp), is_delete (flag).
azazie__dispatch_sn_outer_provide_notice.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational IDs and timestamps. All columns are non-PII per exclusion rules: 'id' is an internal identifier, 'dispatch_sn' is a transaction code, 'provide_id' is likely an internal reference, 'create_time' and 'last_update_time' are timestamps, 'create_user' is a system user account, and 'is_deal' and 'notice_type' are status flags. No PII fields are present.
azazie__dispatch_sn_print_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, status flags, and timestamps. No PII fields are present. Columns: id (internal ID), provider_id (internal ID), status (flag), create_time (timestamp), last_update_time (timestamp). All columns are non-PII per exclusion rules.
azazie__dispatch_sn_print_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, timestamps, and operational data (e.g., dispatch serial numbers, print counts, timestamps, party IDs). These do not map to any PII fields per the defined schema.
azazie__dispatch_status_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only internal dispatch IDs, timestamps, status codes, and system/user identifiers that do not represent personally identifiable information. All columns are internal operational data (DISPATCH_STATUS_HISTORY_ID, timestamps, STATUS, USER_ID, DISPATCH_LIST_ID).
azazie__dispatch_supply_chain_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal transactional IDs, shipment tracking numbers, dates, financial amounts, and refund values. No PII fields (names, emails, addresses, etc.) are present in this dataset. Columns such as abs_id, DISPATCH_SN, ship_date, provider_id, party_id, and various financial amounts are purely operational and do not contain personally identifiable information.
azazie__dispatch_tag.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible fields are internal identifiers (dispatch_sn), status flags (tag, is_enabled), user references (action_user), and timestamps (create_time, last_update_time). These match the exclusion rules for internal IDs, flags, and timestamps.
azazie__dispatch_to_pp_color_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The data appears to be product catalog or inventory records with numeric IDs and timestamps, but no personal information such as names, emails, phone numbers, addresses, or other PII fields.
azazie__dispatch_warehouse.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns detected. All columns appear to be internal warehouse identifiers, serial numbers, location codes, timestamps, and container IDs. No personal information such as names, emails, phone numbers, addresses, or dates of birth are present in the provided rows.
azazie__dispatchblack.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only product SKU identifiers and binary flags (is_black, is_not_in). No PII fields are present. The pattern shows product variants (c34g4044, AMc34g4044, etc.) with binary status flags, typical of inventory or product catalog data. No email addresses, phone numbers, names, or other personal data appear in the sample.
azazie__distributor.csv3 columns1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | password | high | [4] header is 'password', values are stored credentials |
| 7 | skip | high | [7] header is 'email', values contain '@' symbols |
| 9 | address1 | high | [9] header is 'address', values appear to be street addresses |
Notes: Only 3 columns contain PII: password, email, and address. All others are internal IDs, status flags, or system settings. The 'name' column contains business/distributor names, not personal names, and is therefore skipped per exclusion rules.
azazie__dress_color.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in this dataset. The file contains only color codes and descriptions with timestamps. No email addresses, phone numbers, names, or other personally identifiable information are present.
azazie__dress_color_28.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file contains only product color information (dress_color_id, color_en, color_cn, created_stamp, last_update_stamp). No PII fields are present. All columns represent internal product attributes, color names in English and Chinese, and timestamps.
azazie__dress_color_card.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal product identifiers (IDs), color/fabric codes, and vendor names. Values contain numeric codes and non-personal vendor names in Chinese, with no personal identifiers like names, emails, or addresses.
azazie__dress_color_index.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product color metadata (IDs, English names, Chinese translations, color indexes, and timestamps). No PII fields are present.
azazie__dress_color_product.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns appear to be internal product identifiers (abs_id, dd_id), color names, system flags, user identifiers, and timestamps. None contain email, phone, name, address, DOB, SSN, password, or other PII fields.
azazie__dress_designer.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. The file contains internal designer IDs, references, names (which appear to be designer/staff names, not customer PII), job titles, and timestamps. All columns fall under the exclusion rules: designer_id and designer_ref are internal IDs, designer_name appears to be staff/designer names not customer PII, job is a role/designation, and add_time is a timestamp. None map to any defined PII fields.
azazie__dress_fabric.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/fabric data (dress_fabric_id, fabric_code, fabric_name). No PII fields present. Columns are product identifiers and material descriptions, which are excluded per rules.
azazie__dress_length.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product sizing data and internal timestamps. No PII fields are present. All columns are either numeric size measurements or internal IDs/timestamps which must be skipped per exclusion rules.
azazie__dress_length_asymmetrical.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain product/size data (goods_id, size_code, price ranges, timestamps) — no PII present in this dataset
azazie__dress_length_bride.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product metadata (dress lengths and train types) with no personal identifiable information (PII). All columns are internal product attributes and should be skipped.
azazie__dress_length_junior.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product dimension data (dress length IDs, factory length names, size measurements, and timestamps). No PII fields are present. All columns are skipped per exclusion rules (vehicle/product data, internal IDs, timestamps).
azazie__dress_length_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only product specifications (dress lengths, sizes, measurements) and timestamps. No personal identifiers, contact details, or sensitive data appear in the first 50 rows.
azazie__dress_length_zz.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain product sizing and inventory data (dress length IDs, size measurements, and last update timestamps). No personal information present in the first 50 rows.
azazie__dress_length_zz_bd.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product sizing and inventory data. No PII fields present. All columns are product-related metrics and timestamps, which are excluded by the rules.
azazie__dress_length_zz_bride.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product attributes (dress length types, codes, prices) and no personal identifiable information. All columns are internal product metadata and should be skipped.
azazie__dress_length_zz_junior.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product catalog file containing dress measurements and sizes. No PII fields are present. All columns relate to product attributes (IDs, descriptions, sizes, timestamps) and should be skipped per exclusion rules.
azazie__dress_shawl_relations.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns appear to be internal IDs and product/operational references (abs_id, dress_id, same_id, shawl_id, maintenance_record). No PII fields are present in the first 50 rows. The data represents internal product relationships and maintenance tracking for Azazie's inventory system.
azazie__dress_shawl_relations_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction IDs and timestamps. Columns are rec_id, abs_id, dress_id, same_id, shawl_id, create_time, user_name, rec_type. user_name appears to be internal system usernames (e.g., 'chwang', 'ylzheng') not customer identifiers. No PII fields present.
azazie__dress_size_chart.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only dress sizing and measurement data (dress_chart_id, factory_length_name_id, size, bust, hollow_to_floor, dress_length, units). All values are numeric measurements or internal IDs.
azazie__due_date_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns appear to be internal IDs, status flags, timestamps, and action metadata. No names, emails, phone numbers, addresses, DOB, SSN, passwords, usernames, or other PII fields are present in the first 50 rows.
azazie__due_date_check_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an audit log table showing check detail changes. All columns are internal IDs, timestamps, status flags, or action metadata. No PII is present. Columns like 'action_user' contain system usernames, not customer PII.
azazie__due_date_config.csv1 column239 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | fullName | high | [6] column name 'action_user', values are personal names like 'test101', 'webService', 'xiaoguang.zhang' |
Notes: Only column 6 contains PII (fullName). All other columns contain internal IDs, timestamps, codes, or numerical values with no personal identifiers. Values in column 6 include names and system identifiers, but only the human-readable names qualify as PII.
azazie__duedate_group_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All values are internal IDs, group names in Chinese/English, provider IDs (numeric), usernames (yzhang), and timestamps. No emails, phone numbers, names, addresses, DOB, SSN, or passwords present in the sample.
azazie__duedate_memo_dispatch.csv1 column6 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | fullName | high | [5] values are human names (cwang), column named handler_name |
Notes: Only column 5 contains PII (fullName). All other columns are internal IDs, timestamps, or status codes and must be skipped per exclusion rules.
azazie__duedate_memo_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only two columns: action_id (internal ID) and is_closed (status flag). No PII fields are present. Per exclusion rules, action_id is skipped as an internal ID, and is_closed is a status flag.
azazie__duty_refund_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction IDs, monetary amounts, timestamps, and user identifiers. No PII fields are present. All columns map to skip categories: abs_id (internal ID), refund_id (internal ID), refund_detail_id (internal ID), customer_word (monetary value), create_time (timestamp), action_user (internal user identifier).
azazie__dyeing_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, status flags, timestamps, or product codes. 'apply_user' and 'action_user' appear to be internal system usernames rather than customer PII.
azazie__e_craft.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/technical identifiers and timestamps. No PII fields are present. Columns map to internal database keys, version counters, flags, and timestamps. All columns are marked as skip per exclusion rules (internal IDs, timestamps).
azazie__e_craft_dispatch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal dispatch/production tracking data (IDs, statuses, timestamps). No PII fields such as names, emails, phone numbers, or addresses are present in the first 50 rows. All columns map to internal IDs, statuses, user references, and timestamps which are excluded by policy.
azazie__e_craft_process.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, codes, timestamps, and operational flags. No PII fields are present in this dataset. Columns like 'id', 'craft_primary_key', and 'process_code' are internal system identifiers. 'create_time' and 'last_update_time' are timestamps. 'action_user_id' is an internal user identifier, not a username or email. No personal data such as names, emails, addresses, or dates of birth are found.
azazie__e_craft_process_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, product codes, process metadata, timestamps, flags, and numeric counters — no PII present. The data represents internal production workflow tracking for dress manufacturing rather than customer data.
azazie__e_craft_tmp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal system configuration or template management table. All columns contain internal IDs, names, versions, flags, timestamps, and system metadata. There are no PII fields present. The values appear to be test entries, system template names (in Chinese/English), and numeric codes with no personal information. All columns fall under skip categories: internal IDs, flags, timestamps, and non-PII identifiers.
azazie__e_craft_tmp_process.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, codes, flags, timestamps, and numeric values unrelated to personal identifiable information. This appears to be a processing/operations table from the Azazie database, not customer data.
azazie__e_craft_tmp_process_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, process codes, timestamps, flags, or numeric counters. No names, emails, addresses, phone numbers, DOB, SSN, or other PII fields are present.
azazie__e_craft_tmp_sync_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file contains only numeric IDs, timestamps, and foreign keys. No PII is present in the first 50 rows. All columns are internal identifiers or timestamps, which must be skipped per rules.
azazie__e_dispatch_process.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal process/tracking IDs, timestamps, status flags, and numeric counters. This appears to be an operational logging table for dispatch processes rather than customer data.
azazie__e_dispatch_process_cache.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, flags, or numeric counters typical of operational/process tracking tables. No emails, names, addresses, phones, DOB, or SSN present.
azazie__e_dispatch_process_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal tracking IDs, codes, status flags, and timestamps. No PII fields are present in this dataset.
azazie__e_dispatch_process_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, process codes, or operational flags. No PII fields are present in this structured dataset.
azazie__e_dispatch_process_settlement.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, or process metadata. No PII fields present.
azazie__e_failed_jobs.csv0 rows
File structure
Notes: This is a free-form log file (not structured CSV/TSV) containing JSON payloads embedded in text lines. While it contains internal system IDs and technical metadata, it does NOT contain any actual PII fields like names, emails, or addresses. The sample shows log entries with system identifiers (uuid, user_id), technical routes, and exception messages, but no personal data. This file should be processed as unstructured logs rather than structured PII data.
azazie__e_goods_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product attribute table with no PII fields. All columns are internal IDs, image URLs, and timestamps. No email, phone, name, address, or other PII is present.
azazie__e_permission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only permission/role definitions with internal IDs, codes, and timestamps. No PII fields are present. All columns are internal identifiers, flags, or timestamps and must be skipped per exclusion rules.
azazie__e_process.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal process identifiers, timestamps, and operational flags. No PII fields are present. All columns are internal IDs, codes, status flags, numeric values, or timestamps — none map to any PII categories. The Chinese text in process_name appears to be factory operation descriptions, not personal names or addresses.
azazie__e_process_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. This appears to be an internal process category table with codes, names, and timestamps. All columns are process-related metadata (process_category_id, name, code, etc.) and timestamps (create_time, last_update_time). No personal identifiable information is present in the first 50 rows.
azazie__e_process_category_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a structured log of process category updates with no PII fields. All columns contain internal system codes, JSON payloads with process category metadata, and timestamps. No personal identifiers (names, emails, addresses, etc.) are present in the sample data.
azazie__e_process_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data appears to be a structured log of process updates and changes within a manufacturing or service workflow. The columns include IDs, process codes, JSON payloads describing changes to process states, user IDs, and timestamps. However, there are no identifiable PII fields such as names, emails, phone numbers, addresses, SSNs, DOBs, or passwords present in either the headers or sample values. All visible data pertains to internal business processes, codes, and status updates. Therefore, no PII columns can be mapped from this dataset.
azazie__e_request_log_202011.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an API request log table (request_sn, request_method, request_route, request_body, response, timestamps). No PII columns are present — all columns are internal operational/technical fields (IDs, HTTP metadata, JWT tokens, IP addresses, timestamps). All columns map to skip.
azazie__e_request_log_202012.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an API audit log table containing request IDs, timestamps, IP addresses, and bearer tokens. No PII fields are present. Columns like id, request_sn, user_id are internal identifiers. request_hosts are IP addresses (skip per rules). request_body contains bearer tokens (not passwords) and process metadata. Timestamps (create_time, last_update_time) are not DOB. No emails, names, addresses, phones, or SSNs appear.
azazie__e_request_log_202101.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, timestamps, or technical metadata. No PII fields present. Columns like 'request_body' contain JWT tokens and usernames but these appear to be internal system identifiers rather than customer PII based on values and context.
azazie__e_role.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a roles/permissions table with no PII fields. All columns represent internal system roles and timestamps. No email, phone, name, address, or other PII fields present.
azazie__e_role_permission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps (permission_id, role_id, id_delete, create_time, last_update_time). No PII fields are present. All columns are internal system identifiers or audit timestamps and must be skipped per exclusion rules.
azazie__e_role_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only internal IDs (provider_id, role_id), timestamps (create_time, last_update_time). No PII fields present. All columns are internal identifiers or timestamps which must be skipped per exclusion rules.
azazie__e_user.csv6 columns137 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | [1] header 'user_name', values are alphanumeric handles/screen names |
| 2 | password | high | [2] header 'password', values are MD5 hashes |
| 3 | fullName | medium | [3] header 'name', values mirror username but represent display/full name field |
| 4 | gender | medium | [4] header 'sex', values are numeric gender codes (0/1) |
| 5 | phone | medium | [5] header 'mobile', some values are valid phone numbers (e.g. 13812345678) |
| 8 | high | [8] header 'email', values contain @ signs confirming email addresses |
Notes: 18 columns total; user_id, provider_id, employee_code are internal identifiers; is_order, is_inservice, is_facility, is_enable are internal flags; last_login_time, create_time, last_update_time are timestamps; country_code mapped to skip as it is a system-level code field rather than a user-entered country; id_card column appears empty in sample — skipped due to no values to confirm PII, though it could contain national ID numbers if populated.
azazie__e_user_action_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal ERP audit/action log table (id, user_id, ip, action_log, action_user_id, create_time, last_update_time). All columns are internal system identifiers, IP addresses, JSON audit blobs, and timestamps. No direct PII columns exist — user_id and action_user_id are numeric internal IDs (skip), ip is an IP address (skip), action_log is a JSON audit trail blob (internal operational data, not a mappable PII column), and timestamps are non-DOB dates (skip). No email, phone, name, address, DOB, SSN, password, or other mappable PII fields are present as structured columns.
azazie__e_user_party.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns detected. File appears to be an internal relational table linking users to parties with numeric IDs and timestamps. All columns are internal identifiers or timestamps and contain no personal data.
azazie__e_user_platform.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, platform flags, and timestamps. No PII fields are present. All columns are excluded per rules: 'id' and 'user_id' are internal IDs, 'platform' is a device type flag, 'is_enable' is a status flag, and all date/time columns are non-DOB timestamps.
azazie__e_user_process.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, process codes, flags, timestamps, and user references — no PII present in the first 50 rows. The values are numeric codes, boolean flags, and ISO timestamps. No emails, names, addresses, phones, or other personal data detected.
azazie__e_user_role.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII found. File appears to be an internal admin/privilege table containing only numeric IDs, role IDs, timestamps, and flags. All columns are internal identifiers or operational metadata with no personal data.
azazie__e_work_wage_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order IDs, dispatch IDs, settlement amounts, and timestamps. No PII fields are present. Columns like 'title' contain order status codes or numeric IDs, not personal names. All columns are internal business identifiers or timestamps and are skipped per exclusion rules.
azazie__ebay_export_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File is purely transactional with order numbers, timestamps, user actions, and internal indexes. No PII fields detected. Columns: abs_id (internal ID), order_sn (order number), create_time (timestamp), action_user (username), current_index (counter).
azazie__ecs_abnormal_order_action_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The file contains only internal order IDs, user actions, and timestamps. Columns: id, taobao_order_sn, order_id, type, action_type, action_user, action_note, create_time, last_update_time. No email, phone, name, address, or other PII fields present.
azazie__ecs_additional_fee.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in first 50 rows. File appears to be internal database keys and timestamps (abs_id, zipcode, timestamps, flags). No email, phone, names, addresses, DOB, SSN, or passwords visible. Likely an internal reference table.
azazie__ecs_admin_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only action codes, names, and categories — no PII present. All entries are system permissions or menu items for an admin panel. No columns map to personal data fields.
azazie__ecs_admin_log.csv1 column959 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | emailText | high | free-text column with embedded emails (132/199 cells, 66% density) |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__ecs_admin_message.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a messaging table with no PII fields. All values appear to be numeric IDs or placeholder test strings. Columns: message_id (internal ID), sender_id (internal ID), receiver_id (internal ID), send_date (timestamp), read_date (timestamp), readed (flag), deleted (flag), title (test strings/IDs), message (test strings). No emails, phones, names, addresses, DOB, SSN, passwords, or usernames present.
azazie__ecs_admin_role.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only role management data (role_id, parent_id, role_name, description, role_type). No PII fields present. All columns are internal system identifiers or role metadata.
azazie__ecs_admin_role_permission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain internal system identifiers, permission codes, and timestamp data. No names, emails, addresses, phone numbers, SSNs, DOBs, or passwords present in the first 50 rows.
azazie__ecs_admin_user.csv4 columns2,029 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | username | high | header "user_name" resolves to PII field "username" |
| 4 | high | header "email" resolves to PII field "email" | |
| 5 | password | high | header "password" resolves to PII field "password" |
| 13 | fullName | high | header "real_name" resolves to PII field "fullName" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__ecs_admin_user_201912.csv4 columns249 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | username | high | header "user_name" resolves to PII field "username" |
| 4 | high | header "email" resolves to PII field "email" | |
| 5 | password | high | header "password" resolves to PII field "password" |
| 13 | fullName | high | header "real_name" resolves to PII field "fullName" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__ecs_admin_user_202002.csv4 columns51 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | username | high | header "user_name" resolves to PII field "username" |
| 4 | high | header "email" resolves to PII field "email" | |
| 5 | password | high | header "password" resolves to PII field "password" |
| 13 | fullName | high | header "real_name" resolves to PII field "fullName" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__ecs_admin_user_sso.csv91 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header 'sso_user_name', values are alphanumeric strings with periods |
| 181 | skip | high | [181] header '181', values match E.164 international phone format with country codes and hyphens |
| 182 | skip | high | [182] header '182', values match E.164 international phone format with country codes and hyphens |
| 183 | skip | high | [183] header '183', values match E.164 international phone format with country codes and hyphens |
| 184 | skip | high | [184] header '184', values match E.164 international phone format with country codes and hyphens |
| 185 | skip | high | [185] header '185', values match E.164 international phone format with country codes and hyphens |
| 186 | skip | high | [186] header '186', values match E.164 international phone format with country codes and hyphens |
| 187 | skip | high | [187] header '187', values match E.164 international phone format with country codes and hyphens |
| 188 | skip | high | [188] header '188', values match E.164 international phone format with country codes and hyphens |
| 189 | skip | high | [189] header '189', values match E.164 international phone format with country codes and hyphens |
| 190 | skip | high | [190] header '190', values match E.164 international phone format with country codes and hyphens |
| 191 | skip | high | [191] header '191', values match E.164 international phone format with country codes and hyphens |
| 192 | skip | high | [192] header '192', values match E.164 international phone format with country codes and hyphens |
| 193 | skip | high | [193] header '193', values match E.164 international phone format with country codes and hyphens |
| 194 | skip | high | [194] header '194', values match E.164 international phone format with country codes and hyphens |
| 195 | skip | high | [195] header '195', values match E.164 international phone format with country codes and hyphens |
| 196 | skip | high | [196] header '196', values match E.164 international phone format with country codes and hyphens |
| 197 | skip | high | [197] header '197', values match E.164 international phone format with country codes and hyphens |
| 198 | skip | high | [198] header '198', values match E.164 international phone format with country codes and hyphens |
| 199 | skip | high | [199] header '199', values match E.164 international phone format with country codes and hyphens |
| 200 | skip | high | [200] header '200', values match E.164 international phone format with country codes and hyphens |
| 201 | skip | high | [201] header '201', values match E.164 international phone format with country codes and hyphens |
| 202 | skip | high | [202] header '202', values match E.164 international phone format with country codes and hyphens |
| 203 | skip | high | [203] header '203', values match E.164 international phone format with country codes and hyphens |
| 204 | skip | high | [204] header '204', values match E.164 international phone format with country codes and hyphens |
| 205 | skip | high | [205] header '205', values match E.164 international phone format with country codes and hyphens |
| 206 | skip | high | [206] header '206', values match E.164 international phone format with country codes and hyphens |
| 207 | skip | high | [207] header '207', values match E.164 international phone format with country codes and hyphens |
| 208 | skip | high | [208] header '208', values match E.164 international phone format with country codes and hyphens |
| 209 | skip | high | [209] header '209', values match E.164 international phone format with country codes and hyphens |
| 210 | skip | high | [210] header '210', values match E.164 international phone format with country codes and hyphens |
| 211 | skip | high | [211] header '211', values match E.164 international phone format with country codes and hyphens |
| 212 | skip | high | [212] header '212', values match E.164 international phone format with country codes and hyphens |
| 213 | skip | high | [213] header '213', values match E.164 international phone format with country codes and hyphens |
| 214 | skip | high | [214] header '214', values match E.164 international phone format with country codes and hyphens |
| 215 | skip | high | [215] header '215', values match E.164 international phone format with country codes and hyphens |
| 216 | skip | high | [216] header '216', values match E.164 international phone format with country codes and hyphens |
| 217 | skip | high | [217] header '217', values match E.164 international phone format with country codes and hyphens |
| 218 | skip | high | [218] header '218', values match E.164 international phone format with country codes and hyphens |
| 219 | skip | high | [219] header '219', values match E.164 international phone format with country codes and hyphens |
| 220 | skip | high | [220] header '220', values match E.164 international phone format with country codes and hyphens |
| 221 | skip | high | [221] header '221', values match E.164 international phone format with country codes and hyphens |
| 222 | skip | high | [222] header '222', values match E.164 international phone format with country codes and hyphens |
| 223 | skip | high | [223] header '223', values match E.164 international phone format with country codes and hyphens |
| 224 | skip | high | [224] header '224', values match E.164 international phone format with country codes and hyphens |
| 225 | skip | high | [225] header '225', values match E.164 international phone format with country codes and hyphens |
| 226 | skip | high | [226] header '226', values match E.164 international phone format with country codes and hyphens |
| 227 | skip | high | [227] header '227', values match E.164 international phone format with country codes and hyphens |
| 228 | skip | high | [228] header '228', values match E.164 international phone format with country codes and hyphens |
| 229 | skip | high | [229] header '229', values match E.164 international phone format with country codes and hyphens |
| 230 | skip | high | [230] header '230', values match E.164 international phone format with country codes and hyphens |
| 231 | skip | high | [231] header '231', values match E.164 international phone format with country codes and hyphens |
| 232 | skip | high | [232] header '232', values match E.164 international phone format with country codes and hyphens |
| 233 | skip | high | [233] header '233', values match E.164 international phone format with country codes and hyphens |
| 234 | skip | high | [234] header '234', values match E.164 international phone format with country codes and hyphens |
| 235 | skip | high | [235] header '235', values match E.164 international phone format with country codes and hyphens |
| 236 | skip | high | [236] header '236', values match E.164 international phone format with country codes and hyphens |
| 237 | skip | high | [237] header '237', values match E.164 international phone format with country codes and hyphens |
| 238 | skip | high | [238] header '238', values match E.164 international phone format with country codes and hyphens |
| 239 | skip | high | [239] header '239', values match E.164 international phone format with country codes and hyphens |
| 240 | skip | high | [240] header '240', values match E.164 international phone format with country codes and hyphens |
| 241 | skip | high | [241] header '241', values match E.164 international phone format with country codes and hyphens |
| 242 | skip | high | [242] header '242', values match E.164 international phone format with country codes and hyphens |
| 243 | skip | high | [243] header '243', values match E.164 international phone format with country codes and hyphens |
| 244 | skip | high | [244] header '244', values match E.164 international phone format with country codes and hyphens |
| 245 | skip | high | [245] header '245', values match E.164 international phone format with country codes and hyphens |
| 246 | skip | high | [246] header '246', values match E.164 international phone format with country codes and hyphens |
| 247 | skip | high | [247] header '247', values match E.164 international phone format with country codes and hyphens |
| 248 | skip | high | [248] header '248', values match E.164 international phone format with country codes and hyphens |
| 249 | skip | high | [249] header '249', values match E.164 international phone format with country codes and hyphens |
| 250 | skip | high | [250] header '250', values match E.164 international phone format with country codes and hyphens |
| 251 | skip | high | [251] header '251', values match E.164 international phone format with country codes and hyphens |
| 252 | skip | high | [252] header '252', values match E.164 international phone format with country codes and hyphens |
| 253 | skip | high | [253] header '253', values match E.164 international phone format with country codes and hyphens |
| 254 | skip | high | [254] header '254', values match E.164 international phone format with country codes and hyphens |
| 255 | skip | high | [255] header '255', values match E.164 international phone format with country codes and hyphens |
| 256 | skip | high | [256] header '256', values match E.164 international phone format with country codes and hyphens |
| 257 | skip | high | [257] header '257', values match E.164 international phone format with country codes and hyphens |
| 258 | skip | high | [258] header '258', values match E.164 international phone format with country codes and hyphens |
| 259 | skip | high | [259] header '259', values match E.164 international phone format with country codes and hyphens |
| 260 | skip | high | [260] header '260', values match E.164 international phone format with country codes and hyphens |
| 261 | skip | high | [261] header '261', values match E.164 international phone format with country codes and hyphens |
| 262 | skip | high | [262] header '262', values match E.164 international phone format with country codes and hyphens |
| 263 | skip | high | [263] header '263', values match E.164 international phone format with country codes and hyphens |
| 264 | skip | high | [264] header '264', values match E.164 international phone format with country codes and hyphens |
| 265 | skip | high | [265] header '265', values match E.164 international phone format with country codes and hyphens |
| 266 | skip | high | [266] header '266', values match E.164 international phone format with country codes and hyphens |
| 267 | skip | high | [267] header '267', values match E.164 international phone format with country codes and hyphens |
| 268 | skip | high | [268] header '268', values match E.164 international phone format with country codes and hyphens |
| 269 | skip | high | [269] header '269', values match E.164 international phone format with country codes and hyphens |
| 270 | skip | high | [270] header '270', values match E.164 international phone format with country codes and hyphens |
azazie__ecs_assign_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product attributes, timestamps, or system-generated codes. No personal information such as names, emails, addresses, or phone numbers is present.
azazie__ecs_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product attribute metadata (image sizes, template IDs, flags). No PII fields are present. All columns are internal identifiers, flags, or technical settings.
azazie__ecs_attribute_gfjin11142020.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product attribute table from Azazie's database. All columns contain internal product specification data (attribute IDs, category IDs, measurement names, selection flags, etc.). No PII fields are present — these are purely operational/product metadata fields used for dress sizing and styling configurations.
azazie__ecs_attribute_if_ppml_can_not_sync_again_then_use_it.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product attribute metadata from Azazie, not customer PII. All columns relate to product design attributes (e.g., goodsStyle_sash_size), attribute types, and system flags. No personal data is present.
azazie__ecs_attribute_joey.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product attribute metadata (image sizes, template IDs, flags). No PII fields present. All columns are internal identifiers, flags, or product configuration data.
azazie__ecs_au_shipping_warning.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, order references, or transaction amounts. No PII fields present. Columns like id, order_id, taobao_order_sn, and timestamps contain internal reference codes or dates that are not personally identifiable. country_code shows country codes (AU) but is not address-level PII.
azazie__ecs_azorder_deliver.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided rows. All visible columns contain only order IDs, tracking numbers, timestamps, and other non-personal identifiers. The data appears to be transactional records without any personal information such as names, emails, addresses, or phone numbers.
azazie__ecs_brand.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a product/brand metadata export with no PII present. Columns describe brand identifiers, names, logos, descriptions, URLs, and display settings — all internal business data and non-personal. No customer or user information is visible in the sample row.
azazie__ecs_carriage.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns appear to be internal IDs, numeric codes, weights, and fees — typical logistics/shipping data. No names, emails, addresses, or other personal identifiers present in the first 50 rows.
azazie__ecs_carrier.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a shipping carrier master table, not a customer/PII database. All columns contain carrier operational data (IDs, addresses, phone numbers, websites, carrier names). Column [0] carrier_id is an internal identifier (skip). Columns [1] address, [2] phone_no, [3] web_site, [4] name, [5] name_en all contain carrier business information, not personal PII. No customer records, names, emails, SSNs, DOBs, or personal identifiers are present. This table should not be processed for PII extraction.
azazie__ecs_carrier_bill.csv2 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | receiver | high | [6] header 'receiver', values appear to be names or identifiers |
| 7 | skip | high | [7] header 'phone_no', values include numeric sequences resembling phone numbers |
Notes: Only columns 6 (receiver) and 7 (phone_no) contain PII. All other columns are internal IDs, weights, statuses, or empty fields and are mapped to skip.
azazie__ecs_carrier_bill_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal action logs (action_id, bill_id, status codes, timestamps, and user identifiers). No PII fields are present. The 'action_user' column contains alphanumeric usernames (xmwang, hliu, manager, etc.) which are internal system identifiers, not public-facing usernames or handles, and therefore should be skipped per exclusion rules for internal IDs.
azazie__ecs_category.csv751 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__ecs_check_pangu_sku.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain internal identifiers, timestamps, and system-generated codes with no personal information. The data appears to be product/SKU identifiers and system logs from Azazie's database dump.
azazie__ecs_check_pangu_sku_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains inventory management records (stock levels, SKU codes, timestamps). No PII fields are present — all columns are internal product IDs, quantities, timestamps, and system actions. Columns like 'id', 'uniq_sku', and 'long_code' are internal identifiers; 'note' and 'action_user' are system messages; 'create_time' and 'last_update_time' are operational timestamps. No personal data such as names, emails, or addresses is included.
azazie__ecs_country_operate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers, container codes, timestamps, and status flags. No PII fields are present. Columns like 'id', 'country_id', 'container_id', and timestamps are internal system identifiers or operational metadata, which must be skipped per exclusion rules.
azazie__ecs_customer_ticket_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, codes, and timestamps. Columns like 'action_user' contain generic usernames ('test103') but no email, phone, or other PII fields are present. The data represents internal system metadata (department codes, timestamps, user actions) not customer personal data.
azazie__ecs_customer_ticket_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, order references, timestamps, status flags, or system metadata. Values contain only order numbers, numeric codes, system usernames, and dates — none match PII patterns. Columns like 'action_user' contain system usernames (not human usernames), and all date/timestamp columns are excluded by rules.
azazie__ecs_customer_ticket_order_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is a transactional/order tracking table with no PII present. Columns represent order IDs (order_sn), internal problem codes (one_level_problem, two_level_problem), and order goods IDs (order_goods_id). All values are numeric identifiers or paths to internal files. No personal information such as names, emails, addresses, or other sensitive data is visible in the first 50 rows.
azazie__ecs_customer_ticket_order_department.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, codes, flags, timestamps, or user references that do not contain personally identifiable information per the exclusion rules. 'action_user' appears to be an internal system username (not customer-facing), and timestamps/flags are non-PII.
azazie__ecs_fabric_accessory_bill.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, status codes, and financial amounts. No PII fields are present. Columns like bill_id, party_id, create_user, and timestamps are internal system fields and not personal data. The breach context suggests this is an operational/billing table, not customer PII.
azazie__ecs_fabric_accessory_bill_detail.csv67 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__ecs_fabric_accessory_bill_provider.csv2 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | fullName | high | [2] header 'addressee_name', values include personal names like 'wjjjj', 'testtest', and Chinese names |
| 43 | skip | high | [43] contains valid email address 'yyz@tetx.com' |
Notes: Only two columns contain PII: addressee_name (fullName) and a column with email addresses. All other columns are transactional/internal IDs, amounts, statuses, and timestamps.
azazie__ecs_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All fields represent product metadata, inventory status, pricing, and operational flags. No customer names, contact details, or personal identifiers are present.
azazie__ecs_goods_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a product attributes dataset for an online retailer. All columns contain product metadata (URLs, measurements, flags) and no personal identifiable information (PII) is present. Columns map to product attributes, image URLs, and inventory flags rather than customer data.
azazie__ecs_goods_attr_base.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product attributes, timestamps, or action metadata. 'action_user' contains system identifiers ('WebService'), not usernames. No email, phone, name, address, DOB, SSN, or password data present.
azazie__ecs_goods_fabric.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/order identifiers, timestamps, or operational flags. No PII present. Columns like 'id', 'external_goods_id', 'dress_color', 'pp_uniq_sku', 'pp_color', size consumption metrics, unit of measurement, action_user, and timestamps contain no personal data.
azazie__ecs_goods_fabric_tmp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/order identifiers, timestamps, or non-PII metadata. No PII fields detected.
azazie__ecs_goods_final.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, timestamps, product identifiers, and transaction counters. This is a sales/order tracking table, not customer data.
azazie__ecs_goods_level_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains only product identifiers (ids, weights, units), brand information, and timestamps. No personal data such as names, emails, addresses, or other PII fields are present in the provided rows.
azazie__ecs_goods_sales_situation_settings.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal system settings/tracking data (IDs, flags, timestamps). No PII fields are present. The 'create_user' column contains system usernames not intended for public exposure and should be skipped per policy.
azazie__ecs_goods_sales_situation_settings_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent product metadata and internal operational data (IDs, sales counters, timestamps). No PII present. Columns like 'id', 'external_goods_id', 'goods_name', 'uniq_sku', 'color', and sales metrics contain product identifiers and inventory statistics, not personal customer data. Timestamps ('create_time', 'last_update_time') are internal logs. No emails, names, addresses, or other PII detected.
azazie__ecs_goods_style_in_use.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file contains only product size attributes (S, M, L, 0X) with timestamps. No PII fields are present. This is likely a product inventory or order size tracking table from Azazie's database.
azazie__ecs_inter_carriage.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, operational codes, timestamps, or numeric values (weights/fees). No personal data (names, emails, addresses, etc.) is present in the first 50 rows.
azazie__ecs_inter_carrier_partition.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and operational data (fenqu_id, carrier_id, country_list, fenqu_name). No PII fields are present. The entries appear to be internal system codes for carriers or regions, not customer or personal data. Therefore, no columns map to PII fields.
azazie__ecs_inter_discount.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, transaction amounts, status flags, or operator identifiers. No emails, names, addresses, phone numbers, DOB, SSN, passwords, or usernames present.
azazie__ecs_inter_partition.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, region codes, and timestamps. No PII fields are present. All columns are marked as skip per rules (internal IDs, region data, operational timestamps).
azazie__ecs_move_batch_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product catalog file containing only product identifiers, categories, and pricing. No PII fields present. All columns are internal product data or commercial categories, and therefore should be skipped per exclusion rules.
azazie__ecs_no_goods_fabric.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data contains only product color and identifier information with no personal identifiable information (PII). Columns such as 'id', 'external_goods_id', 'dress_color', 'note', 'action_user', 'create_time', and 'last_update_time' do not map to any PII fields. The 'action_user' field appears to be a system identifier ('WebService') rather than a human user. There are no columns containing email, phone, name, address, date of birth, SSN, password, or other PII fields in this dataset.
azazie__ecs_no_goods_fabric_tmp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only product IDs, color codes, and timestamp data. No personal information (names, emails, addresses, etc.) is present in the visible columns.
azazie__ecs_order_action.csv6,032 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__ecs_order_action_extension.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is an internal order action log table (id, action_id, attr_name, attr_value) containing serialized JSON blobs describing product/order changes (SKUs, dress names, prices, image URLs). No PII fields (names, emails, phones, addresses, DOB, etc.) are present in any column.
azazie__ecs_order_action_show.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal transaction IDs and flags with no PII. All columns represent internal system identifiers (show_id, order_id, action_id) and a binary flag (is_show). No personal information is present in the first 50 rows.
azazie__ecs_order_cstracking.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal tracking / operational fields (order IDs, timestamps, status codes). No PII detected in the sample rows. Columns like ecs_order_cstracking_id, order_id, track_note, etc., contain only internal identifiers, status flags, or placeholder values. No emails, names, addresses, DOB, SSN, or other PII fields are present in this sample.
azazie__ecs_order_cstracking_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal tracking IDs, user identifiers, and timestamps. No PII fields are present. All columns map to skip categories: internal IDs (ecs_order_cstracking_history_id, ecs_order_cstracking_id), reason IDs, result IDs, action_user (internal username), and update_time (timestamp).
azazie__ecs_order_extension.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order IDs, VAT fees, channels, and an empty 'extra_source' column. No PII fields are present. All columns are internal transactional data and should be skipped per exclusion rules.
azazie__ecs_order_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/order identifiers, pricing, status codes, and flags. No PII fields (names, emails, addresses, etc.) are present in the first 50 rows. Columns like rec_id, order_id, goods_id, goods_price, and status_id are all internal system identifiers or transactional data — NOT personal data. The file appears to be a product/order inventory table from Azazie, not a customer PII dump.
azazie__ecs_order_goods_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, status codes, timestamps, and action notes related to order processing. The action_user column contains short alphanumeric strings that appear to be internal system usernames rather than customer-facing identifiers.
azazie__ecs_order_goods_change_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, numeric codes, price data, timestamps, and action metadata. No PII fields (email, phone, name, address, etc.) are present in the first 50 rows. Columns like 'action_user' contain system-generated usernames, not personal identifiers.
azazie__ecs_order_goods_del.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an inventory/order details file with product codes, pricing, and internal system statuses. No PII fields (names, emails, addresses, etc.) are present. All columns are internal IDs, product attributes, financial amounts, or system timestamps that do not contain personal information.
azazie__ecs_order_goods_del_copy1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns relate to product/order metadata (IDs, prices, status flags, timestamps). No names, emails, addresses, or other personal identifiers present in the sample.
azazie__ecs_order_goods_snap.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product metadata, transaction amounts, timestamps, and system flags. snap_desc contains HTML-encoded product edit descriptions, not personal data.
azazie__ecs_order_info.csv6 columns71,039 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 8 | fullName | high | [8] header 'consignee', values are full names |
| 9 | gender | high | [9] header 'sex', values are 'male'/'unknown' — maps to gender |
| 14 | address1 | high | [14] header 'address', values contain street address components |
| 15 | zip | high | [15] header 'zipcode', values are 4-digit Norwegian postal codes |
| 16 | phone | high | [16] header 'tel', values are valid Norwegian phone numbers with country code +47 |
| 18 | high | [18] header 'email', values contain '@' with domain structure |
Notes: 101 columns total, 6 contain PII: fullName, gender, address1, zip, phone, email. All others are order metadata, financial data, timestamps, or internal IDs.
azazie__ecs_order_info_copy1.csv7 columns51,081 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 8 | fullName | high | [8] header 'consignee', values are full names |
| 9 | gender | high | [9] header 'sex', values are 'male'/'unknown' |
| 14 | address1 | high | [14] header 'address', values are full addresses |
| 15 | zip | high | [15] header 'zipcode', values are 4-digit Norwegian postal codes |
| 16 | phone | high | [16] header 'tel', values are Norwegian phone numbers (+47 prefix) |
| 18 | high | [18] header 'email', values contain '@' with domain structure | |
| 31 | fullName | high | [31] header 'inv_payee', values match full names from column 8 |
Notes: 101 columns total, 7 contain PII (names, email, phone, address, zip, gender). Columns 10-13 (country/province/city/district) contain numeric codes rather than human-readable locations and are skipped per rules. Financial/timestamp columns excluded.
azazie__ecs_order_info_snap.csv8 columns63,835 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 9 | country | high | header "country" resolves to PII field "country" |
| 10 | state | high | header "province" resolves to PII field "state" |
| 11 | city | high | header "city" resolves to PII field "city" |
| 13 | address1 | high | header "address" resolves to PII field "address1" |
| 14 | zip | high | header "zipcode" resolves to PII field "zip" |
| 15 | phone | high | header "tel" resolves to PII field "phone" |
| 16 | skip | high | header "mobile" resolves to PII field "phone" |
| 17 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__ecs_order_return_tracking.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns represent internal logistics/tracking identifiers, timestamps, and status codes for return shipments. No names, emails, addresses, or other personal data present.
azazie__ecs_order_shipping_tracking.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, tracking numbers, timestamps, status codes, and operational metadata. No names, emails, addresses, or other personal data present.
azazie__ecs_order_status_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a log or transaction table with no PII fields. Columns include internal IDs (id, order_id), status codes, empty list placeholders, timestamps, and system identifiers. No personal data present.
azazie__ecs_other_subsidy.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal tracking data (IDs, statuses, timestamps, notes in Chinese/English). No PII fields detected. All columns are non-PII according to the exclusion rules: internal IDs (party_id), status flags, timestamps, and free-form notes/descriptions.
azazie__ecs_other_subsidy_bill.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, transaction metadata, timestamps, and status flags — no PII present. 'bill_name' contains invoice identifiers (PPML-QTTK-...) not personal names. 'create_user' and 'party_id' are internal numeric IDs. Timestamps and numeric values are operational data only.
azazie__ecs_other_subsidy_bill_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided data. The dataset appears to contain only internal transaction IDs, amounts, and JSON strings with non-PII values (e.g., '稍等深V的11we', '电脑', etc.). No identifiable personal information such as names, emails, addresses, or phone numbers is present in the visible columns.
azazie__ecs_oukoo_erp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, transaction flags, timestamps, or numeric counters. Columns like 'purchaser' and 'action_user' contain only a single username 'xmwang' across all rows, likely an admin account, not customer PII.
azazie__ecs_oukoo_erp_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be SQL statements from an ERP system, containing INSERT and UPDATE operations on tables like `ecs_oukoo_erp`, `ecs_order_info`, and `ecs_order_goods`. There are no columns that map to PII fields such as email, phone, dob, etc. The data consists of order IDs, timestamps, user actions, and internal system identifiers. No PII is present in the visible rows.
azazie__ecs_oukoo_erp_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file appears to be a system log with internal IDs (log_id, in_sn, out_sn), user identifier (log_user), and timestamps (log_datetime). No personal information such as names, emails, addresses, or other PII is present in the visible columns.
azazie__ecs_oukoo_po_return.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain only internal IDs, transaction flags, amounts, timestamps, and statuses. No names, contact info, or personal identifiers present.
azazie__ecs_pangu_fix_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The data appears to be internal transaction logs with IDs and timestamps, but no personal information such as names, emails, addresses, or other PII fields is present in the visible columns.
azazie__ecs_pay_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order IDs, amounts, and flags — no personal or identifiable information present. All columns are transactional/internal IDs and numeric values. No PII fields detected.
azazie__ecs_paycode_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only payment method codes and internal identifiers. No PII fields are present. All columns are internal payment codes, flags, or IDs which must be skipped per exclusion rules.
azazie__ecs_payment.csv1 column69 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | emailText | high | free-text column with embedded emails (69/161 cells, 43% density) |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__ecs_pp_inv.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file contains only inventory/operational data (product SKUs, quantities, timestamps). No personal or identifiable information is present in any column. All columns map to skip categories (internal IDs, counters, timestamps).
azazie__ecs_pp_sku_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain product metadata (SKU, names, colors, sizes, timestamps). No PII fields detected. Columns 0-12 are internal product identifiers, inventory data, and system timestamps — all excluded by policy. No emails, names, addresses, or other personal data present in the sample.
azazie__ecs_print_template.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, timestamps, and codes. No PII fields present. Columns map to internal identifiers, country codes, timestamps, and usernames (xiaoguang.zhang appears to be an internal username but not a user-facing PII field). All columns are excluded per rules: 'party_id', 'type', 'file_id', 'code', 'country_id', 'create_time', 'last_update_time', 'action_user' are internal IDs, timestamps, or non-PII identifiers.
azazie__ecs_print_template_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only operational/transactional records with internal IDs, timestamps, and status codes. No PII fields (names, emails, addresses, etc.) are present. All columns map to skip categories: internal IDs, timestamps, flags, and codes.
azazie__ecs_provider.csv4 columns1,619 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | address1 | medium | [4] header 'address', values contain street addresses (though first value is '2', remaining are Chinese street addresses) |
| 6 | fullName | medium | [6] header 'contact_person', values are Chinese personal names (王佳, 薛文斌, 顾力平, 陆毅) |
| 7 | phone | high | [7] header 'phone', values are phone numbers (13701772177, 52868883/13916836022) |
| 8 | high | [8] header 'email', values contain email addresses (guliping-jh@yahoo.com.cn, yuzhimin@dopod.com) |
Notes: This appears to be a supplier/provider registry table from a Chinese e-commerce platform, not an Azazie customer table. Most columns are business/operational data (company names, bank accounts, order types, status flags). Contact person names and contact details (phone, email, address) are mapped as PII. Bank account numbers in column 14 are financial data but no 'bankAccount' field type is available — skipped. Provider/company names in column 1 are business entities, not personal names — skipped per exclusion rules.
azazie__ecs_provider_action.csv1 column326 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header 'provider_action_user', values are alphanumeric strings likely usernames |
Notes: Only column 2 (provider_action_user) contains PII (username). All other columns contain internal IDs, timestamps, and non-PII status flags.
azazie__ecs_provider_addressee.csv1 column31 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | fullName | high | [2] header 'addressee_name', values are full names or identifiers like '刘运单' and 'Gillian Harper' |
azazie__ecs_provider_beneficiary.csv7 columns13 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | lastName | high | [1] header 'last_name', values are non-Western characters consistent with surnames |
| 2 | firstName | high | [2] header 'first_name', values are non-Western characters consistent with given names |
| 4 | phone | high | [4] header 'personal_mobile_number', values are 11-digit Chinese mobile numbers |
| 16 | state | high | [16] header 'state', values are Chinese province names like '北京市' |
| 17 | city | high | [17] header 'city', values are Chinese city names like '北京市' |
| 18 | address1 | high | [18] header 'street', values appear to be street-level address fragments |
| 19 | zip | medium | [19] header 'postcode', values match Chinese postal code patterns (5-6 digits) |
Notes: Mapped 7 PII columns: lastName, firstName, phone, state, city, address1, zip. All other columns are internal business identifiers, timestamps, or non-PII codes.
azazie__ecs_provider_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. File contains only internal provider/category IDs and status flags. All columns map to internal business identifiers and numeric status codes, none contain personal information per the defined PII field types.
azazie__ecs_provider_category_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal IDs, usernames (non-PII), and timestamps. The 'provider_category_action_user' column contains generic usernames (xmwang, pangou, etc.) which are not considered PII per exclusion rules. Timestamps and numeric IDs are internal operational data only.
azazie__ecs_provider_contact_person.csv6 columns1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | fullName | high | [2] header 'name', values are short strings that could be names |
| 4 | phone | high | [4] header 'phone_no', values are numeric strings matching phone number format |
| 5 | skip | high | [5] header 'email', column exists and may contain email addresses |
| 6 | username | high | [6] header 'qq', values are likely social media handles or usernames |
| 7 | username | high | [7] header 'msn', values are likely social media handles or usernames |
| 8 | skip | high | [8] header 'birthday', column exists and may contain date of birth information |
Notes: This file appears to contain personal information for providers/contacts. Columns 0,1,3,9-13 are internal IDs, flags, or non-PII data and have been excluded. Columns 2,4,5,6,7,8 contain PII and have been mapped accordingly.
azazie__ecs_provider_drafts.csv1 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__ecs_provider_mail_config.csv3 columns1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | high | [1] header 'az_mail', values are valid email addresses | |
| 2 | high | [2] header 'bl_mail', values are comma-separated lists of email addresses | |
| 3 | high | [3] header 'ppml_mail', values are comma-separated lists of email addresses |
Notes: CSV file with 4 columns; 3 columns contain email addresses (primary, billing, and payment method linked emails). Column 4 is a flag ('is_useful').
azazie__ecs_provider_oc_check.csv47 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__ecs_provider_provider_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns present. This appears to be an internal reference table mapping absolute IDs to provider attributes. All columns are numeric IDs and flags (is_used), with no personal or identifiable information.
azazie__ecs_provider_uploaded.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system tracking records (provider uploads metadata). No PII fields present. Columns are internal IDs, statuses, file types, sizes, operators, timestamps, and filenames. All are non-PII operational data.
azazie__ecs_purchase_bill.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal transaction IDs, statuses, amounts, and operational codes. No PII fields detected. Columns like 'user' and 'purchaser' appear to be internal user handles (xmwang) not actual usernames or emails. No emails, phone numbers, names, addresses, DOB, SSN, or passwords present in the sample. This is purely transactional accounting data.
azazie__ecs_purchase_bill_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a pure transactional table with only internal purchase IDs (purchase_bill_id), ERP system IDs (erp_id), and type codes (type). No PII fields are present. All columns are internal identifiers or flags and must be skipped per exclusion rules.
azazie__ecs_region.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only geographic region IDs and names (China administrative divisions), which are not considered personally identifiable information under the defined schema. All columns represent internal region codes and display names without any personal data.
azazie__ecs_reserved_fail_sku.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields present. All columns are internal IDs, order identifiers, timestamps, inventory counters, and status flags. The data represents product/order tracking metadata rather than customer personal information.
azazie__ecs_role_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only role permissions and internal action codes, no PII fields. Columns map to system permissions only.
azazie__ecs_sessions.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to contain only session keys, timestamps, and internal admin IDs. The 'data' column contains serialized PHP arrays with facility IDs and role lists, but no personal identifiers. All IP addresses are internal (192.168.x.x) and not considered PII in this context.
azazie__ecs_shipping.csv3 columns1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 14 | fullName | high | [14] header 'contact_name', values appear to be personal names |
| 15 | high | [15] header 'contact_email', contains '@' symbol | |
| 16 | phone | high | [16] header 'contact_phone', values are 11-digit numeric strings |
Notes: Only three columns contain PII: contact name (fullName), contact email, and contact phone. All other columns are shipping configuration data, internal IDs, or flags and should be skipped.
azazie__ecs_shipping_area.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only shipping configuration data (shipping areas, fees, weights). No PII fields are present. All columns map to internal business logic or configuration parameters.
azazie__ecs_shipping_batch_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system fields (IDs, flags, timestamps, numeric ranges). No PII present. Columns like create_user/update_user contain system usernames (not customer usernames), and all other columns are numeric codes, weights, timestamps, and boolean flags. No emails, names, addresses, phones, DOB, SSN, passwords, or other PII fields identified.
azazie__ecs_shipping_batch_weight.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in this dataset. File contains only internal inventory/product weight records with SKU codes, weight values, deletion flags, and user/timestamp audit fields. No personal information present.
azazie__ecs_shipping_change.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to contain only transactional data (order IDs, change IDs, shipping IDs, timestamps, and action users). No email addresses, phone numbers, names, addresses, DOBs, SSNs, passwords, usernames, or other PII fields are present in the first 50 rows. The 'action_user' field contains only short alphanumeric strings (e.g., 'fxie', 'xmwang') that do not resemble usernames or other PII.
azazie__ecs_shipping_change_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a non-PII file containing only internal reason codes and descriptions for order issues. No personal identifiable information is present in any column.
azazie__ecs_shipping_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order identifiers and timestamps. All columns are internal IDs, flags, or timestamps and do not contain any PII fields. Therefore, no columns are mapped to PII fields.
azazie__ecs_shipping_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order identifiers, shipping codes, status flags, timestamps, and XML payloads. No PII fields (email, phone, name, address, etc.) are present. All columns map to skip categories: internal IDs, transaction codes, timestamps, status flags, and unstructured XML data.
azazie__ecs_shipping_region_name.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the first 50 rows. Columns present are identifiers (id, shipping_id) and region information (region_id, region_name), which are not considered PII under the defined rules.
azazie__ecs_shipping_zone.csv3 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | country | high | [2] header 'country', values are country names |
| 3 | state | high | [3] header 'province', values are provinces/states |
| 4 | city | high | [4] header 'city', values are city names |
Notes: Only location-related PII columns (city, state, country) identified. Other columns appear to be internal IDs, timestamps, or zone codes without personal data.
azazie__ecs_shipping_zone_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only transactional/order data fields (ID, container/shipping IDs, zone classifications, weight, pricing, currency, user action, timestamps). No personal identifiers, contact info, or sensitive data present in the header or sample rows.
azazie__ecs_shop_config.csv18 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 114 | skip | high | [114] header 'service_email', values contain '@' symbol: hqqi@ouku.com |
| 503 | username | high | [503] header 'smtp_user', values are potential usernames: ouku |
| 504 | password | high | [504] header 'smtp_pass', values appear to be passwords: oukooMail0705 |
| 505 | skip | high | [505] header 'smtp_mail', values contain '@' symbol: noreply@notice.oukupai.com |
| 801 | skip | high | [801] header 'sms_shop_mobile', values are numeric phone-like strings: 0 |
| 831 | skip | high | [831] header 'order_blacklist', values contain '@' symbol: consignee=阿布 mobile=13818900165 mobile=13818900165 |
| 843 | skip | high | [843] header 'callcenter_phone', values are numeric phone-like strings: 4008206206 |
| 852 | skip | high | [852] header 'callcenter_exclude_channel', values contain '@' symbol: erpchenlei@163.com |
| 1029 | skip | high | [1029] header 'az_sender_email_setting', values contain '@' symbol: azcaiwu@i9i8.com,rewrwerwerwerwer |
| 1112 | skip | high | [1112] header 'ppml_sender_email_setting', values contain '@' symbol: test@i9i8.com,rewrwerwerwerwerxgfd^&*(<>?,./._dfg大公司 |
| 1136 | skip | high | [1136] header 'az_order_deliver_report_03_02', values contain '@' symbol: ["bwang3@i9i8.com,yzhang14@i9i8.com"] |
| 1143 | skip | high | [1143] header 'ppml_overseas_stock_setting', values contain '@' symbol: leopard.wang@i9i8.com,jacky.hu@i9i8.com,minzhi.chen@i9i8.com |
| 1158 | skip | high | [1158] header 'provider_price_alert_mail', values contain '@' symbol: ["minzhi@i9i8.com"] |
| 1183 | skip | high | [1183] header 'bl_daily_operate_email_peter.xing@i9i8.com', values contain '@' symbol: peter.xing@i9i8.com |
| 1184 | skip | high | [1184] header 'bl_daily_operate_email_wswan@i9i8.com', values contain '@' symbol: wswan@i9i8.com |
| 1185 | skip | high | [1185] header 'bl_daily_operate_email_hmhe@i9i8.com', values contain '@' symbol: hmhe@i9i8.com |
| 1188 | skip | high | [1188] header 'bl_daily_operate_email_daly.tian@i9i8.com', values contain '@' symbol: daly.tian@i9i8.com |
| 1195 | skip | high | [1195] header 'bl_daily_operate_email', values contain '@' symbol: ["peter.xing@i9i8.com","wswan@i9i8.com","hmhe@i9i8.com","daly.tian@i9i8.com","daly1.tian@i9i8.com"] |
Notes: Identified 17 PII columns across emails, phone numbers, passwords, and usernames. All values conform to expected PII patterns, with explicit '@' symbols for emails and numeric strings for phones.
azazie__ecs_stock_up_statistics.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be product/sales metrics, IDs, and timestamps. No personal information such as names, emails, addresses, or other PII fields are present in the first 50 rows.
azazie__ecs_usage_goods_final.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be an inventory or operational table with internal IDs, timestamps, product codes, and system metadata. All columns are non-PII per exclusion rules (internal IDs, timestamps, product identifiers, system flags).
azazie__ecs_user_rank.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only rank/points information with no personal or identifiable data. All columns are internal business metrics (rank_id, rank_name, min_points, min_price, discount, etc.) and must be skipped per exclusion rules for company/business data.
azazie__ecs_user_role.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This is a purely internal transactional table containing only database IDs, role mappings, and flags. No PII fields are present — all columns are internal identifiers or boolean flags (is_used). The values are numeric IDs and single-character status codes, with no names, addresses, emails, or other personal data. Therefore, no columns map to any PII categories.
azazie__ecs_users.csv8 columns1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | [2] header 'email', values contain '@' | |
| 3 | username | high | [3] header 'user_name', values look like usernames |
| 4 | password | high | [4] header 'password', contains raw password data |
| 7 | gender | high | [7] header 'sex', values '0' likely represent gender |
| 8 | dob | high | [8] header 'birthday', values in YYYY-MM-DD format |
| 21 | skip | medium | [21] header 'user_mobile', values appear to be phone numbers |
| 27 | zip | medium | [27] header 'zipcode', contains potential postal codes |
| 37 | phone | medium | [37] header 'user_tel', contains potential telephone numbers |
Notes: 39 columns total, 8 contain PII. Columns with 'Company', 'Business', 'CompanyName', 'BusinessPhone', 'BusinessName', 'employer', 'FaxNumber', 'user_id', 'salt', 'user_money', 'pay_points', 'rank_points', 'address_id', 'reg_time', 'last_time', 'last_ip', 'visit_count', 'user_rank', 'is_special', 'user_realname', 'user_address', 'user_profile', 'user_fav_cate', 'user_fav_brand', 'user_products', 'track_id', 'reg_source', 'reg_province', 'reg_recommender', 'email_valid', and 'email_validate_point_id' were skipped per exclusion rules
azazie__editor_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent product attribute metadata (e.g., dress silhouettes) and operational flags. No PII fields present. Columns like attr_id, parent_id, cat_id, attr_name, attr_type, attr_values, sort_order, is_delete, is_show, display_order, last_update_time, and display_filter are internal product catalog identifiers and settings.
azazie__editor_attribute_backup.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product attribute table from Azazie (Silhouette轮廓裙型 means 'Silhouette skirt type' in Chinese). All columns are internal product metadata: attribute IDs, types, values, and display settings. No PII fields are present.
azazie__editor_attribute_languages.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product attribute data (silhouette, neckline, hemline, fabric, etc.) with no personal or identifiable information. No PII fields are present.
azazie__editor_attribute_languages_backup.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a product attribute configuration table for dresses, containing only product metadata (silhouette types, necklines, hemlines, fabrics, embellishments, etc.). There are no personal identifiers or PII fields present in this dataset. All columns relate to product design specifications and styling options.
azazie__editor_bridesmaid_sample_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only product attribute data (e.g., 'upper_body', 'dress', 'sleeve', 'accessory') and internal IDs. No personal information such as names, emails, addresses, or other PII fields is present in the first 50 rows.
azazie__editor_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent product/category metadata (names, IDs, configurations). No PII fields present. All columns are skipped per exclusion rules (company/product data, internal IDs, timestamps).
azazie__editor_category_backup.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent product/category metadata (category IDs, names, descriptions, configuration parameters). No PII fields are present. Columns like cat_name and cat_desc contain product-related text, not personal information. Timestamps (last_update_time) and internal IDs (cat_id, parent_id, erp_cat_id, etc.) are non-PII operational data.
azazie__editor_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII found in first 50 rows. All columns contain product metadata (IDs, SKUs, pricing, inventory status, timestamps), images, and operational flags. No customer contact information, names, or sensitive data present in the visible columns.
azazie__editor_goods_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file contains only product attribute data (skirt styles, embellishments, etc.) with no personal identifiable information. All columns represent product characteristics and internal product IDs.
azazie__editor_goods_attr_backup.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file containing product attribute mappings for dresses, but it contains no PII fields. All columns represent product IDs, attribute IDs, attribute values (style descriptions), flags, and timestamps. No personal information is present.
azazie__editor_goods_attr_languages.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be purely product/attribute data (size ranges, timestamps) with no personal information. All columns represent internal product attributes (IDs, values, languages, timestamps) and contain no PII fields.
azazie__editor_goods_backup.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be product metadata, internal IDs, inventory flags, and timestamps. Values contain only product codes, SKU numbers, descriptions, pricing, and operational status flags. No personal identifiers (names, emails, addresses, etc.) are present in the sample.
azazie__editor_goods_color_style.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a product catalog or inventory listing from Azazie, containing only product identifiers (style_id, goods_id), color information, timestamps, and thumbnail flags. No PII fields are present in this dataset. The columns represent product SKUs, color variants, creation/update timestamps, and thumbnail availability flags — all operational data without any personal customer information.
azazie__editor_goods_color_style_ontime.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be a product catalog or inventory dump containing only product IDs, color codes, timestamps, and site metadata. All columns fall under exclusion rules (internal IDs, product data, timestamps).
azazie__editor_goods_gallery.csv1 column4,279,633 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 18 | username | high | [18] header 'user_name', values appear to be usernames |
Notes: Only column 18 (user_name) contains PII (username). All other columns are internal identifiers, timestamps, product metadata, or flags and do not contain personal identifiable information.
azazie__editor_goods_gallery_backup.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, URLs, timestamps, flags, or technical metadata. The column 'user_name' is empty in the sample and likely unused in this table; if populated it would map to username, but current values show no PII. This appears to be an image/product metadata table from the Azazie database, not customer data.
azazie__editor_goods_project.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are product-related data (IDs, pricing, timestamps, flags). No PII fields present. This is a product inventory table from Azazie.
azazie__editor_goods_project_backup.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product catalog data (goods_id, project_name, image paths, pricing, timestamps). No PII fields are present. Columns map exclusively to product metadata and internal business identifiers, which are excluded by policy.
azazie__editor_goods_project_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and timestamps. No PII fields are present. The columns 'goods_id', 'project_name', and 'last_update_time' are internal business identifiers and timestamps, which must be skipped per exclusion rules. There are no email addresses, phone numbers, names, addresses, or other PII in the sample.
azazie__editor_goods_sample_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal product/operation identifiers and timestamps. No PII fields detected. The 'user' column contains only a generic username placeholder ('yzhang') and no actual personal identifiers.
azazie__editor_goods_v3_az.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal IDs, timestamps, and product metadata. Columns: id (internal ID), goods_id (product ID), cat_id (category ID), deadline (date), creater (username), create_time (timestamp), last_update_time (timestamp).
azazie__editor_goods_v3_az_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal IDs (dispatch_sn), status flags, numeric identifiers (v3_az_id), and timestamps (create_time). No personal data such as names, emails, phone numbers, or addresses is present in the first 50 rows.
azazie__editor_style.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product attribute table from Azazie, containing style and category IDs, attribute names like 'Color', values such as 'White', parent IDs, display flags, timestamps, prices, and party IDs. No PII fields are present — all columns relate to product configuration and internal product data.
azazie__email_change.csv2 columns58 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | high | unlabeled column — sampled values parse as email addresses | |
| 2 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__email_log.csv1 column407,226 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | high | [1] header 'email', values are JSON arrays of email addresses like nat.meng@gaoyaya.com and xiaoyu.wang@gaoyaya.com |
Notes: This appears to be an internal alert/notification log table (likely a message queue or error notification table). Column 2 'title' contains system alert titles (PHP ERROR messages, Chinese notification strings) — not honorific titles and not PII. Columns 3-4 are timestamps. Only the email column contains PII (internal staff/admin emails at gaoyaya.com stored as JSON arrays).
azazie__email_operate_log.csv1 column10 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | high | [3] header 'action_user', values are names like 'frankie.fu', 'zhaoyong' |
Notes: Only column 3 (action_user) contains PII. The email_list field in JSON payloads contains emails, but it's nested JSON and not a dedicated column — handled elsewhere. All other columns are internal IDs, timestamps, or JSON payloads without direct PII mapping.
azazie__email_reciever.csv1 column335 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | [2] header 'email', values are valid email addresses with @ signs and domains (canola.ge@i9i8.com, maggie.shi@i9i8.com, etc.) |
Notes: This appears to be an internal email routing or distribution table with columns 'id' (skip: internal counter), 'email_id' (skip: internal grouping ID), and 'email' (PII). Column 0 and 1 are non-PII structural metadata. Only column 2 contains searchable PII.
azazie__email_subscribe.csv2 columns32 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | high | header "email" resolves to PII field "email" | |
| 2 | username | high | header "user_name" resolves to PII field "username" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__engine_cost.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a system cost configuration table from the database. It contains internal system metrics and cost parameters, with no PII fields present. All columns are internal system identifiers, cost values, timestamps, and comments — none contain personal or identifiable information.
azazie__enquiry.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal business/inquiry tracking data (IDs, product attributes, timestamps, statuses). No PII fields present. Columns like creator appear to be internal usernames (yzhang/xm-yifu) not public-facing identifiers. Timestamps (created_stamp/last_update_stamp) are operational logs. All values are non-personal business metadata.
azazie__enquiry_accessory_cost.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional data (IDs, quantities, prices) with no personal identifiable information. All columns represent internal order/enquiry identifiers, numeric quantities, and monetary values. No PII fields detected.
azazie__enquiry_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product attribute mappings (e.g., fabric types, trims) with no personal or identifiable information. All columns map to internal product metadata and should be skipped.
azazie__enquiry_fabric_cost.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be a transactional ledger file containing only order IDs, provider IDs, usage counts, prices, subtotals, and totals. All columns represent internal business metrics and identifiers, with no personal information present in the first 50 rows.
azazie__enquiry_image.csv1 column0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 9 | username | high | [9] header 'username', values appear to be alphanumeric strings likely used as login identifiers |
Notes: Only column 9 (username) contains PII. All other columns are internal IDs, file metadata, timestamps, or flags and should be skipped per rules.
azazie__enquiry_labour_cost.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional data (prices, totals) with internal IDs and references. No PII fields are present. All columns map to internal business identifiers, monetary values, and notes — none constitute personal identifiable information per the defined schema rules.
azazie__enquiry_other_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional data (IDs, prices, costs) with no PII fields. All columns map to internal IDs, monetary values, or reference codes. No emails, names, addresses, or other personal data are present.
azazie__enquiry_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, product attributes, timestamps, flags, or other non-PII operational data. No PII fields present.
azazie__enter_warehouse_intercept.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, status flags, timestamps, and order references. No PII fields are present in this dataset.
azazie__entry_declaration.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product declaration data for Azazie's inventory. All columns appear to be product metadata, pricing, and customs information. There are no personal identifiable information (PII) fields present. Columns like 'create_by' and 'update_by' contain usernames, but these are internal system users rather than customer PII. All other columns are product codes, descriptions, pricing, and timestamps which are not considered PII under the defined rules.
azazie__entry_declaration_cost.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain only non-PII data: hs_code, cost figures, country codes, usernames, and timestamps. No personal identifiers (email, phone, name, address, etc.) present in the first 50 rows.
azazie__entry_declaration_item.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All visible fields are internal IDs (id, type_id, entry_declaration_id, item_id), user identifiers (create_by, update_by), timestamps (create_time, last_update_time), and a static party_id value. None contain personal information such as names, emails, addresses, or other protected data types per the defined schema.
azazie__envelope_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product/price table with no PII fields. Columns are internal IDs, price values, timestamps, and flags. No email, name, address, phone, or other PII present.
azazie__envelope_goods_purchase_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product attribute data (envelopes, colors) and operational metadata. No PII fields are present. Columns map to product attributes, pricing flags, timestamps, and operator identifiers — all non-personal data. 'operator' is an internal username but not a public-facing identifier; per rules, internal IDs are skipped.
azazie__epacket_post_code.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to contain only postal code data (post_code and zip_code). Neither column maps to any defined PII fields. post_code values appear to be internal codes (e.g., '1F,000') and zip_code values are numeric but do not follow standard postal code patterns. No PII is present in this dataset.
azazie__erp_check_getbatchinvcosterrorlist.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, transaction metadata, timestamps, and operational flags. No names, emails, addresses, phone numbers, or other personal identifiers are present.
azazie__erp_check_getbatchrepeatorders.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order identifiers, product IDs, quantities, and timestamps. No PII fields (names, emails, addresses, etc.) are present in the visible data. Columns are purely transactional and operational.
azazie__erp_check_getconfirmerrororders.csv1 column58 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__erp_check_geterrorcontainerorderids.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order/shipment metadata: IDs, timestamps, status codes, and container references. No PII fields are present. All columns are internal IDs, transaction references, or timestamps — none map to email, name, address, etc. Therefore, no columns are classified as PII.
azazie__erp_check_geterrorspellbarcodes.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal identifiers, codes, and timestamps. No names, emails, addresses, phone numbers, DOBs, SSNs, passwords, usernames, or other PII fields are present in the provided rows.
azazie__erp_check_getgoodsisbatcherrorlist.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, SKU codes, and timestamps. No PII fields are present. Columns map to internal product/warehouse data and are all skippable per rules.
azazie__erp_check_getinverrorlist.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an inventory/stocking table with no PII fields. Columns contain internal IDs, SKU codes, quantities, timestamps, and inventory status. All columns are excluded per rules: IDs, inventory data, timestamps, and counters are non-PII.
azazie__erp_check_getkucunreserveerror.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. All visible columns appear to be internal identifiers (order_item_id, dispatch_sn), timestamps (create_time, last_update_time), and other non-PII operational data. No emails, phone numbers, names, addresses, or other PII fields are present in the visible data.
azazie__erp_check_getmpsnotdeletedisptchs.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain internal IDs, timestamps, product codes, statuses, and operational flags. Values are numeric IDs, date/time stamps, product descriptions, and system statuses — none contain personal information such as names, emails, addresses, or phone numbers.
azazie__erp_check_getnodwdispatchs.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The data appears to be order/shipment tracking numbers (DISPATCH_SN), statuses, and timestamps with no personal identifiable information visible.
azazie__erp_check_getnompsdispatchimgs.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the provided rows. The file appears to contain only order IDs, timestamps, and image URLs, which do not contain personal information such as names, emails, phone numbers, addresses, or other PII fields.
azazie__erp_check_getobdmmulti.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns appear to be internal identifiers, transaction counters, and timestamps. No PII fields are present in the first 50 rows. Columns: id (internal ID), dispatch_sn (tracking number), total (count), max_create_time (timestamp), create_time (timestamp), last_update_time (timestamp). All columns are excluded per rules for internal IDs and timestamps.
azazie__erp_check_getoglcerr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only product inventory data (SKU, stock levels, timestamps) with no personal or identifiable information. All columns map to internal business metrics and inventory tracking.
azazie__erp_check_getpperrbatchcheckprice.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product pricing and inventory data (SKU, price, dates). No PII fields are present. All columns are internal business metrics and timestamps, which are excluded per policy rules.
azazie__erp_check_getppnotshippedorders.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, order references, status flags, and timestamps. No email, phone, name, address, or other PII fields present in the sample.
azazie__erp_check_getrushordernotreserve.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, order identifiers, timestamps, status codes, and product references. This is typical transactional data from an e-commerce platform with no customer personal information exposed.
azazie__erp_check_getsampleoversalelist.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible fields are order identifiers, status codes, numeric values, and timestamps. No emails, names, addresses, phone numbers, or other personal data appear in the sample.
azazie__erp_check_getsamplerepeatorders.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order identifiers and timestamps. No PII fields are present. Columns: id (internal ID), taobao_order_sns (transaction references), rec_id (internal record ID), dispatch_sn (shipping reference), total (order count), create_time (timestamp), last_update_time (timestamp). All columns are internal identifiers or timestamps — no personal data exposed.
azazie__erp_check_getshippedbutnotoutorders.csv1 column175 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__erp_check_getshippednotoutlist.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. All columns appear to be order identifiers, timestamps, and status flags with no personal information.
azazie__erp_check_getshippmentshippingerrlist.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal IDs (taobao_order_sn), timestamps (order_time, create_time, last_update_time), and internal codes (shipping_id, shipment_type_id). These match the exclusion rules for internal IDs and timestamps.
azazie__erp_check_gettjprocessitems.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be transactional log data with internal IDs, status flags, and timestamps. Values like 'joseph' and 'tim' are likely internal usernames or transaction codes, not personal names.
azazie__erp_check_gettransferboxerr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (box_code, transfer_box), timestamps (create_time, last_update_time), and numeric codes. No PII fields are present. All columns are excluded per rules (company/business references, internal IDs, timestamps).
azazie__erp_check_gettransfernoreservelist.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present. Columns 'id' and 'order_sn' are internal identifiers, and 'create_time' and 'last_update_time' are timestamps, which are excluded per rules.
azazie__erp_check_gettransferoutrepeat.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, order/transactional data, timestamps, and product identifiers. No PII fields present.
azazie__erp_email.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This appears to be a log or alert configuration file, not customer data. Columns contain system alert identifiers, descriptions, and status flags — no PII fields are present. The 'email_key' column name is misleading; values are internal system keys, not email addresses.
azazie__erp_email_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a list of email notification templates and configurations. It does not contain actual customer data or PII. The columns are: id (internal ID), email_key (template identifier), email_title (template title), email_summary (template summary), is_test (flag), is_open (flag), create_time (timestamp), last_update_time (timestamp). No PII fields are present in this dataset.
azazie__erp_email_setting_reciever.csv1 column75 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | [2] contains valid email addresses with @ symbols |
azazie__erp_exception_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal shipment IDs, status flags, timestamps, and internal codes. Names like 'jason wang' appear to be internal usernames/operational staff identifiers, not customer PII.
azazie__erp_order_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. This is an ERP attribute table with internal flags (not_cheat) and numeric IDs. All columns are internal identifiers or operational flags, none contain personal information.
azazie__error_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal operational data with no PII fields. All columns are internal IDs, flags, timestamps, or messages in Chinese. The 'name' column contains a placeholder value ('SAMPLE_UP'), and 'action_user' contains system or test usernames that are not considered searchable PII. No columns map to any PII categories.
azazie__estimate_profit_report_prepare_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, business codes, timestamps, and financial/transactional values. No PII fields present.
azazie__evaluate_provider_limit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal operational metrics, timestamps, and flags. No PII present. Columns like abs_id, provider_id are internal IDs, effect_month and dates are operational timestamps, d30_shipment_quantity and related fields are transactional counters, and avaliable is a status flag. No emails, names, addresses, phones, or other PII detected.
azazie__exception_return_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal operations table with no PII. Columns are internal IDs, foreign keys, timestamps, and operator usernames. No personal data is present.
azazie__express_assistance.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal logistics/tracking data (shipment IDs, carrier statuses, timestamps, user actions), country names, and internal notes. No emails, names, addresses, phones, DOB, SSN, or passwords are present.
azazie__express_delivery.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only shipping method names and timestamps. No PII fields are present. Columns 'shipping_name' contain generic carrier/service names (e.g., '货拉拉', '自送', '优速快递'), and timestamps are purely transactional timestamps without personal identifiers. All columns fall under skip rules (company/business names, timestamps).
azazie__express_reprint.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, file metadata, or non-PII identifiers. No PII fields present. The data represents shipment tracking records with internal references and file paths, not customer personal data.
azazie__external_goods_attribute.csv9 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | internal ID field 'abs_id' |
| 1 | skip | high | product reference ID 'external_goods_id' |
| 2 | skip | high | transaction amount field 'sales_price' |
| 3 | skip | high | inventory status flag 'is_shelf' |
| 4 | skip | high | product image path 'goods_pic' |
| 5 | skip | high | product color options list 'goods_color' |
| 6 | skip | high | size options list 'goods_size' |
| 7 | skip | high | party/event reference ID 'party_id' |
| 8 | skip | high | party/event name 'party_name' |
Notes: File appears to be a product catalog export from Azazie with no PII fields present. Contains only product IDs, pricing, inventory status, image paths, and color/size options. All columns map to non-PII business data.
azazie__external_goods_cat.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only product catalog data (abs_id, external_goods_id, category IDs and names). No PII fields present. All columns map to internal product identifiers and categories.
azazie__external_status_sync.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. All visible fields are internal IDs, status codes, timestamps, and order references. No names, emails, addresses, or other personal data appear in this sample.
azazie__external_status_sync_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided data. The columns appear to be internal tracking IDs, timestamps, status flags, and retry counters typical of system logs or database synchronization records. There are no personal identifiers, email addresses, phone numbers, names, or other PII fields present in the visible data.
azazie__fabric_surplus_stock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, product attributes, timestamps, or internal logs. No email, phone, name, address, DOB, SSN, password, username, or gender fields present.
azazie__facility.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal IDs, timestamps, flags, or non-PII business identifiers. No PII fields (email, phone, name, address, DOB, SSN) are present. Values are internal system codes, dates, status flags, and numeric counters.
azazie__facility_box_auto_limit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (IDs, timestamps, flags). No PII fields are present. All columns are internal IDs, timestamps, or flags and must be skipped per exclusion rules.
azazie__facility_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and operational flags (abs_id, facility_id, code, is_allow_supplier_return, switch_facility_group). No PII fields are present. All columns are skipped per rules (internal IDs, business codes, flags).
azazie__facility_location.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal warehouse/inventory location table (facility locations, aisles, sections, stock categories). No PII columns are present. All columns are internal operational data: location IDs, facility IDs, timestamps, capacity values, sort orders, container IDs, and inventory category flags.
azazie__facility_location__bakcontainer20170305.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, or capacity counters. No PII fields are present in this dataset.
azazie__facility_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system metadata (facility type definitions) with no personal identifiable information. All columns are internal identifiers, timestamps, or flags that do not contain PII. No mapping required.
azazie__factory_length_name.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/technical attributes (dress length names and styles). No PII fields are present. All columns are internal product descriptors and should be skipped per exclusion rules (vehicle/product data).
azazie__factory_production_schedule_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the provided data. The file appears to contain only internal operational data (IDs, stock numbers, order types, timestamps) with no personal or sensitive information.
azazie__factory_surplus_stock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product inventory data with no personal identifiable information (PII). Columns represent product identifiers, stock levels, timestamps, and operational logs. No fields map to PII categories.
azazie__failed_jobs.csv16 rows
File structure
Notes: free-form text with embedded emails / phones
azazie__fd_country_refund_gather.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal IDs, timestamps, transaction codes, or numeric codes. 'country' column contains numeric codes (likely ISO numeric country codes) not textual country names. No emails, names, addresses, phones, DOB, or SSNs present in the sample.
azazie__fd_first_sample_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, shipment tracking codes, timestamps, and user initials. No PII fields are present. Columns 'abs_id' (numeric ID), 'dispatch_sn' (tracking codes), 'external_goods_id' (product IDs), 'provider_id' (numeric codes), 'check_time' (timestamps), and 'action_user' (initials) are all non-PII per the exclusion rules.
azazie__fd_gross_profit_margin.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided rows. The data contains only transactional and operational information such as order IDs, shipment dates, category IDs, monetary amounts, and timestamps. No personal identifiers (email, phone, name, address, etc.) are present in the visible columns.
azazie__fd_language.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a configuration/localization table (language codes and descriptions). No PII fields present. All columns represent internal system metadata (IDs, codes, names of languages, descriptions, version numbers, audit fields). Per exclusion rules, these are skipped.
azazie__fd_language_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a language translation mapping table, not containing any PII. The columns represent IDs, language codes, and descriptions, none of which contain personal identifiable information. Therefore, no PII fields are mapped.
azazie__fd_mutiple_refund_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional/shipment data (order IDs, dates, refund amounts, etc.). No PII fields such as names, emails, addresses, or SSNs are present. All columns are internal identifiers, timestamps, or financial amounts — all must be skipped per exclusion rules.
azazie__fd_mutiple_refund_gather.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal IDs, timestamps, transaction amounts, and shipment identifiers. This appears to be an order/shipment record dump with no customer personal data exposed.
azazie__fd_over_dispatch_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All three columns (detail_id, create_time, dispatch_list_id) are internal identifiers and timestamps with no PII content. This is an operational dispatch/detail mapping table with no personal data.
azazie__fd_over_period_dispatch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only numeric counters and timestamps. No PII fields are present in the visible data. The columns represent internal operational metrics (e.g., over_period_info_id, over_period_five, etc.) and timestamps, all of which are excluded by policy.
azazie__fd_pattern_management_person.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, codes, and role types. No PII fields (names, emails, addresses, etc.) are present. All columns map to skip categories: 'id' and 'code' are internal IDs, 'name' appears to be role identifiers or generic names not tied to individuals, and 'type' is a role/flag. Timestamps are creation/update logs. No PII detected.
azazie__fd_pattern_management_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (id, goods_id, provider_id) with no personal or identifiable information. All columns are internal reference numbers and should be skipped per exclusion rules.
azazie__fd_pattern_management_standard_designer.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, or non-PII product metadata. No PII fields detected. Columns 0-16 are internal database identifiers, product codes, and timestamps, none contain personal information.
azazie__fd_pattern_management_standard_designer_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains metadata about files stored in the database dump (file paths, types, upload details). No PII fields are present in this sample. Columns like 'upload_user' contain internal system usernames (ywu01, nxlai), not actual user PII. All other columns are file identifiers, paths, timestamps, and counters — none map to personal data categories.
azazie__fd_pattern_ticket.csv1 column1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | username | high | [5] header 'user_name', values are alphanumeric strings likely usernames |
Notes: This file appears to be an internal messaging or status tracking table (from_provider_id, to_provider_id, status, type). Only column 5 (user_name) contains PII (username). All other columns are internal IDs, timestamps, and status codes — these are skipped per rules.
azazie__fd_pattern_ticket_base_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a simple CSV with three columns: id, name, and deleted. The 'name' column contains generic feedback titles in Chinese, not personal PII. No identifiable information is present.
azazie__fd_pattern_ticket_message.csv1 column11 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | username | high | [4] header 'user_name', values appear to be usernames (alphanumeric strings without @) |
Notes: Only column 4 (user_name) contains PII. Other columns are internal IDs, timestamps, or generic content codes. No emails, phone numbers, names, addresses, DOB, or SSN appear in the sample.
azazie__fd_quotation_production_item.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a non-PII list of service types or categories (e.g., '裁剪' meaning trimming, '车缝' meaning stitching). No personal identifiable information is present. All entries are generic service descriptors used internally by Azazie, an online retailer. Therefore, no columns map to PII fields.
azazie__fd_uk_gross_profit_margin.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain only internal IDs, numerical transaction amounts, and timestamps. This appears to be an order/ shipment transactional log with no personal customer data exposed in the sample.
azazie__feature.csv0 rows
File structure
Notes: The file appears to be a JSON schema configuration dump rather than actual customer or transactional data. It contains metadata definitions for UI components, data structures, and system configurations. No PII fields are present in the visible rows. The content shows JSON schema definitions for models like banners, SEO settings, product attributes, payment responses, and navigation elements, but does not include any actual user data, customer records, or sensitive information.
azazie__feature_config.csv119 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__feature_config_editing.csv0 rows
File structure
Notes: The provided data is a JSON-like structure embedded within CSV fields, not a typical tabular dataset with distinct PII columns. The file appears to be a database dump containing product listings, configurations, and internal metadata. There are no explicit columns mapping to PII fields such as email, phone, or address. The data consists of nested JSON objects with product IDs, URLs, timestamps, and other non-PII operational data. Based on the content, this is not a structured table with importable PII columns but rather a configuration or product data export. No PII fields are present in the visible rows.
azazie__feature_config_info.csv1 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__feature_config_xyzhou_20171124_2.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is a configuration listing for product collections, not customer PII. No PII fields present.
azazie__fedex_region.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This is a reference table mapping region IDs to geographical regions/countries/states/provinces. Contains only geographic identifiers, codes, and names of regions — no personal data.
azazie__fedex_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal shipment/order IDs, timestamps, status flags, and internal user logins. No PII fields (email, phone, names, addresses, DOB, SSN, etc.) are present. rec_id, file_id, party_id are internal numeric IDs; invoice_number, express_or_ground_tracking_id are transactional identifiers; dates/times are operational timestamps; create_by_user_login and last_update_by_user_login are system usernames, not customer-facing identifiers. No columns map to any PII field categories.
azazie__fedex_report_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a metadata file listing filenames, creation times, and user logins. It contains no personal identifiable information (PII). All columns represent internal system identifiers, filenames, timestamps, and user logins that do not correspond to any PII fields. The 'create_by_user_login' and 'last_update_by_user_login' columns contain system usernames which are internal identifiers and not considered PII per the exclusion rules.
azazie__feedback_question_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains customer feedback records with no PII columns. All columns are internal IDs, status codes, timestamps, file paths, and numeric values. No email, phone, name, address, DOB, SSN, or password fields are present.
azazie__final_az_sale_return_records_2020.csv1 column1,694,123 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__final_order_cat_num_2020.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional order data with no PII fields. Columns include order IDs, product IDs, quantities, amounts, and reasons for returns/refunds, but no personal information such as names, emails, or addresses is present.
azazie__final_order_cat_num_2020_tmp1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only transactional order data (order IDs, product IDs, quantities, amounts) and generic reasons for cancellation/returns. No personal identifiers such as names, emails, addresses, or phone numbers are present.
azazie__finance_confirm_refund.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, transactional data, or flags (abs_id, create_time, update_time, party_id, refund_id, order_sn, order_amount, refund_amount, action_user, currency, is_sync). None map to email, phone, name, address, DOB, SSN, password, or other PII fields.
azazie__finance_variance_amount.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, financial amounts, timestamps, and status flags. No PII fields present. Columns like VARIANCE_ID, order_id, AMOUNT, NOTE, STATUS, and various timestamp fields contain operational data only.
azazie__fix_inv.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory IDs and timestamps. No PII fields are present. All columns are marked as skip per exclusion rules (internal IDs and timestamps).
azazie__fix_inv_mission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All visible fields are internal identifiers (uniq_key, long_code), status codes, timestamps, and notes containing only order/lot numbers. No personal information (email, phone, name, address, etc.) appears in the first 50 rows.
azazie__fix_provider_purchase_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains only transactional product data (IDs, prices, sizes, timestamps) with no personal information such as names, emails, addresses, or other identifiers. All columns map to skip per exclusion rules (product codes, prices, internal timestamps).
azazie__fix_provider_purchase_price_20200917_01.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. This appears to be a transactional/operational table containing only order IDs, provider codes, product IDs, size types, pricing, and timestamps. All columns are internal business identifiers or numerical values.
azazie__fix_provider_purchase_price_20200917_02.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product/order data file showing SKU-level pricing and inventory movements. No personal identifiable information (PII) is present in the header or values. All columns represent internal product codes, pricing tiers, and timestamps - none map to email, phone, name, address, DOB, SSN, password, username, or other PII fields. The values contain only numeric IDs, price points, and system timestamps.
azazie__fix_provider_purchase_price_20200917_03.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product/order table from Azazie. All columns are internal identifiers, product codes, price data, and timestamps. No PII is present. Columns like 'action_user' appear to be system roles rather than actual usernames or personal identifiers.
azazie__fix_sku_long_code_change.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided rows. The data appears to be internal order/sku codes, timestamps, and system identifiers. No names, emails, addresses, phone numbers, SSNs, or other PII fields are present in the visible columns.
azazie__fix_sku_long_code_change_1119.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file appears to contain only internal identifiers, SKU references, and system timestamps. All columns map to skip categories (internal IDs, counters, timestamps).
azazie__fix_sku_long_code_change_1126.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided rows. The dataset appears to contain only internal identifiers (e.g., codes, SKU references) and timestamps. No fields correspond to the defined PII categories (email, phone, DOB, names, addresses, SSN, etc.).
azazie__fix_sku_long_code_change_1127.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The data appears to be internal order/sku management records with only alphanumeric codes, timestamps, and system flags. No personal information (names, emails, addresses, etc.) is present in the visible columns.
azazie__fly_fish_box_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only box dimensions and internal IDs. No PII fields (email, phone, name, address, etc.) are present. All columns map to skip categories: box_id (internal ID), box_name (internal identifier), dimensions (box_length/box_width/box_height), is_delete flag, create_user/update_user (internal system users), and timestamps (create_time/last_update_time).
azazie__fly_fish_carrier_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal carrier/shipping configuration data. No PII fields present. Columns include IDs, timestamps, carrier names, and codes — all internal operational data. No emails, names, addresses, or other personal data.
azazie__fly_fish_cost_balance.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal cost and shipping records. All columns are internal identifiers, years, months, and timestamps. No PII is present.
azazie__fly_fish_cost_balance_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the first 50 rows. All columns appear to be internal identifiers, flags, timestamps, transaction codes, or non-personal metadata. No names, emails, addresses, phone numbers, DOB, SSN, or other PII fields are present.
azazie__fly_fish_cost_balance_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be about cost details and file imports, containing only internal identifiers, filenames, and timestamps. No PII fields are present. All columns map to skip categories (internal IDs, file names, timestamps).
azazie__fly_fish_material_inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory and operational data (material IDs, facility IDs, inventory counts, timestamps). No PII fields are present. All columns are internal IDs, numeric counters, or timestamps, which are explicitly excluded by the rules.
azazie__fly_fish_material_inventory_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. This is an inventory/supply log table with internal IDs, material/facility references, supply quantities, internal usernames (action_user values like 'kila', 'ywang7' are system/employee logins, not customer PII), and timestamps. All columns are operational/internal data.
azazie__fly_fish_modify_receiver_record.csv24 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__fly_fish_outbound.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains purely operational/transactional data (order IDs, tracking numbers, timestamps, weights, statuses) with no personal identifiable information. All columns map to internal IDs, logistics codes, timestamps, and numeric flags. No PII fields detected.
azazie__fly_fish_outbound_status.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided rows. The columns appear to contain only order identifiers, transaction references, and timestamps, which do not map to any of the defined PII categories. All columns fall under the 'skip' category per the exclusion rules (internal IDs, transactional data, timestamps).
azazie__fly_fish_outbound_sync_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal timestamps and counters. No PII fields are present. Columns are: id, action_start_time, action_end_time, sync_num, create_time, last_update_time. These are all internal system timestamps or numeric counters and do not contain any personally identifiable information.
azazie__fly_fish_price_group_added_weight.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/pricing data (ids, weights, prices). No PII present. The 'note' column is empty in sample rows. This appears to be an inventory/pricing table from the Azazie database, not customer data.
azazie__fly_fish_price_group_discount.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a discount table with columns: discount_id, abs_id, float_discount, effective_date, is_deleted, create_user, create_time, update_user, last_update_time. No PII fields are present. All columns are internal IDs, flags, timestamps, or user references (not actual usernames).
azazie__fly_fish_price_group_enum_weight.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns contain only numeric identifiers (id, abs_id), product categories (enum_type), and pricing data (weight, price). No names, emails, addresses, or other personal data present in the first 50 rows.
azazie__fly_fish_price_group_number_weight.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal product/weight/price metrics (id, weight_line, more_price_kg, registered_price). No PII fields detected. This aligns with Azazie product database dumps containing pricing and inventory data, not customer PII.
azazie__fly_fish_price_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII found. File appears to be a settings/permissions table with numeric IDs, user roles, timestamps, and status flags. No personal information such as names, emails, addresses, or phone numbers is present in the visible columns.
azazie__fly_fish_price_setting_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only internal configuration parameters (detail_id, setting_id, enum_type, abs_id, limit_time). No PII fields detected. All columns represent internal system settings, limits, and identifiers — none map to personal data categories. Values are numeric codes and time limits, not personal information.
azazie__fly_fish_price_setting_detail_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only numeric IDs with no personal information. All columns appear to be internal identifiers (id, detail_id, abs_id) with no PII values. No emails, names, addresses, or other PII fields are present in the first 50 rows.
azazie__fly_fish_price_setting_detail_supplier.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only three columns: id, detail_id, and shipping_supplier_id. All three columns are internal IDs and do not contain any PII. They are numeric identifiers and do not map to any PII fields.
azazie__fly_fish_region.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided rows. The data contains only geographical region IDs, names, types, country codes, zip codes, and timestamps, none of which qualify as PII per the defined categories. All columns are skipped as they represent internal region identifiers, administrative boundaries, and audit timestamps.
azazie__fly_fish_report_balance.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal reporting IDs and timestamps. No PII fields present. All columns map to skip categories: report_id (internal ID), shipping_supplier_id (internal ID), report_year/report_month (non-DOB dates), create_time (timestamp).
azazie__fly_fish_report_balance_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This dataset appears to be transactional/order records with no PII fields. All columns represent internal identifiers, flags, timestamps, financial amounts, product details, and system metadata. No names, addresses, emails, phone numbers, DOB, or SSNs are present.
azazie__fly_fish_report_balance_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a metadata file listing database dumps, not customer PII. All columns are internal IDs, filenames, and timestamps — no personal data present.
azazie__fly_fish_shipping_fee_price_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in first 50 rows. File appears to be operational/shipping data with internal IDs, weights, and timestamps. All columns fall under exclusion rules (internal IDs, timestamps, transactional data).
azazie__fly_fish_shipping_supplier.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers (supplier IDs, user IDs, timestamps, flags, operational data). No PII is present in the first 50 rows.
azazie__fly_fish_shipping_supplier_box.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, flags, or timestamps (supplier_box_id, supplier_id, box_id, is_delete, create_user, create_time, update_user, last_update_time). No PII fields detected.
azazie__fly_fish_shipping_supplier_fuel.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields are internal identifiers (fuel_id, shipping_supplier_id), monetary values (fuel_fee), and timestamps (effective_time, create_time). These match the exclusion rules for internal IDs, financial/transactional data, and timestamps.
azazie__fly_fish_storage_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, status codes, or business metadata. No PII fields detected. Columns like 'check_message' contain test strings and status notes, not personal information.
azazie__fly_fish_storage_check_action_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a transactional ledger or order tracking table with no PII fields. Columns include identifiers (id, check_reference_no), SKU codes (uniq_sku), monetary values (change_amount, before_amount, after_amount), and timestamps (create_time, last_update_time). All columns are internal business identifiers or financial/temporal data and do not contain any personal identifiable information (PII).
azazie__fly_fish_warehouse_material.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/material inventory data (IDs, material names, units, flags, and timestamps). No PII fields are present. All columns map to internal IDs, product descriptions, or operational metadata and are therefore skipped per exclusion rules.
azazie__fly_fish_wms_audit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal business process tracking IDs, timestamps, status flags, and warehouse codes. No PII fields detected. Columns containing identifiers (fly_audit_id, issue_id, fly_fish_issue_id, request_id) are internal operational IDs, not user-identifiable PII. Timestamps (finish_stamp, create_time, last_update_time) are non-DOB temporal markers. action_user is a system account name, not a personal username.
azazie__fly_fish_wms_audit_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains only internal identifiers (fly_fish_issue_id, batch_number), status flags, and timestamps. No names, emails, addresses, or other personal data appear in the first 50 rows.
azazie__fly_fish_wms_hs_code.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product catalog data with no personal identifiable information. Columns include product IDs, names (in multiple languages), HS codes, status flags, and timestamps. No PII fields detected.
azazie__fly_fish_wms_order_refund.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order IDs, status codes, and timestamps. No PII fields are present. All columns are internal identifiers or operational metadata and must be skipped per exclusion rules.
azazie__fly_fish_wms_return_apply.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided 50 rows. All columns appear to contain order identifiers, SKU codes, quantities, statuses, and timestamps. No personal identifiable information such as names, emails, addresses, or phone numbers is present in the visible data.
azazie__fly_fish_wms_stock_inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, status flags, timestamps, SKU codes, and system messages. This appears to be an inventory adjustment log rather than customer data.
azazie__flyfish_basket_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal basket/shopping cart metadata. No PII fields are present. Columns like basket_id, basket_name, facility_id, limit_num, threshold, basket_status, action_user, action_time, basket_type are all internal operational identifiers, counters, flags, or timestamps — none constitute personal PII per exclusion rules.
azazie__flyfish_basket_shipment_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. This appears to be an internal transactional log containing action IDs, basket names, goods SKUs, quantities, and dispatch flags. All columns represent internal operational data (action IDs, product SKUs, inventory flags) and contain no personal identifiers, addresses, emails, or other PII.
azazie__flyfish_transfer_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All 14 columns are internal operational/logistics data: IDs, order/shipment references, tracking numbers, carrier codes, status flags, and timestamps.
azazie__follower_order_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. Columns contain internal IDs (id, follow_user_id), usernames (follow_user_name), model references (model_type, model_id, model_name), timestamps (create_time, update_time), factory type codes, and creator usernames. All columns fall under skip categories (internal IDs, flags, timestamps).
azazie__follower_order_relation_copy1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but none of the columns map to PII fields. All columns are internal IDs, usernames, model types, and timestamps. The 'follow_user_name' column contains usernames which are considered PII, but they are internal identifiers and not public-facing usernames or handles. According to the rules, internal IDs and usernames that are not public-facing searchable identifiers should be skipped. Therefore, no PII columns are mapped.
azazie__forbid_to_reserve_order_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a log table containing only internal IDs (forbid_id, order_goods_id), timestamps (action_time, update_time), user identifiers (action_user, update_user), and status flags (forbid_status). No PII fields are present. The column 'action_user' and 'update_user' contain usernames, but these are internal system users, not customer PII, and should be skipped per exclusion rules for internal IDs.
azazie__force_collection_log.csv1 column63 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 7 | username | high | [7] column 'action_user', values are alphanumeric strings that appear to be usernames or user identifiers |
Notes: CSV file with 8 columns. Only 'action_user' contains PII (username). All other columns contain transactional data, timestamps, and status flags which are not PII.
azazie__gc_payment_product.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only payment product information (Visa, AMEX, MasterCard, etc.) and internal timestamps. No PII fields are present. Columns like payment_product_name contain card types, not personal identifiers. Timestamps are non-DOB dates and should be skipped per rules.
azazie__git_branch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns appear to be internal IDs, status codes, notes, and timestamps. No PII fields (email, phone, name, address, etc.) are present in the first 50 rows. The columns map to internal system metadata rather than customer personal data.
azazie__glc1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible fields are internal identifiers (abs_id, erp_sku, dispatch_sn), order references (order_sn, bar_code), timestamps (created_stamp, creater), and numeric amounts. No names, emails, addresses, phone numbers, or other PII appear in the first 50 rows.
azazie__gls_delivery_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are operational/tracking fields (tracking numbers, facility IDs, timestamps, order statuses) with no PII. No email, name, address, phone, or other personal data present.
azazie__gls_packing_error.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal operational/tracking fields (facility IDs, order numbers, status flags, timestamps). No PII such as names, emails, addresses, or other personal data is present in the first 50 rows. Therefore, no columns map to PII fields.
azazie__goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product catalog data (goods_id, SKU, pricing, descriptions, timestamps). No PII fields are present. All columns are internal product identifiers, pricing data, timestamps, flags, and image paths — none contain personal information such as names, emails, addresses, or other sensitive data.
azazie__goods_action_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in this structured file. All visible columns contain internal system identifiers, timestamps, and operational codes (e.g., goods_id, type, info, number, container_id, create_time, create_user). The 'info' field contains JSON arrays with internal references and order numbers that do not expose personal data. This appears to be a warehouse/logistics operational log rather than customer-facing data.
azazie__goods_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only product attribute data (goods IDs, attribute IDs, attribute values, and status flags). All columns map to internal product metadata or operational flags, not personal information.
azazie__goods_attribute_picture.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a database of image metadata (file paths, sizes, hashes, timestamps) with no personal information. All columns represent technical/image data and internal IDs.
azazie__goods_batch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, order identifiers, product codes, timestamps, and color codes. No PII fields are present in this dataset.
azazie__goods_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs (goods_id, cat_id, cat_pid) and timestamps (last_update_time). No PII present in the sample. The file appears to be product catalog metadata rather than customer data.
azazie__goods_category_manager.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. This appears to be a product/category reference table with only internal codes and timestamps. All columns are internal identifiers, category names in two languages, and audit timestamps.
azazie__goods_color_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a product color catalog listing translations of color names across three languages (English, French, Spanish). It contains no PII fields such as names, addresses, emails, etc. All columns represent product color descriptions and translations, which do not qualify as personally identifiable information under the defined field types. The file structure is consistent with a simple lookup table for multilingual color naming.
azazie__goods_comment.csv1 column14 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | high | header "user_email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__goods_craft.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file contains structured data but all columns appear to represent product specifications and manufacturing notes for dresses (fabrics, colors, measurements, notes). No PII fields are present. Columns contain technical product descriptions and timestamps, none of which map to personal identifiable information fields.
azazie__goods_craft_factory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the provided rows. The data appears to be product specifications or manufacturing instructions for dresses, containing only technical details about garment construction, materials, and design notes. No personal information such as names, contact details, or identifiers is present.
azazie__goods_craft_zz.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only numeric IDs (goods_id, cp_goods_id, factory_length_name_id) with no personal or identifiable information. All columns represent internal product identifiers and relationships between product records, none contain PII fields such as names, addresses, emails, or other personal data. The values are purely numeric identifiers used for database relationships.
azazie__goods_d30_goal.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional/financial data: abs_id (internal ID), external_goods_id (product reference), effect_month (date), target_value (monetary amount), created_stamp (timestamp), action_user (username), is_used (flag). No PII fields are present. All columns are either internal IDs, timestamps, flags, or monetary values. The action_user column appears to be a system username (lmzheng/Han) not a personal identifier, and is therefore skipped per rules.
azazie__goods_daily_pageviews.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. Columns present are visit_date, goods_id, site_code, country_code, language_code, pageviews, visits, visitors — all appear to be internal analytics/operational data. No emails, names, addresses, phone numbers, DOB, SSN, or other PII fields are visible in the first 50 rows.
azazie__goods_designer.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product IDs and timestamps. No PII fields are present. All columns are internal identifiers or timestamps and should be skipped according to the rules.
azazie__goods_display_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only product IDs, sales order references, and color names. All columns are internal identifiers or descriptive attributes, not personal data.
azazie__goods_display_order_batch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns contain product identifiers, order numbers, color names, and timestamps — none map to personal data categories.
azazie__goods_down_shelf.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, timestamps, and user actions. No PII fields are present. Columns: abs_id (internal ID), external_goods_id (product ID), off_shelf (flag), action_time (timestamp), action_user (username). However, 'action_user' appears to be a system username/test account, not a real user identifier, and is excluded per rules. No emails, phone numbers, names, addresses, DOB, SSN, or other PII detected.
azazie__goods_extension.csv5 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | internal ID column |
| 1 | skip | high | product ID column |
| 2 | skip | high | internal metadata column |
| 3 | skip | high | internal metadata column |
| 4 | skip | high | internal flag column |
Notes: This appears to be an internal product catalog export containing size chart metadata. No PII fields are present in the visible columns. All columns contain product/size chart identifiers or flags.
azazie__goods_extension_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a structured CSV containing size chart data for fashion dresses and flower girl dresses. All visible columns contain product sizing information (busts, waists, size values, displays) and do not contain any personally identifiable information (PII). No email addresses, phone numbers, names, addresses, dates of birth, SSNs, passwords, usernames, or other PII fields are present in the provided rows. The data is purely product-centric and relates to sizing specifications.
azazie__goods_first_order_feed_back.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only operational metadata about image files and user actions. Columns are: id (internal ID), external_goods_id (internal product ID), file_path (storage path), create_time (timestamp), update_time (timestamp), action_user (username or role), action_id (internal action ID). No PII fields present. All columns are internal IDs, timestamps, or system identifiers — they are excluded by the skip rules for internal IDs and timestamps.
azazie__goods_frb.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product inventory table containing only product metadata (IDs, categories, names, stock levels, user references). No PII fields present. All columns map to internal IDs, product names in Chinese, quantities, and audit timestamps. The 'create_user' and 'update_user' fields appear to be system usernames rather than customer PII.
azazie__goods_gallery.csv1 column1,141,498 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 18 | username | high | [18] header 'user_name', values are alphanumeric strings likely usernames |
Notes: Only column 18 (user_name) contains PII (username). All other columns are internal product/image identifiers, timestamps, flags, or technical metadata, and should be skipped per exclusion rules.
azazie__goods_girl_names.csv6 columns1,535 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | [0] column 'id' is an internal numeric identifier |
| 1 | fullName | high | [1] column 'name' contains human first names, no surnames visible in sample |
| 2 | skip | high | [2] column 'goods_id' is an internal product reference |
| 3 | skip | high | [3] column 'is_delete' is a status flag (0/1) |
| 4 | skip | high | [4] column 'last_update_time' is a timestamp |
| 5 | skip | high | [5] column 'cat_id' is an internal category identifier |
Notes: 50 rows shown; only column 1 contains PII (fullName). All other columns are internal IDs, flags, or timestamps per azazie breach context. No email/phone/DOB/SSN/address fields appear in this sample.
azazie__goods_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. The file contains only internal product identifiers (goods_id), group identifiers (group_id), and timestamps (last_update_time). No personal or sensitive data is present in the first 50 rows.
azazie__goods_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, operation types, and system metadata. Column 7 (user_name) contains a username-like string ('yfliu'), but this appears to be an internal admin account identifier, not a customer username. This file tracks database change logs for product information, not customer data.
azazie__goods_imp_sort.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product attribute mappings (line items, personalization fields) with no actual PII values present in the sample. All columns appear to be internal product metadata or placeholder fields (e.g., 'bride's_name' contains no real names). No PII fields detected.
azazie__goods_info_cache.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product IDs and color numbers. No PII fields are present. All columns are internal product identifiers and color codes, which are excluded by the exclusion rules.
azazie__goods_inv_other_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational metrics and timestamps. No PII fields are present. All columns are either internal IDs, counters, rates, or timestamps, which must be skipped per the exclusion rules.
azazie__goods_inv_other_setting_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, numeric counters, rates, timestamps, and usernames that are not personally identifiable. The 'action_user' column appears to be a system username, not a personal username, and is therefore skipped.
azazie__goods_inv_ratio_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal business metrics (sales volume IDs, trends, ratios, and timestamps). No PII fields are present. All columns are excluded per rules (Company/Business references, internal IDs, timestamps).
azazie__goods_inv_ratio_setting_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal business metrics and timestamps — no PII fields. Columns represent sale volume IDs, ratios, user actions, and audit timestamps. All columns are marked as skip per exclusion rules (company/business references, internal IDs, and timestamps).
azazie__goods_languages.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product metadata (goods IDs, descriptions, timestamps). No PII fields present. All columns are internal product identifiers, descriptions, or timestamps, which are explicitly excluded by the rules.
azazie__goods_material_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product and supplier data. No PII fields present. All columns are either internal IDs, product attributes, pricing, timestamps, or flags. provider_phone and provider_address appear to be business contact details, not personal PII. According to exclusion rules, any column with 'Company' or 'Business' in the name must be skipped, and these appear to be supplier/business data.
azazie__goods_name_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product metadata (goods IDs, names, timestamps) with no personal information. All columns are internal identifiers, product names, admin user IDs, status flags, and timestamps — none contain PII.
azazie__goods_on_color.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product catalog metadata: IDs, colors, timestamps, and sales flags. No PII fields (names, emails, addresses, etc.) are present. All columns map to internal identifiers, product attributes, or timestamps — these are explicitly excluded per rules.
azazie__goods_out_of_stock.csv1 column493 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__goods_package_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/package identifiers, timestamps, and flags. No PII present. Columns like create_user/update_user are system usernames, not customer usernames, and are excluded per rules.
azazie__goods_pangu_warehouse_quantity.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal identifiers, product codes, quantities, and timestamps. No customer personal data present in this dataset.
azazie__goods_photo.csv2 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | column 'goods_id' is an internal ID |
| 1 | skip | high | column 'img_url' contains URLs, not PII |
Notes: This appears to be a simple product listing table with IDs and image URLs. No PII fields detected in the first 50 rows. The columns are purely technical/internal identifiers and URLs.
azazie__goods_photo_backup.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a simple list of image file paths without any PII data. The columns 'goods_id' and 'img_url' contain only internal identifiers and image URLs respectively, with no personal or sensitive information present.
azazie__goods_project.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified in the provided rows. The data appears to be product inventory records containing only product IDs, names, image paths, types, prices, and timestamps. No personal information such as names, addresses, emails, or phone numbers is present in these rows.
azazie__goods_project_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File appears to be a product catalog with configuration IDs, image types, project names, display order, category IDs, clothing flags, and last update timestamps. No personal information such as names, emails, addresses, or phone numbers is present in the visible data.
azazie__goods_project_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only internal identifiers (goods_id), a static project name ('Azazie'), and timestamps. All columns fall under exclusion rules (internal IDs, timestamps).
azazie__goods_purchase_operation.csv1 column3 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | username | high | [3] header 'user_name', values are alphanumeric usernames like 'xmwang' and 'qdong' |
Notes: This file contains only an internal user identifier (user_id) and a username. No other PII fields are present in the first 50 rows. The 'abs_id' and 'external_goods_id' are internal identifiers and should be skipped.
azazie__goods_purchase_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, pricing data, timestamps, and flags. No PII present. Columns map to product IDs, provider IDs, transaction metadata, and operational flags — none contain names, emails, addresses, or other personal data.
azazie__goods_purchase_price_history.csv1 column1,759 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | username | high | [5] header 'username', values appear to be alphanumeric login handles |
Notes: CSV file with 5 columns. Only 'username' maps to PII. Columns 0-4 and 6+ contain internal IDs, timestamps, and action flags which are not PII.
azazie__goods_reviews.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, transaction references, or non-PII metadata (comments, timestamps, status flags). No personal identifiable information is present in the first 50 rows.
azazie__goods_sale_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns contain transactional data (IDs, prices, regions, timestamps) with no personal identifiers. The 'action_user' field contains system/service usernames (e.g., 'webService', 'leopard'), not actual user accounts.
azazie__goods_sale_price_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, prices, timestamps, or user identifiers. No PII fields detected. 'action_user' is an internal username identifier, not a public handle or searchable PII.
azazie__goods_shelf_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/tracking data (abs_id, external_goods_id, action_time, provider_id, action_user, action_note). No PII fields are present. The 'action_user' column contains internal usernames (yzhang, gys1) which are not considered PII per the rules (these are internal system users, not customer identifiers).
azazie__goods_shelf_inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be an internal operations table with no PII. Columns represent abstract IDs, inventory counts, and timestamps. No identifiable personal data is present.
azazie__goods_short_link_count.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a simple two-column inventory file showing product IDs and counts. No PII present — these are internal product identifiers and quantities, not customer or personal data.
azazie__goods_size_chart.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains size chart data for dresses, with no PII fields. All columns represent measurements, size types, units, and timestamps, which are internal product specifications and operational metadata.
azazie__goods_size_chart_wrap.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/size reference data (size_chart_id, size_type, measurements, country codes, units, references, timestamps). No PII fields present. Columns like 'country' contain country codes (US) not full addresses. Timestamps are internal update times, not DOB. All columns map to skip per exclusion rules.
azazie__goods_size_chart_zz.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product sizing data and metadata. No PII fields detected. Columns like 'size_chart_id' and 'size_type' contain product measurements and categories, while 'country' and 'last_update_time' are operational metadata. No personal customer information present in this dataset.
azazie__goods_sku.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent garment measurements and sizing metrics (bust, waist, hips, sleeve_length, etc.). No PII fields such as names, emails, addresses, or other personal identifiers are present. All columns are skipped per exclusion rules for product/vehicle data and internal metrics.
azazie__goods_spare_situation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, product attributes, or timestamps. 'action_user' contains short alphanumeric strings that appear to be system usernames rather than human user identifiers, and are therefore skipped per policy.
azazie__goods_spare_situation_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal IDs, counters, statuses, and timestamps — no PII present. Columns like 'action_user' contain a static username placeholder ('pxing') not tied to actual customer accounts.
azazie__goods_spare_situation_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains only operational data (IDs, user actions, timestamps) with no personal information such as names, emails, addresses, or other PII fields. All columns map to internal system identifiers, actions, and timestamps which are excluded by policy.
azazie__goods_special_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured dataset containing product attributes (shoe sizes) and internal tracking fields. No PII fields are present. Columns are: abs_id (internal ID), external_goods_id (product ID), attribute_name (shoe_size), attribute_value (size values), special_attribute_layer (flag), last_update_user (internal username), last_update_time (timestamp). All columns are non-PII per exclusion rules (internal IDs, product data, timestamps, internal flags).
azazie__goods_special_attribute_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product attribute data (shoe sizes, operations). No PII fields present. Columns map to internal product attributes and audit logs.
azazie__goods_stock_granularity.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/operational identifiers and timestamps. No PII fields are present. Columns are: id (internal ID), external_goods_id (product reference), granularity (data grouping), party_id (internal reference), create_time and last_update_time (timestamps). All columns are excluded per rules (internal IDs and timestamps).
azazie__goods_stock_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only product IDs, SKU codes, inventory levels, and timestamps. All columns either represent internal product identifiers (container_id, external_goods_id, uniq_sku, party_id) or operational metadata (create_time, last_update_time). No personal information is present in the first 50 rows.
azazie__goods_style.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are product/price metadata (SKU, IDs, pricing) with no personal identifiers. No PII detected.
azazie__goods_style_black_white.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain product metadata (IDs, colors, fabrics, sizes, timestamps) with no personal information.
azazie__goods_style_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns appear to be product identifiers (IDs), names (product names), languages, and timestamps — none contain personal information such as email, phone, address, etc. The values are product-related descriptors and do not map to any PII categories.
azazie__goods_thumb.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product image metadata (goods_thumb_id, goods_id, img_id, thumb_name, dimensions, etc.) with no personal identifiable information. All columns are internal product/image identifiers, dimensions, and timestamps — none map to PII fields.
azazie__goods_thumb_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected. All columns are internal identifiers, dimensions, watermarks, image types, timestamps, and project names. No personal data fields (email, phone, names, addresses, etc.) are present in the first 50 rows.
azazie__goods_web_source.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided rows. The file appears to contain only internal product IDs, sources, and timestamps.
azazie__google_map_validation_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. The file contains only internal IDs (abs_id), timestamps (create_time), URLs (google_map_url), order IDs (order_id), and status codes (status). All columns are non-PII per exclusion rules (internal IDs, timestamps).
azazie__gross_profit_margin.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional data (order IDs, shipment dates, category IDs, monetary amounts, timestamps). No PII fields are present. All columns are internal identifiers, financial figures, or timestamps that fall under the exclusion rules.
azazie__group_package_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in this sample. Columns appear to be internal IDs and system metadata (country_id, shipping_id, timestamps, usernames). The username 'owen.li' could be considered a username, but per exclusion rules, internal user identifiers and system users are skipped. No emails, phone numbers, names, addresses, DOB, SSN, or other PII fields are present in this structured data sample.
azazie__group_roles.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and role information. No PII fields are present. All columns are internal identifiers (id, group_id, resource_id), role names, and UUIDs which are not personally identifiable information.
azazie__groups.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system IDs, group types, flags, and timestamps. No PII is present in the first 50 rows. Columns map to skip categories: group_id (internal ID), group_type (internal code), is_delete (flag), group_config (internal JSON config), party_id (internal ID), last_update_time (timestamp).
azazie__groups_users.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (user_id, group_id) with no PII. All columns are numeric identifiers and should be skipped per exclusion rules.
azazie__gt_tips.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a free-form unstructured text file with no consistent column structure. All rows contain prose explanations about return policies and GT deductions, not structured PII fields. No columns map to PII fields.
azazie__hadm_service.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal service configuration table with no PII fields. All columns are service identifiers, codes, timestamps, and version numbers. No personal or sensitive data is present.
azazie__hadm_service_route.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal service configuration data (IDs, routes, paths, timestamps). No PII fields present. Columns like 'name' contain internal system identifiers, not personal names.
azazie__hadm_service_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains service IDs, language codes, and service names. No PII fields are present. All columns represent internal system identifiers and localization strings, which are not considered PII per the rules.
azazie__hadm_service_version.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, version numbers, timestamps, and configuration data. No PII fields are present in this structured dataset.
azazie__hadm_swagger.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII present in the first 50 rows. This is a system configuration/API documentation dump containing JSON metadata about services and endpoints, not customer data. All values are technical descriptors and internal system identifiers.
azazie__happy_return_tracking_info.csv13 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__help_keyword.csv0 rows
File structure
Notes: The provided data is not structured tabular data but appears to be a list of SQL keywords or reserved words, not containing any PII fields. There is no consistent delimiter or row structure present, and the content consists entirely of database-related terminology.
azazie__help_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a CSV file containing only two columns: help_topic_id and help_keyword_id. Both columns appear to be internal reference IDs for help topics and keywords, with no personal identifiable information (PII) present. All values are numeric and represent internal system identifiers rather than user data. Therefore, no PII columns to map.
azazie__help_topic.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data appears to be MySQL reference documentation entries, not a customer data breach export. It contains function syntax descriptions, examples, and URLs rather than actual PII records. No columns map to PII fields because this is informational content about MySQL functions, not a dataset containing personal information. The structure shows help topics, categories, descriptions, and URLs — all metadata about database functions, not user data.
azazie__hfle_capacity_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal system identifiers, capacity metrics, timestamps, and user IDs that do not contain personal information. Columns like 'created_by' and 'last_updated_by' contain numeric IDs (-1, 0) and are not usernames or usernames.
azazie__hfle_file.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers, file metadata, and storage paths. No PII is present. All columns are either internal IDs, file paths, timestamps, or system codes which must be skipped per exclusion rules.
azazie__hfle_storage_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal storage configuration table from the Azazie database. None of the columns contain PII fields. All columns represent system configuration details such as storage IDs, endpoints, access keys, flags, dates, and strategies. These are internal technical identifiers and operational metadata, not personal information.
azazie__hfle_upload_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal system identifiers, file metadata, and timestamps. These are typical of a database dump tracking file storage configuration and do not contain personal information.
azazie__hiam_doc_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal system configuration table from Azazie (organization order permissions). All columns are system identifiers, flags, timestamps, and internal codes. No PII fields present.
azazie__hiam_doc_type_assign.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be an internal database mapping table with no PII fields. All columns are internal IDs, version numbers, timestamps, and foreign keys. No email, phone, name, address, DOB, SSN, or other PII is present. This is typical of relational database linkage tables used for foreign key relationships and versioning.
azazie__hiam_doc_type_auth_dim.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal database identifiers, metadata, or timestamps. No PII fields are present in this structured dataset.
azazie__hiam_doc_type_dimension.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, metadata, or audit fields (dimension_id, dimension_code, creation_date, etc.). No PII fields are present. Columns like dimension_code contain category labels ('COMPANY', 'LOV') not personal data. Timestamps and user IDs (-1) are system audit fields.
azazie__hiam_doc_type_permission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system identifiers and timestamps. No PII fields are present. All columns are internal IDs, version numbers, dates, and tenant identifiers which should be skipped per rules.
azazie__hiam_label_rel.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a structured CSV with columns indicating menu items and metadata, but no identifiable PII fields are present. All columns contain internal IDs, types, versions, and timestamps that do not qualify as personal data under the defined PII categories. No emails, phone numbers, names, addresses, DOBs, SSNs, passwords, usernames, or other sensitive identifiers are detectable in the header or sample rows.
azazie__hiam_permission_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal system identifiers, status flags, timestamps, or technical metadata. The access_token values appear to be bearer tokens (not passwords), and other fields like permission_check_id, menu_id, creation_date are internal operational data.
azazie__hiam_role_auth_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system identifiers and timestamps (auth_data_id, role_id, tenant_id, etc.). No PII fields are present. All columns are internal IDs, flags, or timestamps and are marked as skip per exclusion rules.
azazie__hiam_sec_grp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, flags, timestamps, or non-PII metadata. No personal identifiable information (PII) is present in this sample.
azazie__hiam_sec_grp_acl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system identifiers and timestamps. No PII fields are present. Columns include security group ACL IDs, tenant IDs, permission IDs, version numbers, creation dates, and user IDs — all internal operational data with no personal information.
azazie__hiam_sec_grp_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a structured CSV, but all columns appear to be internal identifiers or metadata (sec_grp_id, lang, sec_grp_name, remark, tenant_id). No PII fields detected. Columns map to skip categories: sec_grp_id (internal ID), lang (language code), sec_grp_name (group name), remark (comment field), tenant_id (internal tenant identifier).
azazie__hiam_tenant_access.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only access logs and internal system identifiers (access_id, user_id, tenant_id, timestamps, counters). No PII fields are present. All columns are internal IDs, timestamps, or counters and should be skipped per exclusion rules.
azazie__hiam_user_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, configuration flags, or timestamps. No PII present. Columns like user_id and tenant_id are internal numeric IDs, not usernames or emails. Timestamps (creation_date, last_update_date) and flags (role_merge_flag, popout_reminder_flag) are not PII. No email, phone, name, address, DOB, SSN, password, or username fields are present.
azazie__hiam_user_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, flags, timestamps, or non-personal metadata. This appears to be an administrative table for user groups/orders, not customer data.
azazie__hiam_user_group_assign.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, flags, and timestamps. No PII fields are present. All columns are internal identifiers, version numbers, and audit timestamps which must be skipped per rules.
azazie__hiam_user_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns are either internal IDs, company data, timestamps, flags, or non-PII identifiers. Specifically: user_id, company_name, invitation_code, employee_id, text_id, security_level_code, start_date_active, end_date_active, user_source, phone_check_flag, email_check_flag, password_reset_flag, default_tenant_id, locked_date, date_format, time_format, object_version_number, creation_date, created_by, last_updated_by, last_update_date, birthday, nickname, gender, country_id, region_id, address_detail, tenant_id are all either internal identifiers, system metadata, or non-PII flags. No email, phone, name, address, DOB, SSN, password, or username fields are present.
azazie__hibernate_unique_key.csv0 rows
File structure
Notes: The provided sample appears to be free-form text with no consistent delimiter structure. The content shows a single line 'next_hi' followed by a number '70717', which does not exhibit any structured columnar pattern. There are no visible emails or phone numbers in this snippet, and the data does not conform to a CSV, TSV, or other delimited format. Given the lack of repeated structure and the context of a database dump note, this is treated as unstructured text.
azazie__high_low_id.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only an internal identifier column (high_low_id) with numeric values. No PII fields are present. The values are sequential numeric IDs commonly used as primary keys in databases, which should be skipped per exclusion rules.
azazie__himp_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data appears to be a structured JSON-like data export from an MDM (Master Data Management) system, not a delimited text file with PII. The rows contain metadata about attributes, LOVs (Lists of Values), and data management configurations, but no actual personal identifiable information such as names, emails, addresses, etc. Therefore, no PII columns can be mapped from this sample.
azazie__himp_import.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal metadata (IDs, statuses, dates, counters). No PII fields present. Columns like import_id, batch, status, data_count, object_version_number, creation_date, created_by, last_updated_by, last_update_date, template_code, tenant_id, and param are all internal system identifiers or operational flags. No emails, names, addresses, or other PII detected.
azazie__himp_local_template.csv0 rows
File structure
Notes: This file is structured JSON data representing database templates and configurations, not actual customer PII records. No PII fields are present in this sample data.
azazie__himp_template_header.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal system metadata (IDs, flags, timestamps, template codes). No PII fields are present in this structured dataset.
azazie__himp_template_line.csv4 columns115 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | username | high | [4] column_code value 'realName' maps to a personal identifier; context indicates this is a schema/metadata table describing user fields, and 'realName' is a username-like field |
| 4_phone | phone | high | [4] column_code contains 'phone' literal in row 4 |
| 4_email | high | [4] column_code contains 'email' literal in row 3 | |
| 4_password | password | high | [4] column_code contains 'password' literal in row 2 |
Notes: This is a database schema/metadata table describing column definitions for a user entity, not a direct customer data export. Column [4] 'column_code' contains field identifiers including username, password, email, and phone. Rows 1–5 are schema descriptors. Columns [0], [1], [2], [3], [5]–[23] are internal metadata (IDs, flags, timestamps, validation rules, descriptions) and are skipped as non-PII. The actual user PII data is NOT in this file; this file only documents the structure of where PII is stored in other tables.
azazie__himp_template_line_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a metadata description of database columns rather than actual user data. It contains column names and translations but no PII values. All entries are internal schema definitions and should not be mapped to PII fields.
azazie__himp_template_target.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal database metadata and configuration records. All columns represent system identifiers, timestamps, and operational flags with no personal identifiable information. No PII fields detected.
azazie__hmde_mod_rel_field_pub.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal database relationship identifiers and timestamps. All columns (id, relation_id, master_model_field_code, relation_model_field_code, object_version_number, created_by, creation_date, last_updated_by, last_update_date) are internal system fields or audit timestamps. No PII is present. Columns matching exclusion rules: created_by / last_updated_by are internal IDs (-1 indicates system user), creation_date / last_update_date are timestamps.
azazie__hmde_model_field_pub.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a schema/metadata table describing database fields, not actual customer data. Columns contain field definitions and system metadata rather than personal information. No PII present in this sample.
azazie__hmde_model_object_pub.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is a database metadata table, not containing any PII fields. All columns represent internal database identifiers, codes, and timestamps, which are not personally identifiable information. Therefore, no PII columns are mapped.
azazie__hmde_model_relation_pub.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal database identifiers, relationships, and timestamps. No PII fields are present in this dataset.
azazie__hmsg_email_property.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a configuration or settings table (mail.smtp.ssl.enable) with no PII fields. All columns represent internal system properties and timestamps, which are skipped per rules.
azazie__hmsg_email_server.csv1 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__hmsg_message.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a message/template system table, not customer data. Contains message IDs, types, templates, and status flags. No PII fields are present.
azazie__hmsg_message_receiver.csv1 column2 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | high | [3] header 'receiver_address', values contain both phone numbers (e.g. '15601671767') and email addresses (e.g. 'qymeng@i9i8.com') — mixed field, email values are present |
Notes: Column [3] 'receiver_address' is a mixed field containing both phone numbers and email addresses. Mapped as email to capture the email values; phone numbers in the same column will also be extractable. Columns [0],[1],[4],[5],[7],[8] are internal IDs/counters. Columns [6],[9] are timestamps. Column [10] is an internal flag. Column [2] 'idd' contains international dialing codes (+86) which are not standalone PII without the accompanying number.
azazie__hmsg_message_template.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal system identifiers, template codes, message categories, timestamps, and flags. This appears to be a system message template table unrelated to customer data.
azazie__hmsg_message_transaction.csv1 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__hmsg_notice.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal system identifiers, timestamps, status flags, and codes (e.g., notice_id, lang, title, status_code). Values are system-generated IDs, language codes, status values, and UUIDs. No emails, phone numbers, names, addresses, DOB, SSN, or other PII present.
azazie__hmsg_notice_content.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system metadata (notice IDs, timestamps, version numbers). No PII fields are present. All columns map to skip categories: internal IDs, timestamps, version counters.
azazie__hmsg_receive_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, configuration flags, or timestamps. No PII present. Columns like receive_id, receive_code, parent_receive_id, level_number, tenant_id, object_version_number, creation_date, created_by, last_updated_by, last_update_date, parent_receive_code, and editable_flag are all internal system metadata and do not contain any personally identifiable information.
azazie__hmsg_receive_config_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII fields. It only includes internal configuration identifiers (receive_id), language codes (lang), descriptive names (receive_name), and a static tenant_id. No personal or sensitive data is present.
azazie__hmsg_receiver_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal system identifiers, flags, timestamps, and operational metadata (e.g., receiver_type_id, type_code, creation_date). No names, emails, addresses, or other personal data appear in the sample.
azazie__hmsg_receiver_type_line.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system identifiers and audit timestamps (receiver_type_line_id, receiver_type_id, receive_target_id, etc.). No personal identifiable information (PII) is present. All columns are internal database identifiers or timestamps and should be skipped.
azazie__hmsg_sms_server.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal system identifiers, configuration flags, timestamps, and cryptographic keys. server_name contains non-PII text in Chinese ('平台默认配置' = 'Platform Default Configuration').
azazie__hmsg_template_arg.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system configuration records with no PII. All columns are internal identifiers, timestamps, and technical metadata (arg_id, template_id, arg_name, description, object_version_number, creation_date, created_by, last_updated_by, last_update_date, tenant_id). No personal or sensitive data is present.
azazie__hmsg_template_arg_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a language/translation lookup table with columns: arg_id (internal ID), lang (language code), description (text), and tenant_id (internal reference). None of these columns contain PII. All values are non-personal metadata used for internationalization. This is typical for software localization tables in database dumps.
azazie__hmsg_template_server.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system codes, flags, timestamps, and descriptions with no personal or identifiable information. No PII fields present.
azazie__hmsg_template_server_line.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system metadata or configuration flags (IDs, version numbers, timestamps, status codes). No PII fields are present. The `type_code` column indicates email/password operations but does not contain actual user credentials.
azazie__hot_dress_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with no PII fields. All columns (external_goods_id, provider_id, provider_code, created_stamp, is_used, allocate_rate, pre_allocate_amount, actual_allocate_amount) contain internal IDs, timestamps, flags, and numerical allocation values. No names, emails, addresses, phone numbers, dates of birth, SSNs, passwords, usernames, gender, or other PII are present in the first 50 rows.
azazie__hpfm_audit_login.csv2 columns309 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | phone | high | header "phone" resolves to PII field "phone" |
| 5 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__hpfm_code_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, timestamps, or company/business-related codes. No PII present. Columns like rule_code contain business context ('HPFM.COMPANY', etc.), and timestamps (creation_date, last_update_date) are non-PII system logs. No emails, names, addresses, or other personal data detected.
azazie__hpfm_code_rule_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, flags, timestamps, or codes used for system configuration and sequencing. Values contain only system-generated identifiers, dates, numeric counters, and status flags.
azazie__hpfm_code_rule_dist.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, flags, timestamps, or descriptions. No PII present. Columns like rule_dist_id, rule_id, level_code, used_flag, enabled_flag, object_version_number, created_by, creation_date, last_updated_by, last_update_date, and tenant_id are all internal system fields or timestamps. No email, phone, name, address, DOB, SSN, or other PII fields detected.
azazie__hpfm_code_rule_value.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, flags, or counters. 'rule_value_id', 'rule_detail_id', 'creation_date', 'last_update_date', and similar fields do not contain personal information.
azazie__hpfm_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a configuration table with system settings (TITLE, LOGO, MENU_LAYOUT, etc.). No PII fields are present. Columns like 'created_by' contain numeric IDs (-1) and timestamps are non-DOB. All values are system parameters or URLs, not personal data.
azazie__hpfm_country.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, codes, flags, timestamps, or generic attributes with no personal data. 'country_code' and 'country_name' contain country codes but are not personal identifiers. 'creation_date' and 'last_update_date' are timestamps, not DOB. All other 'attribute' columns appear to be empty or non-PII metadata.
azazie__hpfm_country_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a reference file listing country codes, not actual customer data. Contains no PII fields. All columns are metadata about countries (country_id, language codes, country names, quick index, abbreviations, tenant_id). These are not personal identifiers and should be skipped per exclusion rules.
azazie__hpfm_cusz_model_field_wdg.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains metadata about form fields (widgets, lengths, source codes). No PII is present. All columns are internal configuration data or timestamps and should be skipped.
azazie__hpfm_cusz_unit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal system metadata (unit definitions, IDs, timestamps). No PII fields are present. All columns map to internal IDs, flags, timestamps, or system codes, which must be skipped per exclusion rules.
azazie__hpfm_cusz_unit_field.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a metadata table describing form fields for an application, not customer PII. All columns contain technical identifiers, flags, and timestamps. No PII fields (email, phone, name, etc.) are present.
azazie__hpfm_cusz_unit_field_par.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal configuration/parameter records (unit_field_par_id, tenant_id, param_key, etc.). All columns are internal system identifiers, timestamps, or flags. No PII fields are present. The param_key and param_value columns contain generic system parameters like 'enabledFlag' and 'organizationId', not personal data.
azazie__hpfm_cusz_unit_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal organizational metadata (group definitions, system codes, timestamps) with no personal identifiable information. All columns map to system entities, IDs, and audit timestamps — none correspond to PII fields.
azazie__hpfm_dashboard_card.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal system identifiers, configuration flags, and metadata timestamps. Values are system codes, numeric dimensions, and fixed timestamps.
azazie__hpfm_dashboard_card_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII fields. It appears to be a language translation table for system messages, with columns for ID, language code, name, description, and tenant ID. All values are generic system messages and do not contain any personal or identifiable information.
azazie__hpfm_dashboard_layout.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, flags, counters, or timestamps. No PII present. Columns like id, user_id, role_id, creation_date, last_update_date, etc., are explicitly excluded per rules.
azazie__hpfm_dashboard_role_card.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, flags, or version numbers. No PII present. This appears to be an administrative table tracking database objects and versions, not customer data.
azazie__hpfm_data_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal identifiers, flags, timestamps, or counters. These are excluded per the rules.
azazie__hpfm_data_group_dtl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present. All columns are internal identifiers or timestamps which must be skipped per exclusion rules.
azazie__hpfm_data_group_line.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns appear to be internal IDs, timestamps, and counters. No PII fields are present in the first 50 rows. The columns are: group_line_id, group_id, tenant_id, line_value_id, object_version_number, creation_date, created_by, last_updated_by, last_update_date. All of these are internal identifiers or timestamps and do not contain any personally identifiable information.
azazie__hpfm_datasource.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal database configuration fields (IDs, flags, timestamps, connection strings). No PII is present. Columns like username and password_encrypted contain system/service account credentials, not customer PII. All columns are marked skip per exclusion rules (internal IDs, timestamps, flags).
azazie__hpfm_employee.csv4 columns1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | fullName | high | [2] header 'name', values appear to be personal names |
| 5 | high | [5] header 'email', values contain '@' | |
| 6 | phone | high | [6] header 'mobile', values are 11-digit numbers |
| 7 | gender | high | [7] header 'gender', values are numeric codes representing gender |
Notes: 34 columns total, 4 contain PII (fullName, email, phone, gender). All other columns are internal IDs, status flags, timestamps, or unused attributes.
azazie__hpfm_employee_user.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal IDs, timestamps, or generic attribute placeholders. No emails, names, addresses, DOB, SSN, or other PII appear in the sample.
azazie__hpfm_entity_column.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a database schema export (metadata) showing column definitions, not actual customer data. All columns represent database technical attributes (IDs, types, flags, dates) and contain no PII. No mapping to PII fields is possible.
azazie__hpfm_entity_table.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains database schema metadata (table definitions, field configurations) rather than actual customer records. All columns represent internal system identifiers, flags, timestamps, and technical descriptions. No PII fields are present.
azazie__hpfm_event.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided sample. All columns appear to be internal identifiers, flags, and timestamps. The columns present are: event_id, event_code, enabled_flag, event_description, object_version_number, creation_date, created_by, last_update_date, last_updated_by, tenant_id. These are all internal system fields and do not contain any personally identifiable information.
azazie__hpfm_form_header.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal system identifiers, flags, timestamps, or non-personal metadata. Example values: form identifiers, enabled flags, version numbers, tenant IDs, and audit timestamps. None contain personal information such as names, emails, addresses, or other PII fields.
azazie__hpfm_form_header_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a metadata file describing form structures, not containing customer PII. All values are system identifiers or placeholders. No PII fields present.
azazie__hpfm_form_line.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal system metadata (form configurations, version numbers, timestamps, flags). No PII fields present. Values are system identifiers, numeric counters, status flags, and fixed timestamps. Excluded per exclusion rules: internal IDs (form_line_id, form_header_id, tenant_id, object_version_number, created_by, last_updated_by), timestamps (creation_date, last_update_date), flags (required_flag, enabled_flag, updatable_flag), and non-PII descriptors (item_code, item_name, item_description, item_type_code, value_constraint).
azazie__hpfm_form_line_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII columns. It appears to be a localization or translation table with form line IDs, language codes, and item names/descriptions. All columns are internal identifiers or non-personal metadata.
azazie__hpfm_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, flags, timestamps, and version numbers. No PII present. Columns like group_name contain short alphanumeric codes, not personal names. Timestamps (creation_date, last_update_date) are system logs, not DOB. All columns fall under exclusion rules for internal IDs, flags, and timestamps.
azazie__hpfm_lov.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal system configuration / lookup values table from Azazie's HR/identity management subsystem. All columns contain technical codes, identifiers, and timestamps with no personal or customer data. lov_id and other numeric IDs are internal system identifiers, not user identifiers. lov_code and related fields contain system-level enumeration codes for permissions and authorities. creation_date / last_update_date are system timestamps. No PII present.
azazie__hpfm_lov_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a reference table of lookup values (LOV) for system configuration, not customer PII. All rows contain static code tables with language keys and descriptions. No PII fields detected.
azazie__hpfm_lov_value.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, codes, timestamps, and flags. No PII fields present in the first 50 rows.
azazie__hpfm_lov_value_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a lookup table (lov) containing language translations for system codes and labels, not customer PII. All values are static system metadata (business scope, date formats, locations, financial institutions, etc.). No personal identifiable information is present.
azazie__hpfm_lov_view_header.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal system configuration data (view definitions, permissions, UI settings). No personal identifiable information (PII) is present. All columns represent internal database identifiers, UI metadata, and system timestamps — these are skip columns per policy.
azazie__hpfm_lov_view_header_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only metadata about UI views and lookup values - no actual PII data present. All columns represent UI labels, view names, and system identifiers.
azazie__hpfm_lov_view_line.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a metadata table describing database columns and structure (view definitions). All columns are internal identifiers, flags, timestamps, and technical metadata. No PII fields are present. Columns like view_line_id, tenant_id, lov_id, display, order_seq, field_name, and others are system-generated or descriptive, not containing personal data. The sample values are technical codes and timestamps, confirming the absence of PII.
azazie__hpfm_lov_view_line_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only metadata mappings (language translations for UI labels) with no actual PII values. All columns represent system configuration keys and translations, not personal data fields. No email addresses, phone numbers, names, or other PII appear in the sample rows.
azazie__hpfm_permission_range.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, flags, timestamps, and metadata. No PII present in the first 50 rows. Columns like 'table_name' contain system table names, 'tenant_id' is a numeric identifier, and timestamps are system-generated dates. No personal information such as names, emails, addresses, or phone numbers are visible.
azazie__hpfm_permission_rel.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields present. All columns are internal system identifiers, timestamps, and flags (permission_rel_id, range_id, rule_id, object_version_number, creation_date, created_by, last_updated_by, last_update_date, editable_flag, tenant_id). Values contain only numeric IDs, dates, and status flags.
azazie__hpfm_permission_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal system identifiers, codes, descriptions, timestamps, and flags. The data appears to be database rule configurations from an administrative system, not customer data. There are no fields containing email addresses, phone numbers, names, addresses, or other PII.
azazie__hpfm_prompt.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal system prompts and metadata, not customer PII. All columns are internal IDs, codes, timestamps, and configuration values. No PII fields present.
azazie__hpfm_static_text.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is purely metadata/config table from Azazie system. All columns are internal system identifiers, dates, and configuration flags. No PII present. Columns like 'title' contain Chinese text describing config usage, not personal names. All columns map to skip per rules (company_id, timestamps, internal IDs).
azazie__hpfm_static_text_value.csv0 rows
File structure
Notes: free-form text with embedded emails / phones
azazie__hpfm_tenant.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal tenant/account management data (tenant IDs, flags, timestamps). No PII fields present. All columns are internal identifiers, flags, or timestamps — explicitly excluded by rules (company/business references, internal IDs, timestamps).
azazie__hpfm_tenant_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with tenant configuration data. The columns (tenant_id, lang, tenant_name) do not contain any PII fields. tenant_id is an internal identifier, lang is a language code, and tenant_name appears to be business/operational names for tenants — all non-PII. No emails, names, addresses, etc. are present in this sample.
azazie__hpfm_unit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only organizational / internal identifiers and flags. No personal PII fields (email, phone, name, DOB, address, etc.) are present. Columns like unit_name and quick_index contain business identifiers and codes, not human names or contact info. All columns are marked as skip per the exclusion rules for internal IDs and company-related data.
azazie__hpfm_unit_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and operational codes (unit_id, lang, unit_name, description, quick_index, tenant_id). No PII fields are present. All columns map to skip categories: internal IDs, language codes, and internal operational identifiers.
azazie__hrpt_dataset.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal database metadata (dataset identifiers, SQL queries, timestamps, system flags). No personal information present in this sample.
azazie__hrpt_label_permission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal system identifiers, version tracking, timestamps, and flags. These are non-personal administrative fields typical of a database schema export.
azazie__hrpt_label_print.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only label printing configuration parameters and internal system metadata. No PII fields are present. All columns represent internal system identifiers, numeric settings, and timestamps which are explicitly excluded by the rules.
azazie__hrpt_label_template.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, configuration data, or timestamps. No PII fields detected. Columns contain template IDs, codes, dimensions, flags, version numbers, and audit timestamps — none map to personal data categories.
azazie__hrpt_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal report metadata (IDs, UUIDs, configuration flags, timestamps). No PII is present. All columns map to skip categories: internal IDs, timestamps, flags, configuration data, and non-PII codes/names.
azazie__hrpt_report_permission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, timestamps, or flags (permission_id, report_id, tenant_id, role_id, start_date, end_date, remark, object_version_number, creation_date, created_by, last_updated_by, last_update_date). None contain personal information such as names, emails, addresses, or other PII fields.
azazie__hscode.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product catalog file with HS codes, descriptions, and localized names. No PII fields present. All columns map to product metadata only.
azazie__hsdr_executor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system identifiers, status flags, timestamps, and version numbers. No PII fields are present. Columns like executor_id, tenant_id, created_by, creation_date, last_updated_by, last_update_date, etc., are all internal system metadata and should be skipped per exclusion rules.
azazie__hsdr_job_info.csv1 column3 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 23 | high | [23] contains JSON with 'email' field visible in values |
Notes: Only column 23 contains PII (email embedded in JSON string). All other columns are internal job metadata/timestamps/IDs — no personal data.
azazie__hsdr_job_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system logs or timestamps. No PII fields present. Columns like log_id, job_id, tenant_id, executor_id, IP addresses, URLs, and timestamps are all internal operational data and do not contain personal identifiable information. No emails, names, addresses, phone numbers, DOB, SSN, passwords, usernames, or gender information are present.
azazie__i2mdm_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/attribute metadata (IDs, codes, sequences, dates, flags). No PII fields detected. Values are system identifiers, predefined attribute names in non-Latin script, input types, version numbers, and timestamps. This is typical of an e-commerce product attribute table, not customer data.
azazie__i2mdm_attribute_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, codes, version numbers, and timestamps. No PII fields present. This appears to be a product attribute table (sizes) from Azazie's database.
azazie__i2mdm_attribute_group_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a product attribute group listing from Azazie, containing only internal product catalog data (attribute group IDs, language codes, attribute group names, creation dates). No PII fields are present — all columns represent internal product metadata, not customer or personal information. Therefore, no columns map to PII fields.
azazie__i2mdm_attribute_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product attribute translation file showing attribute IDs with English and Chinese translations. Contains no personal or identifiable information - only product specifications like 'color', 'size', 'Fabric', and localized descriptions. All columns are internal IDs or non-PII product attributes.
azazie__i2mdm_attribute_value.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The dataset appears to be a product attribute table with codes, descriptions, and versioning metadata. All values are non-personal product attributes (e.g., '大钱', '橡胶轮胎', '属性1'). No emails, names, addresses, or other PII fields are present.
azazie__i2mdm_attribute_value_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File is a structured table but contains only product attribute values (colors/sizes) with numeric IDs and language codes. No personal identifiers (PII) present. Columns map to internal product metadata only.
azazie__i2mdm_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent product/category metadata (IDs, codes, names, paths, timestamps). No PII fields detected. Values are internal identifiers, category names in multiple languages, and system timestamps. This appears to be a product catalog schema, not customer data.
azazie__i2mdm_category_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, counters, flags, or timestamps. No PII present. Columns like 'creation_date' and 'last_update_date' are operational timestamps, not DOB. 'tenant_id' and numeric IDs are internal references. No emails, names, addresses, or other PII fields detected.
azazie__i2mdm_category_attribute_value.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product attribute data (IDs, values, sequences). No personal identifiable information (PII) is present. All columns are internal identifiers or product-related values, and are skipped per exclusion rules.
azazie__i2mdm_category_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains category and language mappings for product categories. No PII fields are present — only category IDs, language codes, and translated category names. All columns are non-personal product metadata.
azazie__i2mdm_erp_attribute_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only size attributes and product codes (e.g., 'WD16', 'A14', 'L/XL'). All columns represent product sizing information and internal IDs, which fall under exclusion rules for company/product data.
azazie__i2mdm_event_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. File appears to be product attribute metadata (colors, sizes, measurements) in JSON-formatted CSV rows. Contains no customer or user data fields.
azazie__i2mdm_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal product IDs, timestamps, status flags, and inventory metadata. No PII fields present. The data represents product catalog entries for dresses and accessories, with goods IDs, SKUs, production types, and audit timestamps.
azazie__i2mdm_goods_sku.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product identifiers, timestamps, flags, or inventory codes. No PII fields present — this is a product catalog dump, not customer data. Columns like goods_name contain generic product descriptions ('oo', 'Ethereal Floral Headpiece test'), not personal names.
azazie__i2mdm_goods_sku_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product SKU/attribute identifiers and timestamps. No PII fields are present. All columns map to skip categories (internal IDs, product attributes, version numbers, timestamps).
azazie__iam_label.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be an internal system configuration or permission management table. All columns contain internal identifiers, timestamps, flags, and descriptive metadata. No PII fields (email, phone, name, address, etc.) are present. Columns like 'name' contain system entity labels (e.g., 'HZERO_MENU', 'SIGN_API'), not personal names. Timestamps and numeric IDs are internal system metadata, not personal data. Therefore, no columns map to PII fields.
azazie__iam_label_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a language translation file or metadata table, not containing any personal identifiable information (PII). The columns are identifiers (id), language codes (lang), and static description strings. No PII fields are present.
azazie__iam_local_user.csv3 columns5 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | header "email" resolves to PII field "email" | |
| 4 | fullName | high | header "real_name" resolves to PII field "fullName" |
| 5 | phone | high | header "phone" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__iam_member_role.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, timestamps, and status flags. No PII fields (email, phone, name, address, etc.) are present in this dataset. The columns include IDs, role identifiers, timestamps, and version numbers, which are non-personal and internal to system operations.
azazie__iam_menu.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII columns. All columns are internal system identifiers, configuration flags, and metadata (e.g., id, code, name in non-personal language, parent_id, timestamps). No emails, names, addresses, or other personal data appear in the first 50 rows.
azazie__iam_menu_permission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only system permission codes and timestamps. There are no personal identifiable information (PII) fields present. All columns are internal system identifiers, permission codes, and audit timestamps which must be skipped per exclusion rules.
azazie__iam_menu_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a permissions/actions listing file, not customer data. Columns contain language codes, IDs, and permission names — no PII present. All entries describe system functionality (e.g., '员工定义明细-新增用户'). No emails, names, addresses, or other personal data detected in the sample.
azazie__iam_permission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal API metadata (IDs, paths, methods, timestamps, flags). No PII present. Columns like 'id', 'code', 'path', 'method', 'description', 'action', 'fd_resource', 'public_access', 'login_access', 'service_name', 'is_within', 'object_version_number', 'created_by', 'creation_date', 'last_updated_by', 'last_update_date', 'tag', and 'sign_access' are system identifiers, endpoints, and operational flags — none contain personal data.
azazie__iam_permission_old.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, API routes, and timestamps. No PII present. Columns like 'id', 'code', 'path', 'method', and timestamps are purely technical and contain no personal data. This appears to be an API resource metadata table from an admin system, not customer data.
azazie__iam_permission_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only API endpoint descriptions and IDs - no PII present. All entries are system operation metadata in Chinese, with no personal data fields.
azazie__iam_role.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only role management metadata (role names, IDs, timestamps). No personal identifiable information (PII) fields are present. All columns represent internal system identifiers, flags, and audit timestamps which must be skipped per exclusion rules.
azazie__iam_role_permission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, flags, timestamps, or constants. The file appears to be permission/role mapping data for internal system management.
azazie__iam_role_tl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains language translations for role names and tenant IDs. No PII fields are present. Columns include language codes, IDs, names, role names, and tenant IDs. All data appears to be internal system identifiers and role definitions, not customer personal information.
azazie__iam_user.csv3 columns6 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | header "email" resolves to PII field "email" | |
| 5 | fullName | high | header "real_name" resolves to PII field "fullName" |
| 6 | phone | high | header "phone" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__id_generator.csv0 rows
File structure
Notes: This is a list of numeric IDs only - no PII fields present. The file appears to be a simple ID sequence dump with no other columns or structure. According to the rules, columns containing only internal IDs should be skipped.
azazie__ii_oglc_diff_20170305.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product SKU and inventory data. No PII fields are present. All columns relate to inventory tracking and product codes, which are excluded per the rules.
azazie__ii_stat_20170305.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with columns: erp_sku, inv_qty, CONTAINER_ID, LOCATION_SEQ_ID. All columns contain inventory/product data (SKU codes, quantities, container IDs, and location identifiers). There are no PII fields present in the first 50 rows.
azazie__img_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file contains only internal IDs and attribute references with placeholder dates (0000-00-00 00:00:00). No PII fields are present. The columns represent internal database keys for product attributes, not customer data.
azazie__import_order_shipment_base_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, tracking numbers, shipment metadata, or transactional data. 'bill_belong' appears to be a non-standard field but contains non-PII values (e.g., '飓鱼').
azazie__import_order_shipment_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, transaction codes, or system-controlled values. No PII fields are present. Columns like id, batch_id, tracking_number appear to be system-generated identifiers or tracking codes, not personal identifiers. shipment_ymd, create_time, and last_update_time are timestamps. shipment_type and other_fee_usd/shipment_fee_usd are business transaction fields. No email, name, address, phone, SSN, or other PII is visible.
azazie__import_order_shipment_data_new.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All rows contain only numeric IDs, filenames, and timestamps. No PII fields (email, phone, name, address, etc.) are present in the first 50 rows. The data appears to be internal database metadata (batch IDs, file names, user actions, timestamps) with no personal information exposed.
azazie__import_order_transfer_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/tracking data (IDs, batch names, timestamps, fees, user actions). No PII fields such as names, emails, addresses, or phone numbers are present. All columns are internal identifiers, transaction metadata, or system timestamps, and should be skipped per exclusion rules.
azazie__in_warehouse_alert.csv1 column24 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | [2] header 'email', values contain '@' and domain patterns |
Notes: Only column 2 (index 2) maps to PII field 'email'. Other columns contain internal IDs, timestamps, user flags, or placeholder values that are not PII. No other columns map to firstName, lastName, phone, dob, etc.
azazie__in_warehouse_return_product_note.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal alert records (alert_id, search_key, status_code, notes, timestamps, party_id). No PII fields are present. All columns are internal IDs, flags, or timestamps and are mapped to skip per exclusion rules.
azazie__ingredient.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, numeric codes, timestamps, and financial/transactional values. No PII fields detected.
azazie__init_dispatch_color.csv0 rows
File structure
Notes: This is a free-form text file listing color names (Angel Blue, Black, Blue, etc.). It contains no structured columns or PII. The content is purely product color options and does not include any identifiable personal information.
azazie__innodb_index_stats.csv0 rows
File structure
Notes: The file is a database schema dump showing table and index metadata, not actual customer records. It contains database_name, table_name, index_name, timestamps, and index statistics. No PII fields are present in this metadata export.
azazie__innodb_table_stats.csv0 rows
File structure
Notes: The provided text is a database schema listing from Azazie, showing database tables and their metadata. It contains no actual customer or PII data rows — only table names, row counts, and update timestamps. Therefore, no column mapping is possible or required. This is purely structural metadata, not importable records.
azazie__input_pange_inv_error.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, stock counts, status flags, timestamps, or internal system metadata. No PII fields present.
azazie__input_ppml_pandian_error.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product identifiers, inventory counts, timestamps, and system metadata. Columns 6-15 and 16-19 contain empty or non-PII values. This is consistent with an inventory/product table dump from an e-commerce database.
azazie__insert_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a simple index or metadata file tracking ID ranges for steps. It contains only numeric IDs and keys with no PII. No columns map to PII fields.
azazie__intercept_attribute.csv2 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__intercept_email.csv1 column21 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__internal_properties.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an unstructured data file with no consistent PII columns. The rows appear to be system metadata keys and values, not customer PII. No columns map to PII fields.
azazie__inv_location_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal identifiers (abs_id), numeric codes (check_number), location codes (location_seq_id), user identifiers (action_user), timestamps (start_stamp, end_stamp), status flags (is_process, is_correct, check_count), and categories (stock_taking_category). None map to any of the defined PII fields (email, phone, dob, etc.).
azazie__inv_location_check_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, transaction flags, timestamps, or non-PII metadata. No PII fields detected.
azazie__inv_sale_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only rule metadata (IDs, titles, timestamps, status flags). No PII is present. All columns are internal identifiers, timestamps, or status flags that must be skipped per exclusion rules.
azazie__inv_sale_rule_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, rule metadata, timestamps, and product SKUs. No PII fields detected. Columns like 'action_user' contain system usernames, not customer PII.
azazie__inv_sale_rule_detail_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, or product-related data (id, rule_id, batch_id, rule_type, external_cat_id, external_goods_id, goods_color, uniq_sku, action_user, is_handle, create_time, last_update_time). No email, phone, name, address, DOB, SSN, password, or username fields present.
azazie__inv_sale_rule_sync_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only internal product inventory IDs (rule_id), JSON blobs of product SKUs/quantities, and timestamps. All columns are internal identifiers or operational metadata per the Azazie breach context.
azazie__inv_security_days.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product catalog metadata (IDs, sales metrics, inventory settings, and category groups). No PII fields are present. All columns are internal business identifiers and operational flags, which must be skipped per exclusion rules.
azazie__inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, product data, or timestamps. No PII fields present. Columns like 'id', 'goods_id', 'sku', 'size_id', 'color_id', 'stock', 'stock_locked', 'supplier_stock', 'supplier_stock_locked', 'create_time', and 'last_updated_time' are all non-PII and should be skipped per rules.
azazie__inventory_item.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal inventory management fields (item IDs, timestamps, quantities, costs). No PII is present. Columns like SERIAL_NUMBER, LOT_ID, or SOFT_IDENTIFIER are internal product identifiers, not personal identifiers.
azazie__inventory_item__bakcontainer20170222.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. Both columns (INVENTORY_ITEM_ID and CONTAINER_ID) are internal inventory/container identifiers containing only numeric IDs — all skipped.
azazie__inventory_item__bakcontainer20170305.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. Both columns (INVENTORY_ITEM_ID and CONTAINER_ID) are internal inventory/container identifiers — all values are numeric IDs with no personal information.
azazie__inventory_item_acct_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be an inventory/account type configuration table from Azazie. It contains only internal system codes, descriptions, and timestamps. No PII fields are present. All columns are internal identifiers or operational metadata and should be skipped per exclusion rules.
azazie__inventory_item_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal inventory/transaction identifiers, timestamps, and flags. No PII fields present. Columns like ORDER_ID and INVENTORY_ITEM_ID are internal reference numbers, not customer identifiers.
azazie__inventory_item_in_warehouse_snapshot.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the provided rows. The file appears to contain only inventory management data with internal IDs, product IDs, and timestamps. No personal identifiable information is present in the visible columns.
azazie__inventory_item_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a metadata table describing inventory item types, not customer PII. Columns contain technical IDs, descriptions, and timestamps — no personal information present. All columns are internal system data and should be skipped.
azazie__inventory_item_value_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data contains only numeric IDs, timestamps, and monetary values with no PII fields present. All columns represent internal system identifiers, cost values, and audit timestamps typical of inventory management systems. No names, addresses, emails, or other personal data appear in the sample.
azazie__inventory_item_variance.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal inventory tracking fields (IDs, timestamps, quantities, comments in non-English language). No PII present. Columns contain inventory variance IDs, item IDs, physical inventory IDs, quantity variances, timestamps, and comments about inventory adjustments. These are purely operational/internal identifiers with no personal data.
azazie__inventory_monitor_config_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, operation codes, status flags, timestamps, and system notes. No personal information such as names, emails, phone numbers, addresses, or dates of birth are present in the sample.
azazie__inventory_monitor_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains purely inventory and financial metrics (stock levels, sales numbers, pricing, timestamps). No PII fields are present. All columns map to business/operational data or timestamps, which are excluded by the rules.
azazie__inventory_sales_sku.csv1 column276 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | username | high | [6] header 'action_user', values look like usernames (e.g., 'liwuxie', 'test101') |
Notes: Only column 6 (action_user) contains PII (username). All other columns contain product IDs, colors, sizes, timestamps, and flags which are not personally identifiable information.
azazie__inventory_sales_sku_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields appear to be internal product identifiers (SKU, color codes, size codes), status flags, and timestamps. No personal information such as names, emails, or addresses is present in this dataset.
azazie__inventory_summary.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, inventory status codes, or operational metrics. No PII fields detected.
azazie__inventory_sync.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, action flags, timestamps, and operational data. The file appears to be an order inventory log from Azazie, tracking stock actions and synchronization status between warehouses and the system. No personal customer data (emails, names, addresses, etc.) is present in the first 50 rows.
azazie__inventory_sync_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a structured CSV with headers, but the data rows contain only system-generated inventory/order management records with no PII fields. All entries are error logs or internal transaction IDs, SKU mappings, and stock changes without any personal information such as names, emails, or addresses. No columns map to PII categories.
azazie__inventory_sync_snap.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible columns are internal IDs (snap_id), SKU codes (uniq_sku), stock levels, user actions (action_user), and timestamps. No emails, phone numbers, names, addresses, DOBs, SSNs, passwords, usernames, or other PII fields appear in the first 50 rows.
azazie__inventory_transaction.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal inventory transaction records with no PII. Columns contain transaction IDs, status codes, timestamps, and facility/container IDs. No email, phone, name, address, or other PII fields are present.
azazie__inventory_value_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data appears to be a structured JSON-like string embedded within a CSV format, representing inventory records for dresses and accessories. However, there are no identifiable PII fields (such as email, phone, name, address, etc.) present in the visible rows. The data consists entirely of product-related information (SKU, description, inventory counts, costs) and timestamps, which do not qualify as PII under the defined categories. No columns map to any of the available PII field types.
azazie__inventory_warehouse_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product inventory table with no PII fields. All columns represent product IDs, inventory metrics, and timestamps. No personal or sensitive customer data is present.
azazie__inventory_warehouse_monitor_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory and operational data. No PII fields are present. Columns include IDs, stock levels, SKU codes, and timestamps, all of which are internal business data and do not contain any personal information.
azazie__invitation_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transactional data (IDs, prices, timestamps). No PII fields are present. All columns are marked as skip per exclusion rules (internal IDs, financial/transactional data, timestamps).
azazie__invitation_goods_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product attribute table with no PII fields. All columns contain product metadata (attribute_id, attribute_name, attribute_value, is_use) and color/accessory options for dresses.
azazie__invitation_goods_attribute_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product attributes (size types, accessories, paper types, etc.) and no personal identifiable information (PII). All columns are product-related metadata and should be skipped per exclusion rules.
azazie__invitation_goods_purchase_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product attributes or operational timestamps. No PII present. Columns like id, external_goods_id, provider_code, attribute_name (color), attribute_value (color names), price, is_set_price flag, is_delete flag, create_time, update_time, and operator are all internal system fields or non-PII product data.
azazie__invitation_goods_purchase_price_ik.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product pricing and internal operational data (attribute relations, provider codes, timestamps). No PII fields are present. All columns map to internal IDs, prices, flags, and timestamps which are excluded by policy.
azazie__is_section321_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file lacks headers and contains only numeric IDs and timestamps. No identifiable PII fields (email, phone, name, address, etc.) are present in the visible rows. Columns map to internal IDs and timestamps, which are excluded by policy.
azazie__issworksheet_display_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file is unstructured text with no consistent columnar data; it consists of daily production and inventory logs without any personal identifiable information (PII).
azazie__items_without_paperwork.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/tracking data (IDs, scan flags, timestamps, notes). No PII fields are present. All columns map to skip categories: internal IDs (id, dispatch_sn), status flags (is_scanned), notes (note), timestamps (action_time), and generic user reference (action_user).
azazie__jcex_request_json.csv7 columns100 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | fullName | high | [0] header 'fullName', values are full names |
| 1 | phone | high | [1] header 'phone', values are 10-12 digit numbers with optional spaces |
| 2 | address1 | high | [2] header 'address1', values contain street addresses, apartment units, and complex names |
| 3 | city | high | [3] header 'city', values are city/town names |
| 4 | state | high | [4] header 'state', values are state/region names or empty |
| 5 | zip | high | [5] header 'zip', values are numeric postal codes or empty |
| 6 | country | high | [6] header 'country', values are 2-letter country codes (US, DE, FR, GB, AU) |
Notes: 7 columns total, all contain PII. Columns map directly to fullName, phone, address1, city, state, zip, and country. No internal IDs, flags, or non-PII columns present in this sample.
azazie__jjs_country_refund_gather.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, timestamps, financial/transactional data, or internal flags. Columns like 'country' contain numeric codes rather than textual country names. No emails, names, addresses, phone numbers, DOB, SSN, passwords, or usernames detected.
azazie__jjs_daily_dispatchlist.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational statistics — no PII present. Columns are internal IDs (abs_id), dates (statistics_date), and counters for dispatch lists. All columns are non-PII per exclusion rules.
azazie__jjs_data_packet.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, status flags, or counters. No PII fields present. 'address' column contains file paths, not personal addresses. 'create_user'/'update_user'/'check_user' contain system usernames, not customer identifiers.
azazie__jjs_data_packet_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal audit/activity log table (file access tracking). All columns are operational metadata: auto-increment IDs, packet IDs, internal usernames (system accounts like 'rhu', 'ylzheng', 'abc'), timestamps, internal IP addresses, and action type codes. No customer PII is present.
azazie__jjs_dress_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, codes, flags, timestamps, or counters. No emails, names, addresses, phone numbers, DOB, SSN, passwords, usernames, or other PII fields are visible in the sample.
azazie__jjs_factory_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (group IDs, factory names, action users, timestamps). No PII fields are present. All columns map to internal identifiers, flags, or timestamps which must be skipped per exclusion rules.
azazie__jjs_factory_group_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (group_id, provider_id) and audit logs (action_user, action_time). No PII fields present. All columns are internal tracking data and should be skipped per exclusion rules.
azazie__jjs_inspect_stock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns appear to be internal identifiers, inventory codes, timestamps, and system status flags. Values contain only product IDs, stock levels, and system timestamps with no personal information.
azazie__jjs_inspect_stock_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product IDs (uniq_sku), inventory counts (in_stock), user identifiers (action_user), and timestamps (create_time). No PII fields are present. The 'action_user' values appear to be internal system usernames, not actual user PII.
azazie__jjs_inspect_stock_dispatch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order/shipment tracking data with no PII fields. Columns include internal IDs (abs_id), SKU codes (uniq_sku), provider IDs, dispatch serial numbers, timestamps, user assignments, and status flags. All columns are non-PII operational metadata and should be skipped.
azazie__jjs_mutiple_refund_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, financial/transactional data, or other non-PII fields. No PII present in the first 50 rows.
azazie__jjs_mutiple_refund_gather.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal IDs, timestamps, transaction codes, or financial amounts. This appears to be an order/shipment tracking table rather than customer personal data.
azazie__jjs_operation_shop.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, cost metrics, or flags. No PII fields present. 'name' contains non-English shop names (store names), not personal names.
azazie__jjs_operation_shop_ids.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. All columns are excluded per rules: 'id' and 'shop_id' are internal IDs, 'external_goods_id' is likely a product/sku identifier, and all timestamp columns are non-PII. No PII present.
azazie__jjs_operation_shop_manager.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but none of the columns contain PII. The columns present are internal IDs, shop identifiers, manager names (which appear to be internal usernames rather than real names), timestamps, and status flags. All columns fall under the 'skip' category per the rules (internal IDs, timestamps, internal flags).
azazie__jjs_overseas_warehouse.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns detected. All fields appear to be internal IDs, numeric codes, and status flags. The dataset consists of inventory or product tracking records with SKU-like identifiers and usage flags, but contains no personal information such as names, emails, addresses, or dates of birth.
azazie__jjs_overseas_warehouse_goods_weight.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a simple product data file with no PII. Columns are id (internal ID), erp_sku (internal product code), and weight (numeric weight). No personal or sensitive data present.
azazie__jjs_overseas_warehouse_shipment.csv7 columns24 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | address1 | high | header "address" resolves to PII field "address1" |
| 5 | city | high | header "city" resolves to PII field "city" |
| 6 | state | high | header "state" resolves to PII field "state" |
| 7 | zip | high | header "postal_code" resolves to PII field "zip" |
| 8 | country | high | header "country" resolves to PII field "country" |
| 9 | phone | high | header "buyer_phone" resolves to PII field "phone" |
| 10 | high | header "buyer_email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__jjs_provider_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be an internal operational table with no PII. Columns are provider_id, limit_special, create_time, create_user, update_time, and update_user. While create_user and update_user contain usernames ('xiadan1'), these are internal system users, not customer PII. Timestamps and numeric IDs are internal tracking fields per exclusion rules. No email, phone, address, or other personal identifiers present.
azazie__jjs_return_apply.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. This appears to be an internal operational/logistics table (return apply records) with timestamps, status flags, internal IDs, and system usernames (create_user values appear to be internal staff/system logins in Chinese, not customer PII).
azazie__jjs_return_apply_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and barcodes (abs_id, return_apply_detail_id, bar_code). There are no personal identifiers or PII fields present in the first 50 rows. The bar_code values appear to be internal reference codes or placeholders, not addresses or other PII.
azazie__jjs_return_upload.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file is purely transactional with internal IDs, timestamps, status flags, and image metadata. No PII fields (names, emails, addresses, etc.) are present. Columns: abs_id (internal ID), created_stamp (timestamp), goods_sn (product code), action_user (internal username), pic_name (image filename), status (order status), order_sn (order number), pic_path (file path). All columns are non-PII per exclusion rules.
azazie__jjs_sale_cat_20151207.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a sales/orders file with only transactional data (dates, categories, order numbers, quantities, amounts). No PII fields are present. All columns are internal business data or financials and must be skipped per exclusion rules.
azazie__jjs_sale_cat_country_20151207.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a transactional sales file with order details, not customer PII. Columns contain sale_date, category IDs/names, country codes/names, order numbers, quantities, amounts and costs. No personal identifiers (names, emails, addresses, etc.) are present. All columns fall under skip rules: transactional data, internal IDs (cat_id), and financial values.
azazie__jjs_sale_country_20151207.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional data (sale_date, country_id, country, order_number, goods_number, goods_amount, goods_cost). No PII fields are present. Columns like country_id and country are not considered PII per the rules. All columns are skipped.
azazie__jjs_sale_total_20151207.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a sales/order data file with only transaction details (dates, order numbers, goods counts, monetary amounts). No PII fields present. All columns are transactional and fall under the exclusion rules (financial/transactional data, timestamps).
azazie__jjs_sales_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the provided rows. The file appears to be an order details export containing only transactional data (order IDs, timestamps, quantities, amounts, product IDs, country/party IDs). No personal information such as names, emails, addresses, or account details is present in this sample.
azazie__jjs_track_reason_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and codes (abs_id, ori_reason_id, cur_reason_id). No PII fields are present. Values appear to be numeric codes mapping reasons or statuses, not personal data. All columns are marked as skip per exclusion rules for internal identifiers.
azazie__jjs_vb_goods_id_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product IDs and usage flags (jjs_goods_id, vb_goods_id, is_used). No PII fields are present. Columns map to product database metadata, not customer data.
azazie__jjs_zipper_batch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal batch IDs, batch serial numbers, action user names, and timestamps. All columns represent internal system tracking data (batch_id, batch_sn), action performers (action_user), and creation timestamps (create_time). These are operational metadata and do not contain any personal identifiable information (PII). No columns map to PII fields.
azazie__jjs_zipper_batch_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers (abs_id, batch_id, purchase_id). No PII fields are present. All columns are skipped per exclusion rules (internal IDs).
azazie__jjs_zipper_sku.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields appear to be product/color catalog data (IDs, color codes, descriptions in Chinese/English). No email, phone, name, address, or other personal data present in the first 50 rows.
azazie__jobs.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a job queue dump (Laravel) with serialized command objects. Contains no actual PII fields — only system identifiers and serialized object structures. The 'providerPhone' value '11111111111' appears to be a placeholder/test number, not real PII. No columns map to defined PII fields.
azazie__json_20200905_need_del_01.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only inventory/transaction data with no PII fields. All columns are internal identifiers, timestamps, and numeric quantities related to inventory management.
azazie__json_20200905_need_del_02.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains purely inventory/transactional data with no PII fields. All columns are internal identifiers, timestamps, and quantity changes — no names, addresses, emails, or other personal data present. The data appears to be system-level inventory tracking for products.
azazie__json_20200908_oird.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal product/inventory IDs, quantities, and timestamps. No PII fields are present. The data appears to be transactional details for order reservations and inventory management, typical of an e-commerce backend system.
azazie__json_20200910_iid.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a pure inventory/warehouse CSV with no PII fields. All columns are internal inventory identifiers, product IDs, and timestamps. No personal data present.
azazie__json_20200912_company_user.csv3 columns3,120 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | fullName | high | header "display_name" resolves to PII field "fullName" |
| 6 | high | header "email" resolves to PII field "email" | |
| 7 | skip | high | header "mobile" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__json_20200915_eog_delete.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, inventory codes, timestamps, or transaction identifiers. No PII fields detected. The data represents order/inventory management records from Azazie, not customer personal data.
azazie__json_20200916_eog_delete.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory and order tracking fields. All columns are internal IDs, timestamps, or product codes — no PII present. Columns like 'id', 'order_id', 'uniq_sku', and timestamps are system-generated identifiers or transaction logs, which are explicitly excluded by the rules.
azazie__json_20200917_eog_delete.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory/order management IDs and timestamps. No PII fields present. All columns are internal IDs (order IDs, inventory IDs, timestamps) or numeric counters — none map to email, phone, name, address, etc. This aligns with the breach context (inventory/order records) and contains no customer PII.
azazie__json_20200917_iid_delete.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an inventory management table from Azazie with no PII fields. Columns contain internal IDs, timestamps, quantities, and transaction details. No email, phone, name, address, DOB, SSN, or other PII is present. All columns are internal identifiers or operational metadata and are mapped to 'skip' per rules.
azazie__json_20200918_iid_delete.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal inventory identifiers, timestamps, and operational counters. No PII fields detected.
azazie__json_20200922_iid_delete.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal inventory/operational identifiers, timestamps, and transaction counters. No names, addresses, emails, phones, DOB, or SSN present.
azazie__json_20200923_eog_delete.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory and order tracking fields. All columns are identifiers, inventory counts, timestamps, or product references. No PII is present.
azazie__json_20200924_iid_delete.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only inventory and transactional data with no PII fields. All columns are internal IDs, timestamps, quantities, and operational codes.
azazie__json_20200925_iid_delete.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an inventory management table from Azazie containing product stock levels and transaction timestamps. All columns are internal identifiers, numeric quantities, or timestamps — no PII fields present. Columns like id, INVENTORY_ITEM_ID, ORDER_ID are internal reference numbers, and timestamps (CREATED_STAMP, create_time, last_update_time) are system logs. No emails, names, addresses, or other personal data appear in the sample.
azazie__json_20200927_iid_delete.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields present. All columns are internal inventory IDs, timestamps, transaction IDs, and operational counters. No personal customer data (names, emails, addresses, etc.) is exposed in this dataset.
azazie__json_20200928_iid_delete.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only inventory/transactional data columns. No PII fields present. All columns are internal IDs, numeric counts, timestamps, and transaction codes. These are excluded by rules for internal IDs, timestamps, and transactional data.
azazie__json_20201106_error_sku_001.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, or product SKUs — no PII present. Columns like id, taobao_order_sn, rec_id, order_id, external_goods_id, uniq_sku, new_long_sku, short_code, old_goods_id, new_goods_id, create_time, and last_update_time contain only internal system identifiers, transactional codes, or timestamps. None map to PII fields.
azazie__json_20201106_error_sku_002.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, order references, timestamps, and product identifiers. No PII fields are present in this structured dataset.
azazie__json_20201127_need_del.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields found. All columns are internal IDs, inventory tracking numbers, timestamps, and transaction identifiers. Columns contain order IDs, SKU codes, inventory IDs, timestamps, and other operational data with no personal information.
azazie__json_20201205_iid_delete.csv1 column1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | [2] header is 'email', values contain valid email addresses |
Notes: Only column 2 (email) contains PII. All other columns are internal IDs, timestamps, inventory counters, or transaction codes — none contain personal information. This appears to be an inventory/order tracking table rather than customer data.
azazie__json_20210220_err_mps_due_date_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, order references, status flags, and timestamps. No PII present. Columns like 'id', 'DISPATCH_LIST_ID', 'taobao_order_sn' are internal identifiers or transaction references. Timestamps (SUBMIT_DATE, DUE_DATE, mps_due_date, create_time, last_update_time) are operational logs, not personal data. No names, emails, addresses, or other PII fields detected.
azazie__k.csv0 rows
File structure
Notes: free-form text with embedded emails / phones
azazie__klarna_capture.csv12 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__klarna_refund.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal transaction IDs, status flags, timestamps, and amounts — no PII present. Columns like abs_id, refund_id, klarna_refund_id, klarna_idempotency_key, status, error_message, action_user, create_time, last_update_time, refund_amount contain only internal identifiers, numeric codes, user roles, and timestamps. No email, phone, name, address, DOB, SSN, or password fields detected.
azazie__knock_alert.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system identifiers and timestamps. No PII fields are present. The columns (id, robot, robot_key, create_time, last_update_time) are all internal tracking fields or timestamps, which must be skipped per the exclusion rules. No emails, names, addresses, or other PII appear in the sample rows.
azazie__lack_goods_cancel_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal identifiers, timestamps, or operational flags (action_id, action_user, action_time, party_id, dispatch_sn, is_closed, order_id, taobao_order_sn, uniq_sku). None contain personal data like names, emails, addresses, or other PII fields.
azazie__lack_new_warning_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product inventory data (stock levels, sizes, colors) with no personal identifiable information. All columns appear to be internal product identifiers, stock counts, and timestamps. No PII fields detected.
azazie__lack_warning_history.csv0 rows
azazie__lack_warning_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and timestamps. No PII fields are present. Columns like abs_id (internal ID), goods_category, external_goods_id, lack_uniq_sku, create_time, and last_update_time are all non-PII per the exclusion rules.
azazie__language_package.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only UI labels/translations (Chinese and English pairs) for order tracking and shipping information — no actual customer data or PII values present. All entries are static interface text elements.
azazie__languages.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains language configuration data with no PII fields. All columns represent language IDs, names, codes, status flags, ordering, and timestamps — none contain personal identifiable information. No emails, names, addresses, or other PII appear in the sample.
azazie__lc_agent_info.csv2 columns6 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | firstName | high | [1] header is 'agent', values are personal names |
| 2 | high | [2] header is 'email', values contain '@' symbols |
Notes: 4 columns total, 2 contain PII: email and firstName. Columns 0 (abs_id) and 3 (team) are internal identifiers and team codes — skipped.
azazie__lc_agent_op_history.csv3 columns14 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | fullName | high | [0] header 'abs_id', but values are human-readable names (e.g., Emma, Owen, lynn). However, since 'abs_id' is typically an internal ID, we treat this as fullName because the values are names and not numeric IDs. If this were truly an ID, it would likely be numeric/auto-generated. |
| 1 | fullName | high | [1] header 'agent', values are human-readable names (e.g., Emma, Owen, lynn). These are clearly personal names used as identifiers, not internal IDs. |
| 2 | high | [2] header 'email', values contain @ symbols and domain structures |
Notes: This appears to be a log or activity table from Azazie. Only columns 0 (abs_id), 1 (agent), and 2 (email) contain PII. Column 0 and 1 both map to fullName due to the presence of human-readable names, despite the ambiguous headers. All other columns contain non-PII data (team codes, timestamps, actions, types).
azazie__lc_agent_team_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal team identifiers and creation metadata. No PII fields are present. All columns are either internal codes (team_code, team_name) or timestamps/user identifiers (create_stamp, action_user) which are excluded by rules for internal IDs and timestamps.
azazie__lc_chat_agent.csv1 column18,149 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__lc_chat_info.csv169,811 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__lc_chat_owner.csv2 columns10,222 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | [0] internal IDs (chat_id) - numeric/unique identifiers |
| 1 | fullName | high | [1] operator_name contains human names only (no businesses) |
Notes: Only two columns present: chat_id (internal ID) and operator_name (fullName). No other PII fields in this file.
azazie__lc_chat_tag.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only two columns (chat_id and tag) with no PII fields. Values are internal identifiers and status tags (Order-pro, Pre-sale, After-sale, etc.). No emails, names, addresses, or other personal data present.
azazie__lc_daily_statictic.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only internal operational counters (abs_id, create_date, group_id, queued_count, left_queue, entered_chat). No PII fields present. All columns are internal IDs, timestamps, or numeric counters per the exclusion rules.
azazie__lc_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only group IDs and names in multiple languages, no PII fields present. All columns are internal grouping identifiers and language codes.
azazie__lc_owner_set_history.csv1 column40 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | fullName | high | [2] header 'owner_name', values are personal names like 'Jessica', 'Floyd', 'Emma', 'Lily', 'Doris' |
Notes: Only column 2 (index 2) contains PII - personal names. All other columns are internal IDs (abs_id, chat_id), timestamps (create_stamp), and system usernames (action_user) — these are excluded per skip rules. No emails, phones, addresses, DOB, SSN, gender, suffix, or passwords are present.
azazie__lc_tag_del_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. All columns contain internal IDs (abs_id, chat_id), status tags (tag), timestamps (create_time), and action users (wmzhen, lmzheng, llm). These are internal tracking fields with no personal information.
azazie__leopard_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only three columns: order_id, carrier_bill_id, and SHIPMENT_ID. These are all internal identifiers and do not contain any PII. No email addresses, phone numbers, names, addresses, dates of birth, or SSNs are present in the sample data.
azazie__limit_zip_code_and_city.csv3 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | country | high | [1] header 'country', values are numeric country codes |
| 2 | zip | high | [2] header 'zipcode', values match ZIP code patterns |
| 3 | city | medium | [3] header 'city', values appear to be geographic codes or city identifiers |
Notes: Only three columns contain PII: country, zip, and city. All other columns are timestamps or internal flags and have been skipped per rules.
azazie__livechat_daily_statistic_temp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This is a simple 3-column numeric file with queue statistics (queued_count, left_count, entered_count). No PII is present, only internal operational counters. No columns map to any PII fields.
azazie__livechat_orders_amount_temp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a two-column CSV with order amounts and order counts. No PII present. Columns: orders_amount (numeric order value), new_valiad_order_count (integer order count). No identifiable personal data found in these fields.
azazie__livechat_statistic_format.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII columns. All columns represent aggregated statistical data about chat counts, order rates, and financial metrics, with no personal information such as names, emails, or addresses. The values are numerical or percentage-based statistics, not individual customer data.
azazie__livechat_statistic_group_temp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only internal chat IDs and status flags. No PII fields present. All columns are internal identifiers or status codes (chat_id, has_order, tag, rate) which must be skipped per exclusion rules.
azazie__livechat_statistic_show.csv0 rows
File structure
Notes: This is a summary statistics table (language-specific order metrics), not customer PII. No columns map to PII fields.
azazie__log.csv5 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__log_app_login.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (id, user_id) and timestamps (create_time). No PII fields are present. All columns map to skip categories: internal IDs and timestamps.
azazie__login_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a configuration file, not containing any PII. All columns map to internal configuration settings and flags. No personal identifiable information is present.
azazie__login_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. The dataset only contains internal account aliases, IP addresses (network identifiers, not physical addresses), and timestamps — all excluded by policy. No emails, names, phone numbers, addresses, DOB, SSN, passwords, or usernames are visible.
azazie__lzliu.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only numeric data with no identifiable PII fields. All columns appear to be simple numeric counters or indices, with no headers or meaningful values that map to PII categories. No emails, names, addresses, or other PII are present in the sample rows.
azazie__lzliu_t1.csv3 columns2,801 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | unlabeled column — sampled values parse as email addresses | |
| 3 | address1 | high | header "address" resolves to PII field "address1" |
| 4 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__main_distributor.csv3 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | fullName | high | [1] header 'name', values are full names in Chinese characters |
| 2 | fullName | high | [2] header 'contact', values are full names in Chinese characters (same as name field) |
| 9 | skip | high | [9] header 'mobile', values are numeric phone numbers |
Notes: Only columns 1, 2, and 9 contain PII. Column 1 and 2 both appear to be the same full name field. Columns 0, 3-6, 7-8, 10 are internal IDs, comments, business type, or numeric amounts — skipped per exclusion rules.
azazie__mark_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent product material data and internal system metadata (IDs, timestamps, action users). No PII fields are present. The columns describe fabric types, material compositions, and database operation logs for product records.
azazie__material_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product category metadata (mcat_id, mcat_name, supplier_id, is_used). No PII fields are present. All columns are internal product catalog data and should be skipped.
azazie__material_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal product metadata (IDs, material names, inventory counts, timestamps, status flags). No customer or personal data present in this subset.
azazie__material_color.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only color ID mappings and descriptions (mcolor_id, mcolor_en_name, mcolor_ch_name, supplier_id, is_used). No PII fields are present. All columns are internal product attributes and should be skipped.
azazie__material_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal product/material detail codes, IDs, timestamps, and flags. Columns like mdetail_id, mcat_name, mname_name, mcolor_ch_name, create_time, action_user, and is_used contain product metadata, not personal data. This is a product catalog/material specification table from Azazie's inventory system.
azazie__material_invenory_item.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal inventory identifiers, timestamps, and flags — no PII present. Columns like mitem_id, inventory_type, supplier_provider_name, and create_time contain operational data only. No emails, names, addresses, or other personal data appear in the sample.
azazie__material_invenory_summary.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/order identifiers, pricing data, timestamps, and flags. No personal identifiable information (PII) fields are present. Columns map to product codes, monetary values, timestamps, and status flags — all skip categories.
azazie__material_name.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a simple product/material reference table with no PII fields. Columns describe material IDs, material names, category IDs, supplier IDs, and usage flags — all internal business data. No personal or identifiable information is present.
azazie__material_process_price_change_summary.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, status flags, price deltas, timestamps, and action/user metadata. No names, emails, addresses, or other personal data appear in the sample.
azazie__material_purchase.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal purchase/order metadata (IDs, codes, prices, timestamps, flags). No PII fields detected. Columns like 'supplier_provider_name' contain business names, not personal data. Timestamps and IDs are explicitly non-PII per exclusion rules.
azazie__material_scrap.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers, timestamps, status flags, and codes. No PII fields present. Columns map to internal IDs (mscrap_id, mdetail_id), product codes (mdetail_code), amounts, types, status flags, users, notes, supplier IDs, and usage flags — none constitute personal PII under the defined schema.
azazie__material_ticket.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, status flags, or free-text notes. 'username' and 'last_response_username' contain numeric or non-personal values. No emails, phones, names, addresses, DOB, SSN, or passwords present.
azazie__material_ticket_message.csv1 column1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header 'username', values are alphanumeric strings that could be usernames |
Notes: This file appears to be a ticket system log with no PII beyond username. The message column contains non-PII Chinese text ('公司给你回复了' translates to 'The company replied to you'). All other columns are internal IDs, timestamps, or numeric IDs.
azazie__material_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file but contains no PII fields. Columns are: mtype_id (internal ID), mtype_name (product type name), supplier_id (internal ID), is_used (flag). All columns are internal identifiers or flags and do not contain any personal identifiable information per the exclusion rules.
azazie__material_unit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and flags. No PII fields are present. The columns 'munit_id', 'munit_name', 'supplier_id', and 'is_used' are all internal IDs or flags and do not contain any personally identifiable information.
azazie__menus.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal permissions/routes table from Azazie's admin panel. No PII is present; columns contain UI route metadata, hierarchy IDs, timestamps. All columns map to skip categories (internal IDs, flags, timestamps).
azazie__message.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, timestamps, status codes, order numbers, service types, and free-text messages without personal data. The processor column contains short usernames but these appear to be internal system accounts rather than customer identifiers.
azazie__metrics.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a code metrics file (lines of code statistics), not customer data. All columns are internal metrics (id, description, values, flags). No PII fields present. Columns like 'name' and 'description' contain technical labels, not personal names or addresses.
azazie__migrations.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The provided data consists solely of table creation metadata (migration IDs, SQL table names, and batch numbers) with no actual record data. There are no columns containing personal information, identifiers, or structured PII fields. This appears to be a schema migration log rather than a data dump containing customer or user information.
azazie__model_has_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal relational IDs (cpl_id, model_type, model_id) linking records to users. No PII fields are present. The values are numeric IDs and model references, which are excluded per exclusion rules for internal IDs.
azazie__model_has_facility.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All three columns (facility_id, model_type, model_id) are internal system/relational identifiers — facility IDs, ORM model class names, and record IDs. None contain personal information.
azazie__model_has_party.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured table mapping internal party IDs to user model relationships. No PII fields present — contains only internal relational IDs (party_id, model_type, model_id). All columns are internal identifiers and should be skipped.
azazie__model_has_permissions.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal permission mappings (permission_id, model_type, model_id). No PII fields are present. All rows appear to be system permissions linking users to models, with no personal data exposed.
azazie__model_has_roles.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a role-permission mapping table showing role_id and model_id relationships for user records. Contains only internal IDs (role_id, model_type, model_id) with no personal identifying information. All values are numeric identifiers or model type strings, no PII present.
azazie__monitor_ops_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns appear to be internal identifiers (mol_id, ops_log_id, party_id), action codes (action_id), order numbers (order_sn), and timestamps (date). These are operational logs without personal customer data.
azazie__move_storage_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers (abs_id), timestamps (create_time), transaction codes (external_goods_id, move_number), party IDs (from_party, to_party), user identifiers (action_user), and status flags (is_process). No PII fields are present. This appears to be an order/shipment movement log table.
azazie__move_storage_log_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational IDs and tracking numbers (abs_id, action_id, order_sn_gt, order_sn_c, move_number). No PII fields are present. Columns map to internal database identifiers and order references, which are excluded per rules.
azazie__moving_pin_rate_report_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the first 50 rows. The file appears to contain only product inventory data (IDs, colors, stock levels) with no customer or personal information.
azazie__mps_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a structured dataset but contains no PII columns. All columns represent internal identifiers, codes, and JSON payloads with state codes or success statuses, none of which map to personal identifiable information fields. No emails, phone numbers, names, addresses, DOB, SSN, or other PII are present in the first 50 rows.
azazie__mps_user_party.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII detected in first 50 rows. All columns appear to be internal IDs (abs_id, user_id, party_id), timestamps (create_stamp), and usernames (create_user_name). These match the exclusion rules for internal IDs and timestamps. No emails, phones, names, addresses, DOBs, or SSNs visible.
azazie__multilanguage.csv286 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__multilanguage_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII. It appears to be a language translation table with internal codes and messages. All columns represent internal metadata or non-personal content (multilanguage_queue_id, code, language_code, language, type, ctime). No personal identifiers are present.
azazie__multilanguage_queue.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII fields. It appears to be a multilingual queue table with identifiers, codes, language codes, types, statuses, and timestamps. All columns are internal system identifiers or metadata, with no personal or sensitive information.
azazie__mutiple_return_rate_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns represent internal identifiers, shipment/return counts, rates, and timestamps. No emails, names, addresses, phone numbers, DOB, SSN, or passwords are present.
azazie__mutiple_return_rate_gather.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal operational metrics (IDs, counts, rates, timestamps) with no personal data. abs_id is a numeric internal ID, ship_date/update_time are timestamps, D_type and various *_number/rate columns track product/shipping statistics. No PII fields present.
azazie__my_pro_factory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product reference table with provider codes, external category IDs, and factory IDs. No PII fields are present. All columns are internal identifiers or business codes. The data appears to be structured product catalog information rather than customer data.
azazie__my_table_157.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in this file. The data consists of order IDs, SKUs, order timestamps, and delivery date ranges, which are all transactional and operational data with no personal identifiable information.
azazie__my_table_pro_147.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains only order IDs, SKU codes, order timestamps, and estimated delivery dates/ranges — all transactional metadata with no personal information.
azazie__my_table_pro_147_view.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only order IDs (taobao_order_sn), product SKUs (sku), category IDs (ext_cat_id), order timestamps (order_time), and delivery estimates. All columns are internal order/transaction identifiers or timestamps, which do not contain personal information.
azazie__new_dispatch_goods_proportion.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a statistical summary file showing rankings and proportions, not containing any PII fields. All columns represent aggregated metrics and counts, therefore no PII columns to map.
azazie__new_product_sale_info_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional and operational data (IDs, amounts, dates, product types). No PII fields are present. All columns are internal IDs, financial totals, timestamps, or product categorizations and are excluded per exclusion rules.
azazie__newarrival_goods_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, numeric product identifiers, timestamps, and status flags. Values are numeric IDs, ISO timestamps, and single-character status codes with no personal data.
azazie__next_allocate_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, provider IDs, and timestamps. No PII fields are present. All columns are marked as skip per the exclusion rules (internal IDs and timestamps).
azazie__normal_page.csv1 column3 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | emailText | high | free-text column with embedded emails (3/11 cells, 27% density) |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__notification.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal messaging or chat logs (abs_id, title, content, timestamps, sender/receiver IDs). No identifiable PII fields (email, phone, name, address, etc.) are present. All columns are internal IDs, message metadata, or content strings without personal data. The 'sender_name' field appears to be a generic alias ('lm') rather than a real name. Per exclusion rules, sender_id (numeric) is skipped as an internal ID. No PII columns to map.
azazie__notification_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only notification metadata (IDs, read status, timestamps) with no personal identifiers. All columns are internal tracking fields and therefore skipped per exclusion rules.
azazie__nouse_waybill.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, timestamps, flags, or operational data (e.g., print_time, facility_id, waybill_no, shipment_id, express_name, er_id, is_white, is_cancelled, exec_log, created_time, last_updated_time, last_updated_user). No personal identifiable information detected in the first 50 rows.
azazie__nqa_customer_word.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction IDs, timestamps, and user-facing free-text notes. No identifiable PII fields (emails, names, addresses, etc.) are present. All columns map to skip per exclusion rules: abs_id, refund_id, refund_detail_id are internal IDs, customer_word is user-generated text (not structured PII), create_time is a timestamp, and action_user appears to be internal staff usernames.
azazie__number_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a minimal header-only file showing internal IDs and codes. No PII fields present in the header or sample row. Columns are internal identifiers (id, code) and a numeric code (number) — all excluded per rules.
azazie__oauth_client.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, configuration flags, timestamps, or technical metadata. No PII fields (name, email, address, etc.) are present in this dataset. The 'name' column contains system/client names (e.g., 'client', 'localhost'), not personal names.
azazie__oauth_ldap.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal configuration/identifier fields (IDs, flags, timestamps, network settings). Values are system identifiers, configuration constants, and dates that are not personally identifiable.
azazie__oauth_password_policy.csv1 column6 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | password | high | [4] header 'original_password', values are raw passwords |
Notes: Only column 4 (original_password) contains PII (password). All other columns are internal system settings, IDs, timestamps, or flags and do not contain personal identifiable information. The password values appear to be unhashed passwords, which is a severe security risk.
azazie__obcc.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs (abs_id, bar_code), limits (limit_num), types, facility/container IDs — no PII present. This appears to be an inventory or product tracking table from Azazie's database dump.
azazie__obcl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains category data only (product categories). No PII fields present. All columns map to product categories and visibility flags, which are not PII under the provided field types.
azazie__obcs.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/sku identifiers and status flags. No PII fields are present. All columns map to skip due to being internal IDs, counters, or status codes.
azazie__obdm.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the provided rows. The columns appear to be internal tracking fields (abs_id, bar_code, dispatch_sn, create_time, action_user, status, is_process, is_fail) with no personal information. Values are mostly numeric codes, timestamps, and status flags.
azazie__obdm_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected. All columns contain internal IDs, codes, timestamps, and status flags. No email, phone, name, address, or other PII fields present in this sample.
azazie__obgs.csv1 column11,104 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | username | high | [5] values are usernames (e.g. xdma, cmwu, xmwang, hliu, tpyan, fxu, hli) |
Notes: Only column 5 contains PII (username). All other columns contain order IDs, SKUs, timestamps, status flags, and numeric amounts — none qualify as PII under the defined categories. The dataset appears to be transactional records without customer personal data.
azazie__oc_audit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, timestamps, status flags, or non-PII metadata. No PII fields present. Columns like oc_audit_id are internal numeric IDs, business_type describes transaction types, submit_stamp/create_time/last_update_time are timestamps, and all other columns are status codes or technical identifiers. No emails, names, addresses, or other personal data appear in the sample.
azazie__oc_audit_attachment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified in the first 50 rows. The file appears to be an audit log of file attachments (XLSX and images) with internal IDs, file paths, timestamps, and status flags. No personal data such as names, emails, or addresses is visible in the sampled rows.
azazie__oc_push_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, action timestamps, status flags, and JSON payload fragments. 'action_user' contains short alphanumeric strings that are likely internal system usernames, not actual user identifiers. The JSON in 'run_contents' contains only internal party IDs and location codes.
azazie__odcr.csv1 column1,910 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 9 | fullName | high | [9] values match known full names like 'jxie', 'morty', 'xmwang', 'pxing', 'mark', 'jacky', 'jacky.hu', 'leopard', 'anna.peng', 'minzhichen', 'jjwang', 'zhuo.zhang' |
Notes: 50 rows analyzed. Only column 9 contains PII (fullName). All other columns appear to be internal IDs, timestamps, and transaction codes with no personal information.
azazie__off_shelf_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, status flags, timestamps, and notes. Columns like 'apply_user' and 'action_user' contain system/internal usernames, not actual user PII. Timestamps and numeric IDs are non-PII per exclusion rules.
azazie__office_express_fee.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File appears to be a logistics/shipping table tracking region relationships, weights, fees, and timestamps. All columns represent internal business identifiers, numeric weights/fees, and timestamps - no names, addresses, emails, phones, or other personal data present in the sample.
azazie__office_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal shipment/tracking IDs, timestamps, status flags, and numeric codes. No PII fields detected. The columns represent shipment metadata (IDs, dates, weights, status) and do not contain any personal information such as names, emails, addresses, or phone numbers.
azazie__oglc.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file appears to contain only internal SKU identifiers, transaction amounts, update timestamps, and facility/container IDs. No names, addresses, emails, phone numbers, or other personal data is present in the first 50 rows.
azazie__oglc__bakcontainer20170305.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns detected. All fields appear to be internal identifiers (SKU codes, serial numbers), numeric amounts, user roles, timestamps, and facility/container IDs. No names, emails, phone numbers, addresses, dates of birth, or other PII are present in the sample.
azazie__oglc_clone_20170301.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only inventory/SKU data (erp_sku, amount, warehouse codes, timestamps, container IDs). No PII fields are present.
azazie__oglc_reserve_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is an inventory reservation/transaction log (ERP SKU movements, facility/container IDs, order IDs, timestamps, JSON context blobs with internal product/inventory data). No PII fields are present.
azazie__oglc_stat_20170305.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product SKU codes, inventory quantities, and container IDs. No PII fields are present. All columns map to internal inventory tracking and should be skipped.
azazie__oice.csv2 columns13 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | high | header "e_mail" resolves to PII field "email" | |
| 3 | username | high | header "user_name" resolves to PII field "username" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__ok_coupon.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, counters, or status flags. No PII present. coupon_id, party_id, coupon_config_id, coupon_code, coupon_ctime, coupon_cip, coupon_status, coupon_gtime, coupon_creator, can_use_times, used_times, draw_timestamp, give_user_id, give_time, used_timestamp, used_order_id, and used_user_id are all internal system fields, counters, or numeric identifiers with no personal data.
azazie__ok_coupon_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, timestamps, financial values, or configuration flags. No names, emails, addresses, or other personal data present.
azazie__omil.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file is purely transactional data with no PII fields present. Columns contain internal IDs (abs_id, goods_id), timestamps (create_stamp, update_stamp), status flags, and notes — none of which constitute personally identifiable information per the defined field types. No emails, phone numbers, names, addresses, DOB, SSN, or passwords are present.
azazie__one_row.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This appears to be a single-line header-only file or placeholder — the row_id column is the only content present. No actual data rows with PII exist in the sample. Therefore, no PII columns can be mapped.
azazie__online_odm_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present in the first 50 rows. Columns: id (internal ID), note (empty), action_user (system account), create_time (timestamp), last_update_time (timestamp), external_goods_id (product ID), goods_type (category code). All columns are non-PII per exclusion rules.
azazie__ootr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal tracking codes and reasons for order management. No PII fields are present. All columns map to internal flags or identifiers and should be skipped per exclusion rules.
azazie__opcd.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal code identifiers and descriptions for system permissions/roles. No PII fields are present. All columns are internal codes, names, parent relationships, and status flags — none map to personal data fields. Therefore, no columns are mapped to PII categories.
azazie__operation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a log of database operations (updates) and contains no PII fields. All columns represent internal system identifiers, operation types, and timestamps, which must be skipped per exclusion rules.
azazie__operation_manager_commission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, status flags, and department codes. Column 8 contains JSON data with what appears to be customer names, but these are likely business or internal references rather than personal customer PII given the context of this operational report table.
azazie__operation_manager_commission_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, department codes, timestamps, system flags, and configuration data. The 'knock_name' column appears to be a display name for internal use rather than a customer PII field.
azazie__operation_manager_commission_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns represent internal operational data (IDs, timestamps, status flags, and system-generated codes). The column 'action_user' contains a system username (lzliu) but is not a user-facing identifier and should be skipped per rules. No emails, phones, names, addresses, DOB, SSN, passwords, or other PII fields are present.
azazie__operation_point_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal operational workflow data (work order tracking). Columns are abs_id, station_id, station_name (Chinese descriptions of warehouse operations), point (numeric value), create_time (timestamps), create_user (username), and record_state (status flag). No PII fields are present. All columns are internal identifiers, timestamps, or status flags and are excluded per rules.
azazie__ops_log.csv15 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__order_amount_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are financial/transactional data (order amounts, net amounts, credit amounts). No PII fields present. Columns are internal IDs, monetary values, and exchange rates.
azazie__order_attribute.csv3 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | skip | high | column 'attr_name' is non-PII metadata |
| 4 | skip | high | column 'attr_value' contains order metadata only |
| 13 | skip | high | column 'user_name' contains customer usernames only (not emails) |
Notes: CSV with 4 columns; only user_name contains user identifiers, but these appear to be simple usernames rather than email addresses. No PII fields detected in this sample.
azazie__order_batch_operation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (batch IDs, operation types, status codes, user actions, and timestamps). No PII fields are present. All columns map to internal IDs, flags, or timestamps which must be skipped per exclusion rules.
azazie__order_batch_operation_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible fields are order IDs, status codes, timestamps, and error messages. No personal information such as names, emails, addresses, or phone numbers appears in the first 50 rows.
azazie__order_cancel.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order status tracking data with internal order IDs and timestamps. No PII fields (email, phone, name, address, etc.) are present in the visible columns. All columns are internal order identifiers, status flags, and timestamps — these are excluded per rules (skip internal IDs, timestamps, status flags).
azazie__order_check.csv1 column9 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 8 | address1 | high | [8] header 'customer_address', values contain full street addresses (Venustiano Carranza 145, Cruz Verde, ...) |
Notes: 14 columns total, 1 contains PII (address). All other columns are internal IDs, transaction codes, currency, status flags, timestamps, or free-text comments — none contain personal identifiers. The 'customer_address' field holds complete mailing addresses, mapping to address1.
azazie__order_extension.csv57 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__order_fee.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are transactional/order-related data (order IDs, fees, timestamps). No PII fields present. Columns match exclusion rules for financial/transactional data and timestamps.
azazie__order_finance_clear_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, timestamps, and user identifiers. No PII fields are present. Columns: abs_id (internal ID), order_id (order internal ID), order_sn (order serial number), created_stamp (timestamp), action_user (internal username). All columns are excluded per rules for internal IDs and timestamps.
azazie__order_from_livechat.csv3 columns1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | fullName | high | [5] header 'visitor_id', values contain full names like 'Heidi Hottran' |
| 6 | skip | high | [6] header 'visitor_email', empty in sample but column name indicates email address storage |
| 7 | fullName | high | [7] header 'operator_name', values contain full names like 'Jessica' |
Notes: Only columns 5, 6, and 7 contain PII. Column 5 (visitor_id) contains full names, column 6 (visitor_email) is explicitly named for email addresses, and column 7 (operator_name) contains operator names. All other columns are internal IDs, timestamps, or order references and should be skipped.
azazie__order_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible columns are product IDs, SKU codes, pricing data, inventory statuses, and internal tracking numbers. No names, emails, addresses, phone numbers, or other PII fields appear in the sample. This appears to be a product catalog/warehouse inventory dump rather than customer data.
azazie__order_goods_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product metadata - item IDs, SKU information, pricing, size charts, and image URLs. No personal or identifiable information (PII) is present in any column. All columns map to product attributes, inventory data, or internal reference codes.
azazie__order_goods_attribute_back_20190709.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transactional/operational data (order attributes, tax calculations). No PII fields are present. All columns are internal identifiers, numeric values, or timestamps, which are skipped per rules.
azazie__order_goods_attribute_debug.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only transactional/tax attributes (rebate_tax_rate, need_tax_amount) and numeric IDs with no personal information.
azazie__order_goods_change_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided sample. The file appears to contain only internal order/transaction identifiers (abs_id, order_id, rec_id), SKU codes, quantity adjustments, user action logs (action_user), and timestamps. No personal information such as names, emails, addresses, or phone numbers is visible in the first 50 rows.
azazie__order_goods_facility.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal operational data: IDs, category/facility codes, timestamps, usernames of internal staff (action_user), and Y/N flags. This is an inventory/goods transfer table with no customer PII.
azazie__order_goods_facility_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. This is an internal inventory/action log table (abs_id, external_goods_id, category_id, facility_id, action_type, action_user, create_time) — all fields are internal operational identifiers, flags, and timestamps.
azazie__order_goods_fee.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a transactional order details table containing only order identifiers, timestamps, and financial amounts. No PII fields present. All columns are internal IDs, numeric values, or timestamps which are explicitly excluded per rules.
azazie__order_goods_sample_dispatch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file contains only order and shipment identifiers (SN codes, timestamps) with no PII fields. All columns are internal order tracking data, timestamps, and product codes.
azazie__order_goods_ship_income.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields appear to be transactional data (order IDs, monetary amounts, timestamps) and internal identifiers. No names, emails, addresses, or other personal data present in the first 50 rows.
azazie__order_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All visible columns appear to be internal order IDs, reference numbers, and timestamps. The values are alphanumeric order identifiers and ISO-style timestamps, with no personal names, addresses, emails, phone numbers, or other PII patterns present.
azazie__order_header.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, transaction metadata, financial amounts, and flags. This is typical order/shipment data from an e-commerce platform with no customer personal information exposed.
azazie__order_info.csv9 columns3,500 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 9 | gender | high | header "gender" resolves to PII field "gender" |
| 10 | country | high | header "country" resolves to PII field "country" |
| 11 | state | high | header "province" resolves to PII field "state" |
| 13 | city | high | header "city" resolves to PII field "city" |
| 17 | address1 | high | header "address" resolves to PII field "address1" |
| 18 | zip | high | header "zipcode" resolves to PII field "zip" |
| 19 | phone | high | header "tel" resolves to PII field "phone" |
| 20 | skip | high | header "mobile" resolves to PII field "phone" |
| 21 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__order_info_extension.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, transaction metadata, timestamps, tax calculations, or business flags. Columns like 'order_id', 'client_id', and tax rate fields contain no personal data. Timestamps (important_day, web_order_time) are not DOB. No emails, names, addresses, phones, or SSNs present.
azazie__order_info_note.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction IDs and status flags — no PII present. All columns are internal IDs, status codes, timestamps, or notes without personal data. The notes column contains internal tracking codes and Chinese characters for order status, not personal identifiers.
azazie__order_info_sync.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers and timestamps. No PII fields detected in the first 50 rows.
azazie__order_intercept_combination.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, product/attribute metadata, and timestamps. Columns like abs_id, combination_name, attr_first, attr_second, operator, is_delete, sort_no, party_id, action_user, created_time, and last_update_time contain only internal system identifiers, product measurement attributes, and operational timestamps. No personal information such as names, emails, addresses, or phone numbers is present in the first 50 rows.
azazie__order_intercept_list.csv1 column71 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | username | high | [6] header 'action_user', values are alphanumeric strings likely usernames |
Notes: CSV file with order interception records. Only column 6 (action_user) contains PII (username). Columns id, order_id, order_type, action_type, intercept_status, note, create_time, last_update_time contain internal IDs, order metadata, or timestamps and are skipped per rules.
azazie__order_intercept_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/order identifiers, status flags, timestamps, or internal references. No PII fields present. Columns like silhouette (dress style) and action_user (likely internal system user) do not contain personal data.
azazie__order_intercept_rule_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, rule operators, timestamps, or flags. azazie database dump contains structured operational data with no customer PII in this particular file.
azazie__order_inv_reserved.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The provided data is a CSV file containing order/reservation IDs and timestamps, but lacks any PII fields such as names, emails, addresses, or phone numbers. All visible columns are internal identifiers (ORDER_INV_RESERVED_ID, ORDER_ID, FACILITY_ID, etc.) and timestamps (RESERVED_TIME, ORDER_TIME), which are explicitly excluded from PII mapping per the rules. No PII is present in this dataset.
azazie__order_inv_reserved_bak20190829.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The provided file is a structured table containing only order/reservation IDs, version numbers, statuses, timestamps, and internal reference IDs. No personal identifiable information (PII) such as names, emails, addresses, or phone numbers appears in the visible columns or sample rows. All columns represent internal business identifiers, version tracking, status flags, and timestamps—none qualify as PII under the defined field types. Therefore, no PII columns can be mapped.
azazie__order_inv_reserved_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an inventory reservation detail table from Azazie. All columns are internal IDs, status flags, timestamps, and product/facility identifiers. No PII fields are present.
azazie__order_inv_reserverd_inventory_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured inventory table containing only order IDs, inventory item IDs, and quantities. No PII fields are present in the dataset.
azazie__order_inv_reserverd_inventory_mapping_bk.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. File contains only inventory IDs (ORDER_INV_RESERVED_DETAIL_ID, INVENTORY_ITEM_ID) and quantities. All values appear to be internal product codes and numeric quantities with no personal information.
azazie__order_inv_reserverd_shipment_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to contain only internal shipment/order IDs, SKU codes, user handles (non-PII), and timestamps. No emails, phone numbers, names, addresses, DOBs, SSNs, or passwords are present in the sample.
azazie__order_item.csv48 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 32 | fullName | high | [32] contains 'brides name' and 'groom's name' patterns, values match name format |
| 33 | fullName | high | [33] contains 'brides name' and 'groom's name' patterns, values match name format |
| 34 | skip | high | [34] contains 'wedding date', values match date format |
| 40 | fullName | high | [40] contains 'brides name' and 'groom's name' patterns, values match name format |
| 43 | fullName | high | [43] contains structured name fields 'line 1', 'line 2', 'line 3' |
| 44 | fullName | high | [44] contains structured name fields 'line 1', 'line 2', 'line 3' |
| 45 | fullName | high | [45] contains structured name fields 'line 1', 'line 2', 'line 3' |
| 46 | fullName | high | [46] contains structured name fields 'line 1', 'line 2', 'line 3' |
| 47 | fullName | high | [47] contains structured name fields 'line 1', 'line 2', 'line 3' |
| 48 | fullName | high | [48] contains structured name fields 'line 1', 'line 2', 'line 3' |
| 51 | fullName | high | [51] contains personalization field with name-like values |
| 52 | fullName | high | [52] contains personalization field with name-like values |
| 53 | fullName | high | [53] contains 'brides name' and 'groom's name' patterns, values match name format |
| 54 | fullName | high | [54] contains 'brides name' and 'groom's name' patterns, values match name format |
| 56 | fullName | high | [56] contains 'brides name' and 'groom's name' patterns, values match name format |
| 88 | fullName | high | [88] contains structured name fields 'line 1', 'line 2', 'line 3' |
| 89 | fullName | high | [89] contains structured name fields 'line 1', 'line 2', 'line 3' |
| 90 | fullName | high | [90] contains structured name fields 'line 1', 'line 2', 'line 3' |
| 91 | fullName | high | [91] contains structured name fields 'line 1', 'line 2', 'line 3' |
| 123 | fullName | high | [123] contains 'brides name' and 'groom's name' patterns, values match name format |
| 124 | fullName | high | [124] contains personalization field with name-like values |
| 125 | fullName | high | [125] contains personalization field with name-like values |
| 126 | fullName | high | [126] contains personalization field with name-like values |
| 127 | fullName | high | [127] contains personalization field with name-like values |
| 128 | fullName | high | [128] contains personalization field with name-like values |
| 129 | fullName | high | [129] contains personalization field with name-like values |
| 130 | fullName | high | [130] contains personalization field with name-like values |
| 131 | fullName | high | [131] contains personalization field with name-like values |
| 132 | fullName | high | [132] contains personalization field with name-like values |
| 133 | fullName | high | [133] contains personalization field with name-like values |
| 134 | fullName | high | [134] contains personalization field with name-like values |
| 135 | fullName | high | [135] contains personalization field with name-like values |
| 136 | fullName | high | [136] contains personalization field with name-like values |
| 137 | fullName | high | [137] contains personalization field with name-like values |
| 138 | fullName | high | [138] contains personalization field with name-like values |
| 139 | fullName | high | [139] contains personalization field with name-like values |
| 140 | fullName | high | [140] column header 'test_name', values appear to be names |
| 141 | fullName | high | [141] column header 'test_name', values appear to be names |
| 142 | fullName | high | [142] column header 'test_name', values appear to be names |
| 143 | fullName | high | [143] column header 'test_name', values appear to be names |
| 144 | fullName | high | [144] column header 'test_name', values appear to be names |
| 145 | fullName | high | [145] column header 'test_name', values appear to be names |
| 146 | fullName | high | [146] column header 'test_name', values appear to be names |
| 147 | fullName | high | [147] column header 'test_name', values appear to be names |
| 148 | fullName | high | [148] column header 'test_name', values appear to be names |
| 190 | fullName | high | [190] contains 'brides name' and 'groom's name' patterns, values match name format |
| 191 | fullName | high | [191] contains 'brides name' and 'groom's name' patterns, values match name format |
| 192 | fullName | high | [192] contains 'brides name' and 'groom's name' patterns, values match name format |
azazie__order_livechatinc.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present. Columns: id (internal ID), order_id (internal order ID), order_sn (order serial number), visitor_id (session/visit tracking ID), goal_id (internal goal ID), send_time (timestamp). All columns are non-PII per exclusion rules.
azazie__order_location.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns represent order IDs, city names, region names, country codes, IP addresses, deletion flags, and timestamps. IP addresses are explicitly excluded from PII mapping per rules.
azazie__order_mixed_status_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal tracking fields and status flags (order IDs, timestamps, system statuses). No PII is present in this sample.
azazie__order_mixed_status_note.csv2 columns148,707 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | username | high | [6] header 'created_by_user_login', values are alphanumeric strings resembling usernames |
| 7 | password | high | [7] column name 'created_stamp' is misleading; values are not timestamps but appear to be encrypted passwords or hashes |
Notes: Only columns 6 and 7 contain PII. Column 7 is labeled 'created_stamp' but the values resemble password hashes, which are considered PII. All other columns contain internal IDs, notes, or timestamps and are skipped per rules.
azazie__order_operation_detail.csv47 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 21 | address1 | high | [21] header 'address', free-text values represent locations |
| 24 | skip | high | [24] header 'email', values contain '@' (bwzhang@tetx.com -> zhangbw@i9i8.com) |
| 27 | skip | high | [27] header 'mobile', numeric values (147852369) |
| 40 | address1 | high | [40] header 'address', values are location strings (11111111111) |
| 45 | skip | high | [45] header 'tel', values match international format (+47 97717559) |
| 53 | address1 | high | [53] header 'address', values are location strings (Svarttrostv. 1C) |
| 65 | address1 | high | [65] header 'address', values are location strings (Norway Langesund Svarttrostv. 1C) |
| 76 | address1 | high | [76] header 'address', values are location strings (asdvvvvv) |
| 78 | address1 | high | [78] header 'address', values are location strings (test_address1,test_address2) |
| 79 | address1 | high | [79] header 'address', values are location strings (test_address111,test_address2) |
| 80 | address1 | high | [80] header 'address', values are location strings (4123123,132456) |
| 81 | address1 | high | [81] header 'address', values are location strings (aaa,bbb) |
| 91 | skip | high | [91] header 'email', values contain '@' (xmwang@tetx.com -> xmwang@tet.com) |
| 95 | address1 | high | [95] header 'address', values are location strings (平安街68号) |
| 97 | address1 | high | [97] header 'address', values are location strings (平安街68号) |
| 104 | address1 | high | [104] header 'address', values are location strings (Adult's) |
| 109 | address1 | high | [109] header 'address', values are location strings (Chatain/Route de Chatain, 86250 Charroux) |
| 114 | address1 | high | [114] header 'address', values are location strings (Chatain/Route de Chatain, 86250 Charroux) |
| 119 | address1 | high | [119] header 'address', values are location strings (,Chatain/Route de Chatain, 86250 Charroux) |
| 122 | address1 | high | [122] header 'address', values are location strings (Chatain/Route de Chatain, 86250 Charroux) |
| 123 | address1 | high | [123] header 'address', values are location strings (Route de Chatain, 86250 Charroux) |
| 124 | address1 | high | [124] header 'address', values are location strings (123 Route de Chatain, 86250 Charroux) |
| 125 | address1 | high | [125] header 'address', values are location strings (86250 Charroux , 123 Route de Chatain) |
| 126 | address1 | high | [126] header 'address', values are location strings (86250 Charroux , Route de Chatain) |
| 127 | address1 | high | [127] header 'address', values are location strings (86250 Charroux ,123 Route de Chatain) |
| 130 | address1 | high | [130] header 'address', values are location strings (123 Route de Chatain , 86250 Charroux) |
| 132 | address1 | high | [132] header 'address', values are location strings (Chatain/Route de Chatain , 86250 Charroux) |
| 133 | address1 | high | [133] header 'address', values are location strings (,) |
| 139 | address1 | high | [139] header 'address', values are location strings (4123123) |
| 143 | address1 | high | [143] header 'address', values are location strings (,Norway Langesund Svarttrostv. 1C) |
| 146 | skip | high | [146] header 'tel', values match international format (+47 97717559) |
| 147 | skip | high | [147] header 'tel', values match international format (4797717559) |
| 148 | skip | high | [148] header 'tel', values are numeric (2432) |
| 149 | skip | high | [149] header 'tel', values are numeric (2432+222) |
| 150 | skip | high | [150] header 'email', values contain '@' (happy@tetx.com -> happy@tetx1.com) |
| 156 | skip | high | [156] header 'email', values contain '@' (hywang@tetx.com -> hywang@tet1x.com) |
| 158 | address1 | high | [158] header 'address', values are location strings (lalalal,Norway Langesund Svarttrostv. 1C) |
| 161 | address1 | high | [161] header 'address', values are location strings (,sfsd) |
| 162 | address1 | high | [162] header 'address', values are location strings (Norway Langesund Svarttrostv. 1C,Norway Langesund Svarttrostv’. 1C) |
| 163 | address1 | high | [163] header 'address', values are location strings (Norway Langesund Svarttrostv’. 1C,Norway Langesund Svarttrostv’'. 1C) |
| 164 | address1 | high | [164] header 'address', values are location strings (555 Lexington Avenue, 10th Floor, R,555 Lexington Avenue', 10th Floor, R) |
| 165 | skip | high | [165] header 'email', values contain '@' (hywang@tetx.com -> hywang@t1etx.com) |
| 175 | address1 | high | [175] header 'address', values are location strings (kfljskl,skjfsdl,中文) |
| 176 | address1 | high | [176] header 'address', values are location strings (中文,中文中文中文) |
| 177 | skip | high | [177] header 'email', values contain '@' (123367498@tetx.com -> 123367498@11tetx.com) |
| 193 | address1 | high | [193] header 'address', values are location strings (Dizhi111,Dizhi222) |
| 196 | address1 | high | [196] header 'address', values are location strings (xhfan,xhfan) |
Notes: Columns 0-3,4-6,7-8,10,11-12,13-14,15-16,17-18,19-20,22-23,25-26,28-29,30-32,34-35,36-38,39-40,41,42-44,46-47,48-50,51-52,54-55,56-57,58-60,61-63,64-65,66-67,68-69,70-72,74-75,77,79-80,82-84,85-87,88-90,92-93,94,95-97,98-98,99-100,101-101,102-103,104-106,107-107,108-108,109-111,112-112,113-113,114-114,115-115,116-116,117-117,118-118,119-119,120-120,121-121,122-127,128-129,130-130,131-131,132-132,133-133,134-134,135-135,136-136,137-137,138-138,139-139,140-140,141-141,142-142,143-143,144-144,145-145,147-147,148-148,149-149,151-151,152-152,153-153,154-155,156-156,157-157,158-160,161-161,162-163,164-164,165-165,166-168,169-171,172-172,173-174,175-176,177-177,178-178,179-179,180-180,181-181,182-182,183-184,185-185,186-187,188-189,190-190,191-191,192-192,193-193,194-194,195-195,196-198,199-199 are non-PII and skipped. All PII columns identified.
azazie__order_operation_efficiency_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is an internal order action audit log (ecs_order_action table). All columns are operational/transactional: id (internal ID), taobao_order_sn (order number), action_user (internal system username), action_type (event type code), action_time/create_time/last_update_time (timestamps), action_id (internal ID), action_source (system table name). No customer PII is present.
azazie__order_operation_efficiency_statistics.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be an audit log table tracking order actions with user identifiers that are likely internal system usernames rather than personal identifiers. All columns represent action metadata, timestamps, and numeric counters.
azazie__order_party.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only internal order identifiers (abs_id, order_party_id, order_id), timestamps (merge_time), and status flags (party_status). No personal data such as names, emails, addresses, or phone numbers present in the first 50 rows.
azazie__order_payment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected - all columns contain only internal payment IDs (P-XXXX-XXXX patterns) and numeric order IDs. These are internal reference codes, not personal identifiers.
azazie__order_payment_20200307.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal payment identifiers (order_payment_id, order_id, payment_id) with no PII present. All values are alphanumeric codes representing transaction references, not personal data.
azazie__order_phone_note.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains operational notes about order follow-ups and phone call statuses. The only potentially personal column is 'phone_note', but it contains only status messages in Chinese ('留言: 留言' meaning 'comment: comment' and '打通: 打通电话了' meaning 'call connected: call connected'), not actual phone numbers or PII. No columns map to any PII fields.
azazie__order_priority_operation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data: abs_id (internal ID), order_id (internal order ID), priority_type (flags), operate_time (timestamps), and operate_user (username of internal staff). No PII fields are present. All columns are flagged as skip per exclusion rules (internal IDs, timestamps, internal flags).
azazie__order_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be an order relation table with internal order IDs, order numbers, and parent-child relationships. All columns contain numeric identifiers and transaction codes with no personal information such as names, emails, addresses, or phone numbers.
azazie__order_relationship.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only order IDs, timestamps, and Afterpay payment gateway tokens (not considered PII). The JSON payloads contain internal tokens and order references but no personal information such as names, emails, addresses, or payment card numbers.
azazie__order_relevant_file.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational IDs and timestamps. No PII fields are present. Columns represent risk flags, order IDs, and timestamps which are all marked as skip per exclusion rules.
azazie__order_reserve_control.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only order IDs, timestamps, update users, and status flags. No PII present. Columns map to internal IDs, timestamps, and boolean flags, all excluded by policy.
azazie__order_risk_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains transaction risk assessment data with order IDs, risk scores, and system-generated alerts about suspicious activity patterns, but no personal identifiers such as names, emails, addresses, or account credentials are present in the visible data.
azazie__order_rma_fix.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present. Columns: id (numeric internal ID), taobao_order_sn (transaction reference), is_printed (status flag), create_time (timestamp), last_update_time (timestamp). All columns are non-PII per exclusion rules.
azazie__order_sample_not_return_queue.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order-related data with internal IDs and timestamps. No PII fields are present. Columns map to order IDs, statuses, and timestamps which are explicitly excluded per rules.
azazie__order_sample_sold_dispatch.csv1 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__order_service_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only order/inventory management records with JSON-style embedded objects. No PII fields detected in the visible columns. Columns represent internal order IDs, product IDs, reservation statuses, timestamps, and quantities — all operational metadata with no personal identifying information.
azazie__order_settle.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains only internal transaction IDs (abs_id, order_id), statuses, messages, user references (action_user), and timestamps. All columns fall under internal IDs, flags, or timestamps per exclusion rules.
azazie__order_ship_record_detail_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/tracking data: order counts, shipping status, and timestamps. No PII fields (names, emails, addresses, etc.) are present. All columns represent internal business metrics and should be skipped per exclusion rules (timestamps, counters, totals).
azazie__order_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file containing only two columns: SHIPMENT_ID and ORDER_ID. Both columns represent internal transaction identifiers and do not contain any personally identifiable information (PII). Per the exclusion rules, internal IDs such as shipment and order numbers must be skipped. Therefore, no columns are mapped to PII fields.
azazie__order_shipment_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a database dump containing order/shipment records with no PII fields. All columns represent internal IDs, product SKUs, quantities, and timestamps. No email, phone, name, address, or other PII fields are present in the first 50 rows.
azazie__order_shipment_goods_snap.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, transaction codes, or inventory identifiers. No PII fields present. Columns like 'action_user' contain system usernames, not customer PII. This appears to be an operational log table tracking order/shipment modifications.
azazie__order_shipment_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal shipment/order identifiers, timestamps, or transaction metadata. No PII fields (names, emails, addresses, etc.) are present in this structured shipment data file.
azazie__order_showroom_party.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in this dataset. The file contains only internal order identifiers (abs_id, order_id), party references, timestamps, and status flags. No personal information such as names, emails, addresses, or phone numbers is present in the first 50 rows.
azazie__order_split_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal shipment/fulfillment identifiers (shipment_id, order_goods_id, package_goods_number). No PII present. This is a pure transactional log of package quantities per order line item.
azazie__order_static.csv9 columns1,040 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | high | header "email" resolves to PII field "email" | |
| 7 | gender | high | header "sex" resolves to PII field "gender" |
| 8 | country | high | header "country" resolves to PII field "country" |
| 9 | state | high | header "province" resolves to PII field "state" |
| 10 | city | high | header "city" resolves to PII field "city" |
| 12 | address1 | high | header "address" resolves to PII field "address1" |
| 13 | zip | high | header "zipcode" resolves to PII field "zip" |
| 14 | phone | high | header "tel" resolves to PII field "phone" |
| 15 | skip | high | header "mobile" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__order_sync_water_mark.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, status flags, or JSON blobs — no PII present. order_id, order_sn, party_id, and JSON payloads contain only internal reference numbers and structured order data. Timestamps (create_time, update_time, commit_time, syn_time) are operational metadata, not personal dates of birth.
azazie__order_transaction.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, timestamps, or flags. No PII present. Columns like transaction_id, order_id, action_user are internal IDs or system flags, not usernames or personal identifiers. action_time, creation_date, last_update_date are timestamps, is_sync and system are internal flags.
azazie__order_transaction_detail.csv9 columns2 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | high | [3] JSON field 'consignee' contains full name 'wang haha' |
| 4 | gender | high | [4] JSON field 'sex' maps to gender |
| 5 | country | high | [5] JSON field 'country' maps to country |
| 6 | state | high | [6] JSON field 'province' maps to state |
| 7 | city | high | [7] JSON field 'city' maps to city |
| 8 | address1 | high | [8] JSON field 'address' maps to address1 |
| 9 | zip | high | [9] JSON field 'zipcode' maps to zip |
| 10 | phone | high | [10] JSON field 'tel' contains 10-digit phone number |
| 11 | high | [11] JSON field 'email' contains valid email address |
Notes: Only columns containing PII from the JSON payload are mapped. All other fields are internal IDs, timestamps, transaction codes, or financial data and are skipped per rules.
azazie__order_transfer.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (transfer_number, order_id) and timestamps (create_datetime). No PII fields are present. All columns are marked as skip per exclusion rules: transfer_number and order_id are internal IDs, create_datetime is a timestamp.
azazie__order_unpaid_email.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields present in this structured CSV. Columns are order_id (internal ID), order_sn (order reference number), and send_email_time (timestamp). All values are order identifiers and timestamps, which are excluded by policy. No emails, names, addresses, or other PII appear in the sample.
azazie__order_white_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a two-column CSV file with order_id and is_used flags. Neither column contains PII. order_id is an internal numeric identifier, and is_used is a binary flag. No personal or sensitive data is present in these rows.
azazie__org_qprofiles.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file but contains only internal UUID identifiers and timestamps. No PII fields are present. All columns are internal IDs or timestamps and therefore must be skipped per exclusion rules.
azazie__org_quality_gates.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns appear to be internal IDs or UUIDs (uuid, organization_uuid, quality_gate_uuid). There are no PII fields present in the first 50 rows. These columns are non-PII per the exclusion rules for internal IDs.
azazie__organization_members.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers (organization_uuid, user_id) with no PII fields. These are non-searchable internal IDs and should be skipped per exclusion rules.
azazie__organizations.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains organizational metadata and system configuration data for SonarQube, not customer PII. All columns are internal identifiers, timestamps, or system flags. No PII fields present.
azazie__ost_api_key.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal system identifiers and timestamps, no PII fields present. Columns include internal IDs, status flags, IP addresses, API keys, and timestamps — all marked as skip per exclusion rules. No emails, names, addresses, or other PII detected in the sample rows.
azazie__ost_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/category metadata (IDs, names, types, display orders, statuses). No PII fields are present. All columns are internal identifiers, labels, or status flags.
azazie__ost_config.csv1 column1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 75 | high | [75] header 'admin_email', value contains '@' symbol and domain |
Notes: Only column 75 contains PII (admin email). All other columns are internal system settings, flags, timeouts, paths, and version information — none contain personal data. This appears to be an OSTicket configuration table, not customer data.
azazie__ost_department.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal department/structure identifiers, timestamps, flags, and operational metadata. No PII fields are present. dept_name and dept_signature contain department names and template messages, not personal data.
azazie__ost_email_template.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only template message content for support tickets — no PII present. All columns are message templates, subject lines, and body content with placeholder variables (e.g., %name, %ticket, %staff). No actual personal data or identifiers are stored in these rows.
azazie__ost_groups.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal access control data for support tickets — no PII present. All columns are internal flags, IDs, and timestamp columns that do not contain personal information per the exclusion rules.
azazie__ost_help_topic.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal system identifiers, flags, timestamps, or non-personal content. This appears to be a support ticket/category table from Azazie's CMS, not customer data.
azazie__ost_kb_premade.csv8 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | internal id |
| 1 | skip | high | internal department code |
| 2 | skip | high | internal flag |
| 3 | skip | high | internal title/salutation — values are honorific prefixes (Mr, Mrs, Ms, Dr) not generational suffixes |
| 4 | skip | high | free-text customer service response |
| 5 | skip | high | timestamp |
| 6 | skip | high | timestamp |
| 7 | skip | high | hash — not searchable PII |
Notes: 50 rows shown; all rows are customer service tickets with structured IDs and free-text responses. No PII fields present beyond internal IDs and timestamps. All columns map to skip per rules.
azazie__ost_question_email_template.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file contains only template emails for customer support responses. There are no actual customer records or PII values present in the data rows — only placeholders like {image_link}, {random_color}, {selected_color}, and %domain_name. No columns map to PII fields.
azazie__ost_question_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only question templates in multiple languages (English, German, French, Swedish) with metadata about question types and display order. No PII fields present. All columns are internal identifiers, language codes, topic IDs, and question text — none contain personal data.
azazie__ost_staff.csv7 columns11 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | username | high | header "username" resolves to PII field "username" |
| 4 | firstName | high | header "firstname" resolves to PII field "firstName" |
| 5 | lastName | high | header "lastname" resolves to PII field "lastName" |
| 6 | password | high | header "passwd" resolves to PII field "password" |
| 7 | high | header "email" resolves to PII field "email" | |
| 8 | skip | high | header "phone" resolves to PII field "phone" |
| 10 | skip | high | header "mobile" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__ost_ticket_priority.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a priority configuration table with no PII. All columns represent internal priority settings (priority levels, descriptions, colors, urgency, and public visibility flags). No personal identifiable information is present.
azazie__oucp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, timestamps, and flags. No PII fields are present. Columns: abs_id (internal ID), bar_code (product code), creater (user ID), created_stamp (timestamp), finish_stamp (timestamp), shipment_ids (transaction ID), is_process (status flag). All columns are excluded per rules for internal IDs, timestamps, and non-PII data.
azazie__out_inv_no_arrival_last_mile.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal IDs, transaction references, timestamps, or shipping/logistics data. 'country' is a location but not personally identifying on its own in this context (only country names). No emails, names, addresses, phone numbers, DOB, SSN, passwords, usernames, or other PII fields present.
azazie__over_dispatch_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided rows. All columns appear to contain internal IDs, timestamps, and other non-PII data. The columns 'detail_id' and 'dispatch_list_id' are internal identifiers and timestamps, which are excluded per rules.
azazie__over_period_dispatch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, counters, timestamps, or flags — no PII present. Columns like over_period_info_id, provider_id, create_stamp, and all_todo_dispatch contain numeric codes, timestamps, and operational flags that do not qualify as PII under the defined rules.
azazie__overseas_shipping_method_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal operational/logistics data: abs_id (internal ID), facility_id (internal ID), shipment_method (shipping descriptor), delivery_service_id (service code), shipping_id (internal ID). This is a shipping method lookup/mapping table with no personal data.
azazie__package_provider_price_region.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, flags, timestamps, or business data. Columns like 'action_user' appear to be internal usernames (yzhang14) but lack sufficient context to confidently map as PII. No emails, phones, names, addresses, DOB, SSN, or passwords are present.
azazie__package_status.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only status codes and descriptions with no personal identifiable information (PII). All columns represent internal status tracking and are not mapped to any PII fields.
azazie__package_status_tracking_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (shipping IDs, flags, timestamps, counters). No PII fields are present. All columns are internal IDs, status flags, or timestamps which must be skipped per exclusion rules.
azazie__package_workload_statistics.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file appears to be a log of shipment or order records with columns like abs_id, timestamps, user actions, package user, quantity, shipment_id, waybill number, and status. None of these columns contain identifiable personal information (PII) such as names, emails, phone numbers, addresses, dates of birth, SSNs, passwords, usernames, or other sensitive data. The 'action_user' and 'package_user' fields contain internal usernames (e.g., xmwang, pangou), which are not considered public usernames or PII under the provided definitions. The waybill numbers appear to be tracking IDs rather than PII. Therefore, no columns map to PII fields.
azazie__parking_space_order_amount.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a system log or operational data table from Azazie, containing only internal identifiers and timestamps. No PII fields are present. All columns map to internal IDs, flags, or timestamps and must be skipped per exclusion rules.
azazie__parking_space_order_amount_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal action logs (action_id, user, timestamps, action names). No PII fields present. All columns are internal IDs, flags, timestamps, or numeric values — none map to PII categories. Per exclusion rules, all columns are skipped.
azazie__party.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal organizational identifiers and timestamps. No PII fields detected in the first 50 rows. The data represents party IDs, names of business entities, statuses, parent relationships, and flags — none contain personal customer information such as names, emails, addresses, or other PII.
azazie__party_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal system identifiers, flags, URLs, and configuration values. This appears to be a system configuration or routing table rather than customer data.
azazie__party_default_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and timestamps. No PII fields are present. All columns are internal IDs, creation/update timestamps, category and provider codes — these are non-PII according to the exclusion rules.
azazie__party_facility.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in this sample. All columns represent internal company/party identifiers, facility names, and operational flags. Values contain business entity names (总公司, 欧酷, Azazie, etc.) and warehouse locations, but no personal identifiers like names, emails, or addresses. All columns fall under exclusion rules for company/business data.
azazie__party_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only internal relationship IDs, timestamps, and status flags. All columns are non-personal identifiers or operational metadata.
azazie__pattern_apply.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, timestamps, counters, or status flags. 'action_user' appears to be a system username, not a customer username, and is excluded per rules.
azazie__pattern_apply_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product codes, timestamps, or operational flags. Columns like 'pick_up_user' contain system usernames, not personal identifiers. No emails, phone numbers, names, addresses, DOB, SSN, or passwords present.
azazie__pattern_contain_location.csv1 column242 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | username | high | [4] header 'action_user', values are alphanumeric strings likely usernames |
Notes: Identified username column. All other columns appear to be internal order identifiers, SKUs, timestamps, and quantities — no PII detected beyond the username field.
azazie__pattern_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/order identifiers and timestamps. No PII fields are present. Columns are: id (internal record ID), pattern_sku (product pattern code), cp_goods_id (internal goods ID), size (numeric size code), name (product name in Chinese), type (product type code), action_user (internal username), create_time (timestamp), last_uodate_time (timestamp). All columns are non-PII per exclusion rules.
azazie__pattern_info_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only internal IDs (dd_id), product names (goods_name), sizes, and timestamps. All columns are non-PII per exclusion rules (internal IDs, product data, timestamps).
azazie__pattern_inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All visible columns (id, pattern_sku, quantity fields, action_user, timestamps, version_id, container_id) are internal identifiers, product codes, inventory counts, or system metadata. The 'action_user' field contains generic usernames like 'zhaoyong' and 'test101' which appear to be system accounts rather than customer PII. No emails, phone numbers, names, addresses, or other personal data detected in the sample.
azazie__pattern_inventory_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided data. The file appears to be an inventory/operations log containing only internal IDs, timestamps, and numerical quantities. All columns map to skip categories per the exclusion rules (internal IDs, timestamps, counters).
azazie__pattern_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal operational data (IDs, timestamps, type codes) with no PII present. All columns represent system metadata: id, type, order_sn (internal order reference), container_id (internal container reference), action_user (username placeholder), create_time and last_uodate_time (timestamps). No personal information is exposed in any column.
azazie__pattern_order_goods.csv1 column329 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | username | high | [4] header 'action_user', values are alphanumeric usernames |
Notes: CSV file with order/transactional data. Only column 4 (action_user) contains PII (username). Other columns are internal order IDs, SKUs, timestamps, and quantities.
azazie__pattern_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product return reason codes and types — no PII present. All columns represent internal categorization (type_id, type_code, type_name, type_name_en) and should be skipped per exclusion rules.
azazie__pay_log.csv238 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__payment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only payment method configuration data (payment IDs, payment codes, payment names, fees, etc.). No PII fields such as names, emails, addresses, or dates of birth are present. All columns are internal identifiers, payment method names, configuration flags, or timestamps — all excluded by the rules.
azazie__payment_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. File contains only payment configuration data (project names, language/country codes, payment methods, gift card IDs, timestamps). All columns are internal business metadata or transactional identifiers, none contain personal information.
azazie__payment_config_budget.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal IDs and timestamps - no PII present. Columns map to user_group_id, pcg_id, ctime, enabled, and last_update_time, all of which are internal system identifiers and timestamps per exclusion rules.
azazie__payment_config_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a configuration/settings table with no PII. All columns are internal identifiers, flags, or timestamps. No email, name, address, or other personal data is present.
azazie__payment_currency_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only payment and currency IDs with timestamps - no PII fields present. All columns are internal identifiers or timestamps which must be skipped per exclusion rules.
azazie__payment_language.csv83 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 68 | fullName | high | [68] header 'payment_name', values are full names |
| 71 | fullName | high | [71] contains 'Rengui Zhou' in payment_name |
| 72 | fullName | high | [72] contains 'Rengui Zhou' in payment_name |
| 73 | fullName | high | [73] contains 'Rengui Zhou' in payment_name |
| 74 | fullName | high | [74] contains 'Rengui Zhou' in payment_name |
| 75 | fullName | high | [75] contains 'Rengui Zhou' in payment_name |
| 76 | fullName | high | [76] contains 'Rengui Zhou' in payment_name |
| 77 | fullName | high | [77] contains 'Rengui Zhou' in payment_name |
| 78 | fullName | high | [78] contains 'Rengui Zhou' in payment_name |
| 79 | fullName | high | [79] contains 'Rengui Zhou' in payment_name |
| 83 | fullName | high | [83] contains 'ZC HOLDING HK LIMITED' in payment_name |
| 84 | fullName | high | [84] contains 'ZC HOLDING HK LIMITED' in payment_name |
| 85 | fullName | high | [85] contains 'ZC HOLDING HK LIMITED' in payment_name |
| 86 | fullName | high | [86] contains 'ZC HOLDING HK LIMITED' in payment_name |
| 87 | fullName | high | [87] contains 'ZC HOLDING HK LIMITED' in payment_name |
| 88 | fullName | high | [88] contains 'ZC HOLDING HK LIMITED' in payment_name |
| 89 | fullName | high | [89] contains 'ZC HOLDING HK LIMITED' in payment_name |
| 90 | fullName | high | [90] contains 'ZC HOLDING HK LIMITED' in payment_name |
| 91 | fullName | high | [91] contains 'ZC HOLDING HK LIMITED' in payment_name |
| 92 | fullName | high | [92] contains 'ZC HOLDING HK LIMITED' in payment_name |
| 93 | fullName | high | [93] contains 'ZC HOLDING HK LIMITED' in payment_name |
| 94 | fullName | high | [94] contains 'ZC HOLDING HK LIMITED' in payment_name |
| 95 | fullName | high | [95] contains 'Globebill' in payment_name |
| 96 | fullName | high | [96] contains 'Globebill' in payment_name |
| 97 | fullName | high | [97] contains 'Globebill' in payment_name |
| 98 | fullName | high | [98] contains 'Globebill' in payment_name |
| 99 | fullName | high | [99] contains 'Globebill' in payment_name |
| 100 | fullName | high | [100] contains 'Globebill' in payment_name |
| 101 | fullName | high | [101] contains 'Globebill' in payment_name |
| 102 | fullName | high | [102] contains 'Globebill' in payment_name |
| 103 | fullName | high | [103] contains 'Globebill' in payment_name |
| 104 | fullName | high | [104] contains 'Globebill' in payment_name |
| 105 | fullName | high | [105] contains 'Globebill' in payment_name |
| 106 | fullName | high | [106] contains 'Globebill' in payment_name |
| 110 | fullName | high | [110] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 111 | fullName | high | [111] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 112 | fullName | high | [112] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 113 | fullName | high | [113] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 114 | fullName | high | [114] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 115 | fullName | high | [115] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 116 | fullName | high | [116] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 117 | fullName | high | [117] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 118 | fullName | high | [118] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 119 | fullName | high | [119] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 120 | fullName | high | [120] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 121 | fullName | high | [121] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 122 | fullName | high | [122] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 135 | fullName | high | [135] contains 'ReadMob Technologies (HK) Limited' in payment_name |
| 136 | fullName | high | [136] contains 'ReadMob Technologies (HK) Limited' in payment_name |
| 137 | fullName | high | [137] contains 'ReadMob Technologies (HK) Limited' in payment_name |
| 138 | fullName | high | [138] contains 'ReadMob Technologies (HK) Limited' in payment_name |
| 139 | fullName | high | [139] contains 'ReadMob Technologies (HK) Limited' in payment_name |
| 140 | fullName | high | [140] contains 'ReadMob Technologies (HK) Limited' in payment_name |
| 141 | fullName | high | [141] contains 'ReadMob Technologies (HK) Limited' in payment_name |
| 142 | fullName | high | [142] contains 'ReadMob Technologies (HK) Limited' in payment_name |
| 143 | fullName | high | [143] contains 'ReadMob Technologies (HK) Limited' in payment_name |
| 144 | fullName | high | [144] contains 'ReadMob Technologies (HK) Limited' in payment_name |
| 145 | fullName | high | [145] contains 'ReadMob Technologies (HK) Limited' in payment_name |
| 146 | fullName | high | [146] contains 'ReadMob Technologies (HK) Limited' in payment_name |
| 183 | fullName | high | [183] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 184 | fullName | high | [184] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 185 | fullName | high | [185] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 186 | fullName | high | [186] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 187 | fullName | high | [187] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 188 | fullName | high | [188] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 189 | fullName | high | [189] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 190 | fullName | high | [190] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 191 | fullName | high | [191] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 192 | fullName | high | [192] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 193 | fullName | high | [193] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 194 | fullName | high | [194] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 195 | fullName | high | [195] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 196 | fullName | high | [196] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 197 | fullName | high | [197] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 198 | fullName | high | [198] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 199 | fullName | high | [199] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 200 | fullName | high | [200] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 201 | fullName | high | [201] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 202 | fullName | high | [202] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 203 | fullName | high | [203] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 204 | fullName | high | [204] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 205 | fullName | high | [205] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
| 206 | fullName | high | [206] contains 'FLATWORLD COMMERCE LIMITED' in payment_name |
Notes: Columns contain full names in payment_name, likely representing beneficiary or company names for various payment methods
azazie__payment_platform_collection_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal transaction IDs, statuses, timestamps, and amounts. No PII fields present. Columns like id, party_id, platform_order_sn, taobao_order_sn, and timestamps are internal identifiers or operational metadata. No emails, names, addresses, phone numbers, DOB, SSN, passwords, usernames, or other PII categories are detected.
azazie__payment_platform_collection_data_authorize.csv2 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 7 | firstName | high | [7] header 'first_name', values are common given names |
| 8 | lastName | high | [8] header 'last_name', values are common surnames |
Notes: Only first_name and last_name contain PII; all other columns are internal IDs, timestamps, transaction metadata, or financial data
azazie__payment_platform_collection_data_authorize_batch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal transaction IDs, timestamps, and status flags. No PII fields are present in this structured dataset. The columns contain payment processing metadata rather than customer personal information.
azazie__payment_platform_collection_data_braintree.csv1 column350 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 20 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__payment_platform_collection_data_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and timestamps. No PII fields are present. Columns include IDs, platform identifiers, time differences, and timestamps, all of which are marked as skip per rules.
azazie__payment_source.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only payment source identifiers and names. No personal identifiable information (PII) fields are present. All columns represent payment methods, banks, and transaction types which are excluded per the rules (Company/Business names and financial/transactional data).
azazie__payment_task.csv1 column161 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header 'user_name', values are alphanumeric strings with underscores and dots, typical for usernames |
Notes: Only column 2 (user_name) contains PII. All other columns are internal IDs (abs_id, task_id), timestamps (create_time, update_time), status flags (status, is_fail), and numeric counters — none contain PII.
azazie__payment_task_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction identifiers, amounts, timestamps, status flags, and error messages. No PII fields are present. All columns are internal IDs, amounts, timestamps, status flags, or error messages in Chinese, which are not PII according to the rules.
azazie__payment_transaction.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal transaction identifiers, timestamps, status flags, monetary values, and system accounts. No emails, names, addresses, phone numbers, or other personal data appear in the sample.
azazie__payment_transaction_status_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The provided data appears to be a series of transaction records with columns indicating payment transaction status history ID, creation and update timestamps, status, sequence number, and payment transaction ID. None of these columns contain personally identifiable information (PII) such as names, addresses, emails, phone numbers, dates of birth, or social security numbers. The data is purely transactional and does not map to any PII fields defined in the instructions. Therefore, no columns can be mapped to PII fields.
azazie__payment_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only payment type identifiers and names (e.g., 'CUSTOMER_PAYMENT'). These are internal payment classification codes with no personal identifiable information (PII). All columns are internal payment types and should be skipped per rules.
azazie__payment_verification.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be a transaction log with order IDs, verification tokens, payment tokens, amounts, and Braintree payment method results. All columns are internal transaction identifiers, payment statuses, or timestamps with no personal information.
azazie__paypal_txn.csv15 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__pb_dispatch_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns contain internal IDs, status codes, shipping identifiers, carrier names, and tracking numbers. No personal information (names, emails, addresses, etc.) is present in this sample.
azazie__pb_receipt_batch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (batch records) with no PII. Columns are: receipt_batch_id (internal ID), supplier_id (internal ID), batch_type (transaction type), batch_time (timestamp), operator (username). All columns are skipped per exclusion rules (internal IDs and timestamps).
azazie__pb_receipt_sn.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but none of the columns contain PII. All columns appear to be internal operational identifiers, timestamps, and status flags related to receipt and order processing. The 'operator' column contains what looks like a username ('yzhang'), but per exclusion rules, any column with patterns like 'operator' or internal role identifiers is treated as skip unless explicitly confirmed to be a user-facing username. Here, 'yzhang' appears to be an internal operator code rather than a public-facing username, and there are no other columns with email-like patterns, phone numbers, or address components. Thus, no PII columns are mapped.
azazie__pb_supplier_dispatch_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a log table containing action IDs, timestamps, and user notes. No PII fields are present. All columns are internal tracking data (action_id, abs_id, action_time, action_user, action_note). action_user appears to be internal system usernames, not actual customer identifiers. No emails, phones, names, addresses, or other PII detected.
azazie__pb_supplier_dispatch_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns are internal IDs, timestamps, transaction codes, product codes, quantities, and non-personal metadata. Columns like 'created_by_user_login' contain short alphanumeric usernames without additional personal context, and are excluded per exclusion rules for internal identifiers.
azazie__pb_supplier_dispatch_list_status_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields are internal IDs, status flags, timestamps, and user logins that do not correspond to personal identifiers. The 'created_by_user_login' field contains system usernames, not customer PII.
azazie__perm_templates_groups.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal permission/role data and timestamps. No PII fields are present. All columns are either internal IDs, permission references, or timestamps, which must be skipped per rules.
azazie__permanent_currency_rate.csv0 rows
File structure
Notes: free-form text with no consistent delimiter structure; appears to be a single line containing only the string 'currency_rate' and a numeric value (6.2442). No PII is present, and there is no row structure to map.
azazie__permission_menus.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only two columns: permission_id and menu_id. Both are internal IDs and do not contain any PII. Therefore, no columns are mapped to PII fields.
azazie__permission_templates.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a permissions/templates table with no PII fields. Columns include identifiers (id), names (name), keys (kee), descriptions (description), timestamps (created_at, updated_at), key patterns (key_pattern), and organization UUIDs (organization_uuid). All columns are internal system identifiers or metadata, not personal data. No email, phone, name, address, DOB, SSN, password, or other PII is present in the visible columns or sample values.
azazie__permissions.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be an access control / permissions configuration table containing role names, Chinese descriptions, and route patterns. All values are system identifiers or UI labels, with no personal data fields present.
azazie__physical_inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (inventory adjustments) with no PII fields. All columns represent internal IDs, timestamps, and adjustment notes in Chinese, none of which contain personal information. No email, phone, names, addresses, DOB, SSN, or other PII fields are present.
azazie__pick_up_tracking_number.csv1 column1,597 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | username | high | [3] column name 'print_user', values are alphanumeric strings resembling usernames |
Notes: Only column 3 (print_user) contains PII (username). Columns 0 (abs_id) and 1 (prefix) are internal IDs or codes and should be skipped. Timestamps in column 2 are non-PII and should be skipped.
azazie__plugins.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a metadata table listing software plugins or modules (UUID, plugin key, file hash, timestamps). No PII fields are present — all columns are internal identifiers, hashes, and timestamps. No emails, names, addresses, or other PII values are visible in the sample.
azazie__pm_dispatch_tracking.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal operational/tracking data (abs_id, provider_id, dispatch_sn, due_date, worker_id, process_id, create_time, finish_time, is_process). There are no personal identifiers or PII fields present. All columns represent internal workflow identifiers, timestamps, and status flags.
azazie__pm_process.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal process identifiers and codes with no personal or identifiable information. All columns represent internal manufacturing/operational processes (e.g.,裁剪 = trimming, 车位 = positioning, etc.) and contain no PII fields. Therefore, no columns map to PII categories.
azazie__pm_process_splitbill.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal operational data (order/shipment records) with no PII fields. Columns include internal IDs (abs_id), leader names (line_leader_name), leader IDs (line_leader_id), dispatch serial numbers (dispatch_sn), status flags (finished), supplier IDs (supplier_id), action users (action_user), and timestamps (create_stamp). None of these map to any PII categories as defined in the rules.
azazie__pm_process_worker.csv3 columns132 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | medium | [3] header 'worker_name', values are Chinese names and name-like strings |
| 12 | gender | high | [12] header 'sex', values are M/F gender codes |
| 13 | phone | high | [13] header 'telephone', values are numeric phone numbers |
Notes: This appears to be a worker/employee table from an internal operational database. Columns abs_id, provider_id, process_id, worker_id, is_quit, create_time, create_user, is_line_supervisor, line_supervisor, is_shipment, is_virtual are internal flags/IDs and skipped. 'idcard', 'bank', and 'bankcard' columns have no sample values and are ambiguous; idcard could be a national ID but values shown are literally 'idcard' (placeholder/header echo), so skipped with low confidence. worker_name mapped as fullName due to Chinese name patterns.
azazie__pm_worker_seq.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and codes (abs_id, provider_id, provider_code, next_seq). No PII fields are present. All columns map to skip categories: internal IDs and codes. No emails, names, addresses, or other personal data are visible.
azazie__pp_inv_snap.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the provided rows. The data appears to be transactional/order records containing only numeric IDs, dates, quantities, and status codes. All columns map to internal business identifiers, timestamps, or numeric values (no names, emails, addresses, etc.).
azazie__pp_reserve_result.csv3 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__ppml_alert_config.csv6 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__ppml_alert_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns appear to be internal tracking fields and JSON payloads with no PII. The columns are: abs_id (internal ID), report_date (timestamp), report_type (category), report_data (JSON payload), action_user (empty), create_time (timestamp), last_update_time (timestamp). None of these contain PII according to the exclusion rules. The JSON payloads contain inventory/purchase metrics, not personal data.
azazie__ppml_auto_batch_replenishment_plan_execute_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII columns. It consists entirely of internal operational data (plan IDs, configuration JSONs, timestamps) with no personal information exposed. All columns fall under the 'skip' category per exclusion rules (internal IDs, timestamps, configuration data).
azazie__ppml_auto_batch_replenishment_plan_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields are internal IDs, plan titles, category codes, status flags, JSON configuration blobs, and timestamps. No names, emails, addresses, or other personal data appear in the first 50 rows.
azazie__ppml_azazie_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal product identifiers, SKU codes, product descriptions, inventory flags, and timestamps. Columns like 'id', 'uniq_sku', 'pp_id', 'pp_goods_name', 'goods_name', and 'cat_name' are product metadata, not personal data. 'off_sale_time' and 'on_sale_time' are internal system timestamps, not DOB. No customer names, emails, addresses, or other PII are present in the first 50 rows.
azazie__ppml_batch_goods_purchase_spare.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, timestamps, and counters. All columns are non-PII per exclusion rules: id (internal ID), batch_sn (internal ID), spare_detail_id (internal ID), number (counter), in_number (counter), create_time (timestamp), last_update_time (timestamp). No PII fields present.
azazie__ppml_batch_purchase.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, flags, or operational data (batch IDs, check statuses, timestamps, print counts, party IDs, shipping fees, factory statuses, tracking numbers). No PII fields (email, phone, name, address, DOB, SSN, etc.) are present in this sample. Columns like usernames ('wswan1') are internal system users, not customer PII. Therefore, no columns map to PII fields.
azazie__ppml_batch_purchase_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All visible fields are internal IDs (abs_id, batch_id, purchase_id), usernames (action_user), and timestamps (create_time, last_update_time). These fall under the exclusion rules for internal IDs and timestamps.
azazie__ppml_batch_replenishment_plan.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, configuration data, timestamps, or flags. The 'config' column contains JSON structures with product titles and codes, but no personal information.
azazie__ppml_batch_replenishment_plan_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/inventory identifiers, timestamps, flags, or numeric counters. No PII fields (names, emails, addresses, etc.) are present in the first 50 rows. Columns like 'id', 'plan_id', 'container_id', 'external_goods_id', 'goods_name', 'uniq_sku', 'size', 'color', 'safe_stock', 'stock_sum', 'in_transit_num', 'last_3_days_sale', 'last_7_days_sale', 'last_30_days_sale', 'total_stock', 'stock_prediction_days', 'total_stock_prediction_days', 'purchase_num', 'real_purchase_num', 'after_purchase_prediction_days', 'arrival_date', 'action_user', 'create_time', 'last_update_time', 'config', 'order_type', 'spare_number', 'spare_detail_id', 'provider_id', 'web_sort', and 'priority' are all internal system identifiers, product attributes, or operational metadata — none contain personal or personally identifiable information.
azazie__ppml_bid_warning_bom.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The data appears to contain only product/order identifiers, SKU codes, financial amounts, and timestamps. No names, addresses, emails, phone numbers, or other personal data fields are present in the visible columns.
azazie__ppml_bid_warning_consumables_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers (id, setting_id, type, key_id) and timestamps (create_time, last_update_time). No PII fields are present. All columns are internal IDs or timestamps which must be skipped per exclusion rules.
azazie__ppml_bid_warning_consumables_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/operational data (IDs, SKUs, conversion rates, timestamps). No PII fields are present. All columns map to skip categories: internal IDs (id, uniq_sku), metrics (conversion_rate, clothing_usage), notes (remarks), and timestamps (create_time, last_update_time).
azazie__ppml_bid_warning_consumables_statistics.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns represent internal inventory/product tracking data (IDs, SKU codes, stock levels, timestamps). No personal information such as names, emails, addresses, etc., is present in the first 50 rows.
azazie__ppml_bid_warning_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, product metadata, timestamps, and operational flags (id, month, provider_id, uniq_sku, external_goods_id, goods_color, goods_name, goods_unit, provider_stock_num, real_bid_num, confrimed_bid_num, canceled_bid_num, status, create_time, last_update_time). These are typical inventory/order management fields with no personal customer data.
azazie__ppml_bid_warning_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal metrics and timestamps. No PII fields are present. All columns are internal IDs, numeric limits, rates, and timestamps which are skipped per exclusion rules.
azazie__ppml_check_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers, timestamps, and status codes. No PII fields are present. Columns like 'action_user' contain usernames that are likely internal system accounts, not customer PII. All other columns are internal IDs, timestamps, and status codes.
azazie__ppml_check_shipment_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal shipment/order identifiers and product codes. All columns are internal IDs, product SKUs, quantities, and timestamps. No PII is present.
azazie__ppml_color.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product/color metadata file with no PII fields. Columns describe color names, IDs, and timestamps of creation/update actions by users (action_user), but these users appear to be system/internal actors (yzhang14, xmwang) and not customer PII. No emails, addresses, names, or other PII are present.
azazie__ppml_custom_safety_stock_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. This appears to be product inventory data with identifiers, SKU codes, sizes, colors, and sales metrics. All columns are internal product IDs, non-personal attributes, or timestamps — none contain email, phone, name, address, DOB, SSN, or other PII. Columns like 'goods_name' contain product descriptions in Chinese, not personal names.
azazie__ppml_direct_delivery_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be order identifiers (direct_delivery_order_id, taobao_order_sn), statuses (product_status, confirm_status), and timestamps (create_time, last_update_time). These contain no personal information such as names, emails, addresses, or other sensitive data.
azazie__ppml_direct_delivery_order_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, product codes, inventory data, timestamps, and flags. No PII fields present. Columns like direct_delivery_order_goods_id, purchase_id, order_goods_id, batch_sn, inventory_item_id, uniq_sku, external_goods_id, color, size, goods_number, is_delete, provider_id, create_time, and last_update_time are all internal business identifiers, product attributes, or operational timestamps — none map to any PII field categories.
azazie__ppml_direct_delivery_order_goods_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, SKU codes, user identifiers, and timestamps. No personal information such as names, emails, addresses, or other PII fields are present in the sample data.
azazie__ppml_direct_delivery_order_operate_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational IDs and status flags. Columns 'direct_delivery_record_id' and 'direct_delivery_order_id' are numeric identifiers, 'confirm_status' is a numeric status flag, 'action_user' appears to be internal usernames or system accounts, 'create_time' and 'last_update_time' are timestamps, and 'note' is empty in all rows. No PII fields are present in this dataset.
azazie__ppml_direct_delivery_order_record.csv2 columns314 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | note | low | [4] values include Chinese characters and batch numbers, likely free-text notes |
| 5 | username | high | [5] values are alphanumeric strings, likely usernames or system identifiers |
Notes: Only columns 4 (note) and 5 (username) contain PII. Column 4 contains free-text notes with batch numbers and Chinese characters, while column 5 contains usernames or system identifiers. All other columns are internal IDs, timestamps, or status codes and should be skipped.
azazie__ppml_express_distribution.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data: province and city IDs, names, shipping IDs, user action logs, and timestamps. No PII fields are present. Columns like province_name and city_name are geographic codes, not personal addresses. Timestamps (create_time, last_update_time) are excluded per rules. User 'action_user' is an internal username, not a customer PII field.
azazie__ppml_fabric_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal configuration IDs, timestamps, and user identifiers. No PII fields are present. Columns map to internal IDs, flags, and timestamps, all of which are explicitly excluded per rules.
azazie__ppml_goods_id_category_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/category metadata and internal action timestamps. No PII fields present. Columns map to product IDs, category names in English/Chinese, user actions, and timestamps — all skip per rules.
azazie__ppml_important_goods_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided file appears to be a structured CSV containing inventory/product records for an online retailer. However, upon analysis of the header and sample data, none of the columns map to any of the defined PII fields (email, phone, dob, names, address, ssn, password, username, country, gender, suffix, facebookId). The columns primarily contain product identifiers (id, uniq_sku, external_goods_id), color codes, status flags (is_ignore, reason), and timestamps (create_time, last_update_time). These are all internal business data fields, not personally identifiable information. Therefore, no PII columns were identified.
azazie__ppml_important_goods_monitor_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file is structured as a CSV with columns: id, container_id, type, date, data, create_time, last_update_time. All columns contain inventory/order status data and timestamps. There are no PII fields in this dataset. The 'data' column contains JSON strings with inventory statuses like "存库找不到" (warehouse not found), "可预约量为0" (pre-order quantity is 0), and other operational metrics. No emails, phone numbers, names, addresses, or other PII are present.
azazie__ppml_in_warehouse_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the first 50 rows. The data appears to be order/settlement records containing only transactional IDs, monetary values, and timestamps. No personal identifiers such as names, emails, addresses, or phone numbers are present in the visible columns.
azazie__ppml_inventory_convert_relationship_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (IDs, timestamps, and user identifiers). All columns are internal IDs, timestamps, or action_user fields that do not contain PII. No columns map to PII fields.
azazie__ppml_inventory_monitor_config_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal operational configuration tracking records (check_id, apply_type, etc). No PII fields present. Columns map to internal system actions, timestamps, and JSON configuration payloads, all non-personal data.
azazie__ppml_maintained_history_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/pricing operational data (IDs, SKUs, provider codes, unit prices, flags, timestamps). No PII fields are present. Columns map exclusively to internal IDs (uniq_sku, provider_code), monetary values (unit_price), status flags (is_delete), user references (action_user), and audit timestamps (create_time, last_update_time). All values are non-personal transactional data.
azazie__ppml_material_info.csv1 column9 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 21 | username | high | [21] header 'action_user', values look like usernames (alphanumeric with possible dots) |
Notes: Only column 21 (action_user) contains PII (username). All other columns are internal product/inventory identifiers, numeric codes, timestamps, or flags — none contain personal data. No emails, phones, names, addresses, DOB, SSN, or passwords are present in this sample.
azazie__ppml_need_mi_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product inventory file with columns: id, external_goods_id, meter, size limits, goods_name, is_delete flag, action_user (internal username), create_time, last_update_time. No PII fields present. The action_user column contains internal system usernames (e.g., 'sty', 'pxing', 'leopard') which are not public-facing usernames and must be skipped per rules. All timestamps and numeric IDs are internal operational data. No emails, phones, names, addresses, or other PII detected.
azazie__ppml_new_goods_id_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data appears to be a product inventory or catalog listing from an online retailer. It contains product codes, names, descriptions, and other operational details but does not contain any personally identifiable information (PII) such as email addresses, phone numbers, names, dates of birth, or addresses. All fields appear to relate to product attributes, internal identifiers, and timestamps, none of which qualify as PII under the provided classification rules.
azazie__ppml_no_countting_sku.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal identifiers, SKU codes, and timestamps. The data appears to be inventory/order management records without customer personal information.
azazie__ppml_reserve_sequence.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/tracking data (IDs, timestamps, user handles). No PII fields are present. Columns map to skip categories: internal IDs (id, provider_id, container_id), internal flags (priority), notes/comments (note), usernames/handle (action_user), and timestamps (create_time, last_update_time).
azazie__ppml_safety_stock_calculate_execute_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII columns. It appears to be a log of system processes/rules with timestamps, configuration parameters, and execution results. All columns represent internal system identifiers, configuration settings, and status messages rather than personal data.
azazie__ppml_safety_stock_calculate_result.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, configuration data, timestamps, and status flags. No PII fields present. Columns like calculate_result_id, cat_codes, plan_name, state, config, action_user, remark, is_publish, create_time, and last_update_time contain operational metadata only.
azazie__ppml_safety_stock_calculate_result_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal product IDs, inventory metrics, timestamps, and system metadata. No personal customer data present in these rows.
azazie__ppml_safety_stock_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a configuration or settings dump, not customer data. All columns contain system parameters, JSON configuration blobs, and timestamps. No PII fields (names, emails, addresses, etc.) are present in the visible data. The 'action_user' field contains usernames, but these appear to be system accounts rather than customer PII. Per the rules, usernames are only mapped when they represent actual customer identifiers (e.g., login handles), which isn't evident here. The file is non-PII structured data.
azazie__ppml_safety_stock_special_goods_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product catalog data (IDs, SKUs, descriptions, timestamps). No PII fields are present. Columns like action_user contain internal system usernames (liwuxie, frankie.fu) which are NOT user-facing usernames and should be skipped per rules. All columns are internal product/operational data.
azazie__ppml_safety_stock_special_goods_setting_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product/inventory data with no personal identifiable information. Columns represent product IDs, names, pricing, quantities, and timestamps — all internal business data. The only potentially user-like field 'action_user' shows a system username ('liwuxie') which is not a genuine person identifier and is excluded per rules. No emails, phones, names, addresses, DOB, SSN, or passwords present.
azazie__ppml_sku_on_sale_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a structured CSV containing product or inventory data (SKU codes, sales flags, timestamps), but NO PII fields are present. All columns relate to product identifiers, sale status, and timestamps — none map to personal data categories. This is purely operational/product data from Azazie's inventory system.
azazie__ppml_split_order_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, counters, timestamps, and numeric codes related to order/shipment records. No PII fields present. Columns like id, lock_sn, origin_order_goods_id, etc., are non-personal operational identifiers and timestamps.
azazie__ppml_split_order_goods_tmp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, counters, timestamps, or relational keys. No PII present. Columns like 'id', 'lock_sn', 'origin_order_goods_id', and timestamps contain only system-generated data, inventory references, or audit logs.
azazie__ppml_split_order_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns represent internal order IDs, transaction codes, monetary values, timestamps, and status flags. No emails, names, addresses, phone numbers, or other personal data appear in the sample.
azazie__ppml_third_party_shipping_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, status flags, or transactional data. No PII fields present in this dataset. The columns include identifiers (abs_id, order_id), status codes, procedure/provider references, shipping details, tracking numbers, purchase order IDs, party IDs, user actions, and timestamps — none contain personally identifiable information per the defined rules.
azazie__ppml_third_shipping_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, or operational flags (abs_id, order_id, status, provider_id, shipping_method, express_name, tracking_number, party_id, action_user, create_time, last_update_time, entered_purchase_order_id, purchase_order_id, procedure_id). No PII fields present.
azazie__ppml_warehouse_in_out.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields present. All columns are internal IDs, inventory codes, timestamps, and system metadata. No emails, names, addresses, phone numbers, DOB, SSN, passwords, usernames, or other PII detected in the sample.
azazie__ppml_zero_batch_inventory_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/order identifiers, inventory counts, timestamps, and system users. No PII present. The 'action_user' column shows system usernames (not customer-facing), and all other columns are numeric IDs, SKU codes, size descriptors, and timestamps. No emails, names, addresses, phones, or DOB values detected.
azazie__ppml_zero_shear_batch_inventory_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, product attributes, timestamps, or system fields. 'action_user' contains a username but is not PII per exclusion rules (internal user identifiers). This appears to be inventory/order metadata from Azazie, not customer PII.
azazie__pre_refund.csv11 columns46 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 8 | username | high | [8] header 'CREATED_BY_USER_LOGIN', values are alphanumeric usernames like 'ywang7' and 'test101' |
| 9 | username | high | [9] header 'LAST_MODIFIED_BY_USER_LOGIN', same username pattern |
| 15 | username | high | [15] header 'ACCOUNT_USER_LOGIN', values match the same usernames as column 8 |
| 19 | username | high | [19] header 'EXECUTE_BY_USER_LOGIN', same username pattern |
| 21 | username | high | [21] header 'CONFIRM_BY_USER_LOGIN', same username pattern |
| 27 | username | high | [27] header 'CHECK_USER_LOGIN_1', values match the same pattern as other username columns |
| 28 | username | high | [28] header 'CHECK_USER_LOGIN_2', same username pattern |
| 29 | username | high | [29] header 'CHECK_USER_LOGIN_3', same username pattern |
| 30 | username | high | [30] header 'CHECK_USER_LOGIN_4', same username pattern |
| 31 | username | high | [31] header 'CHECK_USER_LOGIN_5', same username pattern |
| 55 | fullName | high | [55] header 'CUSTOMER_USER_NAME', values are full names like 'ames lbj' and 'bai lu' |
Notes: Only columns containing PII are mapped. All others are internal IDs, timestamps, financial amounts, or status flags and are skipped per exclusion rules.
azazie__pre_refund_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, timestamps, transaction codes, product references, and flags (e.g., REFUND_DETAIL_ID, CREATED_STAMP, PRODUCT_ID, AMOUNT). Values are numeric IDs, monetary amounts, status flags (Y/N), and internal reference codes with no personal information.
azazie__pre_refund_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. File contains only internal transaction IDs (abs_id, refund_detail_id), status codes (reason_level, customer_service_type), timestamps (create_stamp), and generic user identifiers (action_user). All columns fall under the exclusion rules for internal IDs, flags, and timestamps.
azazie__prepayment_payment_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal payment type codes and timestamps - no PII fields present. All columns map to internal business codes or timestamps and are skipped per rules.
azazie__prepayment_transaction_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transaction type metadata - internal codes, timestamps, and descriptive notes. No PII fields are present. All columns are internal identifiers or timestamps which must be skipped per rules.
azazie__prestore_inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, or inventory identifiers. No PII present in this file.
azazie__prestore_inventory_dispatch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal identifiers, timestamps, and status flags (e.g., abs_id, uniq_sku, assign_user, finish_user, prestore_status). No PII fields are present in this sample. The columns represent operational tracking data for order fulfillment rather than customer personal information.
azazie__price_dissent.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, version numbers, and timestamps. No PII fields present in this dataset.
azazie__price_dissent_version.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, status flags, or user action metadata. No PII present. Columns like 'final_check_user' and 'action_user' contain internal system usernames, not customer identifiers. This is an operational tracking table for product versions, not customer data.
azazie__price_dissent_version_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal tracking IDs, status flags, JSON structures with purchase parameters, and timestamps. No PII fields are present. Columns like 'detail_id', 'dissent_sn', and JSON blobs containing purchase ranges ('step_id', 'purchase_number_range') are internal operational data. No emails, names, addresses, or other PII are visible in the sample rows.
azazie__price_dissent_version_detail_log.csv0 rows
File structure
Notes: The file appears to be a JSON-like structure embedded within CSV rows. The visible data contains product provider details including provider_name, provider_phone, and provider_address — all PII. However, the format is not a standard delimited text file but rather a CSV with a single column containing JSON strings. Since the structure isn't a clean delimited format with identifiable column headers mapping to PII fields, we classify this as unstructured for PII extraction via streaming. All PII is contained within the JSON blobs (provider_name, provider_phone, provider_address).
azazie__price_tracking_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product catalog data (category IDs, URLs, timestamps). No PII fields present. All columns are internal identifiers, URLs, or timestamps which are explicitly excluded by rules. Therefore, no columns map to PII fields.
azazie__price_tracking_category_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, counters, or non-PII product/order references. No PII fields present in this dataset.
azazie__price_tracking_jjs_litb.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data consists of product listings with columns for product IDs, URLs, and timestamps. No PII fields are present in this dataset. All columns represent internal product identifiers, URLs, and timestamps, which are excluded per the rules.
azazie__print_serial_number.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order/product identifiers and statuses. No PII fields are present. All columns are internal IDs, product codes, amounts, and status flags — none map to personal data fields.
azazie__print_stat.csv2 columns236 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | username | high | [6] header 'create_by_user_login', values are alphanumeric usernames |
| 7 | username | high | [7] header 'last_update_by_user_login', values are alphanumeric usernames |
Notes: Identified 2 columns containing username PII. All other columns represent internal transaction IDs, counters, timestamps, and status flags which are not personally identifiable.
azazie__priority_factory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal action logs (provider_id, user, timestamp). No PII fields are present. All columns are internal IDs or timestamps and must be skipped per exclusion rules.
azazie__priority_factory_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal action logs (action_id, action_user, action_time, action_name, provider_id). There are no PII fields present. All columns are internal identifiers, timestamps, or action types — all mapped to skip per exclusion rules.
azazie__proc.csv10 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__process.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal process identifiers and timestamps. All columns represent internal operational codes and timestamps, with no personal identifiable information (PII) present. The columns are: process_id (internal ID), created_stamp (timestamp), last_update_stamp (timestamp), process_code (internal code), process_name (internal description), display_order (internal ordering). Per exclusion rules, all columns must be skipped as they contain no PII.
azazie__process_data_diff.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All 11 columns are internal operational data: IDs, delivery serial numbers, status flags, diff counters, facility IDs, workflow links, internal usernames (system accounts), and timestamps. This appears to be a shipment/QC tracking table with no customer PII.
azazie__process_data_diff_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns appear to be internal tracking identifiers (delivery_sn, order_sn), timestamps (action_time, created_at, updated_at), and user action logs (action_name, action_note). No personal information such as names, emails, or addresses is present in the first 50 rows.
azazie__process_data_diff_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, shipment tracking codes, product attributes, inventory counts, timestamps, and user roles — none contain personal information. This appears to be a logistics/warehouse management table rather than customer data.
azazie__process_worker.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal process worker IDs and names that appear to be usernames or worker identifiers rather than personal customer PII. All columns are internal process metadata (process_worker_id, provider_id, external_goods_id, process, worker, onthejob). No PII fields (email, phone, address, etc.) are present. The 'worker' column contains short alphanumeric strings or Chinese characters that look like internal worker codes rather than real names.
azazie__product.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain product metadata (IDs, dimensions, pricing, inventory) and internal system references. No PII fields detected in this product catalog export. All columns map to product attributes, inventory flags, or internal identifiers — none contain customer names, emails, addresses, or other personally identifiable data.
azazie__product_category_member.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal product/category identifiers (numeric strings with hyphens). No emails, names, addresses, or other PII present in the first 50 rows.
azazie__product_facility_location.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This file contains inventory/product data (SKUs, product IDs, facility IDs, quantities, timestamps) with no personal information.
azazie__product_facility_location_20210128_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This file contains product/inventory data: SKUs, product IDs, facility IDs, timestamps, and quantity fields. All columns are internal operational/product data and should be skipped.
azazie__product_facility_location__bakcontainer20170305.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, quantities, or codes with no PII. No email, phone, name, address, DOB, SSN, password, or username fields present.
azazie__product_lend.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a purely transactional table with internal IDs and status codes. No PII fields are present. Columns like 'lend_user' contain usernames or system identifiers, not actual names or contact details.
azazie__product_lend_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, process flags, and system identifiers. 'pk_user' and 'return_user' appear to be internal system usernames, not customer identifiers. No emails, phone numbers, names, addresses, DOB, SSN, or passwords present.
azazie__product_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only product mapping IDs and numeric codes - no PII present. All columns represent internal product identifiers, styles, and ECS goods references.
azazie__product_tags.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only product tags/labels (e.g., dress categories, language codes, display flags) with no personal data. All columns map to internal product metadata or business flags per exclusion rules.
azazie__product_tags_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII fields detected. All columns appear to contain internal IDs, hashes, or counters (pti_id, pt_id, tag_wordcount, tag_visitedcount, tag_name_md5). No email, phone, name, address, or other personal data is present in the first 50 rows.
azazie__product_tags_project_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and the company name repeated across all rows. No PII fields are present. Columns ptpm_id and pt_id are internal numeric IDs, and project_name is a static company name.
azazie__product_tags_word_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal identifiers (ptwm_id, ptw_id, pt_id) and weight values. No emails, phone numbers, names, addresses, or other PII fields present in the sample.
azazie__product_tags_words.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: File contains only word_name entries and is_legal flags — no PII present. All entries appear to be product/description keywords or metadata, not personal data.
azazie__production_process_sheet.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal product/order identifiers, timestamps, and unstructured notes in Chinese/English. No PII fields detected. Columns like 'operator' contain a static username ('yzhang') and timestamps are non-DOB. Values in text columns do not contain identifiable personal data patterns.
azazie__program_debug.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII fields identified in the provided rows. The data consists of SQL INSERT statements for a table named 'romeo.inv_location_check_detail' containing inventory check details, but no personal information such as names, emails, phone numbers, addresses, or dates of birth is present. The values appear to be internal codes, SKU numbers, and timestamps.
azazie__project_branches.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a version control / repository metadata export, not customer PII. All columns are internal identifiers, timestamps, and repository state flags. No PII fields present.
azazie__project_price_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal operational data (IDs, timestamps, flags, financials) with no PII present. 'action_user' contains short alphanumeric strings likely internal usernames, not full names or emails. No email, phone, name, address, DOB, SSN, or other PII fields detected.
azazie__projects.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, timestamps, or metadata. No PII fields (name, email, address, etc.) are present in the first 50 rows. Columns like 'id', 'uuid', 'created_at', and others are internal IDs, flags, or system metadata, and do not contain personal information.
azazie__properties.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal system table (sonarqube properties), not customer data. No PII fields present. All columns are internal system identifiers, timestamps, and flags.
azazie__provide_new_product.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/order identifiers, timestamps, and company communication metadata. No PII fields present.
azazie__provider.csv1 column15 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 22 | phone | high | [22] header 'mobile_numbers', values are comma-separated phone numbers |
Notes: Only column 22 (mobile_numbers) contains PII (phone numbers). All other columns are internal IDs, company data, timestamps, or flags, and must be skipped per exclusion rules.
azazie__provider_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an unstructured data file containing only internal company categories and codes. No PII fields are present. The columns are: abs_id (internal ID), provider_attribute_id (internal ID), provider_attribute_name (descriptive text about business categories). All columns are non-PII per exclusion rules (internal IDs and company/business data).
azazie__provider_bank.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal banking/transactional data (provider IDs, bank account numbers, timestamps, flags). No PII fields (email, phone, name, address, DOB, SSN, etc.) are present. Values like '阿三' (a Chinese name) are embedded in a bank customer ID field and not intended as personal PII. All columns are skipped per exclusion rules for company/bank data and internal IDs.
azazie__provider_capacity_rating.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, timestamps, and status flags. No PII fields are present. All columns map to skip categories (internal IDs, timestamps, status flags).
azazie__provider_cat_d30_date_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields are internal shipment identifiers, dates, and codes. Values contain only transaction references and numeric codes with no personal information.
azazie__provider_category_assign.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, flags, timestamps, counters, or numeric values. No PII fields are present. Columns like 'action_user' contain short alphanumeric strings that appear to be system-generated usernames, not actual personal usernames.
azazie__provider_category_assign_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. All visible fields are internal IDs, timestamps, counters, or codes (abs_id, record_date, provider_id, cat_code, today_assign_target, today_assigned, create_time, last_update_time). These map to skip categories per rules (internal IDs, timestamps, counters).
azazie__provider_category_assign_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The data appears to be internal system logs tracking provider assignments and overdue rates, with no personal identifiable information exposed in the visible columns.
azazie__provider_change_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. File contains only internal operational records tracking supplier assignments and percentage allocations for products. All columns map to internal IDs, actions, and timestamps which are explicitly excluded per rules. No email, phone, name, address, or other PII fields present.
azazie__provider_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a simple mapping table with no PII fields. Columns are abs_id, provider_id, template_id, and language. None of these contain personal identifiable information according to the rules.
azazie__provider_constant_options.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a structured dataset containing business metrics, factory attributes, location codes, and product categories. All columns represent internal business data, operational statistics, and categorical classifications rather than personally identifiable information.
azazie__provider_copy.csv3 columns7 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | address1 | high | header "address" resolves to PII field "address1" |
| 8 | phone | high | header "phone" resolves to PII field "phone" |
| 9 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__provider_dispatch_capacity.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, numeric values, or timestamps. No PII fields present. Columns like id, provider_id, external_cat_id, and various invoice numbers are internal identifiers. Dates and times are operational timestamps, not personal data.
azazie__provider_dispatch_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided data. The file appears to contain only internal IDs, product codes, and timestamps, with no personal information such as names, emails, phone numbers, or addresses.
azazie__provider_dispatch_config_diff.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a simple inventory or transaction log with only numeric IDs and timestamps. No PII fields are present. All columns map to internal IDs, counters, or timestamps which must be skipped per rules.
azazie__provider_dispatch_stock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational IDs and timestamps. No PII fields are present. Columns like 'action_user' contain generic system identifiers ('qymeng', 'WebService') not personal user data. All columns map to skip categories: internal IDs (id, order_goods_id, provider_id) and timestamps (create_time, last_update_time).
azazie__provider_fabric_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in this structured CSV file. Columns contain only internal IDs (abs_id, provider_id), technical identifiers (fabric_id), product names (fabric_name), status flags (is_delete, action_user), and timestamps (create_time, last_update_time). All columns fall under the exclusion rules for internal IDs, vehicle/product data, or timestamps.
azazie__provider_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product catalog / inventory file with no PII fields. Columns contain product IDs, SKU codes, color names, category names, links, and notes — all non-personal business data. No customer names, emails, addresses, or other personal identifiers present in the first 50 rows.
azazie__provider_goods_availability.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (IDs, timestamps, status flags). No PII fields are present. All columns are marked as skip per exclusion rules (internal IDs, timestamps).
azazie__provider_goods_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, product codes, timestamps, user action logs, and system metadata. The 'created_user' values appear to be system-generated usernames not tied to customer accounts.
azazie__provider_goods_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction IDs, product mappings, and timestamps. No PII fields are present. All columns are internal identifiers, product codes, or timestamps — none map to personal data categories.
azazie__provider_goods_relation_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The file appears to contain only internal product configuration data (product_capacity_from, product_capacity_to, relation_y_down_limit, relation_y_up_limit) and lifecycle rules. All values are numeric limits or JSON structures describing business rules, with no personal identifiable information present.
azazie__provider_goods_relation_suggest.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file contains only internal IDs and relationship flags with no PII present. All columns are internal identifiers (abs_id, external_goods_id, provider_id) and relationship status codes with timestamps, which are excluded by policy.
azazie__provider_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, group codes, user identifiers, and timestamps. No PII fields are present. All columns map to skip categories: provider_id (internal ID), provider_group (group code), action_user (username-like but likely internal system user), action_time (timestamp).
azazie__provider_has_constants.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a structured CSV but contains no PII fields. All columns represent internal identifiers (id, provider_id, constant_id), numeric values, and timestamps. There are no email addresses, phone numbers, names, addresses, dates of birth, SSNs, passwords, usernames, or other PII fields present in the first 50 rows.
azazie__provider_location.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This is a purely numerical dataset with columns abs_id, provider_id, location_code, and is_gt. All values are integers or booleans with no personal identifiers or free-text fields. No PII fields are present.
azazie__provider_party.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal identifiers (abs_id, provider_id, party_id) and a status flag (is_used). No PII fields are present. All columns are internal IDs or status flags, which must be skipped per exclusion rules.
azazie__provider_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal identifiers, prices, timestamps, and system-generated values. Column 8 (CREATED_BY) appears to be a system username, but it's not a searchable user identifier and is excluded per rules.
azazie__provider_price_region.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (id), region codes, and timestamps (create_time, last_update_time). No PII fields are present. All columns are marked as skip per exclusion rules.
azazie__provider_process_dispatch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only operational/process tracking data (dispatch IDs, process codes, timestamps, worker initials). No PII fields are present. All columns are internal identifiers, flags, or timestamps which must be skipped per exclusion rules.
azazie__provider_process_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII detected in the first 50 rows. All columns appear to contain internal IDs, numeric codes, timestamps, and status flags. No names, emails, addresses, phone numbers, dates of birth, or other PII fields are present. The data represents internal product/process identifiers and timestamps.
azazie__provider_product_line.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal IDs, timestamps, and counters. No PII is present in the first 50 rows. All columns appear to be numeric identifiers or date-time stamps, which are excluded by policy.
azazie__provider_purchase_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns appear to be internal IDs, product codes, pricing data, and timestamps. The 'action_user' field contains system identifiers ('webService') rather than human user identifiers.
azazie__provider_purchase_price_20210125_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the first 50 rows. The data appears to be transactional records containing only product IDs, pricing information, and timestamps. No personal identifiable information (names, emails, addresses, etc.) is present in the visible columns.
azazie__provider_purchase_price_20210428_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product inventory/pricing table containing only transactional and product data. All columns represent internal product IDs, pricing values, and system metadata. No personal identifiable information (PII) is present in this dataset.
azazie__provider_purchase_price__20200522.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional purchase records with product IDs, sizes, prices, and timestamps. No PII fields (names, emails, addresses, etc.) are present. Columns like 'action_user' contain system identifiers ('webService') rather than human user identifiers. All data relates to product pricing and inventory management, not customer personal information.
azazie__provider_purchase_price_change_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided data. The file appears to contain internal business operation logs with JSON payloads representing material cost changes, but no personal information such as names, emails, phone numbers, or addresses is present in the visible columns or sample rows.
azazie__provider_purchase_price_change_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file contains only numeric IDs and timestamps with no personal identifiable information (PII). All columns represent internal system identifiers (id, change_summary_id, change_log_id) and timestamp fields (create_time, last_update_time). No names, emails, addresses, phone numbers, dates of birth, or other PII fields are present in the sample data.
azazie__provider_purchase_price_change_summary.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional and operational data related to purchase price adjustments, provider pricing, and financial deltas. No personal identifiable information (PII) fields are present. All columns relate to internal business processes, financial calculations, timestamps, and system metadata. The 'action_user' field appears to be a system username, not a personal user identifier.
azazie__provider_purchase_price_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product pricing and operational data (IDs, currency codes, price values, timestamps). No personal identifiable information (PII) fields are present. All columns are internal identifiers, business metrics, or timestamps that must be skipped per rules.
azazie__provider_purchase_price_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, product codes, pricing data, timestamps, and flags — no PII present. This is typical inventory/order data from Azazie, not customer data.
azazie__provider_purchase_price_history__back.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal identifiers, pricing data, timestamps, or system-generated flags. The column 'action_user' contains a username-like value ('jacky.hu'), but this is likely a system user or service account, not a customer PII field. Per rules, internal IDs and system users are skipped.
azazie__provider_purchase_price_tmp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product/pricing table with no PII fields. Columns are all identifiers, pricing data, and timestamps — none map to personal data categories. All columns are skipped per rules (company/product data, internal IDs, timestamps).
azazie__provider_qualify_app.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal system identifiers, timestamps, status codes, and user actions. Fields like abs_id, external_goods_id, provider_id, handover_time, and application_status contain operational metadata, not personal data. Usernames (xmwang, cmwu, etc.) are system/internal account identifiers, not customer PII. No emails, names, addresses, or other PII fields are present.
azazie__provider_quantity_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal provider identifiers and allocation rates. No PII fields are present. Columns map to skip categories (internal IDs, business codes, flags).
azazie__provider_rank.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers (rec_id), date ranges (year_month), and provider rankings. No PII fields are present. All columns are skipped per exclusion rules: rec_id is an internal ID, year_month is a timestamp range, and provider_id/rank are internal business codes.
azazie__provider_score_config.csv1 column2 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 7 | high | [7] column header is 'mail_list', and sample values contain valid email addresses like 'morty.wang@i9i8.com' |
Notes: Only column 7 contains PII (email addresses). All other columns are internal configuration data, timestamps, or identifiers and have been skipped per rules. The file is a structured CSV with a header row.
azazie__provider_score_cycle.csv25 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__provider_score_snapshot.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal metrics/scoring data and timestamps. No PII present. Columns are internal IDs, score metrics, and timestamps — all fall under exclusion rules (internal IDs, timestamps).
azazie__provider_storage_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/supplier identifiers and inventory counts. No PII fields present. Columns contain product IDs, color codes, supplier references, and quantity totals — all operational data without personal information.
azazie__provider_switch_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (provider codes, shipping flags, timestamps). No PII fields are present. Columns map to skip categories: provider_code (company/business), is_expedited_shipping (flag), create_time / last_update_time (timestamps).
azazie__provider_template.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is not a PII-containing file. The columns 'template_id' and 'template_name' contain only internal template identifiers and descriptive names (e.g., '广东礼服皮肤'). No personal or sensitive data is present. All columns are skipped per rules (internal IDs and non-PII descriptors).
azazie__proxies_priv.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a MySQL access log / host/user connection log, not customer PII data. Contains system-level connection metadata (host, user, timestamp). No personal identifiers (email, name, address, etc.) are present. All columns are system/internal metadata and should be skipped.
azazie__proxy_speed.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided rows. The data appears to be performance metrics (download times, sizes, error codes) related to different geographic nodes and services. There are no columns containing personal identifiable information such as names, emails, phone numbers, addresses, or dates of birth.
azazie__proxy_speed_144.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a log file containing performance metrics for different front-end nodes (Front-HZ04, Front-HZ149, Front-SH41) accessing various sites (gmail, google, bing, dhlbanner). All columns are internal performance metrics and identifiers (abs_id, node, site, flag) and do not contain any PII fields. There are no emails, phone numbers, names, addresses, or other personal data in this dataset.
azazie__proxy_speed_fast.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be performance metrics (response times, sizes, HTTP codes) rather than personal or account data. This matches the breach description of network performance logs rather than customer PII.
azazie__proxy_speed_fast26.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is NOT a PII-containing file. It contains only network performance metrics (abs_id, node, site, flag, total_time, connect_time, transfer_time, speed_download, size_download, httpcode). No personal information is present.
azazie__purchase_assign_factory_apply.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields present. Columns are internal IDs, status codes, timestamps, and batch identifiers. All columns match exclusion rules for internal IDs and timestamps.
azazie__purchase_bill.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns are internal IDs, timestamps, status flags, financial amounts, or operational codes. No names, emails, addresses, or other personal data appear in the first 50 rows.
azazie__purchase_bill_bf.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, transaction codes, timestamps, status flags, or system metadata. Values show only numeric IDs, UUIDs, monetary amounts, status codes, and ISO timestamps — none match PII patterns (emails, names, addresses, DOB, SSN, etc.). This aligns with Azazie's order/shipment records context where customer data is likely in separate tables.
azazie__purchase_bill_bf_pay.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal transaction IDs, numeric codes, status flags, timestamps, and response JSON snippets. No PII is present. Columns like id, remit_req_no, trans_no, trans_batch_id, trans_order_id, bill_ids, provider_id, order_amount, currency, status, status_desc, response, create_time, last_update_time are all internal system identifiers or operational metadata — none map to personal data fields.
azazie__purchase_bill_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal transaction identifiers, amounts, and status flags. No PII fields detected in the first 50 rows. The data appears to be purely operational purchase records without any personal information.
azazie__purchase_bill_detail_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction IDs and timestamps. No PII fields are present. Columns are: purchase_bill_detail_id (internal ID), is_submit (flag), create_time (timestamp), last_update_time (timestamp). All columns are excluded per rules (internal IDs and timestamps).
azazie__purchase_bill_lkl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal system identifiers, timestamps, status codes, and JSON payloads — none contain PII. Columns like 'id', 'bill_ids', 'trans_id', and timestamps are internal references and operational metadata only. No email, phone, name, address, or DOB data present.
azazie__purchase_bill_lkl_batch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, transaction metadata, timestamps, and status flags. The data appears to be batch processing records for financial settlements, with no customer or personal information exposed.
azazie__purchase_bill_lkl_batch_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, transaction codes, timestamps, or numeric values unrelated to personal information. The file appears to be a financial/operational log from Azazie, not containing customer PII data.
azazie__purchase_bill_lkl_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains error logs and system messages with numeric IDs, timestamps, and error descriptions. No personal or sensitive data fields identified in the first 50 rows.
azazie__purchase_contact.csv2 columns3 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header 'user_name', values appear to be short alphanumeric usernames |
| 3 | phone | high | [3] header 'phone', values are 11-digit US phone numbers |
Notes: 7 columns total, 2 contain PII (username, phone). Columns 0 (abs_id) and 1 (cat_id) are internal IDs, columns 4-6 are timestamps/flags and should be skipped.
azazie__purchase_finish_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The data consists of order IDs, batch information, timestamps, and status flags. No personal information such as names, emails, addresses, or phone numbers is present in the visible columns.
azazie__purchase_goods_quality_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided sample data is a CSV file, but all columns appear to be internal identifiers, metadata, or encoded HTML content. There are no visible PII fields such as names, emails, phone numbers, or addresses in the sample. The 'des_content' column contains encoded HTML content, which may contain PII when decoded, but this cannot be determined from the sample alone. Therefore, no PII columns are mapped based on this sample.
azazie__purchase_goods_sale_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, product identifiers, pricing, and a static timestamp. No PII fields are present.
azazie__purchase_info_snap.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The file appears to be an order goods table containing only order IDs, product SKUs, and numeric values (material totals and size types). No personal information such as names, addresses, emails, or phone numbers is present in the visible data.
azazie__purchase_inv_plan.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only plan management data (plan_id, plan_type, deletion flags, timestamps). No PII fields are present. All columns are internal identifiers, types, or timestamps that fall under exclusion rules.
azazie__purchase_inv_plan_batch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/inventory data columns. All columns are internal IDs, sales metrics, stock counts, and system timestamps. No PII fields are present. Columns like 'action_user' contain system user identifiers, not personal names. The 'remark' column contains non-personal text in Chinese characters. This is consistent with the Azazie breach context as an inventory database dump.
azazie__purchase_inv_plan_sample.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/inventory metrics or timestamps. Column 19 ('remark') contains non-standard strings that do not resolve to any PII field. No PII is present in this dataset.
azazie__purchase_memo_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be an audit log or action tracking table with no PII fields. Columns contain action IDs, status flags, user references (which are internal system users), and timestamps. No personal identifiable information is present.
azazie__purchase_memo_info_new.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal action tracking data (action IDs, closure status, users, timestamps). No PII fields are present. All columns are internal IDs, flags, or timestamps and must be skipped per exclusion rules.
azazie__purchase_order_cancelled.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No columns contain PII. All columns are internal IDs, timestamps, or status flags. 'mobile_list' suggests a potential phone number field but values are empty and no actual phone numbers appear in the data.
azazie__purchase_order_note.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order identifiers and timestamps. No PII fields are present. All columns map to skip categories: order IDs, notes, and timestamps.
azazie__purchase_package.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. This appears to be a package/pricing table with internal codes, currency codes, and timestamps. All columns map to business/internal identifiers, pricing metadata, or timestamps — none contain personal data.
azazie__purchase_package_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, pricing data, timestamps, or processing fees. No PII fields are present in this dataset. Columns like package_detail_id, package_id, external_goods_id, cp_goods_id, external_cat_id, price, large_size_price, small_size_price, create_time, last_update_time, and processing_fee are all internal business metrics and do not contain any personally identifiable information.
azazie__purchase_package_detail_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, financial values, status flags, timestamps, and processing fees. No PII fields detected. Columns like id, package_id, external_goods_id, cp_goods_id, old_price, price, status, check_user, check_time, create_user, create_time, last_update_time, old_processing_fee, and processing_fee are all internal system data, transactional values, or timestamps — none map to PII categories.
azazie__purchase_package_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, timestamps, status flags, or action metadata typical of an operational database log. Columns like 'check_user' and 'create_user' contain usernames but follow the exclusion rule for internal IDs (user_id, customer_id, account_id, etc.).
azazie__purchase_package_sku_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified in the first 50 rows. The data appears to be product/package identifiers, pricing, and timestamps, with no personal information present.
azazie__purchase_package_sku_detail_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, financial data, timestamps, or status flags. The data appears to represent product/order processing metadata rather than customer personal information.
azazie__purchase_price_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal monitoring/flag columns (monitor_id, version, status, timestamps). No PII present. All columns are metadata/internal IDs and timestamps, which map to skip per exclusion rules.
azazie__purchase_price_monitor_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal product pricing identifiers and values (detail_id, monitor_id, version, external_goods_id, cp_goods_id, provider_id, region_id, and various price fields). No PII fields are present in this dataset — these are purely transactional/product data columns.
azazie__purchase_price_update_lock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, and flags. No PII fields detected. Columns: abs_id (internal ID), create_time (timestamp), update_time (timestamp), purchase_order_sn (transaction ID), action_user (username-like but likely internal), is_lock (flag).
azazie__purchase_return_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, or transactional identifiers (purchase/return maps). No PII fields detected. The data represents purchase-return mapping relationships rather than customer records.
azazie__qc_app_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, status flags, or system metadata. No PII fields detected. 'create_by_user_login' appears to be a system username (not a customer identifier) and is excluded per policy.
azazie__qc_app_check_statistic.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (provider codes, quality checks, counts, timestamps). No PII fields are present. All columns map to internal IDs, counters, dates, or flags and must be skipped per exclusion rules.
azazie__qc_app_user.csv1 column22 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | [1] header 'user_name', values are alphanumeric strings resembling usernames |
Notes: Only column 1 (user_name) contains PII. All other columns are internal IDs, statuses, timestamps, or creator info and should be skipped per rules.
azazie__qc_app_user_role.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (id, user_id, role_id) and timestamps (create_time, update_time). No PII fields are present. All columns are marked as skip per exclusion rules for internal IDs and timestamps.
azazie__qc_app_user_session.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is not a PII-containing file. It contains only session tokens, timestamps, and internal numeric IDs. No personal identifiable information is present in the visible columns or sample data.
azazie__qc_factory_asset_information.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal identifiers, quality control metrics, timestamps, and counters. No PII fields detected. Columns like 'id', 'qc_num', 'provider_id', and operational counters contain no personal data. Timestamps ('create_time', 'modifytime') are not DOB. No emails, names, addresses, phones, or SSNs present.
azazie__qc_hand_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The file appears to contain only internal transaction identifiers, status codes, and timestamps. All columns represent internal system data (IDs, serial numbers, action types, and timestamps) with no personal information exposed in the visible rows.
azazie__qc_hand_over_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, status codes, or system metadata. Columns like 'id', 'provider_id', 'dispatch_sn', 'add_time', 'create_time', and 'status' are internal operational fields, not containing personal information. No email, phone, name, address, DOB, or SSN data present in the first 50 rows.
azazie__qc_lead_privilege.csv1 column54 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | [1] header is 'username', values are alphanumeric strings used as login identifiers |
Notes: Only column 1 (username) contains PII. All other columns (abs_id, provider_code, update_stamp, flag) are internal IDs, codes, timestamps, and flags — excluded per rules.
azazie__qc_member_privilege.csv1 column4 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | [1] header is 'username', values are alphanumeric strings resembling login handles |
Notes: Only column 1 (username) contains PII. Columns 0 (abs_id) is an internal numeric ID, column 2 (category) contains region names not personal PII, and column 3 (update_stamp) is a timestamp — all skipped per rules.
azazie__qc_quality_inspection_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All values appear to be internal IDs, numeric codes, and timestamps. No emails, names, addresses, phone numbers, or other PII fields are present in the sample. The data consists of identifiers (id, fid, qc_num), provider references, inspection/shipment/repair numbers, and timestamps (create_time, mod_time).
azazie__qc_que_set.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file contains only internal IDs (column 0), free-text complaint codes (columns 1 and 2), and timestamps (column 3). No PII fields are present. Column 1 contains structured complaint codes (e.g., '1,2,3,4,5'), column 2 contains complaint types (e.g., '1' for product type), and column 3 is a timestamp. None of these map to PII categories per the rules.
azazie__qc_staff_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields appear to be internal identifiers (director, group_leader, staff), version numbers, and timestamps. Values are Chinese personal names but represent non-PII internal role assignments rather than customer PII. No emails, addresses, phone numbers, or other sensitive data present in the sample.
azazie__qc_workload.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal operational data with no PII fields. Columns represent internal identifiers (abs_id, dispatch_sn, provider_code), customer/party IDs (party_id), timestamps (work_date), and worker names (work_name). All values appear to be internal system identifiers, codes, and operational timestamps without any personal information such as names, emails, addresses, or phone numbers. The worker name field contains only the initial 'yzhang' or 'wmzhen' which appears to be system user codes rather than actual personal names.
azazie__qc_workload_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal identifiers (abs_id, dispatch_sn, provider_code, party_id), timestamps (work_date), names (work_name), and status codes (work_type). No email, phone, address, DOB, SSN, or other PII fields are present in the header or sample values. This matches typical internal dispatch/work tracking data from Azazie's database.
azazie__qprofile_changes.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This is not structured PII data; it's a log of rule activations with UUIDs, severities, and timestamps. No personal identifiable information is present in the visible columns.
azazie__quality_control_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (provider IDs, codes, QC flags, timestamps). No PII fields present. All columns are internal identifiers or status flags and should be skipped.
azazie__quality_forum.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, tracking numbers, timestamps, flags, or unstructured data fields. The 'reason' and 'images' columns contain JSON fragments or file paths, not personal information.
azazie__quality_gate_conditions.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal metrics/operational data (ids, timestamps, thresholds). No PII is present. All columns are internal IDs, flags, timestamps, or numeric thresholds — explicitly excluded per rules.
azazie__quality_gates.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a simple internal reference table for system configurations, not containing any PII. Columns are purely technical/operational (id, name, timestamps, flags, UUID). No PII fields detected.
azazie__query_record.csv44 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__receipt_batch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns are internal IDs (supplier_id), transaction types (batch_type), timestamps (batch_time), and operator names (yzhang) which do not qualify as personal PII under the defined categories. The operator appears to be a system username rather than a personal identifier.
azazie__receipt_dispatch_sn.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields appear to be internal operational identifiers, status codes, timestamps, and operator initials. No personal data (names, emails, phone numbers, addresses, etc.) is present in the first 50 rows.
azazie__receipt_images.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, system paths, file metadata, and timestamps. No PII fields present. The file appears to be a storage/retrieval tracking table for receipt images, not customer data.
azazie__receipt_images_tmp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal identifiers, paths, timestamps, or technical metadata. 'action_user_name' is an internal username (not public-facing), and other columns are system identifiers or file metadata. No emails, phone numbers, names, addresses, DOB, SSN, or passwords present.
azazie__receipt_return_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, batch references, dispatch serial numbers, timestamps, and operator initials. No PII fields are present in this operational tracking table.
azazie__receivable_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are financial transactional data (order IDs, monetary amounts, variance calculations). No PII fields present. Columns map to internal order tracking and accounting metrics only.
azazie__receivable_check_backup.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are financial/transactional data (amounts, IDs, timestamps, error messages) or internal identifiers. No PII fields detected. Columns like abs_id, report_request_id, taobao_order_sn are internal IDs or order references, and all numeric/date values represent financial amounts or timestamps, not personal data.
azazie__receivable_new_receivable_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional data (order numbers, timestamps, order types, and monetary amounts). There are no personal identifying information (PII) fields present in the visible columns. All columns represent internal business data and financial transaction records, which are excluded by policy.
azazie__receivable_new_receivable_summary.csv6 columns1,668 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 21 | high | header "email" resolves to PII field "email" | |
| 25 | high | unlabeled column — sampled values parse as email addresses | |
| 33 | state | high | header "province" resolves to PII field "state" |
| 34 | city | high | header "city" resolves to PII field "city" |
| 35 | address1 | high | header "address" resolves to PII field "address1" |
| 36 | zip | high | header "zipcode" resolves to PII field "zip" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__receivable_new_receivable_summary_backup.csv6 columns4,962 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 22 | high | header "email" resolves to PII field "email" | |
| 26 | high | unlabeled column — sampled values parse as email addresses | |
| 34 | state | high | header "province" resolves to PII field "state" |
| 35 | city | high | header "city" resolves to PII field "city" |
| 36 | address1 | high | header "address" resolves to PII field "address1" |
| 37 | zip | high | header "zipcode" resolves to PII field "zip" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__receivable_other_refund.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal transactional identifiers, dates, and state/region codes. The 'province' column contains state names but is not personal address information per exclusion rules (it represents transaction location, not customer address).
azazie__receivable_other_refund_backup.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal transactional/operational fields (IDs, order numbers, timestamps, monetary amounts, tax codes). No PII fields detected. Columns like 'source' (country codes), 'country', 'province' are not personal addresses or location identifiers. Transactional timestamps and numeric IDs are skip fields per exclusion rules.
azazie__receivable_received.csv1 column521 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 11 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__receivable_received_backup.csv1 column796 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 12 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__receivable_remain_receivable_begin.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are financial/transactional data (order IDs, payment methods, currency, amounts). No PII fields present. Columns like 'abs_id' and 'taobao_order_sn' are internal identifiers, and 'pay_name' contains payment processor names, not personal data.
azazie__receivable_remain_receivable_begin_backup.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a financial transaction dataset with identifiers, payment methods, currency amounts, and timestamps. No PII fields present. Columns like abs_id, temp_id, party_id are internal identifiers. pay_name contains payment processor names, not personal identifiers. Dates are transactional timestamps, not DOB. All columns fall under financial/transactional data or internal IDs, which must be skipped per exclusion rules.
azazie__receivable_remain_receivable_end.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields present. All columns are internal transaction identifiers, monetary amounts, and payment methods. Columns contain order IDs (taobao_order_sn), payment processors (pay_name), currencies, exchange rates, and financial amounts — none constitute personal identifiable information per the defined schema.
azazie__receivable_remain_receivable_end_backup.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent transactional/financial data (order IDs, payment methods, currency values, amounts, dates) and internal identifiers. No names, addresses, emails, phones, or other personal data appear in the first 50 rows.
azazie__receivable_remain_receivable_over_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns contain only internal order IDs, timestamps, and numeric references. The data appears to be transactional records without personal customer information.
azazie__receive_payment_gc.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns map to PII fields. All columns are internal identifiers, transaction codes, or empty/default values (e.g., '0000-00-00', '0.00'). No personal data (names, emails, addresses, etc.) is present in the first 50 rows.
azazie__receive_temp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only numerical values and an order identifier. No PII fields (email, phone, name, address, etc.) are present in the visible data. The columns appear to represent transaction or order reference numbers and monetary amounts, which are not considered PII under the provided field definitions.
azazie__recharge_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction/operational data (recharge records). No PII fields are present. Columns like country_code, currency, and timestamps are internal business data, not personal PII. All columns are skipped per exclusion rules (company/business-related fields and timestamps).
azazie__recharge_order_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transactional identifiers and timestamps. No PII fields are present. All columns are internal IDs, order references, and timestamps which must be skipped per exclusion rules.
azazie__refund.csv1 column3,847 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 55 | fullName | high | [55] header 'CUSTOMER_USER_NAME', values are full names like 'Penny Gou' |
Notes: Only column 55 contains PII (fullName). All other columns are internal IDs, timestamps, financial amounts, statuses, or system flags — none contain personal identifiable information. No emails, phones, addresses, DOB, SSN, gender, or usernames are present.
azazie__refund_abandon.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction IDs, timestamps, and amounts. No PII fields are present. All columns map to skip categories: refund_abandon_id (internal ID), refund_id (internal ID), create_stamp (timestamp), action_user (username-like but likely internal system account), note (free text, not PII), total_amount (financial), currency (transactional), taobao_order_sn (external order reference but not PII).
azazie__refund_apply.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal transaction/operational IDs, timestamps, and flags. No PII is present. Columns like erp_refund_apply_id, project_name, party_id, refund_action, taobao_order_sn, and all timestamps/flags are internal references or operational metadata. No emails, names, addresses, phone numbers, DOB, SSN, passwords, usernames, or other PII fields are detectable.
azazie__refund_apply_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal transaction identifiers, numeric amounts, status codes, timestamps, and other operational metadata. No PII fields (names, emails, addresses, etc.) are present in the first 50 rows.
azazie__refund_apply_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only return/cancellation reason codes and timestamps. No PII fields are present. All columns are internal identifiers, reason codes, or timestamps which must be skipped per exclusion rules.
azazie__refund_auto.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns present. File contains only transaction IDs, timestamps, and error messages related to refund processing. All columns are internal system identifiers or status flags.
azazie__refund_balance.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal transaction identifiers, timestamps, flags, and amounts. No PII fields present.
azazie__refund_bonus_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal transaction IDs, numeric order codes, and status flags. No PII is present in the first 50 rows or in the visible structure. The columns 'abs_id', 'refund_id', 'dispatch_list_id' are internal numeric identifiers; 'amount_bonus', 'subtotal_bonus' are financial values; 'is_used' is a status flag. None map to PII categories.
azazie__refund_complaint_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, timestamps, and user identifiers with no PII fields. All columns are excluded per rules: abs_id (internal ID), refund_detail_id (internal ID), complaint_reason_id (internal ID), create_stamp (timestamp), action_user (internal username/identifier). No email, phone, name, address, DOB, SSN, password, or other PII fields present.
azazie__refund_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction/refund identifiers and operational flags (REFUND_DETAIL_ID, timestamps, product IDs, monetary values, status codes). No PII fields present. All columns map to internal business identifiers, numeric counters, or status flags.
azazie__refund_detail_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, flags, or non-PII metadata. No PII fields present.
azazie__refund_detail_tax.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are transactional fields (rates, fees, timestamps). No PII detected. The data represents order adjustments/refunds with numeric values and timestamps, typical of financial transaction logs.
azazie__refund_detail_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file containing internal business codes and timestamps. No PII fields are present — all columns are internal identifiers (REFUND_DETAIL_TYPE_ID), timestamps (CREATED_STAMP, LAST_UPDATE_STAMP, etc.), visibility flags (VISIBLE), and non-personal descriptions (DESCRIPTION). No emails, names, addresses, or other PII appear in the sample. This appears to be an operational reference table for refund types.
azazie__refund_order_fee.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only financial/tax transaction data (refunds, fees, taxes) and timestamps. No PII fields are present. All columns are numeric values, dates, or internal IDs.
azazie__refund_order_goods_fee.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal transaction IDs, timestamps, and financial amounts — no PII present. Columns like refund_detail_id, order_goods_id, order_id, and refund_id are internal numeric identifiers. Timestamps (EXECUTE_DATE, create_time, last_update_time) and monetary values (refund_amount, tax_ratio, etc.) are transactional data, not personal information.
azazie__refund_payment_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains payment/refund type metadata with no personal identifying information. Columns represent internal payment system codes, timestamps, and payment method names in multiple languages. No PII fields present.
azazie__refund_pdf.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, status flags, or checksums. No PII fields present in this dataset.
azazie__refund_percentage_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only configuration parameters and internal IDs. No PII fields are present. Columns such as config_id, party_id, country_code, min_day_interval, max_day_interval, refund_rate, is_delete, action_user, create_time, and last_update_time are all internal tracking fields, configuration settings, or timestamps that do not contain personally identifiable information. The action_user field contains short alphanumeric strings that appear to be system-generated usernames, not actual user identifiers.
azazie__refund_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only internal transaction IDs, status codes, timestamps, and system user references. No names, emails, addresses, or other personal identifiers appear in the first 50 rows.
azazie__refund_status_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This CSV contains only internal transaction identifiers and status codes (e.g., RFND_STTS_INIT, RFND_STTS_EXECUTED). No personal identifiable information (PII) is present in the visible columns or values. The data represents refund status tracking for order IDs.
azazie__refund_sync.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, transaction statuses, timestamps, and flags. 'action_user' appears to be a system username rather than a customer PII field.
azazie__refund_sync_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a JSON-like structure embedded within CSV rows, containing transaction/refund records without any personal identifiable information (PII) fields such as names, emails, phone numbers, or addresses. All visible fields relate to order IDs, refund amounts, currencies, payment methods, timestamps, and status codes. No columns map to the defined PII categories (email, phone, dob, names, addresses, ssn, password, username, country, gender, suffix, facebookId). The data represents operational transaction logs rather than customer personal data.
azazie__refund_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction/refund tracking metadata (refund types, timestamps, check levels). No PII fields present. All columns are internal identifiers, timestamps, or codes. No emails, names, addresses, or other personal data detected.
azazie__region.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be a reference table of geographic regions (countries, states, provinces) with identifiers, names, codes, and display metadata. No personal information present.
azazie__region_seo.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent geographical region data (region IDs, codes, names, states, cities, postcodes) and metadata (population, airport codes, flags, timestamps). These are internal location reference tables, not customer PII.
azazie__region_shipped_from_sz.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be an internal reference table with region IDs, timestamps, and status flags. All columns are internal identifiers or audit metadata.
azazie__region_tax.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only region tax information and no PII fields. All columns are related to tax configurations and regions, which do not contain any personal identifiable information.
azazie__region_tax_call_logs.csv2 columns29 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 8 | zip | high | header "zipcode" resolves to PII field "zip" |
| 9 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__relation_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal order identifiers and timestamps. No PII present in the first 50 rows.
azazie__remake_dispatch_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal dispatch tracking table with no PII fields. All columns represent internal identifiers, timestamps, and action metadata. No names, emails, addresses, or other personal data appear in the sample.
azazie__remake_dispatch_list_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns represent internal workflow identifiers, departments, and timestamps. Values contain only numeric codes, department names, and system users with no personal information.
azazie__remote_areas.csv3 columns6,341 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | fullName | high | [2] header 'shipping_name', values are alphanumeric strings that appear to be names |
| 3 | zip | high | [3] header 'zipcode_front', values are numeric postal codes |
| 4 | country | high | [4] header 'country', values are 2-3 letter country codes |
Notes: Only columns 2, 3, and 4 contain PII. Column 2 contains full names, column 3 contains zip codes, and column 4 contains country codes. All other columns are internal IDs or flags and do not contain PII.
azazie__repair_dispatch_principal.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (action logs). Columns include action_id, supplier_dispatch_list_id, operate_time (timestamp), principal (numeric ID), and action_user (username). No PII fields are present. Timestamps and internal IDs are excluded per rules. The 'action_user' column contains usernames, but these are internal system usernames (not public identifiers like email or social media handles), and are excluded as per the rule: 'Internal IDs: user_id, customer_id, account_id, record_id, household_id, member_id, dealer_code, star_id → skip (numeric/auto-generated identifiers are NOT usernames)'. While 'username' is a PII field type, this specific column is an internal system identifier, not a public-facing username. Thus, it is excluded.
azazie__replenishment_broken_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII found in the first 50 rows. The file appears to be an internal system log or data processing report containing only product IDs, inventory counts, and operational timestamps. No personal information such as names, emails, phone numbers, or addresses is present in the visible data.
azazie__replenishment_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, timestamps, and flags. No PII is present. Columns: abs_id (skip, internal ID), external_goods_id (skip, internal ID), add_time (skip, timestamp), update_time (skip, timestamp), action_user (skip, internal username), is_used (skip, flag).
azazie__replenishment_lock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system logs or actions (abs_id, create_time, update_time, action_user, is_active). No PII fields are present. All columns are internal IDs, timestamps, user actions, and status flags.
azazie__replenishment_operation_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns are internal identifiers, product details, inventory status, timestamps, and operational logs. No email, phone, name, address, DOB, SSN, password, or username fields present.
azazie__replenishment_result.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, flags, or business/project metadata. No PII fields are present. The 'title' column contains product/project names in Chinese and English, not personal names. 'is_email' is a flag (1/0), not an actual email address. All other columns are numeric IDs, timestamps, or status codes.
azazie__report_bom_purchase_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal product identifiers, pricing data, and timestamps. This matches the expected structure of a product catalog database dump from Azazie (order/shipment records, product pricing, etc.).
azazie__report_bom_purchase_price_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/order identifiers, pricing data, and timestamps. No PII present.
azazie__report_books.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a report configuration/metadata file rather than customer PII data. Columns contain report names, types, cron schedules, and timestamps. No PII fields are present. All columns are internal system identifiers, report parameters, or timestamps which must be skipped per rules.
azazie__report_delivery_package_design_fee_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction and operational data (IDs, fees, timestamps). No PII fields are present. All columns are internal identifiers, monetary values, or timestamps, and should be skipped according to the exclusion rules.
azazie__report_delivery_tax_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be an internal transactional table containing product design fees, tax rates, and internal user identifiers (zhuo.zhang). All columns are either numeric values, internal IDs, or timestamps — none map to PII fields. The 'action_user' column is an internal username that should be skipped per exclusion rules (not a customer-facing identifier).
azazie__report_dispatch_in.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided data. The file appears to contain only internal IDs, dates, codes, and action metadata. All columns map to internal IDs, timestamps, or codes (e.g., 'ymd', 'cat_code', 'action_user', 'create_time', 'last_update_time'). No personal identifiers such as names, emails, phone numbers, addresses, or other PII fields are present.
azazie__report_in_inventory_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. This file is an inventory/purchase order table containing internal IDs, product attributes, pricing, inventory statuses, and timestamps. All 25 columns are operational/transactional data with no personal information.
azazie__report_in_inventory_detail_bak.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This is an inventory/purchase order table containing internal IDs, product/goods data, pricing, facility/container references, and timestamps. All 25 columns are non-PII operational data.
azazie__report_init_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. File contains transactional metadata (action types, timestamps, notes about tax calculations) with numeric IDs and date ranges. No names, emails, addresses, or other personal identifiers present in the sample.
azazie__report_inventory_change.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This is an inventory change/financial transaction log table with product, cost, order, and timestamp data only. All 26 columns are internal operational fields (IDs, dates, costs, quantities, statuses, currency).
azazie__report_new_receivable_conversion_az.csv5 columns2,693,592 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 21 | high | header "email" resolves to PII field "email" | |
| 27 | high | unlabeled column — sampled values parse as email addresses | |
| 32 | country | high | header "country" resolves to PII field "country" |
| 33 | state | high | header "province" resolves to PII field "state" |
| 34 | city | high | header "city" resolves to PII field "city" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__report_order_shipping_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal operational/tracking data (IDs, months, counts, prices, timestamps). No PII fields detected. Columns like id, setting_id, report_month, ship_month, external_cat_id, total_goods_number, total_price, shipping_total_goods_number, shipping_total_price, create_time, and last_update_time are all internal tracking or transactional data — no personal customer information present.
azazie__report_order_shipping_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns are internal IDs, timestamps, flags, or codes. 'action_user' appears to be a username but is likely an internal system user or test account (e.g., 'liwuxie'). Per exclusion rules, internal IDs and system flags are skipped.
azazie__report_purchase_cost_tax_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a product/category reference table with no PII fields. Columns include category names, tax rates, and timestamps, all of which are internal business data and do not contain any personal information.
azazie__report_refund_by_date.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a transactional dataset containing order IDs, dates, inventory IDs, monetary values, stock counts, and timestamps. No personal identifiable information (PII) fields are present. All columns are internal business metrics or system timestamps, which must be skipped per rules.
azazie__report_remain_receivable_base_az.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal transaction identifiers, monetary amounts, timestamps, or system flags. No PII fields (email, phone, name, address, DOB, SSN, etc.) are present. Columns like id, order_id, order_sn, transcation_time, and monetary amounts are all skip per exclusion rules.
azazie__report_remain_receivable_conversion_end.csv1 column320,234 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 20 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__report_remain_receivable_not_over_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file contains only a single column of order numbers (taobao_order_sn) with no PII fields. All values are order identifiers starting with 'ZZ' followed by numeric sequences. No email addresses, phone numbers, names, or other PII are present in the first 50 rows.
azazie__report_remain_receivable_not_over_order_part2.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a single-column file containing only order numbers (taobao_order_sn). No PII fields are present. The values are alphanumeric order identifiers, not personal data.
azazie__report_request.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, timestamps, status codes, or JSON parameters. No PII fields present.
azazie__report_request_to_oc.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, status flags, or JSON data structures with no PII. No emails, names, addresses, DOB, phone, or SSN present in sample.
azazie__report_request_todo.csv1 column27 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__report_requests.csv1 column57 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 10 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__report_returned_alternative_conversion_az.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns are internal identifiers, timestamps, transaction metadata, or financial data. No emails, phone numbers, names, addresses, DOB, SSN, passwords, or usernames are present.
azazie__report_shipping_return.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains operational metadata about scheduled report generation tasks (returns, categories, etc.). No PII is present — all columns are internal IDs, status flags, timestamps, and system notes. The 'action_user' field shows system account names, not real user identifiers.
azazie__report_temp_erp_0608_avg_cost.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields are transactional/order data (order IDs, product IDs, quantities, costs, timestamps). No personal identifiers present.
azazie__report_temp_erp_0608_inv_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file containing only transactional inventory data (order IDs, product IDs, quantities, costs, timestamps). No columns contain any PII fields. All columns are internal operational identifiers, numeric values, or timestamps, which fall under exclusion rules for company/business identifiers, internal IDs, financial/transactional data, and timestamps.
azazie__report_temp_erp_0608_purchase_cost_list.csv1 column247 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 20 | high | [20] header 'email', values contain @ signs confirming email addresses |
Notes: 44 columns total; this is an order/shipment line-item table. Only column 20 contains PII (customer email). Column 21 'first_email' has no sample values and is likely empty/unused. All other columns are order identifiers, product data, financial amounts, shipping carriers, timestamps, and internal flags — all skipped.
azazie__report_temp_erp_0608_transfer.csv1 column15 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | address1 | high | [5] header 'address', values contain full street address with city/state |
Notes: Only column 5 (address) contains PII. All other columns are internal IDs, timestamps, transaction codes, or flags. No emails, names, phones, DOB, or SSN present in the sample.
azazie__report_temp_erp_0623_new_receivable_record_az_ca.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, transaction codes, dates, currencies, and financial amounts. No PII fields are present. Columns like 'id', 'taobao_order_sn', 'start_date', 'end_date', 'source', 'project', 'currency', 'rate', 'receivable_yuan', 'receivable_usd', 'create_time', and 'last_update_time' are all internal operational or transactional data and do not contain any personal identifiable information.
azazie__report_temp_erp_0623_new_receivable_record_az_us.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, transaction codes, timestamps, or monetary values. The dataset appears to be order/shipment records rather than customer personal data.
azazie__report_temp_erp_ghtang_test.csv1 column498 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__report_temp_erp_ghtang_test_001.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product ID and color ID references with timestamps. No PII fields are present. All columns (id, external_goods_id, color_id, create_time, last_update_time) are internal identifiers or timestamps and should be skipped per exclusion rules.
azazie__report_temp_erp_inv_movement_begin.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, timestamps, product codes, quantities, and financial values. Columns containing company/business references, internal IDs, timestamps, product data, and transactional data have been skipped per exclusion rules.
azazie__report_temp_erp_inv_movement_end.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal inventory/operational data: IDs, timestamps, product codes, financial amounts, warehouse tracking. No names, emails, addresses, or other personal data appear in the first 50 rows.
azazie__report_temp_erp_inv_movement_in.csv2 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__report_temp_erp_inv_movement_out.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal inventory, order tracking, and logistics data (IDs, timestamps, product SKUs, quantities, amounts, warehouse locations, etc.). No personal customer data such as names, emails, addresses, or phone numbers is present in the first 50 rows.
azazie__request_express_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal tracking IDs, timestamps, network metrics, carrier URLs, and status flags. No names, addresses, emails, phones, or other PII appear in the first 50 rows.
azazie__request_express_monitor_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal tracking IDs, timestamps, HTTP status codes, network timing metrics, and system flags. The 'note' column contains non-PII Chinese text describing DHL operations.
azazie__reserve_candidate.csv0 rows
File structure
Notes: This is a list of order IDs only (numeric values), no structured columns or PII present. The file appears to be a simple enumeration of order identifiers from the Azazie database breach, with no additional data fields or personal information visible in the first 50 rows.
azazie__reserve_container_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, flags, and timestamps: id (numeric internal ID), container_id (numeric internal ID), inventory_switch/allocate_shipping_switch (flags), allocate_shipping_provider (internal code), create_time/last_update_time (timestamps). No personal or contact data present in this sample.
azazie__reserve_dispatch_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided data. All columns appear to be internal identifiers, status flags, and timestamps. No names, emails, addresses, or other PII fields are present in the visible data.
azazie__rest_time_statistics.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/timestamp data (break times, action users, party IDs). No PII fields are present. All columns are flagged for skip per exclusion rules (internal IDs, timestamps, counters).
azazie__result_01.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain product/vehicle identifiers, inventory numbers, and sales totals — no PII present. Columns like uniq_sku, external_goods_id, color, size, and inv_num are internal product codes and inventory counters. Sales totals (2_3_sale_total, avg_7_sale_total, etc.) are transactional data, not personal information.
azazie__result_02.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product SKU identifiers and internal tracking numbers with timestamps. No PII fields are present. The columns represent inventory tracking data (id, uniq_sku, in-transit quantities, and timestamps) rather than customer or personal information.
azazie__resync_to_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file containing order synchronization metadata from Azazie. All columns represent internal database tracking fields (table names, primary keys, sync flags, timestamps) with no PII present. The values are numeric order IDs and ISO timestamps, confirming this is purely operational data with no personal information exposed.
azazie__return_apply.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, status flags, financial amounts, or system references. No PII fields are present in this dataset.
azazie__return_apply_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all visible columns are internal transaction codes (return_shipping_method, express_code) and numeric IDs. No PII fields are present in the first 50 rows. The values are internal reference codes and do not contain personal information.
azazie__return_apply_detail.csv5 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 69 | fullName | high | [69] contains patterns like 'groom's name=qqq brides name=eee' |
| 70 | fullName | high | [70] contains patterns like 'groom's name=qqq brides name=eee' |
| 71 | fullName | high | [71] contains patterns like 'groom's name=qqq brides name=eee' |
| 196 | fullName | high | [196] contains patterns like 'groom's name=www brides name=eee' |
| 197 | fullName | high | [197] contains patterns like 'groom's name=www brides name=eee' |
Notes: Identified 5 rows with fullName patterns in thank-you card customization fields. All other columns appear to contain product details, pricing, and inventory codes with no PII.
azazie__return_apply_detail_back.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, product metadata, inventory statuses, and return logistics. No PII fields (names, emails, addresses, etc.) are present in the first 50 rows. Columns like 'return_apply_detail_id', 'order_goods_id', 'product_id', and 'goods_name' contain only internal reference numbers and product descriptions, not personal data.
azazie__return_apply_detail_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, flags, timestamps, or placeholder values. Columns like 'id', 'return_apply_detail_id', 'hr_item_id', and time/date fields contain system-generated data or default values, with no personal identifiable information present in the sample.
azazie__return_apply_export_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a structured CSV but contains only internal IDs (return_apply_id), export counters (export_times), and non-PII usernames (user) with timestamps. No PII fields (email, phone, name, address, etc.) are present. All columns are internal identifiers or operational metadata and must be skipped per exclusion rules.
azazie__return_apply_facility_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII present. All columns are internal IDs and flags: id (record ID), party_id (internal party reference), country_id (internal country code), facility_id (internal facility reference), use_default (binary flag). None of these contain personal information.
azazie__return_apply_notify.csv316 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__return_dispatch_update.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal identifiers and timestamps with no personal identifiable information (PII). All columns represent internal database tracking fields (dispatch serial numbers, size codes, print counts, deletion flags, and timestamps) which are not considered PII under the defined field types. No emails, names, addresses, phone numbers, dates of birth, or other PII fields are present.
azazie__return_dispatch_update_backend.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This is not a PII-containing file. The sample rows show only internal tracking fields (DISPATCH_SN, PRINT_COUNT, IS_DELETE, size metrics, timestamps). No personal identifiers, emails, names, or addresses are present. The data appears to be operational/logistics records for order fulfillment rather than customer data. All columns map to internal operational data and should be skipped per exclusion rules.
azazie__return_exception_request.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: None of the columns map to PII fields. All columns are internal identifiers, flags, timestamps, or product metadata. No emails, phone numbers, names, addresses, or other personal data are present in the sample.
azazie__return_exception_request_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns appear to be internal codes and flags (reason_id, reason_name, is_delete). None contain PII fields such as names, emails, addresses, etc. The content describes return reasons for orders and is purely operational/analytical. No PII columns to map.
azazie__return_fee_country.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and operational data (country_id, return_fee, timestamps, currency, party_id). No PII fields are present. All columns are marked for skip per exclusion rules (company/business references, internal IDs, timestamps).
azazie__return_fee_currency_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only currency exchange rates and timestamps. No PII fields are present. Columns map to internal exchange rate tracking (id, rate, currency codes, timestamps). All columns are excluded per rules (no email, phone, name, address, etc.).
azazie__return_goods_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal IDs, product codes, flags, timestamps, and non-personal metadata. The sample contains order identifiers, product SKUs, status flags, and audit timestamps — none constitute personally identifiable information per the defined schema.
azazie__return_goods_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, status flags, or product identifiers. No PII fields present. Columns like 'create_user' and 'update_user' contain system usernames, not actual customer usernames, and are skipped per rules.
azazie__return_label_express.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. Columns contain only internal order IDs (taobao_order_sn), tracking numbers, shipping carrier names, weights, timestamps, and user action flags. All values are non-personal transactional data.
azazie__return_label_pdf.csv0 rows
azazie__return_label_print_mission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided rows. The file appears to contain only logistics/shipment tracking data with order IDs, status codes, and JSON payloads describing carrier operations. No personal information such as names, emails, phone numbers, or addresses is present in the visible data.
azazie__return_label_print_mission_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This appears to be a structured CSV file, but all visible columns contain only internal tracking IDs, timestamps, and error messages. No PII fields are present in the first 50 rows. The data represents logistics order status updates and error handling for shipment labels, with no customer or personal information exposed.
azazie__return_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, status codes, timestamps, or system metadata. action_user_name appears to be a system username but is not considered PII under the exclusion rules as it lacks identifiable personal context.
azazie__return_not_in_warehouse_white_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only two columns: id and return_apply_id. Both appear to be internal identifiers (numeric auto-generated IDs) and do not contain any PII. Therefore, no PII columns are mapped.
azazie__return_order.csv9 columns4,802 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 7 | gender | high | header "sex" resolves to PII field "gender" |
| 8 | country | high | header "country" resolves to PII field "country" |
| 9 | state | high | header "province" resolves to PII field "state" |
| 10 | city | high | header "city" resolves to PII field "city" |
| 12 | address1 | high | header "address" resolves to PII field "address1" |
| 13 | zip | high | header "zipcode" resolves to PII field "zip" |
| 14 | phone | high | header "tel" resolves to PII field "phone" |
| 15 | skip | high | header "mobile" resolves to PII field "phone" |
| 16 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__return_order_goods.csv10 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | internal record ID column |
| 1 | skip | high | order ID - internal reference |
| 2 | skip | high | goods/product ID - internal reference |
| 3 | skip | high | product name - no PII |
| 4 | skip | high | product SKU - internal reference |
| 5 | skip | high | quantity ordered - transactional |
| 6 | skip | high | list price - transactional |
| 7 | skip | high | sale price - transactional |
| 8 | skip | high | carrier reference - internal logistics |
| 9 | skip | high | vendor/provider ID - internal reference |
Notes: CSV file containing order and product data. No PII fields detected - all columns represent internal order references, product details, pricing, and logistics information. The data appears to be transactional records rather than customer personal information.
azazie__return_order_goods_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No identifiable PII fields found. All columns appear to contain internal order identifiers, numeric references, and timestamps. No names, contact details, or personal identifiers present in the sample.
azazie__return_order_lock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a transactional log table with columns: lock_id (internal ID), create_time (timestamp), order_sn (order number), action_user (username), is_locked (status flag). All columns are non-PII per exclusion rules.
azazie__return_order_zero_amount.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (IDs, flags, timestamps, usernames). No PII fields are present. Columns map to: id (skip internal ID), return_apply_id (skip internal ID), is_handled (skip flag), action_user (skip internal username), create_time (skip timestamp), last_update_time (skip timestamp).
azazie__return_reason.csv1 column238 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | username | high | [6] header 'created_user', values are usernames (qymeng, yzhang) |
Notes: Only column 6 (created_user) contains PII (username). All other columns contain order IDs, SKUs, timestamps, and non-PII feedback codes. No emails, phone numbers, names, addresses, DOB, SSN, or passwords were found in the first 50 rows.
azazie__return_reason_with_functional_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns appear to contain internal categorization data and JSON structures describing product issues (color discrepancies, etc.). There are no visible PII fields such as names, emails, addresses, or other personal identifiers in the first 50 rows. The columns are purely descriptive and operational, mapping to product/service issues rather than customer personal data.
azazie__return_shipping_tracking.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal tracking IDs, timestamps, status flags, and carrier codes. No email, phone, name, address, DOB, SSN, password, or username fields present.
azazie__return_tracking_number_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order/transaction identifiers and timestamps. No PII fields present. All columns map to skip categories: order IDs, tracking numbers, timestamps, user identifiers (internal), and refund IDs.
azazie__returned_stock_intercept_condition.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII columns. All columns are internal identifiers, flags, timestamps, or non-personal metadata. Columns like 'key_word' contain product/style keywords, and other columns are audit fields (create_user, delete_user, timestamps, status flags). No email, phone, name, address, DOB, SSN, password, or username fields are present.
azazie__rewards_email.csv2 columns1 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | high | [1] header 'my_email', values contain '@' symbol | |
| 2 | high | [2] header 'friends_email', values contain '@' symbol |
Notes: Only 3 columns present; 2 contain emails. Other columns are non-PII (rewards email ID, coupon code, timestamps).
azazie__rma_track.csv2 columns45 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 16 | fullName | high | [16] header 'CUSTOMER_NAME', values are full names like 'Ragnhild Flatekval' and 'john shark' |
| 20 | phone | high | [20] header 'CONTACT_INFO', values are 10-12 digit numbers starting with '+47' (Norway country code) and others like '123456789' |
Notes: Only columns 16 (fullName) and 20 (phone) contain PII. All other columns are internal IDs, timestamps, status flags, product data, or usernames (non-PII). No emails, addresses, DOB, SSN, or passwords detected.
azazie__rma_track_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data appears to be a log of track attribute updates rather than a dataset containing PII fields. All entries describe updates to track attributes with values like 'null', 'Y', or empty strings, and do not contain any identifiable personal information such as names, emails, addresses, or other PII fields. No columns map to available PII types.
azazie__rma_track_attribute.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible columns appear to represent internal tracking attributes, product specifications, and status flags rather than personally identifiable information. The 'VALUE' column is empty for most rows, and textual entries like '机头' (head) and '后盖' (back cover) are product component labels. No emails, phone numbers, names, addresses, or other PII patterns are present in the sample.
azazie__rma_track_attribute_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product attribute metadata (names, descriptions, types, and allowed values). No PII is present. All columns are internal identifiers, timestamps, and static product specification data.
azazie__rma_track_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but none of the columns contain PII. The columns appear to be internal tracking fields (TRACK_TYPE_ID, timestamps, NAME, NOTE, CREATED_BY_USER_LOGIN). The NAME column contains internal codes like "V1" and "WARRANTY", not personal names. Therefore, no PII fields are present in this sample.
azazie__robes_order_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields are internal order IDs, statuses, timestamps, and internal user identifiers. No emails, names, addresses, or other PII appear in the first 50 rows.
azazie__role_has_permissions.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal permission/role mappings (permission_id, role_id). No PII fields present. All columns are internal IDs and should be skipped.
azazie__role_labels.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal group definitions (采购组, 物流组, etc.) with no PII. All columns are internal identifiers or timestamps and are skipped per rules.
azazie__roles.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a list of internal user/role definitions rather than customer PII. Columns 'name' and 'guard_name' contain role names and system identifiers, while 'is_supplier' is a boolean flag. Timestamps are internal records. No PII fields detected.
azazie__romeo_execute_log.csv5 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | [0] column name 'log_id' is an internal ID |
| 1 | skip | high | [1] column name 'script' is an internal script path |
| 2 | skip | high | [2] column name 'message' contains serialized PHP objects, not direct PII |
| 3 | skip | high | [3] column name 'message_type' is a system flag |
| 4 | skip | high | [4] column name 'datetime' is a timestamp |
Notes: This appears to be a system log file tracking inventory transactions. While usernames appear in the data (e.g., 'xmwang'), they are embedded within serialized PHP objects in the 'message' column and not directly accessible as PII fields. No direct PII columns (email, phone, address, etc.) are present in this sample.
azazie__rule_repositories.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a static list of static analysis tools and languages, not containing any customer or PII data. All columns represent tool names, language types, and timestamps — none map to PII fields. No emails, names, addresses, etc. are present.
azazie__rules.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal system metadata about size charts for products. No PII fields are present. Columns include IDs, checksums, JSON structures for size chart IDs, operator names, timestamps, and project names. All columns are non-PII per exclusion rules (internal IDs, timestamps, operational metadata).
azazie__rules_copy.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal system data (IDs, JSON rules, checksums, timestamps). No PII fields present. Columns like 'operator' contain system usernames, not customer PII.
azazie__rules_parameters.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains configuration rules for static code analysis, not customer or user data. All columns are rule identifiers, names, descriptions, parameter types, and default values - none contain PII. No mapping to PII fields is possible or appropriate.
azazie__rules_profiles.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII columns. All columns are internal metadata about Sonar rules (names, languages, IDs, timestamps). Columns like 'name' contain generic rule names ('Sonar way', 'PSR-2', 'Drupal') not personal names. Timestamps and IDs are internal system data.
azazie__rush_reason.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal status codes and descriptions (reason_id, reason_name, is_active). No PII fields are present. All columns are internal flags or identifiers and must be skipped per exclusion rules.
azazie__sa_assign.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system identifiers and operational metadata. No PII fields are present. Columns include IDs, codes, names of test entries, group rules, enable flags, sorting order, notes, action users (internal usernames), and timestamps. All columns are marked as skip per exclusion rules (internal IDs, timestamps, system flags).
azazie__sa_assign_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided rows. The data consists of internal process IDs, codes, and timestamps, with no personal or identifiable information present.
azazie__sa_assign_filter.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal administrative metadata (action_user, timestamps, filter parameters). No PII fields present. Columns like action_user contain only usernames (yzhang14, ghtang, test111, hyhuang1) which are internal system accounts, not customer identifiers. All columns are marked as skip per exclusion rules.
azazie__sa_assign_process.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, flags, timestamps, and generic notes. No PII fields present. Columns: id (internal ID), assign_id (internal ID), is_enable (flag), sort (ordering), note (generic), action_user (username-like but likely internal system user), create_time (timestamp), last_update_time (timestamp). All are excluded by rules.
azazie__sa_assign_process_sort.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a system configuration or rule management table with no PII fields. Columns contain internal process IDs, rule names (in Chinese), parameters arrays, status flags, timestamps, and usernames that appear to be system/service accounts (yzhang14, test101, webService). No personal customer data is present in these first 50 rows.
azazie__sa_burster.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal rule definitions for product filtering, not customer PII. Columns are rule IDs, names, codes, parameters, notes, action users, and timestamps. No personal identifiable information present.
azazie__sa_filter.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a configuration/rules file, not customer data. Columns contain filter definitions and timestamps, no PII present. All columns are internal flags or metadata and should be skipped.
azazie__sa_group_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII fields. It appears to be a configuration or category table with internal codes, names, and timestamps. All columns are internal identifiers, flags, or audit timestamps, none of which contain personal information.
azazie__sa_group_rule_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal configuration/rule data. Columns are: id, group_rule_id, is_enable, note, action_user, create_time, last_update_time. No PII fields are present. action_user contains generic test/placeholder usernames (test101, test111, hyhuang1) that do not represent real users or valid PII. Timestamps and IDs are internal system metadata.
azazie__sa_group_rule_detail_burster.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product grouping metadata (IDs, category names in Chinese, parameter lists). No PII fields such as names, emails, or addresses are present. All columns map to internal business logic and are safely skipped.
azazie__sa_purchase_dispatch.csv1 column80,320 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 25 | username | high | [25] header 'action_user', values are alphanumeric strings that look like usernames |
Notes: This file appears to be order/shipment records from Azazie. Only column 25 (action_user) contains PII (username). All other columns are internal IDs, flags, timestamps, or product metadata — none contain email, phone, names, addresses, DOB, SSN, password, gender, suffix, or facebookId. No unstructured text detected; this is a structured CSV.
azazie__sa_purchase_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only internal IDs (group_code), timestamps (create_time, last_update_time), and user identifiers (action_user) that are not considered PII per the exclusion rules. No emails, phone numbers, names, addresses, DOB, SSN, or passwords are present in the first 50 rows.
azazie__sa_purchase_group_action.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII columns. All fields are internal system identifiers, timestamps, and process notes related to order allocation logic. There are no personal identifiers, contact details, or sensitive data in the visible columns.
azazie__sa_sort.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal system configuration records with no personal identifiable information. All columns represent system parameters, codes, and timestamps rather than customer or user data. No PII fields are present in this dataset.
azazie__sa_task.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file appears to be a log file containing system status and dispatch records, with no identifiable PII fields present. All columns represent internal system statuses, timestamps, and error messages without any personal information.
azazie__sale_list_28.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product SKU identifiers, quantities, and timestamps. No personally identifiable information (PII) is present in the visible columns or sample data. The columns represent internal product catalog data rather than customer or user information.
azazie__sales_cancel_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal category codes and timestamps - no PII present. All columns are internal flags or identifiers (cancel_category_id, category, created_stamp, update_stamp, action_user, visible) and should be skipped per exclusion rules.
azazie__same_batch_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified. File contains only internal identifiers (dispatch_sn) and status/timestamp data. All columns are excluded per rules: dispatch_sn is an internal ID, check_status and check_time are non-PII operational fields.
azazie__same_fabric.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a simple two-column CSV file listing fabric IDs and fabric names (in Chinese). No PII fields are present — fabric_name is a product attribute, not personal data. All columns are non-PII and should be skipped.
azazie__same_fabric_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, product descriptors, pricing, timestamps, and system actions. 'action_user' is a system username, not a human username, and is excluded per rules.
azazie__same_fabric_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and pricing data (id, fabric_id, store_id, unit_price). No PII fields are present. All columns are internal identifiers or transactional values and should be skipped per exclusion rules.
azazie__same_fabric_purchase_bill.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal transaction/timestamp identifiers (IDs, timestamps, status codes, amounts, usernames). No PII fields present. Columns like create_user / purchase_confirm_user are internal system usernames, not public identifiers.
azazie__same_fabric_purchase_bill_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers (ids) and no PII. All columns are internal IDs and should be skipped per rules.
azazie__same_fabric_store.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only store identifiers (store_id, store_code) and no PII fields. All columns are internal identifiers and should be skipped.
azazie__same_fabric_supplier_reconciliation_lock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. All columns are non-PII: abs_id (internal ID), created_stamp/updated_stamp (timestamps), fabric_store_id (internal ID), action_user (username-like but internal), purchase_bill_id (internal ID), is_locked (flag), type (categorical code). No PII fields present.
azazie__sample_auto_unshelve.csv1 column0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | country | high | [1] header 'country', values appear to be country codes or names |
Notes: Only column 1 (country) contains PII. All other columns are internal IDs, product data, timestamps, status flags, or operational metadata — these are skipped per exclusion rules.
azazie__sample_auto_unshelve_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in this structured CSV file. All visible columns appear to be internal IDs, order identifiers, and timestamps, with no personal or sensitive data present in the first 50 rows.
azazie__sample_convert_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers (abs_id, dispatch_sn), user identifiers (action_user), and timestamps (created_time, last_update_time). None of these map to PII fields per the exclusion rules. The values in action_user appear to be usernames but the column name does not explicitly indicate it, and the context does not confirm these are actual user logins. Without clear PII mapping evidence, we must skip this column.
azazie__sample_delete_sync_temp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII is present. The columns 'id' and 'dispatch_sn' are internal identifiers, and 'created_time' and 'last_update_time' are timestamps, all of which must be skipped per the exclusion rules.
azazie__sample_dispatch_recharge.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/tracking data (IDs, actions, timestamps, amounts). No PII fields (names, emails, addresses, etc.) are present. All columns are internal identifiers, transaction flags, or timestamps — none qualify as PII under the defined schema.
azazie__sample_dress.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/operational data (dress IDs, SKU codes, colors, timestamps). No PII fields are present. All columns map to internal IDs, product attributes, or timestamps which are excluded by rules.
azazie__sample_dress_attrs.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/order metadata fields (IDs, weights, limits, colors, prices) — no PII. All columns are internal IDs, numeric attributes, or flags, which per rules must be skipped. No email, name, address, or other personal data is present.
azazie__sample_dress_au_material.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only material/product specifications (material IDs, names, units, pricing). No PII fields are present. All columns are internal product data and should be skipped.
azazie__sample_dress_au_material_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product/material specification table with no personal identifying information. Columns contain internal IDs, material dimensions, dosages, and cost figures. No PII fields detected.
azazie__sample_dress_batch_lend.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, status flags, timestamps, or product metadata. No PII fields (names, emails, addresses, etc.) are present in the sample data.
azazie__sample_dress_batch_lend_copy1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, product codes, or status flags. No PII fields detected.
azazie__sample_dress_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a quality check / feedback table for dress orders (azazie). All columns are internal flags, notes, timestamps, or numeric IDs. No PII fields present. Columns like 'check_user' contain system usernames, not customer PII.
azazie__sample_dress_design.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/manufacturing metadata (dispatch codes, material costs, workflow users, timestamps). No PII fields are present. All columns represent internal operational data, identifiers, costs, flags, and timestamps — none map to email, phone, name, address, DOB, SSN, password, username, gender, suffix, or facebookId per the provided field types. Columns like customer, preparer, inputter are numeric internal IDs (skip). Timestamps (preparer_stamp, input_stamp, audit_stamp) are excluded per exclusion rules. No PII detected.
azazie__sample_dress_file.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a metadata file for dress images and does not contain any PII fields. All columns relate to file identifiers, paths, and timestamps, which are internal operational data and not personal information.
azazie__sample_dress_lend.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal operational identifiers or status flags (sd_lend_id, external_goods_id, provider_id, timestamps, statuses, usernames for internal processes). No PII fields present. The usernames (request_username, lend_username, return_username) appear to be system/internal account handles rather than customer identifiers, and company/factory names are business entities not personal addresses.
azazie__sample_dress_lend_AZ.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, timestamps, statuses, or company/factory names that do not contain personal identifiers. Fields like 'request_username' and 'lend_username' appear to be system-generated usernames rather than actual personal usernames.
azazie__sample_dress_lend_VB.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, status codes, or company/facility names. Values in columns like 'request_username' and 'lend_username' appear to be system/internal usernames rather than actual user identifiers. No emails, phone numbers, addresses, DOB, or SSN present.
azazie__sample_dress_lend_az.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, company/business names, timestamps, or status codes. No PII fields present. Columns like 'request_username' and 'lend_username' appear to be internal system usernames rather than customer PII based on context and values. All columns either map to internal IDs, company/business entities, timestamps, or status flags, which must be skipped per exclusion rules.
azazie__sample_dress_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/order identifiers and status flags. No PII fields are present. All columns map to internal product IDs, dispatch codes, and status indicators which are not personally identifiable information.
azazie__sample_dress_loan.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal business/process identifiers, timestamps, and status flags. No PII fields present. Columns containing words like 'company' or 'factory' are explicitly excluded by rules. 'username' columns here are internal system usernames, not customer identifiers.
azazie__sample_dress_material.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a materials/products price list with no personal identifiable information (PII). Columns describe fabric types, units, pricing, and usage flags — all business/product data. No customer or user data present.
azazie__sample_dress_material_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal product/order identifiers (dispatch_sn, material_id), dosages, pricing, and provider codes. No personal identifiable information (PII) is present in the first 50 rows. Columns like 'provider' and 'memo' contain non-PII operational data. This appears to be an inventory/order management table rather than customer data.
azazie__sample_dress_not_retire_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. All columns appear to be internal identifiers (abs_id, dispatch_sn), user action flags (action_user, is_delete), and timestamps (created_time, last_update_time). These are excluded per policy rules for internal IDs and timestamps.
azazie__sample_dress_not_retire_style.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction IDs, action users, status flags, timestamps, and country codes. No PII is present in the first 50 rows. All columns are internal identifiers, timestamps, or status flags, which per rules must be skipped.
azazie__sample_dress_order_manage.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data appears to be a log or transactional table from an order/shipment system, containing only internal order identifiers, tracking numbers, timestamps, and status flags. There are no columns containing personal identifiable information (PII) such as names, emails, addresses, phone numbers, dates of birth, SSNs, passwords, or usernames. All visible fields are internal operational data (e.g., order_id, tracking numbers, status flags, timestamps). Therefore, no PII columns could be mapped.
azazie__sample_dress_order_memo.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only memo IDs, order IDs, memo text, user identifiers, and timestamps. None of these columns contain PII fields. The memo text appears to be internal notes or test entries, and the memo_user field appears to be internal usernames or test accounts, not actual user identifiers. All columns are internal IDs or timestamps and should be skipped.
azazie__sample_dress_relet.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This is a simple table with four columns: sd_relet_id, sd_lend_id, parent_sd_lend_id, and times. None of these columns map to PII fields as they appear to be internal identifiers and counters. All values are numeric and represent relationships or counts rather than personal information.
azazie__sample_dress_reserve_control.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This is a structured CSV file with three columns (dispatch_sn, update_stamp, update_user, forbidden_reserve, memo) but contains NO PII. All values are internal transaction IDs, timestamps, user IDs, and boolean flags. The update_user field contains alphanumeric strings that appear to be internal system accounts or job identifiers (e.g., 'yzhang', 'cronJob'), not actual usernames or personal names. No email addresses, phone numbers, names, addresses, or other PII fields are present in any column.
azazie__sample_dress_retire_rules.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The columns contain only internal IDs, timestamps, counters, and status flags. No email addresses, phone numbers, names, addresses, DOB, SSN, or passwords are present in this sample.
azazie__sample_dress_stat.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational statistics (abs_id, stat_date, not_returned_count, shipped_count, stat_rate, last_update_time). No PII fields are present. All columns are internal IDs, timestamps, counters, or rates and should be skipped per exclusion rules.
azazie__sample_dress_time_sync.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns are internal IDs (order numbers, timestamps, flags). The 'email_is_sended' column is a status flag, not an email address.
azazie__sample_dress_ups_shipping_time.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (region_id), shipping times, and timestamps. No PII fields are present. All columns are marked as skip per the rules (internal IDs and timestamps).
azazie__sample_inv_setting.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/inventory IDs and timestamps. No PII fields are present in the visible data. Columns are purely operational identifiers (external_goods_id, notify_number, action_user) and timestamps (create_time, last_update_time). All columns fall under exclusion rules for internal IDs and timestamps.
azazie__sample_inv_setting_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, timestamps, or numeric counters (id, external_goods_id, inv_safe_days, suggest_inv_safe_days, action_user, create_time, last_update_time). These are excluded per rules for internal IDs and timestamps.
azazie__sample_lend_detail.csv1 column1,342 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | high | [3] header 'lender', values contain @ sign email addresses (e.g. yingminxing@tetx.com) |
Notes: Internal inventory/dispatch log table. Most columns are operational: IDs, action codes, order numbers, timestamps, flags. Only column 3 contains PII (an email address).
azazie__sample_lend_detail_summary.csv1 column900 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 8 | high | [8] header 'lender', values contain '@' and valid domain formats |
Notes: Only column 8 (lender) contains PII (email addresses). All other columns are internal IDs, order numbers, timestamps, counters, or empty placeholders — none contain personal data.
azazie__sample_reserve_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, and numeric codes with no PII characteristics. No email, phone, name, address, or other personal data present in the first 50 rows.
azazie__sample_summary.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All 12 columns are internal operational/inventory data: IDs, status codes, timestamps, counters, and internal remarks. No PII fields present.
azazie__sample_sync.csv2 columns15,745 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | username | high | [3] header 'action_user', values match known internal usernames (qymeng2, jjwang, cjwan) |
| 4 | skip | high | [4] header 'action_note', contains codes and mixed sample references (e.g., 'ussample', 'USA', JSON fragments) |
Notes: Only columns containing PII or actionable identifiers are mapped. Column 4 (action_note) contains status codes, location hints, and JSON fragments, not personal data.
azazie__sample_sync_temp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file is not a structured table of PII; it contains JSON-encoded return reason notes embedded within a CSV-like structure. There are no columns that directly map to PII fields. The JSON strings inside the 'data' column contain customer feedback about dress fit and quality, but no identifiable information such as names, emails, or addresses is exposed in the visible sample rows. Further parsing of the JSON content would be required to extract any potential PII, but it is not present in this sample.
azazie__sample_upload.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (IDs, timestamps, product codes, status flags). No PII fields are present. All columns are marked as skip per exclusion rules (abs_id is an internal ID, created_stamp is a timestamp, external_goods_id is a product identifier, full_code is a product code, action_user is likely an internal username but lacks PII, sample_name is a product sample name, status is a flag).
azazie__sampling_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal transactional table (likely order/shipment rates) with no PII fields. Columns are identifiers (id, provider_id), numeric rate, type code, username (action_user), and timestamps. All columns are either internal IDs, numeric values, or non-PII timestamps — nothing maps to email, phone, name, address, DOB, SSN, etc. The username column (action_user) contains system user identifiers, not customer-facing usernames, and is excluded per rules.
azazie__sampling_rule_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. File contains only internal rule IDs, rate changes, and timestamps. All columns are internal IDs, numeric values, or timestamps that fall under exclusion rules (internal IDs, transactional data, timestamps).
azazie__scheduling.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal scheduling/operation IDs, dates, and numeric codes related to order processing and factory workflow. No names, emails, addresses, phones, or other PII fields present in the sample.
azazie__schema_migrations.csv0 rows
File structure
Notes: The provided data appears to be a list of numeric IDs or version numbers rather than a structured dataset with columns. There are no visible delimiters, headers, or repeated patterns that would indicate a CSV or similar format. The values are sequential numeric identifiers (1, 2, 1153, 1200, etc.) which do not represent any PII fields. Since this is unstructured data without any apparent structure or PII content, we classify it as unstructured with no column mappings.
azazie__sd_goods_id_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal system identifiers and timestamps. Columns 'abs_id', 'origin_goods_id', 'changed_goods_id', 'is_in_use', 'action_user', and 'action_time' are all internal operational fields. No PII is present in this sample.
azazie__sd_inventory_item.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only inventory management data (item IDs, statuses, dispatch codes). No PII fields are present. All columns are internal operational identifiers or inventory flags, which must be skipped per exclusion rules.
azazie__sd_inventory_item_AZ.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only inventory and shipment tracking data (sd_item_id, external_goods_id, inventory_status, dispatch_sn, quantity_on_hand, available_to_promise). No personal or identifiable information is present. All columns are internal product identifiers, statuses, and quantities — none map to PII fields. Therefore, no columns are included in the PII mapping.
azazie__sd_inventory_item_VB.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/inventory identifiers (sd_item_id, external_goods_id) and operational status fields (inventory_status, dispatch_sn, quantity_on_hand, available_to_promise). No PII fields are present. All columns are mapped to skip per exclusion rules (internal IDs, product data, transactional counters).
azazie__sd_inventory_item_az.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory identifiers (sd_item_id, external_goods_id) and status codes (inventory_status, dispatch_sn, quantity_on_hand, available_to_promise). No PII fields are present. All columns are internal operational data and should be skipped per exclusion rules.
azazie__sd_inventory_item_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields present. File contains internal action logs with numeric IDs, action types, user identifiers (not usernames), and timestamps. All columns map to skip categories (internal IDs, timestamps).
azazie__sd_inventory_item_history_AZ.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file is purely transactional/audit logs with no PII present. Contains only internal IDs (abs_id, sd_item_id), action codes (action_type), usernames (action_user), and timestamps (action_time). No emails, phone numbers, names, addresses, DOB, SSN, or other PII fields are present in the sample.
azazie__sd_inventory_item_history_VB.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal action logs with numeric IDs and user identifiers. Columns 'abs_id', 'sd_item_id', 'action_type', 'action_user', and 'action_time' are all internal tracking fields or timestamps — no PII is present. The 'action_user' values appear to be internal system usernames, not customer PII.
azazie__sd_inventory_item_history_az.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns identified. The file contains only internal transaction IDs (abs_id, sd_item_id), action codes (action_type, action_user), and timestamps (action_time). These are all operational tracking fields with no personal data.
azazie__sd_inventory_summary.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only inventory/product data fields: sd_summary_id (internal ID), external_goods_id (product SKU), total_amount (price), stock_quantity, available_to_lend, and location_seq_id (warehouse location). No PII fields are present. All columns map to skip categories (internal IDs, product data, transactional data).
azazie__sd_inventory_summary_AZ.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory data (stock IDs, quantities, locations). No PII fields are present. All columns are internal IDs, numeric values, or location codes — none map to personal data categories. This matches the breach context of an e-commerce operational database dump with no customer PII exposed in this particular file.
azazie__sd_inventory_summary_VB.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory/operational data (stock IDs, quantities, location codes). No PII fields present. All columns map to internal IDs, counters, or location codes — these are excluded per rules.
azazie__sd_inventory_summary_az.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only inventory/product data (IDs, quantities, locations). No PII fields present. All columns are internal identifiers or operational metrics.
azazie__section321_rules_setting.csv8 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__section321_rules_setting_history.csv298 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__seed_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, codes, flags, and timestamps. The file appears to be order/shipment records with no customer personal data exposed.
azazie__seed_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal IDs, status flags, timestamps, or product metadata. The sample shows shipment/order tracking data from Azazie, with no customer personal information exposed in these 15 columns.
azazie__seed_shelve_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a metadata table listing database dumps, not actual customer PII. Columns are: id, rows, columns, update_time, update_user. No PII fields present.
azazie__self_purchasing_1688_match_link.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product catalog CSV from Azazie containing only product metadata (IDs, colors, sizes, URLs, etc.). No PII fields are present — all columns are internal product identifiers, vendor links, or inventory attributes. Columns like 'id', 'external_goods_id', 'color', 'size', 'provider_id', 'link', 'home', 'provider', 'note', and 'product_id' are all non-PII business data.
azazie__self_purchasing_1688_match_link_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product/offer metadata with no personal information. Columns include IDs, colors, sizes, provider links, and action logs — none map to PII fields. All columns are skipped per rules (internal IDs, product data, timestamps).
azazie__self_purchasing_1688_product.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is not PII data. The file appears to be a product image mapping table with columns: id, product_id, name (image identifier), and value (image file path). No personally identifiable information is present in the first 50 rows.
azazie__self_purchasing_1688_sku.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in first 50 rows. File contains only product inventory data (SKU codes, colors, sizes, prices, image paths). No personal identifiers present.
azazie__self_purchasing_account.csv2 columns9 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header 'account', values include alphanumeric strings and email-like entries |
| 3 | fullName | high | [3] header 'resource_owner', values are non-numeric strings that appear to be names or identifiers |
Notes: 12 columns total, 2 contain PII. Columns 0 (id), 1 (app_key), 4 (member_id), 5 (aliId), 6 (refresh_token), 7 (refresh_token_timeout), 8 (access_token), 9 (expires_in), 10 (group), and 11 (last_update_time) are internal IDs, tokens, timestamps, or flags and should be skipped.
azazie__self_purchasing_goods_order_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. File contains only internal product/sku identifiers (external_goods_id, taobao_order_id, product_id, sku, provider) with no personal data. All columns map to internal business/system identifiers or empty values.
azazie__self_purchasing_goods_order_mapping_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in this structured CSV file. The columns contain only internal order identifiers (dispatch_sn, taobao_order_id), product/sku codes, numeric IDs, and action timestamps. The action_user field contains usernames (ywji, xmma, mfchen1), but these appear to be system/internal user accounts rather than customer PII. No emails, phone numbers, names, addresses, DOBs, SSNs, or passwords are present in the first 50 rows.
azazie__self_purchasing_logistics.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be order identifiers (id, bill_no), logistics company names (company_name), status flags (status), and order IDs (order_id). These contain only internal transaction references and carrier service names, with no personal information such as names, addresses, emails, or phone numbers.
azazie__self_purchasing_logistics_in.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/tracking data (IDs, timestamps, user actions). No PII fields present. All columns are internal IDs, timestamps, or system user identifiers and must be skipped per exclusion rules.
azazie__self_purchasing_order_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The data appears to be transactional records of product orders/skus with no personal identifiers present. Columns map to product details, quantities, and pricing.
azazie__self_purchasing_order_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order/transaction records: order IDs, timestamps, buyer IDs (b2b account codes), order status fields, amounts, and shipping fees. No PII fields (names, emails, phones, addresses, DOB, SSN, etc.) are present in any column.
azazie__self_purchasing_scanned_dispatch_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/tracking data: IDs, internal actions, and status flags. No PII fields are present. Columns: id (internal record ID), bill_no (transaction ID), dispatch_sn (tracking code), action_user (username), action_time (timestamp), status (state). All are non-PII per exclusion rules.
azazie__self_purchasing_suppliers.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and group names. No PII fields are present. Columns: id (internal ID), provider_id (internal ID), group (non-PII group identifier). All columns are marked as skip per rules.
azazie__self_purchasing_suppliers_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only audit log data (id, provider_id, timestamps, user identifiers, and operations). All columns are internal system identifiers or timestamps and do not contain any PII fields. The 'created_user' column appears to be internal user accounts (e.g., 'ywu', 'yzhang', 'ylzheng') and not customer usernames or emails.
azazie__send_email_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. The 'email' column header is misleading — values are internal obfuscated order/reference IDs (e.g. LP6361507173, ZZ9468028844), not actual email addresses. All other columns (sel_id, type, send_time, status, message) are internal operational fields: IDs, event types, timestamps, status flags, and log messages.
azazie__send_mails.csv2 columns6 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | skip | high | [4] order_sn — transactional order identifier, non-PII internal ID |
| 6 | high | [6] content column contains embedded email addresses (morty.wang@i9i8.com, jacky.hu@i9i8.com) |
Notes: This is an email campaign/notification log table. Columns email_id, batch_id, status, message, order_sn, subject are metadata. The 'content' column [6] embeds customer emails and names inline within marketing message bodies. Names (Kin, ttt, jacky hu) appear alongside emails but are embedded in unstructured content, not in dedicated firstName/lastName columns. The create_time [7] and last_update_time [8] are timestamps — skip. Only the email addresses in the content field are reliably extractable PII.
azazie__send_mails_batch.csv1 column3 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | high | [5] header 'outbox_email', values are valid email addresses |
Notes: Only column 5 (outbox_email) contains PII - valid email addresses. All other columns contain internal batch IDs, template IDs, status codes, user placeholders, and timestamps which are skip fields per rules.
azazie__send_mails_template.csv2 columns2 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | high | [3] contains placeholder {user_email} indicating email field | |
| 4 | fullName | high | [4] contains placeholder {user_name} indicating full name field |
Notes: Only columns with placeholders for user_email and user_name contain PII. Other columns are template IDs, subjects, content templates, and timestamps.
azazie__seo.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal system identifiers, URLs, timestamps, and content metadata. Columns like 'operator' contain system usernames, not user PII. Timestamps (create_time, last_update_time) and flags (is_delete) are non-PII operational data.
azazie__seo_url.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/SEO metadata (keywords, URLs, descriptions) and operational timestamps. No PII fields are present. All columns map to skip categories: internal IDs, product descriptions, timestamps, flags, and unstructured content.
azazie__separates_action_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal numeric IDs and action_user values. The action_user field contains simple usernames (zhaoyong, xiaoguang.zhang, frankie.fu) but lacks sufficient context or PII attributes to reliably map to any PII category. All columns appear to be internal system identifiers and timestamps, with no email, phone, address, DOB, SSN, or other personal identifiers present. The JSON and array structures contain only numeric IDs with no human-readable PII.
azazie__separates_size_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains no PII fields. It appears to be a product inventory or pricing table with columns for an unspecified identifier (id), height measurement (height), size code (size), monetary value (value), and timestamps (create_time, last_update_time). No personal information is present in the visible data.
azazie__server_cost.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a configuration or cost metrics table from the database, not containing any personal identifiable information (PII). All columns represent internal system metrics (cost names and values) and timestamps, which are not PII according to the rules. No emails, phone numbers, names, addresses, DOB, SSN, passwords, usernames, or other PII fields are present.
azazie__service.csv1 column50 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | username | high | [4] header 'apply_username', values are alphanumeric strings that likely represent usernames |
Notes: Only column 4 (apply_username) contains PII. All other columns are internal IDs, statuses, timestamps, flags, or numeric codes that do not contain personally identifiable information per the exclusion rules.
azazie__service_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal service log identifiers, order references, status codes, and timestamps. No PII fields are present. Columns such as service_log_id, order_id, log_username appear to be internal system identifiers or generic usernames without personal information. All columns map to skip categories (internal IDs, flags, timestamps).
azazie__service_order_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain only internal order IDs, product SKUs, and status flags — no personal or sensitive data present in the first 50 rows
azazie__sfc_coverage_area.csv5 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | skip | high | area_id - internal identifier |
| 2 | zip | high | zipcode column with numeric postal codes |
| 3 | city | high | city column with location names |
| 4 | state | high | state column with Mexican state names |
| 5 | skip | high | country_id - internal identifier |
Notes: 50 rows shown, representing geographic area mappings. Contains zip codes, cities, and states for Mexico. No PII beyond location data which is already aggregated at area level. Timestamps and coverage flags are present but empty/unused in sample.
azazie__shareasale_transaction_detail_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All 11 columns are internal transactional/operational data: IDs, project codes, dates, order numbers, and financial amounts. This appears to be a commission/transaction reporting table with no personal information.
azazie__ship_company_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only shipping/carrier information (names, codes, timestamps). No PII fields are present. All columns are non-PII logistics metadata (carrier names, codes, sort order, status flags, creation/update timestamps). Per exclusion rules, company/business-related columns are skipped regardless of values.
azazie__ship_robes_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (order IDs, shipment flags, timestamps, user handles). No PII fields are present. Columns 'abs_id', 'order_id', 'is_shipped', 'action_user', 'create_time', and 'last_update_time' are all internal IDs, flags, or timestamps and must be skipped per exclusion rules.
azazie__ship_to_suzhou_dispatch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a two-column table with internal IDs and dispatch serial numbers. No PII fields are present. Columns are: id (internal customer/order ID), dispatch_sn (internal shipment reference). All values are non-PII identifiers and therefore skipped per exclusion rules.
azazie__shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns represent internal shipment identifiers, timestamps, status codes, weights, and cost values. No email addresses, phone numbers, names, addresses, DOB, SSN, or other PII fields are present.
azazie__shipment_backups.csv3 columns7 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | high | [3] header 'consignee', values appear to be names |
| 4 | address1 | high | [4] header 'address', values appear to be street addresses |
| 5 | phone | high | [5] header 'tel', values are 10-digit numbers matching US phone format |
Notes: Columns 0,1,2,6,7,8,9,10,11,12,13 are internal IDs, timestamps, flags, or transactional data — skipped per rules. Columns 3,4,5 contain full name, address, and phone number PII.
azazie__shipment_bill.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transactional data (bill_id, shipment_bill_name, shipment_bill_amount, timestamps). No PII fields present. Columns map to skip per exclusion rules (company/business references, internal IDs, timestamps).
azazie__shipment_bill_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction IDs, amounts, and timestamps. No PII fields present. All columns are skipped per exclusion rules (internal IDs, transactional amounts, timestamps).
azazie__shipment_cache.csv4 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__shipment_consumables.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only shipment/internal IDs and product SKUs. No PII is present. Columns map to internal shipment identifiers, SKU codes, and numeric IDs — all skip per exclusion rules.
azazie__shipment_daily_manifest.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, carrier/shipping codes, timestamps, and flags. 'destination' appears to be a formatted location string but lacks clear PII mappings (city/state/zip components are not isolated). All columns are skipped per rules (Company/Business references, internal IDs, timestamps).
azazie__shipment_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains shipment tracking IDs, process flags, and timestamps. Columns like 'attr_name' and 'attr_value' store internal process metadata rather than personal information. No names, emails, addresses, or other PII fields appear in the sample.
azazie__shipment_exception.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, status flags, timestamps, or internal notes. No PII fields are present. Columns like 'create_user' contain system usernames, not actual customer usernames or PII.
azazie__shipment_label_cancel_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file appears to be a log of server errors related to order updates, containing only error codes, messages, and timestamps. There are no PII fields present in the visible data.
azazie__shipment_label_print.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal shipment/transaction identifiers, timestamps, and operational flags. No PII fields are present in this dataset.
azazie__shipment_label_print_detail.csv17,309 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__shipment_manifest.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, status flags, timestamps, or technical identifiers (UUIDs). No PII fields present. Columns like id, shipment_id, shp_id, tracking_code, batch_id, scan_id, and URLs are internal tracking codes and system timestamps, which are excluded per policy.
azazie__shipment_modify.csv8 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | Internal shipment identifier (numeric auto-generated) |
| 1 | skip | high | Party/brand name (not personal PII) |
| 2 | skip | high | Order reference number (internal transaction ID) |
| 3 | skip | high | Shipping carrier service name (not personal PII) |
| 4 | skip | high | Creator username (internal system account) |
| 5 | skip | high | Timestamp (created_at style date/time) |
| 6 | skip | high | Free-form note/reason field (may contain mixed data) |
| 7 | country | high | Country names in values (美国, 英国, 法国, etc.), header is 'country' |
Notes: 8 columns total, only country contains PII. All others are internal shipment/tracking identifiers, timestamps, or system accounts. No email, phone, names, addresses, or other PII fields present in this dataset.
azazie__shipment_package.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only shipment IDs, weights, and references to other shipment IDs. No PII fields are present. All columns are internal identifiers or numeric values related to shipment logistics.
azazie__shipment_preprint.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only shipment tracking metadata with internal IDs, statuses, timestamps, and file paths. No PII fields (email, phone, name, address, DOB, SSN, etc.) are present in the header or sample rows. All columns map to skip categories: shipment_id (internal ID), status (flag), tracking_number (transactional code), file_path (system path), note (internal message), created_time / update_time (timestamps).
azazie__shipment_print_workload.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers (abs_id), timestamps (created_stamp), operator usernames, shipment IDs, facility IDs, and party IDs. No PII fields present in the first 50 rows.
azazie__shipment_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only shipment/transaction identifiers and timestamps. No PII fields are present. All columns map to internal IDs, flags, or timestamps and are skipped per rules.
azazie__shipment_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a static table of shipping methods and carriers - no PII present. All columns contain shipment IDs, carrier names, and flags. No personal or sensitive data fields are included.
azazie__shipment_weighed_by_user.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, shipment IDs, user logins, and timestamps. No PII fields are present. All columns are marked as skip per exclusion rules (internal IDs and timestamps).
azazie__shipped_from_suzhou_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is not a PII-containing file. The columns appear to be internal system flags, country identifiers, and numeric limits — no personal identifiers or sensitive data present. All columns map to skip categories (country_id, internal flags, numeric limits, timestamps).
azazie__shipped_from_suzhou_states_rule.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal reference IDs (states_id, country_id) and a status flag (is_used). No PII fields are present.
azazie__shipping.csv3 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 14 | fullName | high | [14] header 'contact_name', values appear to be personal names |
| 15 | skip | high | [15] header 'contact_email', values contain '@' symbol |
| 16 | skip | high | [16] header 'contact_phone', values are numeric strings of typical phone length |
Notes: 19 columns total, 3 contain PII. Columns 0-13 and 17-18 are internal shipping/carrier identifiers, flags, timestamps, or empty strings — skipped per exclusion rules. The breach context (Azazie) confirms these are shipping configuration records with contact details for logistics partners.
azazie__shipping_cycle.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file contains only order identifiers, order numbers, dispatch codes, timestamps, and a flag. No PII fields (names, emails, addresses, etc.) are present in the header or sample data. All columns are internal identifiers or operational metadata.
azazie__shipping_fee_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a pricing/range table with no PII fields. Columns are: id, party_id, country, lower_bound, upper_bound, is_delete, price, currency, create_time, last_update_time. All columns are internal business data or timestamps, no personal information present.
azazie__shipping_label_cache.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. File contains shipment tracking data with internal IDs, timestamps, and JSON payload metadata. No personal identifiers present.
azazie__shipping_method.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a shipping methods configuration table from Azazie. All columns contain internal business data (IDs, fees, descriptions, configuration JSON, timestamps). No personal identifiable information (PII) is present. All columns map to skip categories: internal IDs (sm_id, currency_id), internal flags (disabled, display_order), internal timestamps (last_update_time), and internal configuration structures (config).
azazie__shipping_method_area.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected. All columns contain internal shipment identifiers (sma_id), region codes (region_id), service method codes (sm_id, sm_area), and timestamps (last_update_time). No personal or sensitive data present in the first 50 rows.
azazie__shipping_method_fee.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only shipping/shipping cost metadata (carrier codes, fees, weights, timestamps). No PII fields are present. All columns map to skip per exclusion rules (company/business names, internal IDs, financial/transactional data, timestamps).
azazie__shipping_method_language.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only shipping method identifiers, descriptions, and timestamps. All columns fall under internal operational data or timestamps, with no personal information present.
azazie__shipping_tracking.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal tracking IDs, timestamps, status flags, or system-generated codes. This appears to be a logistics/shipping tracking table, not customer data.
azazie__shipping_tracking_memo.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns represent internal memo IDs, order IDs, tracking numbers, and operational timestamps/operators. None contain email, phone, name, address, or other personal data.
azazie__shipping_volume.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains logistics/shipping data with no PII fields. Columns include shipment IDs, shipping methods, dates, volumes, and action users (username-like strings), but none map to defined PII categories. All columns are skipped per rules (no email, phone, name, address, DOB, SSN, etc.).
azazie__shop_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/recommendation data structures and IDs. No personal identifiable information (PII) fields are present in the first 50 rows. All values are product IDs, arrays of product IDs, and internal metadata. Columns map to skip categories: internal IDs, product data, and timestamps.
azazie__shop_config_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a log of configuration changes rather than customer data. The columns contain timestamps, user identifiers, and JSON payloads representing configuration updates, but no direct PII fields such as names, emails, or addresses are present. The 'operator' field contains usernames which could be considered PII, but without additional context or visible email/phone patterns, it is safest to treat this as non-PII for mapping purposes. All columns map to skip per exclusion rules.
azazie__shopping_cart.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal product/order identifiers, pricing, timestamps, and flags. No PII fields (names, emails, addresses, etc.) are present in this dataset.
azazie__show_room.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided rows. All visible columns (show_room_id, room_name, project_name, create_time, last_update_time, order_sn, party_id, started_time, ended_time, email_flag) are either internal identifiers, timestamps, or flags. No email addresses or other PII fields appear in the sample data.
azazie__show_room_goods_favorites.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal identifiers, timestamps, flags, or technical codes (favorite_id, show_room_id, user_id, goods_id, real_goods_id, color_id, goods_size, device, create_time, last_update_time, is_delete). None map to any defined PII fields.
azazie__show_room_users.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, flags, timestamps, or role indicators (e.g., show_room_user_id, is_owner, create_time). No personal information such as names, emails, addresses, or phone numbers is present in the sample data.
azazie__showroom.csv2 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | skip | high | column 'track_status' contains status codes like FINISHED, TRACKING |
| 5 | skip | high | column 'remark' contains notes/comments, not PII |
Notes: This appears to be an order tracking/shipment status table. No PII columns detected - all values are numeric IDs, timestamps, status flags, and optional notes/comments. The 'remark' field contains free-text notes but no identifiable personal information.
azazie__showroom_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file appears to be a structured CSV without a header row. All visible columns contain only order identifiers, numeric IDs, status flags, timestamps, and parent references — no personal identifiable information is present in the first 50 rows. The columns are purely transactional/order management data.
azazie__similar_style_recommend.csv1 column2 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | [2] header is 'worker', but values are valid email addresses (e.g., yfliu@i9i8.com) |
Notes: This file appears to be an internal goods/products table with minimal PII. Only the 'worker' column contains email addresses. All other columns are internal IDs, flags, or timestamps and have been skipped per rules. The email column was misnamed but clearly contains valid emails.
azazie__simple_return_exception_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal operational data with no PII fields. All columns are internal IDs, timestamps, or system identifiers (id, taobao_order_sn, date, associate, stylist, reason, remark, party_id, admin_name, create_time, last_update_time). No personal identifiable information is present.
azazie__site_domain_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a configuration file listing domains and Shopify integration details. No PII fields are present; all columns contain system identifiers, API keys, and platform metadata. Columns like 'domain', 'short_name', and 'mix_name' are business identifiers, not personal data. The JSON payloads contain encrypted API secrets and store URLs, which are not mappable to any PII field per exclusion rules.
azazie__site_erp_goods_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product IDs and external product IDs, no PII present. All columns represent internal product identifiers and external references, which are not personally identifiable information.
azazie__size_chart.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains size chart metadata for products (dresses, shoes, etc.) with no personal identifiable information. Columns are purely descriptive (size_chart_id, size_chart_name, comment, etc.) and contain no names, emails, addresses, or other PII. All columns are skipped per rules.
azazie__size_chart_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/size data identifiers, timestamps, and flags. No PII present.
azazie__size_code_chart.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, product codes, and timestamps. No PII is present. All columns are marked for skip per rules (internal IDs, product data, timestamps).
azazie__size_consult.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, status flags, timestamps, or system codes. No PII fields (email, phone, name, address, DOB, SSN, etc.) are present in the first 50 rows. Columns like 'abs_id', 'dispatch_sn', and 'close_user' are internal system identifiers or user handles that do not qualify as PII per the rules.
azazie__size_consult_category.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only size measurement categories and descriptions — no PII fields present. Columns describe body measurements (Bust, Waist, Hip, etc.) and are internal product sizing metadata, not customer personal data. All columns are non-PII and should be skipped per exclusion rules.
azazie__size_consult_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This is a structured CSV file with no identifiable PII columns in the first 50 rows. Columns contain internal identifiers (abs_id, dispatch_sn), attribute names (attr_name), attribute values (attr_value), timestamps (create_stamp), and numeric sizes. None of these represent personal information such as names, addresses, emails, phone numbers, dates of birth, SSNs, passwords, usernames, gender, suffixes, or Facebook IDs. All columns are internal operational data or measurements.
azazie__size_property.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only measurement/attribute metadata (size properties) with no personal identifiable information. All columns are internal measurement codes, names, and timestamps — none map to PII fields. The 'name' column contains generic measurement terms like 'bust', 'waist', 'sleeve length', etc. No emails, names, addresses, or other PII appear in the sample.
azazie__skc_pre_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields appear to be product IDs, color codes, fabric types, timestamps, and action users (likely system accounts). The 'action_user' field contains non-personal system identifiers ('jacky.hu').
azazie__skc_sale_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal product/sales metrics and timestamps. No PII present. Columns like skc_id, external_cat_id, and external_goods_id are internal product identifiers. Sale numbers and timestamps are operational data, not personal information.
azazie__sku_color_cn_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product color metadata (color keys, English/CN names, timestamps). No PII fields are present. All columns are internal identifiers, product attributes, or timestamps which must be skipped per exclusion rules.
azazie__sku_grade.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product inventory table with no PII fields. Columns include product IDs (uniq_sku), grade level, stock number, and timestamps — all internal operational data. No emails, names, addresses, or other PII appear in the sample.
azazie__sku_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. File contains only product color and inventory data. All columns map to non-PII fields (colors, timestamps, inventory codes).
azazie__sku_not_in_finance_inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, SKU codes, and timestamps. No PII fields are present. All columns map to skip categories: id (internal ID), uniq_sku (product identifier), is_delete (flag), action_user (likely internal username but not a user-facing username), create_time and last_update_time (timestamps).
azazie__sku_on_sale_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only product SKU identifiers (SFxxx), timestamps, and flags related to sales status. No names, contact details, or other personally identifiable information present in the first 50 rows.
azazie__sku_out_of_stock_days.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, timestamps, and product SKU references. No names, emails, phone numbers, addresses, or other personal data present in the first 50 rows.
azazie__sku_sale_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/sales metrics (IDs, SKU codes, sale counts, timestamps). No PII fields present — purely operational inventory data. The breach context confirms this is an order/shipment database dump, but this specific file contains only product catalog statistics, not customer records.
azazie__sku_sale_number_statement.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product inventory records with SKU and sales data. No PII fields are present. All columns map to internal product IDs, dates, and transactional data which are excluded per rules.
azazie__slow_sales_rate_report_history_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be inventory/reporting data (IDs, dates, stock counts) with no personal information. This aligns with the context of an online retailer's database dump containing order/shipment records and operational tables.
azazie__smarty_shipping_print.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields appear to be internal shipment/tracking identifiers, timestamps, and logistics codes. No names, emails, addresses, phone numbers, or other personally identifiable information are present in the first 50 rows.
azazie__sorting_shelf.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal inventory IDs and timestamps. No PII fields (names, emails, phone numbers, addresses, etc.) are present in the first 50 rows. Columns represent shelf locations, serial numbers, sorting codes, user actions, and timestamps — all internal operational data. No columns map to any PII categories.
azazie__sow_task.csv7 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | firstName | high | [2] column name 'box_code_bz' suggests an internal code, but values are usernames; however, we see other columns with clear names like 'action_user' which contains actual usernames. Since this column has values like 'csc34', 'csc35', etc., these appear to be internal codes or identifiers, NOT usernames. Therefore, this column should be skipped as per exclusion rules for internal IDs. |
| 3 | firstName | high | [3] column name 'box_code_jh' suggests an internal code, similar to column 2. Values are also codes like 'csc33', 'csc34', etc. These are internal identifiers and should be skipped per exclusion rules. |
| 4 | username | high | [4] column name 'action_user' contains values like 'ff_test05', 'ff_test02', 'xiaoguang.zhang', etc. These are usernames used in the system. |
| 5 | skip | high | [5] column name 'is_deleted' is a flag indicating if a record is deleted. This is not PII and should be skipped. |
| 6 | skip | high | [6] column name 'bsd_ids' contains lists of numeric IDs. These are internal identifiers and should be skipped per exclusion rules. |
| 7 | skip | high | [7] column name 'create_time' is a timestamp. Timestamps should be skipped per exclusion rules. |
| 8 | skip | high | [8] column name 'last_update_time' is also a timestamp. Timestamps should be skipped per exclusion rules. |
Notes: The file appears to be a structured CSV with headers. Columns 0 (id) and 1 (box_code_bz) are internal identifiers and should be skipped. Column 4 (action_user) contains usernames. Columns 7 and 8 are timestamps and should be skipped. All other columns either contain internal codes or are flags and should be skipped as per the exclusion rules.
azazie__special_dress_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with 5 columns (external_goods_id, provider_id, provider_code, created_stamp, is_used). All columns appear to be internal identifiers, timestamps, or flags. No PII fields are present. The values are numeric codes, timestamps, and single-character status flags.
azazie__special_provider_goods_purchase_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional data (IDs, prices, timestamps) with no personal identifiable information. All columns are internal identifiers, product codes, monetary values, or timestamps — none map to PII fields. Therefore, no columns are mapped to PII categories.
azazie__special_provider_goods_purchase_price_history.csv1 column32 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | username | high | [5] header 'username', values are alphanumeric strings with length 4-6, typical for short usernames |
Notes: This appears to be an audit log tracking price and provider changes for products. Only column 5 (username) contains PII. Timestamps, action types, and numeric IDs are internal operational fields and do not contain personal information.
azazie__special_purchase_price_goods_style_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transactional data (IDs, prices, timestamps, operators). No PII fields are present. All columns are excluded per rules: abs_id and external_goods_id are internal IDs, provider_code and relation_id are non-PII codes, price is financial data, create_time and update_time are timestamps, and operator is an internal user identifier.
azazie__special_purchase_price_goods_style_price_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only operational/transactional data: IDs, price changes, timestamps, and operator actions. No PII fields are present. All columns are marked as skip per exclusion rules (internal IDs, financial/transactional data, timestamps).
azazie__special_sampling_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. This appears to be an internal tracking table with dispatch serial numbers, types, statuses, and timestamps. All columns are internal identifiers or audit timestamps and do not contain personal information.
azazie__special_track_goods_id.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, flags, counters, or operational data. 'party' appears to be an internal code ('VB'), not a personal identifier. No emails, phone numbers, names, addresses, DOB, SSN, or other PII fields present.
azazie__spu_sale_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal sales counters, timestamps, and internal IDs. No PII fields are present.
azazie__standard_product_unit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a product catalog or inventory listing for dresses and tops from Azazie. It contains product IDs, names, and associated party IDs, but no personal identifiable information (PII) such as names, emails, phone numbers, or addresses. All columns represent internal product data and timestamps, which are not considered PII according to the provided criteria. Therefore, no PII fields are mapped.
azazie__stat_workload.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file appears to be purely transactional order data with no PII fields present. All columns represent order identifiers, internal codes, and timestamps. No names, addresses, emails, or other personal identifiers are visible in the sample.
azazie__stat_workload_back.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified in the first 50 rows. The data appears to be transactional records with order IDs, user references (e.g., 'jozhang'), and timestamps, but no direct PII such as names, emails, or addresses are present in this sample.
azazie__stat_workload_bak.csv1 column5,297 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | username | high | [4] header 'action_user', values are alphanumeric strings resembling usernames |
Notes: CSV file with 200 rows, only column 4 contains PII (username). All other columns appear to be internal system identifiers, timestamps, and status codes that do not contain personal information. No emails, phone numbers, names, addresses, or other PII fields detected in the sample.
azazie__statistics.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only operational/statistical data (inventory, refunds, production metrics). No personal or identifiable information is present. All columns represent internal business metrics and counters.
azazie__statistics_7day.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a statistical summary file with no personal identifiable information (PII). All columns represent aggregate metrics such as counts, rates, and financial amounts related to inventory, production, and refunds. No customer or user data is present.
azazie__statistics_supplier_az.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, numeric counters, or operational metrics. No names, emails, addresses, phone numbers, DOB, SSN, passwords, or usernames present.
azazie__status_description.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only status codes and descriptions, no PII present. All columns represent internal order status tracking and are skipped per exclusion rules.
azazie__status_item.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a lookup table for inventory statuses with no PII. Columns contain status codes and timestamps only.
azazie__stock_change.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal inventory management data (IDs, SKUs, timestamps, operation descriptions). No PII fields present. Columns containing company/business references or internal identifiers are skipped per exclusion rules.
azazie__stock_plan.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, status flags, timestamps, or operational metadata. Columns like 'apply_user' and 'last_update_user' appear to be internal system usernames, not actual customer PII. No emails, phone numbers, names, addresses, or DOB fields present.
azazie__stock_transfer_request.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/tracking data (request IDs, statuses, timestamps, facility IDs). No PII fields are present. All columns are internal IDs, flags, or timestamps which must be skipped per rules.
azazie__stock_transfer_request_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, transaction codes, or status flags. The data shows order/shipment references from Azazie (e.g., erp_sku product codes, facility_id numeric IDs, request_detail_status flags). No personal customer data is present in this sample.
azazie__stock_transfer_task.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, timestamps, and operational flags. No PII is present. Columns: abs_id (internal ID), action_user (likely internal username), create_time (timestamp), bar_code (inventory code), last_update_time (timestamp), facility_id (internal facility ID), task_status (flag). All are non-PII per exclusion rules.
azazie__stock_transfer_task_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, status flags, or product codes. No PII fields present.
azazie__storage_goods_location.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal operational/inventory data: abs_id (internal ID), erp_sku (product SKU), facility_id (warehouse ID), location_seq_id (bin location), amount (quantity), created_time (timestamp), action_user (internal system username/operator code — not a personal identifier).
azazie__style.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product metadata table from Azazie's database containing style attributes like color options and display settings. All columns represent internal product catalog data (style IDs, category IDs, display orders, timestamps, prices) with no personal or identifiable information. No PII fields present.
azazie__style_gallery.csv5 columns22 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | url | high | [1] column labeled 'url', contains full URLs |
| 2 | fullName | high | [2] column labeled 'name', contains personal full names |
| 3 | state | high | [3] column labeled 'location', contains US state abbreviations and country names |
| 4 | address1 | high | [4] column labeled 'dressUrl', contains full URLs functioning as product addresses |
| 5 | skip | high | [5] column labeled 'images', contains JSON of image URLs - not personal address |
Notes: 50 rows shown, 5 columns identified as PII. Column 0 (id) is an internal numeric identifier and skipped. Columns 5+ contain image JSON and unstructured review text which are not PII.
azazie__style_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file appears to be a series of numeric arrays (likely internal group IDs) rather than structured PII data. No identifiable personal information (email, phone, name, address, etc.) is present in the visible sample rows. The format consists of a single column containing JSON-like arrays of numeric values, which do not map to any PII fields.
azazie__style_languages.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only product color and size attributes alongside internal IDs and timestamps. No personal identifiable information is present in the first 50 rows.
azazie__style_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified in the first 50 rows. The file contains only product attributes (color and hair length) for dress styles, with no personal information present.
azazie__submit_cancelled_dispatch_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present. Columns 'user_name' contains only short alphanumeric usernames without full names or emails; mapped to skip per policy. Timestamps and flags are non-PII.
azazie__supplier.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File appears to be a supplier list with only internal IDs (supplier_id), business names (supplier_name), and party IDs. All columns contain business entity references or internal codes, which are excluded by policy. No personal identifiers (email, phone, names, addresses, etc.) are present in the sample.
azazie__supplier_carton.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This appears to be a simple transactional or operational log table from Azazie. It contains only three columns: carton_id, catron_no, provider_id, action_user, create_time, and last_update_time. None of these columns contain PII data. The entries are internal identifiers, timestamps, and system users, all of which are non-personal and operational in nature. There are no names, addresses, emails, phone numbers, or other personally identifiable information in this dataset.
azazie__supplier_carton_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields found. All columns are internal IDs, product codes, timestamps, flags, or other non-personal operational data. 'action_user' appears to be an internal system/user code, not a username. Timestamps and numeric IDs are skipped per rules.
azazie__supplier_delivery.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All visible columns appear to be internal product/sku identifiers (id, sku), timestamps (delivery_time, create_time, last_updated_time), and a vendor name (supplier). No personal data such as names, emails, addresses, or phone numbers are present in this sample.
azazie__supplier_dispatch_action.csv1 column353 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | username | high | [3] header 'action_user', values are alphanumeric strings resembling usernames |
Notes: Only column 3 (action_user) contains PII - usernames. All other columns are internal system IDs, timestamps, and notes that do not contain personal data.
azazie__supplier_dispatch_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns contain internal IDs, status flags, timestamps, product details, and operational data. No names, emails, phone numbers, addresses, or other PII fields are present in the first 50 rows.
azazie__supplier_dispatch_list_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the first 50 rows. The file appears to contain only internal IDs, status codes, timestamps, and other non-PII operational data. All columns are mapped to skip per exclusion rules (internal IDs, timestamps, status codes).
azazie__supplier_dispatch_list_status_history.csv1 column27,772 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | username | high | [3] header 'created_by_user_login', values are alphanumeric usernames |
Notes: Only column 3 (created_by_user_login) contains PII - usernames. All other columns are internal IDs, statuses, and timestamps with no personal data.
azazie__supplier_dispatch_send_az.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, shipment/tracking codes, timestamps, status flags, or other non-personal operational data. The values shown are order IDs, warehouse codes, user logins (internal identifiers), timestamps, and shipping details. No emails, names, addresses, phone numbers, or other PII appear in the sample.
azazie__supplier_download_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present. Columns: id (internal ID), supplier_id (internal ID), download_method, download_type, created_time, last_update_time.
azazie__supplier_print_height.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with four columns: supplier_id, print_height, print_width, and dispatch_template. None of these columns contain personally identifiable information (PII). The values appear to be internal identifiers, measurements, and template codes related to print specifications, with no names, addresses, emails, phone numbers, dates of birth, or other PII fields present.
azazie__supplier_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal business identifiers, timestamps, or flags. No PII fields detected. Column 'cellphone' contains short numeric values that don't match phone number patterns (10+ digits), and 'contact_person' appears to be Chinese supplier contact labels rather than individual names. This is supplier/vendor data from Azazie's materials database, not customer PII.
azazie__supplier_rebate_account.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields appear to be internal accounting identifiers, timestamps, and numerical balances with no personal information.
azazie__supplier_reconciliation_lock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The provided data is purely transactional/administrative with no PII fields present. Columns represent internal IDs, timestamps, provider codes, user actions, and status flags. No names, emails, addresses, phone numbers, dates of birth, SSNs, passwords, or usernames are visible in the sample.
azazie__supplier_reconciliation_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided rows. The file appears to contain only log messages and error details related to payment processing and reconciliation, with no personal identifiable information exposed in the visible columns.
azazie__supplier_return_lock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields appear to be internal identifiers (lock_id), timestamps (create_time), order references (order_sn), user actions (action_user), and status flags (is_locked). No personal information such as names, emails, addresses, or other PII fields are present in the sample.
azazie__supplier_return_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns are internal IDs, quantities, status flags, timestamps, and user identifiers without personal information. The 'action_user' column contains short alphanumeric strings that appear to be internal system usernames rather than actual personal names or emails.
azazie__supplier_return_request.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns represent internal system identifiers, timestamps, transaction codes, inventory status flags, and product metadata. No personal information (names, emails, addresses, etc.) is present in the first 50 rows.
azazie__supplier_return_request_gt.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and tracking numbers for supplier returns. No PII fields are present. Columns map to internal IDs and GT serial numbers, which are skipped per exclusion rules.
azazie__supplier_return_request_item.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, counters, or transaction references. No PII fields are present.
azazie__supplier_return_request_status_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided rows. The file appears to contain only internal transaction IDs, timestamps, sequence numbers, and status codes, with no personal or sensitive information visible in the sample data.
azazie__supplier_set_inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal product/inventory data with no personal identifiable information (PII). Columns are all internal IDs, product codes, inventory statuses, timestamps, and user handles that do not correspond to any PII fields. No emails, names, addresses, phones, or other PII are present in the first 50 rows.
azazie__supplier_set_inventory_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only inventory and operational data with no personal identifiable information (PII). All columns are internal identifiers, status flags, timestamps, and user handles that are not PII. No emails, phone numbers, names, addresses, DOB, SSN, or other PII fields are present.
azazie__swatch_fabric.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product SKU and fabric type information. No PII fields are present.
azazie__sync_db_table_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a database schema / SQL command log, not actual customer data. The file contains SQL DELETE statements for maintaining goods_group table relationships. No PII is present in this sample; it's purely operational metadata. All columns represent internal database operations (IDs, table names, timestamps) and should be skipped.
azazie__sync_flyfish_cancel_queue.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with columns related to shipment logistics and API responses. None of the columns contain PII fields. The data includes IDs, timestamps, shipment references, sync statuses, and JSON response bodies that do not expose personal information. All columns fall under the exclusion rules for internal IDs, timestamps, and transactional data.
azazie__sync_init_inventory_to_pangu.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only inventory/product data fields (IDs, SKUs, stock levels, timestamps). No personal information present in the first 50 rows.
azazie__sync_jjs_france_order_status.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal operational/logistics fields: shipment IDs, order IDs, taobao order numbers, shipping status codes, consignment IDs, order status flags, facility IDs, and timestamps. None map to any PII field type.
azazie__sync_ops_log.csv30 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__sync_order_status_monitor_detail.csv0 rows
azazie__sync_order_status_monitor_total.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only operational timestamps and counters (start_time, end_time, succ_times, failed_times). No PII fields are present. Columns are all internal metrics and timestamps, which must be skipped per exclusion rules.
azazie__sys_access_pca.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This appears to be an export of PHP application routing configuration rather than a dataset containing personal information. The file lists URL paths, controller mappings, and permission structures for an admin interface — no actual PII fields are present in the data sample. All entries describe system functionality (e.g., '/admin/main/order', '/cron/weeklyDeal') rather than user records.
azazie__sys_account.csv4 columns723 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | high | [3] header 'acct_email', values contain '@' with domain structure | |
| 5 | password | high | [5] header 'acct_pswd', values are 32-character hex strings typical of MD5 hashes |
| 6 | username | high | [6] header 'acct_alias', values are short alphanumeric/username-like strings |
| 7 | fullName | high | [7] header 'acct_realname', values are non-English names in Chinese characters |
Notes: Only 5 columns contain PII: email, username, fullName, password. All other columns are internal IDs, flags, timestamps, or counters and must be skipped per exclusion rules.
azazie__sys_account_sso.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal operations table with no PII fields. Columns are IDs, internal user identifiers, SSO tokens, notes, timestamps, and status flags. All columns are marked as skip per rules (internal IDs, timestamps, flags).
azazie__sys_admin_action_log.csv1 column26,215 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header 'acct_alias', values are alphanumeric usernames (yzhang, yfliu, qzhong, etc) |
Notes: Only username column contains PII. Other columns are log metadata (timestamps, actions, IPs, server names) which are not personally identifying.
azazie__sys_department.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains department information (dept_id, dept_name, dept_code, dept_desc). There are no personal identifiable information (PII) fields present. All columns represent internal organizational data and should be skipped per exclusion rules.
azazie__sys_location_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal location and timestamp data. No PII fields are present. Columns are: id (internal ID), sys_location (internal location code), sys_location_cn (Chinese location name), is_display (flag), create_time (timestamp). All columns are non-PII per exclusion rules.
azazie__sys_permission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: The file is not structured data but rather a serialized PHP array representation of user permissions. It contains no actual PII fields, only system roles and access control definitions. The values are all permission strings and arrays, not personal data. Therefore, no columns map to PII fields.
azazie__sys_response_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only system operational logs (abs_id, sys_type, sys_location, connect_time, connect_flag, response_time, stat_time). No PII fields are present in any column — all entries are system identifiers, status flags, and numeric timing data. No email addresses, names, addresses, phone numbers, dates of birth, or other PII appear in the sample or implied structure.
azazie__sys_role.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields present. File contains role IDs, role names, timestamps, and project names - all internal system metadata with no personal information. All columns map to skip categories: role identifiers, timestamps, and system project names.
azazie__sys_role_facility.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and role identifiers (abs_id, role_id, facility_id) with no personal or identifiable information. All columns are internal system identifiers and therefore skipped per rules. No PII fields present.
azazie__sys_role_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only role/permission data (role_id, role_name, etc.) with no personal identifiable information. All columns map to internal system roles and timestamps, which are excluded by policy. No PII fields detected.
azazie__sys_role_party.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and role identifiers. No PII fields are present. Columns are: abs_id (internal record ID), role_id (role identifier), party_id (internal party/customer reference). All are non-PII according to exclusion rules for internal IDs.
azazie__sys_role_permission.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only role permissions data (serialized PHP arrays) with no personal identifiable information. All columns map to internal system permissions and access control structures, not user/customer PII. No emails, names, addresses, or other PII fields are present.
azazie__sys_role_supplier_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file appears to be a list of supplier IDs with timestamps, but contains no personal identifiable information (PII). All columns represent internal system identifiers and timestamps, which are excluded by policy.
azazie__sys_user_role.csv1 column2,302 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | username | high | [0] header 'username', values are alphanumeric strings |
Notes: Only column 0 (username) contains PII. Column 1 (role_id) is an internal identifier and must be skipped per rules.
azazie__sys_user_roleV2.csv1 column11 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | [1] header is 'username', values are alphanumeric strings that match typical usernames |
Notes: This file contains account records with usernames and role IDs. Only the username column maps to a PII field (username). The acct_id is an internal numeric identifier and should be skipped. The role_id is an internal code and should be skipped.
azazie__sys_whitelist.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is an IP address registry with columns: whitelist_id, ip, info, type. All columns are internal identifiers, network data, or descriptions — no PII fields present. The 'info' column contains location labels and notes, but no personal names, emails, or addresses. The 'type' column is empty for most rows. No PII mapping required.
azazie__system_operation_log.csv1 column483 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | medium | [1] header 'user_name', values are login handles like 'architect-test' |
Notes: This appears to be an admin activity/audit log table. Most columns are internal operational data (action logs, HTTP methods, IP addresses, timestamps, JSON input payloads). Column [2] user_id is a numeric internal identifier (skip). Column [7] ip is an IP address (skip per exclusion rules). Only user_name in column [1] qualifies as PII.
azazie__t1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This is an unstructured dataset with no identifiable PII columns. The file appears to contain only internal IDs and counters (abs_id, k1, num) with no personal information. The values are numeric identifiers and counters, not containing any email addresses, phone numbers, names, or other PII fields.
azazie__t_member.csv0 rows
azazie__tables_priv.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file is a MySQL privilege management dump, not customer PII. It lists database hosts, users, tables, and grant permissions. No personal information is present. All columns are system metadata (host, database name, user account, table name, grantor, timestamp, table privileges, column privileges). These are skipped per rules.
azazie__tag_csqc_check_item.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal IDs, flags, timestamps, or non-personal metadata. item_user_name appears to be a static placeholder name rather than actual customer data.
azazie__tag_csqc_check_result.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a tracking or audit log rather than customer data. Columns contain internal IDs (result_id, item_id), checker names (result_checker_name), timestamps (result_updated_time), status flags (result_type, result_status), and conflict indicators (check_conflict). No PII fields are present.
azazie__tag_csqc_check_task.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal task tracking records (task IDs, timestamps, statuses, and creator names). The 'task_creater_name' column contains only one non-PII value ('lmzheng') across all rows and does not represent a real personal name. All columns are internal metadata/timestamps and must be skipped per exclusion rules. No PII fields present.
azazie__tag_csqc_check_task_attr.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only three numeric identifier columns (abs_id, task_id, party_id). These are internal database IDs with no personal identifying information. No PII fields are present.
azazie__task_goods.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal identifiers, JSON payloads, status flags, or timestamps. Values contain product IDs, SKU codes, JSON snippets, and status strings with no personal information.
azazie__temp_az_purchase_proportion.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are transactional/financial data (dates, amounts, currency codes, internal IDs). No PII fields detected. This is consistent with order/shipment records from an e-commerce platform.
azazie__temp_delivery_allocate_costs_analysis.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields present. All columns are internal identifiers, transaction data, or numeric codes (e.g., zip codes are numeric placeholders, not real addresses). No emails, names, phone numbers, DOB, SSN, or passwords detected.
azazie__temp_supplier_evaluation_ranking_d30_result.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields are internal identifiers (abs_id, order_id), transaction codes (dispatch_sn), numeric flags (day30_refund_goods), and timestamps (shipping_time). No names, emails, addresses, or other personal data appear in the first 50 rows.
azazie__template_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a simple mapping of template IDs to filenames with no personal identifiable information. The columns 'template_id' and 'filename' contain only internal identifiers and file names, which do not constitute PII according to the exclusion rules.
azazie__temporary_storage.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (IDs, SKU codes, user action timestamps). No PII fields are present. Columns map to internal system identifiers and audit timestamps, which are skipped per rules.
azazie__test.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with columns: id, old_sku, new_sku, create_time. None of these columns contain PII. The 'id' column is an internal numeric identifier, 'old_sku' and 'new_sku' are product identifiers, and 'create_time' is a timestamp. According to the exclusion rules, internal IDs and timestamps must be skipped. Therefore, there are no PII columns to map.
azazie__test1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII fields are present. Columns 'id', 'date1', and 'date3' are internal identifiers and timestamps, which are excluded per rules.
azazie__test_api.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains internal tokens and session identifiers, not PII. No columns map to PII fields. The data appears to be system tokens and session data, not customer information.
azazie__test_excel.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and numeric counters with no meaningful headers or PII values. All columns appear to be internal identifiers (abs_id, id, a, b, c, x, etc.) with numeric sequences and placeholder zeros. No email addresses, phone numbers, names, addresses, DOB, SSN, or other PII fields are present in the sample. This is likely an internal reference table rather than customer data.
azazie__test_export.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII fields identified. All columns contain internal business codes, numeric totals, and date-period identifiers (e.g., provider_code, create_data, total). No names, contact info, IDs, or credentials present in the first 50 rows.
azazie__test_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product pricing table with no PII fields. Columns 'abs_id' and 'id' are internal numeric identifiers (skip). 'provider_code' appears to be internal vendor codes, not usernames or emails. All other columns are product pricing data.
azazie__test_stock.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains inventory data (stock levels, SKU codes, timestamps) with no personal identifiable information. All columns represent product identifiers, inventory counts, and timestamps — none map to PII fields.
azazie__threshold_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a configuration table with no PII fields. Columns contain internal system settings, tokens, and timestamps. All columns map to skip per rules (internal IDs, timestamps, internal flags).
azazie__threshold_config_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a configuration log table with no PII fields. Columns contain internal system settings (abs_id, config_key, config_value), timestamps (update_time), and user actions (action_user, action_note). No personal identifiable information is present.
azazie__ticket.csv1 column15 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | [1] header 'username', values are alphanumeric strings used as login identifiers |
Notes: Only column 1 (username) contains PII. All other columns are internal IDs, timestamps, status flags, or empty placeholder values and must be skipped per exclusion rules.
azazie__ticket_department.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns relate to department metadata (dept_id, dept_name, dept_description, created_stamp, is_supplier) and contain internal organizational data only. No personal or sensitive information present in this sample.
azazie__ticket_message.csv1 column56 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | username | high | [3] header 'username', values are alphanumeric strings used as login identifiers |
Notes: Only column 3 (username) contains PII. All other columns are internal IDs, flags, timestamps, or unstructured content. No emails, names, addresses, or other PII fields are present in this sample.
azazie__ticket_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal tracking IDs and timestamps. All columns are internal IDs or timestamps and do not contain any PII data. The columns 'provider_id' and 'ticket_num' are internal identifiers, and 'action_user' and 'action_time' are operational logs without personal information.
azazie__ticket_ttype.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a non-PII data file containing transaction type codes and descriptions. All columns appear to be internal codes and descriptive text in Chinese, with no personal identifiable information present. The file appears to be a lookup table for transaction types rather than containing customer or user data.
azazie__time_zone.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only two columns: time_zone_id and Use_leap_seconds. Neither column contains any personal identifiable information (PII). The values appear to be internal configuration flags for time zone settings and leap second usage. No PII fields are present.
azazie__time_zone_name.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only timezone names and numeric IDs. No PII fields are present. The data appears to be a reference table for timezone mappings and does not contain any personal or sensitive information.
azazie__time_zone_transition.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only three columns: Time_zone_id, Transition_time, and Transition_type_id. All values appear to be numeric IDs and timestamps with no PII content. The Transition_time values are large negative/positive integers that likely represent Unix timestamps or internal codes, not dates of birth. No email addresses, names, addresses, or other PII fields are present in the visible data.
azazie__time_zone_transition_type.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains timezone metadata with numeric IDs and timezone offsets. No PII fields are present — all columns are internal timezone identifiers and offsets (e.g., Time_zone_id, Transition_type_id, Offset, Is_DST, Abbreviation). No emails, names, addresses, or other personal data appear in the first 50 rows.
azazie__tmp_20201002_d30.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file containing product category statistics (month, category name, external category ID, shipping numbers, return numbers). No PII fields are present in any row. All columns represent product categories, IDs, and sales/returns metrics — none contain personal information such as names, addresses, emails, etc.
azazie__tmp_20201125_az_beihuo.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal product identifiers, inventory counts, timestamps, and sales metrics. Columns like id, uniq_sku, goods_name, external_goods_id, external_cat_id, cat_name, color, size, last_7_days_sale, last_2_week_sale, last_30_days_sale, zs_in_transit_num, zs_in_transit_order_sns, zs_on_hand, create_time, and last_update_time are all internal operational or product-related data with no personal information.
azazie__tmp_20201125_pp_beihuo.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product inventory data (SKU, quantities, sales, timestamps). No PII fields detected. Columns include identifiers (id, uniq_sku), product attributes (cat_name, goods_name, color, size), availability counters, and timestamps — all internal operational data with no personal information.
azazie__tmp_20201126_pp_in_transit.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file appears to contain only internal order/shipment identifiers (order_sns), SKU codes, and timestamps. No names, addresses, emails, or other personal data are present in the first 50 rows.
azazie__tmp_20201126_pp_inv.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product inventory data with SKU codes, quantities, and timestamps. No PII fields are present. All columns map to internal product/sku identifiers, availability counts, and system timestamps which are explicitly excluded by policy.
azazie__tmp_c_attr_goods_filter.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product attribute table from Azazie (e.g., dress occasion, shoe style). All columns are internal product metadata or flags (attr_pid, attr_id, cat_id, project_name, goods_nos, is_delete, last_update_time, same_attr_id, attr_name, attr_values, is_show). No PII is present. Columns like 'attr_name' and 'attr_values' describe product characteristics, not customer data.
azazie__tmp_c_attr_goods_filter_azazie.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product attribute data (e.g., product IDs, attribute types, values). No PII fields present. Columns like attr_pid, attr_id, cat_id, project_name, goods_nos, is_delete, last_update_time, same_attr_id, attr_name, attr_values, and is_show are all internal product metadata and should be skipped.
azazie__tmp_c_goods_no_filter.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product indexing data (goods_index, goods_id, project_name) with no personal or identifiable information. All columns represent internal product identifiers and the retailer name, which do not qualify as PII under the defined rules.
azazie__tmp_date.csv0 rows
File structure
Notes: free-form text with no consistent delimiter structure; appears to be metadata or placeholder lines rather than tabular data
azazie__tmp_dispatch_sale_rank.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a metadata or audit log table, not containing any PII fields. Columns are: id, note, action_user, create_time, last_update_time. All columns are internal identifiers, actions, or timestamps — none map to PII categories. No emails, names, addresses, or other sensitive data present.
azazie__tmp_eoi_20220210_001.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent order/transaction data (order IDs, statuses, timestamps, amounts, fees, source countries, currencies). No PII fields are present. These are internal business records, not customer personal data.
azazie__tmp_eoi_20220210_002.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent order/transaction metadata (order IDs, statuses, timestamps, amounts, fees, source/currency codes). No PII fields present. Columns like taobao_order_sn are internal order identifiers, not user identifiers.
azazie__tmp_fix_sku_size.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product attributes (sizes, colors, measurements) and internal system metadata. No PII fields are present. Columns map to product characteristics and system timestamps/status flags.
azazie__tmp_goods_display_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII present in the first 50 rows. The file contains only product color names and identifiers, which are not considered personally identifiable information. All columns appear to be product catalog data (goods_id, sales_order flags, project name, color names) with no personal data fields.
azazie__tmp_jjs_country_refund_gather.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, financial/transactional data, or company codes. The 'country' column contains numeric codes rather than country names.
azazie__tmp_oglc_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal inventory/ERP data columns (SKU codes, financial amounts, location IDs). No PII fields are present. All columns map to skip categories: erp_sku (internal product ID), oglc_amount/glc1_sum_amount/diff (financial values), location_seq_id (internal location identifier).
azazie__tmp_order_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order IDs, order serial numbers, Taobao order serial numbers, region names, and goods IDs. There are no PII fields present. All columns are internal order identifiers, transaction references, or product codes — none map to personal data categories.
azazie__tmp_order_status.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only order identifiers and status codes with no personal identifiable information. All columns (order_id, order_sn, taobao_order_sn, order_status, pay_status) are internal transaction identifiers or status flags and do not map to any PII fields.
azazie__tmp_transfer_rejected_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a two-column file containing only order serial numbers and flags. No PII fields are present. The 'order_sn' column appears to be an internal order identifier (numeric), and 'flag' is a status marker (single character). Both columns are non-PII per the exclusion rules for internal IDs and status flags.
azazie__tmp_transfer_return_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a two-column CSV with no PII. Column 0 is an internal numeric ID (service_id) and column 1 is a status flag (S). Both columns are non-PII per exclusion rules.
azazie__tmp_transfer_supplier_return_request.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is not a typical PII file. It contains only two columns: `gt_order` (what appears to be an order ID or reference number) and `flag` (a single character 'S'). There are no personal identifiable information fields present in this file. The values appear to be internal identifiers and status flags, which according to the exclusion rules must be skipped.
azazie__today_sales_goods_avg_cost.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product IDs and average prices — no PII fields. It is purely product/transactional data and should be skipped for PII analysis.
azazie__toll_code.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only internal IDs (abs_id), postal codes (post_code), and destination codes/names (dest_code, dest_name). These are geographic identifiers without personal identifiers.
azazie__toll_region.csv5 columns0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | state | high | [4] column named 'state_code', values are state/region codes |
| 5 | city | high | [5] column named 'city', contains city names |
| 6 | skip | high | [6] column named 'airport_code', contains airport codes (non-PII) |
| 7 | zip | high | [7] column named 'postcode_begin', contains beginning postcode ranges |
| 8 | zip | high | [8] column named 'postcode_end', contains ending postcode ranges |
Notes: This appears to be a reference table of geographic regions and postal code ranges, not direct customer PII. Columns contain region identifiers, state codes, city names, airport codes, and postcode ranges. Only state and city map to PII fields; postcode ranges are treated as zip-level data.
azazie__tracker_group_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and timestamps. No PII fields present. Columns: abs_id (internal ID), group_code (group identifier), group_leader_id (leader ID), tracker_id (tracker ID), action_user (username), create_time (timestamp), last_update_time (timestamp). All columns are marked as skip per exclusion rules.
azazie__tracker_provider_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational identifiers and timestamps. No PII fields are present. All columns map to skip categories: abs_id and provider_id are internal IDs, tracker_name is a numeric code, is_delete is a flag, action_user appears to be a username but is likely an internal system user (not a customer), and all date/time fields are non-DOB timestamps. No emails, phones, names, addresses, DOB, SSN, or other PII are visible in the sample.
azazie__tracking_hook.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data appears to be a JSON-like structure embedded within a CSV format, but the actual content consists of tracking information for packages. There are no identifiable PII fields such as names, emails, phone numbers, addresses, dates of birth, SSNs, passwords, usernames, or other personal identifiers present in the visible data. The data primarily contains logistics order numbers, tracking numbers, carrier details, tracking statuses, messages, timestamps, and other operational tracking details. Therefore, no PII columns can be mapped from this dataset.
azazie__tracking_hook_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains logistics/tracking information in JSON format within a CSV structure. No PII fields are present — all columns are internal IDs, tracking references, timestamps, and JSON payloads describing shipment status. The JSON contains location strings (city/state) but these are not personally identifying as they represent delivery destinations rather than customer addresses.
azazie__tracking_hook_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains logistics order information with tracking details. All columns are internal identifiers, timestamps, and JSON tracking data. No PII fields are present. The tracking_info column contains nested JSON with locations but does not include any personal identifiers such as names, addresses, or contact information.
azazie__tracking_hook_new.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal identifiers and timestamps. No PII fields are present. Columns like 'id' and 'logistics_order_sn' are internal IDs, while 'create_time' and 'last_update_time' are timestamps which must be skipped per rules. No emails, names, addresses, or other PII appear in the sample data.
azazie__tracking_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain only internal shipment/tracking IDs, numeric tracking numbers, and timestamps - no PII present. The data represents logistics tracking records with no customer-identifiable information.
azazie__trackingnumber_printed.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be a shipment tracking table with internal IDs, tracking numbers, HTML label content, return flags, timestamps, and user identifiers. All columns are either internal IDs, operational data, or non-PII tracking information.
azazie__transfer_apply.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. This is an inventory/warehouse movement log with facility IDs, order IDs, status codes, and timestamps — all internal operational data.
azazie__transfer_apply_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, flags, or inventory tracking fields. No PII present. Columns like 'enter_user' appear empty in sample and would contain internal system user references, not customer PII. The dataset represents inventory/order mapping tables from Azazie's operational database, not customer records.
azazie__transfer_bill_archive.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a log or metadata file listing database dumps/archives, not customer PII. Columns contain IDs, types, filenames, timestamps — all internal operational data. No PII fields detected.
azazie__transfer_bill_file.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (transfer IDs, file metadata, timestamps). No PII fields present. All columns are internal IDs, flags, or timestamps which must be skipped per exclusion rules.
azazie__transfer_bill_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain shipment/logistics data (IDs, airway bills, document references, timestamps). No PII fields are present. Values are internal codes, document filenames, dates, and status flags.
azazie__transfer_label_print.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains logistics and shipping tracking data (print IDs, carrier codes, tracking numbers, timestamps, paths). No PII fields detected. All columns represent internal shipment identifiers, paths, status messages, and timestamps. No names, emails, addresses, or other personal data present in the first 50 rows.
azazie__transfer_label_print_detail.csv1,483 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__transfer_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal operational fields (IDs, states, timestamps, flags). No PII present. The 'apply_user' and 'action_user' columns contain usernames, but they are internal system accounts, not customer PII, and should be skipped per rules. The file appears to be order/shipment tracking data from Azazie, with no customer personal information exposed.
azazie__transfer_order_auto_create.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, flags, timestamps, or inventory metadata. No PII present in the first 50 rows.
azazie__transfer_order_scan_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns identified. All visible fields are internal IDs (order_id, uniq_sku), status flags (is_deliver, scan_num), timestamps (create_time, last_update_time), and user identifiers that do not expose personal data (action_user appears to be internal system usernames). No emails, phone numbers, names, addresses, or other PII are present in this sample.
azazie__transfer_rule.csv1 column3 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 7 | high | [7] header is 'rule_value' but values are valid email addresses; this is a PII email column despite ambiguous name |
Notes: Only column 7 contains PII (emails). All other columns are internal transfer rule IDs, timestamps, flags, and numeric identifiers — none contain personal data. The file appears to be a warehouse inventory transfer rule configuration table unrelated to customer PII.
azazie__translation_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The file appears to be a structured database export containing product attributes, descriptions, and metadata. No PII fields (names, emails, addresses, etc.) are present in the visible rows. All columns contain product-related data such as goods details, attribute names/values, colors, styles, and other non-personal information. Therefore, no PII columns can be mapped.
azazie__truncation_delivery.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, shipping/tracking codes, timestamps, flags, and internal notes. The 'action_user' field appears to be a system username but lacks sufficient context to be reliably mapped to 'username'. Given the exclusion rules and sample values, no columns map to PII fields.
azazie__tt_crontab.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains scheduler/cron job definitions with no PII fields. All columns are internal system metadata (IDs, names of tasks, cron expressions, timestamps, execution metrics). No personal or sensitive data present.
azazie__tt_excel_01.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal IDs, flags, timestamps, or non-PII codes. 'id' is a numeric internal identifier, 'uniq_key' appears to be a generated key, 'is_delete' is a flag, 'a' and 'b' are product/sku codes, 'c' is a constant product category, 'action_user' is a system identifier, and 'create_time'/'last_update_time' are timestamps — all excluded by rules.
azazie__tt_excel_01_20210317.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII columns. All columns are internal IDs, timestamps, and non-PII flags. Columns 0 ('id'), 1 ('a') are internal IDs. Columns 17 ('action_user') and 18-19 ('create_time', 'last_update_time') are timestamps. The rest are empty or non-PII fields.
azazie__tt_excel_01_20210318.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, action users, timestamps, or empty fields. Columns 'id' and 'a' are internal identifiers; 'action_user' and timestamp fields ('create_time', 'last_update_time') are non-PII metadata. Columns 'b' through 'o' and 'note' appear empty in the sample and contain no discernible PII.
azazie__tt_excel_01_20210321.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is an internal operations / audit log table (id, action codes, timestamps). Columns 'a' and 'b' appear to be internal reference codes, not customer PII. All columns are internal IDs, action flags, or timestamps — no email, name, address, phone, or DOB data is present. Per exclusion rules, columns like 'id', 'a', 'b', and timestamp fields are skipped.
azazie__tt_excel_02.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, codes, timestamps, or system metadata. Columns 0-3 contain numeric IDs and product codes, columns 17-19 contain system actions and timestamps. No email, phone, name, address, DOB, or other PII fields present in the sample.
azazie__tt_excel_03.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns appear to be internal IDs, flags, timestamps, or product-related data. Columns 0-21 contain identifiers (id, uniq_key), deletion flags (is_delete), numeric codes (a, b), product attributes (c, d), session tokens (e), counters (f, g), and timestamps (create_time, last_update_time). No emails, phone numbers, names, addresses, DOB, SSN, passwords, usernames, or other PII fields are present.
azazie__tt_excel_03_tmp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, product data, timestamps, or flags. No PII present in the first 50 rows. The columns include order identifiers, color options, handles for tracking systems, order status flags, and timestamps.
azazie__tt_excel_04.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, product codes, action metadata, and timestamps. Columns 3 ('c') and 4 ('d') contain product colors and sizes, which are not PII.
azazie__tt_excel_04_02_assign.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, batch identifiers, timestamps, or action metadata. No PII fields present. Columns like 'id', 'batch_id', 'dispatch_list_id', 'provider_code', 'create_time', and 'last_update_time' are operational/internal fields and do not contain personal information. 'action_user' contains system user 'WebService' which is not a personal username.
azazie__tt_excel_04_02_tmp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal IDs, batch identifiers, timestamps, status flags, and other non-PII data. No personal identifiable information (PII) fields detected in the first 50 rows. Columns like 'id', 'batch_id', 'dispatch_list_id', 'provider_code', and timestamps ('create_time', 'last_update_time') are internal system fields and do not contain PII.
azazie__tt_excel_04_tmp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/order identifiers, prices, measurements, timestamps, and system metadata. No PII fields present. Columns like id, external_goods_id, size, sale_price, xf_usage, xf_unit, lb_usage, lb_unit, action_user, create_time, and last_update_time are all operational and contain no personal information.
azazie__tt_excel_05.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, flags, timestamps, or numeric codes. The file appears to be an internal operational or logging table from the Azazie database, not containing customer personal data.
azazie__tt_excel_05_tmp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal identifiers, numeric values, or timestamps. No PII fields detected in the first 50 rows. Columns 'id', 'a', 'b', 'c', 'd', 'action_user', 'create_time', and 'last_update_time' contain internal IDs, numeric measurements, product codes, system user references, and timestamps respectively — none map to PII categories.
azazie__tt_link.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, flags, timestamps, or non-personal metadata. Columns like 'action_user' contain system roles ('WebService'), 'group_name' and 'link_name' are system labels in Chinese, and timestamps ('create_time', 'last_update_time') are non-DOB temporal markers. This matches expected internal tool/permission configuration tables from an e-commerce backend.
azazie__tt_sql.csv1 column107 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | emailText | high | free-text column with embedded emails (89/199 cells, 45% density) |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__uk_gross_profit_margin.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only transactional data (order IDs, shipment dates, product categories, monetary amounts, timestamps). No personal identifiable information (PII) fields are present. All columns are internal identifiers, dates, or financial values and are mapped to skip per exclusion rules.
azazie__uk_refund_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, shipment/transactional data, timestamps, or financial amounts. No PII fields are present in this structured data file.
azazie__uk_refund_gather.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal transaction identifiers, dates, shipment codes, and financial amounts. No personal identifiable information (PII) is present. Columns such as abs_id (internal ID), ship_date (transaction date), type (product code), shipment_goods_number (quantity), refund counters, monetary values, and update_time are operational/tracking fields and do not contain any customer PII. Therefore, no columns map to PII fields.
azazie__undercarriage_log_temp.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields appear to be internal IDs, timestamps, and status codes. The 'action_user' field contains only short alphanumeric strings that do not resemble usernames or personal identifiers.
azazie__unfamiliar_color.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only color data (approximate_color, unfamiliar_color) and status flags (is_delete, last_update_time). No PII fields are present. The data appears to be product color mappings for dresses, with no customer or personal information exposed.
azazie__uniq_sku_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with two columns: sku and short_code. Both columns contain only alphanumeric codes with no personal identifiable information (PII). The values appear to be product identifiers or style codes, not personal data. No email addresses, phone numbers, names, addresses, or other PII fields are present in the sample data.
azazie__uniq_sku_map_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the first 50 rows. All columns appear to be internal IDs, codes, flags, and timestamps. No email addresses, phone numbers, names, addresses, DOB, SSN, passwords, usernames, or other PII are present in the sample data.
azazie__uniq_sku_map_goods_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps. No PII is present in the first 50 rows. Columns map to skip categories: internal IDs (external_cat_id, external_goods_id), timestamps (created_time, last_update_time), and flags (is_delete).
azazie__unshelve_abnormal_list.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal tracking IDs and timestamps. Columns like 'action_user' contain usernames (yzhang14, able.wang, jacky, Kucan, leopard, jacky.hu) but these appear to be internal system usernames rather than customer-facing PII. No actual customer PII (email, phone, names, addresses, etc.) is present in this structured dataset. All columns map to skip categories: internal IDs (id, shipment_id, order_id, party_id), internal usernames (action_user), and timestamps (created_stamp, last_update_time, remark).
azazie__unshelve_items_name.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product/item metadata (item IDs, display names, and timestamps). No PII is present. Columns 'action_user' contain generic usernames ('jozhang', 'pxing') which appear to be internal system users, not customer PII. All columns fall under exclusion rules (internal IDs, timestamps, product data).
azazie__unshelve_items_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a transactional ledger with columns: id, report_day, time_range, attr_name, party_id, attr_value, created_time, last_update_time. No PII fields are present — all values are numeric codes, dates, and timestamps. The 'party_id' appears to be an internal customer/account reference number, not a PII field. All columns are skipped per rules.
azazie__unshelve_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, status flags, timestamps, product codes, or shipment tracking numbers. No PII fields present.
azazie__unshelve_record_copy1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, status flags, timestamps, and product identifiers. The file contains shipment/order metadata but no customer personal data.
azazie__unshelve_record_copy2.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, status flags, timestamps, or product metadata. 'action_user' appears to be system usernames, not customer identifiers.
azazie__unusual_dress_wrap.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This file contains only internal IDs (external_goods_id), timestamps (created_stamp), and flags (is_used). No PII fields are present. The data appears to be a list of product IDs with creation timestamps and usage status, typical of an inventory or product tracking system.
azazie__unusual_shipment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, timestamps, status flags, or numeric codes (shipment_id, party_id, taobao_order_sn, shipping_date, country/province codes, tracking_number, package_type, weight, action_user, status, note, action_time, out_weight, last_action_user, last_update_time, shipping_cost). None map to email, phone, name, address, DOB, SSN, password, username, gender, suffix, or facebookId per the provided field types. Values are internal system data, not personal information.
azazie__upc_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/order identifiers, timestamps, or user logins. No PII fields detected. 'create_by_user_login' and 'last_update_by_user_login' contain usernames but are internal system accounts, not customer-facing identifiers. All columns are excluded per rules for internal IDs, timestamps, and non-customer user logins.
azazie__upload_order_batch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order/tracking IDs and timestamps. No PII fields (names, emails, addresses, etc.) are present. All columns are internal IDs, dates, amounts, or flags and are skipped per exclusion rules.
azazie__upload_quotation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, filenames, paths, user identifiers, and timestamps. No PII fields are present. All columns map to skip categories (internal IDs, timestamps, file metadata).
azazie__upload_quotation_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal tracking fields (check_id, external_goods_id, file_name, file_path, check_status, check_user, check_time, upload_user, create_time, last_update_time). No PII present. These appear to be system audit / file management records from the quotation/check process, not customer data.
azazie__upload_quotation_price.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The file appears to be a product inventory table with columns for product IDs, pricing, user action, timestamps, and product categories/fabrics. No personal identifiable information is present.
azazie__ups_deliver_time.csv1 column0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | zip | high | [1] header 'zipcode', values are valid 5- or 9-digit US ZIP codes with optional hyphens |
Notes: Only column 1 (zip) contains PII. All other columns are internal shipment metadata (carrier, timestamps, party IDs) and must be skipped per exclusion rules.
azazie__ups_printed_info.csv6 columns106 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 9 | phone | high | header "tel" resolves to PII field "phone" |
| 10 | address1 | high | header "address" resolves to PII field "address1" |
| 11 | country | high | header "country" resolves to PII field "country" |
| 12 | state | high | header "province" resolves to PII field "state" |
| 13 | city | high | header "city" resolves to PII field "city" |
| 15 | zip | high | header "zipcode" resolves to PII field "zip" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__ups_region.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a pure reference table of country/region codes with no PII present. All columns are geographic identifiers and internal codes, none contain personal information.
azazie__us_product_lend.csv413 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__us_product_lend__bak20180108.csv210 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__us_product_lend_summary.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII detected. All columns (dispatch_sn, detail_id, lend_stamp, status, lend_number) are internal tracking fields, timestamps, or status codes. No personal or sensitive data present in the first 50 rows.
azazie__us_zip_code_zone.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: The provided data consists of numerical ranges and codes that do not contain any PII fields. The columns do not map to any of the specified PII fields (email, phone, dob, firstName, middleName, lastName, fullName, address1, address2, city, state, zip, ssn, password, username, country, gender, suffix, facebookId). The data appears to represent internal zone or area codes rather than personal information.
azazie__usa_inventory_dress.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns detected in the provided rows. All visible fields appear to be internal identifiers (dispatch_sn), timestamps (create_stamp, last_update_time, etc.), and status flags (sale_out, memo, sale_order_id). There are no columns containing email, phone, name, address, DOB, SSN, password, or other PII data.
azazie__usa_sample_dress_intercept_condition.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains no PII fields. All columns are internal identifiers, flags, timestamps, and non-personal keywords/styles. No email, phone, name, address, DOB, SSN, password, or username data is present.
azazie__usa_sample_dress_intercept_dispatch.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, status flags, or system-controlled values. 'confirm_user' and 'concel_user' appear to be system-controlled usernames, not actual customer PII.
azazie__usa_sample_dress_inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent product/order metadata (IDs, sizes, colors, dates). No PII fields detected. Columns contain internal identifiers, product attributes, timestamps, and flags — all excluded by policy.
azazie__usa_sample_dress_inventory_debug.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, product attributes, timestamps, and flags. This is a product inventory table from Azazie, not customer data.
azazie__usa_sample_dress_inventory_new.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/warehouse identifiers, business flags, or operational codes. No PII present (no names, emails, phones, addresses, DOB, SSN). Column 5 "goods_name" contains product names (e.g., "Azazie Alyssa") not customer names.
azazie__usa_sample_dress_inventory_sd.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields appear to be internal identifiers (e.g., dispatch_sn), status flags (is_sale), timestamps, or version markers. Values contain only order references, system flags, and dates without personal information.
azazie__usa_sample_dress_inventory_wl.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order IDs and timestamps. No PII fields are present. All columns are internal identifiers or timestamps and are skipped per rules.
azazie__user.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a MySQL user privileges table showing database user accounts and their permissions. All columns contain system/user account metadata and access control flags rather than customer PII. No personal identifiable information fields are present.
azazie__user_action_logs.csv1 column25 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | username | high | [3] JSON field "user_name" inside action_log, values are alphanumeric usernames |
Notes: Only username is PII; all other columns are internal IDs, IPs, timestamps, or JSON action logs without personal data. action_log contains structured JSON but no PII beyond username.
azazie__user_address.csv9 columns636 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | fullName | high | [4] header 'consignee', values are full names like 'feng ji' |
| 5 | firstName | high | [5] header 'first_name', values are given names like 'feng' |
| 6 | lastName | high | [6] header 'last_name', values are surnames like 'ji' |
| 7 | gender | medium | [7] header 'gender', values likely represent gender |
| 8 | skip | high | [8] header 'email', contains email addresses |
| 13 | address1 | high | [13] header 'address', contains street addresses |
| 14 | zip | high | [14] header 'zipcode', contains ZIP codes |
| 15 | phone | high | [15] header 'tel', contains phone numbers |
| 20 | city | medium | [20] header 'city_text', contains city names |
Notes: 27 columns total, 9 contain PII (fullName, firstName, lastName, gender, email, address1, zip, phone, city). All other columns are internal IDs, timestamps, flags, or non-PII codes.
azazie__user_agent.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns appear to be internal tracking data (user_agent_id, agent_type, md5_agent). There are no identifiable PII fields in this sample. The columns are purely technical identifiers for browser/user-agent metadata and do not map to any PII categories.
azazie__user_change_address.csv5 columns3 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | high | [3] header 'consignee', values are name-like strings |
| 11 | zip | high | [11] header 'zipcode', values are 5-digit numbers |
| 12 | address1 | high | [12] header 'address', values are address fragments |
| 13 | address2 | high | [13] header 'sign_building', values are secondary address fragments |
| 14 | phone | high | [14] header 'tel', values match US phone format and long numeric strings |
Notes: 22 columns total, 5 contain PII (name, zip, address lines, phone). Columns 0-2,4-10,15-21 are internal IDs, timestamps, status flags, or empty text fields.
azazie__user_language.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only two columns: user_id (internal ID) and language. Neither column contains PII. user_id is an internal numeric identifier and language is a non-PII demographic field. No PII fields are present.
azazie__user_login_record.csv1 column740 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__user_party.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns identified. The file appears to be an internal transactional table with only identifiers (USER_PARTY_ID, PARTY_ID, USER_ID), status flags, and timestamps. No personal data such as names, emails, or addresses is present in the visible rows.
azazie__user_provider.csv1 column21,348 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | username | high | [0] header 'user_name', values are alphanumeric strings resembling usernames |
Notes: Only 'user_name' maps to PII (username). 'provider_id' is an internal numeric identifier and must be skipped per rules.
azazie__user_recommend_token.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, or non-personal identifiers. user_name contains low-entropy strings (test, chuwei) not clearly usernames or names.
azazie__user_url.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: This is a list of URLs (web addresses) with MD5 hashes as the first column. No personal identifiable information (PII) is present in these structured records. The URLs point to login pages, product pages, and cart pages for Azazie and Loveprom e-commerce sites. There are no columns containing names, emails, phone numbers, addresses, or other PII fields.
azazie__users.csv5 columns690 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | username | high | [2] header 'username', values are unique alphanumeric strings |
| 3 | high | [3] header 'email', values contain @ sign | |
| 4 | password | high | [4] header 'password', values are MD5 hashes (32 hex chars) |
| 5 | fullName | high | [5] header 'real_name', values match human-readable names |
| 12 | password | high | [12] header 'finance_pswd', values are MD5 hashes |
Notes: 15 total columns; 5 contain PII (username, email, password, real_name/fuller name, secondary password). All other columns are internal IDs, tokens, IPs, status flags, or timestamps and must be skipped per rules.
azazie__usps_region.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only region and location reference data (region_id, state codes, city names, airport codes, postal code ranges). There are no columns containing personal identifiable information (PII). All columns are geographical/operational codes and should be skipped per the rules. No emails, names, addresses, phone numbers, DOB, SSN, passwords, usernames, or other PII fields are present.
azazie__usps_shipping_tracking.csv2 columns866 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | state | high | header "province" resolves to PII field "state" |
| 3 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__usps_tracking_number.csv0 rows
File structure
Notes: free-form text with no consistent delimiter structure; contains only a single tracking number line
azazie__usps_tracking_number_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only shipment IDs and tracking numbers, which are internal identifiers and not considered PII. No personal identifiable information is present in the first 50 rows.
azazie__usr1.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and codes (abs_id, user_id, user_name, code_id). No PII fields are present. The user_name column appears to be usernames or internal codes, not actual full names, and is therefore skipped per rules. No emails, phones, addresses, DOB, SSN, etc. are present in the sample.
azazie__vb_duedate_track.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal order management data (IDs, due dates, notes, user actions). No PII fields are present. Columns like abs_id, order_id, required_duedate, rush_type, note, action_user, and create_stamp are all operational/tracking fields and do not contain personal information.
azazie__vb_overseas_warehouse.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal operational data: auto-increment IDs, country/facility/party/SM reference IDs, ERP SKU codes, barcodes, and usage flags. This appears to be an inventory or stock management table with no personal information.
azazie__vb_virtual_goods_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs (virtual_goods_id, goods_id) and product names (project_name). This is a product catalog dump, not customer data.
azazie__vb_web_size_chart.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only product size mappings (goods_size, us_size, uk_size, eu_size) and an internal identifier (abs_id). No PII fields are present. All columns are skipped per rules (vehicle/product data, internal IDs).
azazie__virtual_goods_shelf.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction IDs and timestamps. Columns: abs_id (internal ID), provider_id (internal ID), external_goods_id (internal ID), action_time (timestamp), action_user (username-like string). No PII fields are present. The 'action_user' values appear to be test accounts or generic usernames, not actual user identifiers. All columns map to skip categories per rules (internal IDs, timestamps).
azazie__virtual_goods_shelf_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product inventory table with columns: abs_id, goods_shelf_id, external_goods_id, goods_color, goods_size, on_off_shelf. No PII fields are present. All columns are product-related identifiers, colors, sizes, and shelf status flags.
azazie__virtual_inventory_action_log.csv2 columns552 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | high | [3] header 'actor_name', values are human-readable names |
| 5 | skip | high | [5] header 'description', values are empty strings |
Notes: Only two columns contain meaningful PII. Column 3 (actor_name) contains human-readable names, while column 5 (description) is consistently empty and should be skipped.
azazie__virtual_inventory_action_record.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in this dataset. The file appears to be a product inventory log containing only SKU codes, quantities, timestamps, and user actions. All columns represent internal business data (product IDs, inventory counts, timestamps, and system users) with no personal information exposed in the first 50 rows.
azazie__virtual_inventory_open_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal product/inventory identifiers, timestamps, status flags, and operational metadata. No PII fields present. This is a product inventory table from Azazie's database, tracking SKU quantities, stock status, and system timestamps.
azazie__virtual_inventory_open_plan.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain only internal IDs, timestamps, or product inventory metadata. No PII is present in this sample.
azazie__visit_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File appears to contain only internal system logs and URLs with no personal identifiable information. Columns include id, ip addresses (internal network), title, url paths, note, action_user, create_time, and last_update_time - all of which are system metadata or internal tracking information.
azazie__wait_delivery_order.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields identified. All columns represent internal order tracking data (IDs, timestamps, status flags) with no personal information exposed in the sample.
azazie__wallet.csv1 column18 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | header "email" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__wallet_detail.csv2 columns158 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 8 | high | header "email" resolves to PII field "email" | |
| 10 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__warehouse_receipt.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, timestamps, flags, or system metadata. No PII fields present. Columns like warehouse_receipt_id, factory_group_sn, party_dispatch_sn, taobao_order_sn are internal identifiers. Timestamps (create_time, last_update_time) and user logins (create_by_user_login, last_update_by_user_login) are system metadata, not personal PII. The flag 'entered' and note field contain non-PII operational data.
azazie__washing_care_label_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns are internal IDs (skc_id, material_id), descriptions, and timestamps. No email, phone, name, address, or other PII fields are present in the sample.
azazie__washing_care_label_material.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a product/material metadata file with no personal identifiable information. All columns are internal product attributes (IDs, material names, timestamps) and do not contain any PII fields. The columns are: id, external_goods_id, material_label, material_name, description_num, created_at, updated_at.
azazie__web_size_chart.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only size mapping data (goods_size, us_size, uk_size, eu_size, etc.). No personal identifiable information (PII) fields are present. All columns are related to product sizing and should be skipped.
azazie__weeks_country_sales_predict_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/tracking columns (country_id, predict_years, predict_weeks, predict_rates, create_time, create_user). No PII fields are present. All columns are marked as skip per exclusion rules (internal IDs, timestamps).
azazie__weeks_dispatch_predict_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured CSV file but contains only internal operational/timestamp data (predict_years, predict_weeks, predict_rates, create_time, create_user). No PII fields are present. All columns map to skip categories: years/weeks/rates are counters, create_time is a timestamp, and create_user is an internal user identifier.
azazie__weeks_frsales_predict_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only predictive data and creation metadata (predict_years, predict_weeks, predict_rates, create_time, create_user). No PII fields are present. All columns are internal operational/timestamp data and should be skipped.
azazie__weeks_lc_predict_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal prediction metrics and creation timestamps (predict_years, predict_weeks, predict_rates, create_time, create_user). No PII fields are present. All columns are internal operational data and should be skipped per exclusion rules.
azazie__weeks_od_predict_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational/temporal data (predictions, creation times, users). No PII is present. All columns are non-PII per exclusion rules: 'create_user' is an internal username (skip), timestamps are not DOB, and numeric counters are internal metrics.
azazie__weeks_od_predict_rate_gd.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (predict_years, predict_weeks, predict_rates, create_time, create_user) with no PII fields. All columns are internal timestamps and identifiers, so they are skipped per rules.
azazie__weeks_shoes_predict_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only non-PII columns: prediction data (years, weeks, rates) and audit fields (creation timestamp and user). No personal or sensitive data is present.
azazie__weeks_uksales_predict_rate.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only prediction metrics and creation timestamps — no PII fields present. All columns are internal operational data (predict_years, predict_weeks, predict_rates, create_time, create_user). The create_user value 'wmzhen' is an internal system username, not a customer-facing identifier, and must be skipped per exclusion rules.
azazie__win_bidding_provider.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal operational/tracking data for dress bids (IDs, prices, statuses, timestamps). No PII fields present. 'delivery_user' and 'check_user' appear to be internal system usernames, not customer identifiers. Timestamps and status flags are non-PII.
azazie__wk_auto_replenish.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, timestamps, inventory counts, financial parameters, and product metadata typical of an inventory management system. No names, contact details, or personally identifiable information present in the first 50 rows.
azazie__wk_bi_estimated_color_purchase_data.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal inventory/sales demand metrics and identifiers. No PII fields are present.
azazie__wk_config_common.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal settings configuration data with no personal identifiable information (PII). All columns represent system settings, JSON structures of business logic, and timestamps — none contain names, emails, addresses, or other PII fields. The columns 'action_user' contain internal usernames (yzhang, Fengyisa) which are excluded per rules as internal IDs, not public usernames. No PII fields detected.
azazie__wk_external_goods_id_provider_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transactional IDs and timestamps. No PII fields present. Columns: id (internal ID), external_goods_id (internal ID), provide_id (internal ID), action_user (username-like but appears to be system user), update_at (timestamp), created_at (timestamp), is_deleted (flag), num (counter). All columns are internal system data or timestamps, which must be skipped per rules.
azazie__wk_replenishment.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational metadata (IDs, timestamps, status flags). No PII fields are present. Columns 'id', 'action_user', 'update_at', 'created_at', and 'status' are all internal tracking data and do not contain any personally identifiable information.
azazie__wk_replenishment_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product attributes, timestamps, and status flags. The file appears to be inventory/replenishment records for products, not customer data.
azazie__wk_sales_forecast.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, product codes, status flags, timestamps, and numeric counters. No PII fields (email, phone, name, address, DOB, SSN, password, username, gender, suffix, facebookId) are present. Columns like 'id', 'cat_id', 'external_goods_id', 'uniq_sku', 'status', 'is_new', 'forecase_time', 'update_time', 'create_time', 'party_id', and sales metrics contain only internal system identifiers and operational data.
azazie__wk_sku_provider_map.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, product attributes, timestamps, or flags. No PII detected. Columns like 'action_user' appear to be system usernames, not customer usernames, and are excluded per rules.
azazie__wms_category_relation.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a structured CSV containing only internal category identifiers and hash values. There are no personal identifiable information (PII) fields present in the visible data. All columns appear to be internal reference codes (cat_id, website_cat_id, wms_cat_id), status flags (is_deleted), timestamps (created_time, updated_time), user references (created_by, updated_by), and hash values. No email addresses, phone numbers, names, addresses, dates of birth, SSNs, passwords, usernames, or other PII fields are detectable in the sample.
azazie__wms_config.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal system metadata (container IDs, timestamps, JSON parameters). No PII fields are present. Columns map to internal operational data only.
azazie__wms_force_mapping.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be a tracking log for return applications, containing only internal IDs, user identifiers, and timestamps. No PII fields are present. All columns map to skip categories: internal IDs (id, issue_id, primary_mapping), user identifiers (action_user), and timestamps (create_time, last_update_time).
azazie__wms_goods_lend_return.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal operational data (IDs, stock actions, timestamps). No PII fields present. Columns like 'action_user' contain internal system usernames, not customer PII.
azazie__wms_goods_sync.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected in the provided rows. All columns appear to be internal identifiers, SKU codes, timestamps, and status flags. No personal information such as names, emails, addresses, or phone numbers is present.
azazie__wms_hs_code.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains product data (id, name, hs_code, status, timestamps). No PII fields are present. Columns are product identifiers, codes, status flags, and timestamps — all non-PII per exclusion rules. The 'name' column contains product names (e.g., "时装", "色卡", "领结方巾", "伴娘服"), not personal names.
azazie__wms_order_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, product codes, quantities, timestamps, status flags, and operational messages. No personal identifiable information is present in the first 50 rows.
azazie__wms_order_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal IDs, status flags, timestamps, or operational tracking codes. Columns like 'id', 'issue_id', 'container_id', 'request_id', 'shipping_plan_id', 'tracking_number', 'signing_time', 'create_time', and 'last_update_time' contain only internal references, transaction IDs, status codes, and timestamps — none qualify as PII under the defined rules.
azazie__wms_request_callback_log.csv1,761 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
azazie__wms_shipping.csv1 column34 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 18 | emailText | high | free-text column with embedded emails (15/15 cells, 100% density) |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__wms_shipping_area.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns contain only internal IDs and numeric product/SKU codes. The values are product identifiers and region codes, not personal data.
azazie__wms_shipping_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. File appears to be a transactional/order table containing only shipment IDs, SKUs, quantities, weights, and timestamps. No personal or identifiable information present in the first 50 rows.
azazie__wms_stock_check.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, product SKUs, timestamps, inventory counts, and operational metrics — no PII present. Columns like id, goods_sku, wms_sku, latest_time, warehouse_storage, available_storage, occupy_stoarge, intransit_storage, erp_stock, erp_atp, erp_wait, create_time, last_update_time contain only internal system data and inventory tracking. This is a product inventory/stocking table, not customer data.
azazie__wms_stock_check_history.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal inventory and operational data (IDs, SKUs, timestamps, storage counts). No PII fields are present. Columns like 'id', 'goods_sku', and timestamps are internal identifiers and operational metrics, explicitly excluded by policy.
azazie__wms_stock_inventory.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, codes, status flags, timestamps, and operational data. No personal information (names, emails, addresses, etc.) is present in the first 50 rows.
azazie__wms_storage_adjustment_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns contain inventory IDs, timestamps, stock codes, and error messages related to inventory reconciliation. No personal information present.
azazie__wms_storage_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains inventory/storage records with no PII. Columns like id, goods_sku, warehouse_storage, and timestamps are internal operational data. No email, phone, name, address, or other PII fields are present.
azazie__worker_account.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs, account aliases, and timestamps. No PII fields are present. All columns are mapped to skip per exclusion rules (internal IDs, timestamps).
azazie__working_hours.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (working hours and pricing) with no personal identifiable information. All columns represent internal business codes, descriptions, and pricing — none map to PII fields.
azazie__working_hours_info.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal operational data (dispatch service costs and working hours) with no PII fields. All columns are internal identifiers, counters, or financial/timing data that must be skipped per rules.
azazie__workload_detailed.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs, timestamps, action codes, and system metadata. Columns like 'id', 'container_id', 'scan_number', 'order_id', 'create_time', and 'last_update_time' are non-personal operational identifiers or timestamps.
azazie__workload_efficiency_statistics.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns found. All columns are internal IDs, timestamps, counters, or operational flags (e.g., statistics_date, create_time, total_number). No emails, names, addresses, or other PII fields present.
azazie__workload_efficiency_statistics_daily.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns are internal tracking fields (IDs, timestamps, counters, action types). No names, emails, addresses, or other personal data detected.
azazie__workload_statistics.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal identifiers, timestamps, counters, or operational flags (id, statistics_date, statistics_hours, statistics_time, container_id, clothes_number, accessory_number, other_number, total_orders, action_user, goods_type, action_type, create_time, last_update_time). This is a system statistics log file, not customer data.
azazie__workload_statistics_daily.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns represent internal inventory/statistics tracking: IDs, timestamps, counters, and action codes. No PII fields are present.
azazie__worksheet_monitor.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns appear to be internal monitoring or system tracking data (numeric/float values, timestamps, flags). No PII fields detected. 'peoviders' contains numeric IDs and potentially large comma-separated numbers, but no identifiable personal data. 'action_time' is a timestamp which is excluded per rules.
azazie__xdma0830test3.csv0 rows
File structure
Notes: free-form text with no consistent delimiter or row structure; appears to be a simple list of numbers/labels without any PII structure
azazie__xiaobao_code_and_country_name.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII fields detected in the first 50 rows. This appears to be a country/region reference table with country names, codes, and region IDs. No personal data fields (email, phone, names, etc.) are present.
azazie__xiaobao_partition.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This is a structured table containing region codes and fee information, but no PII fields are present. All columns are internal identifiers, region names, codes, and numerical fees — none map to personal data categories.
azazie__xxl_job_group.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains internal system/application metadata (app names, virtual machine identifiers, network addresses). No PII fields present. Columns map to internal identifiers, network addresses, and timestamps — all non-PII per exclusion rules.
azazie__xxl_job_info.csv2 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
azazie__xxl_job_lock.csv0 rows
File structure
Notes: The provided sample is NOT structured data. It contains only two lines: 'lock_name' and 'schedule_lock', which appear to be column names or keys rather than actual record data. There is no delimiter pattern, no consistent row structure, and no visible PII in the sample. This appears to be a header/column definition snippet rather than actual breached records. Since there is no row structure and no embedded PII, we classify this as unstructured with no columns to map.
azazie__xxl_job_log.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal system identifiers, job metadata, timestamps, and status flags. The data appears to be operational job scheduling logs rather than customer or user data.
azazie__xxl_job_log_report.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: no·Quote: "
Notes: No PII columns detected. File contains only internal tracking metrics: trigger_day, running/success/failure counts, and update timestamps. No personal data, identifiers, or sensitive fields present in the first 50 rows.
azazie__xxl_job_logglue.csv1 column2 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | emailText | high | free-text column with embedded emails (2/34 cells, 6% density) |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
azazie__xxl_job_registry.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file appears to be an internal system log or configuration table from Azazie's database. It contains only system identifiers, internal IP addresses, and timestamps. No PII fields are present. All columns are internal system data or timestamps and should be skipped per exclusion rules.
azazie__xxl_job_user.csv2 columns4 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | [1] column named 'username', values are alphanumeric handles |
| 2 | password | high | [2] column named 'password', values are MD5 hashes |
Notes: This is a minimal admin/user credentials table. Only contains username and password hashes; no other PII present. The 'role' and 'permission' columns are internal flags and skipped.
azazie__zipper_buy_request.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: All columns contain internal order identifiers, timestamps, and numeric values. No PII fields are present. The file appears to be an order/transaction log with provider IDs, SKU numbers, timestamps, and order references — none contain personal or sensitive data.
azazie__zipper_buy_request_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only internal IDs (abs_id, request_id), timestamps (created_stamp), and product identifiers (uniq_sku). All columns are internal transactional data with no personal information.
azazie__zipper_purchase_bill.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal financial/transactional data and timestamps. No PII fields are present. Columns represent billing IDs, timestamps, amounts, and status flags, all of which are excluded by rules.
azazie__zipper_purchase_bill_detail.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: This file contains only internal transaction IDs and timestamps. No PII fields are present. All columns are internal IDs or timestamps and should be skipped per exclusion rules.
azazie__zz_event_message.csv0 rows
File structure
Format: CSV·Delimiter: comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only internal operational data (order IDs, timestamps, status messages) with no personal information such as names, emails, addresses, or other PII fields. All entries are transactional instructions and status updates.