Adsense and profanity

[lcampers]

I want to post an article a friend wrote but it has 'some' profanity in it. Google's tos states that it does not allow "excessive profanity." Does anyone know where this line is/can be crossed? The article is well written and humorous but tends to stray into a few profanity containing statements.

I don't want to edit them out if I don't have to but am fearful of bringing down the wrath.

Should I just replace them with $%*#)...

#*$!

thanks.

[Bates]

You're probably pretty safe if the article is somewhat tasteful. "Excessive profanity" leaves some space to play.

[greatstart]

I think they are talking about using 4-letter words in every sentence. Maybe one or two is OK? I try not to use any, as many kids like to surf my sites.

[timchuma]

What about if you sub-domain name has a profanity in it?

I don't want to put ads on that part of my site anyway, especially the lyrics for #$%# the #$%#*(^ #$%#$% you #$%# the #$%#$%^ #$%##@# #$%#$%.

[swa66]

Acually I'm still fearful of this problem on my website that needs placenames and route numbers to describe something. But some placenames and some numbers are plain and simply written in exactly the same manner as some bad words.

I'm talking about e.g. Hooker, MO, Devil's Elbow (also in Missouri and actully right next to the previous, US-666 (which got renamed recently out of political correctness).

It gets worse when you know there is a pass there over a mountain that got a rock cut in it, that normally are all referenced with the place name in front of it (but to cut down on the bad words here ...)

I didn't invent those placenames, so I don't think they are a real problem to use. But they just happen to be bad words as well ...

Main problem I see popping up is when an algorithm spots those placenames. ... I do hope Google is smart enough (but I fear AI is still way to primitive to spot the difference)