Maybe its just that they don't understand what they are doing, I don't want to place blame on somebody for doing something unawares. But it is extremely important nowadays to keep an eye out for these kinds of things.
You know who you are. I see what you're up to.
What that means is that, it's sort of like having a friend that says you are who you are. Someone may not trust you, but they trust your friend, so they'll accept you because they trust their friend. That's the extent of it. That's what a SSL certificate does primarily to maintain integrity.
The other thing it does is provides an encryption keypair, together with that trusted certificate, that the client and server can use to communicate. The strength will vary, but this can be done with a self-signed certificate just as well as a certificate from a proper provider. The difference is trusting that you are who you say you are.
This depends how you define it. Are you worried about IP addresses being logged? Because that happens in the web server's access log regardless of HTTP or HTTPS. Other than that, are you concerned about a man in the middle (MITM) attack? HTTPS does help with that, so long as you're not blindly clicking past security warnings.
HTTPS provides security, not anonymity. Proactive steps on your part like using a VPN and, most importantly, not providing identifying information about yourself are the most important part for that. If you must provide said information you want to do that across an encrypted connection, HTTPS, which aids in protecting your sensitive data. Of course, if the people on the other end aren't doing what they should be doing, it's irrelevant anyway--think LinkedIn, Ashley Madison, Equifax, etc. You better believe they used HTTPS, but they left the back door open.