IE6 just had to make it HARDER with their P3P compatibility. On top of that, my stupid domain name providers have some bizarre convention where they put the actual page (where https://vivin.net or http://www.vivin.com refers to) inside a STUPID FRAME. So when I run the P3P validator, it finds p3p.xml alright, but it’s inside a STUPID FRAME so it comes across as HTML to it…​ WHY ON EARTH WOULD ANYONE WANT TO SET IT UP LIKE THAT? I sent them an email…​ the bastards never write back…​ I hate them…​ I hate them so much…​ and I have another year with them…​ I’m going to go with register.com next year…​ Yeah so why did I do P3P? Because IE6 won’t take cookies otherwise…​ But then I FINALLY got it all to work…​ I was making the pop-up window open with reference to https://vivin.net so it was putting it inside that STUPID FRAME…​ I changed it and now it WORKS!!! WOOHOOO!!! P3P is still interesting though…​ Yeah so this site has P3P and you can read the policy here. The XML is here. I generated it using IBM’s P3P Policy Editor. It’s free and easy to use. I don’t understand half the legal stuff that’s in the Policy file…​ I just made it so that my cookies would work…​