Web Civics mark Web Civics Databox

Plain-language introduction

Information should work for people, not the other way around.

Web Civics Databox is a way for a person, family, community group or organisation to keep important information in a place they can understand, and share it only for clear reasons.

Start with the decision guide See how it works

What it is

Think of it as a secure filing cabinet with a clear visitors’ book.

Many services ask people to give up copies of their information. It can then be hard to know where those copies have gone, who can see them, or how to correct a mistake.

A Databox is designed to make the arrangement clearer. It gives each relationship its own place: for example, one place for a library membership, another for a local support service, and another for a community project.

In everyday language

Databox
A protected place for records and messages.
Permission
A clear rule about who may do what, and why.
Record
Something worth keeping: a receipt, notice, form, decision or correction.
Audit trail
A dated record of an important action, so it can be checked later.

How it works

One clear relationship at a time.

The exact steps depend on the service. This picture shows the basic pattern without technical jargon.

  1. 1

    Agree the purpose

    People decide what the service is for and what information it needs.

  2. 2

    Set the boundaries

    The group records who may see, add or change information, and under what conditions.

  3. 3

    Exchange what is needed

    Only the relevant record is shared. A service does not need a person’s whole digital life.

  4. 4

    Review and correct

    Important actions can be checked. A correction is recorded rather than quietly hiding the earlier record.

What this means in practice

A community organisation might send a member a program notice, a receipt or an eligibility decision. The member can see what has arrived, request a correction where appropriate, and choose whether to share relevant information back.

Different settings, same principle

It can support people working alone or together.

For a person or household

Keep personal or shared records in an arrangement the household understands. Any support or guardianship arrangements should be explicit, limited and reviewable.

For a local group

Keep a clear record of memberships, contributions, shared equipment or project decisions without turning a volunteer group into a data broker.

For an organisation

Create a defined channel for a particular service or program, with clear records, responsibilities and a way to handle corrections.

For councils, boards and committees

Start with the public benefit, not the technology.

You do not need to be a technical expert to decide whether this approach is worth exploring. Ask the questions below before approving a pilot or program.

1. What problem are we solving?

Describe the real-world problem in a sentence. For example: “Members cannot easily find their receipts or ask for a correction.”

2. What is the smallest amount of information needed?

Do not collect information merely because it may be useful later. Name each type of information and its purpose.

3. Who is responsible?

Identify the people or roles who may add records, approve access, respond to corrections and deal with a problem.

4. How will people get help?

Plan for a phone number, a face-to-face option, accessible instructions and a process for people who cannot or do not wish to use a smartphone.

5. How will we know it is fair?

Decisions should be explainable. Keep a process for checking errors, challenging decisions and reviewing whether the system is helping.

6. What happens if we stop?

Agree how people will receive their records, how long information is retained, and who is accountable for closing the service safely.

An honest note about safety

Good technology helps, but good governance is still essential.

Designed to support

  • clear reasons for sharing information;
  • separate spaces for separate relationships;
  • records of important actions and corrections;
  • open standards, so one supplier does not own everyone’s data.

It cannot replace

  • consent, privacy and records-management obligations;
  • staff training, accessible support and careful service design;
  • independent oversight and a process for complaints;
  • ordinary security work such as updates, backups and incident response.

A Web Civics Works principle

Good technology should help people be paid fairly for the value they create.

Web Civics Works rejects digital slavery: the extraction of people’s labour, knowledge, creative work, data, computing resources or support work without meaningful consent, recognition and a fair opportunity to agree terms and payment.

That principle includes the people who build, host, maintain and support community technology. Open standards and voluntary sharing can be valuable, but neither makes a person’s time, skill, electricity, equipment or care work free to take.

What fair participation asks for

  • clear, voluntary terms before a person’s work, data or resources are used;
  • credit and a traceable record of meaningful contributions;
  • a fair way to agree compensation, costs or shared benefit where value is created;
  • no hidden dependence on unpaid work, coerced data extraction or one-sided platform rules.

Consent is not meaningful under economic coercion

People and communities may volunteer, donate, share or contribute to a commons, but a choice is not genuinely free when a person faces poverty, loss of housing, loss of income, loss of care, loss of essential services, threats to their safety or no reasonably safe alternative. Protecting people’s economic rights and ability to live with dignity is a demanding, ongoing Web Civics Works objective. It requires work on technology, governance, funding, support and accountability; it is not an easy binary fix. The direction is clear: access to basic needs should never depend on surrendering a person’s work, data, rights or future.

Learn more

Choose the next step that suits you.

The project

Civics.au brings together the wider work: resilient community infrastructure, fair participation, local capability and the practical ideas that the Databox can support.

Visit Civics.au

Discuss a possible use

Use the decision questions above as the agenda for a first conversation with your committee, staff or community.

Read the questions again

Try the demonstration

The demonstration uses made-up information. It is for learning how an organisation might set up a program, not for managing real people’s records.

Open the demonstration

Compare the two engines

Oxigraph and Web Civics Qualia have different purposes, deployment options and licence terms. The comparison explains the choice without assuming technical knowledge.

Compare engines

Read the technical material

Implementation notes, developer guidance and the source code are available for technical teams and independent review.

Open technical documentation