Security & Trust

• Email and password authentication only. No social or consumer sign-in is offered, and anonymous sign-up is disabled.
• Registrars self-enrol solely from a verified official government email address held on an allowlist; the address must be confirmed before any role is granted.
• Judges, clerks, counsel, parties and witnesses are provisioned by the registrar. There is no self-registration for these roles.
• Every sitting invitation is issued to a named individual, bound to that person's account and email address, and requires sign-in before admission. Links are revocable and not transferable.
• Compromised-password screening is applied at sign-up and password change.

Each licensed court is a separate tenant. Row-level security in the database scopes every read and write to the acting user's court, so no query can reach another court's cases, participants or records — the isolation is enforced in the data layer, not only in the interface.

• Proceedings are append-only: update and delete privileges are revoked, so an entry once made cannot be edited or removed.
• Certification seals a sitting's transcript and stamps it with a SHA-256 fingerprint, so any later alteration is detectable.
• Certification is restricted to the court's own officers, and a sealed record cannot be re-opened.
• Every record carries its appearances, appellations, sequence numbers and timestamps.

The application runs on managed edge infrastructure with a managed PostgreSQL database. Data is encrypted in transit with TLS and at rest by the hosting provider. Secrets are held in a managed secret store and are never present in application code or in the browser. Privileged database credentials are not accessible to court users.

Order in the virtual courtroom is administered by the clerk under the presiding judge: floor control, permission to address the court, hand-raising for leave to speak, and removal of a participant from the sitting. Removal is recorded in the written record.

• The platform operator secures the software, infrastructure, isolation model and record integrity.
• The court controls who is enrolled, which roles are granted, which participants are invited to each sitting, and its own retention schedule.
• Court users are responsible for keeping their credentials confidential and for not forwarding invitations.

Suspected vulnerabilities should be reported to the court's administrator for escalation to the platform operator. Reports made in good faith are welcomed and are not pursued; please do not access, alter or exfiltrate real case data while testing. Acknowledgement is given within two working days.

This is an app-owned statement of current practice. It is not an independent certification, penetration-test report or audit opinion, and it does not assert compliance with any certification scheme. Formal assurance documentation, where a court requires it, is agreed in the licence.