Privacy Statements

This functionality provides you with the ability to add a privacy statement the user needs to agree to:

1. At the point of account creation

2. At the point of registering to link to a given department

Account wide Privacy Statement

The first of these, i.e. that which is shown to all users upon login is managed in OneVu Control > Privacy Statement as shown below:

Because this statement maybe long there is the ability to use HTML to better layout/structure the content with bullets etc.

Once a privacy statement has been added at this level the user must agree to the terms prior to being able to access their account:

NOTE

It is not mandatory to have this functionality i.e. you do not need to add a privacy statement if you are handling this elsewhere for global, cross council purposes.

Department Specific Privacy Statement

There is also the ability in this release to add custom messages for any department where the customer is authenticating. This could be useful if a department has specific nuances on data usage. E.g. Council Tax has the Local Government Finance Act and underpinning legislation which is only relevant for that department.

You can see this as a button when on the registration screen below:

Note that if you have a privacy statement present for a department, the 'Register' button is greyed out until the privacy statement is agreed to.

To set up a privacy statement for a specific department you need to go to OneVu Control > Data silos and select the department. In the case below it is Council Tax. You can see there is a section for 'Privacy statement configuration'.

The privacy statement added at department level manifests itself as follows when the button is clicked. Once this is checked/submitted the user can click register.