How Likz Drop moves your files, what we can and cannot see, and how live transfer differs from optional Keep 24h. This page is product documentation — the legal details live in the Privacy Policy.
In one minute
- Live transfers go device-to-device when possible. Across networks, an encrypted relay may forward sealed bytes without reading them — and does not keep them as cloud files.
- Keep 24h is optional, for group drops only: a temporary encrypted copy with a quota.
- No account required to start. Sign-in is optional for linked devices, identity, groups, and Pro.
- The app can label which path a transfer used (direct vs relay).
Data flow by path
Same Wi-Fi / LAN
Devices connect directly. Your local network carries the encrypted stream. Likz servers are not in the file path.
Different networks
Likz tries a direct path first. If that fails, encrypted bytes go through a relay that only forwards — no decrypt of the payload for live transfer.
No internet
Android ↔ iPhone can transfer without the public internet (where supported). No cloud hop for the file bytes.
Share by link
Receiver opens a link in a browser. The sender stays online and approves the download. Stream is still sealed for the live handoff — not the same as Keep 24h storage.
Live transfer vs Keep 24h
| Mode | What moves | Stored by Likz? | When |
|---|---|---|---|
| Live transfer | Encrypted stream between endpoints (or via relay) | No durable file copy of contents | Default send / share link / offline / remote |
| Keep 24h | Temporary encrypted object for a group drop | Yes — short retention, quota (Free/Pro) | Only when you use Keep on a group drop |
Quotas and plan rules: Pricing. Policy language: Privacy · Keep 24h.
Encryption & trust boundaries
- Live transfers use per-transfer keys and end-to-end encryption on supported paths; the product verifies the device-to-device connection when that path is used.
- The relay is designed to forward opaque encrypted bytes for live streams — it is not a place you browse old files from.
- Control-plane metadata (nicknames, offers, device presence, link tokens) is separate from file contents. See Privacy for categories and retention.
- No method is 100% secure. Threats still include compromised endpoints, malicious local networks, and phishing of share links or sign-in.
What this does not protect against
- Someone with physical or account access to either device
- Malware on a sender or receiver
- You sending to the wrong nickname or approving the wrong download
- Platform bugs, OS permission denials, or network policies that block a path
Account, Guest, Pro
Guest mode needs no account. Optional sign-in (email code, Google, Apple) links devices and enables Pro via the app stores. Card numbers are handled by the store — not entered into Likz for App Store purchases.
Operational status
Relay and API availability: status.likz.me checks. Nearby and offline modes do not need Likz servers for the file path, but still need OS permissions and a working local link.