Community Guidelines
Last updated: February 25, 2026
Airlert is a flight-observation utility built to help travelers share real-time, text-only updates about flights. These guidelines set the behavior rules for using the community posting features.
These guidelines apply to your use of community features in Airlert. They supplement the Terms of Use.
Purpose and scope
Posts should be short, factual observations that help other travelers (for example: boarding status, gate changes, delays, and other on-the-ground updates). Airlert is not an official communications channel.
Helpful posting
- Be brief and specific: keep it short and relevant to the flight.
- Be factual: post what you directly observe or reliably hear; avoid rumors.
- Protect privacy: don’t post personal data about yourself or anyone else.
Posts are text-only and length-limited (for example, up to 50 characters). Display names are limited (for example, up to 24 characters) and are locked after your first post.
Prohibited content and behavior
The following are not allowed on Airlert:
- Harassment, hate, or threats toward any person or group
- Violence or incitement, including credible threats or instructions for wrongdoing
- Sexually explicit content
- Impersonation (for example, pretending to be an airline, airport, government agency, crew member, or Airlert staff)
- Spam, scams, or coordinated manipulation (including repetitive irrelevant posts)
- False or deliberately misleading updates (hoaxes or fabricated “status” claims)
- Personal or private information (names tied to real identity, phone numbers, emails, addresses, IDs)
- Illegal activity (promoting, facilitating, or admitting serious wrongdoing)
- Bypassing safeguards (attempting to circumvent on-device checks or display-name rules)
- Technical abuse (probing, exploiting, scraping, or overloading the Service)
Filtering disclosure
Airlert uses automated checks designed to reduce certain categories of objectionable content and obvious impersonation attempts. These checks run on your device (for example, client-side profanity and anti-impersonation checks) before a post is submitted.
Our servers enforce the saved display name associated with a device identifier. However, we do not operate a server-side profanity or “body text” filter for post text, and no automated system is perfect. Content you find objectionable may still appear.
Reporting
If you see a post that violates these guidelines, use Report. When you report a post:
- It is immediately hidden from your view on your device, and
- A report is logged on our backend (for example, by inserting a row in a reports table).
Logging a report may trigger an automated internal notification (for example, via a webhook that routes the report to our moderation channels like Slack). We do not guarantee that any report will be reviewed or that any particular outcome will occur, and we do not promise response times.
Blocking
You can block a traveler from within the app. Blocking is local-only:
- Blocking hides that traveler’s posts on your device (stored locally, for example in on-device app storage).
- The blocked traveler is not notified.
- Blocking does not prevent them from seeing your posts.
Consequences and limitations
We want Airlert to be useful and respectful. You are responsible for complying with these guidelines.
Airlert is anonymous and device-based, and current enforcement options may be technically limited. We may take steps that are reasonably available to us (for example, adjusting on-device checks, changing how content is displayed in the app, or other measures), but we do not promise that we can remove a specific post, identify a specific person, or prevent a repeat offender.
Your tools today include: (a) reporting content (which hides it locally and logs an internal alert), (b) blocking (local-only), and (c) using any in-app “Delete My Data” option (which anonymizes posts tied to your device).
Not for emergencies
Airlert is an informational tool only. It is not a substitute for official communications from your airline, airport authorities, or emergency services. In an emergency, contact the appropriate authorities directly.
Changes and contact
We may update these Community Guidelines from time to time by updating the “Last updated” date above.
Questions about these guidelines:
support@airlert.app
Airlert LLC, 465 Tuckahoe Road #1015, Yonkers, NY 10710