Update integrity
Release packages should be signed and verifiable before installation.
Security
Ghosium treats secure updates, risky navigation, permissions and responsible disclosure as parts of one browser security model.
Release packages should be signed and verifiable before installation.
Prefer encrypted navigation and make insecure downgrades visible.
Rely on modern process boundaries and upstream Chromium security architecture.
Keep camera, microphone, location and notification access under explicit site control.
Surface executable and suspicious-download risk before a file is opened.
Track upstream Chromium security releases and prioritise critical fixes.
If you believe you found a vulnerability in Ghosium or this website, report it privately to security@ghosium.com . Include reproducible steps, affected versions and expected impact where possible.
Machine-readable security contact information is also available at /.well-known/security.txt.
The public website uses HTTPS redirection, a restrictive Content Security Policy, anti-framing protection, local assets and protected server-side application files.