AWARE Neighborhood Alert Platform Privacy Policy

AWARE is a web-based neighborhood alert dashboard that publishes public safety events, including police, ICE, medical, fire, and community notices. This policy applies to visitors of the website and anyone who uses the report form to submit an alert to the platform.

We collect and process information only to support the website’s functionality and to present incident alerts to users. Public browsing does not require an account, but submitting a community alert requires authentication through the backend.

• Public incident feed data: The site retrieves event metadata from external provider APIs, including incident type, neighborhood, timestamp, description, and source confidence.
• Authentication data: If you create an account or log in to report an alert, the site sends your email address, username when registering, and password to the backend authentication service and stores the returned JWT in browser storage on your device.
• Community report submissions: When you submit a report, the form captures the selected event type, neighborhood text, and incident details. This information is used immediately to create an alert card on the page.
• Technical request data: Standard HTTP request data such as IP address, browser user agent, device type, operating system, and language preferences may be collected by the web host for basic site operation and security.
• Performance and error data: If the site logs errors or request failures on the server, those technical logs may include timestamps, requested resources, and status codes needed for diagnostics.

• Payment information, government-issued identification numbers, or financial account data.
• Postal addresses, telephone numbers, or direct personal identifiers beyond the account information voluntarily provided for authentication.
• Social security numbers, driver’s license numbers, or other sensitive identification data.
• Subscription histories or profiling data unrelated to account authentication and site operation.

• Display live and community-submitted neighborhood alerts.
• Authenticate users who want to submit alerts and persist the returned JWT locally so the reporting flow stays unlocked between visits on the same device.
• Provide search, filtering, and pagination for event feeds.
• Support site stability, performance, and security diagnostics.
• Process voluntary community report submissions and render those reports in the incident feed.

We do not use collected data for marketing, advertising, or profiling purposes. Any community-submitted alert is intended solely for display on the site. Authentication data is used only to control access to the report flow.

At this time, AWARE does not deploy third-party tracking cookies, analytics scripts, advertising pixels, or behavioral profiling tools. The site does use browser storage for core functionality, including retaining the backend-issued JWT needed to keep a user signed in for reporting.

If tracking or analytics services are introduced later, this policy will be updated to disclose their use and to explain how users can opt out.

We do not sell, rent, or lease personal information to third parties. The site uses external incident feed providers that may have their own data collection and privacy practices.

The types of third parties the site may interact with include:

• Hosting providers and infrastructure services that deliver this website.
• External alert feed APIs that supply incident data used to populate the live feed.
• Security or monitoring services used to protect site uptime and detect abuse.

Any third-party service that accesses personal data through the site will be governed by its own privacy policies, and we encourage users to review those policies separately.

Users may submit incident reports through the “Report an Alert” form. These reports are published immediately within the local page session and are visible to anyone viewing the feed.

• Do not include personal information about yourself or others in report text.
• Do not submit sensitive details such as medical records, exact home addresses, license plates, or national ID numbers.
• Submitted reports should focus on event type, neighborhood, and observable incident details.

AWARE does not moderate or verify every report before display. The accuracy and completeness of community-submitted alerts cannot be guaranteed.

The site retains only the information required to render alerts and maintain web operations. Reports and incident data are preserved for as long as they are needed to support the live feed experience. The locally stored JWT remains in browser storage until it expires, is cleared by the user, or is removed during logout.

AWARE takes reasonable measures to protect data in transit and to secure the website from unauthorized access. The site uses HTTPS to encrypt communications between visitors and the server.

Although we strive to protect information, no system is completely secure. We cannot guarantee absolute security against unauthorized access, disclosure, or loss.

The AWARE website may be hosted or served from servers located in different countries, and external incident feed providers may operate internationally. By using the site, you consent to the transfer of information across international borders as necessary to provide the service.

AWARE is not intended for use by children under the age of 16. We do not knowingly collect personal information from children under 16. If a parent or guardian believes that a child has provided personal data through this site, please contact the site operator so we can remove the information promptly.

We may update this privacy policy as the site evolves or as legal requirements change. The version available on this page is the current policy. Significant changes will be reflected here, and users should review this page periodically.

For questions about this privacy policy, to request additional information, or to report any privacy concerns, please contact us at support@aware-community.com.

We aim to respond to privacy-related inquiries within 3 business days. If your request relates to a community alert submission, include as much context as possible so we can address the issue promptly.