How do I REMOVE this ECG and it's two step authorization ????

Farron said:

This is a viable idea even if I don't see any difference with my other data ( HRV, heart rate, age, weight, etc.)
Why now the rather meaningless curve of an ECG must be additionally protected by 2FA! eludes my understanding after data security.

I don't understand it either. Their is no difference.

Lets look at an activity for example... say a walking activity. I make mine public, so anyone can see them. They can see my HR, pace, distance, etc... they can even see my GPS track, so they know exactly where I walked.

But ECG requires 2FA?

If there actually was a government regulations, wouldn't all the other manufacturers of devices that had ECG require 2FA?

Garmin - Chris said:

Our competitors also require Two Factor Authentication:

I might well be splitting hairs here but reading through this - https://support.apple.com/en-us/HT208955 gives no indication that 2FA is required to take an ECG with the Apple Watch. This link - Health Data in the Apple Health APP appears to apply only to the sharing of personal ECG information. I can't find anything to suggest that it is needed for Samsung ECG either.

Anyway, I'm going to bow out of this discussion as the 2FA requirement really doesn't bother me. It's more the lack of clarity around the differences between Garmin's insistence on 2FA for ECG and the absence for that need with other manufacturers.

Moderator: Final comment on this thread and two factor authentication.

An official answer has been given that is coming from the highest level. Thank you for the feedback. We appreciate it. Two Factor Authentication will continue to work the way it does now and when anyone adds ECG to their watch, the step to SKIP syncing to Garmin Connect and turning on Two Factor Authentication is an option.

Hmmm, if the 2FA is necessary, I see the field to enter the code, at this moment I got the code (vis SMS) on my watch, I tread it, fill the code in and ready ...

very simple ...

Whatever the case, I have gone back to using my AWU, and have my Epix Pro 51mm up for sale on Facebook market place.

We wish you the best going back to your Apple watch. I hope your Epix Pro will sell quickly.

I just bought a Venu 3 for my mum, who has a history of AFib, so her account is now locked in 2FA. A bit of constructive feedback on the process:
1. The note when setting up irreversible 2FA should be a bit clearer in describing what happens when you press "Skip" (you shouldn't have to read through these forums)
2. I know it's regulatory from the FDA, but perhaps in your next conversations with the FDA, try to get approval for a process to delete all ECG data in a GC account and allow people to disable their 2FA after that.
3. E-Mail and SMS are the most annoying forms of 2FA for me, please add a TOTP option.
4. The whole 2FA only becomes are real issue, because a lot of services use some forms of undocumented APIs to access data in our Garmin accounts. I would argue that these services are vital for the whole ecosystem around Garmin, so while I know it's longstanding policy not to offer proper APIs for third parties, maybe reconsider that because all those services will otherwise be inaccessible for a lot of users.

As a very long time Garmin user, and someone who usually jumps on every update or new feature, I have to say that this situation has not been handled very well at all by Garmin.

Whether or not the ECG feature constitutes a medical device, and whether or not 2FA is really required by the FDA, is beside the point. The point, at least for me, is that Garmin introduced a new feature with much fanfare, and did not take adequate measures to inform its customers that, by initiating that feature, they were taking a completely irreversible path towards 2FA.

To my knowledge, there has never been a feature on any Garmin device which would, once initiated by the user, result in an irreversible consequence. As such, it was incumbent on Garmin to make absolutely sure that users were informed of this new and unprecedented behaviour. Garmin has failed miserably in this regard.

It is disingenuous, at best, for Garmin to hide behind its FDA approval in defending itself on this issue. The real issue has little to do with the FDA. The real issue has to do with Garmin's failure to properly communicate the unintended and unwanted consequences of this change for many, many users.

Garmin owes its customers a more meaningful response than to say, "The highest powers have determined that we will do nothing about this." The simple reality is that Garmin could easily do a reset and make everyone happy by allowing users to remove the ECG feature and its associated data and remove the 2FA. Then, Garmin could properly communicate the consequences of initiating the ECG feature such that users are able to make a fully informed decision as to whether or not to use this feature.

Why Garmin has chosen to stick it to its loyal customers on this issue and refuse to be reasonable is beyond me. But, as a very longtime and loyal Garmin customer, with many, many Garmin devices in my stable, this is extremely disappointing.

I am not leaving Garmin over this, because I am not directly impacted, but if I was directly impacted, I would be seriously considering whether to stick with Garmin devices going forwards.

Extremely well said.