1. Our safety approach
Airwafs is designed around practical user protection, clear rules, and proportionate enforcement. Safety controls should be easy for users to find and realistic for Airwafs to operate consistently.
Our Community Guidelines explain what is allowed. This page explains the main tools and processes used to protect users.
2. Reporting
Airwafs will provide in-app reporting for relevant user-generated content and user interactions. Depending on the feature, users may be able to report a profile, post, discussion or reply, private message, or group message.
Reports may include a reason selected by the reporter and limited context needed for review. Reports should be submitted in good faith.
We do not promise a fixed review time for every report. Higher-risk safety reports may be prioritized.
3. Blocking and unwanted contact
Where users can interact directly, Airwafs will provide a blocking or equivalent user-protection control designed to stop or limit unwanted one-to-one interaction.
Blocking is intended to be available without requiring the blocked person to approve it. Exact effects may vary by feature and will be explained in the app.
4. Moderation and enforcement
Airwafs may use user reports, automated safety signals, account history, and human review to identify possible violations.
Depending on context, severity, evidence, and repeat behavior, Airwafs may take one or more actions:
- take no action when no violation is found;
- show a warning or safety notice;
- filter, label, age-limit, or reduce visibility where appropriate;
- remove content;
- temporarily restrict a feature;
- suspend an account; or
- terminate an account for serious or repeated violations.
Airwafs may also preserve information where necessary for security, legal compliance, or a valid investigation.
5. Child safety
Airwafs has zero tolerance for child sexual abuse and exploitation. Content or behavior that sexually exploits or endangers a child is prohibited.
Airwafs will maintain an in-app reporting mechanism, take appropriate action on confirmed violations, preserve relevant information where legally required, and make legally required reports to appropriate authorities or child-safety organizations.
Before launch, Airwafs will finalize its age and consent design. Where U.S. children's privacy law applies, Airwafs will not knowingly collect personal information from a child under 13 without the notice and verifiable parental consent required by law.
6. Sensitive content
Some content may be restricted, filtered, labeled, or age-limited instead of automatically removed when context matters and the content is otherwise permitted.
Airwafs may use warnings or content controls for sensitive material so users can make informed choices. Illegal content, sexual exploitation, credible threats, and other prohibited content may be removed rather than merely labeled.
7. Private messages and groups
Private or group messaging does not exempt content from Airwafs rules. Users will be able to report relevant private or group interactions when those features are available.
Airwafs does not intend to publicly display private messages. Limited access may occur when needed to review a user-submitted report, protect the service, comply with law, or investigate serious abuse, consistent with our Privacy Policy.
8. Account and platform security
Airwafs is being built with measures such as secure network transport, server-side validation, rate limiting, least-privilege access, separated website and application resources, and security logging where appropriate.
Users should keep account credentials private and report suspected account compromise to Airwafs support.
9. Spam, fraud, and manipulation
Airwafs may restrict automated abuse, fake engagement, repetitive spam, malicious links, scams, impersonation, suspicious account activity, and attempts to bypass safety or security controls.
Anti-abuse controls may include rate limits, deduplication, account restrictions, technical signals, and manual review.
10. Appeals and review
Where appropriate, Airwafs may provide a way to request review of an enforcement decision. An appeal does not guarantee reversal.
We aim to use the least severe action that reasonably addresses the violation, except where serious safety, legal, fraud, or security concerns justify stronger action.
11. Emergency and legal requests
If Airwafs reasonably believes information must be preserved or disclosed to comply with applicable law, valid legal process, or an immediate and serious safety risk, we may do so in accordance with applicable law and our Privacy Policy.
Airwafs support is not an emergency service.
12. Safety contact
We may introduce a dedicated safety email later. Until then, this monitored address is the designated contact for safety matters.
13. Changes to this page
We may update these safety standards when Airwafs features change, new risks emerge, laws change, or app-store requirements are updated. The date at the top of this page will be updated when changes are published.