Security

It cannot move your money

The credentials you give Pruvyo are read only, and the product has no code path that instructs a payment. What leaves this system is a verdict; your provider is the one that acts on it or does not.

That is a design decision rather than a policy: there is nothing to misconfigure, and a stolen Pruvyo session cannot make a payment because Pruvyo cannot make payments.

Nobody signs alone

Who may propose, who may approve and who may sign off is enforced in the database, not in the interface. An account with the wrong standing is refused by the row it is trying to write, so the second signature cannot be skipped by a clever request.

Where the data lives

In the European Union: the database and its storage are hosted in Ireland, the application runs in Dublin. Data is encrypted in transit and at rest, and provider credentials are encrypted before they are stored.

Addresses we are asked to call

Any address you register, whether a callback for decisions or a provider endpoint, is checked against private and internal ranges when it is saved and again every time it is used. An address that was public on the day it was saved and points inside a network today is refused today.

Documents

Verification results flow on a schedule. The files behind them do not: a document crosses from your KYC provider into Pruvyo when an analyst chooses it for a case, so this is not a second vault of everybody's passports.

Every uploaded file is checked before it is stored, and what is checked is the content rather than the name it arrived with.

What the assurances mean today

GDPR: compliant. SOC 2 and ISO 27001: aligned, meaning the controls are built and the audit has not been done. We say aligned rather than certified because the difference is the entire point of an audit, and a buyer who finds out later is right to be angry.

Reporting something

If you believe you have found a vulnerability, write to us before you write about it anywhere else, and you will get a person rather than a form.