Transparency and privacy

Two different things

Verifiable records and public personal data are not the same thing. The intent is that outcomes can be checked by the people entitled to check them, meaning participants, the organization and auditors, without publishing anyone's personal information.

Who can check what

• Participants see their own terms, schedules and recorded activity.
• The organization sees the participant records it administers, under its policies.
• Auditors and authorized reviewers can check recorded outcomes against the rules within a defined scope.
• The public sees this explanatory documentation, never member records. Final operating rules are not published yet.

Role-based access is the intended baseline mechanism. Cryptographic selective disclosure is a research direction rather than a deployed capability. Where a claim about verification depends on technology that is not live, it will be labelled as planned.

Selective disclosure can mean sharing chosen information; a zero-knowledge proof can instead establish a condition without revealing its underlying data. Neither alone supplies informed consent, fair rules or trustworthy source records. Midnight and selective disclosure explains this distinction, the fourth-generation framing and potential community-finance uses. Kapitala is not integrated with Midnight.

Records retain their sources

Records are intended to keep their provenance: what changed, when, and under which rule version, including recorded corrections. Tamper evidence is a direction being studied, not a guarantee against every form of modification. See Rules and implementation status for the boundary between technical testing and an operating program.

What is deliberately absent from this site

Member records, internal operations, member data and correspondence are not published here. No registration or member data is used to build this documentation or its examples; interface previews use fictional example data.

Current state

The verification flows above describe intended behaviour. What exists today is a rule engine and record store used for testing. Data-protection obligations for any future program will be defined by its operating entity and reviewed with qualified advisers before member data is processed at all.