Update the privacy policy
Publish a new version of a privacy policy, say whether it changes what people agreed to, and bring the forms linked to it up to date.
Publish a new version of a privacy policy when its wording changes. You then say whether people need to be asked again. Every form linked to the policy that still shows an earlier version is listed, so you can bring it up to date.
Publish the new version#
- Open Settings, then the Policies tab.
- Choose the policy and change its wording or its link.
- Under Kind of change, when you publish, choose one of the options below.
- Choose Publish.
| Option | When to choose it |
|---|---|
| Wording only: nothing new is asked of anyone | Clearer sentences, a new address, corrected names. Earlier answers stand. |
| Material: what people agreed to changes | New data, a new purpose, a new recipient or a longer time you keep data. |
The console says how many linked forms now show an earlier version. A form records which policy version it showed, so its records keep proving what each person read.
Bring the forms up to date#
The notice appears on the Policies tab and on Consent forms. It lists each form with the version it shows and its current records.
- Read the forms marked has unpublished edits. Open each, review the draft and publish it yourself.
- For the other forms, choose Republish and ask again after a material change, or Republish with the new policy after a wording change.
- To tell people who answered earlier without asking them again, choose Start a notice campaign.
Republish and ask again publishes each form through the usual publish step and asks every returning visitor again. If your project needs a second person to publish, each form waits for approval instead. The notice goes once every linked form shows the new version.
What your systems receive#
Each publication sends one policy.published webhook. It names the policy, the version, the kind of change, the forms that show an earlier version and how many current records rest on them.