رفتن به محتوا

Frequently asked questions (FAQ)

این محتوا هنوز به زبان شما در دسترس نیست.

This FAQ answers common questions about Anonomi Messenger’s design, capabilities, and limitations.

If you’re new, also read:


Anonomi Messenger is designed to reduce metadata exposure, not to provide magical or absolute anonymity.

What it does:

  • Avoids centralized servers
  • Routes internet traffic over Tor
  • Supports fully offline communication
  • Minimizes unnecessary identifiers

What it cannot do:

  • Protect you from a compromised device
  • Fix unsafe behavior
  • Make you anonymous if you reveal your identity through actions or content

Anonomi Messenger is a tool — how safely it’s used matters.


No central servers.

Communication happens:

  • Directly between devices (offline modes)
  • Over Tor for internet-based communication
  • Via optional helper components (e.g., Postbox) that do not act as message-reading servers

There is no central infrastructure to subpoena, seize, or log conversations.


Anonomi Messenger relies on:

  • Low-level networking control
  • Offline transports
  • Background operation without platform mediation
  • Distribution outside centralized app stores

Current iOS platform constraints make these guarantees impossible without compromise.

See:


Can I use Anonomi Messenger without the internet?

Section titled “Can I use Anonomi Messenger without the internet?”

Yes.

Anonomi Messenger supports:

  • Wi-Fi (local network)
  • Bluetooth (proximity)
  • External storage / store-and-forward
  • Offline app distribution

In some environments, staying offline is safer than trying to connect.

See:


Assume the device is compromised.

Anonomi Messenger helps reduce exposure, but:

  • It cannot protect messages already stored on the device
  • It cannot protect against coercion or forced unlocks
  • It cannot remotely “save” a seized device

Use:

  • App lock
  • Stealth mode
  • Panic workflows
  • Good OPSEC habits

See:


The panic workflow is a risk-reduction tool, not a guarantee.

Depending on configuration and situation, triggering panic may:

  • Delete local app state
  • Lock or hide the app
  • Send a panic message to designated contacts (when possible)

It does not:

  • Guarantee data destruction on seized hardware
  • Override OS-level or hardware-level forensics
  • Protect against ongoing coercion

See:


Groups increase exposure by nature:

  • More participants
  • More devices
  • More opportunities for compromise

Private groups are safer than public groups, but:

  • Any member can leak content
  • Metadata risk grows with group size

Keep groups:

  • Small
  • Purpose-driven
  • Short-lived when possible

Voice messages carry biometric risk.

Anonomi Messenger offers optional voice distortion to reduce voice identification risk, but:

  • Distortion is not a guarantee
  • Voice content itself may reveal identity
  • Background sounds can be identifying

Use voice messages only when appropriate.

See:


Anonomi Messenger:

  • Uses Monero primitives designed for privacy
  • Generates unique subaddresses per request
  • Avoids centralized payment servers

However:

  • Payment privacy depends on wallet hygiene
  • Amounts and timing may still leak information
  • Fiat conversions require user-supplied rates

See:


Can I recover my account if I lose my device?

Section titled “Can I recover my account if I lose my device?”

No.

Anonomi Messenger does not rely on central accounts or recovery servers.

If you lose your device or delete the app:

  • Your account and keys may be permanently lost
  • Your contacts may not be recoverable

This is a tradeoff for decentralization.


That depends on your jurisdiction.

Anonomi Messenger is a communication tool. However:

  • Use of Tor may be restricted in some regions
  • Encryption laws vary
  • Offline distribution may raise suspicion in some environments

Know your local risks before use.


Start here:

  1. Threat model
  2. Operational security basics
  3. Scenarios and tradeoffs

Anonomi Messenger works best when you understand why you’re using a feature — not just how.


If your question isn’t answered here:

  • Check the relevant section in the docs
  • Review the threat model
  • Ask in the project channels (when appropriate)