Terms of Use and Privacy Policy – TacOps (Tactical Command Center)
Last updated: August 29, 2026
Part A – Terms of Use
1. General
1.1. Welcome to the TacOps system (the "System"). These Terms govern the relationship between the operator of the System (the "Company", "we") and every user of the System (the "User", "you").
1.2. The System is a tactical command, control and monitoring system that includes a mobile application for smartphones. Use of the System involves access to mobile device resources, including location, camera, microphone, notifications and background execution, as detailed below.
1.3. Use of the System — including browsing, registration, viewing content, activating System functions and granting permissions in the mobile application — constitutes full and express consent to all the terms of this document and to the attached Privacy Policy.
1.4. If you do not agree to these Terms, in whole or in part, you must refrain from making any use of the System and must remove the application from your mobile device.
1.5. The Company may update these Terms from time to time, at its sole discretion. The binding version is the version published in the System at any given time.
1.6. These Terms are written in the masculine form for convenience only and apply equally to all genders.
2. Definitions
2.1. "System" / "TacOps" – the Tactical Command Center system with all its components, interfaces, modules, APIs, linked applications and ancillary services.
2.2. "Application" – the TacOps mobile application (iOS/Android), a central component of the System.
2.3. "Content" – any information, data, text, image, video, file, audio, code, mark, or any other material displayed, stored, transferred or transmitted in the System.
2.4. "User" – any person or legal entity browsing, registering or making any use of the System.
2.5. "Registered User" – a User who has completed the registration process and received personal access credentials.
2.6. "Emergency Event" – a situation defined as an emergency by the System operators or by the User, which enables the activation of advanced transmission capabilities.
2.7. "Live Transmission" – the transfer of video, audio or location in real time from the mobile device to the control center.
3. Terms of Use and Registration
3.1. Use of the System is conditional upon registration and approval by the Company. During registration, the User will be required to provide certain personal details.
3.2. The User undertakes to provide correct, accurate, complete and up-to-date details, and to notify the Company of any change to those details.
3.3. Access to the System is permitted only to persons aged 18 and over, or to persons expressly authorized by the Company.
3.4. Each User is solely responsible for maintaining the confidentiality of their username and password, and for every action performed in their account.
3.5. Access credentials may not be transferred to a third party, nor may a third party be allowed to use the account, except with the Company's express prior approval.
3.6. The User undertakes to notify the Company immediately of any unauthorized use of their account or any compromise of its security.
4. Mobile Application Access and Capabilities
The System includes a mobile application that requests permission to access device resources. Permissions are requested expressly (opt-in) through the operating system's permission mechanism (iOS/Android), and the User may refuse, revoke or narrow them at any time through the device settings.
4.1. Real-Time Location:
(a) With the User's approval, the Application may collect and transmit the device's location using GPS, cellular network, Wi-Fi and Bluetooth.
(b) Location may be sent continuously (including in the background and while the screen is locked) during an active mission, patrol or emergency event.
(c) Accuracy and frequency are determined by User settings or by operational requirements.
(d) The User may stop location sharing at any time through the Application or device settings, unless an emergency mode has been declared by the System operator in accordance with procedure.
4.1.1. Barometric Pressure Sensor and In-Building Floor Estimation:
(a) Subject to device permissions (on iOS: the "Motion & Fitness" permission), the Application may read the device's barometric pressure sensor while the Application is active, in order to calculate relative altitude and estimate the approximate floor inside a building.
(b) The purpose is operational and safety-related: presenting the estimated floor of a team member to commanders in real time, particularly at incidents in multi-story buildings.
(c) This figure is a relative, approximate estimate only (based on air-pressure changes and an assumed average floor height); it is not a certified measurement and may be affected by weather and environmental conditions. The User may calibrate or set the floor manually ("mark floor"), and the System indicates whether the value is calibrated or estimated.
(d) The data (relative altitude, estimated floor and calibration source) is stored as part of the live location record, subject to the same retention, access and security rules as location data; only the User's own device is authorized to write this data for them (enforced server-side). Stopping location sharing also stops the collection of this data.
4.2. Live Emergency Video:
(a) With the User's approval, the Application may activate the device camera and transmit live video to the control center, primarily in emergency situations or at the operator's request.
(b) Transmission begins only after the User's express approval, or during an emergency event agreed in advance.
(c) While a transmission is active, a clear indicator (visual or audible) is shown to the User indicating that the camera is on.
(d) Transmissions may be retained in the System for documentation, investigation and after-action review, subject to the Privacy Policy.
4.3. Audio Recording:
(a) With the User's approval, the Application may activate the microphone and record audio and/or transmit it in real time.
(b) This use is intended for operational communication (Push-To-Talk), incident documentation, and emergency voice transmission.
(c) While recording or transmitting, a clear indicator of the microphone state is shown to the User.
(d) Recordings may be retained in the System in accordance with operational settings and the Privacy Policy.
4.4. Messaging and Broadcast:
(a) The System enables sending and receiving text messages, multimedia (images, video, audio), locations and broadcast messages from teams, commanders or the control center.
(b) Messages may arrive as local notifications or push notifications.
(c) Message content is retained in the System for documentation, security and audit purposes.
4.5. Real-Time Alerts – Including Locked and Silent Modes (Critical Alerts):
(a) With the User's approval, the Application may display and sound Critical Alerts – including while the device is locked, in Do Not Disturb mode, in a focus mode, or while the device is muted.
(b) This permission is requested separately and uses special operating-system capabilities (iOS Critical Alerts / Android High-Priority Notifications).
(c) Critical alerts are reserved for emergencies, urgent operational alerts, and messages classified as critical by the System operator only.
(d) The User may disable critical alerts at any time through device settings, but may consequently miss essential information.
4.6. Health Data from Smartwatches and Wearables:
(a) With the User's approval, the System may interface with a smartwatch or other wearable devices (Apple Watch, Wear OS, Garmin, Fitbit, tactical sensors, etc.) and receive health and fitness data from them.
(b) The types of data that may be collected, subject to express permission:
– Heart rate (HR) and heart-rate variability (HRV)
– Blood oxygen saturation (SpO2)
– Body/skin temperature
– Steps, distance and physical activity
– Sleep data
– Fall detection
– Crash detection
– Irregular heart notifications (low/high heart rate, ECG where available)
– Location and altitude from watch sources.
(c) Data is transferred through operating-system health platforms (Apple HealthKit / Google Health Connect / Health Services) or through the watch manufacturer's interface, subject to the permissions approved by the User.
(d) Health data is used solely for defined operational purposes: assessing fitness for activity, automatic emergency alerts (including falls and crashes), monitoring physiological load in the field, and generating alerts for the medical team at the control center.
(e) Health data is defined as sensitive information under the Protection of Privacy Law; it is stored in a separate data node, encrypted in transit and at rest at the infrastructure level, with strict access control and access auditing. Access to health data is limited as follows: every User may view only their own health data; the health data of other Users is exposed only to authorized role-holders — commanders (in accordance with the command structure and within their own unit only), medical role-holders (medic/paramedic/unit physician) and emergency medical staff, as well as system administrators. A field User may not view the health data of their peers.
(f) Health data sharing may be revoked at any time through the device's health-platform settings and the Application settings. Revocation may impair medical monitoring, automatic emergency alerts and the ability to build a physiological picture.
4.6.1. Blood Type and Shabbat Observance Entered by the User:
(a) The User may voluntarily enter, in their personal profile or in the initial onboarding screen, their blood type and their Shabbat/holiday observance status. Both fields are optional; they may be left blank and updated or deleted at any time from the personal profile.
(b) Blood type is classified as sensitive medical information. It is collected solely for medical emergency preparedness, is not displayed in public personnel lists, and is exposed server-side only to role-holders on a need-to-know basis — commanders in the unit's chain of command, medical role-holders (medic/paramedic/physician) and system administrators; an ordinary peer (field User) is not exposed to the blood type of their colleagues. Users are asked not to record a blood type they do not know with certainty.
(c) Shabbat/holiday observance is classified as data of a religious nature (sensitive information). It is collected and displayed to team members as a shared operational signal, solely to avoid callouts during Shabbat/holiday rest and to coordinate scheduling, and for no other purpose.
(d) The collection and use of both fields are based on express informed consent, captured in the initial onboarding screen (mandatory checkbox) and recorded on the server (time of consent and policy version). The data is stored in the personnel record with the access control described above, and may be deleted at any time from the personal profile.
4.7. Additional Permissions:
(a) Local storage access – for storing maps, media and working data offline.
(b) Bluetooth access – for connecting operational devices (PTT headsets, sensors, beacons, smartwatch).
(c) Network access – for communication with the System servers.
(d) Background execution – for maintaining an active connection, receiving messages and transmitting location even when the Application is not on screen.
(e) Contacts access (optional) – for adding organizational contacts.
(f) Camera/gallery access (optional) – for sending existing photos and videos.
4.8. Refusal of Permissions:
(a) Refusing or revoking certain permissions may impair the functioning of the System or prevent the use of some capabilities.
(b) The System will operate within the limits of the permissions approved by the User, and will not access device components without approval.
4.9. Battery and Data Usage:
(a) Continuous use of GPS, video or audio may lead to increased battery and data consumption.
(b) The User declares that they are aware of this and waives any claim regarding communication costs or battery consumption.
5. Prohibited Uses
The User undertakes not to make any of the following uses of the System:
5.1. Any unlawful use, or use contrary to the provisions of any law.
5.2. Attempting to penetrate, hack, interfere with or disrupt the operation of the System, its servers or communication networks connected to it.
5.3. Operating bots or automated crawlers, or using scraping tools, without express written approval.
5.4. Uploading or distributing viruses, trojans, malware or any harmful code.
5.5. Harvesting, collecting or processing the personal data of other Users, other than for legitimate use of the System.
5.6. Use that infringes intellectual property rights, privacy, or any other legal right of the Company or of third parties.
5.7. Uploading offensive, threatening, harassing, racist, pornographic, defamatory or unlawful content.
5.8. Recording, photographing or transmitting people without their knowledge, beyond legitimate operational needs and subject to the laws governing recording and photography in the State of Israel.
5.9. Using the System's video, microphone or location capabilities for surveillance, spying or harassment.
5.10. Attempting to reverse engineer, decompile, or expose the source code of the System.
5.11. Commercial use of the System without the Company's express written consent.
6. Intellectual Property
6.1. All intellectual property rights in the System – including copyright, trademarks, patents, designs, trade secrets, the user interface, the design, the code, the content and the information – belong exclusively to the Company or to those acting on its behalf.
6.2. The System and its contents may not be copied, duplicated, distributed, published, modified, translated, sold or used commercially without the Company's express prior written consent.
6.3. Content uploaded to the System by a User (including video, audio and images) remains the property of the User, but the User grants the Company a non-exclusive, worldwide, royalty-free license to use the content for the purpose of providing the services, operational documentation and after-action analysis.
7. Availability, Changes and Maintenance
7.1. The Company will strive to provide the System with high availability, but does not undertake to provide continuous or fault-free availability.
7.2. The Company may, at its sole discretion, make any change, addition, restriction, or discontinuation of service in the System, without prior notice.
7.3. The Company may perform periodic maintenance that may cause temporary service interruptions.
7.4. The System must not be relied upon as a substitute for public emergency services (100, 101, 102). In any life-threatening situation, public emergency services must be contacted first.
8. Limitation of Liability
8.1. Use of the System is at the User's sole responsibility. The System is provided AS-IS, without any representation or warranty of any kind.
8.2. The Company is not liable for any direct, indirect, incidental, consequential or punitive damage – including loss of profits, loss of data, bodily injury, property damage, or business interruption – arising from the use of or inability to use the System, from a delay in receiving an alert, from a failure to transmit location, or from a live transmission that did not succeed.
8.3. The Company is not liable for the accuracy of location data, the quality of video transmission, the continuity of communication, or the availability of cellular/internet services provided by communication providers.
8.4. The Company is not liable for content uploaded by other Users or for any third-party content displayed in the System.
8.5. In any event, the Company's liability is limited to the amount actually paid by the User to the Company in the 12 months preceding the event.
9. Indemnification
The User undertakes to indemnify and compensate the Company, its employees, officers and representatives, for any damage, loss, loss of profits, payment or expense (including attorneys' fees) caused to them as a result of the User's breach of these Terms or of any law, including as a result of unlawful use of the System's photography, recording and location capabilities.
10. Termination of Use and Account Cancellation
10.1. The Company may, at its sole discretion, discontinue System services to a User, block their account, or delete their account – including for breach of these Terms.
10.2. The User may cancel their account at any time by contacting the Company and removing the Application from their device.
10.3. Upon account cancellation, the Company may delete the User's data, subject to retention obligations under law.
11. Jurisdiction and Governing Law
11.1. These Terms and the use of the System are governed exclusively by the laws of the State of Israel.
11.2. Exclusive jurisdiction over any dispute relating to these Terms or to the use of the System is granted to the competent courts in the city of Tel Aviv-Yafo only.
Part B – Privacy Policy
1. Introduction
1.1. The Company respects the privacy of System Users and undertakes to protect the personal information collected in the course of its use.
1.2. This Privacy Policy explains what data is collected, how it is used, with whom it is shared, and the scope, manner and duration of retention of location, video, audio and alert data.
1.3. This Policy forms an integral part of the Terms of Use.
2. Information Collected
2.1. Information the User provides voluntarily:
– First name, last name
– Email address, phone number
– Role details, personal number, unit and organization
– Profile photo (if uploaded)
– Emergency contact details
– Additional details provided during registration or use.
2.2. Information collected automatically while using the System services and the Application:
– IP address, network identifiers
– Browser type, operating system, application version
– Unique device identifier (Device ID)
– Usage times, session duration, connection status
– Actions within the System (event logs)
– Performance and crash data (crash logs)
– Battery data and connection state (Wi-Fi/cellular).
2.3. Location Data:
– Coordinates (latitude and longitude), altitude, speed, direction of travel
– Relative altitude from the barometric pressure sensor and estimated in-building floor, including the calibration method (manual/estimated) — see section 4.1.1
– Time and date of each location point
– Geofence events: entry into, exit from, or dwell within a defined area
– Location accuracy (meters)
– Location source (GPS / cellular / Wi-Fi / Bluetooth beacons).
Location is collected only after permission has been granted, and within the scope of the active mission.
2.4. Video and Audio Data:
– Live video transmissions sent from the device to the control center
– Voice recordings and Push-to-Talk transmissions
– Photos, videos and recordings that the User captures and sends voluntarily
– Media metadata (time, location, device).
2.5. Message and Broadcast Content:
– Text messages, multimedia, locations and broadcast messages
– Send, receive and read logs (read receipts).
2.6. Health and Fitness Data from Wearables (sensitive information):
– Heart rate (HR), heart-rate variability (HRV)
– Blood oxygen saturation (SpO2)
– Body/skin temperature
– Steps, distance, physical activity, calories
– Sleep data and sleep cycles
– Fall events and crash detection
– ECG results and irregular heart rhythm (on supported devices)
– Location, altitude and speed from the watch/wearable
– Metadata (device type, firmware version, sync times).
This data is considered sensitive information under the Protection of Privacy Law, 5741-1981, and will be handled accordingly.
2.6.1. Sensitive Information Entered by the User — Blood Type and Shabbat Observance (optional):
In addition to data from wearables, the User may — at their own free choice — enter in their personal profile or in the initial onboarding screen two items classified as sensitive information: (a) blood type — medical information collected solely for medical emergency preparedness; (b) Shabbat/holiday observance — data of a religious nature, for operational purposes only (avoiding callouts during Shabbat/holiday rest and coordinating scheduling). Both fields are entirely optional; they may be left blank, updated or deleted at any time. Their collection and use are based on informed consent captured and recorded in the initial onboarding screen. Full details in section 4.6.1.
2.7. Alert Data:
– Times of sending, receipt and opening of alerts
– Notification permission status (including Critical Alerts).
2.8. Cookies and similar tracking technologies in the System's web interface.
3. Purposes of Use
The information collected is used for the following purposes only:
3.1. Providing the services and operating the System.
3.2. Operational management, mission monitoring, coordination of field teams and command operations.
3.3. Transmitting and sharing location, video and audio with authorized personnel only, at the control center and in field teams, according to the organizational hierarchy.
3.4. Sending operational alerts, emergency alerts and administrative messages.
3.4.1. Physiological monitoring and medical emergency detection: health data from wearables is used to detect medical events (fall, crash, cardiac event), alert the medical coordinator, build a physiological picture of the team in the field, and support data-driven operational decisions. Health data will not be used for profiling, insurance, or employee performance evaluation.
3.5. Verifying User identity and securing their account.
3.6. Documenting incidents, investigation and after-action review.
3.7. Improving the System, developing new features and conducting statistical research – based on aggregated and filtered information.
3.8. Enforcing the Terms of Use and preventing prohibited or harmful actions.
3.9. Complying with the requirements of the law and of competent authorities.
4. Sharing Information with Third Parties
4.1. The Company will not transfer personal information to third parties, except in the following cases:
(a) With the User's express consent.
(b) To the organization or body that employs / operates the User in the System (the Company's customer), as part of the nature of the service.
(c) To service providers that assist in operating the System (cloud storage, security, analytics, alert delivery, communications), subject to confidentiality and data protection agreements.
(d) To emergency services and law enforcement authorities in an emergency or pursuant to an order of a competent authority.
(e) To protect the Company's rights and prevent unlawful acts.
(f) In the event of a merger, acquisition or transfer of operations, subject to the acquiring entity's undertaking to uphold this Policy.
4.2. The Company may transfer aggregated and non-identifying information to third parties for statistical and research purposes.
5. Data Storage and International Transfer
5.1. Information is stored on the servers of authorized service providers, in Israel and/or abroad. In practice, the System's central storage and processing infrastructure — the Realtime Database, the server functions (Cloud Functions) and the backups — is hosted with Google Firebase / Google Cloud Platform in a server region in the United States (us-central1). This means that most User information, including registration details, location data, media, messages, health data and operational data, is stored and processed in the United States. Video and audio data from emergency situations will generally be stored on secure servers with strict access control.
5.2. As a consequence of section 5.1, use of the System involves the transfer of personal information outside the borders of the State of Israel, primarily to the United States. When transferring information outside the State of Israel, the Company will act in accordance with the Protection of Privacy Law, 5741-1981 (including Amendment 13) and the regulations thereunder, and subject to Data Processing Agreements with the infrastructure providers. Continued use of the System constitutes the User's informed consent to such transfer and processing.
6. Information Security
6.1. The Company implements reasonable and accepted security measures to protect the information, including:
– Encryption of data at rest and in transit (TLS 1.2+)
– Two-factor authentication (2FA) where required
– Role-based access control (RBAC)
– Monitoring and audit logs
– Media encryption in transit (DTLS-SRTP) for video and audio channels.
6.2. Nevertheless, the Company cannot guarantee absolute immunity from intrusion, hacking, or unauthorized access. The User declares that they are aware of this and waives any claim against the Company in this regard, provided the Company has taken reasonable security measures.
6.3. Two-Factor Authentication (2FA) and Third-Party Processing:
(a) The System offers, and where organizational policy requires also enforces, SMS-based two-factor authentication using Google's Firebase Phone Authentication service. In order to deliver a one-time verification code, the mobile phone number recorded in the personnel record is transferred to Google and to SMS carriers — for identity verification purposes only. The second authentication factor is bound to the number recorded in the personnel record and cannot be freely changed by the User.
(b) When two-factor authentication is enabled or used, an (invisible) Google reCAPTCHA component is loaded, which helps prevent abuse and collects technical data — including IP address, browser/device data and behavioral signals — subject to Google's privacy policy.
(c) Authentication data is processed on Google infrastructure, including servers outside the State of Israel (the United States). The transfer is carried out in accordance with section 5 above and with the Protection of Privacy Law, 5741-1981 (including Amendment 13) and the regulations thereunder, and subject to data processing/transfer agreements with the provider.
7. Retention Periods
7.1. Location data: The System does not accumulate movement tracks or a continuous location history of Users. Only the User's most recent location is retained, for the purpose of displaying it in real time on the map to authorized personnel, and it is replaced with every update; the location record of an inactive User is deleted automatically within 7 days at most. However: (a) where geofences are defined, discrete boundary-crossing and dwell events (entry, exit, or dwell within a defined area) are recorded — not a continuous movement track; (b) where a location is attached to a specific operational record (a distress/SOS alert, an incident report, etc.) — a one-time "snapshot" of that location is retained as part of that record, subject to its retention period. These details are accessible to authorized personnel only.
7.2. Video and audio transmissions: retained for a period not exceeding 36 months, unless documented as part of an active incident requiring longer retention.
7.3. Message and alert content: retained for a period not exceeding 36 months.
7.4. Health and fitness data from wearables: retained for a period not exceeding 36 months, in a separate data node with administrator-only access, strict access control and access auditing. Medical emergency events (fall, crash, cardiac event) may be retained for a longer period for medical investigation and after-action review, in accordance with the provisions of the law.
7.5. Profile and account data: retained as long as the account is active, and for up to 12 months after its cancellation, unless longer retention is required by law.
7.6. Upon termination of use or deletion of the account, the information will be deleted or anonymized, except for information whose retention is required by law or for handling future claims.
8. User Rights
Under the Protection of Privacy Law, 5741-1981, and subject to any law, the User has the following rights:
8.1. Right of access – to receive from the Company the information held about them.
8.2. Right of correction – to request correction of incorrect or outdated information.
8.3. Right of deletion – to request deletion of the information, subject to the provisions of the law and operational limitations.
8.4. Right to object – to object to processing that is not essential to the operation of the System.
8.5. Right to control permissions – to grant, narrow or revoke application permissions (location, camera, microphone, notifications) at any time through device settings.
8.6. Right to opt out of non-operational communications.
To exercise these rights, the Company may be contacted using the contact details in section 12.
9. Cookies
9.1. The System's web interface uses cookies for its proper operation, for security and to improve the user experience.
9.2. Types of cookies used:
– Essential cookies (for operating the System)
– Functional cookies (for remembering preferences)
– Analytics cookies (for measuring usage)
– Marketing cookies (with consent only).
9.3. Cookies may be blocked through browser settings, but doing so may impair the functioning of the System.
10. Application Permissions and Recommended Privacy Settings
10.1. The User may revoke any permission at any time through device settings:
– iOS: Settings → Privacy → Location / Camera / Microphone / Notifications
– Android: Settings → Apps → TacOps → Permissions.
10.2. Revoking permissions may impair the functioning of the System, in particular location transmission, live video, audio and critical alerts.
10.3. In an emergency declared by the System operator, the System may present the User with a renewed request to approve essential permissions.
11. Changes to the Privacy Policy
11.1. The Company may update the Privacy Policy from time to time. The updated version will be published in the System.
11.2. The User's use of the System after the update constitutes consent to the updated policy.
11.3. In the event of a material change (particularly regarding the collection of location, video or audio), the Company will notify Users by a means of its choosing (in-app notification, email, etc.) and will request permission approval again where necessary.
12. Contact and Data Protection Officer
For any question, request or complaint regarding privacy, the Company may be contacted:
Company name: TacOps IL – TacOps
Email: privacy@tacops.co.il
Phone: +972-50-3404444
Address: HaHashmonaim 96, Tel Aviv
Data Protection Officer (DPO): Or Many
Estimated response time: up to 30 business days.
Consent
By clicking "I agree" / "Register" / "Continue" when approving permissions in the Application, or by making any use of the System, the User confirms that they have read, understood and agreed to all the terms of the Terms of Use and the Privacy Policy, including the manner of collection and use of location, video, audio, message and alert data.