Security at BidCertain

Every table enforces Postgres row-level security, so one company's documents, analyses, rate database and pipeline are never readable by another. Uploaded files live in a private storage bucket under the same rules.

Each workspace has owner, admin, estimator and viewer roles. Every write endpoint checks the caller's role, and an automated test fails the build if a new endpoint skips that check.

All traffic is HTTPS-only (HSTS, two-year max-age). Data is encrypted at rest by our database and hosting providers. Integration credentials you store are additionally encrypted with AES-256-GCM using per-account derived keys.

We don't use your documents, estimates or rates to train AI models. Documents are sent to our AI sub-processors only to produce your analysis.

Changes to analyses, proposals and other records are written to an activity log, and administrative actions — including any support access to an account — are recorded separately.

Every change is reviewed through pull requests that must pass lint, type checks, thousands of automated tests, secret scanning and a database-migration replay before it can merge. Dependencies are audited weekly and updated through Dependabot.

A strict Content Security Policy, frame blocking and a tight referrer policy protect against injected scripts, clickjacking and leaking private links.

Application errors are captured and alerted on, and a scheduled synthetic check exercises key flows.

Workspace owners can set retention rules, place records on legal hold, and export their data.