Everything DAF puts in writing before your countersign.

• Native e-signature (UECA-compliant)

  Live
  Engagement letters and supplemental agreements are signed on DAF's own /sign surface. Typed-name match, drawn signature, intent checkbox, and IP/UA/timestamp captured. Signed PDF issued to both parties and archived in the operator's portal. Not a third-party redirect.
• Data residency

  AWS ca-central-1
  Client project data is stored in Supabase Postgres, hosted in AWS ca-central-1 (Montréal). PIPEDA-compliant. Photo uploads persist in Vercel Blob (US-east) with http/https-only URL validation.
• Refund + termination

  Written policy
  The deposit is refundable in full up to the point DAF issues a PO to the workshop. After PO issuance, the deposit is refundable minus the supplier's cancellation fee (typically the tooling / cutting-fee band) plus DAF's coordination fee. Full policy is written into the engagement letter — no post-hoc surprises.
• AI canon guardrail

  Every AI output
  Every AI-drafted communication (RFQ, sample plan, status update) passes through DAF's canon guardrail before it reaches a supplier or operator. Pricing, sourcing region, identity, and voice rules are statically checked; hard violations auto-repair via a second model pass; any residual break stops the message.
• Warranty administration

  Per-piece registration
  Every delivered piece is registered on the operator's DAF portal at delivery. Manufacturer warranty terms are held in writing; DAF administers the claim end-to-end with the workshop. The operator never coordinates a warranty issue with an overseas supplier.
• Early-stage honesty

  No pretense
  DAF is early-stage. No claim of insurance certificates, SOC 2 status, or a shelf of prior clients that don't exist. When you sign, you're signing with a specific individual (Ben Lafreniere) who responds to every enterprise brief within one business day. The published-case-study shelf is intentionally empty until the first portfolio closes with permission.

Controls in production today.

• ·Clerk-authenticated /portal + /ops with allowlisted admin roles.
• ·Supabase Row-Level Security enabled on every project + supplier table; service-role writes only through server routes.
• ·Immutable audit rows on /sign completions (IP, UA, timestamp, signature SVG).
• ·requireOps() defense-in-depth wrapper on every /api/ops route, in addition to middleware allowlist.
• ·URL scheme allowlist on all uploaded / stored asset links (http/https only) — statically enforced at zod boundary and defensively at render.
• ·Per-supplier tokens for factory uploads: single-purpose, kind-scoped, expirable, revocable.
• ·Canon guardrail on every AI-generated string that reaches an external party.
• ·Stripe webhook idempotency on evt.id — retries never double-fulfill.

Talk to Ben directly.

Sample engagement letter, refund + termination language, and all controls above are available on request. Ben responds within one business day and will send documents where they exist and be direct about what's still on the roadmap.