A browser that cannot be turned against you

A browser that cannot be turned against you

A strict content policy, code from a lesson run in a sealed sandbox, and uploads scanned before anybody can open them.

Three specific things

The pages refuse to execute script that was not served as part of them, which closes the most common route from a stray piece of text to running code.

Code somebody writes in a lesson runs in a sandbox of its own with no cookies, no access to our pages and no network but ours. A site or page somebody uploads to present is put in an isolated origin for the same reason.

An uploaded file is not reachable until a virus scan has returned clean, and an unreachable scanner fails the upload rather than waving it through.

What we will not claim

Nobody should believe a security section on a marketing page. What we can offer is specifics you can check, and an answer to any question your security team wants to ask.

Read next

  • One organisation can never see another’s data

    Enforced by the database itself, not by remembering to write the right query. A mistake fails closed instead of leaking.

  • The Lab

    One document the whole meeting edits, with Python and JavaScript running inside the browser rather than on our machines.

  • Chat, with files

    Messages during the meeting, attachments up to ten megabytes, and a virus scan that has to pass before the file is reachable at all.

Everything it does

Want to see this working?

Tell us what you are trying to do with it and we will show you that, rather than a tour of everything else.

info@seeuall.com
    A browser that cannot be turned against you — SeeUAll · SeeUAll