bitsphere.in
Aug 10, 2026
Database dump from bitsphere.in, an Indian digital services/IT company. The breach contains multiple tables including user registration data, login credentials, SMS data, campaign data, doctor profiles, chatbot interactions, car registration/survey data (Hyundai models), Indian Oil campaign entries, blog content related to AYUSH/traditional medicine systems, and various government/health-related data. The data appears to be from a company that managed multiple client campaigns and government digital initiatives in Bihar and Jharkhand regions of India.
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.
bitsphere.in__blogs.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a free-form news/articles dataset. Columns are id, news content, heading, image path, date, user_id, status. No PII fields present. The text contains general educational content about AYUSH medical systems and does not include any personal identifiers. All columns are either IDs, timestamps, status flags, or free-text content — none map to PII categories.
bitsphere.in__campaign.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with campaign data (campaign_id, name, start_date, end_date). No PII fields are present. All columns are campaign identifiers and dates, which are not considered PII under the defined rules.
bitsphere.in__car.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a simple CSV with two columns: id (numeric internal ID) and car_name (vehicle model names). Neither column contains PII. id is an internal numeric identifier, and car_name contains generic vehicle model names without any personal or identifiable information. All columns should be skipped per exclusion rules.
bitsphere.in__car_data.csv4 columns168 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 | vehicle make/model field |
| 2 | address1 | high | header 'address', values are location strings possibly with embedded addresses |
| 3 | zip | high | header 'pincode', values are 6-digit Indian postal codes |
Notes: CSV file with 3 columns: ID (skip), car name/model (skip), address line (contains city/state/zip fragments), and pincode (zip). Address field contains city/state fragments combined with '/' separators and sometimes full addresses.
bitsphere.in__car_data_add.csv3 columns518 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | column 'id' is an internal identifier (numeric auto-generated) |
| 1 | skip | high | column 'car_name' contains vehicle/product data (e.g., GRAND i10 NIOS, SANTRO), not personal PII |
| 2 | address1 | high | column 'address' contains location strings including city names, regions, and postal codes (e.g., "816106, Pakur", "Bettieh, w. Chamaparan") |
Notes: CSV file with 3 columns. Column 0 is an internal numeric ID, column 1 contains vehicle make/model data (skip), column 2 contains full address information (city, district, state, postal codes). No email, phone, name, or other PII fields present.
bitsphere.in__car_district_data.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns present. All columns contain vehicle/car data (IDs, models, districts) which are internal IDs and non-PII per exclusion rules. No emails, phones, names, or addresses detected.
bitsphere.in__category.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is not a data row file; it's a simple table of table names and IDs. The rows shown are just metadata describing available tables ('SMS', 'Whatsapp'). No PII present in this sample.
bitsphere.in__chatbot_ayush_reply.csv1 column91 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | phone | high | header "mobile_no" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
bitsphere.in__chatbot_damo_contact.csv2 columns24 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | high | header "email_id" resolves to PII field "email" | |
| 4 | phone | high | header "mobile_no" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
bitsphere.in__chatbot_hints.csv0 rows
File structure
Notes: free-form text with embedded emails / phones
bitsphere.in__district_pincode.csv3 columns0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | [0] header 'id', values are numeric identifiers |
| 1 | zip | high | [1] header 'pincode', values match Indian postal code format (6-digit) |
| 2 | state | high | [2] header 'district', values represent Indian districts/states (ANANTHAPUR) |
Notes: 50 rows of Indian district/postal code mapping data. Only contains zip and state columns with no other PII. No email, phone, names, or DOB present.
bitsphere.in__inbox.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file but contains only internal IDs and counters (id, inbox_num, campaign_id). No PII fields are present. All columns are marked as skip per rules.
bitsphere.in__indian_oil_hero.csv1 column66 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | phone | high | header "phone" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
bitsphere.in__login_user.csv3 columns505 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | password | high | header "password" resolves to PII field "password" |
| 4 | high | header "email" resolves to PII field "email" | |
| 5 | phone | high | header "phone" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
bitsphere.in__mihir_hero.csv2 columns23,005 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | phone | high | [0] header 'phone', values are 10-digit numbers starting with 62 (Indian mobile prefix) |
| 1 | fullName | high | [1] header 'name', values are full person names in Indian format |
Notes: CSV with 2 PII columns: phone and fullName. Column 2 ('id') is an internal numeric ID and column 3/4 are delivery flags — skipped. No other PII present.
bitsphere.in__permission.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only an ID and permission type. No PII present. 'permission' column lists categories like News, Banner Images, Events, etc. which are not personal data. Therefore, no columns map to PII fields.
bitsphere.in__registration_filter_data.csv3 columns176 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | firstName | high | header "first_name" resolves to PII field "firstName" |
| 2 | phone | high | header "mobile_no" resolves to PII field "phone" |
| 3 | address1 | high | header "address" resolves to PII field "address1" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
bitsphere.in__registrationform.csv6 columns399 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | firstName | high | header "student_first_name" resolves to PII field "firstName" |
| 2 | middleName | high | header "student_middle_name" resolves to PII field "middleName" |
| 3 | lastName | high | header "student_last_name" resolves to PII field "lastName" |
| 4 | dob | high | header "dob" resolves to PII field "dob" |
| 10 | phone | high | header "mobile_no" resolves to PII field "phone" |
| 11 | high | header "email_id" resolves to PII field "email" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
bitsphere.in__sms_data.csv1 column15,637 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | phone | high | header "phone" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
bitsphere.in__sms_data_old.csv1 column4,891 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | phone | high | header "phone" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
bitsphere.in__state.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only state/region names and IDs with no personal identifying information. All columns are geographic identifiers and do not map to any PII fields.
bitsphere.in__switch.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only internal tracking fields: id, switch_status, campaign_id, and count. No PII is present. Columns map to internal IDs and counters, which are explicitly excluded per rules.
bitsphere.in__tb_achievement.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a README or descriptive file, not structured data with PII. The content is prose describing achievements under the National AYUSH Mission and contains no importable columns or personal identifiable information fields.
bitsphere.in__tb_act_rules.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but the sample row does not contain any PII fields. All columns appear to be metadata or identifiers (id, act_rules, type, status, created_at). No PII is present in this snippet.
bitsphere.in__tb_app_update.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a metadata table listing app versions, not user data. No PII present. Columns: id (internal ID), app_url (application URL), version_name (semantic version), version_code (integer version). All columns are non-PII per exclusion rules.
bitsphere.in__tb_articles.csv1 column1 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | fullName | high | [4] header 'name', values are full person names (e.g., 'Sanjeet Kumar') |
Notes: Only column 4 contains PII (fullName). All other columns are either non-PII (salutation as honorific prefix), internal IDs, timestamps, or free-text content. The 'salutation' column maps to skip per rules (honorific prefixes like 'Mr.' are not PII).
bitsphere.in__tb_awareness.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs (id), file references (image), document names (document), status flags (status), and timestamps (created_at). No PII fields are present. All columns are non-PII per exclusion rules (internal IDs, timestamps).
bitsphere.in__tb_ayurveda_drug_name_list.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.
bitsphere.in__tb_block.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only district and block names (Hindi script) with numeric IDs. No PII fields (email, phone, DOB, names, addresses, SSN, etc.) are present. All columns are internal geographic identifiers and location names, which do not qualify as PII under the defined rules.
bitsphere.in__tb_case_study.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file is a README or description file, not structured data containing PII. It contains prose about a journal and does not have importable columns with personal information.
bitsphere.in__tb_case_study_heading.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 non-PII metadata: 'id' (internal ID), 'heading' (article title), 'status' (flag), and 'created_at' (timestamp). No PII fields are present in the first 50 rows. According to exclusion rules, internal IDs and timestamps must be skipped. Therefore, no columns map to PII fields.
bitsphere.in__tb_caste_category.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a purely demographic dataset with only internal IDs and counters. No PII fields are present. All columns are internal identifiers or flags: district_id, ur, ews, bc_1, bc_2, st, sc, timestamps.
bitsphere.in__tb_citizen_charter.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file appears to be a metadata listing of files (document management table), not user PII. Columns: id (internal ID), heading (document title), file (filename with checksum), status (flag), created_at (timestamp). No PII fields present.
bitsphere.in__tb_contact_us.csv7 columns737 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | Internal ID or auto-generated identifier |
| 1 | fullName | high | Header is 'name', values are personal full names |
| 2 | high | Header is 'email', values contain '@' symbols and valid email formats | |
| 3 | phone | high | Header is 'phone', values are 10-digit numbers (Indian format) |
| 4 | skip | high | Free-text message column, not a structured PII field |
| 5 | skip | high | Status flag column, not PII |
| 6 | skip | high | Timestamp column, not PII |
Notes: 6 columns total, 3 contain PII (fullName, email, phone). The 'message' column contains free text but isn't a structured PII field. All other columns are internal IDs, flags, or timestamps and have been skipped per rules.
bitsphere.in__tb_contact_user.csv106 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
bitsphere.in__tb_database_backup.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file appears to be a listing of SQL dump filenames and creation timestamps, not actual data records. There are no columns containing PII fields — only an ID, a filename pattern, and a timestamp. No email, phone, name, address, or other PII values are present in the sample rows.
bitsphere.in__tb_district.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only district names and internal IDs. No PII fields present. The data appears to be a simple list of districts in Jharkhand, India, with numeric identifiers. All entries are geographic names and numeric IDs, which do not qualify as PII under the defined rules.
bitsphere.in__tb_division.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a README / descriptive table with no personal identifiable information (PII). Columns describe alternative medicine systems and contain only article metadata (IDs, image filenames, titles, descriptions, URLs, status flags, and timestamps). No names, emails, addresses, or other PII fields are present.
bitsphere.in__tb_division_page.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to be a content dump of medical system descriptions (Siddha, Unani, Homeopathy, Ayurveda, Yoga, Sowa-Rig-pa) with no personal data. Columns are purely informational: id, division_id, image filename, heading, paragraph text, link, status flag, and timestamp. No email, phone, name, address, or other PII fields present.
bitsphere.in__tb_doctor_profile.csv1 column473 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | phone | high | header "phone_no" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
bitsphere.in__tb_downloads.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file is a document inventory with no personal identifiable information. Columns contain document IDs, titles, file sizes, statuses, and timestamps. No PII fields are present.
bitsphere.in__tb_e_library.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. Columns are: id, book_name, book_image, book_pdf, status, created_at. All columns are non-PII per exclusion rules (internal IDs, timestamps, non-personal content metadata).
bitsphere.in__tb_edl_ayurveda_name.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file appears to be a lookup table or category list for Ayurvedic/herbal formulations. Columns contain only internal IDs, type codes, descriptive names (non-person entities), status flags, and timestamps. No PII fields are present. All columns map to skip categories: internal IDs (id), type codes (type), status flags (status), and timestamps (created_at).
bitsphere.in__tb_edl_unani_name.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file containing herbal medicine data (AYUSH/traditional medicine system). All columns are product/formulation metadata (IDs, medicine names, indications, dosages, etc.). No PII fields are present. Columns like 'id', 'created_at', and status codes are internal identifiers/timestamps and must be skipped per rules. No emails, names, addresses, or other PII appear in the sample.
bitsphere.in__tb_edl_unani_type.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a simple lookup table with no PII fields. Columns are id, type, name (product/drug names), status, and created_at (timestamp). No personal information present.
bitsphere.in__tb_feedback.csv2 columns3 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | fullName | high | Header is 'name', values are full names |
| 2 | phone | high | Header is 'phone_no', values are 10-digit phone numbers |
Notes: Only name and phone_no contain PII. org_name contains business names (excluded by rule). created_at is a timestamp (excluded). Rows 2 and 3 contain obfuscated data (likely placeholders or encoded values), but row 1 has valid PII. Total columns: 5, PII columns: 2.
bitsphere.in__tb_guidelines.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a metadata file listing documents/files rather than user PII. Columns contain IDs, file names, statuses, and timestamps — no actual personal data. All columns are internal IDs or non-PII metadata, so no PII fields to map.
bitsphere.in__tb_homeopathy_edl_list.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file but contains no PII columns. All columns are internal IDs, product data (medicine names, potencies), status flags, and timestamps. No emails, phone numbers, names, addresses, DOB, SSN, passwords, usernames, or other PII fields are present.
bitsphere.in__tb_hwc_division.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains unstructured descriptive text in the second column (names of Ayurvedic/ Homeopathic dispensaries) with no identifiable personal information. The first column is an ID, third column is a status flag, and fourth column is a timestamp. No PII fields are present in this structured CSV.
bitsphere.in__tb_hwc_list.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns appear to be internal IDs, geographic coordinates, status flags, and timestamps. No personal identifiable information (names, contact details, etc.) is present in the first 50 rows.
bitsphere.in__tb_inquiry.csv2 columns1 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 |
| 2 | phone | high | [2] header 'phone_no', values are 10-digit numbers |
Notes: 4 columns total, 2 contain PII. The 'id' column is an internal ID (skip). The 'inquiry' column is a free-text field (skip). The 'created_at' column is a timestamp (skip).
bitsphere.in__tb_latest_update.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a news/article summary table with no personal identifiable information (PII). Columns contain IDs, dates, paragraphs, URLs, status flags, and timestamps — all non-PII per exclusion rules. No emails, names, addresses, or other PII fields present.
bitsphere.in__tb_mission_vision.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all columns map to non-PII fields (mission statements, types, statuses, timestamps). No PII fields are present in the provided rows.
bitsphere.in__tb_news_media.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is unstructured text data with no consistent column mapping. The file appears to be a list of news headlines and notices from Jharkhand's AYUSH department, with no PII fields present. All columns contain article titles, URLs, dates, and status flags — none map to PII categories.
bitsphere.in__tb_notice.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file is a README / description document, not structured data containing PII. It contains informational notices and document metadata, with no actual personal information exposed in the rows. All columns (id, notice, document, link, status, created_at) are non-PII metadata or timestamps, and thus should be skipped.
bitsphere.in__tb_notification.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a notification record with no personal identifying information. The columns contain generic notification text, dates, and status flags. There are no PII fields present in this sample.
bitsphere.in__tb_patient_details.csv5 columns320,068 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | fullName | high | [2] header 'doctor_name', values are full names |
| 3 | fullName | high | [3] header 'patient_name', values are full names or IDs with dates (some rows contain full names) |
| 4 | skip | high | [4] header 'patient_mobile_no', expected to contain phone numbers |
| 6 | gender | high | [6] header 'gender', values are 'Female'/'Male' |
| 7 | address1 | high | [7] header 'address', expected to contain address information |
Notes: 13 columns total, 5 contain PII. Columns 0 (id), 1 (raise_req_id), 5 (age), 8 (disease), 9 (date), 10 (user_id), 11 (status), 12 (created_at) are internal IDs, timestamps, or non-PII fields and thus skipped.
bitsphere.in__tb_photo_gallery.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with columns: id, image, img_type, heading, description, status, created_at. None of these columns contain PII. The values are mostly image filenames, statuses, timestamps, and static text. No identifiable personal information is present.
bitsphere.in__tb_photo_gallery_type.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains no PII fields. All columns are internal identifiers, status flags, or timestamps. No emails, names, addresses, or other PII are present.
bitsphere.in__tb_presentation.csv1 column1 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | fullName | high | [6] column 'created_by' contains full names like 'Sanjeet Kumar' |
Notes: Only column 6 (created_by) contains PII (fullName). All other columns are internal IDs, timestamps, or non-PII metadata.
bitsphere.in__tb_program_event.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 'paragraph' column contains free-form text with embedded emails and phone numbers, but there are no structured columns mapping to defined PII fields. All rows appear to be free-form prose describing yoga and health initiatives, with no consistent columnar structure for personal data. The file should be processed as unstructured text for email/phone extraction.
bitsphere.in__tb_raise_request.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains no PII fields. Columns are internal IDs (id, user_id), image filenames, dates, status codes, district codes, patient counts, and timestamps. All columns are internal identifiers, timestamps, or counters and do not contain any personal identifiable information per the exclusion rules.
bitsphere.in__tb_reference_material.csv1 column1 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | fullName | high | [5] header 'name', values are full names like 'Sanjeet Kumar' |
Notes: Only column 5 (name) contains PII. Column 4 (salutation) contains honorifics (Mr.) which are not mapped to any PII field. Other columns are non-PII: id (internal ID), heading (title), paragraph (text), picture (filename), year (non-DOB), created_at (timestamp), created_by (username-like but appears to be same as name field).
bitsphere.in__tb_repository.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is not structured PII data; it's a metadata table for files uploaded to the platform. Columns are: id (internal ID), heading (title/description), file (filename with possible embedded IDs), date (file date), status (flag), created_at (timestamp). No personal identifiers (names, emails, addresses, etc.) are present. The filename 'adhar card pdf.pdf' suggests a document about Aadhaar cards but does not contain actual Aadhaar numbers or personal data.
bitsphere.in__tb_ro_participation.csv2 columns141 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | phone | high | [6] header 'ro_contact_details', values are 10-digit mobile numbers |
| 7 | phone | high | [7] header 'fo_contact_details', values are 10-digit mobile numbers |
Notes: CSV with 7 columns. Only columns 6 and 7 contain PII (phone numbers). All other columns are non-PII: internal IDs, names of fuel stations, areas, districts, etc.
bitsphere.in__tb_scheme.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is unstructured descriptive data about AYUSH initiatives. Columns contain scheme names and HTML tables describing activities, not personal identifiable information. All columns are skipped per rules (no PII fields present).
bitsphere.in__tb_seniority_list.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a README / description file, not structured data containing PII. The file contains prose descriptions of roles and titles rather than columnar PII fields. All columns are honorific titles or organizational roles that do not map to any PII field.
bitsphere.in__tb_slider.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only static CMS/slider content metadata. All columns represent image IDs, titles, status flags, and timestamps. No PII fields are present. The 'status' and 'created_at' columns are internal flags/timestamps and excluded per rules. No email, phone, name, address, or other PII fields exist in the sample.
bitsphere.in__tb_tenders.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains tender information with no PII fields. All columns are identifiers, descriptions, statuses, and timestamps — none contain personal information. Columns 'id', 'tender', 'document', 'status', and 'created_at' are all skipped per rules (internal IDs, company/business references, and timestamps).
bitsphere.in__tb_testimonial.csv9 columns532 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | column contains mixed data types, some values appear to be paths, others are encoded strings, and some are SQL injection attempts; cannot be mapped to a known PII field |
| 1 | username | high | column header 'user_name' maps to username; values include alphanumeric strings and encoded data which could represent usernames |
| 2 | skip | high | column header 'image' likely refers to image filenames or paths; values appear to be image references or encoded strings, not PII |
| 3 | phone | high | column header 'phone_no' maps to phone; values include numeric strings and encoded data that could represent phone numbers |
| 4 | skip | high | column header 'patient_type' contains non-PII data; values appear to be codes or categories |
| 5 | skip | high | column header 'testimonial' contains free-text testimonials; while it may contain PII indirectly, it is not a direct PII field and should be treated as general text |
| 6 | skip | high | column header 'link' contains URLs or paths; values appear to be links or encoded strings, not direct PII |
| 7 | skip | high | column header 'status' contains status codes; values are numeric and do not represent PII |
| 8 | skip | high | column header 'created_at' contains timestamps; values are date-time strings and should be skipped as per exclusion rules |
Notes: The file contains several columns with encoded strings and SQL injection attempts, which may require further decoding and analysis. The 'user_name' and 'phone_no' columns contain potential PII, while other columns contain non-PII data or require additional context for accurate mapping.
bitsphere.in__tb_today_user.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 counters, status flags, and timestamps. No email addresses, phone numbers, names, addresses, DOB, SSN, passwords, or usernames are present in the sample.
bitsphere.in__tb_users.csv4 columns1 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 |
| 2 | high | [2] header 'email_id', values contain @ signs | |
| 3 | phone | high | [3] header 'phone_no', values are 10-digit numbers |
| 4 | password | high | [4] header 'password', values are hashed strings |
Notes: 6 columns total, 4 contain PII (fullName, email, phone, password). Columns 5 (profile_image) and 6 (user_type) are not PII. Timestamps (created_at, updated_at) are excluded per rules.
bitsphere.in__tb_video_gallery.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a video metadata table with no PII fields. Columns include video IDs, YouTube embed URLs, status flags, and timestamps — all non-personal data. No emails, names, addresses, or other PII appear in the sample.
bitsphere.in__tb_video_gallery_type.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: id (internal ID), gallery_type (category), status (flag), created_at (timestamp). All columns are excluded per rules.
bitsphere.in__tb_years.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only internal IDs and timestamps (id, year, created_at). No PII fields present. Columns map to skip categories per exclusion rules.