Civic Ledger service terms

Accountable participation

You must use your own authenticated identity, provide accurate civic context, and exercise only roles explicitly assigned through a case, space, organisation, or city record. A preferred profile role never grants operational authority. Profile modes, contribution history, invitations, and any recognition signal do not create authority or a universal social score. Authority is explicitly assigned for a particular case, space, organisation, place, role, and time; it may expire or be withdrawn with a recorded reason.

Civic records are not permits

An agreement records what participants accepted and how they reasoned. It does not replace permits, insurance, safeguarding duties, employment obligations, property rights, emergency directions, or applicable law. Participants remain responsible for obtaining external authority. Proposal review combines space context and proposed activity into a transparent 0–100 routing score: low (0–40), moderate (41–70), or high (71–100). A rule conflict or material safety concern can still require conditions or human review. AI may identify additional risk but cannot lower the deterministic score or approve a proposal.

Evidence and personal data

Upload only evidence you are authorised to share with case participants. Mark files that contain identifiable personal data, avoid unnecessary sensitive information, and do not upload malware, unlawful material, credentials, or content intended to harass or identify vulnerable people.

Fair process

Do not impersonate participants, manufacture endorsements, evade independence rules, conceal material incidents, manipulate consultation through duplicate identities, or use Civic Ledger to discriminate or retaliate. Automated rate limits and recorded security events protect the ledger. AI supports risk review and high-risk deliberation, but people remain responsible for conditions, endorsements, agreements, evidence decisions, mediation, and appeals. Personal, sensitive civic, non-public authority, payment, credential, and raw security data are not sold or published. Public learning uses non-identifying, thresholded aggregates.

Rule evolution

Verified-space rules change only through governed proposals. Evidence snapshots, consultation responses, objections, amendment requests, authority, and final reasoning are preserved. City templates do not automatically overwrite local space rules.

Suspension and erasure

Civic Ledger may reject writes that lack current consent, exceed safety limits, or come from a restricted account. Erasure cannot silently abandon active civic duties; accountable handoff is required before final anonymisation. Before an activity starts, its proposer or appointed space steward may cancel with a recorded material reason; pending work closes and reserved space time is released. Once the activity starts, use pause, incident, mediation, or accountable completion workflows instead. Civic Ledger does not collect, hold, refund, or settle money. Any external fee, deposit, tax, insurance, refund, or payment arrangement must be an explicit case condition handled by the responsible parties outside Civic Ledger.

Availability and change

The service may evolve as governance, security, and legal requirements change. Material terms or privacy changes require a new version and renewed core consent before further writes. A Civic Ledger access pass proves that a participant’s browser code matched an active agreed reservation at verification time. It does not operate a physical lock, guarantee admission, or override the space authority’s safety duties. Civic Ledger does not continuously track location or collect GPS, Wi-Fi, or nearby-device identifiers. Place information is limited to locations and map coordinates deliberately supplied for spaces, proposals, or evidence. Do not use access passes, records, or identity checks to rank people beyond the specific civic purpose for which they were issued.

Review the privacy notice for data-specific controls.