Security

Built for tenant isolation, private records, and defensible reports

DamperOps is planned around least-privilege access, private file delivery, audit logging, and future SOC 2 readiness evidence.

Offline-ready field workflow
Tenant-scoped records and audit logs
PDF reports with defensible revision history

Workflow

Built from the field record forward

Every page uses the same source-of-truth model: tenant, job, asset, inspection item, media, deficiency, report, audit.

Access Control

Tenant roles, customer portal grants, and internal support roles are separated at the backend policy layer.

  • Tenant-scoped queries
  • MFA for privileged roles
  • Support access audit logs
  • Session revocation

Data Protection

Private media and report documents are delivered with signed access, not public buckets.

  • TLS everywhere
  • KMS-ready storage
  • Hashed tokens
  • Stripe-hosted card collection

Operational Evidence

Critical actions produce append-only audit events that support incident response and report defensibility.

  • Report release logs
  • Measurement override logs
  • Webhook processing logs
  • Worker failure visibility

FAQ

Common launch questions

Does DamperOps support offline inspections?

The field workflow is designed around downloaded job packs, local drafts, queued media, and retry-safe sync.

Can reports be released to customers?

Yes. The product model includes QA approval, immutable report revisions, release actions, email delivery, and a customer portal.

Is billing built in?

The backend owns entitlements and syncs subscription truth from Stripe webhooks.