Secure Health Plans of Georgia LLC, which does business as Secure Health, administers health benefit plans on behalf of employers. The company has publicly disclosed a security incident in which an unauthorized third party gained access to its computer systems. When a plan administrator holds the health and personal records of people who never chose to do business with it directly, the people whose information is exposed deserve clear answers.
Secure Health’s Data Breach Investigation
Secure Health Plans of Georgia works as a third-party administrator for employers that fund their own health benefit plans. In that role it handles information about plan members, which can include enrollment details, claims activity and other records tied to an individual’s health coverage. Most of those members have no direct relationship with the administrator, and they typically learn about a problem only when a notice arrives.
According to the company’s own public notice, dated April 3, 2026, Secure Health discovered on or about February 12, 2026, that an unauthorized third party had accessed its systems. The company says it promptly engaged outside specialists to help contain the incident and investigate its nature and scope. It also reports that passwords were changed, systems were resecured and additional protections were put in place. The investigation later determined that the unauthorized party may have gained access to certain files on or before February 3, 2026, which means the access began before the company noticed it.
The incident was reported to the U.S. Department of Health and Human Services on March 23, 2026, ahead of the company’s April 3, 2026 website notice. A public breach tracking summary of the federal filing lists 501 individuals as affected. That figure is the initial number associated with the regulatory report, and it may change if the company’s review of the files identifies additional people. Secure Health has also been tied to filings with several state regulators, which is common when plan members live in more than one state.
As of its April 3, 2026 notice, Secure Health said it was still conducting a comprehensive review of the files that may have been affected in order to determine what information was involved. The company said it would notify affected individuals and regulators as required by law. In other words, the notice did not list the specific categories of personal or health information that were exposed, and Secure Health has not publicly confirmed them in the material reviewed for this page. Readers should not assume any particular data type was or was not involved until the company says so in writing.
Secure Health set up a toll-free assistance line for questions about the incident. The line is staffed Monday through Friday during business hours Eastern Time, excluding U.S. holidays. The notice also directs potentially affected individuals to monitor their financial account statements and credit reports, to report discrepancies to law enforcement, and to consider credit freezes and fraud alerts with the three major credit reporting agencies.
It is worth understanding why incidents involving health plan administrators draw close attention. Administrators sit between employers, insurers and healthcare providers, and the records they maintain can combine identity details with coverage and claims information. That combination is valuable to criminals because it can support several kinds of fraud at once, including financial identity theft, medical identity theft and targeted phishing that references real coverage details. These are general risks associated with this sector, not confirmed facts about what happened at Secure Health.
The timeline here also follows a familiar pattern. A company detects unauthorized access, brings in outside specialists, secures its systems, and then spends weeks or months reviewing files to work out whose information was involved and what kind it was. During that review period, the public often has only a short notice with limited detail, which is why individual letters and regulatory filings matter as the main sources of specifics. The company’s statement that its file review was still underway as of April 3, 2026, means further details may emerge as that work finishes.
Federal health privacy rules require organizations that handle protected health information to notify affected people and regulators after a qualifying breach, and many states add their own notification requirements and deadlines. If you receive a letter from Secure Health, or from an employer or health plan referencing this incident, keep it. It will describe what was involved in your case and may explain any protection services being offered. If you believe your information may have been affected but have not been contacted, the toll-free line listed in the company’s notice is the most direct way to ask.
This page will reflect only what the company and regulators have made public. Where a detail has not been disclosed, we say so rather than speculate.
When Did This Breach Occur?
Secure Health says an unauthorized third party may have accessed certain files on or before February 3, 2026. The company discovered the unauthorized access on or about February 12, 2026. The incident was reported to the U.S. Department of Health and Human Services on March 23, 2026, and Secure Health posted a public notice on its website on April 3, 2026. At the time of that notice, the company’s review of the potentially affected files was still ongoing.
What Information Was Breached?
Secure Health has not yet publicly identified which categories of personal or health information were involved. Its April 3, 2026 notice states that a comprehensive review of the potentially affected files was underway to make that determination. Because the company is a health plan administrator, the files it maintains could include identity, coverage and claims information, but that is a general observation about the sector and not a confirmed finding about this incident. Affected individuals should rely on the notice they receive from the company for the specifics of their own situation.
What You Can Do
If you may be affected by the Secure Health incident, consider these steps:
- Review your financial account statements and credit reports for activity you do not recognize.
- Place a security freeze or fraud alert with Equifax, Experian and TransUnion.
- Request your free annual credit reports at annualcreditreport.com.
- Review explanation-of-benefits statements and provider bills for services you did not receive.
- Report suspected fraud to law enforcement, the Federal Trade Commission and your state Attorney General.
- Keep any notification letter you receive, and use the company’s toll-free assistance line with questions.
File a Data Breach Lawsuit Against Secure Health
If you received notice that your information may have been exposed in the Secure Health data breach, you may be entitled to compensation. Organizations that hold sensitive personal and health information are expected to take reasonable steps to protect it, and people affected by a breach can face a lasting risk of identity theft and fraud.
Contact us at Class Action U, where we’ll connect you with a lawyer skilled in class action lawsuits. If you’ve been contacted about this breach, received notice, or discovered you were impacted, fill out our quick, easy, and secure form to sign up. There is no cost to reach out to our legal partner and no obligation after speaking with someone from our team.