Security
Last updated 18 November 2026
How accounts are protected
- Passwords are stored only as a salted scrypt hash. Sign-in locks after five wrong tries.
- The sign-in cookie cannot be read by scripts, and we store only a hash of it.
- Every project, clip and file request is checked against the signed-in account. Share links expose one clip and nothing else.
- Card details are handled by Stripe and never reach our servers.
Report a vulnerability
If you find a way to reach someone else's data, bypass payment, or run code on our systems, tell us first. Use the form below and include the steps to reproduce it.
Our side of the deal
- We acknowledge a report within three working days and tell you what we plan to do.
- We will not take legal action against research done in good faith under these rules.
- We credit you when the fix ships, if you want that. We do not pay bounties at this stage.
Rules for testing
- Use your own account. Do not open, change or delete other people's projects.
- No denial of service, no spam, no social engineering of people.
- Give us a reasonable time to fix a problem before you publish it.
Machine-readable version: /.well-known/security.txt