Back to sign in

Privacy Policy

How personal data is handled in the TruEye web console, the TruEye Operator mobile app and the rest of the TruEye platform.

Effective date:
24 October 2026
Last updated:
31 October 2026

Contents

  1. 1. About this policy
  2. 2. Who decides how your data is used
  3. 3. What we collect
  4. 4. The mobile app and your phone
  5. 5. How we use personal data
  6. 6. Analytics and AI features
  7. 7. Who we share it with
  8. 8. Where your data is held
  9. 9. How long we keep it
  10. 10. How we protect it
  11. 11. Cookies
  12. 12. Your rights and choices
  13. 13. Children
  14. 14. Changes to this policy
  15. 15. Contact

1. About this policy

This Privacy Policy explains how personal data is handled when you use TruEye: the web console, the TruEye Operator mobile app, the APIs and the edge agent software (together, the “Service”). TruEye is provided by VertexPlus Technologies Limited (“TruEye”, “we”, “us”).

It is a notice, not a contract. Use of the Service is governed by the Terms of Service. Where a customer has agreed separate terms with us about how we process data on its behalf, those terms govern that processing.

2. Who decides how your data is used

TruEye is sold to organisations (each a “Customer”), which connect their own cameras and recorders and decide who gets an account. For the video, images and analytics from those cameras, and for the accounts a Customer creates, the Customer decides why and how the data is processed. We process that data on the Customer’s behalf and on its instructions.

So if you appear in a Customer’s footage, or your employer gave you a TruEye account, questions about why footage is recorded, who may view it and how long it is kept are best put to that organisation. We will help it answer, and we will pass on any request we receive about its data.

We decide how data is used for our own purposes: securing and running the Service, answering support requests, and billing.

3. What we collect

  • Account details: your name, work email address, organisation, role and the sites and cameras you may access, and, if your organisation uses single sign-on, the identifier your sign-in provider gives you. Your password is stored only as a one-way hash. If you sign in with a password, you must also use two-step verification; the secret behind your authenticator app is stored encrypted.
  • Sign-in and activity records: your sign-in sessions; failed sign-in attempts and lockouts; if you choose to trust a browser or phone for two-step verification, a description of it (its user agent); and an audit log of significant actions, such as viewing or exporting recordings and changing settings. Your IP address is used to slow down repeated sign-in attempts.
  • Video, images and analytics: the video recorded by a Customer’s cameras (with sound, where a camera records it), still images taken from it, and what the analytics detect in it: people, vehicles, objects, events and sounds. Video and images can show identifiable people. To make footage searchable, the analytics also produce numerical descriptions of what they detect, which can be used to find the same person or vehicle on other cameras. Where a Customer turns them on for a camera, this also includes face recognition (which makes a numerical template of each face it detects and compares it with the people the Customer has enrolled), number-plate recognition, pose detection and attendance records.
  • Content you add: incident reports, notes, labels, handover notes, and the photos, voice memos and body-camera clips you attach in the app.
  • Questions you ask: what you type or say to Ask, the assistant built into the Service.
  • Mobile device data: a push notification token so alerts can reach your phone, your phone’s model and operating system version, the app version, and a random identifier for the app on your phone that labels body-camera uploads. If crash reporting is turned on in the app, a crash report (the error, device and app details, your user ID and organisation, but not your name or email address) is sent when the app crashes.
  • Support and business contacts: what you send us when you ask for help, and the contact details of a Customer’s administrators and billing contacts.

4. The mobile app and your phone

The TruEye Operator app asks for access to parts of your phone only when you use a feature that needs it, and you can refuse or withdraw that access in your phone’s settings:

  • Camera: to take photos and body-camera clips that you attach to incidents and handovers, to scan the QR code on a camera you are adding, and, where your organisation uses face recognition, to photograph a person being enrolled.
  • Microphone: to record a spoken question for Ask, a voice memo on an incident, or the sound on a body-camera clip. It records only while you are recording.
  • Photos: to attach photos or videos you choose from your library. The app sees only the ones you pick.
  • Face ID or fingerprint: to unlock the app. Your phone checks it; we never receive your face or fingerprint data.
  • Notifications: to alert you to alarms and events. Notifications are delivered through Expo’s push service and Apple’s or Google’s notification service. What a notification shows on your lock screen stays general unless your organisation chooses to show more.
  • Location: the app does not ask for or collect your location. Its map shows your organisation’s sites, using Apple Maps on iPhone and Google Maps on Android.

The app contains no advertising, does not use your phone’s advertising identifier, and does not track you across other companies’ apps or websites. It keeps your sign-in in the phone’s secure storage.

5. How we use personal data

  • to provide the Service: recording, playback, analytics, alerts, reports and Ask;
  • to sign you in, keep accounts secure, and detect and investigate misuse;
  • to answer support requests and tell administrators about changes to the Service;
  • to bill Customers and keep business records;
  • to comply with the law and respond to lawful requests.

We do not sell personal data, and we do not use it for advertising. We do not use a Customer’s video, images or labels to train AI models for anyone else.

6. Analytics and AI features

Video analytics run on our servers or, where a Customer installs one, on its edge agent on its own premises. Where a Customer turns on written descriptions of snapshots, they are produced on our servers too.

Ask answers questions with a language model run by Groq, an outside provider in the United States. What you type, and details of the events and cameras your question is about (but not images or video), are sent to Groq to produce the answer. If you ask by voice, the recording is sent to Groq to turn it into text; we do not store the recording.

Analytics results are probabilistic. They produce false positives and miss things, and a person should review an alert, a recognition or an answer from Ask before acting on it. The Service is not a life-safety system.

7. Who we share it with

Inside a Customer, people see what their role and site access allow. Outside it, we share personal data only with:

  • Service providers that run parts of the Service for us: Hetzner (servers and storage), Groq (Ask and voice transcription), Expo (delivering notifications and app updates), Apple and Google (delivering notifications, and maps in the app), and, if crash reporting is turned on in the app, Sentry (crash reports).
  • Authorities, when the law requires it. Where we can, we refer the request to the Customer whose data it is.
  • A buyer or successor of our business, under the same protections as this policy.

A Customer can also send alerts and recordings to services it chooses, such as email, Slack, Microsoft Teams, WhatsApp or its own security systems, and can export a clip as evidence. Those are the Customer’s decisions.

8. Where your data is held

Our servers are in Finland, in the European Union, and are operated by Hetzner. Ask and voice transcription are processed by Groq in the United States, and notifications pass through Expo, Apple and Google. Your data may therefore be processed outside your own country.

A Customer that installs an edge agent keeps the recordings that agent makes on its own premises.

9. How long we keep it

Where a period below is a default, a Customer can change it. A legal hold pauses deletion of the data it covers.

  • Recordings are kept for the retention period and within the storage allowance set for each camera, then deleted automatically, oldest first. An edge agent on a Customer’s premises overwrites its oldest recordings as its storage fills.
  • Events, alerts and notifications: 90 days by default.
  • Face recognition: records of recognised faces 90 days, and faces that were not recognised 30 days, by default. A person’s enrolment is kept until the Customer removes it, or until an expiry date the Customer sets for it.
  • Body-camera uploads: 30 days by default.
  • Incident reports, the evidence attached to them, and number-plate reads have no default period. They are kept until they are deleted, or, for evidence, until a retention period the Customer sets.
  • Account details are kept while the account exists. A removed account can no longer sign in, but its name and email address are kept so the audit log still shows who did what. They are removed when the Customer’s administrator or data protection officer erases the account, which also deletes its phone registrations and preferences.
  • Audit logs: 365 days by default. They can outlive the deletion of a Customer’s other data, because they are the record of who did what.
  • Backups: data deleted from the Service can remain in backup copies of the database until those copies are deleted.

When a Customer’s subscription ends, we delete its data as its agreement with us provides.

10. How we protect it

Connections to the Service are encrypted in transit. Signing in with a password also needs two-step verification; where an organisation uses single sign-on, its own sign-in provider handles that step. Access is limited by role and by site, video is played through short-lived links, and significant actions are recorded in an audit log. Only staff who need it to run or support the Service can reach Customer data.

No system is perfectly secure. If you believe your account or data has been compromised, contact security@trueye.io straight away.

11. Cookies

The web console sets cookies to keep you signed in, to complete single sign-on, and to remember a browser you have chosen to trust for two-step verification (for up to 90 days). It sets no advertising or analytics cookies.

12. Your rights and choices

Depending on where you live, you may have the right to see the personal data held about you, to correct it, to have it deleted, to receive a copy, to object to or restrict some uses of it, and to withdraw consent you have given. You may also complain to the data-protection authority where you live.

  • Your account: ask your organisation’s administrator or data protection officer, who can export or erase the data held about your account from the Service, including from the Privacy screen in the app. To ask for your account to be deleted, use the account deletion form, which tells them for you. You can also write to privacy@trueye.io. We may keep what the law or a legal hold requires us to keep.
  • Footage of you: ask the organisation that runs the cameras. If you write to us instead, we will pass your request on to it.
  • Grievances: if you are unhappy with how your personal data has been handled, write to privacy@trueye.io with “Grievance” in the subject line.

We may need to confirm who you are before acting on a request.

13. Children

The Service is for organisations and their staff, and is not meant for anyone under 18. Cameras can still record children who pass in front of them; that footage is handled like any other, under the control of the Customer that runs the cameras.

14. Changes to this policy

We will update this policy when what we collect, who we share it with or where we hold it changes, and change the “Last updated” date above. Where a change is significant, we will also tell Customers’ administrators through the Service or by email.

15. Contact

Questions about this policy or your personal data:

  • Privacy and data protection: privacy@trueye.io or dpo@trueye.io
  • Security reports: security@trueye.io
  • Support: support@trueye.io

Get in Touch

  • Sales Enquiries: sales@trueye.io
  • General Contact: contact@trueye.io
  • Sales Phone: +91 723 002 7503
  • General Phone: +91 723 088 9911
  • Main Line: +91 7230 926 926

Where a customer has signed a separate written agreement with TruEye covering the same subject matter, that agreement prevails over this document to the extent of any conflict.

See also the Terms of Service.