Skip to content

Vendor & Subprocessor Management Policy

Owner [Security Owner β€” to be named: founder/CTO]
Approved by [signatory]
Effective date [set on approval]
Review cadence Annual
Version 0.1 β€” DRAFT
TSC mapping CC9.2

Ensure third parties that process Company or customer data meet the Company’s security commitments, and that the Company can demonstrate oversight of them.

The Company maintains a register of all subprocessors that store or process customer data. Current subprocessors (from the CASA self-assessment Β§1):

Subprocessor Purpose Data
Clerk Authentication / identity User identity
Google Cloud Application hosting (Cloud Run), infra All platform data
Neon Application database (Postgres) Orders, PII
Cloudflare R2 object storage, Access, edge/CDN Documents, PO files
Stripe Billing Company billing data
WhereFour ERP integration Order/PO data
Prophet21 (Epicor) Customer ERP integration Order/PO data
Infisical Secrets management Credentials
1Password Secrets / credential vault Credentials
Google Workspace Email, identity, docs Company data

Before a vendor processes Company or customer data, the Security Owner:

  1. Confirms the business need and the data the vendor will touch.
  2. Collects the vendor’s SOC 2 / ISO 27001 report (or equivalent) as inherited evidence; records the report date and any exceptions.
  3. Signs a Data Processing Agreement (DPA) where the vendor processes personal data.
  4. Records the vendor in the register with owner, data class, and review date.
  • The vendor register is reviewed annually: re-collect current SOC 2/ISO reports, re-confirm DPAs, and re-assess risk.
  • Subprocessor SOC 2 reports also serve as the Company’s inherited evidence for physical security and data-center controls (CC6.4), since all infrastructure is cloud-hosted.

The Company publishes a current subprocessor list to customers (trust center / website) and updates it when subprocessors change.

Reviewed at least annually by the Security Owner.