← All datasets

havenly.com

Jul 1, 2020

1,708,507
Records
2
Files
Apr 24, 2026
Added

A breach of Havenly (havenly.com), an online interior design platform. The archive contains a MySQL database dump (havenly.sql) from the 'havenly_app' database and a customers CSV file. The SQL dump includes a users table schema with fields for usernames, names, email addresses, bcrypt-hashed passwords, phone numbers, ZIP codes, Stripe customer IDs, Facebook OAuth IDs, referral data, subscription status, and various account metadata. The customers CSV contains user IDs, email addresses, first and last names, account creation timestamps, address fields, and LTV (lifetime value) data. The breach was distributed via BreachForums.

Data found in this dataset

EmailFirst nameLast nameUsernameAddressCityStatezipskipfullNamephone

Search this dataset

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

Source files

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

customers.csv
7 columns1,707,928 rows

File structure

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

Source columnMapped fieldConfidenceLLM assessment
1emailhigh[1] header 'EMAIL', values contain @ signs and email addresses
2firstNamehigh[2] header 'FIRST_NAME', values are common given names
3lastNamehigh[3] header 'LAST_NAME', values are common family names
5address1high[5] header 'ADDRESS', maps to address1
6cityhigh[6] header 'CITY', maps to city
7statehigh[7] header 'STATE', maps to state
8ziphigh[8] header 'ZIP_CODE', maps to zip

Notes: 10 columns total. USER_ID (col 0) is an internal identifier — skipped. USER_CREATED (col 4) is a timestamp — skipped. LTV_LIFETIME (col 9) is a financial/transactional value — skipped. Address fields (cols 5-8) are present in the header but mostly empty in the sample rows; still mapped as PII.

havenly.sql
25 columns579 rows

File structure

Source columnMapped fieldConfidenceLLM assessment
0skiphighauto-increment primary key 'id'
1skiphigh'vip' flag - tinyint boolean, non-PII status field
2usernamehighcolumn named 'username', human-generated login name
3fullNamehighcolumn named 'name', full name field
4firstNamehighcolumn named 'first_name'
5lastNamehighcolumn named 'last_name'
6skiphigh'photo' - profile photo URL, non-PII
7passwordhighcolumn named 'password', bcrypt hashed passwords per breach context
8emailhighcolumn named 'email', primary email address
9phonehighcolumn named 'phone_number', varchar(10) phone digits
10ziphighcolumn named 'zip_code', varchar(6) postal code
11skiphigh'timezone' - user timezone preference, non-PII
12skiphigh'stripe_customer' - third-party payment processor ID, internal reference
13skiphigh'referral_source_id' - internal referral FK, non-PII
14skiphigh'referral_source_details' - referral metadata, non-PII
15skiphigh'role' - account role/permission level, non-PII
16skiphigh'support' - tinyint boolean flag, non-PII
17skiphigh'created' - account creation timestamp, non-PII
18skiphigh'modified' - record update timestamp, non-PII
19skiphigh'welcome_sent' - tinyint boolean flag, non-PII
20skiphigh'likely_to_order' - CRM datetime flag, non-PII
21skiphigh'status' - tinyint account status flag, non-PII
22skipmedium'notes' - internal CRM notes field, likely non-PII operational data
23skiphigh'preferred_designer_id' - internal FK reference, non-PII
24skiphigh'allow_reminders' - tinyint boolean preference flag, non-PII

Notes: MySQL dump from havenly_app database users table. Contains bcrypt-hashed passwords per breach context. Key PII fields: username, full name, first/last name, email, phone number, and ZIP code. Stripe customer IDs skipped as third-party internal references. No SSN, DOB, or address fields present in this table schema. Breach also includes a customers CSV (not analyzed here) which per context contains address fields and LTV data.

Articles about this breach

havenly.com. Shadow Identity