Virohana
Trust & data

What we hold — and what we never do.

Sovereignty is a claim, and a claim you can't check is marketing. This page states plainly where things run, what we refuse to hold, and how we handle the parts that could hurt you if we got them wrong.

Data locality

Local first, EU second, nowhere third.

Your systems run on your machines

The systems we build for you are local-first by design: they execute on your hardware, against your credentials, with your data staying where it already lives. That is the default, not an upgrade.

Our company is Estonian

Virohana is operated from Tallinn, Estonia. What little we hold on our own side — enquiries, bookings, invoices — sits within the EU.

Nothing leaves unless you send it

No silent uploads, no background sync of your working data to us. Where a build calls an external model, that call is a deliberate, visible part of the design you signed off on.

The scorecard proves the point

Our own free scorecard runs entirely in your browser and sends us nothing. It would have been easier to collect the answers. We didn't.

What we never hold

Three things that stay yours.

01

Your keys

Credentials for your bank, your government portals, your tools — you hold them. Systems we build run under your keys, on your side. We do not keep copies.

Never
02

Your money

We are not a payment intermediary. We never hold, move, or have authority over your funds. Nothing we build initiates a payment without a human approving it.

Never
03

Your books

Accounting work runs against your own account in the official system. Your ledgers are not copied into a Virohana cloud, because there is no Virohana cloud in that loop.

Never
Security posture

How the dangerous parts are handled.

Secrets are encrypted at rest

Credentials and tokens used by the systems we operate are stored encrypted, never in plaintext config, and never in a repository.

Irreversible actions are human-gated

Anything that files, pays, sends, or deletes waits for a person. The machine proposes; you dispose. This is a structural rule in every build, not a setting someone can turn off in a hurry.

Actions are logged

What the system did, when, and on whose approval is written to an audit log you can read. If you can't reconstruct why something happened, it isn't finished.

Deterministic where mistakes are expensive

Numbers that matter are computed by code, not generated by a model. The same inputs always produce the same output, and it can be tested.

Company

Who you are contracting with.

A real Estonian company with a name, a register number, and a founder you can look up. Sovereign, humanity-first AI is what we sell; being findable and accountable is the least of what that implies.