osu.ppy.sh

File structure

Format: CSV·Delimiter: comma·Has header: yes·Quote: `

Notes: This file contains database schema/structure metadata (column definitions with backticks and SQL keywords like CREATE) rather than actual user PII records. The rows show table column definitions and schema structures, not populated data rows. No actual personal information is present to map. This is a source code/schema leak artifact, not a data breach with extractable PII.

File structure

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

File structure

Notes: This is an email template (prose/markup) from a source code leak, not a structured data file with PII records. It contains template variables ({USERNAME}, {U_USER_DETAILS}, {U_ACTIVATE}, {EMAIL_SIG}) but no actual user data rows. No importable PII columns.

File structure

Notes: This is a README or email template file, not a structured data file. It contains template placeholders ({SITENAME}, {CONTACT_EMAIL}, {MESSAGE}, {EMAIL_SIG}) and prose instructions about handling spam/abuse reports. There are no delimited records or PII fields to map. This file describes breach context and email notification procedures, not user data.

File structure

Notes: This is an email template (prose text with template variables like {USERNAME}, {SITENAME}, {EMAIL_SIG}), not a structured data file containing PII records. No importable data to map.

File structure

Notes: This is an email template (NOT DATA). The file contains free-form prose text with template variables ({USERNAME}, {PASSWORD}, {SITENAME}, etc.) rather than structured records with PII data. No column mapping applies. This is a source code artifact from the osu!web leak, not a user database export.

File structure

Notes: This is an email template (COPPA parental consent form) for the osu! platform, not a structured data file. It contains template placeholders ({SITENAME}, {USERNAME}, {EMAIL_ADDRESS}, {U_BOARD}, {WELCOME_MSG}, {FAX_INFO}, {MAIL_INFO}, {EMAIL_SIG}) rather than actual PII records. No delimited data rows or column structure exists. This is prose documentation, not a breach data export.

File structure

Notes: This is an email template (NOT DATA). It contains template placeholders like {SITENAME}, {TO_USERNAME}, {FROM_USERNAME}, {TOPIC_NAME}, {U_TOPIC}, {BOARD_CONTACT}, {MESSAGE} in free-form prose. This is a README/template file from the osu!web source code leak, not a structured data file with PII records. No importable user data present.

File structure

Notes: This file is an email template (forum post notification) containing only template variables and prose text, not structured PII records. No importable user data present.

File structure

Notes: This is an email template (prose/free-form text with template placeholders like {GROUP_NAME}, {SITENAME}, {U_GROUP}, {EMAIL_SIG}). It is NOT a structured data file containing PII records. It is a notification message template, not delimited tabular data. No importable PII columns exist.

File structure

Notes: This is an email template (prose text with template variables like {USERNAME}, {GROUP_NAME}, {SITENAME}, {U_PENDING}, {EMAIL_SIG}), not a structured data file with PII records. It is part of the osu!web source code leak containing email templates, not user data.

File structure

Notes: This is a phpBB installation confirmation email template (prose/free-form text), not a structured data file or delimited records. It contains template placeholders ({USERNAME}, {PASSWORD}, {U_BOARD}, {EMAIL_SIG}) rather than actual user records. No PII data to extract — this is system documentation/configuration text.

File structure

Notes: This is an email template (forum notification) containing template variables and prose instructions, not a structured data file with PII records. No delimited rows or columns containing actual personal data are present.

File structure

Notes: This is an email template (NOT DATA). The file contains free-form prose with template placeholders ({USERNAME}, {POST_SUBJECT}, {SITENAME}, {REASON}, {EMAIL_SIG}) rather than structured records containing actual PII. This is a README/template artifact from the osu!web source code leak, not a delimited data file with personal information to extract.

File structure

Notes: This is an email template (prose text with template variables like {AUTHOR_NAME}, {USERNAME}, {SUBJECT}, {U_INBOX}, {EMAIL_SIG}). It is NOT a data export or structured record file. No PII data rows are present — only template placeholders for a notification email. This is source code documentation, not a breach data file with actual user records.

File structure

Notes: This is a template/README file for forum email messages, not structured PII data. The content is prose instructions and email template placeholders (e.g., {TO_USERNAME}, {FROM_USERNAME}, {MESSAGE}) rather than actual user records with delimited columns. No importable PII data present.

File structure

Notes: This is an email template (prose text with template variables like {USERNAME}, {POST_SUBJECT}, {CLOSER_NAME}) from the osu!web source code leak. It is NOT a structured data file containing PII records. There are no delimited rows, no headers, and no tabular data — only template instructions. No importable PII data present.

File structure

Notes: This is an email template (NOT DATA). It contains template variables like {POST_SUBJECT}, {USERNAME}, {TOPIC_TITLE}, {SITENAME}, {EMAIL_SIG} but no actual structured records or PII data rows. This is documentation/configuration from source code, not a data breach export.

File structure

Notes: This is an email template (NOT DATA). The file contains template variables and prose text for forum topic approval notifications, not structured records with PII. Variables like {USERNAME}, {TOPIC_TITLE}, {SITENAME}, {U_VIEW_TOPIC}, and {EMAIL_SIG} are template placeholders, not actual PII data. No delimited rows or consistent column structure exists. This is source code / template documentation, not a data export suitable for PII extraction.

File structure

Notes: This is an email template (NOT DATA). It contains template variables like {USERNAME}, {TOPIC_TITLE}, {SITENAME}, {REASON}, {EMAIL_SIG} in a free-form prose email body structure. No actual user PII records are present — this is source code / configuration documentation for the osu!web platform, not a structured data export or user database. No importable PII data to map.

File structure

Notes: This is an email template (forum notification) containing only prose with template placeholders ({USERNAME}, {TOPIC_TITLE}, {U_NEWEST_POST}, etc.). No structured records or delimited columns are present. This is documentation/template content, not a data file with PII records to import.

File structure

Notes: This is an email template file, not a structured data file containing PII records. It contains template variables (placeholders like {USERNAME}, {SITENAME}, {U_ACTIVATE}, {EMAIL_SIG}) used for account reactivation emails, not actual user data rows. No importable PII data present.

File structure

Notes: This is a free-form email template (notification message) with placeholder tokens ({USERNAME}, {SITENAME}, {EMAIL_SIG}), not a structured data file containing PII records. No delimited rows or consistent column structure exists. This is prose documentation of a notification template, not importable personal data.

File structure

Notes: This is a README/template file — an email template for password activation containing only placeholder tokens (e.g., {USERNAME}, {PASSWORD}, {SITENAME}, {U_ACTIVATE}, {EMAIL_SIG}), not structured records with actual PII data. No delimited columns or data rows present. Classified as NOT DATA per instructions.

File structure

Notes: This is a free-form email template (NOT DATA). The file contains prose text with template placeholders ({SITENAME}, {USERNAME}, {U_BOARD}, {U_ACTIVATE}, {EMAIL_SIG}), not structured PII records. It is an email template file from the osu!web source code leak, not a data export. No importable PII columns exist.

File structure

Notes: This is a free-form email template (prose) from the osu!web source code leak, not a structured data file containing PII records. The text contains template variables ({USERNAME}, {REGISTER_DATE}, {SITENAME}, {U_ACTIVATE}, {EMAIL_SIG}) but no actual personal data rows. This is documentation/configuration, not a data breach of user records. No importable PII columns.

File structure

Notes: This is an email template (forum registration welcome message) with template variables like {USERNAME}, {SITENAME}, {U_ACTIVATE}, {EMAIL_SIG}. It is prose/template text describing account setup instructions, not a structured data file containing PII records. No importable tabular data present.

File structure

Notes: File is source code documentation (phpBB Group, British English locale files) not a structured data breach with PII records. No delimited rows containing personal information detected. This is a source code leak artifact, not a user database export.

File structure

Notes: This is a template/configuration file from source code, not a structured PII data export. The rows contain email template variable placeholders ({L_PM_SUBJECT}, {MESSAGE_AUTHOR_FULL}, etc.) and template field references ({to_recipient.NAME}, {bcc_recipient.NAME_FULL}), not actual breach records with PII values. This is infrastructure/source code documentation, not importable user data.

File structure

Notes: This file contains numeric data (likely RGB color values with alpha channel or similar technical configuration data), not PII records. The breach context confirms this is a source code leak of the osu!web platform, not a user database export. No structured PII columns are present.

File structure

Notes: This is NOT a data breach file with PII records. The content is a free-form list of profanity/offensive words with no delimiters, no headers, no columns, and no personal information. This appears to be a word-filter or content-moderation blacklist, not a user database export. No importable PII data present.

File structure

Notes: This is a robots.txt file (unstructured directives), not a delimited data file with PII records. Contains only HTTP user-agent rules and disallow paths, no structured columns or personal information.