> ## Documentation Index
> Fetch the complete documentation index at: https://www.offlineprotocol.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Frequently Asked Questions about Offline Protocol.

<Accordion title="What is Offline Protocol and how does it work?">
  Offline Protocol is a censorship-resistant technology stack enabling
  decentralized communication, peer-to-peer payments, and information sharing
  without the need for internet or telecom connectivity. It uses mesh networking
  (**WiFi-Direct, Bluetooth Mesh**) to keep users connected in any environment,
  including during disasters, protests, or in remote areas.
</Accordion>

<Accordion title="How does Offline Protocol ensure user privacy and security?">
  All communications and transactions are private. User identities are managed
  via **self-sovereign OfflineIDs**, and sensitive data is stored locally on
  devices. Analytics and data sharing are strictly opt-in, anonymized, and
  aggregated, with **privacy by default**.
</Accordion>

<Accordion title="What devices and operating systems are supported?">
  Offline Protocol is designed for both **Android and iOS** devices, leveraging
  cross-platform standards like WiFi-Direct and Bluetooth Mesh. The protocol is
  expanding to support **any Bluetooth-enabled device**, not just smartphones.
</Accordion>

<Accordion title="What ensures near-100% uptime and reliability for Offline Protocol apps in various scenarios?">
  Offline Protocol’s resilience is built on multiple layers: - Mesh Network
  Density: The mesh dynamically adjusts as more devices come online, minimizing
  dead zones and ensuring reliable delivery. - Battery Efficiency: Use of
  Bluetooth Low Energy (BLE) extends device uptime. - Rigorous Testing:
  Real-world simulations ensure messages are stored locally and relayed when
  possible, even under high-stress or congested conditions.
</Accordion>

<Accordion title="What is required for Offline Protocol to provide robust coverage in a specific area?">
  * Node Density: Urban areas need fewer nodes due to higher device
    concentration; rural areas require more. - Critical Mass: Typically, **5–50
    active nodes** are needed in a localized area for optimal performance, but
    this varies by context. - The protocol is expanding to utilize **any
    Bluetooth-enabled device as a node**, not just smartphones.
</Accordion>

<Accordion title="What are the top use cases and user segments for Offline Protocol?">
  * Public Events: Festivals, sporting events, and protests—users can
    communicate, share locations, and transact without overloaded cellular
    networks. - Disaster Response: Enables critical information dissemination and
    coordination when telecom infrastructure is down. - Rural and Remote
    Microfinance: Facilitates secure microtransactions and record-keeping for
    farmers and small businesses.
</Accordion>

<Accordion title="What are the unique benefits of Offline Protocol vs. Web2 P2P networks?">
  * Incentivized Participation: Rewards for relayers and participants, aligning
    incentives for network growth and reliability. - Self-Sovereign Identity:
    OfflineIDs are user-owned, portable identities with verifiable reputation,
    especially valuable for unbanked or undocumented populations.
</Accordion>

<Accordion title="How will Offline Protocol’s GTM work in rural areas with no internet?">
  * Leverage Existing Devices: Local “super-spreaders” with internet access
    distribute the APK via offline sharing, earning rewards for onboarding others.
  * Community Training: NGO partners facilitate workshops to educate and empower
    local communities. - Future Hardware: Plans to deploy pre-configured mesh
    nodes with NGOs and manufacturers to anchor the network.
</Accordion>

<Accordion title="Does Offline Protocol plan to offer an SDK for third-party apps, and how will analytics be balanced with user privacy?">
  Yes. Offline Protocol plans to offer an SDK enabling any app to integrate its **mesh networking**, **encrypted messaging**, and **DORS (Dynamic Offline Relay Switch)** features, allowing apps to function without internet dependency.

  User privacy is paramount: Sensitive data remains stored locally on devices, and any analytics will be opt-in, anonymized, and aggregated.\
  The SDK is designed with **privacy by default**, aligning with the ethos of censorship-resistant, decentralized technology.
</Accordion>

<Accordion title="What are the most promising third-party applications for the Offline Protocol SDK?">
  * Disaster Relief Tools: Emergency messaging, resource tracking, aid
    coordination. - Event Apps: Ticketing, secure payments, group messaging for
    large gatherings. - IoT Networks: Smart devices for agriculture, logistics,
    and supply chains in offline environments. - Local Economies: Offline
    marketplaces, remittance services, and microfinance.
</Accordion>

<Accordion title="How does Offline Protocol handle message delivery and reliability?">
  Messages are stored locally and relayed through the mesh network, ensuring
  delivery even if the recipient is temporarily offline. The network dynamically
  adjusts as devices join or leave, minimizing dead zones and maximizing uptime.
</Accordion>

<Accordion title="What are the requirements for running a node or relayer?">
  Any compatible device (**smartphone, IoT device**) can act as a node by
  participating in the mesh network. Battery-efficient protocols like BLE are
  used to minimize power consumption. Node operators may receive **token
  incentives** for providing coverage.
</Accordion>

<Accordion title="How can I request support or report an issue?">
  Users can email us at **[support@offlineprotocol.com](mailto:support@offlineprotocol.com)** for account deletion, data requests, or product queries.\
  For legal/privacy matters, reach out at **[legal@offlineprotocol.com](mailto:legal@offlineprotocol.com)**.

  Community support is also available via **forums, Discord, and local ambassadors**.\
  For urgent issues in the field, the protocol’s **broadcast messaging** feature can alert nearby support nodes.
</Accordion>