A sandboxed container for WhatsApp, Telegram, and email. Files and images are redirected and opened inside a single-use cloud sandbox the moment they arrive — far from your device. The exploit isolates in the box.
File parsers are a proven, recurring source of real exploits — and messaging apps are the most common way one reaches your phone.
WhatsApp, Telegram, and email clients decode whatever they're sent — there's no layer between "someone sent this" and "your phone parsed it."
Malware is routinely packaged to look like an ordinary photo or document, passing casual inspection by file name or thumbnail alone.
With auto-download and auto-preview left on, a messaging app can render a file before you ever get a say — that's the setting GuardBox asks you to turn off first.
GuardBox doesn't scan the original file for known threats — it never trusts the original at all. It decodes it, discards it, and rebuilds a clean copy from scratch.
Share a file to GuardBox the same way you'd share it to anyone else — the original never lands in GuardBox's own storage.
Forward to @GuardBox and the file is pulled server-to-server from Telegram — it never travels through your device at all.
Route attachments to GuardBox before they ever reach a client-side mail parser.
What you see afterward is a rendered, pixel-based view of the clean copy — nothing is decoded locally.
Isolated, ephemeral processing hosted in the EU, torn down after every file.
Programmatic submission for teams who want GuardBox wired into their own tools.
Journalists, activists, and families who want a safe way to open what's sent to them — free, self-hostable forever.
News agencies, NGOs, and public-sector teams handling sensitive files under GDPR and NIS2 expectations.