Skip to content

Trust Center

ProofOfFit is committed to security, fairness, and verifiable accountability. Every control listed below is live today or labelled explicitly as “in progress.”

Security at a glance

TLS 1.2+ encryption in transit
AES-256 encryption at rest
Hardened cloud perimeter and network segmentation
SSO / SAML & optional SCIM provisioning
MFA required for administrative access
Role-based access control and least privilege
Comprehensive audit logging and daily reviews
Daily backups with point-in-time recovery
Quarterly incident tabletop exercises
Annual vendor risk assessments

Compliance status: SOC 2 Type II in audit (FY2025–FY2026). A public Letter of Attestation will be linked here when available; the full report is provided under NDA through our request process.

Note: When SOC 2 attestation completes, replace "in audit (FY2025–FY2026)" with the actual attestation date and link to the Letter of Attestation.

Security documentation:

Sub-processors and data locations are listed with purpose, region, and DPA references in ourdata handling overview. Cross-border transfers rely on SCCs/UK Addendum with supplementary safeguards.

Fairness, validation & human oversight

What we measure

  • Adverse Impact Ratio (AIR): Selection rate of each protected group divided by the highest selection rate.
  • Error parity: False positive/negative rates monitored across groups when ground truth is available.
  • Calibration & drift: Segment-level calibration checks and alerts when feature distributions shift.

How we run studies

  • Fairness attributes collected only with explicit opt-in consent.
  • Attributes excluded from production decision features—used solely for validation/auditing.
  • Minimum sample thresholds and confidence intervals accompany every finding.
  • Model cards, validation reports, and change logs document methods and limitations.
Human-in-the-loop: Automated outputs are assistive. Customers review results, provide required notices, and maintain appeal channels. We do not claim “bias-free” outcomes; we publish metrics, methods, and limits.

Cryptographic audit trail

Every high-value event is signed so customers can verify integrity independently. Examples include:

  • Score generated
  • Model version applied
  • Decision reviewed
  • Policy or threshold changed
  • Viewer accessed candidate profile

Workflow: create a canonical JSON event, hash with SHA-256, sign using an Ed25519 platform key, append to a daily Merkle tree, and publish the root (optionally anchoring to a public ledger for timestamping). A public verifier CLI/web will let stakeholders confirm object → hash → signature → Merkle membership.

{
  "id": "evt_01HF…",
  "type": "score.created",
  "occurred_at": "2025-11-02T18:44:12Z",
  "subject": {"candidate_id": "cand_9b1…", "requisition_id": "req_42"},
  "actor": {"service": "scoring", "model_version": "fit-v3.2.1"},
  "inputs": {"features": "deterministic_ref_v3", "source_hash": "sha256-abc…"},
  "outputs": {"score": 0.78, "explanations": ["experience_years", "+domain_keywords"]},
  "env": {"app": "api", "region": "us-central1"},
  "privacy": {"contains_sensitive_attributes": false}
}

Signature envelope (detached JWS):

{
  "alg": "EdDSA",
  "kid": "pf-public-ed25519-2025",
  "hash": "sha256-3a5d…",
  "sig": "MEUCIQDu…"
}

Evidence & footnotes

Any numerical claim (for example, “37% faster time-to-hire”) must link to a methods note covering sample size, time period, control group, and statistical test. We will only publish metrics that meet this standard.