Kensington Palace defends Prince Harry's press attack over Meghan Markle coverage

The support comes days after Prince slammed media organisation for intrusion in his private life


Entertainment Desk November 10, 2016
PHOTO: PEOPLE MAGAZINE

The Kensington Palace has defended Prince Harry's statement slamming media intrusion into his relationship with US actor Meghan Markle.

Guardian reported.

The 32-year-old prince urged media organisations to refrain from "further damage" as he blasted the smears and "racial undertones" appearing in newspaper articles.

Prince Harry issues rare statement to slam media intrusion over new girlfriend

Harry also said he remains uncomfortable with public interest in his private life, which has rocketed since rumours began circulating that he was dating television actress Markle, 35, who is best known for her role as Rachel Zane in the US TV drama Suits.

Several journalists hit back at the prince's reservation regarding media coverage and desire for privacy quoting that his public status "comes at a price".

Prince Harry's girlfriend Meghan Markle will not fit in Royal family, her half-sister claims

However, a source close to the prince said the palace did not accept their arguments and stressed he was trying to defend Markle, not himself, from unwanted coverage.

“All this is not for him,” the source said. “He was asking to protect someone else and their privacy, someone he has been in a relationship with for a few months.”



Prince Harry dating Suits actor Meghan Markle?

Meanwhile, Markle also penned down a letter to the British media regulator complaining about press intrusion into her personal life. The Suits actor said she has been subject to harassment from journalists abroad and is bothered by news published about her in the media.

This article originally appeared on the Guardian.

Have something to add to the story? Share it in the comments below.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ