Cybersecurity News and Headlines
  • All Technology
  • AI
  • Autonomy
  • B2B Growth
  • Big Data
  • BioTech
  • ClimateTech
  • Consumer Tech
  • Crypto
  • Cybersecurity
  • DevOps
  • Digital Marketing
  • Ecommerce
  • EdTech
  • Enterprise
  • FinTech
  • GovTech
  • Hardware
  • HealthTech
  • HRTech
  • LegalTech
  • Nanotech
  • PropTech
  • Quantum
  • Robotics
  • SaaS
  • SpaceTech
AllNewsDealsSocialBlogsVideosPodcastsDigests

Cybersecurity Pulse

EMAIL DIGESTS

Daily

Every morning

Weekly

Sunday recap

NewsDealsSocialBlogsVideosPodcasts
CybersecurityNewsCall-On-Doc Allegedly Had a Breach Affecting More than 1 Million Patients. They’ve yet to Comment.
Call-On-Doc Allegedly Had a Breach Affecting More than 1 Million Patients. They’ve yet to Comment.
Cybersecurity

Call-On-Doc Allegedly Had a Breach Affecting More than 1 Million Patients. They’ve yet to Comment.

•January 24, 2026
0
DataBreaches.net
DataBreaches.net•Jan 24, 2026

Why It Matters

A breach of this scale threatens patient privacy, could trigger FTC and state enforcement, and undermines confidence in rapidly expanding telehealth services.

Key Takeaways

  • •Over 1.14 million records reportedly stolen
  • •Data includes names, contact, medical conditions, payment amounts
  • •No evidence of encryption; breach went undetected
  • •FTC may pursue unfair‑practice claims despite HIPAA status
  • •State notification deadlines could trigger multi‑state investigations

Pulse Analysis

The telehealth market has surged in the past few years, driven by consumer demand for convenient, remote care. Providers like Call‑On‑Doc tout robust security and HIPAA compliance to attract self‑pay patients who expect their health information to be protected. When a breach of over a million records surfaces, it not only exposes sensitive personal and medical data but also raises questions about the adequacy of the security measures that many firms claim to have in place. The alleged lack of encryption and delayed detection suggest gaps that could be common across the sector, especially among newer entrants that prioritize growth over mature security frameworks.

Regulatory scrutiny intensifies when a breach involves health information, even if the entity operates outside traditional HIPAA‑covered arrangements. Because Call‑On‑Doc does not accept insurance, its HIPAA status is ambiguous, yet the FTC can still pursue actions for deceptive or unfair practices under the FTC Act. Moreover, state data‑breach statutes—19 of which impose a 30‑day notification window—could compel multi‑state investigations if the data indeed span numerous jurisdictions. The company’s silence on the incident may exacerbate liability, as prompt notice to affected patients and regulators is a legal requirement in many jurisdictions.

The fallout from this incident could reverberate throughout the telehealth ecosystem. Patient trust is a critical asset; a high‑profile breach may prompt providers to reassess their security investments, adopt stronger encryption, and improve incident‑response protocols. Investors and insurers are likely to demand clearer compliance roadmaps, while competitors may leverage the situation to differentiate themselves on privacy safeguards. Ultimately, the Call‑On‑Doc case underscores the need for rigorous data‑protection standards as digital health continues to expand.

Call-On-Doc allegedly had a breach affecting more than 1 million patients. They’ve yet to comment.

Read Original Article
0

Comments

Want to join the conversation?

Loading comments...