Locally
locally.com
About This Breach
Locally, in October 2022, experienced a significant data breach impacting its users. The incident led to the exposure of full names, phone numbers, usernames, physical addresses, partial credit card details, and passwords encrypted as bcrypt hashes.
Data Exposed
Breach Details
| Breach Type | Data Breach |
| Searchable | Yes |
| Verified | Yes |
| Sensitive Data | No |
| Reference | No reference available |
Frequently Asked Questions
When did the Locally data breach happen?
Locally was breached in Oct 2022. The breach was added to the XposedOrNot index on January 10, 2024.
How many records were exposed in the Locally breach?
1,517,529 records were exposed, making it the #326 largest of the 763 breaches in our index.
What data was exposed in the Locally breach?
The exposed data includes: Usernames, Passwords, Email addresses, Geographic locations, Phone numbers, Physical addresses.
What should I do if I was affected by the Locally breach?
Change your password on the affected service (and anywhere you reused it), turn on two-factor authentication, and set up free breach alerts on XposedOrNot so you know the moment your email appears in a new breach.
What Should You Do?
Change Your Passwords
Update your password immediately, using 12+ characters with numbers and symbols.
Enable Two-Factor Authentication
Add 2FA on all supported accounts using an authenticator app like Google Authenticator or Authy.
Watch for Phishing Calls & SMS
Be cautious of unexpected calls or texts asking for personal information.
Beware of Scam Mail
Be skeptical of unexpected correspondence requesting personal details.
Monitor Your Accounts
Set up login alerts and review account activity regularly for suspicious access.
Use a Password Manager
Never reuse passwords: use a password manager to generate unique ones for each account.