◆ Security overview
Security overview
FineSchema is designed as a deterministic pre-action verification layer. It should be inspectable, replayable, and deployable with minimal data exposure. This page summarizes data handling, deployment modes, compliance posture, audit traces, and sub-processors. The full interactive section lives on the home page.
- No data retention by default in self-hosted mode — customer-controlled.
- CPU-only verification, No model weights in the verification gate.
- Deterministic replay and Audit-ready traces for every verdict.
- Air-gapped deployment option and Fail-closed checkpoint.
- Customer-controlled policy cartridges.
For hosted pilots, retention and logging are configured per customer agreement. Self-hosted and air-gapped deployments can be configured for customer-controlled data retention.
Data handling
What FineSchema receives
- Proposed action
- Agent rationale
- Policy cartridge
- Relevant evidence fields
- Optional metadata
What FineSchema stores
- Configurable trace logs
- Verification outcome
- Timestamp
- Policy cartridge version
- No raw customer data by default in self-hosted mode
What FineSchema returns
- VERIFIED / UNCERTAIN / BLOCKED
- Reason code
- Trace
- Missing evidence
- Safer action recommendation
What customers control
- Policy cartridge
- Retention policy
- Deployment mode
- Approval workflow
- Audit export
Deployment modes
The browser prototype demonstrates the inspection pattern. It is not the full production engine.
ModeUse caseData exposureOperational maturityBest for
Browser prototypeIllustrative inspection patternNone — client-sideDemo onlyFirst look, education
Hosted pilotScoped 14-day evaluationPer customer agreementPilotFast proof on one action family
VPC deploymentRun inside your cloud accountStays in your VPCProduction-leaningTeams with cloud governance
Self-hostedYour infra, your control planeCustomer-controlledProductionStrict data-residency needs
Air-gappedOffline / classified enclaveNo network egressProduction · accreditedDefense, regulated, classified
Audit traces
Every verdict carries a trace ID. Replay reproduces the exact reasoning byte-for-byte, and the append-only verdict log records action, verdict, reason code, missing evidence, and trace — audit-ready records customers can export for review.
Sub-processors
Sub-processors depend on deployment mode. Sub-processors are determined by deployment mode. Self-hosted and air-gapped deployments can minimize or eliminate third-party processing. Hosted pilots may use infrastructure providers such as Vercel or email delivery providers if configured. This is not a confirmed sub-processor list until contracted.
Compliance posture
FineSchema is not currently claiming SOC 2, HIPAA, ISO, or GDPR certification. Compliance posture depends on deployment mode, customer requirements, and validation scope.
- SOC 2-ready roadmap
- HIPAA-regulated deployments require customer-specific validation
- GDPR and regional privacy review required before production deployment