If you are displaying the image on a page (whether it is on your site or somewhere else), then the link to the image has to appear in the source code of the page. Since the source code of the page has to be downloaded to the users computer in order for it to be shown in a browser, it can be viewed by the user. For example, if you view the source code of this page, you will see the links to all of the images. So, if you have an image being shown using HTML (eg <img src="
https://secure.server.lunarpages.com/~userid/yourgraphic.gif" />), viewing the source code of the page that has that image will show the servername and userid. If you entered that URL for the image somewhere (e.g. when setting up the custom paypal page), then it is probably in the source code of that page. Unfortunately, this is the way the web works...
I understand your concern about privacy, security, etc., but it is important to be aware that there are several other ways this sort of information (servername and username) could be obtained. A tracert to your domain will end with the server that you are on. (e.g. a tracert to lunarforums.com ends at galaxy.lunarpages.com). Any email that is sent out via LP's server will have your account name in the headers along with the servername (normally not displayed, but available by viewing all the headers). So really, although a personal SSL would mean you could link to
https://yourdomain.com/image.gif and not show the server/username that way, the info is still available in other ways to anyone who really wants to find it.
I guess the main thing that I'm trying to get across is that you shouldn't get a false sense of security by thinking that if you don't post your servername that no one can figure out what it is. At the same time though, having your servername known is not a huge security risk. Having your username out there is a little more of a risk, but provided you have a strong, secure password, it isn't somethign worth worrying about too much.
Glad you got everything working
