ShareSF Guides: Privacy Notice
  • Introduction
  • When Should I Have a Privacy Notice?
  • How To: Create or Update a Privacy Notice
    • Step 1: People & Approach
    • Step 2: Develop the Content
    • Step 3: Check the Language
    • Step 4: Test, Roll Out, and Review
  • Final Note: Preference Management and Consent
Powered by GitBook
On this page
  • 4.1 Test
  • 4.2 Roll Out
  • 4.3 Review

Was this helpful?

  1. How To: Create or Update a Privacy Notice

Step 4: Test, Roll Out, and Review

4.1 Test

There is no better way to ensure your privacy notice is effective than to test it on a sample of users. You should seek user feedback on (at the very least):

  • how they used it;

  • if they found it easy to understand;

  • whether anything was difficult, unclear or they did not like it; or

  • if they identified any errors.

4.2 Roll Out

After amending to account for user feedback, you should be ready for roll out!

4.3 Review

After roll out, your should review your privacy notice on a regular basis and whenever you change or update a process involving personal information. Things to consider:

  • Is it accurate and up to date?

  • Are there complaints from the public about how you use their information and in particular any complaints about how you explain your use of their information?

  • Does it explain all of your current or planned uses of individuals’ personal data?

  • Does it need to be updated to reflect a new or amended process?

PreviousStep 3: Check the LanguageNextFinal Note: Preference Management and Consent

Last updated 5 years ago

Was this helpful?