Tools for Humanity

• Name: Tools for Humanity
• URL: https://www.toolsforhumanity.com/
• Category: app-and-software operating company / World App operator / World software-development-and-maintenance boundary
• Tags: ethereum-ecosystem
• Summary: Tools for Humanity belongs in companies/ because a meaningful part of the World control story is not protocol stewardship in the abstract but who actually ships the main user-facing app, maintains software, composes the vendor graph, and operates the easiest product path most users and integrators touch first. World Foundation’s own materials explicitly name TFH as the provider and maintainer of World App and as a software-development-and-maintenance provider to the Foundation, while TFH’s own processor disclosures show a broad operating perimeter across World App, Orb App, World ID, Orb backend, and adjacent WLD infrastructure. That makes TFH a real company-shaped control surface rather than a background affiliation.
• What it does:
  • Provides and maintains World App according to the World user terms
  • Provides software development and maintenance services to World Foundation according to the Foundation privacy notice
  • Sits in the app-provider data path for Invite Rewards-style flows, where Foundation materials say reward-relevant data may come from app providers such as TFH
  • Operates a broad software and vendor perimeter spanning World App, Orb App, World ID, Orb backend, and WLD-adjacent infrastructure as shown on TFH’s processors page
  • Publicly presents itself as a large operating company with more than 500 staff and headquarters in San Francisco and Munich
• Key claims:
  • The World user terms say World App is provided and maintained by Tools for Humanity Corporation ("TFH"), which is the clearest reason this note belongs in companies/: the main app boundary is assigned to a named company
  • The Foundation privacy notice names Tools for Humanity Corp. as providing software development and maintenance services, which makes TFH part of the live operating stack rather than just a historical founder story
  • The same privacy notice says rewards data may come from app providers such as Tools for Humanity, which shows TFH sitting in at least some live feature and payout data flows
  • TFH’s own processors page discloses infrastructure and vendors across World App, Orb App, World ID, Orb backend, and WLD infrastructure, making the offchain control surface legible instead of hypothetical
  • The processors page names concrete dependencies like AWS, Blockaid, Fireblocks, Mongo Atlas, Tenderly, Twilio, and others for World-facing surfaces, which is useful because the practical authority in app-centric stacks often sits in the composed vendor shell as much as in the protocol itself
  • TFH’s homepage describes a company of over 500 scientists, engineers, creatives, economists and other various optimists founded in 2019 and headquartered in San Francisco and Munich, reinforcing that this is a substantial operating organization rather than a thin wrapper
• Whitepaper: No standalone company whitepaper is the point here. The useful primary materials are TFH’s homepage and processors page plus the World legal materials that assign TFH its role, captured in ../whitepapers/tools-for-humanity-primary-sources-2026-08-08.md.
• Sources:
  • https://www.toolsforhumanity.com/
  • https://www.toolsforhumanity.com/processors
  • https://world.org/legal/user-terms-and-conditions
  • https://world.org/legal/privacy-notice

Internal linkages

• Protocol / credential surface: world-id.
• Adjacent entity note: world-foundation for protocol stewardship, reference-service responsibility, and the broader legal shell.
• Read this note when the question becomes app-shaped or software-operator-shaped: who ships the default mobile app, who maintains the broad software stack, who composes the vendor perimeter, and where user-facing workflow defaults may quietly centralize.

Protocol / company boundary

• World ID is still the right note for credential issuance, registry-key policy, nullifier plumbing, and verifier-facing protocol mechanics.
• World Foundation is the better note for stewardship, authorized-partner framing, reference services, and parts of the legal and feature perimeter.
• Tools for Humanity is the better note when the real question is about product operation: app maintenance, software delivery, dependency composition, support and reward-adjacent data paths, and the default user-facing shell around the broader World stack.

Control surface

• The main control surface here is software distribution and the default user path. If most users reach World through World App, the company shipping and maintaining that app matters even when the protocol below it is nominally open.

• A second control surface is the vendor and backend perimeter disclosed on TFH’s processors page: hosting, fraud tooling, transaction security, custody/settlement integrations, messaging, analytics, and backend databases all sit inside one company-run operating shell.

• The right analytical move is not to say TFH controls World in one sentence. It is to separate layers cleanly: protocol and credential mechanics in World ID, stewardship and some legal/reference-service questions in World Foundation, and app/software operating gravity in Tools for Humanity.

• Last reviewed: 2026-08-08 UTC