Katch authorizes external missions before funding calldata is issued. The goal is to let creators fund useful real-world data collection without asking contributors to capture unsafe, private, or non-consensual information.

​
Unsafe or private data

Do not request:
  • passwords, private keys, seed phrases, wallet secrets, or login screens
  • credit cards, social security numbers, passports, driver licenses, or medical records
  • private messages, private documents, private homes, or home addresses
  • invasive capture of children or private people
  • footage that encourages harassment, trespassing, or breaking venue rules
Rejected example: 
{
  "title": "Film someone's laptop at a cafe",
  "verification": {
    "accept": ["Video shows readable private messages"],
    "reject": ["Screen is unreadable"]
  }
}
Accepted alternative: 
{
  "title": "Film the public cafe menu board",
  "verification": {
    "accept": ["Menu board is visible and readable"],
    "reject": ["Private customer or employee information is readable"]
  }
}
External mission creators receive accepted mission outputs after Katch publishes the mission. Mission instructions should make this clear to contributors. Creator access is limited to accepted and curation-accepted submissions. Rejected, pending, flagged, and withdrawn submissions are not shared with mission creators.

​
World ID and contributor identity

Katch uses World ID as a proof-of-personhood layer for contributors. The purpose is sybil resistance: reducing the ability for one person to farm rewards through many accounts. World ID is not a content-quality signal by itself. It does not prove that a submitted photo or video satisfies the mission. Katch still applies mission rules, capture requirements, GPS checks when relevant, verification, and curation before a submission becomes an accepted deliverable. Katch should not expose World ID identifiers as creator deliverables. Creators receive accepted evidence, verification metadata, GPS metadata when relevant, and provenance IDs for mission/submission traceability.

​
Location and GPS

GPS can be core evidence for place missions. Creators may receive submitted GPS metadata for accepted deliverables when it is part of the mission evidence. Use GPS constraints only when the place is essential to the mission. Do not use location requirements to infer private addresses or track people.

​
Public-context capture

Missions should prefer public objects, products, signage, venues, shelves, menus, events, and task context. Avoid rules that require focusing on private people, private screens, or sensitive documents.