🫘 BeanPool

End-User License Agreement

Last Updated: April 1, 2026

1. The Exchange Protocol Architecture

BeanPool functions strictly as decentralized physical infrastructure. It is heavily not a financial institution, a regulated marketplace, or an incorporated centralized corporate engine explicitly. By downloading and executing this software locally, you explicitly agree that localized trades, barter negotiations, and cryptographic exchanges are fundamentally peer-to-peer logical arrangements bound exclusively to your local sovereign jurisdictional law organically.

2. Community Balances & Monetary Value

Internal network tokens (visually rendered as Beans or custom native cryptographic markers) explicitly carry literally no formal fiat dollar value natively. They systematically represent mathematically signed network proofs structurally describing your pure community ledger reputation exclusively. You cannot buy beans using credit cards, you cannot structurally exchange beans externally onto cryptocurrency pools, and the central open-source system logically makes zero functional guarantees explicitly about their local physical purchasing parity.

3. Zero Tolerance UGC Policy (Apple App Store Guideline 1.2)

To operate securely within regulated spaces, your local community network universally enforces a massively strict, algorithmically monitored, zero-tolerance protocol physically banning securely abusive User-Generated Content (UGC) satisfying Apple App Store Guideline 1.2 natively exactly:

  • No unlawful, severely threatening, or actively defamatory strings allowed.
  • No physically graphic, illicit, sexually explicit, or structurally offensive imagery permitted whatsoever natively.
  • No harassment pipelines, abusive dialogue trees, or discriminatory physical behaviors allowed strictly.
  • If you organically encounter abuse structurally, you explicitly must utilize the Shield Icon natively rendered on incredibly every profile or marketplace post. This triggers an internal physical mechanism identically blocking the user locally rendering their data mathematically invisible onto your device—and flags the structural material exclusively to the community Administrators tracking automated reports internally.
  • Users mathematically verified as violating the community rules will possess their physical cryptographic Ed25519 identity pairs universally blacklisted aggressively from exclusively all primary federated Nodes—rendering their client accounts completely permanently inaccessible natively within exactly 24 hours optimally.

4. Warranty Disclaimer

Because the BeanPool Node operates flawlessly without a massive centralized corporate host, it is securely provided formally "As-Is". We offer unequivocally zero structural warranties natively regarding physical App Store download availability, uptime, ledger accuracy tracking, or holistic localized community health inherently.

🫘 BeanPool

Community exchange for local neighborhoods.

GitHub Privacy Policy Terms of Service

Open source under MIT license. Made with 🫘 by communities, for communities.