RedAlert Privacy Policy
1. Who we are and what this policy covers
MIRA Safety, LLC operates RedAlert ("RedAlert," "we," "us," or "our"). This Privacy Policy explains how we handle personal information in the RedAlert iOS and Android applications and the RedAlert website at redalertus.com (the "Services"). Our privacy contact is [email protected], and our mailing address is 1713 Hur Industrial Blvd., Cedar Park, TX 78613, United States.
This policy covers the RedAlert Services described here. A third-party news website, an app store, a sign-in provider, a separate simulator, or a MIRA Safety shopping website may have its own privacy policy. Following a link to one of those services does not make its data practices part of this policy.
RedAlert helps people follow selected areas and alert categories, view safety information, submit reports, and contact the administration team. It is not an emergency dispatch service. Please do not send emergency requests or unnecessary sensitive information through a report or support message.
2. Information you provide
Account and profile information
We receive an authentication identifier and information made available by your selected sign-in method, which may include your email address, name, profile image, phone number, email-verification status, and linked sign-in-provider identifiers. We also maintain account status, role, and creation and update records. Google Firebase Authentication supports sign-in and identity verification. The information actually provided depends on the sign-in method and the information you choose to supply.
Passwords entered into a supported Firebase sign-in flow are handled by Firebase Authentication. You should never include a password, one-time verification code, recovery code, or push token in a report or support message.
Selected areas and notification preferences
We store the areas and categories you subscribe to, whether those subscriptions are active, and information needed to match eligible alerts to your selections. A selected area can be somewhere you want to follow rather than your current physical location. These choices may nevertheless reveal places or subjects that matter to you.
Reports and uploaded media
When you submit a report, we collect its title, description, category, incident timing, selected area, location coordinates and location accuracy where supplied, location source, location-capture time, anonymity choice, and any other fields you submit. We associate the report with your account and may preserve the author name, email address, and phone number supplied for the report. We record submission, review, and publication events and any administrative corrections or decisions.
We collect the photos, videos, or other supported files you upload and information about those files, such as their type, size, file name, and processing or moderation status. A file may itself contain faces, addresses, license plates, audio, or embedded metadata, including location information. Do not assume that uploading a file removes its metadata or makes its contents anonymous. Review your files and remove unnecessary personal information before uploading them.
Support and other communications
We collect the information you send through Contact Us, support, abuse reports, or privacy requests, including your message, account identifier where applicable, and contact information you provide. In-app Contact Us messages are stored for review by authorized administrators. They are not an emergency hotline or a public discussion channel.
3. Information processed when you use the Services
Devices and notification delivery
We process device-registration identifiers and push tokens, device platform, any supplied device label and app version, technical metadata sent by the app, notification settings, registration and activity timestamps, and delivery records. Delivery records can include the intended account and device, alert or report reference, attempts, timestamps, provider responses, and delivery status. A provider's acceptance of a notification does not establish that you saw or read it.
Google Firebase Cloud Messaging and, for iOS delivery, Apple's notification services process information needed to deliver notifications. A notification may include an alert title, message, severity, and identifiers needed to open the relevant screen. Depending on your device settings, other people may see notification content on your lock screen.
Network, security, and operational information
Requests to our systems and service providers can involve IP addresses, request identifiers, timestamps, authentication status, requested routes, error and delivery information, and other technical records needed to operate and secure the Services. Our systems also maintain activity and audit records for account changes, moderation, and administrative actions. Authentication providers may process user-agent and device information for security and abuse prevention.
Location permissions and maps
Locations you select for subscriptions and coordinates you submit with a report are distinct from any location a device permission allows the app to access. Report coordinates can be precise enough to identify a home, workplace, or incident site.
You can manage available location permissions in your device settings. Turning off a permission does not erase a location already included in a submitted report.
Where the Services use an external place-search service, the search text or location reference needed to resolve a place is sent to that provider. The backend supports OpenStreetMap Nominatim for place resolution. Map displays or native map SDKs may also connect directly to their providers.
Website resources and storage
Some RedAlert website pages load fonts from Google Fonts and a JavaScript library from cdnjs, which uses Cloudflare's content-delivery network. Your browser connects directly to those providers to retrieve the resources, which involves network and technical information such as your IP address and browser details. Your browser may cache website files locally to display them efficiently. Loading an external resource is distinct from the report, account, and notification processing described elsewhere in this policy.
4. How we use information
We use personal information to authenticate you and maintain your account; display information for the areas you select; manage subscriptions and deliver eligible alerts; receive, review, and publish reports and approved media; handle support, abuse, and privacy requests; maintain reliable systems and investigate failures; prevent fraud, misuse, and security incidents; enforce our Terms and Acceptable Use Policy; and meet applicable legal obligations.
Report location and category information help us understand an incident and identify the relevant area. Administrative author information helps us review reports and investigate abuse. We do not treat an anonymity setting as consent to disclose private account contact information to other users.
Where enabled, RedAlert uses automated processing to classify externally sourced news and match information to areas and categories. A news item or alert may be made available under configured publication rules without an individual editor reviewing every item. Automated classifications and summaries can be wrong. This processing is not a determination of your eligibility for employment, credit, insurance, or another essential service.
Where applicable law requires consent for particular processing, including sensitive personal information, we seek that consent separately. You can withdraw consent through the contact methods below. Withdrawal does not change processing that was lawful before withdrawal, but it may affect a feature that needs the information.
5. What other users and administrators can see
Approved reports may be visible to other users and through publicly accessible report-detail links. Visible material can include report text, category, report location and coordinates, timing, an author display label, and approved media. Reports may also lead to alerts. Please submit only information you have the right to share and are comfortable making available to others.
Publishing anonymously hides the author display label; it does not remove your report's location, text, media, or potentially identifying details. Authorized administrators can still associate the report with your account and view author information used for review and safety operations. Other people may infer who you are from an incident, coordinates, a photograph, or the words you use.
Private author contact snapshots, internal account identifiers, moderation notes, and storage keys are not intended for resident or public report views. Authorized personnel may access account and report information to perform their assigned work. A report being approved means it passed the applicable publication workflow; it does not certify that the report is true or complete.
People may copy or share material after seeing it. Removing material from RedAlert does not give us control over independently saved copies or third-party websites.
6. Who receives information
We provide information to service providers as needed for their work for us, including authentication, push delivery, hosting, database operations, media storage, technical support, and security. The RedAlert service uses Google Firebase Authentication and Firebase Cloud Messaging, and supports DigitalOcean hosting and S3-compatible media storage such as DigitalOcean Spaces. Apple participates in iOS push delivery and may provide a sign-in service where offered. Authorized development and operational contractors may access information needed to maintain the Services.
Place-search and map providers receive the information needed for their features as described above. Opening an external news or other website connects you to that site's services and privacy practices. An article link does not mean we share your RedAlert account profile with the publisher.
We may disclose information when required by law or valid legal process, or where legally permitted and reasonably necessary to protect people's safety, investigate security incidents or abuse, establish or defend legal claims, or enforce our agreements. We assess such disclosures in light of applicable law and the information needed for the purpose. RedAlert does not automatically send every resident report to police or emergency responders.
If ownership or operation of RedAlert changes, information may be transferred as part of the transaction, subject to applicable law and the receiving party's obligations. We will provide notice where required. We may use information that has been aggregated or de-identified so that it no longer reasonably identifies a person; we maintain appropriate safeguards and do not use it to re-identify individuals.
7. Retention and deletion
We retain account and subscription information while needed to provide your account and selected features. Reports, media, communications, and operational records are retained according to their purpose, deletion requests, applicable law, and any narrowly necessary safety or legal exception. Merely signing out, uninstalling the app, disabling notifications, or suspending an account does not delete these records.
We use the following retention criteria:
- Account, profile, subscriptions, and device records: while needed to provide the account and selected features, subject to deletion requests and permitted exceptions.
- Reports, uploaded media, and author information: while reasonably needed to review and display the submission, maintain related alerts, or address a specific lawful safety or legal need, subject to applicable deletion rights.
- Support and privacy-request records: while reasonably needed to resolve the matter and document our response or compliance with legal duties.
- Security logs, audit records, and delivery or job records: while reasonably needed to operate and secure the Services, investigate incidents, and meet legal obligations.
- Backups and storage versions: through their normal replacement or expiry cycle. Residual copies awaiting deletion are restricted from ordinary use, and applicable deletions are reapplied after a restore.
We delete personal information or de-identify it when it is no longer reasonably necessary for these purposes. A specific legal hold or other lawful exception may require limited continued retention.
Account deletion addresses associated personal information, including uploaded content, subject to specific legal exceptions. A public-interest report or alert is not an automatic exemption from deletion. Where we can lawfully keep information after removing every reasonable means of linking it to you, that information is treated as de-identified rather than merely relabeled "anonymous."
Service-provider deletion can involve a separate processing period. We initiate the relevant provider actions as part of deletion; provider timing does not justify delaying our own work. See the Account Deletion Policy for the request process and permitted exceptions.
8. Your choices and privacy rights
You can manage subscriptions and notification preferences in the app and control notification permissions in your device settings. You can control available camera, photo, microphone, and location permissions in device settings. A permission control affects future access; it does not automatically erase a report or file already submitted.
You can request account deletion, access to personal information, correction, or another privacy action through https://redalertus.com/privacy/choices or [email protected]. Account deletion instructions are at https://redalertus.com/legal/account-deletion. We may verify your identity using information reasonably necessary for the request. Never send passwords, one-time codes, recovery codes, or push tokens. If an identity document is necessary, we will explain why and provide a secure submission method. Do not send it through ordinary email.
Depending on your location and the laws that apply to us, you may have rights to obtain a copy of information, correct it, delete it, withdraw consent, restrict processing, or opt out of sale, targeted advertising, certain sharing, or certain profiling. You may be entitled to use an authorized agent, appeal a denial, or contact a regulator. We respond within applicable legal deadlines and do not unlawfully discriminate against you for exercising a privacy right. If we cannot fulfill a request, we explain the reason and any appeal process available to you.
9. Children and younger users
The Services are not directed to children under 13, and children under 13 must not create an account or submit personal information. Users under the age of legal majority must have a parent or legal guardian's permission and supervision. If you believe a child under 13 has provided personal information, contact [email protected]. We will investigate and take the steps required by applicable law, including deletion where appropriate. These age rules do not replace any higher minimum age required by local law.
10. Security and international processing
We use reasonable administrative, technical, and organizational measures, including access controls, to protect personal information. No service can guarantee absolute security. Public report content is intended to be visible under the publication rules described above; security measures do not make that content confidential.
We and our providers may process information outside your state or country, where privacy protections may differ. Where required, we use the safeguards applicable to that processing.
11. Policy updates and contact
We publish an updated policy when our practices or obligations change. For material changes, we provide additional notice where required and obtain consent where required before applying a new use of personal information.
Privacy requests: [email protected] or https://redalertus.com/privacy/choices.
General support: [email protected] or https://redalertus.com/support.
Mail: MIRA Safety, LLC, 1713 Hur Industrial Blvd., Cedar Park, TX 78613, United States.