Civesto is a Touman Studio product.

etkaahmet@toumanstudio.comTürkçe

ContentsDiscuss a pilot

A case file your officers can review.

Civesto receives citizen traffic reports and organises the evidence for each case. The authority decides whether an offence has occurred.

Civesto is technically ready and open for pilots. It is not yet in live operation at any public authority, and no pilot has been completed.

Discuss a pilotOpen the authority console (read-only)

Reference CV-FC-0184

Validated

Handheld phone use while driving

Conduct offence · no machine assessment

Evidence seal · SHA-256

c48a7f2d91b6…

capture.jpg · 842 KB · sealed 2026-11-02 10:14:08 UTC

  • Camera recorded as Aster C7
  • Lens and exposure metadata present
  • Content Credentials present (not validated here)

Why these findings?

Machine inspection reports observations, not conclusions — the assessment is yours.

Routing

Held for manual assignment

Your decision

  • New
  • Validated
  • Forwarded
  • Acted
  • Closed

Officer note

Labels as they appear in the authority console; the values are fictional

The system does not assess the driving itself. The authority decides whether an offence has occurred.

A matching digest checks the file bytes. It does not prove that an event occurred.

An officer — not AI — reads the plate and decides.

From a report to a decision

Citizen

System

Officer

Authority

  1. Receive the reportCitizen
  2. Keep the file bytes verifiableSystem
  3. Review the evidenceSystem
  4. Route the reportSystem
  5. Record the decisionOfficer
  6. Take the case into your workflowAuthority
StepWho actsWhat happens
Receive the reportCitizen

The citizen submits a recording, a report type and a location through the Civesto app.

Keep the file bytes verifiableSystem

The upload handler computes a SHA-256 digest from the received file bytes before analysis.

A matching digest checks the file bytes. It does not prove that an event occurred.

Review the evidenceSystem

The system checks file metadata and records the results with the case.

Route the reportSystem

Traffic reports and road hazards reach the responsible team’s queue.

Record the decisionOfficer

An officer validates, forwards, acts on or closes the report. The legal basis and the officer’s note stay with the case.

The system does not assess the driving itself. The authority decides whether an offence has occurred.

Take the case into your workflowAuthority

Cases can be exported as DATEX II, GeoJSON, CSV, XLSX or PDF. The system provides a documented REST API and webhooks.

DATEX II export is for road reports and is a generic v3.5 test publication. National profiles and real publication are not enabled.

A report takes about a minute. All you need: one photo.

The citizen sends photos or a video, chooses what they saw from a list and can add a note.

The app adds the time and, when the citizen allows location sharing, the location.

The most common types are one tap away; the rest are in a searchable, grouped list.

Before sending, the app tells the citizen if similar reports were made nearby in the last 30 days. The citizen can still send.

With no connection, the report waits on the device and is sent when the connection returns.

The citizen follows the report through four steps: Submitted, Pre-check, Officer review, Outcome.

An officer will review your report. Not every report leads to action; that's a normal part of the process.

The app comes in two builds: one for traffic offences and one for road hazards.

First, photograph what you saw

A photo or video is enough

  • Take with Camera
  • Choose from Gallery
  • Record Video

It's fine if you don't know — the photo is enough

You can change anything before sending

Labels as they appear in the app; the values are fictional

What the system measures

The system reads what a file says about itself, such as capture time, camera, encoding traces and any Content Credentials marker, and records each as an observation. An officer decides what the observations mean.

An observation is not a finding against the person who submitted the file, and it carries no score.

These are header observations, not image decoding or authenticity validation. A missing marker or metadata is not evidence of manipulation.

For road reports, visibility, illumination and surface are measured from the image, each with a confidence level. The measurement supports the report; it does not replace confirmation on site.

Road conditions · measured

Road condition (measured)Confidence

… image is consistent with reduced visibility. Officer confirmation required before this is treated as a road condition.

  • heavy rain or road spray can produce a comparable profile
medium

Low-light capture — night or unlit section

  • underexposure by the camera is indistinguishable from an unlit road here
high

Specular pattern on the carriageway consistent with a wet or contaminated surface

  • night-time reflections of street or vehicle lighting
  • fresh asphalt and painted markings reflect similarly
  • a spilled fluid cannot be distinguished from rainwater by image alone
low

The measurement supports the report; it does not replace confirmation on site.

Physical measurements only. This module does not determine whether a condition exists; it reports what the image is consistent with and what it cannot exclude.

Labels as they appear in the authority console; the values are fictional

Route the report

Each report type maps to the responsible roles with a proposed urgency, and the reason is stored with the report. A type with no rule is shown as held for manual assignment.

Routing proposes recipients and urgency. It does not task a crew.

A queued routing entry does not prove delivery or a person's acknowledgement.

See where reports cluster

A location is listed once the same condition is reported twice within about 150 metres and 30 days.

The hotspot view groups reported locations into cells and lists the busiest cells alongside the map.

What Civesto never does

Check file integrity

Each file is digested as it arrives, before any processing. The stored file is not re-encoded, so the digest stands for the original.

A file is accepted for what it is, not for its name: the type is read from the opening bytes of the file, and a file that fails the check is not stored.

Reports that carry media are signed and linked to the previous record in a hash chain; if the seal cannot be written, the report is still recorded and the failure is logged. The time in the record is the server's clock.

A report from before the seal was introduced says so, instead of showing an upload-time digest.

SHA-256 of this file

91448bdd92be3e61135d21e31b18d9df488f49740a1d13562bc7546f3ebef2f5
Illustration; no real case is shown.

A matching digest checks the file bytes. It does not prove that an event occurred.

Check the file yourself

This separate test file was prepared to check file integrity. It was not submitted to the live service.

Files up to 10 MB (10,000,000 bytes). The file stays in this tab; nothing is uploaded.

Only an in-memory copy changes. Your original file is untouched.

Metadata is read only from JPEG headers, identified by their bytes, not the filename. Other files are hashed only.

HEIC metadata is not read by this tool. The SHA-256 digest covers the file bytes.

Download the test file

shasum -a 256 integrity-test.txt
7c150c8f4f1d138cd313e8ca47609a4faf864a8c6459019a98cc5d7ef78e63a1

Declared AI-generated

The file states in its own Content Credentials that a generative model produced it

Labels as they appear in the authority console; the values are fictional

If a file states in its own Content Credentials that a generative model produced it, the case shows that statement.

An observation is not a finding against the person who submitted the file, and it carries no score.

Reference CV-FC-0184

Validated

Handheld phone use while driving

Conduct offence · no machine assessment

Evidence seal · SHA-256

c48a7f2d91b6…

capture.jpg · 842 KB · sealed 2026-11-02 10:14:08 UTC

  • Camera recorded as Aster C7
  • Lens and exposure metadata present
  • Content Credentials present (not validated here)

Why these findings?

Machine inspection reports observations, not conclusions — the assessment is yours.

Routing

Held for manual assignment

Your decision

  • New
  • Validated
  • Forwarded
  • Acted
  • Closed

Officer note

Labels as they appear in the authority console; the values are fictional

The system does not assess the driving itself. The authority decides whether an offence has occurred.

A matching digest checks the file bytes. It does not prove that an event occurred.

This console is read-only. Decision controls are disabled. Open the authority console (read-only)

Keep the decision with the officer

Open the evidence with the report

The case brings the submitted recording together with the results of its metadata checks. The reviewing officer makes the assessment.

Review and record

An officer can validate, forward, act on or close a report. The legal basis and the officer’s note are recorded with the case.

A case moves through recorded states: New, Under review, Validated, Forwarded, Acted, Closed.

The decision form records a legal basis and an officer note with the outcome. Changing an outcome needs a key with the case_write scope.

Follow the work in the audit log

The audit log records views, changes and exports with the user, time and stated justification.

Access follows roles: the case officer sees cases and evidence, the management view sees aggregates only, and the IT view sees the audit log, webhooks and keys but no case content.

A case file can be printed with a signature block for the reviewing officer, the date and the outcome or file number.

Connect to your existing systems

Civesto provides a documented REST API, webhooks and exports in DATEX II, GeoJSON, CSV, XLSX and PDF.

Cases can be exported as DATEX II, GeoJSON, CSV, XLSX or PDF. The system provides a documented REST API and webhooks.
Export and delivery
CSV
Excel workbook
PDF
DATEX II v3.5
GeoJSON

DATEX II export is for road reports and is a generic v3.5 test publication. National profiles and real publication are not enabled.

For road reports, a Common Alerting Protocol 1.2 envelope of the routing decision can be downloaded on request. It is an interoperable format.

Read the interface

The API takes one header, an API key that carries the scopes it needs and nothing more. A key can never create another key with more than it holds.

A key sees only the reports of its authority's area. An id outside it answers as not found.

Evidence media is served only through the key, never by file name.

The authority can read its own audit log through the API: time, action, result, origin address and duration for every call made with its keys.

Documented webhook delivery

The API reference describes event deliveries signed with HMAC-SHA256. The receiving system recomputes the signature from the raw request body and compares it with the delivery header.

Webhooks announce new reports and recorded outcomes. Failed deliveries are retried on a lengthening schedule and every attempt is in a delivery log.

This checks a webhook delivery. It does not establish that a reported event occurred.

The receiving case-management system stays the system of record; Civesto pushes events to it.

Run it where your authority needs it

Civesto can run on an authority’s infrastructure or on servers hosted by Touman Studio. For hosted deployments, the hosting country is stated in the contract.

Data protection

Operational, governance and IT users have separate permissions. Several teams can work within one jurisdiction.

A key sees only the reports of its authority's area. Evidence media is served only through the key.

Plates are returned partly masked. Masking is not anonymisation, and uploaded media can still contain identifying details.

Deployment and data protection
  • Authority infrastructure

    The system runs on the authority’s own infrastructure.

  • Touman Studio servers

    The hosting country is stated in the contract.

Define one pilot around your workflow.

Start with a narrow scope and a measurable outcome. Review the read-only authority console and technical documentation before deciding how to proceed.

Discussion framework for a proposed pilot. No pilot has been completed.

A pilot starts with three decisions

  1. Scope

    Which reports, jurisdiction and responsible teams should the pilot cover?

    Identify the reviewing team, its workflow and the receiving systems.

  2. Installation

    Where should the server run, and which modules and connections are needed?

    Two deployment options, defined for the pilot.

    Before defining a pilot, confirm the workflow, the deployment location and which modules the authority needs. Agree a narrow scope and a measurable outcome.

  3. Assessment

    Choose the questions the pilot must answer and the evidence needed to assess the result.

    Discuss which reports enter the workflow, which formats the receiving system expects and what the pilot will measure.

    Use the read-only authority console and API reference to identify the report types and outputs the authority wants to review.

Read the interface

Questions authorities ask

Does Civesto decide whether an offence has occurred?

The system does not assess the driving itself. The authority decides whether an offence has occurred.

What does the SHA-256 digest show?

The upload handler computes a SHA-256 digest from the received file bytes before analysis. A matching digest checks the file bytes. It does not prove that an event occurred.

Does an AI judge the reports?

The system measures and records. It reads what a file says about itself and, on road reports, measures visibility, illumination and surface, each with a confidence level. The system does not assess the driving itself. The authority decides whether an offence has occurred.

Where can Civesto run?

Civesto can run on an authority’s infrastructure or on servers hosted by Touman Studio. For hosted deployments, the hosting country is stated in the contract.

Which formats can cases be exported in?

Cases can be exported as DATEX II, GeoJSON, CSV, XLSX or PDF. The system provides a documented REST API and webhooks. The authority console's Export menu names CSV, Excel workbook, PDF, DATEX II v3.5 and GeoJSON. DATEX II export is for road reports and is a generic v3.5 test publication. National profiles and real publication are not enabled.

Is Civesto in live operation at an authority?

Civesto is technically ready and open for pilots. It is not yet in live operation at any public authority, and no pilot has been completed.

What happens if a citizen has no connection when reporting?

With no connection, the report waits on the device and is sent when the connection returns.

Can I check a file myself?

Files up to 10 MB (10,000,000 bytes). The file stays in this tab; nothing is uploaded. These are header observations, not image decoding or authenticity validation. A missing marker or metadata is not evidence of manipulation.

How does a pilot start?

Start with a narrow scope and a measurable outcome. Review the read-only authority console and technical documentation before deciding how to proceed.

Can I look at the authority console?

This console is read-only. Decision controls are disabled. Open the authority console (read-only).

Discuss your authority’s workflow.

etkaahmet@toumanstudio.comDiscuss a pilot