Security & compliance
The AI your compliance officer can sign off on.
This page does double duty: it reassures the gatekeeper and gives the champion ammunition to sell internally. We map Microfiber's controls directly to what your firm's WISP requires.
Data custody, tier-honest
Your document corpus always lives inside a boundary we control, on our hardware — this never changes across tiers. Never used for training; never commingled across tenants. What differs by tier is what reaches the model at query time:
Standard (managed inference)
Most firmsYour documents stay in our controlled environment. At query time, only the relevant excerpts needed to answer are processed by our contracted inference provider under a binding no-retention, no-training agreement. The provider is contractually bound and overseeable — documentable for your WISP — but those excerpts do transit to it. (It is not a public model API; it is a vetted, contracted sub-processor.)
Dedicated (owned-hardware, closed-loop)
StrictestNothing leaves the controlled environment — retrieval and inference both happen inside it. This is the only tier on which “your data never leaves” is literally true; the right tier for the strictest custody requirements.
The controls
Isolation
Per-tenant, dedicated environments — your documents and the search index built from them are never commingled with another firm's.
Encryption
TLS in transit; strong (AES-256-class) encryption at rest — including the embeddings / search index, which we treat as sensitive client-derived data, not just metadata.
One hardened front door
The API gateway is the only internet-facing component. The vector store and inference backends sit on a private network behind it — there is no public path to your documents.
Logging & audit trail
Metadata only (which tenant, which model, token counts, latency, status) — never prompt or response content. Your firm gets a browsable, per-tenant audit log: proof a request happened, with nothing sensitive captured.
Sub-processor oversight
Every infrastructure provider that can touch client data operates under a binding agreement with no-retention and no-training terms — vetted, contractually bound, and overseeable, and documentable for your WISP. We don't publish our vendor stack on the open web; the specific sub-processors are disclosed to customers in the DPA and available on request for your compliance review.
Web research (optional) — your data stays in
Optional and off by default. When you enable it, we never send your documents, corpus, or conversation to the web — only a freshly-composed, identifier-stripped search query. Client and people names, SSNs, account/policy numbers, emails, and street addresses are stripped before anything leaves; a question that would need your private data refuses instead of searching. You see the exact query that went out, and it's recorded inside your boundary. Honest caveat: a public search engine is not a no-retention sub-processor, so the query reaches it under that provider's terms — which is why this is opt-in, disclosed, and turned off entirely on the dedicated, closed-loop tier.
Portability / no lock-in
Export your data and (on the owned tier) your model weights anytime; certificate of destruction on exit. Portability is a feature, never lock-in by pain.
Uptime
Uptime is a service commitment defined in your agreement. Custody, by contrast, is architectural and absolute — it doesn't depend on a service level.
Custody is architectural03
A boundary in the architecture — not a promise in a contract.
Your document corpus stays inside a boundary we control; what reaches the model at query time depends on your tier. Custody is architectural and attestable. Uptime is a separate, service-level commitment.
app + users · api.microfiber.[tld] with your key
auth · routing · metadata-only logging
your documents · cited answers
Your document corpus — stays inside a boundary we control.
stateless compute
calls only
prompt + retrieved chunks → ← answer
stateless utility · stores nothing · swappable
The control-plane / data-plane split — the trust story, made architectural.
WISP mapping
What your WISP requires → how Microfiber maps to it.
Informational only — not legal advice. Microfiber is the vetted third party for the AI that touches client data. Controls your firm still owns — a designated Qualified Individual, risk assessments, an incident-response plan, breach notification — remain your responsibility.
- Your obligation (FTC Safeguards Rule)
Oversee third parties that touch client data
How Microfiber helpsA vettable, contractually-bound provider with attestable custody — DPA + documented controls.
What your firm still ownsSelecting Microfiber; keeping the DPA on file; periodic review.
- Your obligation (FTC Safeguards Rule)
Encryption in transit & at rest
How Microfiber helpsTLS in transit; strong at-rest encryption across the data plane.
What your firm still ownsEncryption on your own endpoints.
- Your obligation (FTC Safeguards Rule)
Access controls
How Microfiber helpsPer-tenant isolation; scoped API keys; least-privilege.
What your firm still ownsUser / role management inside your firm.
- Your obligation (FTC Safeguards Rule)
Multi-factor authentication
How Microfiber helpsMFA on the Microfiber portal.
What your firm still ownsMFA on your own systems.
- Your obligation (FTC Safeguards Rule)
Monitoring & logging
How Microfiber helpsMetadata-only request logging; per-tenant audit log.
What your firm still ownsYour own monitoring program.
- Your obligation (FTC Safeguards Rule)
Secure disposal
How Microfiber helpsExport + certificate of destruction on offboarding.
What your firm still ownsYour broader retention policy.
- Your obligation (FTC Safeguards Rule)
Data not used for AI training
How Microfiber helpsContractual no-training / no-retention terms.
What your firm still ownsVerifying the term is in the signed agreement.
For the gatekeeper
Bring your WISP. We'll map to it.
The fastest way to satisfy your compliance gatekeeper is to walk the mapping line by line against your information security plan — in a private demo, on sanitized data first.