One other little tidbit on this issue. After I have logged on to the myheritage web site and confirmed that a myheritage hint for a record is a match, the myheritage hint shows up as confirmed in RM even if I'm not logged on to myheritage at all - for example, if I have no browser windows open at all. This really reinforces the question of how this is all working.
As a reminder, I have no personal tree at myheritage at all, and RM is not storing my myheritage account number and password at all. And myheritage does not seem to have the concept of a community tree as does familysearch. All myheritage has is personal trees for each user. So myheritage is somehow or other remembering that the hint is confirmed, even though the match is between a record at myheritage and data on my PC's desktop, and even though I'm not in any way logged on to myheritage.
It's almost like there is a community tree that's completely invisible so that you can't see it, and that it's that's being constructed by myheritage any time you confirm a hint. I can't find anything in any of the documentation that's at the myheritage web site that addresses this issue. If I logon to the myheritage web site without using RM and if I create a personal tree, then it's very clear that the hints and their confirmations are associated with my personal tree. But I'm still totally puzzled about how this works when I don't have a personal tree at myheritage to which hint confirmations can be attached.
It does appear as if other RM users can see my hint confirmations. That is, if I use RM without being logged on to myheritage, then I see the hint confirmations. But since I'm not logged on and since RM doesn't have my myheritage account and password information, myheritage can't tell if I'm the user who posted the hint confirmation or not. Hence, all users must be able to see my confirmations even though I don't have a personal tree at myheritage.
Sorry to be beating this to death. But if myheritage is storing my hint confirmations in an invisible community tree, then it has to be storing information from my RM database on myheritage servers that I didn't explicity tell it to store. That's what I'm trying to figure out. In the case of familysearch, I finanally convinced myself that no data from my database was being harvested just because I was looking at hints. Which is to say, in the case of familysearch the individual in the community tree and the record to which individual in the community tree are being matched are both already there. And the hint is already there. All I'm doing is confirming that the hint is correct. But in the case of myheritage, it looks like the only thing that's already there is the record. The individual is not already there in myheritage because the individual is in my local copy of RM. And the hint conformation is not being stored in RM. Rather, the hint confirmation is being stored at myheritage. So it looks to me as if the only way this can work is for myheritage to store the data about the individual that is in my RM database as a part of the hint confirmation record on the myheritage servers.
The myheritage web site obviously has access to this data from my RM database when I'm confirming a hint. The reason I know this is that you can see my data at the myheritage site on the hint confirmation screen. And it's on the myheritage hint confirmation screen even though I don't have a tree at myheritage. So the API is obviously passing it through. And in order to keep a record of the hint confirmation, myheritage must be making some sort of permanent record of the data that was passed to from my RM database by the API.