Alert² Mobile Privacy Policy

Alert² Mobile connects authorized users and registered devices to an organization’s Alert² system. Available features depend on the organization’s configuration and your permissions. They may include alarm notifications and response, facility dashboards, resident and staff records, fleet information, maps, and connected video.

The organization operating your Alert² server controls its facility records, user access, integrations, and retention settings. LSSI develops the software and may provide installation and support. Contact your organization for questions about its records and local practices, or contact LSSI using the details below.

• Account and authentication information: email address, account and staff identifiers, staff name, credentials entered to sign in or change a password, roles, and session or device authentication tokens.
• Device registration and diagnostics: a device name you provide, an app installation identifier, push notification token, device manufacturer and model, Android and app versions, registration and connection activity, and routine network or security information.
• Facility and operational information: records you are authorized to view or edit, including resident and staff names, assigned devices, facility locations, alarms, response actions, maps, fleet records, and connected camera information. Alarm records can contain information about people associated with a device or location.
• Notifications and local settings: notification titles, message content and times, selected server and account settings, and a local history of the ten most recent push notifications.
• Support requests: information you choose to send when requesting assistance or account and personal-data deletion.

The app displays locations supplied by the connected platform, such as a pendant or alarm location. Its current Android permission configuration does not request the phone’s precise or background location, camera, microphone, contacts, or shared photo library. Connected video comes from the organization’s configured camera services, rather than the phone’s camera.

Information is used to authenticate users and devices, enforce assigned permissions, deliver alarm notifications, show authorized facility information, record operational actions, synchronize device registration, support and troubleshoot the system, and protect against unauthorized use. Information entered or changed through the app is sent to the configured Alert² server for the requested operation.

Your configured Alert² server receives account, registration, device, and operational information. Authorized users in your organization can access records according to their permissions. Configured hosting, backup, messaging, map, or video services may receive information needed to provide their features; those providers depend on your organization’s deployment.

Google Firebase Cloud Messaging delivers push notifications. Google processes installation and push identifiers and the notification payload, which can include the alert title, message, and related alarm or device identifiers. Notification content is determined by the organization’s messaging configuration.

The app also includes Google Analytics for Firebase. When analytics collection is enabled, Google can process app interactions, installation identifiers, device and app information, and diagnostic or usage information. Collection and retention depend on the Firebase and Analytics settings for the app. Google describes its processing in its Firebase privacy and security information and Privacy Policy.

LSSI does not sell personal information. Information may also be disclosed when required by law or necessary to protect rights, security, or safety. Access during support is subject to the organization’s authorization and applicable agreements.

Access to platform information is controlled through account permissions and device or session authentication. The app stores settings and recent notifications in its private application storage. Authentication values use Android encrypted storage when available, with a private-storage fallback if encrypted storage cannot be initialized.

HTTPS connections encrypt communication with the configured platform. The app also supports server configurations that allow HTTP, which does not provide transport encryption. Your organization should configure HTTPS for personal or sensitive information and protect the server, backups, and devices against unauthorized access. Push notifications can be visible on a device’s lock screen depending on Android settings. No system can guarantee absolute security.

App settings, registration values, and local notification history remain on the device until replaced or removed through Android’s app-storage controls or uninstallation. The local history keeps the ten most recent push notifications. Removing the app or clearing its storage does not delete records already stored on the organization’s server or by a service provider.

The platform retains active records according to the organization’s operational needs and applicable agreements. Its cleanup settings control when eligible records that have been marked for deletion are permanently removed. Default eligibility periods are 30 days for ordinary deleted records, 365 days for deleted alarm history, and 7 days for deleted pending-device records. Administrators can change these settings. These periods are not promises that active records or every record associated with an account are automatically erased after that time.

Backups, legal holds, contractual requirements, and service-provider retention can affect deletion. Ask your organization or LSSI for the settings and obligations that apply to your information. Google’s linked privacy information describes Firebase’s retention practices.

You can manage notification permission and lock-screen previews through Android settings. Declining notifications can prevent push alerts from appearing. You can request access, correction, or permanent deletion of your account and associated personal information through your organization or LSSI.

Use the account and data deletion request form, or email [email protected]. You do not need to sign in or reinstall the app. Include your account email, organization or facility, and the request you want us to address. Do not include passwords or unnecessary sensitive records.

A submitted request does not mean deletion has already occurred. We may need to verify your identity and coordinate with the organization operating the server. Some records may need to be retained for legal, security, or contractual reasons; the applicable retention limits must be considered when responding to your request.

The app is intended for authorized organizational users. Facility records may relate to residents or other people who are not themselves app users. Handle those records only within your organization’s authorized workflows and applicable agreements. The public website’s inquiry and deletion-request forms are not intended for patient protected health information.

We may update this policy as app features, processing practices, or requirements change. The effective date above identifies this version.

For privacy questions, email [email protected] or write to LSSI Technologies, 2550 Boyce Plaza Road, Suite 204, Pittsburgh, PA 15241. Account and data deletion requests can also be sent to [email protected].