Trust and credit
How accreditation works
Accreditation shows what a contributor is trusted to do; it does not make every upload authoritative.
These docs explain the product in plain language. Binding contributor, privacy, payment and other legal terms control if there is a conflict.
Trust is specific
Betabace does not use one universal expert badge. Trust is attached to a capability and can also be local to an area.
- Verified scanner: repeatedly submits technically usable captures.
- Trusted mapper: can publish routine factual edits with less review.
- Local steward: understands the access and history of a defined area.
- Verified beta creator: consistently provides original, clearly labelled beta.
- Creator partner: has completed the identity and payment checks required for payouts.
How trust is earned
Accreditation is earned through accepted work, reliable review and good conduct. Popularity alone is not evidence of accuracy.
New contributors can always submit useful work. Accreditation reduces review friction; it is not a gate that keeps newcomers out.
How trust can change
A capability may be limited or removed after repeated low-quality submissions, copied material, manipulation or abuse. Removing trust changes publishing privileges, not the honest historical record of earlier contributions.