Encrypted in transit
Every page and upload runs over HTTPS with TLS 1.2+ and HSTS enabled. Session cookies are marked Secure and HttpOnly.
Security
Insurance certificates contain vendor names, policy numbers and coverage limits. Here is exactly how that data is handled.
Every page and upload runs over HTTPS with TLS 1.2+ and HSTS enabled. Session cookies are marked Secure and HttpOnly.
Uploaded certificates are encrypted with AES-256-GCM before they touch disk. The encryption key is derived from a server secret and never stored alongside the files.
Daily backups of the database are encrypted with AES-256 before leaving the database. Backups rotate after 14 days.
Passwords are hashed with scrypt. Each workspace is isolated by tenant ID, API keys are stored hashed, and every upload, review and requirement change is written to an audit log.
Document extraction runs on our own servers. Certificates are not sent to an external model provider for processing.
You can delete a vendor or document at any time. Deleting a document removes the file from active storage; audit events remain for the life of the workspace.
Questions or a security concern? Email support@coiprove.com — we answer within one business day.