Who we are

This site is operated by the team behind aisurveillancecamera.com. We build and configure AI video analytics systems that run on edge hardware installed at the customer’s own premises. If you have a question about this policy or about how we handle your data, use the contact page on this site and tell us what your question relates to.

What we collect

We collect the information you choose to give us. In practice that is the content of an enquiry or contact form submission — typically your name, email address, company, and a description of the scenario or project you are asking about. We do not require you to create an account to read this site or to contact us.

Like most websites, our server also records standard technical information needed to deliver pages to your browser, such as IP address, browser type and the pages requested. This is used to keep the site running and secure.

Comments and user accounts

This site does not offer public commenting, and visitors cannot register for an account. We therefore do not collect comment content or user profile information from site visitors.

Cookies

We use cookies to run the site and to understand how it is used. Essential cookies are required for core functions; non-essential cookies can be declined or withdrawn at any time. The full breakdown of cookie types, purposes and lifetimes is on our Cookie Policy page, where you can also change your choices.

Video and event data

This is the part that matters most for surveillance deployments, so we state it plainly. Our analytics run on the edge box installed at the customer’s own site. Camera footage and the events derived from it are processed on that device. Detecting an event does not require footage to be uploaded to our servers, and we do not operate a cloud service that ingests or stores customer video.

For a specific deployment, who can access footage, how long it is retained, and where it is stored are governed by that customer’s own system and retention settings. If you are evaluating a system and need this documented for an internal review, ask us and we will describe it in writing for your configuration.

Who we share your data with

We do not sell your personal data. We share it only with the service providers who need it in order to run this site and to answer your enquiry — for example our hosting provider and our email delivery provider — and where we are required to disclose it by law. We do not share customer video or event data, because we do not hold it.

How long we keep your data

We keep enquiry correspondence for as long as we are dealing with your request and for a reasonable period afterwards, so that we can answer follow-up questions and keep a record of what was discussed. Server and security logs are kept for a limited period needed for troubleshooting and security, then deleted. We do not keep data longer than we need it.

Your rights over your data

Depending on where you live, you may have the right to ask what personal data we hold about you, to receive a copy of it, to have inaccurate data corrected, to have it erased, and to object to or ask us to restrict how it is processed. These rights do not cover data we are obliged to keep for administrative, legal or security purposes. To make a request, use the contact page on this site. We will tell you what we need in order to verify the request before we act on it.

Where your data is sent

This site and the services behind it are hosted on infrastructure that may be located outside your own country, which means information you send us may be processed in another jurisdiction. Where that happens, we rely on the service providers we use to handle it under their own data protection terms. Camera footage and event data are not part of this, because they stay on the customer’s own hardware.

Changes to this policy

If we change how we handle personal data, we will update this page. Material changes will be reflected here with a revised date.

For reference on data-protection practice, see the NIST Privacy Framework and this overview of the GDPR.