Waev

Waev Communication Safety & Acceptable Use

Version 1 · Effective July 19, 2026

Waev is a local-first client for decentralized mesh communication. This policy describes safer use and the controls Waev provides for messages, profile details, channel details, reactions, and other content you encounter or transmit. It is an informational policy, not a membership agreement or access gate. Reviewing, acknowledging, or accepting it is never required to connect, receive, transmit, use background connectivity, or access live mesh features.

MeshCore networks are independent and user-operated. Waev does not own, operate, or centrally moderate them.

Zero tolerance for abusive content

Do not use Waev for:

  • harassment, bullying, credible threats, stalking, or targeted intimidation;
  • hate speech or discriminatory abuse;
  • sexual exploitation, non-consensual sexual content, or sexual content involving minors;
  • graphic violence, instructions encouraging self-harm, or content intended to facilitate imminent physical harm;
  • spam, scams, fraud, impersonation, or malicious deception;
  • trafficking, illegal sales, or instructions whose primary purpose is to facilitate unlawful conduct; or
  • any other content that violates applicable law or another person's rights.

Explicit abusive content is not permitted when presented as a joke, quotation, username, channel name, reaction, or encoded message.

Controls available in Waev

Waev applies a narrow, high-confidence safety check to text before sending and before received peer text reaches chat, notifications, previews, snapshots, or local caches. It applies the same check to outgoing identity fields. This is a focused safeguard, not comprehensive moderation. You can also:

  • report a message from its action menu and review the report before sending;
  • block a direct contact on the current device; and
  • hide an exact channel display name on the current device.

Direct-contact blocks use the contact's currently observed public-key identity. Mesh identities can be rotated; a new key appears as a new observed identity, so Waev cannot permanently identify or block a real-world person across keys. Public channel frames do not provide Waev with an authenticated sender identity, so a channel hide applies only to the exact display name and channel shown; a sender can evade it by changing names. A local block or hide rule does not remove copies that were already transmitted to another radio or client.

Reporting a concern

Use Report on a message, or email admin@waev.app. Include enough context to identify the concern, but do not include passwords, radio credentials, transport keys, precise location, or unrelated sensitive data.

The in-app report flow prepares a reviewable email. Nothing is submitted until you choose to send it through your mail provider.

Credible threats, child-safety concerns, and reports of imminent harm receive priority. Review timing depends on the report and the decentralized-network evidence available.

Enforcement and decentralized-network limits

Waev does not tolerate abusive use. Content may be stopped before transmission, and reports may lead to product safeguards, support action, or restriction of services controlled by Waev where technically and legally available.

MeshCore networks are decentralized and may relay content without a Waev-owned server. Waev cannot recall transmitted traffic, delete copies stored by peers, or impose a network-wide block on hardware and software it does not control. Reports of illegal or dangerous content do not make Waev an emergency service; contact the appropriate local authority when immediate help is required.

Changes

Waev may update this policy as the product and safety risks evolve. Updates may be surfaced through a passive notice or an Updated badge near the policy, but they never disable live mesh features or require acknowledgment. The Explore Demo remains available and does not transmit or persist mesh activity.