Skip to content
Lensgate Technologies
What we doIndustries & insightsOur visionLet’s build ↗
← Back to LensgateLENSGATE TECHNOLOGIES / LEGAL

Privacy Policy

We explain our on-site processing model, what happens during remote access, and how information is handled when you contact us or use our website.

Effective date: 30 October 2026 · Last updated: 30 October 2026
Scope and responsibilitiesInformation we handleOn-site camera processingWhat happens when you access the portal remotelyNetwork transit and geographic locationHow information is usedAuthorised access and securityProviders and disclosuresWebsite fonts, cookies and technical requestsRetention, access removal and deletionRequests, concerns and people appearing in footagePrivacy and grievance contact

01. Scope and responsibilities

This policy covers the Lensgate Technologies website, business communications and our standard on-site service model. For customer-site monitoring, the customer generally determines the purpose of monitoring, camera coverage, authorised users and operational retention. Lensgate processes service data to deliver the agreed service under customer instructions and the relevant agreement. We separately handle website enquiries, billing, support and business administration. The precise responsibilities for a deployment are set out in its agreement.

02. Information we handle

Website enquiries may contain your name, company, email address and message. Business administration may involve contact details, correspondence, invoices and service records. Customer-site systems may analyse camera footage and produce detections, counts, time stamps, event images, plate readings and other agreed operational records. Remote accounts may involve usernames, access permissions, login records and technical security information. The actual information depends on the contracted use case.

03. On-site camera processing

In the standard deployment described here, camera analysis runs on a processing device installed at the customer’s site. The remote-access connection is a way to reach that on-site service; it is not a separate cloud video-analysis engine. Local recording, event storage and retention depend on the cameras, recorder, processing device and agreed configuration. Any separately agreed backup, export, external storage or additional processing must be addressed in the project arrangement rather than assumed to be part of this model.

04. What happens when you access the portal remotely

Where enabled, an outbound connection from the site device provides authorised access through a designated customer portal. When a user opens that portal, the requested content is transmitted through third-party remote-access connectivity to the user’s browser. Depending on enabled features, this may include live or recorded views, snapshots, alerts, counts and dashboard records. Connectivity and hosting providers may also handle IP addresses, request information, time stamps and other technical data needed to route, secure and operate the connection.

05. Network transit and geographic location

On-site analysis and remote transmission are different activities. We do not describe the service as one in which all information always remains inside the premises: a remote browser receives the content it requests. Third-party connectivity may use infrastructure in more than one country, depending on routing and provider configuration. Any location restrictions or customer-specific requirements should be addressed in the written service arrangement.

06. How information is used

We use enquiry and business information to respond to requests, discuss and deliver services, manage billing and support, maintain business records and meet applicable legal requirements. Customer operational data is handled for the agreed monitoring, reporting, integration and support purposes. Access to footage or operational records for troubleshooting must be authorised for that work. Any separate proposed use of customer footage, including publication or model-development work outside the contracted purpose, requires its own appropriate written authorisation and lawful basis.

07. Authorised access and security

Remote portals are intended for authorised users and use assigned username/password access. Customers should control who receives accounts and promptly report suspected misuse or request access removal. Credentials should not be sent in public website messages. Appropriate access and technical safeguards are used according to the deployment, but neither a password nor a remote-access connection makes a system immune to security incidents. This policy describes the access model and does not represent that additional controls such as multi-factor authentication are enabled unless agreed and implemented.

08. Providers and disclosures

Information may be handled by providers supporting connectivity, hosting, email or other agreed service functions, and by personnel authorised to perform support. We may disclose information where required by law or where reasonably necessary to address a security incident or establish or defend legal rights. Customer portal content is not intended for public access. Any customer-authorised sharing, exports or integrations are governed by the relevant workflow and agreement.

09. Website fonts, cookies and technical requests

Our website currently requests font files from Google Fonts, which can receive technical request information such as an IP address and browser details. Website and connectivity infrastructure may also generate request or security logs. Customer portal software may use cookies or browser storage for login sessions and necessary functionality, depending on its implementation. We do not currently include a third-party advertising or visitor-analytics script in the public site code. If additional tracking is introduced, this notice and any required choices should be updated accordingly.

10. Retention, access removal and deletion

Website enquiry, business and support records are kept for the purpose for which they were collected, taking account of service needs and applicable legal recordkeeping obligations. Customer-site retention and end-of-service handling are governed by the deployment configuration and agreement. Removing a remote account or disabling a connection does not automatically erase recordings held on a customer’s cameras, recorder or site device. Customers can contact us to coordinate agreed access removal, export or deletion work.

11. Requests, concerns and people appearing in footage

For a request concerning website or business information we handle, write to [email protected] with enough information to identify the matter. We may need to verify identity or authority before responding. Requests for access, correction, deletion, withdrawal of consent or other rights will be addressed as applicable under Indian law and the relevant role and service arrangement. If you appear in a customer site’s footage, contact that establishment in the first instance; we can assist the responsible customer with requests under our agreement. Customer deployments involving children or other sensitive contexts must be addressed by that establishment and the agreed service scope.

12. Privacy and grievance contact

For privacy questions, account-access concerns or grievances, contact the Lensgate Technologies team at [email protected]. Please identify the relevant website, organisation or portal without sending passwords or unnecessary footage. This policy is subject to applicable Indian data-protection requirements as they come into force. We may update it to reflect changes in our services or legal obligations; the date at the top identifies the current version.

QUESTIONS ABOUT THIS POLICY?[email protected] ↗
lensgate®

Computer vision.
Real-world impact.

[email protected] ↗
© 2026 Lensgate TechnologiesIndustry partnersMore possibility in every frame.
Terms & ConditionsPrivacy PolicyRefund & Cancellation