📤 Send

Start a Transfer

Create a session. Share the code. They connect. Then you send.

Sealed on your device30 secNo account
☝️ Any file. Any person. Sealed before it leaves.
📥 Receive

Join a Transfer

Got a code? Connect to the other person.

Bridge active
30
Your side
📤
Sender
📁
Drop file here
🔒
Sealed
Their side
📥
Receiver
✅
Received
Sealed on your device. Through the bridge. Unsealed on theirs. We're just the pipe.

How TimedBox works

The short version

Your file gets sealed on your device before it goes anywhere. The sealed package passes through our system. The other person unseals it on their device.

We run the bridge. We can't open what's inside it. The code is the only key, and it never touches our servers.

Why should you believe that?

1. You can watch it happen. The bridge shows the handoff in real time. Your file is sealed before it enters, and unsealed after it exits.

2. The math makes it impossible. The sealing method is the same one banks and governments rely on. Without the code, cracking your file would take every computer on earth longer than the universe has existed.

3. We published the code. Every line is open source. Anyone can audit it.

What actually happens

The handoff
1
Your device seals the file using the code as the key. The sealed version is the only thing that leaves your screen.
2
The bridge moves the sealed package. We can see something is moving through. We cannot see what it is.
3
Their device unseals it using the same code. Wrong code = garbage. No recovery.
Nothing stored
Nothing logged
Open source

What we physically cannot do

Open your file. Read your file. Save your file. Know what your file is. Know who you are. Recover your file if the timer runs out. This isn't a policy — it's how the system is built.

Need audit trails & compliance?
SecuredBox
Same sealing method. Full accountability. CMMC L2 ready.
SecuredBox →