Skip to content

Security controls for accounts and records

This page describes some of the controls built into Supplier Share. It does not describe a certification or an independent audit, and it is not a guarantee of security.

Signing in

  • You sign in with your email and a password.
  • Passwords are stored as hashes, not as the password itself.
  • Once an account has an authenticator enrolled, sign-in asks for a code from it.
  • Authenticator secrets are stored encrypted.
  • Platform administrators sign in with an authenticator code as well.
  • On the live service, a new account is asked to set up an authenticator at first sign-in.
  • When you set up an authenticator, you receive recovery codes.
  • Repeated failed sign-in attempts are rate limited.

Records

  • Sensitive actions write an audit row: approval, a year marked paid, invitation, share, acceptance, removal, export and admin changes.
  • Audit rows are append-only: the application can add them but cannot edit or delete them. The only change allowed is after seven years, when the description and any names or email addresses in a row are removed (see the Privacy Policy).
  • Exports are recorded in the audit trail.
  • Each result is a fixed version. A correction creates a new version.

What organisations can see of each other

  • An organisation you buy from keeps its other customers hidden from you. You see what it chooses to share with you, and any further tiers you open with your own available seats.
  • Suppliers choose the result version and allocation percentage to share with a buyer that invited them.

In transit

  • Connections between your browser and Supplier Share use HTTPS.

Hosting

  • The Supplier Share app that you sign in to, and its database, are hosted in Australia.

Reporting a security issue