Document storage
Uploaded documents should be stored in private object storage, not as database blobs.
Files should be downloaded through signed temporary URLs rather than public file links.
ComplyChase AI is designed around private document collection, controlled access, and clear proof records for client document workflows.
Last updated: 1 June 2026
Uploaded documents should be stored in private object storage, not as database blobs.
Files should be downloaded through signed temporary URLs rather than public file links.
Users access data through their current workspace. Staff roles should be used to limit who can manage clients, documents, settings, and billing.
Public upload links can expire, be disabled, limit file size and type, and be rate limited to reduce abuse.
Upload events should be logged so teams can see when proof was received.
Security headers, login throttling, file validation, activity logs, backups, and private buckets all reduce risk.
Admin 2FA and stronger policy controls may be added as the product matures.
If you believe you have found a security issue, contact hello@complychase.ai with enough detail for us to investigate.
Questions about this page?
Contact hello@complychase.ai and include the page name in your message.