SendIt security
SendIt reduces the time a shared file or code snippet remains available. Browser-to-server traffic uses HTTPS, uploaded file content is encrypted before storage, and the receive API checks the access code and expiry before returning content.
A four-digit code is convenient, not a high-assurance secret. Recipients can copy delivered content, expiry blocks application access before scheduled cleanup, and SendIt is not end-to-end encrypted. Read the full security page for practical precautions and current limitations.
Evaluate the risk by considering the content, recipient, access lifetime, and what happens after delivery. Remove unnecessary data, use the shortest expiry, keep the code private, confirm receipt, and delete local copies when they are no longer needed.
If a code is exposed or a security issue is suspected, contact mmbrothersteam@gmail.com with the affected route, approximate time, and reproduction details. Do not send live passwords, private keys, or sensitive file contents in the report.