Diffuse terms of service

Effective 2026-07-31 · Offline Protocol, Inc. · legal@offlineprotocol.com

These terms govern Diffuse and operator-controlled services provided by Offline Protocol, Inc., a Delaware corporation. Public broadcasting is a direction to replicate a signed object across systems that Offline Protocol may not control.

Agreement and eligibility

By continuing through onboarding, creating or connecting an OfflineID, or using Diffuse after these terms are presented, a user agrees to these terms and acknowledges the privacy notice. Users must be at least 13 and legally able to agree; minors must have parent or guardian permission where applicable. Users are responsible for laws governing their content, recording, preservation, encryption, and distribution.

Public distribution and revocation

A public broadcast may be copied by nearby devices, mesh nodes, Nostr relays, the hosted global archive, exports, and third parties. A valid signed revocation tells compliant nodes to stop display and re-serving; it cannot guarantee remote deletion or recall screenshots, exports, caches, recipient copies, or independent archives.

Evidence limits

Hashes, signatures, source metadata, co-signatures, and timestamp commitments can support byte integrity and key-signature claims. They do not by themselves prove legal identity, truth, consent, complete context, exact time or location, chain of custody, or admissibility. Diffuse is not an emergency service, legal advice, or an official evidence custodian.

User content and license

Users retain their rights and must have the authority and lawful basis to capture, preserve, and distribute submitted material. For public content, users grant Offline Protocol the non-exclusive rights needed to host, cache, reproduce, transmit, verify, display, preserve, and make the content available through Diffuse, and direct compatible network participants to copy and relay the public object. Connections-only rights are limited to delivery and operation for chosen recipients.

Accounts and security

Users are responsible for their email account, device, OfflineID session, keys, recovery material, and recipient choices. OfflineID labels and signing keys are not government identity. Signed-in users can request OfflineID deletion in Profile → Advanced settings using a code sent to their verified email. Confirmation starts a 30-day provider recovery period and immediately triggers Diffuse local crypto-erasure. Mesh SDK 0.17.0 does not expose an API to erase its platform-protected signing key, and neither deletion nor wipe recalls distributed content. People without app access can use the published deletion page.

Prohibited use

Users may not distribute child sexual abuse material, non-consensual intimate imagery, exploitation, unlawful threats, doxxing, malware, spam, forged evidence, knowingly false safety reports, or material that unlawfully violates privacy, intellectual-property, confidentiality, or other rights. Users may not evade screening, poison indexes, manipulate trust, attack the network, or test production systems without written authorization.

Safety and independent services

Offline Protocol may restrict content or access on services it controls for safety, security, legal compliance, rights protection, or material violations. It cannot control independent nodes, relays, publishers, forks, or exports. Third-party and open-network services have their own terms, privacy practices, availability, and risks.

Software and intellectual property

Offline Protocol grants a limited personal license to use the distributed app for its intended purpose. Diffuse, Offline Protocol SDKs, names, designs, documentation, and operator services remain protected by intellectual-property law; open-source components remain governed by their licenses.

Changes and termination

Users may stop using Diffuse at any time. Offline Protocol may change, suspend, or discontinue operator-controlled features when reasonably necessary for maintenance, security, law, network protection, or a material violation. Ending the operator relationship does not disable independent software or erase public objects from independent networks. Material term changes receive reasonable notice and renewed acceptance where required.

Disclaimers and liability

To the maximum extent permitted by law, Diffuse is provided as is and as available without implied warranties or guarantees of availability, delivery, propagation, security, truth, legal admissibility, or universal deletion. To the maximum extent permitted by law, aggregate liability is limited to the greater of US$100 or amounts paid for Diffuse in the preceding 12 months, excluding liability that cannot lawfully be limited.

Indemnity

To the extent permitted by law, users must defend and indemnify Offline Protocol against third-party claims arising from their content, unlawful or unauthorized use, material breach, or infringement of another person’s rights, except to the extent caused by Offline Protocol’s own unlawful conduct, negligence, or breach.

Disputes

Delaware law governs except for mandatory local consumer protections. After a 30-day good-faith informal process, covered disputes proceed in individual AAA consumer arbitration, with small-claims and urgent injunctive-relief exceptions. Jury and class proceedings are waived to the extent permitted. A user may opt out by emailing legal@offlineprotocol.com within 30 days after first acceptance.

App stores and general terms

These terms are between the user and Offline Protocol, not an app store. Apple has no support obligation and, where its standard terms require, Apple and its subsidiaries are third-party beneficiaries. The terms and privacy notice form the entire operator agreement; unenforceable provisions are narrowed, non-enforcement is not waiver, and assignment may occur with a corporate transaction or by law.

Contact

Legal notices, disputes, rights requests, and arbitration opt-outs must be sent to legal@offlineprotocol.com. The complete engineering-controlled terms are also maintained in the Diffuse source repository at docs/TERMS.md.