Properties of the system, stated plainly.

Clear plates live on two records, and nowhere else.

A number plate is stored in clear text only on the vehicle record and on a visitor permit. Everywhere else (logs, events, camera matches) the system carries one-way tokens instead.

Clear plates are displayed only to roles with the permission to see them, with one narrow exception: the person who entered a visitor's plate can read back what they typed. Everyone else sees a mask. The permission is granted per role, not a display setting.

Boundaries are structural, not cosmetic.

Each tenant company sees only its own people, vehicles, and bookings. Isolation is enforced in the database layer with row-level security, not filtered in the application.

Rows belonging to other tenants do not exist in a tenant's view. No query a tenant can run returns them.

History cannot be silently rewritten.

Every administrative decision lands in an append-only audit log. Each entry carries the hash of the entry before it, so any alteration breaks the chain.

Every booking keeps which checks passed and a fingerprint of the policies that applied, so a decision can be traced back to the rules that made it.

Any selection of the log, up to 100,000 rows, exports as a signed package with a stand-alone verifier inside it, so a reviewer can check the signature and the chain offline against the verification key Vadoris publishes.

prev 8c41f2…b7d0 · sha256 d90a1c…44e7

A human makes the call.

Two paths bring a violation into review. ANPR cameras at the gates match arrivals against bookings and flag exceptions: an overstaying vehicle, a booking never used, a plate with no booking at all.

And a tenant admin can report what cameras cannot see: a vehicle parked in a stall allocated to someone else. Vadoris identifies the vehicle and routes the case to the right admin: the tenant's own admin when it turns out to be a colleague, the property admin when it crosses tenant boundaries. The reporter learns only "resolved" or "not found", never which company matched.

Either way, a flag carries its evidence to a human reviewer. The system does not fine anyone automatically.

Data subject requests are a product surface.

Privacy requests are built into the product: staff record a person’s request to see, correct, erase or restrict their data and work it to an answer there, not in an inbox. Each tenant company is the controller for its own people.

Vadoris is an EU product, built for the Romanian market first.

Nothing here is decoration.

No customer logos, no uptime figures, no certification marks. We state what the system does and stop there.

If your review needs evidence beyond what is written here, ask for it in the demo.