![]() |
|
|
|
|||||||
| Home | Chat | Register | FAQ | Calendar | Mark Forums Read |
| General Development General Development |
|
|
Thread Tools | Display Modes |
|
||||
|
Finally getting round to adding privacy statements to my websites as required by Adsense's (not so) new T&C, also in the process of moving a large portion of my sites from parking to mini sites, which all need privacy statements.
Easy way i found to implement a personalized privacy page to use the following: Save as privacy.php and upload to your server: Code:
<title>Privacy Policy</title> <body style="font-size:12px;"> <div style="padding:18px; margin:20px;"> <p><strong style="text-decoration:underline; font-size:14px;" >Privacy Policy</strong> - <span style="color:#666666;"><?php echo $_SERVER['SERVER_NAME']; ?></span></p> <p>The privacy of <?php echo $_SERVER['SERVER_NAME']; ?> visitors is important to us. At <?php echo $_SERVER['SERVER_NAME']; ?>, we recognize that the privacy of our visitor’s personal information is important. <br> <br> Here is information on what types of personal information we receive and collect when you visit <?php echo $_SERVER['SERVER_NAME']; ?>, and how we safeguard your information. We never sell your personal information to third parties.</p> <p><strong>Log Files </strong><br> We collect and use the data contained in log files. <br> <br> The information in the log files include your IP (internet protocol) address, your ISP (internet service provider, such as AOL or Shaw Cable), the browser used to visit our site (such as Internet Explorer or Firefox), the time you visited our site and which pages you visited within our site. </p> <p><strong>Cookies and Web Beacons </strong><br> We do use cookies to store information, such as your personal preferences when you visit our site. <br> <br> This could include only showing you a popup once in your visit, or the ability to login to some of our features, such as forums. </p> <p><strong>Third Party Advertisements </strong><br> We also use third party advertisements on <?php echo $_SERVER['SERVER_NAME']; ?> to support our site. <br> <br> Some of these advertisers may use technology such as cookies and web beacons when they advertise on our site, which will also send these advertisers (such as Google through the Google AdSense program) information including your IP address, your ISP , the browser you used to visit our site, and in some cases, whether you have Flash installed. <br> <br> This is generally used for geotargeting purposes (showing New York real estate ads to someone in New York, for example) or showing certain ads based on specific sites visited (such as showing cooking ads to someone who frequents cooking sites). </p> <p>You can choose to disable or selectively turn off our cookies or third-party cookies in your browser settings, or by managing preferences in programs such as Norton Internet Security; however, this can affect how you are able to interact with our site as well as other websites. </p> <p>This could include the inability to login to services or programs, such as logging into forums or accounts.</p> <p> </p> <p> >> <a href="/" title="Return To <?php echo $_SERVER['SERVER_NAME']; ?> Home">Return To <?php echo $_SERVER['SERVER_NAME']; ?> Main Index</a></p> </div> </body> Then: in the footer link to the policy: Code:
<a href="privacy.php">Privacy Policy</a> Using the above should speed up the process a bit.. Ideally would be great if could convert the punycode to unicode 'on the fly', but that os over my head. Not actually sure if that is even possible.. Maybe would be useful if we could get native translations of privacy policies? |
|
|||
|
From SEO perspective it might not be in your best interest to put all that English content on some of your exclusively (language x) sites.
Not to say that privacy policies are a bad idea if taken seriously, especially for sites that collect non-trivial user information; but you're putting a block of standardized English-language content on all of your sites? |
|
|||
|
has anyone heard of google enforcing this rule? i got one site not updated yet, still too lazy to play with the code - site bought from someone else.
|
|
||||
|
You could always use the "Privacy Policy Generator" that I created specifically for the changes in the TOS of Adsense. http://www.serprank.com/privacy-policy-generator
I have not heard myself of this rule being enforced yet, but I am sure it will only be a matter of time. Hopefully, Google will send out warning to sites who have not yet complied, rather than simply ban their Adsense account. Alex
__________________
"She thinks I'm a nice guy. Women always think I'm nice. But women don't want nice. Why is nice bad? What kind of a sick society are we living in when nice is bad?" George Costanza |
|
||||
|
Quote:
Like i said, would be good if people could share native language privacy policies to this thread. If you have a Thai privacy policy fell free to share here Quote:
Quote:
Add no follow to link: Code:
<a href="privacy.php" rel="nofollow">Privacy Policy</a> Code:
User-agent: * Disallow: /privacy.php Quote:
|
|
|||
|
I think you're not seeing the forest for the trees. When I can run adsense on my Thai sites I still won't bother doing this because nobody cares including the big G.
Privacy policies were discussed in the late nineties, if memory serves, as a way to not just publish data collection and retention policies, but allow user agents to act on it based on your personal tolerances. IE4 I think it was, started down that path, but nobody cared. It never turned into a real (let alone useful) standard, it just became a place to publish some soothing talk aimed at nervous types who can't get to sleep. Having said that, published privacy policies remain a very good idea if you collect and store semi-private information associated with identifiable users, and not simply in the aggregate. Anything beyond that, like storing credit card numbers with usernames and you'd better actually take data management seriously; like reconsider your need for the data and re-think your retention policies. If that's your site I'm describing, you need to publish your policies accurately and concisely, and consider your site a target [and act accordingly!] Privacy policies, in my humble O, are counterproductive if you're just saying "we store cookies on your machine but we don't keep any bad info, we're nice!" This sort of thing should not generally be encouraged. |
|
||||
|
Quote:
Sort of like how the secret police used to operate in Poland, Romania, etc. . |
|
|||
|
Quote:
|
|
||||
|
Quote:
. |
|
|||
|
Very useful, thanks
. |
| Thread Tools | |
| Display Modes | |
|
|