Private image sharing is coming.
Read the planned device-to-device transfer model and the parts that are not built yet.
Coming
Sharing is coming, and it is not available yet.
Direct sharing is not built today, so this page cannot create a link and you cannot send an image from here. What follows describes the plan in plain terms and names the parts that are not switched on.
How the planned model works
When sharing launches, you will pick an image and the tool will create two things: a share link and a separate key. The link will point at a temporary rendezvous; the key will be the secret that proves you may receive the file. Send them separately when you can. IndoImage will not need your image or the key to route the session, and it will not keep a copy of the file.
If the two devices can reach each other, they will connect directly. If they cannot, the encrypted traffic will pass through a relay that forwards bytes without holding the file. The relay is a fallback, not storage, and the connection will say which path it took instead of calling every connection direct.
The share will stay alive only while the sharing browser tab or the Beacon app stays connected. Close the tab with no other sharer, and the temporary share identifier will expire; your local file will not change.
What is not here yet
- No share link can be created today.
- No QR code is shown, because there is no working link to encode.
- No file is chosen on this page; that control belongs to the tools that work today.