Where does the Glucobit, Inc. dba Reframe case file come from?

Every entry is taken from the breach report Glucobit, Inc. dba Reframe lodged with the Washington Attorney General. Nothing here is estimated.

Why do the incident date and the report date differ?

Companies usually investigate before they report. The gap between the two dates shows how long that took.

What does the records-affected figure count?

It is the number the company gave the state. It can cover residents of that state only, so the national total may be higher.

Does this case file change over time?

Yes. When a company files an update or a new state publishes its copy of the report, the dates and counts here are refreshed.

Case file

Case File: Glucobit, Inc. dba Reframe Data Breach

This file collects the dated facts on record for the Glucobit, Inc. dba Reframe incident. The state report is dated June 30, 2026.

Timeline

June 30, 2026Report filed in WashingtonDate the notice was lodged with the Washington Attorney General.

Case facts

Filing state: Washington
Date reported: June 30, 2026
Receiving office: Washington Attorney General

Case notes

Glucobit, Inc., doing business as Reframe, has filed a report with the Washington Attorney General regarding a data security incident. Reframe operates in the digital health and wellness sector, offering behavioral health, alcohol reduction programs, and metabolic wellness tracking through its platforms.

The report indicates that this incident was filed on June 30, 2026. However, the specific type of breach that occurred and the categories of personal information that may have been exposed are not detailed in the public filing. The company is currently investigating the full scope of the security event.

Digital health platforms like Reframe typically handle a broad range of user information, from account details to sensitive lifestyle logs and self-reported health metrics. While the precise data involved in this particular incident remains under investigation, the company's notification serves as a formal acknowledgment of unauthorized access or exposure within its systems.

Individuals who receive a notification from Glucobit, Inc. dba Reframe should remain vigilant. It is generally advisable to monitor your personal accounts for any unusual activity. Consider enabling multi-factor authentication on online accounts where available and be cautious of unsolicited communications that may attempt to gather further personal details.

As the investigation by Glucobit, Inc. progresses, more information may become publicly available. Staying informed through official company communications and regulatory updates is recommended for those who may be affected.

Questions about this case file

Where does the Glucobit, Inc. dba Reframe case file come from?: Every entry is taken from the breach report Glucobit, Inc. dba Reframe lodged with the Washington Attorney General. Nothing here is estimated.
Why do the incident date and the report date differ?: Companies usually investigate before they report. The gap between the two dates shows how long that took.
What does the records-affected figure count?: It is the number the company gave the state. It can cover residents of that state only, so the national total may be higher.
Does this case file change over time?: Yes. When a company files an update or a new state publishes its copy of the report, the dates and counts here are refreshed.

Washington data breaches

Named in the Glucobit, Inc. dba Reframe breach?

Attach your notice and a short note. An attorney checks it against this case file at no cost.

Timeline

Case facts

Case notes

Questions about this case file

More Washington case files