Skip to main content

Panic From AdSense "Policy Breach Notice" EMail

Some blog owners, who use AdSense, received some very disturbing email this weekend.
This morning I received the following email from Google.
Dear Publisher,

We have now verified that we are no longer detecting PII being passed to Google from the account(s) under your control.

Thank you for helping to resolve this matter.


The Google Policy Team
What did I do, this time? Is my AdSense account in danger of being terminated?
And the email was labeled "Policy Breach Notice".

Fortunately, this was, apparently, just another episode of Google being Google.

Personally Identifiable Information, or PII, can be passed through some ads, hosted by AdSense.

Some time ago, AdSense Support identified a common mistake being made by some AdSense publishers, which can cause some AdSense ads to pass personal details about their Google accounts. AdSense Support refers to these details as "PII".

AdSense originally notified the negligent publishers of their mistakes, as a "Policy Breach Notice". This weekend, they followed up on their previous action, and advised some publishers that they were no longer in violation.

Presumably, they could have emailed only the publishers, who had made and corrected their mistakes - and thanked them for taking action. In this case, however, they emailed a large amount of publishers who had never made this mistake, and had never received an original "breach notice" - and who had no idea why they were now getting a "breach notice".

Whether the proper publishers received the "thank you" is a matter for speculation.

If you, or someone who you know, received a "Policy Breach Notice"
We have now verified that we are no longer detecting PII being passed to Google from the account(s) under your control.
This is good. You are not in violation of the PII Policy. Get back to work, on your blog. That said, you should be careful to check email, regularly - and look carefully for important email.

For progressing advice on this issue, AdSense Support suggests that you post in the main AdSense Help Forum topic - and / or read the advice provided there.
(Update 4 March): AdSense sent an update
Dear Publisher

Google recently sent you an email in English from, with the subject of "policy breach notice," regarding personally identifiable information.

The message was sent in error; we would like to convey our sincerest apologies for the alarm that this must have caused you and your colleagues.

You do not need to take specific action on this erroneous message however, due to the dynamic nature of publisher monetization we encourage you to periodically review our resources regarding PII.


Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: