Security & Trust

Engineered for documents that matter.

We process documents that decide loans, claims, payouts and onboardings. That responsibility shapes every choice in our stack — from how data is encrypted to how requests are audited. This page documents what we do, what we don't, and where we're going.

Last updated: 2026-04-30

Security pillars

Four commitments. Built into the platform from day one.

Security at fluex isn't a checklist bolted on at the end. These four principles are wired into every code path, every deploy, every customer integration.

Encryption everywhere

TLS 1.3 in transit. AES-256-GCM at rest. Per-tenant data encryption keys managed in Google Cloud KMS, rotated automatically, never co-located with the data they protect. Customer-managed keys (CMEK) available on Enterprise.

Strict tenant isolation

Every API request is scoped to a single tenant at the database layer. No shared compute, no cross-tenant queries, no global indexes. Enterprise customers can opt into dedicated infrastructure isolation and a single-tenant VPC deployment.

Least-privilege access

Role-based access control. MFA required for every employee account. Production access follows a dual-approval workflow with time-bound permissions and audit logging. Engineer access to customer document content requires a documented business reason and reviewer approval.

Complete audit trail

Every extraction, every review, every export — logged with timestamp, requestor identity, model version, prompt and response. Audit metadata is immutable and exportable, ready for SOX, GDPR, CCPA or external auditor review.

Document lifecycle

Where your documents live, and how long.

We're explicit about every stage. No surprise retention, no opaque storage. Defaults are conservative; everything is configurable per contract.

Step 01

Ingestion

TLS 1.3 from your endpoint to our API. Document bytes are never persisted in access logs. Request metadata is logged without document content.

Step 02

Processing

Extraction runs in-memory only during inference. No document data crosses tenant boundaries. Sub-processor LLM calls are configurable per tenant — including no-LLM workflows.

Step 03

Storage

Documents and extraction results are encrypted at rest with per-tenant keys. Retention is configurable per workflow: default 90 days, can be set to zero (no retention beyond the request).

Step 04

Deletion

Hard deletion at retention expiry. A 30-day soft-delete window protects against accidental loss; on request, we hard-delete immediately. Audit metadata is retained per your contract.

Step 05

Audit export

Audit metadata (request, response, model version, reviewer, timestamps) is queryable via API and exportable as JSON-Lines or CSV. Default audit retention: 7 years.

Step 06

Subject requests

As a processor, fluex routes data subject requests (access, deletion, portability under GDPR or CCPA) to the controller — you. We provide tooling and a 30-day SLA for fulfillment.

Compliance posture

Working with regulated industries.

We're transparent about where we are on each framework. Where an audit is in progress, we say so. Where it isn't, we say that too. Trust packets — including DPA, security questionnaire responses, and current audit reports — are available on request.

SOC 2 Type II
● Audit in progress
GDPR (EU)
● DPA available
CCPA / CPRA
● DSR-ready
HIPAA
● BAA on Enterprise
ISO 27001
● Roadmap
PCI DSS
○ Out of scope

GDPR — for our EU customers

fluex acts as a data processor under GDPR Art. 28. Our standard Data Processing Addendum incorporates the EU Standard Contractual Clauses for transfers outside the EEA, and binds every sub-processor to equivalent terms. Sign the DPA at legal@fluex.com.

CCPA / CPRA — for our California customers

fluex is a service provider under CCPA §1798.140(ag). We do not sell or share personal information. Data subject requests (right to know, delete, correct, opt out of sharing) are routed to the controller; our SLA is 30 days from receipt.

SOC 2 Type II — for our enterprise customers

Our Type II audit is currently underway. Target report date, audit progress, and our current Type I report are available under NDA — email security@fluex.com.

HIPAA — for healthcare workflows

Business Associate Agreements are available on Enterprise contracts. PHI handling is configurable per workflow — including no-retention modes and PHI-aware redaction in audit metadata.

Sub-processors

The infrastructure behind fluex.

We list every sub-processor that handles customer data, what they do, and where they operate. Customers receive at least 30 days' notice before any addition or change, with the right to object under the DPA.

Vendor Purpose Region Data accessed
Google Cloud Platform Compute, storage, networking, KMS USA Documents, extractions, audit metadata
OpenAI LLM inference (configurable per tenant) USA Document content during inference; zero-retention API
Anthropic LLM inference (configurable per tenant) USA Document content during inference; zero-retention API
New Relic Observability (logs, metrics, traces, APM) USA Operational telemetry only — document bodies are scrubbed before egress
Twilio Transactional SMS, WhatsApp and email notifications USA Recipient phone / email + transactional message content; never customer documents
Fingerprint Device fingerprinting for fraud detection & KYC USA Browser / device fingerprint metadata; never document content
Cloudflare Edge, WAF, DDoS mitigation Global edge Request metadata only; document bodies bypass edge cache

Subscribe to sub-processor change notifications to receive updates 30 days before any change.

Responsible disclosure

Found something? Tell us.

We respect security researchers and respond to good-faith reports within one business day. We commit to working transparently with reporters and crediting their work.

How to report

  1. Email security@fluex.com with a clear description of the issue, reproduction steps, and impact.
  2. If the issue is sensitive, request our PGP key in your initial email; we'll respond with one within four business hours.
  3. Please give us 90 days before public disclosure. We commit to fixing critical issues within 30 days, high-severity within 60, and to credit you in the changelog (if you'd like).

In scope

  • fluex.ai and all *.fluex.ai subdomains
  • The Document AI REST API and webhook system
  • Authentication, session and tenant-isolation logic
  • Customer dashboards and review queues

Out of scope

  • Self-XSS / clickjacking on pages without sensitive actions
  • Issues in third-party services we sub-process to (report directly to the vendor)
  • Rate-limiting and brute-force on public endpoints (we have those covered)
  • Best-practice header reports without a demonstrated exploit
Trust packet

Need DPAs, audit reports or a security questionnaire?

Most enterprise security questionnaires take us under one business day. Sub-processor notification subscriptions, DPAs, current SOC 2 status and our pen-test summary are all available on request — no NDA gate for the high-level docs.