People search Planity data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 Planity-linked incident, with headline counts up to 999K+ in catalog rows. This page maps every attested event through 2026 with internal links to canonical records.
Why Planity breach history matters
Planity operates in Technology (France). Across indexed rows, recurring themes include unverified actor or scraping claims. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — forum sale claim (~999,451 salon/spa customers; unverified)
Unverified claim — treat actor counts cautiously. Unverified forum sale listing — observed July 28, 2026 on Dark Web Informer. Seller “weykofa” advertised what they described as the Planity (French salon/spa booking platform) database: 1,088,463 lines covering 999,451 individuals as a 261MB JSON file, priced at about $2,500 in Bitcoin (negotiable). Sample reportedly showed customer names, phone numbers in multiple formats, email addresses, and a business identifier linking each customer to the salon or spa they booked with, plus creation timestamps. Planity had no Exposed categories include Advertised: customer names, phone numbers, email addresses, business identifier linking customers to salon/spa, record timestamps — ~1,088,463 lines / 999,451 individuals / 261MB J. BreachHistory cites approximately 999K+ affected records in this row. See the planity-forum-sale 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Unverified actor or scraping claims — appears across multiple Planity catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Review OAuth app permissions and revoke unused third-party integrations.
- Step 5: Bookmark the Planity company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/planity · Latest: planity-forum-sale2026.
Sources: BreachHistory catalog (1 row for Planity), company and regulator disclosures cited in individual breach records.