Zas moves things — files, photos, text — between your devices and the people you choose, then gets out of the way.
Send something from one device, use it on another, done. No cables, no emailing yourself, no chat with yourself growing forever. Whatever you don't pin leaves on its own, so there is nothing to tidy up later.
Messengers are built for conversations: what you send yourself piles up in an endless chat, photos get compressed, and your files live on their servers. Zas sends the original within the limit shown by the app, without compression. It encrypts the file before upload and deletes it when its time runs out.
Those are warehouses: you store, sort folders, manage quotas and pay to keep everything forever. Zas is a corridor: things pass through, get used, and leave. There is nothing to organize and nothing piling up. Content is encrypted on your device before it travels.
Everything is encrypted on your device before it leaves. The database and object storage receive encrypted bytes, not open filenames, content, or previews. A separate service derives account keys. Zas therefore does not call this design end-to-end encryption. For public links, the key is after # and a normal request does not send it to the server.
Yes. Share one item with a public link that dies when the item does, or share a whole channel with someone. Content stays encrypted while it is stored and transported.
Because the sending device marked it as possibly holding a password. That check happens on the sending device before encryption. The mark stays only inside the encrypted item data. The server does not store it as a readable field. Tap the note to reveal it. It covers itself again when you switch channels or return to the tab. This only protects against someone reading over your shoulder. A note with no mark is shown normally. This does not mean it holds no password. You can turn covers off in Settings.