Reference
Monitoring disclosures and permissions (reference for administrators)
YuviRed 1.0, agent 1.8.2, extension 0.5.5. One place for what the software needs on a computer, what it changes, and what you must tell people. This is not legal advice. You, not YuviRed LLC, are responsible for notice, consent and works council duties where you operate.
What the agent needs
| Item | Detail |
|---|---|
| Install | a local administrator, running Install-YuviRed-Agent.cmd from PowerShell as administrator, from a folder only administrators can change |
| Runs as | the Windows service SyntinelRedAgent ("YuviRed Endpoint Agent"), SYSTEM, delayed automatic start, restart on failure. The service name, the state folder and the native messaging host name below carry the product's earlier name; it will change in a later release |
| Files | C:\Program Files\YuviRed Agent (includes NOTICE.txt, the extension folder for Load unpacked, and setup\store-extension-ids.json, empty in this release) |
| State and log | C:\ProgramData\SyntinelRed (SYSTEM and Administrators only); log logs\syntinel-agent.log |
| Network | outbound HTTPS to your server on TCP 8443 only; it trusts only the server's own certificate from enrol.yuvired and changes no Windows trust store. It also asks the computer's DNS server for the name of every remote address it reports (a reverse lookup) |
| Local port | the Agent Monitoring System (AMS) bridge listens on 127.0.0.1 port 47811 whenever the agent runs as a service, connector or not; it accepts nothing from other computers |
| Never collected by the agent | keystrokes, clipboard, screenshots, page contents, prompt and reply text, document contents |
Browser and registry changes
| Change | When |
|---|---|
HKLM\SOFTWARE\Google\Chrome\NativeMessagingHosts\com.syntinelred.native_host, the same under Microsoft Edge, and under SOFTWARE\Mozilla\NativeMessagingHosts | always, at install; removed at uninstall |
Chrome and Edge policy: force-install entry, native messaging allowlist, extension backendUrl and captureLevel (follow server) | not in this release: the agent installer writes these only once the store ids ship in a later build, and never the consent value; it records what it wrote under HKLM\SOFTWARE\SyntinelRed\ExtensionWiring and removes it at uninstall. Today it prints "Browser extension: not in the Chrome and Edge stores yet" and the extension is loaded by hand |
Chrome and Edge policy written by the agent at run time, including consented = 1 | only where the console setting Remote Browser Extension Wiring is active; on a YuviRed Lite server it is inactive (the server holds no extension signing key), so nothing is written |
| Browser blocked-URL or extension-disable policy values | only when an administrator approves a response action; reversible |
| Managed settings files of Claude Code, Codex, Gemini CLI, Cursor, Copilot CLI, Windsurf (hooks) | only when an administrator turns on an AMS connector for that tool; removed at uninstall |
The server also writes one inbound firewall rule (TCP 8443, Domain and Private profiles) when network mode is on.
What to give the people who are monitored
- The monitoring notice (
notice.html, templatefrontend/legal/notice.md) and, for detail, the data notice (data-notice.html). The notice marks lines "[Your organization: ...]" that you must complete or delete: purpose, legal basis, retention you set, whether full capture or AMS connectors are on, who has console accounts, where the server is. Set Organization Name and Privacy contact in Configuration, System so the notice shows them. - Notice before installation, and again before you switch on raw capture or AMS connectors.
- The privacy policy (
https://yuvired.com/privacy) and terms (https://yuvired.com/terms) where your policy needs them.
Every server serves: https://<server>:8443/static/legal/ with manifest.json, eula.html, privacy.html,
notice.html, data-notice.html, third-party.html. The console Legal page under Admin lists them. The agent
notice is NOTICE.txt in the YuviRed Agent folder, and each Add Computer README.txt repeats the duty.
The acceptance record
Installing the server records who accepted the terms at %ProgramData%\YuviRed\status\legal-acceptance.json
(unattended install: YuviRed-Lite.exe /quiet ACCEPT_EULA=1; exit 5101 without the parameter). Running the agent
installer is a separate act: it confirms that your organization may monitor the computer and has told its users.
YuviRed does not record that confirmation per computer.
Things people often miss
- Every web connection of every program is reported, not only AI.
- Any person who can sign in to the console can read endpoint identity and raw telemetry, whatever the role.
- Masked fragments are stored unencrypted; raw capture (off by default) is encrypted and kept 24 hours.
- A person using a browser can narrow the extension's checks on its options page; the console is not told.
- In this release every extension is loaded by hand and consent is the person's own tick on the options page. Nothing in the product sets consent by policy on a Lite server; the agent's wiring route that would is inactive.
- A check-in that cannot be sent is lost: the agent keeps no offline queue, so a computer that was away for a day reports nothing for that day.
- Uninstalling keeps
%ProgramData%\YuviRedon the server; the agent removal deletes its own data.
Notice templates: frontend/legal/notice.md, frontend/legal/data-notice.md, frontend/legal/privacy.md.
Related guides: endpoints.md, extensions.md.