Docs / Operate

Frequently asked questions

#Is Phigon an AI-agent surveillance tool?

Yes. Phigon monitors supported AI-agent activity across authorized machines. It combines fleet health, activity history, and evidence state in one private workspace.

#Does Phigon monitor people?

No. Phigon is designed to supervise AI systems with informed machine-owner consent. It is not a covert employee-monitoring product.

#Does pairing mean the owner has consented?

No. Pairing intent starts a request. The machine owner must review and explicitly accept the collection scope locally.

#Does Phigon collect prompts and responses?

The metadata-first default is designed to exclude prompts, responses, reasoning, terminal output, files, browser contents, and environment values.

#What happens when evidence is missing?

Phigon should show the limitation and leave attribution unresolved. Missing evidence never becomes a positive claim.

#Why is activity marked limited?

Some useful evidence is present, but expected coverage is incomplete. Open the evidence details to see which source is unavailable.

#How do I sign in?

Open the Phigon app and paste your workspace access key. There is no account or password. Read about access keys.

#Is there a limit on connected machines?

No. Connect every machine you are authorized to supervise.

#Can Phigon support enterprise fleets?

Yes. Start with a narrow, authorized pilot and expand in controlled stages. Read the enterprise guide or book a demo.

#Where can I get help?

Book a demo, email nikku@phigon.online, or contact @phigonai on X.