We need to tell professional users who sign in to the ‘Manage connection requests’ service about the data we collect, process and store. This is because when they send a request, they provide their name, email and optionally a contact number. These details are held in the system and made available to the Voluntary and Community Sector (VCS) organisation who receives the request. They are also stored for up to 7 years after they make the request.
We also need to tell the family what information we hold about them, how long we store it and who has access to it.
To make sure everyone knows what information we collect, process and store about them, we need professionals to share a privacy statement with the family before they make a request.
We have added a page to prompt professionals to do this and then document, through answering a question, that they have the family’s permission to share their information.
The statement opens in a new tab so that:
- it does not interrupt the flow through the service
- it's easier to share with the family by email or by printing
It's also a page link that users do not need to be signed in to view.
The page content includes a summary of what the user can find out in the privacy statement.
You must share our privacy statement with the family before you can make a request.
The privacy statement tells them more about:
- what data we collect about them and why we need it
- who is responsible for data within the service
- how we protect, process and store their data
- how long we keep their data
- their personal data rights
Have you shared our privacy statement with the family?
- Yes
- No
We used inline radios from the Radios component on the GOV.UK design system. Inline radios have been used across the service and the options ‘Yes’ and ‘No’ are displayed beside one another as there are only two options.
We have worked with our Data Protection Officer and the Information Governance leads within our partner local authority areas to develop the content of our privacy statement. We will continue to iterate as we develop the content for the Terms and conditions.