Data breaches → Locally
Was your data in the Locally breach?
2022 · locally.com · ~362,619 accounts exposedCritical severity · 10/10
Locally (locally.com) suffered a data breach in 2022 that exposed around 362,619 accounts. If you had an account, some of your personal data may be circulating in leaked databases. The fastest way to know is to check your own email — free, in about 30 seconds, no password required.
What happened
In October 2022, "The Industry's Leading Online-to-Offline Shopping Solution" Locally suffered a data breach. Whilst Locally acknowledged the breach privately, it's unknown whether impacted customers were subsequently notified of the incident which exposed over 362k names, phone numbers, email and physical addresses, purchases, credit card type and last four digits and bcrypt password hashes.
Breach details sourced from Have I Been Pwned, the industry-standard breach database. Risk analysis by Nullivo.
What was exposed, and why it matters
Not all breaches carry the same risk — what matters is which fields leaked. Here is what the Locally breach exposed and what each item actually enables:
Direct financial fraud, plus convincing scam calls that quote your real card or account details to establish trust.
Attackers replay leaked passwords across other sites (“credential stuffing”). Because most people reuse passwords, one leak often unlocks email, shopping and banking accounts elsewhere.
Home addresses feed people-search and data-broker sites, which republish them publicly. They also make phishing far more convincing and, in the worst cases, enable real-world harassment.
Enables SIM-swap attacks (hijacking your number to intercept SMS codes), smishing, and voice scams that appear to come from your bank.
Puts you on spam and phishing lists, and confirms to attackers that you hold an account with this service — which makes impersonation emails more believable.
Also listed in this breach: Email addresses, Partial credit card data, Passwords, Phone numbers, Physical addresses, Purchases.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Payment or bank details: Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions.
- Passwords: Change this password everywhere you have reused it, starting with your email account — whoever controls your email can reset everything else.
- Home addresses: Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating.
- Phone numbers: Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider.
- Email addresses: Treat any message referencing this service with suspicion, and never act on links in unexpected emails.
- Check whether your own email appears in this breach — run a free scan to confirm before you spend time on the steps above.
This breach put your details on data-broker sites
Because Locally exposed home addresses, this is one of the breaches that feeds people-search and data-broker sites. Those sites scrape leaked databases, combine them with public records, and republish the result as a searchable profile — which is how a single breach turns into a permanent public listing. Removal works, but brokers typically re-list within about four months, so it has to be repeated.
See our broker-by-broker removal guides →
How urgent is this now?
This data has been circulating for around 4 years, which means it has been copied, combined with other leaks and indexed by search tools many times over.
Passwords are the reason breach age matters less than people expect. Leaked credentials are compiled into wordlists that get tried against new services for years afterwards, so a password exposed here is unsafe to use anywhere, ever again.
Remember: a breach can't be "un-leaked" — once a database is out, it exists in countless copies. The goal is to make the leaked data useless: change what can be changed, lock down what can't, and remove what has been republished.
Frequently asked questions
What data was exposed in the Locally breach?
The Locally breach exposed payment or bank details, passwords, home addresses, phone numbers, email addresses. Direct financial fraud, plus convincing scam calls that quote your real card or account details to establish trust.
How many people were affected by the Locally breach?
Around 362,619 accounts were exposed, making it a mid-sized breach.
What should I do if I had a Locally account?
Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions. You can check whether your own email appears in this breach with a free Nullivo scan — no password required.
Breaches that exposed similar data
If the Locally breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the Guns.com breach? (2021, ~375,928 accounts)
- Was your data in the Imavex breach? (2021, ~878,209 accounts)
- Was your data in the Bonobos breach? (2020, ~2,811,929 accounts)
- Was your data in the GunAuction.com breach? (2022, ~565,470 accounts)
- Was your data in the Viva Air breach? (2022, ~932,232 accounts)
- Was your data in the Fanpass breach? (2022, ~112,251 accounts)