Most of what follows is unglamorous and that is rather the point. Here is what protects your documents, in plain terms, with the parts we have not built called out as clearly as the parts we have.
TLS 1.3 on the wire and AES-256 on disk, with keys held in a managed key service and rotated quarterly. Backups use the same keys and are restored into a test environment every month, because a backup nobody has restored is a guess.
Permissions attach to teams and document types rather than folders, so a bookkeeper sees invoices across every client and nothing else. Single sign-on and enforced two-factor come with Office.
Every action against a document is recorded with the person, the time and the address it came from. The log is append-only, searchable, and exports as CSV.
Pick Canada, the United States, the United Kingdom or Germany at setup. Your documents and their backups stay in that region and are not processed anywhere else.
SOC 2 Type II, renewed annually. Penetration testing twice a year by an outside firm, with the summary report available to customers on request.
The models that classify and read your documents are not trained on your content, and nothing you store is used to improve a shared model.
We will tell you within 24 hours of confirming an incident that touches your data, before we have the full picture and before it is comfortable to do so. You will get what we know, what we do not yet know, and what we are doing about it.
Status and past incidents are public at status.infohive.app, including the ones nobody noticed. A status page that only shows good news is a marketing page.
Worth knowing before you commit, and easier to read here than to discover in month four.
We answer them ourselves, usually within two working days, and we will tell you when the honest answer is no.