They're perfectly entitled to track you as long as you don't opt out.
And when you opt out, they can't be held responsible for remembering it for even an instant, because they can't identify you.
"That's some catch, that Catch-22"
This is false, GDPR is opt-in.
Since you didn't opt in, you haven't allowed them to track you, and they can't remember that you didn't opt in without tracking you.
See?
Um ... huh? GDPR requires explicit consent.
Airtable did something similar recently with the grandfathered free accounts
If I'm trying to log in, I know that I have to go into Authenticator and approve, so just check if there are outstanding requests (e.g. with a 2 minute timeout) when I open the app.
The user interaction of classic TOTP forms an important grounding function: it forces (in most cases) spatial locality of the user and the device being interacted with.
Nevertheless, at the end of the day the buck always stops at the user. User have to be diligent and shall have no blind trust on anyone/anything.
For a disgruntled employee (most employees), getting hacked is a win-win.
Let's change names.
What if it's Google, Blizzard / Epic (Battle.net), and something personal? These services use the same flows.
Or worse, what if it's your e-Government app, and you lose all your identifying information and somebody can become "you" with all the information they got?
Will you say "Meh, it's a personal account, and I gave access via MFA, but who cares, it's not my problem?".
But that isn't working. Every time the user clicks no, a new notification pops up. Eventually the user learns: Clicking "no" does not work, it does not achieve his goal. If it hasn't worked 5 times, it probably won't work the next 100 times. So, the user tries something different.
(And the best part it: It works!)
The solution for this is obviously to provide a "no, and block requests until I open the app" button.