> ## 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.

> ## Agent Instructions
> These docs target Mesh SDK v0.30.0. Match the installed package and binding before generating code. Start at /getting-started/agents for task-specific reading paths. Apps that call enableTelemetry on 0.26.0 to 0.29.0 should update to 0.30.0: the telemetry uploader now trusts only the telemetry endpoint's issuing roots.
> Call the company and product Offline Protocol, never Offline alone. Current packages: @offline-protocol/mesh-sdk 0.30.0 (React Native), offline-protocol-sdk 0.30.0 on PyPI (Python 3.10 to 3.13; wheels for macOS 14+ arm64, Linux x86_64 and aarch64 with glibc 2.34+, Windows x86_64; other hosts build from source; extras lan and http add LAN discovery, the HTTP front and offline-protocol-verify), the offline-protocol crates 0.30.0 on crates.io, the OfflineProtocolSDK Swift package 0.30.0 (preview, iOS 13+ only), the Android library com.offlineprotocol:offline-protocol-sdk 0.30.0 on Maven Central (preview, minSdk 24), the Java binding com.offlineprotocol:offline-protocol-java 0.30.0 on Maven Central (JDK 22+, native library from the GitHub release's desktop archives), the C header offline_protocol.h with the native library in the GitHub release's desktop archives, the offline_protocol Flutter plugin (preview, not on pub.dev; a path dependency on the SDK repository at tag v0.30.0), @offline-protocol/id-react 0.2.0, @offline-protocol/id-react-native 0.3.3, @offline-protocol/pol 0.1.2 and @offline-protocol/cli 0.2.8. Canonical docs URLs start with https://www.offlineprotocol.com/docs.
> The Mesh SDK runs in a native app or gateway. A browser OfflineID SDK integration does not provide browser mesh transport. Local mesh operation does not require a portal account or API key. The Mesh SDK appId is a mesh app identifier the developer chooses, not the portal App ID (app_...) that OfflineID and Proof of Location require.
> In v0.30.0 service RPC bodies are sealed in the 1:1 MLS session once the recipient runs 0.29 or later and the session is confirmed; discovery, the first request to a provider never met, and requests to older peers are signed plaintext, so keep secrets out of service bodies unless the event says encrypted: true. The HTTP front (offline-protocol-service --http) always carries calls inside encrypted direct messages but does not authorize callers. Message delivery, durable local acceptance and backend commit are distinct outcomes. Use the workflow guide for the required application logic.
> Offline Protocol CLI 0.2.8 is on npm (@offline-protocol/cli, command offline). Its local MCP server, named offline-protocol, runs with npx -y @offline-protocol/cli@0.2.8 mcp serve and requires no login or key. Hosted MCP is at https://mcp.offlineprotocol.com/mcp with an app API key in Authorization: Bearer and the matching App ID in x-app-id; organization keys are rejected, and Claude Desktop and Claude.ai cannot send these headers; there, use the public read-only endpoint https://mcp.offlineprotocol.com/public/mcp as a custom connector, or local MCP to scaffold or edit projects. Follow /tools/overview for setup and do not invent commands beyond it. MCP provides integration context and planning, not mesh execution; file-writing tools are local only.
> In v0.30.0 phone Wi-Fi peer streams carry data: Android over Wi-Fi Direct (the SDK forms the group with autoAccept on Android 10+) and over the Wi-Fi network it is on (DNS-SD), iOS over Network framework (LAN or AWDL). Android and iOS meet over that slot only on a shared Wi-Fi network that allows multicast; iOS 0.28 and later does not see iOS 0.27 or earlier over it. Otherwise use BLE or a provisioned relay across platforms. The Swift and Android packages are previews whose public names may change; the Android library is on Maven Central from 0.29.0 only, so never give a Gradle line for an earlier version. The receiver core ACKs before application persistence; use application acceptance for durable workflows.
> Proof of Location is Sepolia testnet witness evidence, not zero-knowledge proof or proof of presence. The geohash is public onchain. Read /proof-of-location/security before integration.

# Policies and licensing

> Find Offline Protocol's privacy policy, developer terms, data processing terms, security disclosure policy and SDK licensing.

The canonical legal documents are published at [offlineprotocol.com/legal](https://www.offlineprotocol.com/legal). They share one set of definitions, so a term such as Customer, Organization, Application or End User means the same thing in each.

## Platform documents

| Document | What it covers |
| - | - |
| [Privacy policy](https://www.offlineprotocol.com/privacy) | Personal data across the website, these docs, the developer portal, the CLI and MCP servers, and the hosted services. |
| [Developer terms of service](https://www.offlineprotocol.com/legal/developer-terms) | Accounts, organizations, API keys, hosted services, plans, billing, overage, billing limits, usage pauses and data responsibilities. |
| [Acceptable use policy](https://www.offlineprotocol.com/legal/acceptable-use) | What you, your team, your apps and your end users may not do with the services. |
| [Data processing addendum](https://www.offlineprotocol.com/legal/dpa) | Processor terms for end-user data your apps send to hosted services, security measures and Standard Contractual Clauses. |
| [Subprocessors](https://www.offlineprotocol.com/legal/subprocessors) | Third parties that process data for the services. |
| [Cookie notice](https://www.offlineprotocol.com/legal/cookies) | Cookies and browser storage on the website, portal and docs. |
| [Security and responsible disclosure](https://www.offlineprotocol.com/legal/security) | How to report a vulnerability, response times and safe harbor. |
| [Website terms of use](https://www.offlineprotocol.com/terms) | Browsing offlineprotocol.com and these docs. |

For what each hosted service receives and keeps, see [data handling by service](https://www.offlineprotocol.com/docs/legal/data-handling).

## SDK licensing

The Offline Protocol mesh SDK is AGPL-3.0-only, with a commercial license available; the OfflineID and Proof of Location client packages are MIT or ISC. See [licensing and hosted services](https://www.offlineprotocol.com/docs/operations/licensing.md). A hosted plan does not grant a commercial mesh SDK license.

## App policies

| App | Documents |
| - | - |
| Fernweh | [Privacy policy](https://fernweh.chat/privacy), [terms of service](https://fernweh.chat/terms) |
| Fernweh SMS sign-in codes | [Privacy policy](https://www.offlineprotocol.com/docs/legal/twilio-sms-campaign-privacy-policy), [terms](https://www.offlineprotocol.com/docs/legal/twilio-sms-campaign-terms-of-service) |
| MINE | [Privacy policy](https://mine.offlineprotocol.com/privacy) |

App policies apply to those apps only. They do not replace the platform documents above.

## Contact

Privacy requests, legal questions, SDK licensing and anything else policy related: [legal@offlineprotocol.com](mailto:legal@offlineprotocol.com). Security and vulnerability reports only: [security@offlineprotocol.com](mailto:security@offlineprotocol.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.