Security
Seven mechanisms rather than seven adjectives. Each one is something you can ask us to demonstrate.
Tenant separation is enforced by PostgreSQL row-level security with restrictive policies, so a query that forgets to filter by tenant returns nothing rather than somebody else’s stock. It is not a convention the application is trusted to follow.
Not optional and not a setting an owner can switch off for convenience. Sign-in is a code to a registered phone; the counter then unlocks with a PIN for the rest of the shift, so speed at the till does not cost you the second factor.
Branch scope comes from the session token, and assignment is mandatory rather than defaulted. A salesperson at one counter cannot read another branch’s stock or bills.
Who may discount, who may write off, who may see a cost price — checked in the API, not only hidden in the interface. A hidden button is not a permission.
Who did what, and when, including the actions nobody wants to have to ask about. Documents are append-only: a correction raises a credit or debit note rather than rewriting what was handed to a customer.
The desktop app keeps an encrypted local replica so it can trade with the line down. A stolen counter machine is not a copy of your ledger.
No credentials, tokens or environment values in the application code, and financial data, personal data and secrets are kept out of log lines by policy and by review.
No certification badges. Vowerole does not currently hold an external audit or certification, and claiming one it does not have would be the least defensible thing on a security page. When there is one, it will be named here with its scope and its date.
Found something? Write to tech@vowerole.com and it gets read the same day.
Start on the free trial, or book a walkthrough and we will set the first branch up with you.
