Security

What we do to protect the files and answers your clients send you, written without hand-waving.

Files

Uploaded files go into a private storage bucket. Nothing is public. Downloads use short-lived signed links that expire in minutes, and uploads are checked for type and size before they are accepted.

Data isolation

Every row of customer data carries an organisation id, and the database enforces access with row-level security. A request from one account cannot read another account's rows, even if application code is wrong.

Clients and links

Clients do not have passwords. Each project link carries a random token that is stored only as a hash. You can revoke a link at any time. An optional six-digit email code reopens a project on a new device and expires quickly.

Accounts

Sign-in is handled by Clerk. We never store your password. Payments are handled by Polar, and we never see card numbers.

Transport and headers

Everything is served over HTTPS. This site sends a strict Content Security Policy, forbids framing, and runs no inline scripts.

Retention

Files stay for 12 months after a project is marked complete, with warnings at 60 and 30 days. After that they are deleted from storage.

Report a vulnerability

Email security@chasecopy.com. Please give steps to reproduce and do not access other people's data. See security.txt.