Security & Deployment

Your documents, your perimeter.

This page is written for the people who say no: IT, security, and compliance. It describes exactly where documents go, what is stored, and what your institution controls. We are onboarding our first pilot institutions, so read every commitment below as what a Sabiá deployment is contracted to deliver — the scope your team reviews before the pilot, not a description of an installed base.

Deployment

Three ways to run Sabiá

Processing always runs server-side — nothing runs on the analyst's machine, and there is no Excel plugin to clear through bank IT. What changes between tiers is where that server sits.

TierFor whomHow it runs
Managed clouddefaultPilots and most clientsDocuments are uploaded to our hosted environment in the São Paulo region and processed there. Fastest to deploy — zero client install.
Private cloud / VPCInstitutions with cloud tenancy requirementsThe same software deployed inside your cloud tenant, so that documents stay within your account boundary.
On-premiseSecurity-sensitive work (IPOs, confidential M&A)Deployed inside your perimeter, including the model, so that documents — which in Brazil routinely include pre-IPO financials — stay inside your environment.
Commitments

What a deployment commits to

Immutable citation log

Each extracted field is stored with (document, page, bounding box, raw text, confidence score, timestamp, analyst action), and overrides append rather than overwrite. This is the audit trail we commit to putting in front of your compliance team.

Your documents never train models

Client documents are used to serve your extractions — nothing else. No training, no cross-client pooling. This is a contractual term, not a setting.

Per-client isolation

Each institution is provisioned with an isolated workspace, encrypted in transit and at rest, with role-based access control and retention policies your admin configures.

Supervision without exposure

Supervisors are given usage telemetry — workload, review flags, spend — and not the underlying client documents.

LGPD

LGPD & data residency

Processing in Brazil

The managed-cloud tier is deployed in the São Paulo region. Where data would cross borders (e.g. model inference), we disclose it before the pilot and put it under your control — including fully in-country options.

LGPD alignment

A signed DPA and a named contact for data-protection matters before any document is sent; PII detection and masking on uploaded documents, and configurable retention with auto-purge, delivered as part of the deployment.

Cross-border control

The admin console is built to show, per dataset, where data lives and whether it leaves Brazil — so your compliance team can audit residency instead of trusting a slide.

Certification roadmap

SOC 2 Type II preparation is on our roadmap ahead of bank-wide deployments. Security documentation — architecture, data flows, and the citation-log design — is available today for your IT team's review.

Have your IT team put us through review.

We'd rather answer the hard questions before the pilot than after.

Talk to usDownload one-page summary (PDF)