Security and data handling
Security, storage and subprocessors for medical records
Vendor vetting packet (PDF) Data protection agreement (PDF)
- Storage
- Records are processed and stored in the United States, on Amazon Web Services. They are encrypted in transit and at rest.
- Isolation
- Each firm’s records are isolated from every other firm’s, and the isolation is tested.
- Subprocessors
- The subprocessors are Amazon Web Services, Stripe, Cloudflare and Google Workspace. AI reads records inside our own AWS account, under a BAA.
- Agreement
- A data protection agreement covers every client; where the client is a covered entity or its business associate, it is the business associate agreement.
- Training
- No client record is used to train a model. Each version of the agreement takes effect when the firm accepts it. There is no subscription; each case is quoted and paid on its own. Either side can end the agreement on notice.
- Retention
- Files are deleted after 90 days, sooner on request. A failed case is deleted 90 days after it was created. A quote expires after 14 days; an unaccepted quote and its upload are deleted then. A case is deleted sooner at the firm’s request, and every deletion is logged.
- Reviewers
- Reviewers are based in the United States and work under confidentiality agreements. Claracord organizes and extracts; a person verifies.
- Citations
- Every fact cites the page it came from and is checked there by a reviewer. A chronology is released only after every readable page is accounted for. Our errors are corrected at no charge.
- Review log
- Every review decision is written to an append-only log: the question, the page, the answer, the reviewer and the time.
- Incidents
- A firm is told of a security incident affecting its records without unreasonable delay, and within 30 days at the latest.
- Reporting
- Security reports go to security@claracord.com. A client account can add a one-time code from an authenticator app at sign-in.
Each line is backed in the claims register.