Privacy Policy

1. Overview

This Privacy Policy explains how FleeFirst handles information across its website and Offradar iPhone app. Offradar uses your existing FleeFirst account and the same monitoring and alert records.

2. Information we collect

We store your sign-in phone number, account and session identifiers, SMS consent and opt-out state, monitored signals and groups, thresholds, pause settings, alert history, delivery status, and feedback you submit.

For paid website accounts, we store billing identifiers, subscription status, and the billing email supplied through Stripe. Support requests and signal suggestions are stored with your account.

We store verification request metadata, including IP addresses and request times, to limit abusive code requests. Verification codes are stored as hashes with expiration and attempt limits.

3. SMS & phone

We use your phone number for verification codes you request and, where you have consented, SMS alerts. Textbelt receives the phone number and message needed to send a text.

Reply STOP to opt out of SMS alerts. Your SMS choice is separate from optional iPhone push notifications; signing in to an existing account does not itself renew SMS consent.

4. Optional push notifications

When the iPhone app registers for push notifications, we store its installation identifier, Apple Push Notification service (APNs) device token, environment, associated account session, and notification preference. These records let us address notifications to the correct signed-in device.

Apple receives the APNs token and notification payload, including the alert title, explanation, and alert identifier. Notification content may appear on your lock screen according to your iOS settings.

Signing out revokes the app session and its registered devices. Turning off push in the app suppresses queued notifications for that installation. Notifications already sent to a delivery provider cannot be recalled.

5. Local monitoring

Local monitors store the ZIP code, place name, ZIP-based coordinates, radius, hazard type, and threshold you choose. The iPhone app does not request GPS or background location access.

ZIP lookup and hazard-data services receive the query information needed to look up the selected area. Power-outage coverage is limited to supported feeds and may not cover every utility or location.

6. Storage and service providers

We use essential session cookies on the website. The iPhone app stores its session and installation information in the device Keychain. Account and service records are hosted on our Railway infrastructure.

Stripe processes website billing, Textbelt sends texts, and Apple handles APNs delivery. Each receives the information needed for its role. The native app does not include advertising or cross-app tracking SDKs.

7. Account deletion and data help

You can begin account deletion from Account in the iPhone app after fresh phone verification, or request data help through Support. A deletion request disables account access, revokes sessions and registered devices, and stops pending alerts.

FleeFirst processes cancellation of future billing before completing removal of operational account data. If billing cancellation or cleanup fails, deletion remains pending and is retried; processing may continue after you have signed out.

Completed cleanup removes the live account, its monitors, alerts, delivery records, support submissions, and associated verification records. Deleting these records does not itself erase information retained separately by billing or delivery providers under their own retention requirements.