Claims files contain sensitive data. We design accordingly.
The controls below describe the ClaimNest production architecture.
Encryption
TLS 1.2+ in transit. S3, PostgreSQL and backups encrypted at rest with AWS KMS customer-managed keys, one key per tenant on Enterprise.
Tenant isolation
Every record carries a tenant ID enforced by PostgreSQL row-level security. S3 objects live under tenant-scoped prefixes and are reachable only through short-lived pre-signed URLs.
Secure file access
Uploads go straight to S3 via pre-signed POST with size and content-type conditions. Downloads are signed, expire in minutes and are never public. Files are scanned before processing.
Audit logging
Every upload, view, approval, correction, export and permission change is written to an append-only audit table and shipped to CloudTrail-protected storage.
Configurable retention
Set retention per tenant and claim type. Scheduled Lambda jobs delete documents and records at expiry, with legal-hold overrides, and log each deletion.
Access control
Role-based access (broker assistant, reviewer, administrator), SSO on Enterprise, and least-privilege IAM for every function.
AI data handling
Amazon Bedrock inputs and outputs are not used to train foundation models. Prompts contain only the content needed for the task, and model output is stored as a draft pending human review.
Responsible AI
No automated eligibility, denial or settlement decisions. Every AI-extracted value is source-linked and requires human approval before a file is marked ready.