Sendly is engineered for seamless collaboration, developer productivity, and reliable file sharing. By utilizing Sendly, you explicitly agree not to employ our network architecture to transfer, mirror, or publish:
While we cannot inspect zero-knowledge encrypted payloads or LAN P2P streams, any substantiated reports of service abuse or malicious hosting will result in instantaneous automated subnet blocking and infrastructure blacklisting.
Sendly is provided on an 'as-is' and 'as-available' basis. While our distributed infrastructure aims for 99.9% operational reliability and sub-second WebRTC signaling, we do not guarantee uninterrupted execution under network interruptions or strict firewall restrictions. Sendly is not liable for data transmission failures or uncompleted peer handshakes. We strongly recommend maintaining backups of mission-critical archives before transfer.
To ensure global network equilibrium and optimal server responsiveness, cloud-routed standard transfers are capped at 1GB per payload, and Client-Side Encrypted transfers are capped at 50MB to guard against browser RAM exhaustion on low-power devices.
1GB Local Caching Mechanics: When a file up to 1GB is uploaded for standard transfer without peer-to-peer discovery, the file is temporarily cached on our secure cloud infrastructure. This cache is strictly ephemeral. The cache is entirely volatile and immediately self-destructs the byte-payload when the designated recipient downloads the file, or after a maximum 10-minute timeout—whichever occurs first. We do not maintain archival backups or long-term block storage for any user content.
Unbound Transfers: Users requiring multi-gigabyte or uninterrupted massive archive transmissions should utilize ⚡ Local Drop, which imposes zero file size limitations or throttling by bypassing cloud infrastructure entirely and streaming directly over LAN interfaces.