On this phone
Your file stays where it already is, so you don't end up with two of everything. It's sealed the moment you send it. Before that, it's as safe as your phone is, so if your phone is locked, so is your file.
A flamenet.io account is not a Flamenet Messenger account. The two sign-ins are separate.
Not on our servers. Not in a folder we could open if somebody asked us nicely. You add a file, you organise it, and when you send it to someone it travels sealed the whole way. The server holds the sealed blob until the person you sent it to collects it, and clears it after thirty days whether they did or not. It cannot open it at any point, and that copy is the only one in between.
On Android now, and on iPhone in the TestFlight beta. Files shipped on Android in 0.11 and has its own place in the bar. The iPhone build carries it too and is installable as a TestFlight beta, which is a beta rather than the App Store.
A holiday photo and a signed contract don't need the same care, so you get to choose. Here's what each one gives you.
Your file stays where it already is, so you don't end up with two of everything. It's sealed the moment you send it. Before that, it's as safe as your phone is, so if your phone is locked, so is your file.
A locked copy inside the app, opened only by your passphrase. Someone holding your phone gets nothing readable. This is the one for the documents you'd mind losing, and you can move a file into it at any point, without hunting for it again.
Most things don't need locking away, and pretending otherwise just fills your phone up. Add everything the light way, then encrypt the few that matter, one swipe, and the app tells you plainly that you'll then have two copies until you tidy up the original.
A list of filenames tells you nothing about what you're about to send. Every file here carries a marking, how confidential it is, and which part of the business it belongs to, and it stays with the file when it travels, so it arrives filed the same way rather than landing in a heap.
The level is spelled out on every row. Colour helps you scan, but it's never the only thing telling you, nobody should be deciding whether a document can leave the building by remembering what amber meant.
Send something and its marking goes too, so it lands under the same heading on the other phone instead of quietly becoming ordinary. The person receiving it sees what you saw.
Levels and areas are whatever your organisation already calls them. Nothing here assumes a government scale, and a level we haven't been given a name for is shown as itself rather than guessed at.
A level decides who can open a file. It does not decide where a file can be put: if you can read something, nothing here stops you filing it somewhere less protected. Marking is a filing system with teeth on the reading side, not a guard against someone carrying material downward.
We used to make share links. They worked, and the server couldn't read them, but a link is a key anybody can forward, and it has no idea what it's carrying. So we took them out.
Now a file goes to someone you've chosen, through the same encrypted channel as your messages. Before it sends, the app tells you who will be able to open it, in those words. That sentence is deliberate: a marking says how careful to be, and handing someone the file is you deciding they're allowed. Nothing further down the line will second-guess it, so the moment you tap send is the moment that matters.
There is no account to make on any other service, no public link, and no phone number needed. One thing to know: a file is sent exactly as it is, including anything inside it, such as where a photo was taken.