Security

Separation between businesses

Every record in the system carries the id of the business it belongs to, and every query the software makes is bound to the account that is signed in. It is enforced at the database level rather than by a screen that hides things — there is no path through the product where one business's query can reach another's row.

Passwords

Stored hashed with bcrypt. Nobody can read yours, including us. Sign-in attempts are rate-limited per address, and the platform's own admin login harder still.

In transit

Everything travels over an encrypted connection. The panel, the API the mobile apps talk to, and your store front.

Who on our side can see your data

A small number of staff, when you ask for support or when we are investigating a fault. When one of us signs into your account, it is recorded in your account's own history, where you can see it. Support access should not be invisible to the customer it happens to.

Backups

Taken regularly and encrypted. They exist so that a hardware failure is our problem rather than yours.

Permissions inside your own account

You decide what each of your staff can open, section by section and down to individual actions. A rider sees their round and not your books. A login you deactivate stops working immediately.

Reporting a problem

If you think you have found a security flaw, write to us before telling anybody else. We will confirm we have received it within one working day, keep you informed while we fix it, and credit you if you would like us to.