Funds

Where escrow lives

Funds are held in a neutral US escrow account on standard fiat banking rails. No cryptocurrency, no stablecoins. The escrow agent is a regulated US institution; account-level statements are available on request during procurement diligence.

When release happens

Verified completion + 48 hours with no OEM objection releases the escrow automatically. If an objection is raised, deterministic re-inspection resolves within 96 hours. No manual settlement steps; no AP queue.

What we cannot do

Fairbuild cannot unilaterally release funds, freeze accounts beyond the contract terms, or change pricing without 30 days' notice and mutual agreement. The escrow contract is the source of truth.

Data

What we ingest

Test-station artifacts agreed to in the spec — MTF curves, SFR measurements, ToF calibrations, cosmetic QA, etc. Equipment provenance — firmware hashes, bench IDs, calibration timestamps — is captured automatically.

How it is stored

Encrypted at rest. Cryptographically committed at submit time so neither side can revise after the fact. Per-tenant isolation. Retention configurable per contract; default is the lifetime of the manufacturing program plus 7 years for audit.

Who can see it

Both parties on the contract. Fairbuild engineering only when triggered by a dispute or by explicit request from one of the parties. Access is logged and auditable.

Disputes

48-hour objection window

After verification passes, the OEM has 48 hours to raise an objection. No objection = automatic settlement. This is the same window for every contract; it is encoded in the smart contract, not negotiated per deal.

Deterministic re-inspection

If an objection is raised, escrow is frozen. A random sample selection neither side controls is re-tested by Fairbuild. The result is binding. Resolution within 96 hours. The dispute-resolution fee is split equally between OEM and factory.

What is escalation-only

Pricing changes, settlement-window changes, and contract-term changes are governance-only — multi-party approval with a minimum 1-hour delay before any state change. All governance actions are tamper-proof and auditable on-chain.

Contract auditability

The settlement contract is open source. Read it, run it locally, fork it. The code is the contract — there is no separate "what we actually do" hidden behind a UI.

View on GitHub See the platform

Compliance posture

Honest about where we are.

SOC 2 Type II — in progress. Targeted attestation in 2026. Vendor-questionnaire responses available on request during diligence.

Penetration testing — annual third-party engagement on the settlement contract and verification layer. Latest report shareable under NDA.

Data residency — primary processing in US-East. Region pinning available for contracts requiring EU or APAC residency.

Incident response — 24-hour notification SLA on confirmed security incidents affecting your data. Status page and post-incident review for any platform-wide event.

Need anything else for diligence?

SOC 2 progress, vendor-security questionnaires, redlines on the standard contract — write security@fairb.com.