II think you misunderstood what I was saying. When Scrivener, via the Paddle software/API or whatever is used, sent the V1 code to Paddle for verification. Paddle detected that it was not valid for Scrivener3. That much at least did happen.
At that point the Paddle system should have checked to see if it qualified for the free upgrade and, if so, generated a new V3 key, responded to Scrivener that the key is valid and also sent me an email to advise of the new V3 key for my own records. It’s Paddle that should have done all that, not Scrivener.
There are no privacy issues or any other problems associated with such a process. Paddle already have all the details they require, otherwise, the upgrade code could not have been generated. No new information about me needs to be sent anywhere. Scrivener and L&L would not be involved in the process at all.
As for the technical side of such a process, it’s trivial to implement in code. I have implemented such systems myself and can therefore speak from experience.
I’ll drop the subject now and simply wait for support to respond.