Privacy Policy

SafeReach helps families, communities and authorized organizations report missing persons, submit sightings, and coordinate a response. This policy explains what information we collect, how it's used, who can see it, and what choices you have.

A lot of what we handle isn't about the person using the account — it's about the person who is missing. Where that distinction matters, we call it out below.

Account information: name, email, phone number, and role (reporter, verified organization, moderator, law enforcement) when you register.

Case information you submit: a missing person's name, age, physical description, photo, last-known location, and — if relevant — vehicle details. This is personal information about someone who, in most cases, hasn't consented to it being collected, because they're missing. We treat this data with the added care that implies.

Sightings and safety incident reports: a description, location, timestamp, and any photos or video submitted by the person reporting them.

Comments: text you post on a public case update, tied to your account's first name — never posted anonymously or under a spoofed name.

Device information for push notifications: if you enable notifications, we store a device token so we can deliver urgent alerts. You can revoke this at any time by disabling notifications in your browser.

We use Google's Gemini models to generate a structured summary of a case report, a factual summary of a sighting, or a suggested category/priority for a safety incident. Every one of these is a suggestion shown only to a human moderator alongside your original submission — AI never publishes a case, changes its status, or overrides your own account of what happened. We keep an internal record of every AI-generated suggestion and whether a moderator approved, modified, or rejected it.

A new report is not public. It's visible only to you and to moderators until a moderator reviews and verifies it. Once verified, a case may be made public (visible to anyone, including people not signed in) or kept restricted to authorized responders, depending on the moderator's decision and the case's needs.

When a case does go public, we generalize the last-known location to an approximate area — roughly a city block — rather than exposing an exact address. This is deliberate: an exact address can be misused by the wrong person, and it's rarely necessary for the public to help.

Verified law-enforcement accounts and verified-organization accounts (scoped to their own organization) can see additional, non-public case detail relevant to their role. Moderators can see everything necessary to review and act on reports.

SafeReach is built on Google Firebase (authentication, database, file storage, and Cloud Functions), the Google Maps Platform (for location search and mapping), the Gemini API (for the AI features above), and Cloudflare (for hosting the website itself). Your information is processed on this infrastructure, which may store or process data outside your own country. We don't sell your information to anyone, and we don't use it for advertising.

Missing-child cases necessarily involve a minor's personal information, submitted by an adult reporter — not by the child. We don't knowingly allow anyone under 16 to create an account. A minor's case information is used only to help locate them safely, subject to the same moderation and location-generalization protections as any other case.

Account information is kept while your account is active. Case, sighting, and incident records are kept for as long as needed to resolve the case and to maintain an accurate public-safety and audit record — including after a case is resolved, since that history has real value for future search-and-rescue coordination. You can request deletion of your own account information at any time; we'll explain if any part of a record needs to be kept for legal, safety, or audit reasons first.

Access to case data is enforced by role — not just hidden in the app's interface, but blocked at the database level even if someone bypassed our app entirely. Status changes that make a case public, resolve it, or verify a sighting only ever happen through a reviewed, human-authorized action. We also use Firebase App Check to block traffic that isn't coming from our real application.

You can review and correct your own account information at any time, edit a report you submitted before it's reviewed, and request deletion of your account. If you believe information about you or someone you know is inaccurate or shouldn't be public, contact us and we'll review it.

If we make a material change to how we handle your information, we'll update the date at the top of this page and, where appropriate, notify account holders directly.

Questions about this policy or your information can be sent to privacy@safereach.app.