This is fine
View quoted note →
Big Bad John
npub13ndp...0svh
CEO at Synonym, creators of Pubky, Bitkit, and Blocktank.
Grok is here to help educate Nostr on how BOTH relays and nostr clients require ToS, PP, and age limitations:
### Obligations for Nostr Relays
Relays act as servers that store and forward user-generated events (notes, messages, etc.), making them akin to data hosts or processors. With an international user base, relays face obligations under various global laws, though these are not uniform and depend on the relay operator's location, data handled, and user origins.
- **Terms of Service (ToS)**:
- Advisable for liability protection and defining usage rules (e.g., prohibiting illegal content). In the US, this helps invoke DMCA safe harbors for copyright issues. In the EU, consumer protection laws may require clear terms to avoid disputes. Without a ToS, operators risk legal exposure in jurisdictions with strict hosting liability, like under the EU's Digital Services Act (DSA), which mandates transparency for intermediaries.
- **Privacy Policy (PP)**:
- Often required if personal data (e.g., IP addresses, public keys, metadata) is processed. Under the EU's GDPR, relays must provide a PP outlining data collection, retention, and user rights (e.g., access/deletion), with fines up to 4% of global revenue for non-compliance. Similar mandates apply in California (CCPA/CPRA), Brazil (LGPD), and Canada (PIPEDA). For international users, cross-border data transfers require safeguards, typically detailed in a PP.
- **Age Limitations**:
- Necessary to comply with children's privacy laws. In the US, COPPA requires parental consent for users under 13, potentially applying if relays handle minors' data. GDPR sets digital consent ages at 13-16 (country-dependent), requiring mechanisms to verify or restrict access. Operators should implement age gates or policies to mitigate risks, especially in regions like South Korea (under 14) or Australia.
Relay operators commonly include these via NIP-11 metadata for transparency, but legal consultation is essential as obligations vary by jurisdiction.
### Obligations for Nostr Clients (Apps)
Clients are applications (mobile/desktop/web) that connect users to relays for sending/receiving events. Distribution via app stores or direct downloads imposes additional requirements, driven by platform policies and international laws.
- **Terms of Service (ToS):
- Typically required by app stores (e.g., Apple App Store, Google Play) to define user agreements, app functionality, and limitations. For international distribution, this aligns with consumer rights laws (e.g., EU Consumer Rights Directive, Canadian consumer protection) to ensure terms are fair and non-misleading.
- **Privacy Policy (PP)**:
- Mandatory for app stores, which reject submissions without one explaining data practices (e.g., wallet integrations or device access). GDPR/CCPA equivalents demand transparency on data sharing with relays or third parties. For global users, apps must address data flows to potentially non-compliant regions.
- **Age Limitations**:
- Enforced by app stores through ratings: E.g., Apple/Google may require 13+ or 17+ for social features, with COPPA/GDPR compliance for minors. Apps must include age verification if collecting personal data from children, or risk removal/enforcement actions in the US, EU, or other regions.
In practice, both relays and clients should adopt these elements to ensure compliance, trustworthy operations, particularly with diverse international users. Operators are advised to seek region-specific legal advice.
All of nostr right now, scrambling to find whichever janky Nostr client didnt include a ToS so they can claim they dont use one that does, so they can keep being mad at me.
People are telling me Terms of Service are bad, but I cant figure out which Nostr apps dont require them.
If Nostr is already censorship resistant, and does not follow the law, where do i find the illegal stuff like drugs and edibles or whatever?
How does nostr deal with pedos?
Shout out to my number one fan, @corndalorian.