EchidnaA browser you can trust with sessions.
Your profiles carry logged-in accounts. We build, ship and run the browser with that in mind, from the first byte we compile to the last update you install.
One signing authority.
Every app installer, engine package and update feed is approved by a person and signed with keys that never touch the build machines.
- Separated build and signing. Builds run on fresh machines; signing happens elsewhere, only after a human approves the exact files.
- Signed release feed. The app only accepts updates listed in a feed signed by our licence authority, with a short expiry so a stale or replayed feed is refused.
- Signed inventories. Every engine package lists each file with its SHA-256; the inventory itself is signed.
Defence in the running browser.
Sandbox always on
Chromium's process sandbox stays enabled. Options that would switch it off, or route rendering through a remote host without it, are refused before the browser starts.
Exploit mitigations
The Windows engine is built with Control Flow Guard, CET shadow-stack compatibility, ASLR and DEP; the app and engine services add Control Flow Guard and CET too.
Verified engine updates
A downloaded engine is unpacked, checked file by file against its signed inventory and only then made available. A failed check leaves the current engine in place.
Local control only
The engine listens on 127.0.0.1 only. The app's own token changes every time the app starts; scripts and agents get a separate automation token that you turn on, can replace at any time, and that is limited to profiles, browsers, proxies, flows and schedules. Tokens are compared in constant time, and the customer app can't listen on another address.
Guarded outbound requests
Webhooks, mail connections and proxy tests resolve their target first and connect only to the checked public addresses, so a hostile URL cannot reach your local network or cloud metadata.
A locked-down app shell
The desktop app runs with a strict content security policy: no remote scripts, no frames, no plugins.
What we can see, and what we cannot.
Never leaves your computer
- Your profiles, cookies, local storage and history
- The pages you visit and what you do on them
- Your proxy credentials and automation scripts
- Screenshots, downloads and files
Known to the licence server
- Your account e-mail and licence
- A salted hash identifying each activated device, never the raw hardware ID
- Each device's label, operating system and app version
- The IP address a request comes from, for abuse protection
The browser is built from ungoogled-chromium: no Google API keys, no Safe Browsing pings, no crash or metrics uploads. Details are in the Privacy Notice.
Found something? Tell us first.
We take reports seriously and reply quickly. Please give us a reasonable time to fix an issue before you disclose it.
security@renotsnkrs.com