PLATFORM PRIVACY POLICY

LIVE AWARE PRIVACY, DATA PROTECTION & LOCATION POLICY
Applicable to X•SAR, X•SAFETY, X•AWARE, X•PLATFORM and all associated Live•Aware technologies, applications, systems and services

Effective Date: 2026-08-21
Last Updated: 2026-08-27
Version: 1.1

 

1. INTRODUCTION

This Master Privacy, Data Protection, Platform & Operational Policy (“Policy”) describes the privacy, data-protection and responsible-use framework applicable to products, applications, platforms, software, systems and associated services developed, supplied, licensed, hosted or otherwise made available by:

LIVE AWARE LTD
128 City Road
London
EC1V 2NX
United Kingdom

Company Number: 17360063

Privacy and General Contact:

info@live-aware.com

(“LIVE AWARE”, “Live•Aware”, “Company”, “we”, “us” or “our”).

This Policy applies, as relevant, to:

  • X•SAR;

  • X•SAFETY;

  • X•AWARE;

  • X•PLATFORM;

  • Live•Aware mobile applications;

  • handheld systems;

  • drone/UAV-compatible systems;

  • command dashboards;

  • oversight platforms;

  • web applications;

  • servers;

  • APIs;

  • databases;

  • administrative portals;

  • websites;

  • cloud-hosted systems;

  • stand-alone systems;

  • on-premise systems;

  • Bluetooth and Bluetooth Low Energy (“BLE”) functionality;

  • RF detection and analysis functionality;

  • Wi-Fi-related functionality;

  • positioning and location functionality;

  • telemetry;

  • analytics;

  • associated hardware;

  • integrations;

  • documentation; and

  • any other Live•Aware product, technology or service referring to this Policy.

Collectively these are the “Services.”

The Services are designed primarily for safety, search and rescue, emergency response, preventive safety, situational awareness, public safety, operational awareness and related legitimate purposes.

Some Services are capable of detecting, receiving, processing or analysing radio-frequency or wireless signals emitted by compatible devices.

Depending upon the Service, configuration, deployment, environment and Customer use case, information processed by the Services may relate to devices, equipment, assets, authorized users, responders or other persons or objects within a detection environment.

The technical ability of a Service to detect or process particular information does not mean that every deployment collects, stores, identifies, transmits or retains that information.

PART I — FUNDAMENTAL PRINCIPLES

2. LIVE•AWARE’S PRIVACY PRINCIPLES

Live•Aware seeks to design and operate its technology according to the following principles:

Safety

Technology should assist legitimate safety, emergency-response and operational objectives.

Privacy by Design

Privacy considerations should be incorporated into system architecture and operational design where reasonably practicable.

Data Minimization

Information should not be collected merely because it is technically possible to collect it.

Purpose Limitation

Information should be processed for legitimate and defined purposes.

Access Limitation

Operational information should be accessible only to appropriately authorized persons.

Security

Reasonable technical and organizational safeguards should protect information appropriate to its nature and sensitivity.

Retention Limitation

Personal information should not be retained indefinitely without a legitimate reason.

Accountability

Organizations deploying the Services remain responsible for the legality and appropriateness of their deployment where they determine the purpose and means of processing.

3. NO SALE OF PERSONAL INFORMATION

Live•Aware does not operate a data-broker business.

Live•Aware does not sell personal information for monetary consideration.

Live•Aware does not sell:

  • precise geolocation information;

  • responder location information;

  • missing-person information;

  • search-and-rescue information;

  • BLE detection information;

  • RF detection information;

  • Wi-Fi observations;

  • device identifiers;

  • operational mission information; or

  • emergency-response information.

Live•Aware does not use search-and-rescue or emergency-response information to create advertising profiles.

Live•Aware does not provide advertisers with access to operational detection information for behavioral advertising.

4. TECHNOLOGY PROVIDER — NOT CUSTOMER’S LEGAL COMPLIANCE OFFICER

The Services are technology tools.

Live•Aware does not control every location, environment, jurisdiction, purpose or manner in which a Customer chooses to deploy the Services.

Except where Live•Aware itself determines the purposes and essential means of processing, the Customer is responsible for determining whether its deployment is lawful.

The availability of a technical capability does not constitute:

  • legal advice;

  • regulatory approval;

  • authorization to conduct surveillance;

  • authorization to monitor employees;

  • authorization to identify individuals;

  • authorization to combine datasets;

  • authorization to monitor public spaces;

  • authorization to process sensitive information; or

  • a representation that a particular use is lawful in every jurisdiction.

Customers must obtain their own legal, regulatory, privacy, employment, telecommunications and operational advice where appropriate.

PART II — ROLES AND RESPONSIBILITIES

5. CUSTOMER AS CONTROLLER OR RESPONSIBLE ORGANIZATION

The organization, authority, municipality, county, emergency service, SAR organization, public-safety organization, infrastructure operator, company or other entity deploying the Services is referred to as the “Customer.”

The Customer ordinarily determines matters including:

  • where systems are deployed;

  • why detection takes place;

  • the operational purpose;

  • which personnel may use the Services;

  • which devices are authorized;

  • what detection functionality is enabled;

  • which detection parameters are configured;

  • whether detected information is retained;

  • retention periods;

  • who may access information;

  • whether information is exported;

  • whether information is associated with another dataset;

  • what operational actions are taken;

  • whether notices or signage are required;

  • whether consent is required;

  • whether a DPIA is required; and

  • the legal basis for Customer-controlled processing.

Where the Customer determines the purposes and essential means of processing personal information, the Customer generally acts as the controller, business or equivalent responsible party under applicable law.

6. LIVE•AWARE AS PROCESSOR OR SERVICE PROVIDER

Where Live•Aware processes Customer Personal Data solely on documented instructions from a Customer, Live•Aware may act as:

  • processor;

  • service provider;

  • contractor;

  • subprocessor; or

  • equivalent role under applicable privacy legislation.

Where legally required, such processing may be governed by a Data Processing Agreement (“DPA”).

Live•Aware may process Customer Personal Data as reasonably necessary to provide the contracted Services and in accordance with applicable law and contractual instructions.

7. LIVE•AWARE AS INDEPENDENT CONTROLLER

Live•Aware may act independently as controller or equivalent responsible party for information processed for its own legitimate purposes, including:

  • account administration;

  • customer relationship management;

  • billing;

  • security;

  • authentication;

  • fraud prevention;

  • abuse prevention;

  • cybersecurity;

  • service administration;

  • compliance;

  • legal claims;

  • service improvement where legally permitted;

  • protection of intellectual property;

  • protection of the Services; and

  • protection of Live•Aware, Customers, users and third parties.

The legal status of the parties ultimately depends upon applicable law and the factual circumstances.

8. CUSTOMER RESPONSIBILITY FOR LAWFUL DEPLOYMENT

To the maximum extent permitted by law, the Customer is responsible for assessing whether its intended deployment requires:

  • consent;

  • privacy notices;

  • public notices;

  • signage;

  • legitimate-interest assessments;

  • Data Protection Impact Assessments;

  • employee notices;

  • workplace-monitoring policies;

  • union consultation;

  • works-council consultation;

  • regulatory consultation;

  • government authorization;

  • parental or guardian consent;

  • contractual authorization;

  • telecommunications authorization;

  • data-retention policies;

  • access restrictions;

  • security controls;

  • records of processing;

  • public-sector assessments; or

  • other compliance measures.

Customers must not assume that a deployment lawful in one country or context is lawful in another.

PART III — TECHNOLOGY AND INFORMATION

9. BLE AND BLUETOOTH DETECTION

Certain Services may detect Bluetooth or BLE broadcasts from compatible devices.

Depending upon configuration and the broadcasting device, BLE information may include:

  • BLE advertisements;

  • broadcast packets;

  • device names;

  • service identifiers;

  • service UUIDs;

  • characteristic UUIDs;

  • manufacturer information;

  • beacon identifiers;

  • protocol information;

  • device identifiers;

  • pseudonymous identifiers;

  • rotating identifiers;

  • RSSI;

  • transmission information;

  • signal observations;

  • timestamps;

  • first-seen time;

  • last-seen time;

  • detection duration;

  • detection frequency;

  • repeated observations;

  • scanner identifiers;

  • site identifiers;

  • zone identifiers;

  • installation identifiers;

  • estimated proximity;

  • derived signal information;

  • associated metadata; and

  • technical information contained in or derived from compatible broadcasts.

Not every category is necessarily collected in every deployment.

10. RF INFORMATION

Certain Live•Aware Services, particularly X•SAR and X•AWARE, may process supported RF information for legitimate search, safety, emergency-response or situational-awareness purposes.

Depending upon system capability and configuration, RF-related processing may include:

  • detection of supported signals;

  • signal strength;

  • signal changes;

  • signal observations;

  • detection timestamps;

  • approximate direction;

  • relative bearing;

  • estimated proximity;

  • estimated range;

  • signal confidence;

  • detection history;

  • movement-related changes;

  • signal correlation; and

  • derived operational intelligence.

RF observations should not automatically be interpreted as verified identity or exact physical location.

11. WI-FI INFORMATION

Where supported, permitted and enabled, Services may process Wi-Fi or network-related technical information for:

  • connectivity;

  • system operation;

  • device discovery;

  • positioning;

  • troubleshooting;

  • security; or

  • other legitimate operational purposes.

Live•Aware does not design the Services to intercept the contents of private Wi-Fi communications.

12. LOCATION INFORMATION

Certain Services may process:

  • GPS/GNSS coordinates;

  • latitude;

  • longitude;

  • altitude;

  • approximate location;

  • precise location;

  • responder location;

  • scanner location;

  • drone/UAV position;

  • search tracks;

  • mission routes;

  • last-known position;

  • movement;

  • direction;

  • speed;

  • site location;

  • zone location;

  • location accuracy;

  • timestamped location;

  • map position; and

  • derived or estimated location information.

Precise geolocation may constitute sensitive personal information under applicable law.

13. ACCOUNT INFORMATION

Account information may include:

  • name;

  • username;

  • organization;

  • department;

  • role;

  • business email address;

  • telephone number;

  • account identifier;

  • authentication information;

  • permissions;

  • preferences; and

  • administrative information.

14. DEVICE INFORMATION

The Services may process technical information such as:

  • device manufacturer;

  • device model;

  • operating system;

  • operating-system version;

  • application version;

  • installation identifier;

  • device-generated identifiers where permitted;

  • network status;

  • Bluetooth status;

  • location-service status;

  • permission status;

  • language;

  • region;

  • battery information;

  • diagnostic information;

  • crash information;

  • security information; and

  • application configuration.

15. OPERATIONAL INFORMATION

Operational information may include:

  • incident identifiers;

  • mission identifiers;

  • responder assignments;

  • search areas;

  • search tracks;

  • detected-device observations;

  • alerts;

  • warnings;

  • deployment locations;

  • configuration settings;

  • system status;

  • administrative activity;

  • authentication activity;

  • audit records;

  • synchronization records;

  • API activity;

  • security events;

  • application events;

  • exports;

  • error logs;

  • performance data; and

  • troubleshooting information.

PART IV — THIRD-PARTY AND NON-USER DETECTIONS

16. DETECTION DOES NOT NECESSARILY MEAN IDENTIFICATION

A fundamental distinction exists between:

detecting a wireless signal

and

identifying an individual.

A compatible device may broadcast a technically detectable signal without Live•Aware knowing the identity of the person carrying or owning that device.

A detection therefore must not automatically be interpreted as proof that Live•Aware:

  • knows the device owner’s identity;

  • knows who was carrying the device;

  • knows why the device was present;

  • has established ownership;

  • has verified an individual’s presence; or

  • has established an exact location.

17. THIRD-PARTY DEVICES

BLE and other wireless technologies may permit compatible broadcasts to be detected without the broadcasting device owner directly interacting with the scanning device.

Accordingly, detections may involve third-party devices.

Customers must determine whether their collection, storage, analysis, association or use of such information is lawful and appropriate.

The Services must not intentionally be used for:

  • unlawful surveillance;

  • unlawful tracking;

  • stalking;

  • harassment;

  • discriminatory profiling;

  • intimidation;

  • unauthorized employee monitoring;

  • unlawful intelligence gathering; or

  • other prohibited purposes.

18. NON-USERS

Certain legitimate safety or SAR operations may involve devices associated with persons who:

  • do not have a Live•Aware account;

  • have never interacted with Live•Aware;

  • have not installed a Live•Aware application;

  • cannot reasonably receive notice during an emergency; or

  • cannot be identified by Live•Aware.

Where such technical observations constitute personal data, applicable privacy laws may nevertheless apply.

Customers remain responsible for their lawful deployment and use of Customer-controlled detections.

PART V — X•SAR SPECIAL PROVISIONS

19. SEARCH AND RESCUE

X•SAR is intended to provide additional RF-based operational intelligence to authorized search-and-rescue personnel.

X•SAR may assist responders in detecting compatible RF signals that could potentially be relevant to a search.

It is an operational support technology.

It does not replace:

  • trained SAR personnel;

  • established SAR procedures;

  • Incident Command;

  • emergency-service judgment;

  • conventional search methods;

  • visual search;

  • canine teams;

  • aviation procedures;

  • mapping;

  • thermal imaging;

  • other appropriate technologies; or

  • professional decision-making.

20. NO GUARANTEE OF DETECTION

Live•Aware does not guarantee that X•SAR will detect:

  • every person;

  • every missing person;

  • every smartphone;

  • every wearable;

  • every BLE device;

  • every RF signal; or

  • any particular target.

Detection depends upon factors outside Live•Aware’s control.

These may include:

  • device availability;

  • device compatibility;

  • battery state;

  • radio state;

  • operating-system behavior;

  • device configuration;

  • transmission behavior;

  • hardware;

  • distance;

  • terrain;

  • buildings;

  • debris;

  • water;

  • vegetation;

  • weather;

  • interference;

  • signal obstruction;

  • transmission power;

  • antenna orientation; and

  • environmental conditions.

21. NO GUARANTEE OF RESCUE

The Services cannot and do not guarantee:

  • successful search;

  • successful localization;

  • successful rescue;

  • prevention of injury;

  • prevention of death;

  • response time;

  • operational outcome; or

  • availability of a detectable signal.

Search-and-rescue decisions remain the responsibility of appropriately trained personnel and responsible authorities.

PART VI — X•SAFETY SPECIAL PROVISIONS

22. PRIVACY-FIRST PREVENTIVE SAFETY

X•SAFETY may be configured to estimate anonymous presence, density or activity without identifying specific individuals.

Where deployed in such configuration, its purpose is to understand conditions within an environment rather than unnecessarily identify persons.

Depending upon configuration, X•SAFETY may use observations to support:

  • presence estimation;

  • visitor estimation;

  • density assessment;

  • movement patterns;

  • environmental changes;

  • safety warnings;

  • hazard-zone warnings;

  • preventive audio messages; and

  • situational awareness.

23. SAFETY WARNINGS ARE ADVISORY

Warnings, notifications and automated outputs generated by X•SAFETY are intended to support preventive safety.

They cannot guarantee that:

  • every person hears a warning;

  • every person understands a warning;

  • every device is detected;

  • every hazard is detected;

  • every incident is prevented;

  • environmental information is complete; or

  • a warning will prevent injury, damage or loss.

Customers remain responsible for appropriate safety planning and procedures.

PART VII — X•AWARE AND X•PLATFORM

24. X•AWARE

X•AWARE may provide public-safety, resilience, RF-awareness or situational-awareness capabilities.

Customers must use such capabilities only for lawful, authorized and proportionate purposes.

Any Customer use involving monitoring, association, identification or analysis of persons must comply with applicable law.

25. X•PLATFORM

X•PLATFORM may provide centralized configuration, control, command, administration and oversight of one or more Live•Aware systems.

Information visible within X•PLATFORM depends upon:

  • deployed systems;

  • Customer configuration;

  • permissions;

  • user role;

  • operational context; and

  • available integrations.

Customers are responsible for controlling their authorized users and permissions.

PART VIII — TECHNICAL LIMITATIONS

26. PROXIMITY IS AN ESTIMATE

BLE RSSI and other RF measurements are not guaranteed measurements of physical distance.

Signal characteristics may be affected by:

  • walls;

  • floors;

  • buildings;

  • debris;

  • vehicles;

  • people;

  • water;

  • vegetation;

  • terrain;

  • weather;

  • radio interference;

  • reflections;

  • absorption;

  • antenna orientation;

  • transmission power;

  • device hardware;

  • operating systems;

  • device settings;

  • software behavior;

  • battery-saving functionality; and

  • environmental conditions.

Any displayed distance, range, direction, bearing, probability, confidence or proximity is therefore an estimate unless expressly stated otherwise.

27. INFORMATION IS NOT CONCLUSIVE EVIDENCE

Detection information should not, by itself, automatically be treated as conclusive evidence that:

  • a particular person was present;

  • a particular person owned a detected device;

  • a person was present at an exact time;

  • a device was at an exact distance;

  • a device followed a particular route;

  • a detected device belonged to a target person; or

  • an event occurred exactly as inferred from technical observations.

Customers determine the evidential weight attributed to information and are responsible for appropriate verification.

28. FALSE POSITIVES, FALSE NEGATIVES AND DUPLICATES

Wireless detection can produce:

  • false positives;

  • false negatives;

  • duplicate observations;

  • missed detections;

  • delayed detections;

  • intermittent detections;

  • ambiguous detections;

  • inaccurate estimates; or

  • observations relating to unrelated devices.

Customers and users must account for these limitations.

PART IX — DATA USE

29. PURPOSES OF PROCESSING

Information may be processed as reasonably necessary for:

  • providing the Services;

  • search and rescue;

  • emergency response;

  • preventive safety;

  • situational awareness;

  • authorized RF detection;

  • device discovery;

  • proximity estimation;

  • operational coordination;

  • alerts;

  • system administration;

  • authentication;

  • cybersecurity;

  • abuse prevention;

  • fraud prevention;

  • troubleshooting;

  • support;

  • maintenance;

  • service availability;

  • backups;

  • disaster recovery;

  • legal compliance;

  • protection of life;

  • protection of rights;

  • product reliability; and

  • appropriately anonymized or aggregated analysis.

30. NO UNRELATED COMMERCIAL EXPLOITATION OF EMERGENCY DATA

Live•Aware does not sell emergency-response or SAR operational information for unrelated commercial exploitation.

Operational information may nevertheless be processed where necessary to:

  • provide the Services;

  • comply with law;

  • investigate incidents;

  • protect the Services;

  • resolve disputes;

  • defend legal claims; or

  • satisfy contractual obligations.

PART X — LEGAL BASES

31. GDPR AND UK GDPR

Where applicable, processing may rely upon one or more legal bases including:

  • consent;

  • contractual necessity;

  • legitimate interests;

  • legal obligations;

  • vital interests;

  • public interest;

  • exercise of official authority; or

  • another lawful basis permitted by applicable legislation.

The appropriate legal basis depends upon the specific processing and deployment.

An operating-system permission is not automatically equivalent to GDPR consent.

32. VITAL INTERESTS AND EMERGENCY PROCESSING

Where legally appropriate, information may be processed to protect the vital interests of an individual or another person.

This may be particularly relevant to certain life-threatening emergencies.

However, emergency processing does not create a general exemption from privacy legislation.

PART XI — HOSTING AND DEPLOYMENT

33. CLOUD AND HOSTED DEPLOYMENTS

Where Services are hosted by or connected to Live•Aware infrastructure, Live•Aware may technically process Customer Data as necessary for:

  • hosting;

  • storage;

  • synchronization;

  • transmission;

  • support;

  • maintenance;

  • security;

  • backups;

  • availability;

  • troubleshooting;

  • incident response; and

  • disaster recovery.

Personnel access should be limited according to legitimate operational requirements and applicable controls.

34. STAND-ALONE AND ON-PREMISE DEPLOYMENTS

Live•Aware may provide systems capable of operating within Customer-controlled infrastructure.

Where Customer Data remains entirely within Customer infrastructure and Live•Aware has no access to that information, the Customer controls:

  • storage;

  • database security;

  • access;

  • backups;

  • retention;

  • exports;

  • deletion;

  • infrastructure security; and

  • operational administration.

To the maximum extent permitted by law, Live•Aware cannot be responsible for information or infrastructure that it does not possess, operate or control.

35. OFFLINE AND EDGE PROCESSING

Certain functionality may occur locally or at the edge.

Information processed locally may not necessarily be transmitted to Live•Aware.

The existence of a technical observation on a Customer device therefore does not necessarily mean Live•Aware receives or retains that observation.

PART XII — DATA SHARING

36. AUTHORIZED RECIPIENTS

Depending upon deployment, information may be disclosed or made available to:

  • authorized Customer users;

  • responders;

  • administrators;

  • command personnel;

  • emergency services;

  • authorized government bodies;

  • service providers;

  • subprocessors;

  • technical infrastructure providers;

  • professional advisers; or

  • other recipients authorized by law or Customer instruction.

37. SERVICE PROVIDERS

Live•Aware may use third parties for services such as:

  • hosting;

  • cloud infrastructure;

  • cybersecurity;

  • mapping;

  • communications;

  • email;

  • authentication;

  • notifications;

  • customer support;

  • monitoring; and

  • technical infrastructure.

Where required, appropriate contractual data-protection obligations will apply.

38. GOVERNMENT AND LEGAL REQUESTS

Live•Aware may disclose information where required by valid applicable law, legal process, court order or other binding obligation.

Where permitted and appropriate, Live•Aware may assess the validity, scope, jurisdiction and proportionality of governmental requests.

Nothing prevents lawful emergency disclosure where reasonably necessary to protect life or physical safety.

39. CORPORATE TRANSACTIONS

Information may be transferred in connection with:

  • merger;

  • acquisition;

  • restructuring;

  • investment;

  • financing;

  • sale of assets;

  • insolvency;

  • reorganization; or

  • transfer of the business or relevant technology.

Any such transfer remains subject to applicable privacy law.

PART XIII — SECURITY

40. INFORMATION SECURITY

Live•Aware uses reasonable and appropriate safeguards that may include:

  • encryption in transit;

  • encryption at rest where appropriate;

  • authentication;

  • access controls;

  • role-based permissions;

  • least privilege;

  • logging;

  • audit trails;

  • infrastructure controls;

  • network protections;

  • secure development practices;

  • vulnerability management;

  • backups;

  • disaster recovery;

  • incident response; and

  • confidentiality requirements.

No system is completely secure.

Live•Aware does not warrant absolute security.

41. CUSTOMER SECURITY RESPONSIBILITIES

Customers are responsible for protecting:

  • credentials;

  • Customer-controlled infrastructure;

  • administrator accounts;

  • user accounts;

  • exported information;

  • local devices;

  • Customer networks;

  • API credentials;

  • integrations;

  • physical access; and

  • Customer-configured permissions.

Customers must promptly revoke access when it is no longer required.

42. SECURITY INCIDENTS

Live•Aware maintains procedures for responding to suspected security incidents.

Where legally required, Live•Aware will make or support appropriate notifications in accordance with its legal and contractual role.

PART XIV — DATA RETENTION AND DELETION

43. RETENTION

Live•Aware retains information only for as long as reasonably necessary for applicable:

  • service purposes;

  • contractual requirements;

  • operational requirements;

  • security;

  • backups;

  • legal obligations;

  • dispute resolution;

  • incident investigation;

  • fraud prevention;

  • enforcement; or

  • legitimate business requirements.

Different information may have different retention periods.

44. CUSTOMER-CONTROLLED RETENTION

Where the Customer controls retention settings or determines retention periods, the Customer is responsible for ensuring those periods are lawful and appropriate.

45. DELETION

Information may be deleted, overwritten, anonymized, aggregated or de-identified when no longer required.

Deletion from active systems may not immediately remove information from:

  • backups;

  • disaster-recovery systems;

  • security records;

  • immutable audit records; or

  • records required by law.

Such information may remain protected and restricted until normal deletion or overwrite.

46. LEGAL HOLDS

Live•Aware may preserve information where reasonably necessary for:

  • litigation;

  • regulatory proceedings;

  • legal claims;

  • investigations;

  • contractual disputes;

  • enforcement; or

  • compliance with law.

PART XV — GDPR RIGHTS

47. DATA SUBJECT RIGHTS

Where GDPR or UK GDPR applies, eligible individuals may have rights including:

  • access;

  • rectification;

  • erasure;

  • restriction;

  • portability;

  • objection;

  • withdrawal of consent;

  • certain rights concerning automated decision-making; and

  • complaint to a competent supervisory authority.

These rights are subject to applicable statutory conditions and exemptions.

48. PROCESSOR DATA

Where Live•Aware acts solely as processor, requests concerning Customer-controlled information may need to be directed to the relevant Customer.

Live•Aware may assist Customers where required by contract or applicable law.

PART XVI — CALIFORNIA PRIVACY

49. CCPA / CPRA

Where applicable, California residents may have rights relating to:

  • access;

  • knowledge;

  • correction;

  • deletion;

  • categories of information;

  • categories of sources;

  • business or commercial purposes;

  • categories of recipients;

  • sale or sharing;

  • sensitive personal information; and

  • non-discrimination.

These rights are subject to statutory limitations and exceptions.

Live•Aware does not sell personal information.

50. SENSITIVE PERSONAL INFORMATION

Certain information, particularly precise geolocation, may constitute sensitive personal information.

Live•Aware seeks to limit such information to reasonably necessary and proportionate purposes, including:

  • safety;

  • SAR;

  • emergency response;

  • system functionality;

  • security;

  • integrity; and

  • legally authorized operational purposes.

PART XVII — INTERNATIONAL TRANSFERS

51. CROSS-BORDER PROCESSING

Where personal data is transferred internationally, Live•Aware will use a lawful transfer mechanism where required.

This may include:

  • adequacy decisions;

  • Standard Contractual Clauses;

  • the UK Addendum;

  • the UK International Data Transfer Agreement; or

  • another lawful transfer mechanism.

PART XVIII — CHILDREN AND VULNERABLE PERSONS

52. CHILDREN

The Services are not designed for behavioral advertising to children.

Safety or emergency operations may nevertheless involve minors.

Customers are responsible for satisfying applicable requirements relating to minors where their deployment intentionally processes children’s information.

Live•Aware does not knowingly sell children’s personal information.

53. VULNERABLE AND ENDANGERED PERSONS

Safety operations may involve vulnerable, missing, injured, unconscious or endangered persons.

Information concerning such persons should be treated with heightened care and accessed only for legitimate and authorized purposes.

PART XIX — AUTOMATION, ANALYTICS AND AI

54. AUTOMATED ANALYSIS

Services may use software, algorithms, analytics or artificial intelligence to assist with:

  • signal analysis;

  • localization estimates;

  • pattern recognition;

  • confidence calculations;

  • detection filtering;

  • anomaly detection;

  • proximity estimation;

  • operational recommendations;

  • warnings; or

  • visualization.

Such outputs may be probabilistic, incomplete or inaccurate.

55. HUMAN JUDGMENT REMAINS ESSENTIAL

Unless expressly stated otherwise, automated outputs are decision-support information.

Users must apply appropriate professional and operational judgment.

The Services should not be relied upon as the sole basis for decisions where independent verification is reasonably required.

PART XX — ACCEPTABLE USE AND PROHIBITED CONDUCT

56. AUTHORIZED USE

The Services may only be used:

  • lawfully;

  • for authorized purposes;

  • within contractual scope;

  • by authorized personnel; and

  • in accordance with applicable documentation and policies.

57. PROHIBITED USE

Users must not use the Services to:

  • stalk;

  • harass;

  • intimidate;

  • unlawfully surveil;

  • unlawfully track;

  • discriminate;

  • violate privacy rights;

  • violate communications law;

  • obtain unauthorized access;

  • circumvent security;

  • interfere with systems;

  • scrape protected information;

  • reverse engineer where prohibited by agreement or law;

  • create unauthorized databases from detections;

  • publish protected operational information;

  • impersonate another user; or

  • use the Services for an unlawful purpose.

58. SUSPENSION AND RESTRICTION

Live•Aware may, subject to applicable contracts and law, suspend, restrict or terminate access where reasonably necessary to:

  • prevent unlawful use;

  • protect security;

  • protect individuals;

  • prevent abuse;

  • protect infrastructure;

  • respond to legal requirements; or

  • protect Live•Aware or its Customers.

PART XXI — INTELLECTUAL PROPERTY AND SYSTEM PROTECTION

59. PROPRIETARY TECHNOLOGY

Nothing in this Privacy Policy transfers ownership of:

  • software;

  • algorithms;

  • databases;

  • detection methods;

  • signal-processing techniques;

  • user interfaces;

  • APIs;

  • models;

  • documentation;

  • designs;

  • trademarks;

  • trade secrets; or

  • other Live•Aware intellectual property.

Access to information generated through the Services does not grant rights to copy, reverse engineer, reproduce or commercially exploit Live•Aware technology except as expressly authorized.

PART XXII — THIRD-PARTY TECHNOLOGY

60. THIRD-PARTY DEPENDENCIES

Services may depend upon third-party technology including:

  • Android;

  • mobile-device hardware;

  • Bluetooth;

  • Wi-Fi;

  • GNSS/GPS;

  • mobile networks;

  • cloud infrastructure;

  • mapping providers;

  • device manufacturers;

  • drone/UAV systems; and

  • operating-system services.

Live•Aware does not control these third-party technologies.

Changes, outages, restrictions or errors affecting third-party technology may affect the Services.

PART XXIII — SERVICE AVAILABILITY

61. NO GUARANTEE OF UNINTERRUPTED OPERATION

Except where expressly provided by contract, Live•Aware does not guarantee that Services will:

  • always be available;

  • always be uninterrupted;

  • always be error-free;

  • detect every compatible device;

  • receive every broadcast;

  • provide continuous connectivity;

  • provide exact positioning; or

  • operate under every environmental condition.

62. MAINTENANCE AND UPDATES

Live•Aware may update, modify, maintain or improve Services.

Features may change because of:

  • security requirements;

  • operating-system changes;

  • hardware changes;

  • regulatory requirements;

  • technical improvements;

  • third-party dependencies; or

  • product development.

PART XXIV — OPERATIONAL RESPONSIBILITY

63. CUSTOMER DECISION-MAKING

Customers and authorized users remain responsible for decisions made using information provided by the Services.

Live•Aware provides technology and information.

It does not assume command or operational control of a Customer’s:

  • SAR mission;

  • emergency response;

  • public-safety operation;

  • drone operation;

  • personnel;

  • infrastructure;

  • deployment; or

  • incident management.

64. PROFESSIONAL TRAINING

Customers are responsible for ensuring that personnel receive appropriate training for their roles and use the Services consistently with applicable operating procedures.

PART XXV — LIMITATION OF POLICY AND LIABILITY

65. PRIVACY POLICY IS NOT A WARRANTY

This Policy explains privacy and operational principles.

It does not constitute a warranty that:

  • data will never be compromised;

  • every signal will be detected;

  • every location will be accurate;

  • every warning will be received;

  • every incident will be prevented;

  • every missing person will be located; or

  • every SAR operation will succeed.

66. MANDATORY LAW PREVAILS

Nothing in this Policy excludes or limits any right, duty or liability that cannot lawfully be excluded or limited.

To the extent any provision conflicts with mandatory applicable law, the mandatory law prevails and the remaining provisions remain unaffected to the extent permitted.

PART XXVI — CHANGES OF OWNERSHIP

67. SUCCESSORS

If Live•Aware or relevant assets are acquired, merged, reorganized or transferred, information may transfer to the successor subject to applicable law.

The successor becomes responsible for applicable privacy obligations relating to information it receives.

PART XXVII — CHANGES TO THIS POLICY

68. UPDATES

Live•Aware may update this Policy because of:

  • changes in law;

  • regulatory guidance;

  • new products;

  • new functionality;

  • changes in infrastructure;

  • security requirements;

  • operational requirements; or

  • changes in business practices.

The latest version should be identified by its effective date and version number.

Where required, material changes will be communicated or consent obtained as required by applicable law.

PART XXVIII — SEVERABILITY

69. SEVERABILITY

If a provision of this Policy is held invalid, unlawful or unenforceable, that provision will be interpreted or limited to the minimum extent necessary where legally permissible.

The remaining provisions will continue to apply to the maximum extent permitted by law.

PART XXIX — NO WAIVER

70. NO WAIVER

Failure by Live•Aware to enforce a provision of this Policy or an associated contractual right does not constitute a waiver of that provision or right.

PART XXX — PRIVACY REQUESTS AND CONTACT

71. PRIVACY REQUESTS

Privacy and data-protection requests may be submitted to:

info@live-aware.com

Live•Aware may request reasonable information to verify the identity and authority of the requesting person before disclosing, modifying or deleting personal information.

Where Live•Aware processes information on behalf of a Customer, the requester may be directed to the relevant Customer.

72. CONTACT DETAILS

LIVE AWARE LTD
128 City Road
London
EC1V 2NX
United Kingdom

Company Number: 17360063

Email: info@live-aware.com

Website: live-aware.com

PART XXXI — LIVE•AWARE’S COMMITMENT

73. SAFETY WITHOUT UNNECESSARY IDENTIFICATION

Live•Aware develops technology intended to improve awareness, prevention and response.

Our objective is not to collect as much information as technically possible.

Our objective is to provide useful operational intelligence while minimizing unnecessary processing of personal information.

Detection does not automatically mean identification.

Presence does not automatically mean tracking.

Signal observations do not automatically establish identity.

Estimated proximity does not constitute guaranteed distance.

Operational intelligence does not replace professional judgment.

Technology does not replace trained responders.

74. SEARCH AND RESCUE PRINCIPLE

During search-and-rescue and life-safety operations, our guiding principle is:

Use technology and the minimum information reasonably necessary to help responders find, protect and assist people while protecting that information against unrelated or unauthorized use.

75. PREVENTIVE SAFETY PRINCIPLE

For preventive safety deployments, our guiding principle is:

Understand the environment without unnecessarily identifying the people within it.

76. FINAL STATEMENT

Live•Aware technology is designed around a simple objective:

Protect people before and during critical situations.

Our approach to information is therefore built around:

Safety. Privacy. Necessity. Security. Proportionality. Accountability.

LIVE•AWARE

X•SAR — Search. Locate. Rescue.
X•SAFETY — Detect. Warn. Prevent.
X•AWARE — Sense. Analyze. Protect.
X•PLATFORM — Configure. Control. Oversee.

Privacy by Design. Safety by Purpose.

Scroll to Top