Security
Your numbers are the record of your business. We guard them like it.
Viacle holds your invoices, bills, ledger and the instructions that move money. So security here is not a badge on a page — it is who is allowed to do what, what gets recorded when they do it, and how fast anyone can see when something doesn't fit.
The controls behind every record.
Six things have to be true before a number in Viacle can be trusted. Here is how each one is enforced.
Encrypted in transit and at rest
Data is encrypted as it moves between your browser and Viacle, and again while it sits in our storage. Records are never written to disk in the clear.
Role-based permissions
People see and do only what their role allows. Creating a bill, approving a payment and posting an entry can each sit with a different person.
Verified before money moves
Beneficiary and counterparty details are checked before a payment is released, so the money leaves with the right destination attached.
A complete audit trail
Every entry carries who made it, when, and against what evidence. Corrections are new entries, not overwrites — the history stays intact.
Least-privilege access inside Viacle
Our own staff reach customer data only when a specific job requires it, and that access is logged and reviewed rather than assumed.
Funds held by regulated partners
Viacle is software, not a bank. Customer funds and cross-border movement sit with licensed banking and payment providers under their own supervision.
Your side of the account.
Most losses in finance are not breaches. They are a payment approved by someone who shouldn't have been able to, or bank details changed by a person with too much access. These five habits close most of that gap.
- Give each person only the access their job needs — and remove it the day they no longer need it.
- Separate the person who approves a payment from the person who can change bank details.
- Use a unique password for Viacle, and turn on every account protection available to you.
- Review who can approve what once a quarter, and after every change in the team.
- Tell us immediately if something looks wrong — early notice limits the damage.
Found a weakness? Tell us.
Send it to security@viacle.io. We acknowledge reports within one business day, and we would rather hear it from you than find out the hard way. Please test without accessing, changing or deleting anyone else's data, and give us time to fix it before you publish.
Already a customer and something is wrong right now? Use the in-app report or hello@viacle.io.
See it in a walkthrough