HailBound Privacy Policy

Who we are

HailBound is published under the developer name MajoRiver Labs. This policy covers the HailBound app, its supporting services and hailbound.com. For privacy questions or requests, email support@hailbound.com.

Accounts and sign-in

You can use the guest preview without creating an account. When you register, we collect your email address and a display name. New accounts require a display name; some older accounts may not have one. We store a password hash rather than your readable password, account and billing identifiers, and the subscription/access status needed to operate your account.

A random installation identifier and authentication credentials are stored on your device. Our server stores session identifiers, token hashes, expiration/revocation timestamps and the installation identifier to secure sign-in and enforce one active mobile device per person. We do not use a hardware fingerprint for this rule. Signing out clears sign-in credentials but does not necessarily remove the random installation identifier.

Maps, searches and location

The map and address/city search use Mapbox. Mapbox receives map/search requests, including search text and requested geography. If you choose Locate and grant foreground location permission, the app uses your device location to center the map. Those coordinates can also be sent to Mapbox to improve nearby search results. You can use map search without granting location permission.

The HailBound API processes viewed map bounds, searched/selected places and coordinates used for address checks to return weather information. A searched place or monitored area does not necessarily represent your physical location. The current app does not continuously track your device location in the background or save your Locate position as a location-history record in our account database.

Subscriptions and purchases

For Android purchases, Google Play processes payment and RevenueCat helps manage purchase verification, entitlement status and restoration. HailBound stores billing/customer identifiers, product and transaction references, subscription status, relevant dates, ownership records and billing event data. We do not receive your full payment-card details through the app. RevenueCat may create an anonymous SDK customer identifier before you sign in.

Billing event records can contain information supplied by the billing provider. Retaining transaction ownership and fraud-prevention evidence helps prevent duplicate access, incorrect restores and duplicate rewards.

Hail alerts

If you configure alerts, we save your selected town/radius or supported state, minimum hail size, sound choice, quiet hours/timezone and alert preferences. These are saved monitoring choices, not background GPS tracking. After you allow notifications, the app can register an Expo push token linked to the active device session. Expo and Google Firebase Cloud Messaging deliver Android notifications, which may contain the monitored-area name and a radar estimate.

You can turn off alerts or remove monitored areas in Account → Hail alerts, and control permission and sound in Android settings. Removing an area deletes its matching state. Deleting your account removes its alert settings, areas, push registrations and delivery records from the account database. A notification already handed to a provider may still reach or remain on your device.

Support and account-security email

When you submit a support question, bug report or feature request, we save the message, title/category, account email, display name, verified access/plan context, app/build and operating-system information, and delivery status. Support questions are available to signed-in users before purchase; bug/feature feedback requires Pro access. We do not automatically attach your device location or diagnostic logs. Anything you type into the message is included, so please leave out passwords and payment details.

Resend sends support submissions and password-reset/password-change emails. Support messages use your email as Reply-To and are received and answered in our Purelymail-hosted support mailbox. Replies and delivered copies can remain in mail systems separately from the app database. Password recovery records contain a code hash, request/expiry/used timestamps and an attempt count. A reset code is valid for 15 minutes; that is not a promise that its database record is deleted after 15 minutes.

Teams and referrals

Teams store a name, owner, membership/seat assignments and email-bound invitation records. Teammates can see each other’s profile name and email address. Owners can see invitation email addresses and share invitation codes themselves; HailBound does not automatically send invitation emails. Codes expire after seven days, but invitation records are not automatically erased at expiry. An invitation containing your email can remain with the inviting team after you delete your own account.

Referrals store codes, attribution, billing identities, transaction references, normalized email hashes and reward/payment/reversal history to verify eligibility and prevent abuse. These hashes are linkable identifiers, not anonymous data. Some billing and referral evidence is retained after account deletion. The current reward flow applies to qualifying Individual Google Play purchases; a trial or Team purchase alone does not qualify.

Usage information and website requests

The app sends a small set of preview, paywall and checkout interaction events for aggregate daily counts. These event payloads do not contain an account ID, installation ID, search text, town, viewport or precise location, and are sent separately from authenticated requests. There is no in-app switch for these first-party counters. Verified billing milestones are counted separately and retain ownership flags to prevent duplicate counting.

Our application request summaries record route category, status, duration and response size rather than query strings or user-supplied paths. Hosting/security systems can separately process IP addresses, request metadata and operational logs. The current static website has no first-party analytics script, advertising tracker or account form. AWS Amplify Hosting serves it and processes the network requests needed to do so.

Services that receive information

• Mapbox: maps, search and SDK/network data, including optional location bias.
• RevenueCat and Google Play: subscription and purchase processing.
• Expo and Google Firebase: notification delivery and associated device/service identifiers.
• Resend and Purelymail: transactional email, support delivery and correspondence.
• Railway: app API/database hosting; Amazon Web Services: static website hosting.

SDK and hosting providers process network and service data under their own policies. For example, Mapbox describes telemetry used to improve its maps and services; Mapbox describes telemetry choices through its map attribution controls. That control does not turn off HailBound’s separate aggregate counters. Native SDKs may process identifiers before you enable HailBound alerts. We do not treat all SDK processing as optional merely because alerts or sign-in are optional.

HailBound does not run third-party advertising or sell the account, monitored-area or support information you provide. We disclose information to operate and secure the service, respond to your requests, carry out the team features you use, meet legal obligations or protect rights. Provider processing and transfers may occur in the United States or other countries where those providers operate.

Retention and deletion

Account settings, sessions, recovery records, support submissions and access records are generally kept while the account exists unless replaced or removed through a feature. Account deletion removes these account-linked database records, including saved alert information and team membership. An owner’s account deletion also removes their team and ends its members’ Team access; it does not delete each teammate’s separate account.

Some information remains: billing ownership/event records and referral/security history used to prevent abuse, verify purchases, resolve disputes and meet legal requirements; invitation records belonging to another team; and copies held in support mail, provider systems, logs and backups. Complete provider billing events may be present in billing history. These records do not all have an automatic purge schedule. How long we retain these records depends on their purpose, security/fraud needs, unresolved requests/disputes and applicable obligations. Contact us about retained information or a deletion request.

When the relevant cleanup workers run, completed/discarded alert delivery records older than seven days are normally pruned; queued or unresolved deliveries and worker outages can extend that period. Aggregate daily counters are normally pruned after approximately 90 days. Session expiry, invitation expiry, reset-code expiry and email retry limits are not general data-deletion deadlines. Database backups and provider copies follow their separate retention cycles.

Signing out or uninstalling the app does not delete your account. Deleting your account does not cancel Google Play subscriptions. See account deletion instructions.

Your choices and security

You can decline device-location or notification permission, change alert settings, leave a team, sign out, or request account deletion. You can email us to request access to, correction of or deletion of your personal information. We may need to verify ownership of the account before acting. Available rights and exceptions depend on applicable law; we do not require your password in an email request.

We use HTTPS for service requests, password/token hashing, access checks and revocable sessions. No service or transmission can be guaranteed completely secure. HailBound is designed for PDR professionals. If you believe a child has supplied personal information, contact us so we can review it.

Changes and contact

We may update this policy as the service changes. The date above identifies this version. Material changes may also be communicated in the app or by email when appropriate. Privacy contact: support@hailbound.com.