Frequently asked questions
Common questions cover whether an account is required, how codes work, how files are downloaded, the 24-hour normal expiry ceiling, practical file-size limits, code languages, repeated downloads, cleanup timing, and the absence of a normal manual revoke endpoint.
SendIt uses HTTPS for transport and encrypts uploaded file content before storage, but it is not end-to-end encrypted. A four-digit code is a convenience credential, not a high-assurance secret.
If your question is not answered here, contact the SENDIT team at mmbrothersteam@gmail.com and we will reply within 24-48 hours.
SendIt is best understood as a short-lived transfer workflow. It can help with a device-to-device handoff, a client draft, a student assignment, or a code review example, but it does not provide folders, comments, guaranteed retention, one-time viewing, or a normal manual revoke button.
For every transfer, verify that the content is yours to share, remove unnecessary sensitive values, choose a practical expiry, send the code privately, and keep a separate copy until receipt is confirmed. The Security and Sharing Guide pages explain these choices in more detail.
Support requests should include the affected page, approximate time, and a clear description of what happened. Never include your password, private key, API token, or the full contents of a sensitive file in a support email.