Skip to main content

Trust built in

Communities lend their language, voice, and time. What they get back — or don't — decides whether they contribute twice. AfriAnnotate treats the trust layer as product, enforced in the API rather than promised in a PDF:

  • Consent at every boundary. Project consent templates with granular purposes, signed before annotating and enforced server-side; explicit consent to create any cloud account; explicit, receipted consent to link a device-only account; separate, versioned, revocable consent for speaker demographics; opt-in-only leaderboards. Exportable consent records (PDF/CSV).
  • Data licensing on the project itself — declare what the collected dataset will be released under, visible to contributors before they contribute.
  • Roles that mean something. Owner / admin / manager / reviewer / annotator (org roles), plus contributor and facilitator designations at project level — each with deliberately scoped powers, documented per page.
  • An audit trail. Signups, consents, links, appointments, rate-card changes, security events — recorded and reviewable.
  • Security policy you control — session timeouts, verification flows, quotas and auto-suspension for abuse containment.

This section collects every page that answers "who agreed to what, who can do what, and how would we know."