Security at Phigon

Access keys

Administrators sign in to the Phigon app with a workspace access key. Only a SHA-256 digest of each key is stored, each key has one role (administrator, operator, viewer, or auditor), and keys can be revoked at any time. The desktop app stores its key with the operating system's encrypted key store.

Machine credentials

Each paired machine has its own credential, issued after a one-time pairing code and the owner's local approval. Credentials can be rotated or revoked, and the stream refuses to send them to an endpoint other than the one it was paired with.

Isolation

Machines, credentials, audit records, consent, telemetry, and deletion jobs are scoped to one workspace. Requests fail closed when authentication is missing or invalid.

Encryption

Traffic uses TLS. Stored telemetry and action records are encrypted with application keys, and the observer's local delivery queue is encrypted on disk.

Guardian

Guardian decisions are made centrally. The observer has no local switch to weaken a policy, uncertain model reviews fail closed, and an approval can never override a prohibition.

The desktop app

The app's interface has no direct network access: a strict content security policy, a sandboxed renderer, and context isolation keep the access key in the main process.

Reporting a vulnerability

Email nikku@phigon.online with details and steps to reproduce. Please do not include real credentials or other people's data.