Vaultedo in six steps
Vaultedo watches who opens your app, records every attempt to copy, scrape or take it, marks every screen so a leak traces back to the viewer, and enforces only when you say so. Watch mode is the default: nothing is blocked until you switch it on.
About 60 seconds, with the console's own screens and a voiceover. Read the brochure · PDF
01 · INSTALL
Paste one tag on the page, or add one line to your build. Your coding agent can do it for you over MCP: it registers the app, makes a scoped key and adds the tag.
02 · WATCH
View source, saved copies, a headless browser pulling pages, a debugger left open. Each one is recorded with its address, time and device. An alert reaches your inbox, capped so it never floods.
03 · TRACE
Every screen carries a forensic code, a 2 by 2 pixel mark on the blue channel that the eye cannot see. When a screenshot leaks, the code is read back from the image itself and points to the viewer and the time.
04 · ENFORCE
Enforce refuses right-click, copy, the shortcuts, print and framing for the app you choose. Your own console is never blocked by it. Turn it off again from the same switch.
05 · SEE
Every figure opens the events behind it, and every event opens its fields. See where attempts came from by hour and day, which screens were opened, and by whom after sign-in. Events are kept for 90 days.
06 · TRY IT
The website has four rooms: the code, copies and robots, screenshots, and the window itself. Three attacks in each, twelve in all. Press one and watch the window, the gate and the console. Outcomes are shown; how it decides is not.
It does not make the code unreadable to a determined person with time, and it does not stop a camera or an operating-system screenshot. It makes copying expensive, makes every attempt visible, and makes a leak traceable.