Skip to main content
GOV.UK Verify

Comment moderation and privacy guidelines

The commenting functionality on this blog will be deactivated during the pre-election period.

When posting comments, please observe our site participation guidelines:

  • do not post personal or possible identifying information in comments such as addresses, phone numbers, email addresses or other online contact details, which may relate to you or other individuals
  • be respectful of others who use this site
  • stay on topic
  • keep comments concise
  • do not use language that is offensive, inflammatory or provocative (this includes, but is not limited to, swearing and obscene or vulgar comments)
  • do not break the law (this includes libel, condoning illegal activity and contempt of court)
  • do not use this site for party political purposes (this site is paid for with public money so it's inappropriate to engage in party-political activity)
  • do not impersonate or falsely claim to represent a person or an organisation
  • do not attempt to log on using another user’s account
  • do not make any commercial endorsement or promotion of any product, service or publication not relevant to the discussion

If you are aged 16 or under, please get the permission of your parent or guardian before participating. Users without this consent are not allowed to participate.

If you require support for GOV.UK Verify or would like to provide feedback, please submit a user support request here.

Moderation policy

Blog comments are pre-moderated to check they comply with the GDS blog participation guidelines above. If comments don’t comply they will not be published.

Here is a brief outline of how we evaluate comments.

Is this comment on topic, does it add value to the discussion and can GDS answer publicly?
If so, post a timely response within 24 hours.

Is this person asking for information or detail relating to another GDS channel?
If so, we'll pass the query on and ensure it is dealt with as quickly as possible. We will update the user on progress.

Does this comment raise an issue with a tool or transaction? Or is it reporting a bug or performance problem?
If so, alert the GDS team responsible for fixing the tool, transaction or issue and tell the user this has been done.

Is this comment a rant at GDS venting frustration or anger?
If so, STOP, monitor and discuss with the digital engagement team first, referring to the participation guidelines.