Photo on Demand Privacy Notice
Applied from January 1, 2022
Ajax may, from time to time and owing to any changes in the PhOD functionality, supplement, amend, or replace this Notice. All changes, including the way in which they will be performed, are subject to rules, as Article 23 of the Agreement outlines.
SECTIONS 2.3-2.5 HEREOF CONTAIN IMPORTANT NOTICE ON CASES WHEN YOUR PERSONAL DATA MAY BE TRANSFERRED TO THIRD PARTIES AND POTENTIAL CONSEQUENCES PF SUCH TRANSFER. PLEASE READ THEM FIRST AND DO NOT USE THE PHOD NOR ANY OF ITS MECHANISMS IF YOU DO NOT AGREE WITH THOSE CONDITIONS. IF YOU ENABLE THE PHOD SERVICE, YOU CONSENT TO BE BOUND BY THE TERMS HEREOF.
1. Photo on Demand Feature; Permissions
1.1. The PhOD function appears in Ajax systems with OS Malevich 2.13.0 update. The feature allows users to take pictures using new generation of detectors supporting photo verification at any time when devices are armed or not. Information about the current models of devices supporting the PhOD feature will be disclosed in relevant guidelines. The PhOD feature provides an opportunity to find out the situation at the facility, check the cause of the alarm, or ensure the safety of your premises.
1.2. The PhOD is deactivated by default. In order to enable this function, a hub administrator or an authorized hub user only may choose the relevant feature in the Ajax application setting bar.
1.3. There are some categories of hub users that may interact with the PhOD:
- Hub Administrator. It may manage Ajax hub privacy settings, enable and disable the PhOD at any time, assign or revoke a right to use PhOD and access the pictures to other users of a hub, allow a third party to have access to the PhOD’s data, and request taking of pictures, takes photos at any time (when a hub is armed or not), view pictures taken by other users, see Users and their privacy permissions, determine which users can take and view photos on demand, which system detectors can be used to take photos on demand when a user can take photos on demand: at any time or when a device is armed, and disable any Hub User’s assignment or account;
- Hub User. By default, it has no access to either use of the PhOD and taken pictures or settings of PhOD. A Hub User may never enable or disable the PhOD feature otherwise, as with permission granted by a Hub Administrator. If a Hub Administrator grants to a Hub User relevant permission, a Hub User may be able to:
- Manage Privacy Permissions. If a Hub Administrator chooses, it can allow (or prohibit) other Hub Users to enable and disable the PhOD at any time. A Hub Administrator may also null this right at any time;
- Assign/Add New Users. If a Hub Administrator chooses, it can allow (or prohibit) other Hub Users to add or delete new users and assign a certain scope of rights to them. A Hub Administrator may null or amend any of these rights at any time;
- Take Photos on Demand. If a Hub Administrator chooses, it can allow (or prohibit) other Hub Users to request from the Ajax application to take photos of premises. A Hub Administrator may restrict this permission by time (allow to take pictures only when a hub is armed only), by territory (allow access to chosen detectors (cameras) only), by action (allow to request taking a photo). A Hub Administrator may null or amend any of these rights at any time;
- Access to Photos. If a Hub Administrator chooses, it can allow (or prohibit) a Hub User to see photos taken by such a user or by other Hub Users. There are some additional facts: (1) photos taken on demand are available only to users who have the right to take photos on demand at the time of the shooting; (2) if they obtain the right to photos on-demand, users cannot view the photos taken before this right was obtained; (3) users who have lost the right to photos on demand can view the photos taken by them when they had such a right. A Hub Administrator may null or amend this right at any time. Still, when a Hub User (including a Hub Administrator) requests to take a photo, all Hub Users receive a notification that someone took a photo of premises; however, other users may not access such a photo until they have relevant permission.
1.4. The Hub Administrator is obliged to receive the explicit consent of all Hub Users, including other Hub Administrators, prior to (a) enabling the PhOD feature and (b) granting any permissions to any persons. The Hub Administrator must not allow access to nor request from Ajax to give such access to or transfer to any entity personal data of any user of a Hub before such a user grants its unambiguous permission to the Hub Administrator.
2. Personal Data and Third-Party Access
2.1. Owing to the nature of the PhOD and following to Hub Users acts, Ajax may process the following personal data of users in the course of performing the PhOD feature: (a) names and IDs of users of a Hub where the PhOD is enabled; (b) permissions granted to such users and their roles (Administrator or User); (c) photos taken by users; (d) logs of the PhOD: who took a photo, when a photo is taken, what detectors (cameras) were used to take a photo; (e) metadata of pictures: detector (camera) ID, name, size, date, and format of an image, number of images, etc.
2.2. By enabling the PhOD option in the Ajax application, a Hub Administrator allows and directs Ajax to process personal data listed in sections 2.1(a)-(b) hereof to provide the Ajax services as described in the Agreement. By taking a photo or empowering a Hub User to take pictures, a Hub Administrator allows and directs Ajax to process personal data listed in sections 2.1(a)-(e) hereof. By enabling the PhOD option in the Ajax application or adding new Hub Users, a Hub Administrator allows and directs Ajax to deliver event notifications to all Hub Users when a photo is taken by any user. By empowering a Hub User to have access to taken photos, a Hub Administrator allows and directs Ajax to deliver such photos to Hub Users with the relevant access permission.
2.4. Please note that if (a) you grant to Hub Users permission to take photos or a right of access to photos or (b) direct Ajax to give access to any of the PhOD features to third parties (security, guardian, or installation services company, etc.), it may be associated with certain risks for privacy of yours and some other people. Ajax does not recommend granting access to any of the PhOD functionality to any person without a reasonable need or a need that may not be satisfied in another way. Still, if you want to allow other persons to use your PhOD functionality and have access to photos, Ajax strongly recommends assessing all the risks at first.
2.5. If you want to restrict access of other users or third parties to your PhOD functionality, you may do it via the setting bar in the Ajax application or with a help of Ajax Support team at [email protected]. Please note, that Ajax has no power to make either other users or any third parties that have already accessed your data to delete such data. If you want to restrict such persons from processing of your data or make them delete your data, please contact them directly.
3.2. For the sake of clarity, this Notice does not include any representations, warranties, or technical statements, whether explicit or implied, on the functionality, uninterrupted use, the accuracy of either the PhOD feature or of any of the Ajax Products. Ajax does not guarantee any specific results in the use of the PhOD. Ajax provides any description of the PhOD or any other Products for illustration purposes only; the only goal of such description is to refer to the relevant Products and provide you with the context of this Notice. Please refer to the applicable technical documentation to get information on how the PhOD or the Products work.