Security

Control access, data, and every run

Secrets stay in protected storage, files are checked before launch, and visual assistance requires separate consent.

01

Access code and secrets

The app stores the license, service keys, and proxy passwords in operating-system protected storage. The interface sees whether access is configured, not the secret values themselves.

  • Signed activation and server-side license checks
  • Startup is blocked when protected storage is unavailable
  • Reset removes local secrets and app data
02

Program files and updates

Encrypted files for the built-in Ghost Chromium browser are checked with SHA-256, a file checksum. Release information includes the version, size, hash, key, and validity period. Windows signing rules are tied to activation.

03

Privacy of visual help

A screenshot is sent only after explicit consent. Input fields, private areas, and embedded windows are covered; each request contains one JPEG and a short-lived key.

04

What this does not guarantee

Automation cannot prevent blocking and does not replace search-engine or website rules. Public launch, commercial Windows signing, and remaining external checks each have to pass their own stages.

PROJECT GHOST

Check your use case

Describe the workflow. We will review compatibility and explain the invitation terms.

Request access