WARDPASS · WORKING DOCUMENT
Privacy Notice
A working draft for the WardPass public website. The bracketed details and live-service practices still need confirmation.
This draft only describes the public marketing website as currently implemented. It does not describe or govern the live WardPass application, university or NHS trust use, or any future connected data services.
1. Who is responsible for this website?
Controller: [insert the full legal name of the organisation responsible for the website, registered address and company number, if applicable]. Privacy contact: [insert a monitored privacy email address]. Confirm the controller role and contact details before publication.
2. Information handled by the marketing website
The current “Request a demo” form is a front-end preview. It displays an on-page confirmation but does not transmit or store the submitted name, work email or role. This statement must be reviewed if the form is connected to an inbox, CRM or other service.
The site includes Vercel Analytics in production. Confirm the exact analytics configuration, data collected, identifiers or cookies used, lawful basis, retention period, hosting region, opt-out method and relevant service providers before describing it as a live privacy notice.
The website links to the WardPass application. The application’s sign-in, learner records, placement, attendance, assessment and portfolio data are outside this draft and require their own accurate privacy information and appropriate institutional agreements.
3. Purposes and lawful bases
[For each live processing purpose, describe the information used, why it is needed, the applicable UK GDPR lawful basis, and whether the person must provide it. Do not publish this section until the organisation’s actual practices have been confirmed.]
4. Sharing, service providers and international transfers
[List each actual recipient and service provider, its role, the information it receives, and any international transfer safeguards. Confirm the hosting, analytics, email, CRM and other production configuration rather than relying on this draft’s technical observations.]
5. Retention and security
Retention: [state the actual retention periods or criteria for each category of information]. Security: [describe only the technical and organisational measures that are currently implemented and can be substantiated]. Do not add certification marks or security guarantees without current evidence.
6. Your rights and complaints
Add a clear process for exercising applicable data-protection rights and a response contact: [insert verified privacy email and process]. ICO registration: [include the verified registration number only if applicable; otherwise use wording confirmed by the responsible organisation]. Confirm the appropriate supervisory-authority and complaint information before publication.
7. Cookies, analytics and updates
[Describe any cookies, local storage or similar technologies actually used, their purposes, consent requirements and controls. State when this notice was last updated after the final details have been approved.]