13 September 2026
Privacy Policy
Venguard Ltd is being registered at Companies House. Company number, registered office and ICO number will be added here when we have them. Email info@venguard.uk.
This policy explains how Venguard Ltd uses personal data. It covers venguard.co.uk and the Venguard platform. That includes the Admin Centre, Staff Console, public reporting pages, Public App, Staff App and TV Display.
Who we are
Venguard Ltd is being registered at Companies House in England and Wales. We will add our company number and registered office here when registration completes.
We work from North-East Lincolnshire, United Kingdom.
Email: info@venguard.uk
We will add our ICO registration number here when we have it.
Who this policy is for
You might use Venguard in more than one way.
Website visitor. You read the site or send us an enquiry.
Customer staff. Your venue or organisation has an account. You sign in to run safety work.
Public reporter. You scan a tag or use the Public App to report a concern at a venue. You do not need an account.
Who is responsible for your data
Website enquiries. Venguard Ltd is the controller. We decide why we use that information.
Customer accounts and venue records. Your organisation is the controller. They decide what to keep on the platform. Venguard Ltd is the processor. We run the system for them.
Public concerns. The venue organisation is the controller of the report. Venguard Ltd is the processor. We pass the report to that venue and store it so staff can act and keep a record.
If you are unsure, email info@venguard.uk.
What we collect from the website
When you register interest we ask for full name, venue or business name, role, town or area, venue type, approximate capacity, email, phone if you give it, and any message you write.
The form currently opens your email app and sends that text to info@venguard.uk.
Our hosting logs the date, the page you asked for, your IP address and browser type. Those logs are kept for 30 days.
The site loads fonts from Google. Google may see your IP address when the page loads.
We do not use advertising tools on the website.
What we collect from the platform
If you are customer staff we may hold your name and email, organisation, venue and role, sign-in data from our identity provider Clerk, a PIN hash if you approve alerts, training records and uploaded evidence, actions you take with time, IP address and browser type, messages you send on a concern, and photos you upload as evidence.
If you are a public reporter we may hold the concern type you chose, the zone you chose or that the zone was not known, a description if you wrote one, and a photo if you sent one. We strip extra camera data such as GPS from the file. We also hold chat messages you send after you report, and a concern reference. Anyone who has that reference can open the chat for that report.
The Public App may create a short-lived record that an installation is present at a venue. That is used only to send the right alert. The Public App does not send your raw GPS to us. It does not keep a history of venues you visit.
We do not ask public reporters for a name or email.
TV Display installations hold a pairing record for that screen. They do not identify a person.
What we do not collect
We do not sell personal data. We do not use the platform to track members of the public around a venue. We do not ask children for an account.
Why we use personal data
Website enquiries. To reply to you and talk about Venguard for your venue. Lawful basis: legitimate interests, or a step before a contract if you ask for a quote.
Customer accounts. To provide the service, keep the account secure, and meet our contract. Lawful basis: contract, and legitimate interests for security logs.
Public concerns. To deliver the report to the venue and keep an audit trail. The venue relies on its own lawful basis. We process that data on the venue's instructions.
Legal duties. We may keep records if the law requires it.
Who we share data with
We use other companies to run the service.
- Amazon Web Services. Hosting and file storage in the UK, region eu-west-2.
- Clerk. Sign-in for staff.
- Apple and Google. Push notifications to phones, when you use the apps.
- Email delivery. Invites and system mail.
We do not sell your data. We only share it with a venue's own staff who have permission, with a supplier who needs it to run the service, or if the law requires it.
A venue can export its records for a regulator or an insurer.
Where data is stored
Platform data is stored in the United Kingdom on AWS, region eu-west-2.
Clerk is a US company. Staff sign-in data may leave the UK. Clerk uses contracts approved for international transfers.
The marketing site uses Google Fonts. That request may leave the UK.
How long we keep data
Website hosting logs: 30 days.
Website enquiries: while we need them to reply, and for a short time after, unless you ask us to delete them.
Platform records: for as long as the organisation's account needs them for safety and compliance. If the organisation leaves, we delete or return their data after a short wind-down, unless the law says we must keep it.
Concern photos and chat stay with the concern record until the organisation deletes them or the account ends.
Venue presence records expire after a few minutes.
Your rights
You can ask to see your data, correct it, delete it, limit how we use it, or object to some uses. You can also ask for a copy to take elsewhere.
If we are the processor, we will pass your request to the organisation that controls the data, or tell you who to contact.
Email info@venguard.uk.
You can complain to the Information Commissioner's Office at ico.org.uk.
Children
The website and staff tools are for organisations, not for children. A young person at a venue might still use a public reporting tag. We do not ask them for an account or extra personal details.
How we keep data safe
We use encrypted connections, role-based access, and audit logs. Concern photos have extra camera data removed. Public reporting does not require an account. Raw GPS from the Public App stays on the device.
No system is perfect. If a breach is likely to put people at risk, we will tell the ICO and affected people when the law requires it.
Changes
We will update this page when the service or the law changes. The date at the top will change.