Built to Protect
the Evidence.

Built Your data lives on private servers we own and operate in Australia — not rented space in a global cloud, and not replicated offshore. Every node in our fleet is on Australian soil, Australian-owned and operated.

No provider can promise immunity from legal process, and we won't pretend otherwise. What we can do — and have — is remove the pathways foreign orders usually travel: there is no overseas cloud provider in the chain to be served a sealed order, and no foreign parent company to compel. In practice, any lawful demand runs through an Australian court under Australian law — a process you would ordinarily have notice of and standing to contest, rather than a warrant served on a foreign host you never hear about.

One honest exception: our phone apps are distributed through the Google and Apple stores, which handle app download/transaction data under their own terms. Your legal content — the vault and your mail — never touches them.

Built Data is encrypted in transit (TLS) across an encrypted site-to-site VPN mesh between our locations. Full-disk encryption at rest is deployed on newer nodes and being rolled out across the fleet Roadmap — we'd rather tell you it's in progress than claim it everywhere before it's true. Messaging uses end-to-end encryption — elliptic-curve key exchange (ECDH) with AES-256-GCM. What's distinctive is how change is controlled: our cipher configuration is governance-signed using threshold (multi-signature) cryptography — like a two-signatory trust account, no single administrator, including us, can unilaterally weaken the encryption; a change needs multiple independent signatures before any server will run it.

Engineer support access is authenticated and written to an append-only, hash-chained audit log (tamper-evident — any alteration is detectable) — every access is provable after the fact, a stronger guarantee than a certificate attesting a process exists. Roadmap Customer-held keys (bring-your-own-key / BYOK) and richer key custody are in development.

Built Every item in the vault carries a data classification (a privilege marking) — the same principle as a security classification on a defence document, enforced by the system rather than by habit. Disclosure runs under mandatory access control: privileged material cannot be exported or released without passing a gate and writing an audit record of who released what, when and how. Outbound mail passes an opposing-counsel / privilege (DLP) check before it leaves.

On top of that, our practitioner-intelligence layer cross-references the people in your matters and address books against the public legal registers — flagging restricted, struck-off or conflicted practitioners so you don't unknowingly correspond with, or disclose to, the wrong party. Roadmap Parts of the automated conflict-clearance workflow are still being wired in; we'll mark them Built when proven.

Built Yes — we run a Security Operations Centre at our Australian headquarters: security monitoring (SIEM) ingesting logs from every server, firewall and mail gateway across the fleet, with automated rules that flag anomalies such as bulk downloads and unusual logins.

We're honest about the shape of it: detection is 24/7 and automated; response is by the named engineers who built and run your system — not an outsourced night-shift analyst seeing your firm's name for the first time. Alerts reach that team directly, so triage starts with full context. Automated containment (blocklisting, tripwires, isolation of a service or network segment) acts in the meantime. Roadmap Formal on-call hardening and a self-healing watchdog on the monitor itself are in progress.

No — and we want to tell you why before you ask. Those frameworks audit a cloud vendor's internal processes over a period; they were built for the multi-tenant cloud model we deliberately reject. Our model gives you something a certificate can't: you can inspect the actual controls — the audit chain is verifiable, the monitoring console can be shown to your adviser, the servers are physically in Australia and identifiable.

We chose controls you can verify over certificates you have to trust. For insurance and compliance, we provide a controls-mapping document against the recognised Australian control families (ASD Essential Eight, ISO 27001 control areas, APRA CPS 234 principles) so your adviser can do a like-for-like assessment — covering two-factor authentication on vault access, log retention (see our data-retention page), patching, backups and segmentation. If a firm's insurer requires the certificate itself, tell us and we'll discuss it — we will never imply certification is underway when it isn't.

Built Our penetration testing is authorised, scheduled and run from known infrastructure, with written scope agreed before every engagement. Your team can tell it apart because an engagement is pre-notified to a named contact with a defined window and source details, and the test traffic is attributable after the fact. Anything that does not match a registered engagement is treated as a real attack — no benefit of the doubt.

Methodology is refreshed against current threat activity, including new ransomware behaviour, on an ongoing basis. We won't claim a continuous commercial threat-intelligence feed we don't run.

Built Email is the riskiest vector, so we treat it as untrusted. In front of the mail server sits a secure email gateway (SEG): inbound sender authentication — SPF, DKIM and DMARC (so spoofed and forged mail is caught), spam quarantine, honeypot decoy addresses that trip crawlers on first contact, and IP blocklists at the edge. Delivery is encrypted in transit with TLS (opportunistic STARTTLS, and MTA-STS where the far side supports it). Outbound, a data-loss-prevention (DLP) privilege guard checks mail before it leaves. Internal mail rides an isolated, network-segmented path. Roadmap Enforced (not just opportunistic) transport encryption is being tightened further.