DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Update: QxMD fixes privacy problem in Calculate

Posted on November 10, 2013 by Dissent

On  October 30, PHIprivacy.net linked to an article on PCMag that described a review of an app, Calculate, by QxMD. The reviewer, Appthority, had found that “the registration and setup sends the doctor information, such as name, e-mail, and location over the network in plaintext,” despite the app’s assurance that all information was encrypted. At the time, I commented:

There are no identifiable patient data involved, but even so, if your policy says ALL info is sent encrypted, the doctors’ information shouldn’t be in plaintext, right? This could actually be the basis for a complaint to the FTC if the privacy policy is inaccurate in a material way. I’m not suggesting a complaint should be filed, but just that the app may need to either re-write the privacy policy (if the reviewer was accurate about plaintext) or re-code so that all data really are transmitted encryption. I think we all know which option is preferable.

Today, I received an e-mail from Daniel Schwartz, MD, FRCPC, the Medical Director of QxMD. It says, in part:

You correctly noted that Appthority identified several legacy tracking tools we had been using and, unfortunately, not yet disabled.

[…]

We take privacy very seriously and sincerely regret that any user data was transmitted in an unencrypted fashion. It should be made clear that no patient specific identifiers were ever collected or transmitted. In fact, Calculate is meant to be an educational tool to support clinical decisions at the point of care and is purposely not integrated with patient databases. As such, no patient data was ever at risk.

In response to the security bulletin posted by Appthority, we immediately took action. As of November 4, 2013, Google Play has an updated version of Calculate that ensures user data cannot be intercepted.

I’m glad to hear that QxMD took prompt action to correct the problem Appthority had pointed out. And this is a great example of: (1) why apps need to encourage independent entities to review their code for security and privacy, and (2) why we should all be grateful to researchers who do investigate and share their findings with consumers and health care professionals.


Related:

  • CISA Alert: Reported Supply Chain Compromise Affecting XZ Utils Data Compression Library, CVE-2024-3094
  • System Status Note
  • System Status Note
  • System Status Note
  • Fraudster's fake data breach claims should remind media to be careful what we report
  • "Pompompurin" taken into custody after violating conditions of pre-sentencing release on bond (1)
Category: Uncategorized

Post navigation

← Tool to determine if your email address was in the Adobe data dump
"Small" breach, big harm. →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.