Where your calibration records live, and what protects them

• CalibrationOS runs on Amazon Web Services in the AWS GovCloud (US-West) region (us-gov-west-1).
• Your gage list, calibration records, audit log and the certificate PDFs you upload are stored in a PostgreSQL database there.
• The disks that hold the database are encrypted with keys managed in AWS Key Management Service (KMS).

Who else handles your data

Amazon Web Services

Runs the server, the database, the nightly backups, sign-in (Amazon Cognito) and the emails we send (Amazon SES), all in AWS GovCloud (US-West).

Cloudflare

Every request to calibrationos.com passes through Cloudflare's network, which handles the HTTPS connection to your browser.

Anthropic

Reads the certificate PDFs you upload to certificate intake, through Anthropic's API. Each read sends that one certificate PDF; your gage list and other records stay in CalibrationOS.

Stripe

Takes card payments if you subscribe to a paid plan, on Stripe's own checkout page.

The analytics tools on this website, and how to turn them off, are listed in our cookie policy.

• Every page and every API call uses HTTPS. A plain HTTP request is redirected to HTTPS.
• Browsers are told to always use HTTPS for this site and its subdomains, for a year at a time (HSTS).
• Between Cloudflare and our server, traffic is encrypted again, with TLS 1.2 or newer.

• Sign-in runs on Amazon Cognito. Passwords must be at least 12 characters, with upper and lower case letters, a number and a symbol.
• You can turn on two-step sign-in with an authenticator app in your account's security settings.
• Six roles (Owner, Admin, Manager, Technician, Viewer and Auditor) decide who can record calibrations, approve them, change equipment or manage settings.

• Changes to equipment, calibration records, out-of-tolerance investigations, reference standards, vendors, team members and webhooks are written to an audit log: who made the change, what changed, when, and from which IP address.
• When a calibration record is edited, the log keeps the values before and after. For equipment, it records which fields changed.
• Each entry carries a SHA-256 hash of its contents and of the entry before it. A later edit or removal breaks the chain, and the integrity report in your audit evidence package names the first entry where it breaks.
• On Professional, approvals can carry an electronic signature: who signed, when, and what the signature means (approved, reviewed, authored or witnessed), confirmed with the signer's PIN.

The hash chain makes a change to past entries detectable.

• The database is backed up every night to Amazon S3 in AWS GovCloud (US-West).
• Backups are encrypted with AWS KMS and kept for seven years.
• Certificate PDFs are stored in the database, so they are in the same nightly backup.

On every plan, at any time:

• From the Reports page, your gage list (equipment register) as a CSV or PDF file.
• From the Reports page, an audit evidence package: a ZIP of CSV and text files with your gage list, approved calibrations, out-of-tolerance investigations, reference standards and active procedures, plus the most recent 500 audit log entries and an integrity report for the whole log.
• From each calibration record, the lab certificate PDF you uploaded.

On Professional, the REST API also returns your equipment and calibration records as JSON, up to 100 at a time.

• Our security program is built to NIST SP 800-171 for CMMC 2.0 Level 2. The assessment is in progress.
• SOC 2 is in progress.

Amazon Web Services publishes which of its services its own audits cover.

Found a security problem, or need answers for a supplier questionnaire? Email [email protected].