Framework customer information was accessed as part of a data breach
News Computing Framework customer information was accessed as part of a data breach The company says payment details weren't exposed. 7, 2026 2:37 pm EST Daniel Cooper for Engadget Framework, maker of deliberately repairable and upgradeable computers, has notified all of its customers that their data was exposed in a breach. According to an email the company sent late Thursday, August 6, customer names, login IPs, addresses, phone numbers and emails were accessed during a hack of the company's business database provider Metabase.
- ▪News Computing Framework customer information was accessed as part of a data breach The company says payment details weren't exposed.
- ▪7, 2026 2:37 pm EST Daniel Cooper for Engadget Framework, maker of deliberately repairable and upgradeable computers, has notified all of its customers that their data was exposed in a breach.
- ▪According to an email the company sent late Thursday, August 6, customer names, login IPs, addresses, phone numbers and emails were accessed during a hack of the company's business database provider Metabase.
Engadget files mainly under tech. We currently carry 552 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Engadget |
| Canonical URL | https://www.engadget.com/2232708/framework-customer-information-was-accessed-as-part-of-a-data-breach/ |
| Publication time | Fri, 07 Aug 2026 18:37:26 +0000 |
| Retrieval time | 2026-08-07T18:45:47.609Z |
| Last seen | 2026-08-07T18:45:47.609Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | BlN69WVoH0UH · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
News Computing Framework customer information was accessed as part of a data breach The company says payment details weren't exposed. By Ian Carlos Campbell Aug. 7, 2026 2:37 pm EST Daniel Cooper for Engadget Framework, maker of deliberately repairable and upgradeable computers, has notified all of its customers that their data was exposed in a breach. According to an email the company sent late Thursday, August 6, customer names, login IPs, addresses, phone numbers and emails were accessed during a hack of the company's business database provider Metabase. Payment information was not included in the breach. The company included Metabase's explanation in its own email, which details when the provider identified the attack on August 3 and the actions Metabase took to address it.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Engadget.
Discussion
0 commentsMore from Engadget
