ClimaAlert Privacy Policy

Effective date: 5 November 2026

ClimaAlert is operated by UB AI Systems, LLC. This policy describes information processed for the ClimaAlert mobile app and its supporting weather, environmental-risk and notification services. For privacy questions, contact info@ubaisystems.com.

Information we process

• Location and place information. Your device location when permitted, including precise latitude and longitude; selected or searched cities, place names, country and location-update times. Selected location information is saved on your device. Location information is also stored in Firebase with the installation record.
• Installation and notification information. An installation identifier, push-notification token, notification preferences, platform, app version, language and registration or activity timestamps. Depending on the app version, the identifier is generated by the app or established through Firebase anonymous authentication. Ordinary consumer use does not require an email address or password, but the identifier links records to an installation.
• Weather and risk-service records. Observations, forecasts, location-related risk snapshots and summaries, predictions, AI explanations and notification-delivery information associated with your installation or monitored area.
• Community Reports, when available in your app version. If you choose to create a report, we process its category, description, optional expected end time, consent and responsibility acknowledgments, report identifier, creation and submission times, and any selected event reference. We also process your selected incident pin, whether it came from device GPS or a manual map selection, and any separate consent to publish its coordinates. Photos and videos are captured directly in the app; video may include audio. We process the captured original and watermarked media, capture-session times, and location evidence, including precise coordinates, accuracy and location time, to associate the submission with its capture session and check contribution eligibility.
• Support and technical information. Information you choose to send us, including your email address and problem description, and service-request or diagnostic records used to operate and troubleshoot the service. These records can contain installation-related or location information.

How we use information

We use this information to provide local weather and environmental-risk information, maintain your monitored location, deliver notifications, display content in your language, explain changes over time, secure the service and investigate problems. The Risk Engine determines risk levels, thresholds and prediction lifecycle state. AI provides supporting explanations and guidance.

We use Community Report information to receive and track submissions, check technical validity and contribution eligibility, provide public observations, support moderation and investigate false, misleading or abusive reports. In the current reporting flow, reports that pass automated submission and content checks are published immediately as Community Report / Unverified, without prior administrator approval. They may be reviewed, restricted or removed afterward. Some submissions may be held or rejected by automated checks, and older app versions may use a private review flow. Photos and videos undergo separate processing and safety checks; they may appear later or remain unavailable pending review. Original evidence files remain in restricted storage; public media use separately prepared copies. Publication and automated checks do not verify the truth of a report or change official Risk Engine severity.

How a report's location is displayed publicly

Precise incident coordinates: The report form asks for separate, explicit consent to publish the selected incident pin and any available accuracy information. If you give this consent, the public report, map and sharing link can expose those submitted coordinates without deliberate rounding to a coarse area. The pin can come from your device location or a point you manually select, so it can match your capture location. The coordinates identify the submitted position; they do not guarantee the incident's true physical location. Device GPS can have measurement error. Manually selected pins have no independently verified positional accuracy and no measured GPS accuracy value.

Approximate or hidden location: If you do not give that separate consent, precise incident coordinates are not published as the report's location. Where an approximate location is shown, it represents the centre of a coarse area rather than your exact pin or private GPS fix. Some reports may have their location hidden. Private capture-location evidence is not exposed as a separate public record. A public incident pin can nevertheless identify the same place if you selected your capture position and explicitly consented to publish it.

Check the incident pin, description and attachments before submitting. Public text, visible landmarks, images or audio can reveal locations or personal information independently of the map marker. See the Community Report rules in the Terms of Service.

Service providers and processing locations

• Google Firebase and Google Cloud support authentication, application data storage, server processing, notifications and configuration.
• Google Places and Geocoding process city-search text, place identifiers or coordinates as needed to find places and resolve names.
• OpenWeather processes coordinates or area-grid coordinates sent by our server to provide weather and air-quality information.
• Google AI services, when enabled, process structured weather and risk context for explanations. This may include language, area names, country and grid identifiers.
• OpenStreetMap map tiles may be requested to show a report-location preview. The tile service receives the requested map area and connection information such as your IP address.

Our service providers may process information in countries other than the country where you live. Privacy protections and legal requirements may differ between countries. Contact us if you have questions about the providers or processing relevant to your information.

The current consumer app has no advertising or in-app purchase functionality. If you use its share feature, a weather or risk card is passed to the app or recipient you choose. Review the location label and other information before sharing.

If you share a published Community Report, the selected app receives a link to that specific public report and a public summary. Private reporter identifiers are excluded. The linked public page can display the incident coordinates you explicitly consented to publish and any available accuracy information, or an approximate or hidden location as explained above. Withdrawing a report or making it unavailable stops new access through the ClimaAlert link; it cannot remove copies or previews already retained by another person or service.

Location, notifications and your choices

You can choose a city in ClimaAlert and manage location and notification permissions in your device settings. The app accesses device location when active or resumed where permission allows. On iOS, background notifications can also cause the app to send its last-known location to refresh stale monitoring information, subject to permissions and operating-system restrictions.

Revoking location permission stops new device-location access subject to the operating system's behavior. It does not erase existing records or necessarily stop monitoring the previously selected area. Turning off notifications affects delivery; it does not itself delete information.

Creating a Community Report is optional. Direct photo or video capture requires camera permission, and video recording may require microphone permission. A report or supporting observation may require fresh, sufficiently accurate location evidence. If those conditions cannot be met, submission may be unavailable. Opening the Community page alone does not start a report or camera capture.

Retention

We retain information for as long as reasonably necessary for the purposes described in this policy. Installation and location records support the service while it is provided to an installation. Weather and risk history, predictions, explanations and delivery records support risk continuity, alert reliability and troubleshooting. Support and technical records are retained while needed to handle requests, investigate problems and meet applicable legal obligations.

When information is no longer needed for these purposes, or following a verified deletion request, we delete or de-identify it unless continued retention is required or permitted by applicable law for a specific purpose. Retained information remains subject to this policy. These criteria are not a promise that all information is automatically deleted after a fixed number of days.

Request deletion of your ClimaAlert data

Because ordinary use is not registered by email, your email address alone may not identify your installation. We will explain what limited information is needed to locate relevant records and verify your request. We will not treat possession of an installation identifier alone as proof of control.

A verified deletion request covers the relevant installation record and its associated location, notification, risk, prediction and explanation information. We review requests without undue delay and within periods required by applicable law. If we cannot identify the relevant records or must retain certain information, we will explain the limitation and available next steps. Backup copies, where present, follow the applicable backup-retention process; removal is not necessarily immediate in every copy.

Uninstalling ClimaAlert or changing permissions does not by itself delete existing server records. This is a support-assisted request process, not an immediate automatic-deletion feature.

Security and your rights

The app uses HTTPS-based services for network transmission. No storage or transmission system can be guaranteed completely secure.

Depending on applicable law, you may have rights to access, correct or delete your information, restrict or object to processing, withdraw consent, or complain to the relevant privacy authority. Contact us to discuss a request and any applicable verification requirements or limitations. Parents and guardians with concerns about a child's information can use the same contact address.

Updates and contact

We will update this page and its effective date when the policy changes. Where required, material changes will be brought to your attention in the app and any necessary consent will be requested before the changed processing.

UB AI Systems, LLC
Application: ClimaAlert
Privacy contact: info@ubaisystems.com