Consent FinchResearch permissions / Workspace 01
Permission has
a perimeter.
Define who may use which fields, for what purpose,
and for how long. Then test the boundary.
Purpose ∩ Fields
∩ Recipient ∩ Term
Start empty, or load a clearly marked synthetic example. No participant data is collected.
Field × purpose
Give a fictional dataset
a defined scope.
Create a schema with four predefined fields.
No records, names, or health values are accepted.
Rehearse an access request
Decision awaiting request
Four matches.
No shortcuts.
A single grant must cover the entire request. Two partial permissions cannot be stitched together.
Revoke, without rewriting history
Revocation blocks future checks against that grant. It cannot retrieve copies already downloaded. Other matching grants remain valid.
No grants yet. Your first authorization will appear here.
Audit timeline
Recorded on this device; export timestamps are UTC. This editable local trail is not tamper-proof evidence.
- No events recorded.
A portable permission vocabulary
Shared templates.
The same right to withdraw.
Consent Finch explores an application token for access to purpose templates and shared audit workspaces across research apps. The local sandbox needs no token. Holding one would never override a data subject’s withdrawal.
This prototype is not legal compliance certification or a real medical data exchange network.