Security

Security and data

How we protect the Clarapact product, the data in it, and the little we collect about you.

No patient data

Clarapact doesn’t use or hold patient information. The product is built from payer-reported allowed amounts, which contain no patient records. Please don’t send us any patient information.

Customers see a read-only copy

The product reads from a separate, read-only copy of the data that we publish for customers. It has no connection to our internal systems.

That copy holds only out-of-network allowed amounts and the details needed to cite them. Nothing goes into it unless it is on an approved list, and every release of the product is checked for anything that shouldn’t be there.

What you see is what we published

Each data release is checked before it is served. A new release replaces the old one only after it passes every check. If it doesn’t, the product keeps serving the last good version. If no checked data is available, the product says so rather than showing partial data.

Every citation carries a digital fingerprint, so a copied citation can be matched to the exact text Clarapact produced. Figures on screen and in the workbook come from the same calculation, so they match.

Access

Access is by invitation, with credentials we issue. If the product is ever missing its credentials or signing keys, it refuses every request instead of running open. Session cookies can’t be read by page scripts and are sent only over HTTPS.

What each plan includes is checked on our servers for every request, not just hidden in the page. Report tables load a page at a time, and citations are copied with a Copy button that logs each copy.

Protections on every page

All connections use HTTPS, and browsers are told to accept nothing else. Every response, including errors, carries strict browser security headers: pages run only Clarapact’s own scripts and styles, can’t be framed by other sites, and have camera, microphone, location, payment and USB access turned off.

We treat everything you send as data, never as code. Database queries never include pasted-in text, inputs are checked against fixed lists and length limits, and nothing you send is echoed back. Error pages show generic text, never internal details.

What we log

Product logs record which page was requested, the result, and how long it took. They don’t include report figures or database queries.

When you copy a citation, we log the payer, the code, the citation’s fingerprint and a random browser ID. We don’t store the citation text or any dollar amounts. Your browser keeps only your display preferences and that random ID.

How we build and run Clarapact

No passwords or keys live in our code. Credentials are kept in our hosting settings and hidden from logs. Every software dependency is pinned to an exact version, and our code is kept in private repositories.

Changes go through an automated security test suite, and nothing goes live until someone on our team releases it.

This website

clarapact.com uses no analytics, advertising or tracking cookies, and runs only its own scripts. The demo form collects only what you type into it. Our Privacy Policy explains how we handle it.

Reporting a security concern

If you think you’ve found a security issue, email security@clarapact.com.

Bring numbers to your next negotiation.

We’ll walk you through a report built for your payers and states, and show how the citations fit into your claims process.