Skip to content
Hineni

Trust

Each person sees only what their role needs

In short

Hineni limits what each person can see to the records their role requires, and it enforces those limits in the database. Volunteers see their own records, lay leaders see the people tied to their work, and staff see the organization's records. Hineni stores no criminal history, and sign-in uses an emailed link with no password.

Last reviewed 3 November 2026 by the Hineni team

Who can see what in Hineni?

Each role sees the smallest set of records its work requires. The database enforces these limits, and they apply to viewing, searching, exporting and messaging alike.

  • A volunteer sees their own profile and history, their own household's children, their own clearance status and an export of their own data.
  • A lay leader sees people tied to their work, children only for sessions those children are booked into and a cleared badge with no screening detail. Their exports cover their own lists and are logged.
  • Staff see the organization's records and contact details, children only through bookings and the cleared badge. All staff exports are logged.
  • A screening officer sees clearance cases with the process and evidence of each check, never children's details. Evidence exports are logged.
  • No one sees criminal history in Hineni, because Hineni never stores it.

What does a member agree to before Hineni sends a text?

A member agrees to texts for one stated purpose, from one organization, and can end them with one word. Email is the default channel. Text consent is a separate, unchecked choice, recorded with the date and the wording shown, and consent given to one organization never carries over to another.

Replying STOP, or words such as QUIT, CANCEL or UNSUBSCRIBE, ends texts at once with one confirmation. Hineni sends texts only from a number registered with US carriers under 10-digit long code (10DLC) rules, which require a registered brand and campaign.

How does Hineni keep volunteer data secure?

Hineni's security rests on permissions enforced in the database and a short list of what it keeps. A lay leader's search or export returns only their own records, because the database applies each role's limits. Hineni runs on a managed cloud database, and sign-in uses an emailed link.

Hineni keeps clearance status and dates, and it stores no criminal history and no screening documents. Those records stay with the vendor and the organization's designated screener. Every export is logged, so the organization can see who took which records and when.

Where does artificial intelligence fit in Hineni?

Hineni's role suggestions come from written rules, with no generative AI model involved. The rules read a member's own words and compare them with the organization's list of roles. Each suggestion states its reason, and the member can edit how Hineni read their answer.

The member sees what Hineni understood from their words and can correct it before anything is saved. Each organization controls the list of roles the rules draw on.

Questions about trust and privacy

Sources

  • CTIA, Messaging Principles and Best Practices, May 2023
  • FCC, TCPA consent revocation rule, effective 11 April 2025
  • Twilio, A2P 10DLC onboarding for government and nonprofit agencies, accessed October 2026
  • Hineni Research, Information Architecture and Workflows report, 30 October 2026

Last reviewed 3 November 2026 by the Hineni team.

See Hineni with your own volunteer roles.

We'll walk through Hineni with your roles and your lay leaders, and show you how a first season could run.