Built for regulated work. Here is what is in place today.

• Your firm's data stays your firm'sIn place

  Every request is scoped to the firm the signed-in person belongs to, and automated tests check that one firm cannot open another firm's documents or admin pages. A firm can also run in its own dedicated environment, with its own database and file storage.

• A person approves before anything consequential happensIn place

  Actions that change a register, file with a registry, or send material outside the firm wait as proposals until someone at the firm approves them. Who approved, and when, is recorded. For register entries and screening, the person who proposed the action cannot approve it.

• A tamper-evident audit logIn place

  Consequential actions are written to a log kept for each firm, where every entry is chained to the one before it. Entries are never edited in normal operation, and the chain can be checked, so a change made after the fact shows.

• Permissions inside the firmIn place

  Administrators, staff and clients have different permissions. A document can be kept private to its owner, and people using the client portal see only what the firm shares with them.

• Sign-inIn place

  Sign-in is handled by a dedicated identity provider, and the server verifies a signed token on every request.

• Connected-service credentialsIn place

  Credentials for services a firm connects — calendars, registries, payments — are encrypted before they are stored.

• Data residencyIn progress

  Pinning each firm's database and files to a chosen region is being set up. The data residency page has the current details.

Prospective customers can request the full security documentation under NDA at [email protected].