Docs Guides

Employee privacy notice

This is a template. Your employer fills in the parts in [brackets] and gives it to you before Phigon is set up on your computer. It is not legal advice; your employer is responsible for meeting the law where you work.


[Company] uses Phigon to supervise the AI coding agents (such as Claude Code, Codex or Cursor) that run on work computers. This notice explains what Phigon collects from your computer, what it never collects, and what you can do about it.

How it works

A small program, the Phigon observer, runs on your computer. It finds the AI agents installed there and reports what they do to [Company]'s own Phigon server. The data is kept by [Company], in [Company]'s own database. Phigon, the company that makes the software, does not receive it.

The observer is open source. You can read its code at github.com/phigonai/observer.

Who agreed to collection

[Company]: keep the paragraph that matches how you set Phigon up, and delete the other.

You agree at setup. The observer starts only after someone at your computer pairs it and accepts one of two profiles. The pairing command shows exactly what the profile covers, and what [Company]'s administrators may do on your computer, and asks you to type yes.

[Company] agreed for its computers. [Company] installs the observer with its device management, using an enrollment code, and has chosen the [metadata / full activity] profile for its computers. You are not asked when it is installed: [Company]'s [name the policy] is the consent. Phigon records that [Company], not you, gave this consent, and administrators see that in the Phigon app. When the observer starts collecting, it shows a system notification once, "Phigon is recording AI agent activity", saying what it records and to ask your IT team for details, and again if the profile changes. [Company] can turn that notification off, and it may not appear when the observer runs without your desktop session, which is why [Company] tells you here first.

Metadata profile (the default)

Phigon collects facts about the AI agents, not what they say or do:

  • which AI agents are installed and running, and their versions;
  • when agents start and stop, and whether they are healthy;
  • the kind of activity (for example "a file was changed" or "a network call was made"), its time, and whether it succeeded;
  • your computer's name, operating system and the observer's version.

It does not collect prompts, replies, commands, command output, file names, file contents, web addresses or page contents.

Full activity profile

Only under full activity consent (yours at pairing, or [Company]'s with an enrollment code) does Phigon also collect, for supported agents:

  • what you ask the agent and what it answers (prompts and replies);
  • commands and tool calls the agent runs, and their output;
  • file paths, file contents and changes the agent works with;
  • web addresses and page content the agent reads, and network endpoints;
  • past conversations with supported agents, including ones from before setup. They are imported once, then collection continues live.

Environment values, which often hold passwords, are not collected under either profile unless they are turned on separately.

If the consent covers only metadata, the observer keeps content off even if [Company]'s server or a local setting asks for more.

Secrets are removed on your computer

Before anything leaves your computer, the observer removes passwords, access tokens, API keys, private keys, cookies, sign-in headers, one-time codes and other secret formats it recognises. If removing a secret fails, that field is left out. Files the observer keeps on your computer follow the same rules, and its own log masks secrets too. This is a safety net: it catches common formats, not every possible secret.

What Phigon never collects

Phigon does not record your screen, keystrokes, camera, microphone or location. It watches AI agents, not your other work.

What [Company] can do

  • Administrators see the collected activity in the Phigon app.
  • Administrators can stop an AI agent on your computer, and run commands they approve there, check the computer (its operating system, memory, disk space and running agents) or schedule a restart. When you pair your computer yourself, you agree to this at the prompt, unless you pair with --remote-actions stop-agents (only stopping agents) or --remote-actions none. With an enrollment code, [Company]'s consent covers it.
  • Whenever Phigon stops or blocks an agent, runs a command (as it starts and when it ends) or schedules a restart, you see a system notification saying so, with the administrator's reason. [Company] can turn these notifications off.
  • If [Company] turns on AI in Phigon, some collected activity may be sent to the AI provider [Company] chose, to answer administrators' questions and to check agents against [Company]'s rules. [Name the provider, or say "none".]
  • Activity is kept for [30 days, the default] and then deleted. Records of what administrators did are kept for [365 days, the default].

See what is collected

On your computer, run:

phigon-observer doctor --json

It shows the profile this computer runs with, the categories of data it may collect (enabledCollectionCategories), who consented (consent: you, or [Company] with the name of its enrollment code) and where it sends them. It sends nothing. To see which agents the observer finds, and why, run:

phigon-observer discover --explain

Remove your computer

To stop Phigon on your computer, run:

phigon-observer remove-machine

This stops collection, revokes your computer's key so it can no longer send anything, and deletes the observer's local queue. Activity that was already sent stays with [Company] until an administrator deletes the computer or the retention period above ends. Ask [contact] if you want it deleted sooner.

If [Company] installed the observer with device management, it may run under an account you cannot use, and [Company] can enroll the computer again with a new enrollment code. Ask [contact] about it instead.

Questions

Ask [name or team, and how to reach them].