Trust Center

Your project record is evidence. We guard it that way.

Pay estimates, claim narratives, bid numbers and test results are the records that decide what you get paid. This page lists the controls built into RBCopilot today — only what the product actually does.

🏢

One company, one private workspace

Every record is stamped with the company it belongs to, and every query is scoped to the signed-in user's company — one contractor never sees another contractor's projects.

  • Company scoping on documents, projects, bids, pay estimates, field and QC data
  • Automated tests check that one company can't read or change another company's data
  • Anonymous requests to project data are refused
🔑

Sign-in and passwords

Passwords are never stored. We keep only a bcrypt hash (cost factor 12), and sessions use signed tokens that expire.

  • bcrypt password hashing
  • Signed session tokens (JWT) that expire after 7 days
  • Sign-in is switched off if the server's signing secret is missing or weak
  • Rate limits on sign-in, sign-up, team join codes and other secret-bearing endpoints to stop password guessing
  • Optional two-factor sign-in with any authenticator app (TOTP), with one-time recovery codes stored only as hashes; admins can see who on the team has it on
  • API tokens for integrations: created by an admin, read-only or read/write, shown once and stored only as a SHA-256 hash, and revocable at any time
🎛️

Role-based access

Each user has a role: admin, project manager, estimator, superintendent, inspector, QC manager, subcontractor or agency reviewer.

  • Subcontractors and agency reviewers are read-only — any write is refused on the server
  • Only company admins change company settings, manage members and read the full audit log
  • Only admins and project managers can view, rotate or disconnect the Field and Plant connection keys
  • Modules your company doesn't have are locked on the server, not just hidden
🔒

Encryption in transit and at rest

All traffic is HTTPS, enforced with HSTS. The most sensitive text is also encrypted field by field before it reaches the database, with a key held by the application — not in the database.

  • Field-level encryption (Fernet: AES-128-CBC + HMAC-SHA256) for RFI bodies and responses, claim narratives and basis, bid intake data, bid notes, AI summaries and agent outputs
  • Field device keys are stored only as SHA-256 hashes
  • Server-to-server messages from the RBCopilot Field service are verified with an HMAC-SHA256 signature
📑

Change history and protected money records

Contracts, pay estimates, change orders, RFIs and claims keep a change history of who changed what, and when; money records also keep a before/after snapshot. Changes to users, API tokens, field reports and projects are logged too. Admins review it in Office & Rules → Audit Log.

  • The audit trail outlives the project — it stays readable even after a project is deleted
  • A project with submitted, approved or paid pay estimates, or approved change orders, cannot be deleted
🤖

AI that runs only when you turn it on

AI features use Anthropic's Claude models. They are opt-in: nothing is sent to the AI provider unless AI is enabled for your account and a signed-in user runs an AI feature.

  • Server-side AI requires a signed-in user plus an AI unlock issued to that user and company; it expires after 2 hours
  • Per-user hourly and per-company daily AI quotas, and caps on prompt and document length
  • What is sent is the content the feature needs — for example the question, the bid or document being analyzed, and the relevant specification excerpts
  • AI output is a draft — your team reviews it before it is used
🦺

Field devices

RBCopilot Field keeps work on the phone or tablet until it can sync, so nothing is lost with no signal.

  • Each device connects to your company with its own key
  • Device keys are stored on our side only as one-way hashes
  • Admins can remove a phone or tablet from the Device Fleet
🛡️

Application hardening

The web app is built to resist the common attacks against business software.

  • User content is escaped before it is rendered, with an automated check across every page
  • Stored links are limited to same-site paths or approved HTTPS hosts
  • Uploaded Office files are checked for zip bombs before parsing, with time limits on parsers
  • Backend dependencies are pinned to exact, tested versions
☁️

Hosting and infrastructure

RBCopilot runs on managed cloud infrastructure — no servers in someone's back office.

  • Application and API hosted on Vercel
  • Managed PostgreSQL database on Neon, reached through a connection pooler
  • Uploaded files stored in Vercel Blob storage
In your browser

Security headers on every page.

Sent by the hosting layer on every response from rbcopilot.com. You can check them yourself in your browser's developer tools.

Strict-Transport-Security
HTTPS only, for two years, including subdomains (max-age=63072000; includeSubDomains; preload).
Content-Security-Policy
Scripts load only from our own site and a strict allow-list of libraries pinned to exact versions. Inline scripts are allowed (the pages are built with them), but scripts from any host outside the allow-list are blocked. The app can't be framed by other sites (frame-ancestors 'none'), plugins are blocked and forms post only to our own site.
X-Frame-Options
DENY — protects against clickjacking. The companion Bid History pages use SAMEORIGIN so they can open inside the app.
X-Content-Type-Options
nosniff — the browser won't guess file types.
Referrer-Policy
strict-origin-when-cross-origin — page paths aren't leaked to other sites.
Permissions-Policy
Camera, microphone and location can be requested only by RBCopilot's own pages — never by embedded third-party content.
Responsible disclosure

Report a vulnerability.

Found something that looks wrong? We want to hear about it and we'll work with you to fix it.

How to report

Email a description of the issue, the steps to reproduce it and the page or endpoint involved. Please include your contact details so we can follow up.

support@rbcopilot.com

Put "Security report" in the subject line.

Please

  1. Test only against your own account or the public demo workspace.
  2. Don't access, change or delete other customers' data.
  3. Don't run denial-of-service, spam or social-engineering tests.
  4. Give us reasonable time to fix the issue before sharing it publicly.

This page describes the product's controls; it isn't a certification. We don't list third-party audit reports, certifications or an uptime commitment here. If your procurement team needs a security questionnaire answered, contact us. See also our Privacy Policy.