Loading
Loading
Bob handles sensitive customer and health data. We protect it by construction: each firm isolated at the database, sensitive PII kept in region and failing closed, PII redacted before any log, and every decision on an append-only trail. Built for the FMA’s advice rules and the Privacy Act, and honest about the certifications we do not yet hold.
Protection is not a setting someone can forget to switch on. Each of these is enforced by construction, so it holds on every request, for every firm.
Each firm is a separate tenant. Records are scoped by firm at the database with row-level security, so one firm's clients, conversations, and decisions are never visible or joinable to another firm's.
Scoped by firm, at the database
Health and other sensitive PII is routed by data class before any model sees it. Anything sensitive goes to an in-region, DPA-backed model, never offshore. If that host is unavailable, Bob fails closed rather than reroute.
In region, or Bob stops
Personal and health data is stripped before it reaches any log, trace, or analytics sink. Redaction is one seam every event passes through, so a stray identifier cannot leak into an error report or a dashboard.
Redact-before-log
Every decision is written to an append-only record through one wrapper, with the right to edit or delete revoked. The log is the system of record, designed to be exported for a regulator.
Append-only, non-bypassable
Every firm runs as its own tenant. Records are scoped by firm at the database with row-level security, and each firm's knowledge model is trained on that firm's data alone. Isolation is enforced where the data lives, not just in the interface, so there is no shared-mailbox risk and no cross-tenant leak.
Health and other sensitive data is routed by class before any model sees it. Anything sensitive goes to an in-region, DPA-backed model and never offshore. If that host is unavailable, Bob fails closed rather than quietly routing somewhere it should not go, and personal data is redacted before it reaches any log or trace.
This is the security posture as it stands today, stated plainly. Where something is a commitment rather than a certificate, we say so.
We would rather you read the posture than take a logo on faith. Everything here is grounded in how the system is built: where the data lives, how sensitive PII is routed, what happens when the compliant host is down, and how the audit trail resists being edited after the fact.
The honest line at the bottom matters as much as the rest. We hold no SOC 2, ISO, or PCI certification, and we will not imply one. What we can show is a design built for the FMA’s advice rules and the Privacy Act, and a team happy to walk you through every row.
Need our data processing agreement or subprocessor list? Contact our team and we will share everything.
A general AI tool answers with no isolation and no record. A shared inbox and spreadsheet is only as safe as the last person who remembered. Bob makes isolation, residency, redaction, and the audit trail part of how it works.
| A general AI tool | Bob | A shared inbox & spreadsheet | |
|---|---|---|---|
| Data isolated per firm, at the database | No | Yes | No |
| Sensitive & health data kept in region | Unclear | Yes | Depends on the tool |
| Fails closed if the compliant host is down | No | Yes | No |
| PII redacted before logs and traces | No | Yes | Manual, if at all |
| Append-only trail, regulator-exportable | No | Yes | No |
| One firm's model never trained on another's data | No | Yes | No model |
| Role-based access, enforced server-side | Basic | Yes | Mailbox rules |
The guarantees below hold no matter how a firm is configured. Everything else is yours to set, within the rules your licence requires.
Bob is built so that keeping data safe is the default: tenant isolation, in-region routing for sensitive data, redact-before-log, and an append-only audit trail are part of the architecture, framed around FSLAA and the FMA's advice rules and around the Privacy Act with its Health Information Privacy Code. We are early, and we will not claim a SOC 2, ISO, or PCI certification we do not have. What we do claim is simple and checkable: each firm is isolated, sensitive data stays in region or Bob stops, PII is redacted before it is logged, and every decision lands on a trail that cannot be quietly rewritten. A licensed adviser, not Bob, binds any policy, so the record behind every decision has to stand up.
Every record is scoped to a firm, and the isolation is enforced at the database with row-level security, not just in the interface. One firm's clients, conversations, decisions, and knowledge model are never visible or joinable to another firm's. The firm-A-cannot-read-firm-B test is the definition of done for the very first table, and in this preview build a cross-firm read throws an error rather than leaking a single row.